AT*BUSY - 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) +--- Thread: AT*BUSY (/showthread.php?tid=719) |
AT*BUSY - rosenrost - 05-20-2020 Hi, my WiModem232 responds "ERROR" when I try to change the busy message: Code: at*busy Firmware version is 3.03. RE: AT*BUSY - admin - 05-20-2020 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. RE: AT*BUSY - rosenrost - 05-21-2020 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 After seeing that, I put a dummy character in front: Code: at*busy=XBUSY RE: AT*BUSY - admin - 05-21-2020 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. RE: AT*BUSY - admin - 05-21-2020 OK, a new version that corrects this problem is now available. Use the auto-update feature to update your WiModem232: AT*UPDATE RE: AT*BUSY - rosenrost - 05-21-2020 Works perfectly, thank you. RE: AT*BUSY - admin - 05-22-2020 No problem, thanks for pointing that out! |