+- CBMSTUFF FORUM (https://www.cbmstuff.com/forum)
+-- Forum: CBMSTUFF PRODUCTS (https://www.cbmstuff.com/forum/forumdisplay.php?fid=1)
+--- Forum: WiModem (https://www.cbmstuff.com/forum/forumdisplay.php?fid=75)
+--- Thread: AT*L and AT*NET not working? (/showthread.php?tid=1167)
AT*L and AT*NET not working? - mnewkirk - 03-20-2025
Why would these not work? As I recall they worked in the past. I've used them to change ports??
For some reason I can't get it to work - I'm wondering if the modem somehow got damaged?
I just updated firmware to see if that would fix it.
AT*L results in error
AT*L=8502 results in error
AT*HELP shows command is there.
AT*NET also results in error.
Thanks,
Mike
RE: AT*L and AT*NET not working? - admin - 03-21-2025
This is correct. As stated in the documentation any command that has an option associated with it needs the proper suffix. If you want to know the listening port (AT*L) you would need to type:
AT*L?
Same for getting the NET info:
AT*NET?
To set the listening port to 8502 you would type:
AT*L8502
That command has no '=' in it like others to remain backwards compatible with some com programs.
RE: AT*L and AT*NET not working? - mnewkirk - 03-21-2025
(03-21-2025, 10:26 AM)admin Wrote: This is correct. As stated in the documentation any command that has an option associated with it needs the proper suffix. If you want to know the listening port (AT*L) you would need to type:
AT*L?
Same for getting the NET info:
AT*NET?
To set the listening port to 8502 you would type:
AT*L8502
That command has no '=' in it like others to remain backwards compatible with some com programs.
D'oh!! Rookie mistake. Thanks!!! I didn't think about going back to page 8 to see why the command wasn't working ;-)
RE: AT*L and AT*NET not working? - admin - 03-21-2025
Ha... don't feel bad... I had to go back and look at the manual myself to make sure there was actually info on using the question mark!