04-02-2023, 11:58 AM
If you are using a terminal program that does NOT input/output true ASCII when trying to connect to the router, this will happen. The AT*NS0 works because it is providing the CORRECT router name from the scan. What is being sent by the terminal program is NOT correct if this is failing like you show. Once your WiModem232 is connected your terminal program can then be changed to any other terminal type (VT100, VT152, ANSI, etc.)
Once the router name is correct, it is saved until you change it. Every time you power on the WiModem232 from that point it will properly connect. The only exceptions are firewalls, or being too close or to too far away from the router. -46dBm should be fine, but anything in the -30's range (-30 is stronger than -40) could be a problem. Also, if *you* are sitting directly between the router and the WiModem232 your body can actually fully block the signal, because 2.4GHz is blocked by water and the human body is 95%+ water.
Once the router name is correct, it is saved until you change it. Every time you power on the WiModem232 from that point it will properly connect. The only exceptions are firewalls, or being too close or to too far away from the router. -46dBm should be fine, but anything in the -30's range (-30 is stronger than -40) could be a problem. Also, if *you* are sitting directly between the router and the WiModem232 your body can actually fully block the signal, because 2.4GHz is blocked by water and the human body is 95%+ water.