Our full technical support staff does not monitor this forum. If you need assistance from a member of our staff, please submit your question from the Ask a Question page.

Log in or register to post/reply in the forum.

Landline modem reset string

artyb Jun 17, 2020 11:39 AM


I'm trying to figure out how to use the reset string for an unusual landline modem connected to a computer and loggernet. It's not in the modem list, and sometimes blacklists numbers that are dialled too frequently. There seems to be no way to disable or reset the blacklisting that I can find, and in anycase a modem reset is a good thing to do. The command needed is AT+T Erase, but the modem takes around 5 seconds to reboot and doesn't issue OK after doing so.

I've tried several combinations, but loggernet issues +++ and then ATH then tries the reset string again, I think because the reset command doesn't return OK.

Is there any way I can get this to work? Can ; or , be used to delay the issue of the AT commands? It seems not?

I'd wondered about AT+T Erase;;;;;;;;;;;;AT or similar so loggernet received the OK response from the final AT?

Is there another way?

I can't find much documentation about this, or forum questions.


JDavis Jun 17, 2020 03:44 PM

I believe what you are proposing may work. 

Use 'Generic' in Setup instead of 'PhoneBase'. That will give you complete control of the dial sequence and end script. Refer to the help from within Setup to look at Generic Modem Commands.

artyb Jun 17, 2020 06:51 PM


That's worked! I've been able to write a custom dial script which issues the reset, without checking for a response, waits while the modem reboots, then issues 'AT' and checks for 'OK' as a response. I've created the end script based on examples for Iridium modems and all seems to be working well. I haven't put the dialling in the Generic item though, but have moved my existing tree of a Phone Base and many PhoneRemote, PakbusPort and Loggers under it. It would have been a lot of work to change and a lot of work to migrate back if we change to a standard modem. So the modem should keep trying unreliable sites now.

Many thanks,

artyb Feb 9, 2021 11:44 AM

Actually that didn't work. I ended up with the 'Generic' configuration located on the same serial port as my 'Modem' and logger tree. With no dialling in either 'Generic' and the skeleton of a logger config but no 'Modem' works. The logger config makes LoggerNet run the 'Generic' reset script according to the schedule, but as there is no dialling and therefore no connection it fails quickly and other real configs can use the com port.

Log in or register to post/reply in the forum.