WiModem232 Pro won't save SSID and password

[Hans13]

First time setting up a WiModem232 Pro and it doesn't seem to want to save the router information. It acts the same under v1.60 and v1.70 (beta). I have tried setting the router and then powering off for a while. Likewise with button reset <10 seconds, button reset >10 seconds, AT&W, AT&F, etc. No set of conditions seem to get the router info to be saved.
 
When I initially set up the router, it works fine. The modem just doesn't seem to save the information and I have to manually set it back up each time I power back up or reset.
 
The SSID does have spaces; could that be a bug in the AT*NS[x],[password] setting?
 
I have to set the connection up using AT*N and then AT*NSx,password because the SSID has a space. Has anyone else set theirs up using the list and the modem not save the information?

[Hans13]

It might be related to this older thread? https://www.cbmstuff.com/forum/showthread.php?tid=1078

[Hans13]

Yep, there is a problem with setting up using AT*NS[x],[password] when there is a space in the SSID. The modem doesn't store it properly.

I set up a dummy router with an SSID containing no spaces and using *SSID and it saved the information.

I have since tried using *NS on the SSID with no spaces and it did not save that one either.

So, is it a problem with *NS?

[admin]

The router information is always saved, no matter if the SSID (or password) has space characters or not. I have had no reports (since 2014) of a problem with the AT*NS function.

What CAN happen is the entries change between when you do AT*N and AT*NS, so a different SSID could be selected instead of the one you think it is.

You can use WPS or the WIFI option to select the router and set the password.

[Hans13]

Thanks for the fast response.

Well, I spent several hours working with it today and used multiple routers. What I have found is that no matter what I do, the SSID is not being saved or recalled or something when *NS is being used. Over the several hours, I could not get ANY SSID to save with *NS; spaces or not and regardless of which router is being used. I am in the middle of farm land so there isn't like a bunch of SSIDs being detected.

The only way I can get a router to be saved is if I use *SSID and that requires no spaces. So, I have created a virtual network on our main router so I can have an SSID with no spaces for the modem. It's a temporary work-around.

So, do I have a bad modem or has a bug perhaps creeped in with *NS?

tl;dr - The modem I have is not recalling ANY SSID, regardless of spaces or not, when I use the *NS command. It is only being recalled when I set it with the *SSID, which requires that the SSID has no spaces.

[Hans13]

What CAN happen is the entries change between when you do AT*N and AT*NS, so a different SSID could be selected instead of the one you think it is.

That cannot be what is happening because I can set the router and use it to contact BBSes with the *NS command on any SSID. It simply doesn't recall the router after power off or reset. It reverts to no router found. The modem is connecting with the router just fine during the session.
 
So...

(no router connection)
.
AT*N
.
AT*NSx,password
.
(router connected)
.
Can use the modem to dial out and do all sorts of things, including ATDTgoogle.com:80
.
(power down the modem)
.
(no router connection)

[Hans13]

Okay, this is interesting. I noticed where the 2024 thread left off... "Maybe this only occurs if you have not done the SSID entry method at least one time before." So, I tested that possibility. Once I set the router using *NS, it no longer recalled it after power cycle. https://www.cbmstuff.com/forum/showthrea...10#pid6610

I was hoping that by setting with *SSID, it would fix any problem since it saves the router. Then, I could use *NS and it would save the router. No luck. The minute I use *NS, the router is no longer recalled after power cycle. IMHO, there might be a problem with *NS.

[Hans13]

This can be reproduced quite easily.

1) Set up a router with *SSID. Test that it connects fine. Reboot the modem. Notice that it retains the router setting.

2) On this same modem, set up the SAME router it has currently stored using *NS. Test that it connects fine. Reboot the modem. Notice that it does not retain the router setting.
 
(In #2, you can set up a different SSID/router but using the same removes one variable for testing puposes.)

[admin]

Yep, you are right - this is broken! I will look into it.

[Hans13]

Yep, you are right - this is broken!  I will look into it.

Thank you so much!
 
I'm good right now as my usage is on one router for a while and making that virtual SSID on my router is a useful work-around.