CBMSTUFF FORUM
Manual and the AT*SSID command - Printable Version

+- CBMSTUFF FORUM (https://www.cbmstuff.com/forum)
+-- Forum: CBMSTUFF PRODUCTS (https://www.cbmstuff.com/forum/forumdisplay.php?fid=1)
+--- Forum: WiModem232 / WiModem232 Pro (https://www.cbmstuff.com/forum/forumdisplay.php?fid=79)
+---- Forum: Usage (https://www.cbmstuff.com/forum/forumdisplay.php?fid=81)
+---- Thread: Manual and the AT*SSID command (/showthread.php?tid=602)



Manual and the AT*SSID command - Montezuma - 02-03-2019

The space between AT*SSID and the parameters seems to cause a problem.
The Wimodem232 manual says:


"To manually setup the SSID you would enter the following into your terminal
program:

AT*SSID [name][,passphrase]{RETURN}

Using the above example, if you wanted to setup the WiModem232 to use
the router with the name of NETGEAR24 (which has a passphrase of
WiModem1) you would enter the following into your terminal program:

AT*SSID NETGEAR24,WiModem1{RETURN}"

I think it should be:


Code:
AT*SSID[name][,passphrase]{RETURN}


and


Code:
AT*SSIDNETGEAR24,WiModem1{RETURN}



RE: Manual and the AT*SSID command - admin - 02-03-2019

Leading space characters after a command are ignored.


RE: Manual and the AT*SSID command - Montezuma - 02-04-2019

That is what I would expect, but I experienced that establishing a WIFI connection always fails when I have a leading space.


RE: Manual and the AT*SSID command - Montezuma - 02-08-2019

Today I double checked it and can confirm that a leading space is really causing a problem.


RE: Manual and the AT*SSID command - admin - 02-09-2019

I will look at it. I did change this awhile ago so you could include space characters in the password. Maybe the SSID also is affected.