Make modem restart automatically | Thales IoT Developer Community
November 14, 2016 - 12:03pm, 3701 views
Hello.
I'm building an app which is freezing after sometime running through bgs5t and not presenting any errors, despite of having debug **** activated. Is it possible to set a restart timing in which after some defined time the ****m restarts? This would probabily solve my problem. I tried to switch on the watchdog but it doesn't work since the program doesn't terminate. It only gets stuck.
Thanks
Hello,
The watchdog should work - if the kick() method is not called on time the module can be rebooted (depending on the setting made with AT^SCFG command). To use watchdog you have to enable it by AT^SCFG command - by default it is disabled.
In case of the terminal there is an additional hardware watchdog available - it is described in the hardware description for the terminal. It can be configured by i2c interface or on ASC0 with the dedicated baudrate. This watchdog has also a possibility to configure the periodic module restarting.
Regards,
Bartłomiej
Could you please provide more information about that second watchdog? How do I use it? How do I start it?
I'm not finding any information about it on the manuals.
Please let me know if you have such document: "Cinterion® Java Terminals Hardware Interface Description".
There's a chapter "Appendix A: (Hardware) Watchdog".
So, I entered WD=RST_REP,1800000,9 and the modem blinked twice, which confirms it was successful.
Still, I have been running my program for half an hour and still hasn't reset. Should insert some more command? Thanks.
When you change the watchdog configuration it is automatically disabled and you need to enable it again after the change.
I did, by inserting WD=ON,1,1
Still no changes. Should I activate it aswell via AtCommand?
No AT commands activation is needed. This watchdog is controlled by an external microcontroller.
There's one more parameter: MIN_START_TIME which default value is 30 minutes also and which guarantees that no module reset will be performed in the configured time after module starts. So the watchdog‘s reset timer that you have configured for 30 minutes will start after the MIN_START_TIME has expired. So in this case the module should reboot after an hour.
Regards,
Bartłomiej
I've did that. I have tried to shorten the time to 2 minutes for reset, making the time to the first reset 32 minutes. Yet, I saw no difference.
Here's the steps I took:
Connect via RS232 to the Modem on Terminal with 1200 baurate connection.
Sent
WD=RST_REP,1800000,9<CR>
Sent
WD=ON,1,1<CR>
Changed the comm connection for the one with the USB connection of the Modem. Runned my app. Nothing happened.
Have I done anything wrong?
Please try to reset to default values, then configure 5 minutes for each parameter and activate the watchdog like below:
WD= DFT_VAL,1,1
WD=MIN_START_TIME,300000,3
WD=RST_REP,300000,3
WD=ON,1,1
Worked :)
Thanks Bartlomiej!
Pages