03-24-2023, 10:32 PM
You would know what the modem init string is being sent to the WiModem232 by looking at the display.
Ok, try this and let me know if it works:
Type: AT*OFFHOOK?
Look at the response. If it is blank set it to something, ie:
AT*OFFHOOK=this is a test
Then check to make sure it is there by typing AT*OFFHOOK? again.
Now type:
AT&W
This store the setting.
Now type:
ATZ
This recalls the settings.
Now, check to see if the OFFHOOK string is still there by typing:
AT*OFFHOOK?
If the string is there, then the v6.01 firmware update is working. At that point, only AT&F could be responsible for resetting the contents of the OFFHOOK message.
I wonder if I should make a default message, like I did with a few other things? I could do that and make a BETA version available. That would tell us that something is physically resetting the EEPROM contents.
Let me know how the above test goes.
Ok, try this and let me know if it works:
Type: AT*OFFHOOK?
Look at the response. If it is blank set it to something, ie:
AT*OFFHOOK=this is a test
Then check to make sure it is there by typing AT*OFFHOOK? again.
Now type:
AT&W
This store the setting.
Now type:
ATZ
This recalls the settings.
Now, check to see if the OFFHOOK string is still there by typing:
AT*OFFHOOK?
If the string is there, then the v6.01 firmware update is working. At that point, only AT&F could be responsible for resetting the contents of the OFFHOOK message.
I wonder if I should make a default message, like I did with a few other things? I could do that and make a BETA version available. That would tell us that something is physically resetting the EEPROM contents.
Let me know how the above test goes.