Support Forums
DT80 connectivity hungs

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.

Hi,

Just need some clarification

when connected on Ethernet you mentioned that you were getting an IP address but you are not able to establish the connection to the Logger ?

were you tried connecting to logger Web server ? can you connect on Command port 7700 (DeTransfer)

You mentioned both modem and logger seem to work fine when you visited the field . May be logger run out of web sockets (port 80) and you are unable to establish connection .

with remote connection, how are you doing it ? Are you using DDNS ?

can you please try pinging the host name and see if the logger is online when you fail to establish connection again?

also connect to Logger on command port (7700) and get the service ,you access the service log on command port by typing the following command from deTransfer

type b:\Events\service.log

or

type b:\Events\service.log from any other terminal window/telnet

there are no changes in DT to Modem communication in new firmware 9.16

Thanks
Regards
Lokesh

Hi, Just need some clarification when connected on Ethernet you mentioned that you were getting an IP address but you are not able to establish the connection to the Logger ? were you tried connecting to logger Web server ? can you connect on Command port 7700 (DeTransfer) You mentioned both modem and logger seem to work fine when you visited the field . May be logger run out of web sockets (port 80) and you are unable to establish connection . with remote connection, how are you doing it ? Are you using DDNS ? can you please try pinging the host name and see if the logger is online when you fail to establish connection again? also connect to Logger on command port (7700) and get the service ,you access the service log on command port by typing the following command from deTransfer type b:\\Events\\service.log or type b:\Events\service.log from any other terminal window/telnet there are no changes in DT to Modem communication in new firmware 9.16 Thanks Regards Lokesh

Hello Lokesh,

Thank you for answering. I will try to be more specific:
We have got 2 systems on field, first one installed 1 week ago (which is giving the issues) and the second one installed 2 days ago (this one seems to be ok so far). The events and testings have been as follows:

  1. First system correctly installed, upgraded to 9.16, configured and programmed on field.
  2. After 2 days of correct FTP data sending, the system suddenly hangs. All connection is lost.
  3. Come back to the field. What we found is the system correctly working (later on we checked all internal data) and the modem apparently online (strong signal) with none external error message.
  4. We tried to access through Ethernet (as usual) to check the log, but it was impossible. When the cable was connected, the DT80 was giving 0.0.0.0. Eth IP. So we had to make a hard reset. The system then correctly recovered and all communications were restored. The log file was showing ftp sending failed attempt but this is not causing the problem, as we had lost communication with the system time before the DT had tried to make the ftp sending.
  5. After one day, as I was checking some data through DEX interface, the system hung again.
  6. Same as point 3. But this time, we tried to use "stop comms" "start comms" panel functions before hard reset, but it was useless as the modem wasn't responding to the panel key functions. However, the other functions were working ok, as the dt. No error messages were recorded in the log file, as if everything had been ok.
  7. The system is connected to a VPN through a m2m card (Static ip, sim tested). So we thought adding a NETWORK_CHECK=PING to the server were it unloads the data(If it is impossible to reset the modem from the outside, maybe the DT could reset the modem internally if it detects a connection lost).
  8. Now the system has hung again. Seems even the dt is unable to restore communication with its modem internally.

Tests made so far when system connectivity hangs:

  1. HTTP connection through dEX(port 80) - Failed
  2. On field Eth connection - Failed (0.0.0.0 Eth IP, so unable to resolve LAN IP)
  3. FTP connection through ftp client (port 21) - Failed
  4. DeTransfer command port connection (port 7700) - Failed
  5. Ping check - Failed

It seems that when it hangs, it lost all kind of connectivity, like if the internal server process was lost; or maybe the communication between the DT and its modem is failing.
I would appreciate a prompt solution or temporal workaround, as our client is waiting. What I have thought as a bad solution meantime consist in adding a schedule which makes a hard reset each 24h, so that in case the connection hangs again, we wont have to move to the field at least.

Thank you in advance.

Hello Lokesh, Thank you for answering. I will try to be more specific: We have got 2 systems on field, first one installed 1 week ago (which is giving the issues) and the second one installed 2 days ago (this one seems to be ok so far). The events and testings have been as follows: 1. First system correctly installed, upgraded to 9.16, configured and programmed on field. 2. After 2 days of correct FTP data sending, the system suddenly hangs. All connection is lost. 3. Come back to the field. What we found is the system correctly working (later on we checked all internal data) and the modem apparently online (strong signal) with none external error message. 4. We tried to access through Ethernet (as usual) to check the log, but it was impossible. When the cable was connected, the DT80 was giving 0.0.0.0. Eth IP. So we had to make a hard reset. The system then correctly recovered and all communications were restored. The log file was showing ftp sending failed attempt but this is not causing the problem, as we had lost communication with the system time before the DT had tried to make the ftp sending. 5. After one day, as I was checking some data through DEX interface, the system hung again. 6. Same as point 3. But this time, we tried to use "stop comms" "start comms" panel functions before hard reset, but it was useless as the modem wasn't responding to the panel key functions. However, the other functions were working ok, as the dt. No error messages were recorded in the log file, as if everything had been ok. 7. The system is connected to a VPN through a m2m card (Static ip, sim tested). So we thought adding a NETWORK_CHECK=PING to the server were it unloads the data(If it is impossible to reset the modem from the outside, maybe the DT could reset the modem internally if it detects a connection lost). 8. Now the system has hung again. Seems even the dt is unable to restore communication with its modem internally. Tests made so far when system connectivity hangs: 1. HTTP connection through dEX(port 80) - Failed 2. On field Eth connection - Failed (0.0.0.0 Eth IP, so unable to resolve LAN IP) 3. FTP connection through ftp client (port 21) - Failed 4. DeTransfer command port connection (port 7700) - Failed 5. Ping check - Failed It seems that when it hangs, it lost all kind of connectivity, like if the internal server process was lost; or maybe the communication between the DT and its modem is failing. I would appreciate a prompt solution or temporal workaround, as our client is waiting. What I have thought as a bad solution meantime consist in adding a schedule which makes a hard reset each 24h, so that in case the connection hangs again, we wont have to move to the field at least. Thank you in advance.

UPDATE

We have come back today to reset the system on field. This time not only the modem was hung but the entire job. Besides, there was a "software excep" message showing on the LED. Modem was showing "data dropped" also. I have restored factory defaults and reinstalled last firmware, dont know if it will make any change. Any ideas?

Regards

UPDATE We have come back today to reset the system on field. This time not only the modem was hung but the entire job. Besides, there was a "software excep" message showing on the LED. Modem was showing "data dropped" also. I have restored factory defaults and reinstalled last firmware, dont know if it will make any change. Any ideas? Regards

Hi Contek,

Adding auto recycle in separate schedule may work but it just as workaround it won't solve your actual problem.
Software exception indicates another problem in your setting or program.

Could you send the service log from your logger to dataTaker tech support email?
We will take it from there.

Best regards,
Rudy Gunawan

Hi Contek, Adding auto recycle in separate schedule may work but it just as workaround it won't solve your actual problem. Software exception indicates another problem in your setting or program. Could you send the service log from your logger to dataTaker tech support email? We will take it from there. Best regards, Rudy Gunawan
67
4
3
live preview
enter atleast 10 characters
WARNING: You mentioned %MENTIONS%, but they cannot see this message and will not be notified
Saving...
Saved
With selected deselect posts show selected posts
All posts under this topic will be deleted ?
Pending draft ... Click to resume editing
Discard draft