Posts: 6
Threads: 2
Joined: May 2020
Hi,
my WiModem232 responds "ERROR" when I try to change the busy message:
Code:
at*busy
ERROR
at*busyBUSY
ERROR
at*busyGO AWAY
ERROR
Firmware version is 3.03.
Posts: 2,806
Threads: 148
Joined: Nov 2013
The WiModem232 should be returning that error - because you are not entering the syntax correctly. To view the value of any command, you need to end it with a question mark (?)
So, to see the value for AT*BUSY, type:
AT*BUSY?
To set a new value type:
AT*BUSY=[new value]
I see that setting the new value is actually not correct in the manual (missing the = character). I will change that.
Posts: 6
Threads: 2
Joined: May 2020
05-21-2020, 07:35 AM
(This post was last modified: 05-21-2020, 07:37 AM by rosenrost.)
Ah, that helped me, thank you. I was referring to the manual which obviously is wrong at that point.
But, when I tried to follow your instructions, I discovered an issue: After changing the busy string everything is ok, but after writing the settings to memory and then resetting the settings, the first character actually gets lost:
Code:
at*busy=BUSY
OK
at*busy?
BUSY
at&w
OK
atz
OK
at*busy?
USY
After seeing that, I put a dummy character in front:
Code:
at*busy=XBUSY
OK
at*busy?
XBUSY
at&w
OK
atz
OK
at*busy?
BUSY
Posts: 2,806
Threads: 148
Joined: Nov 2013
Hmm... that means a byte in EEPROM is getting shifted over. I use everything RAM based (entire EEPROM is loaded into RAM) because I don't trust EEPROMs. I have seen them fail while in use. That's a hold-over from designing life critical products. I guess I never checked to see if the data was being stored into EEPROM correctly.
I will take a look at this.
Posts: 2,806
Threads: 148
Joined: Nov 2013
OK, a new version that corrects this problem is now available. Use the auto-update feature to update your WiModem232:
AT*UPDATE
Posts: 6
Threads: 2
Joined: May 2020
Works perfectly, thank you.
Posts: 2,806
Threads: 148
Joined: Nov 2013
No problem, thanks for pointing that out!