Hello,
I am having serious issues with the DT80M modem. I have got 2 systems deployed on field, configured and programmed correctly. When we come back to the office (after installing on field), we track the systems through the interface. Everything goes ok, but suddenly the connection is lost. So we had to move to the field and check what happened. Surprisingly, both the modem and the internal job were apparently running ok. We tried to access the DT through the Ethernet (before doing hard reset) to check the log file but it was impossible, it wasn't working either. Then we tried to stop comms and start comms through the function buttons, but the modem didnt respond. As I said, the DT80M was working ok meanwhile. So, the only chance we had was doing manual hard reset. The system rebooted and the modem started to work correctly again.
After two days, it happened again, so we had to move again to the field to make a hard reset. This time, we decided to add the NETWORK_CHECK=PING command to the code, hoping that in case the system doesn't detect outside connectivity it would internally reset the modem. It has work once, as we have seen auth_error message in the log and the connection was recovered. But now, we have lost the connectivity again.
The issue seems to be on the modem-DT connection, as it might to get lost and there is no way to recover it unless you make a hard reset. All internal server listeners hung: HTTP server, Ethernet (it is giving Eth IP when cable connected), modem key functions...
I don't know if this is a problem since last update 9.16, but we need a solution as soon as possible. You have to understand that it is not serious to deploy a system on the field far away and lose total connectivity from time to time. We have got clients waiting and there is no time to lose.
Thank you.
Hello,
I am having serious issues with the DT80M modem. I have got 2 systems deployed on field, configured and programmed correctly. When we come back to the office (after installing on field), we track the systems through the interface. Everything goes ok, but suddenly the connection is lost. So we had to move to the field and check what happened. Surprisingly, both the modem and the internal job were apparently running ok. We tried to access the DT through the Ethernet (before doing hard reset) to check the log file but it was impossible, it wasn't working either. Then we tried to stop comms and start comms through the function buttons, but the modem didnt respond. As I said, the DT80M was working ok meanwhile. So, the only chance we had was doing manual hard reset. The system rebooted and the modem started to work correctly again.
After two days, it happened again, so we had to move again to the field to make a hard reset. This time, we decided to add the NETWORK_CHECK=PING command to the code, hoping that in case the system doesn't detect outside connectivity it would internally reset the modem. It has work once, as we have seen auth_error message in the log and the connection was recovered. But now, we have lost the connectivity again.
The issue seems to be on the modem-DT connection, as it might to get lost and there is no way to recover it unless you make a hard reset. All internal server listeners hung: HTTP server, Ethernet (it is giving Eth IP when cable connected), modem key functions...
I don't know if this is a problem since last update 9.16, but we need a solution as soon as possible. You have to understand that it is not serious to deploy a system on the field far away and lose total connectivity from time to time. We have got clients waiting and there is no time to lose.
Thank you.