Posts: 16
Threads: 3
Joined: Mar 2024
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
Posts: 2,899
Threads: 148
Joined: Nov 2013
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.
Posts: 16
Threads: 3
Joined: Mar 2024
(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 ;-)
Posts: 2,899
Threads: 148
Joined: Nov 2013
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!