We have a similar issue with the logger stopping to respond to be read through Modbus TCP/IP.
The logger works fine for 24-48 hours and then stops communicating over the Modbus TCPIP.
The setup we are using a DT85 connected to 16 CEM channels – a total of 400 HV I/O (we are reading 4-20mA pressures transmitters over a 250Ohm resistor).
The DT85 is connected via a freewave radio and a DCS system reads the CV register of the DT85 every 5s. Everything works fine but after 24-48hrs the DCS losses connection to the DT85.
Product DT85-3 SN: 105590 / Firmware: 9.18.6291 – self diagnostic all pass
Event log shows:
EVENT ,2018/08/21,11:36:36,0.279174,"Beginning entry of job "SWEC""
EVENT ,2018/08/21,11:37:30,0.913330,"Created job "SWEC""
EVENT ,2018/09/05,08:13:27,0.045654,"Peripheral prepared to hard reset"
EVENT ,2018/09/05,08:13:30,0.354858,"Reset 9.18.6291 EXCEPTION (c8610007)"
EVENT ,2018/09/05,08:13:30,0.695312,"Beginning entry of job "SWEC""
EVENT ,2018/09/05,08:13:37,0.752075,"Loaded job "SWEC""
EVENT ,2018/09/17,18:18:22,0.707397,"Peripheral prepared to hard reset"
EVENT ,2018/09/17,18:18:26,0.079467,"Reset 9.18.6291 EXCEPTION (c8610007)"
EVENT ,2018/09/17,18:18:26,0.460449,"Beginning entry of job "SWEC""
EVENT ,2018/09/17,18:18:33,0.665405,"Loaded job "SWEC""

Job SWEC has 4 schedules SWEC_A; SWEC_B; SWEC_C and SWEC_D
No issues with logging
A sample schedules looks like this: 5Minute schedule
Begin “SWEC”
S2=0,10000,1000,5000
RC"SWEC_F14A"("b:",ALARMS:OV:100KB:W60,DATA:OV:25MB)5M
901V("PI-1414B-105_P1~PSI",=300CV,LM,S2,A,GL30V)
901+V("PI-1414B-106_P1~PSI",=301CV,LM,S2,A,GL30V)
And another 100 lines like this and the next schedule
RD"SWEC_F14B"("b:",ALARMS:OV:100KB:W60,DATA:OV:25MB)5M
1301V("PI-1414B-205_P5~PSI",=400CV,LM,S2,A,GL30V)
1301+V("PI-1414B-206_P5~PSI",=401CV,LM,S2,A,GL30V)
….
LOGONA
LOGONB
LOGONC
LOGOND
END
Error report show the following error:
2018/09/17,18:18:26 An error occurred at ppp_interface.c:493
Task: timerThread
Current task : timerThread
Error location : 0002655C
Exception 200 at 0x000f1800

Hi austriacus,

The problem seems related to USB connection, but I believe this is just the surface after losing Ethernet connection. Since you manage to get connection using USB cable (regardless of the error) and retrieve service log, the logger is not in crash/ freeze position.

Thus it is possible to obtain a detailed information via network diagnostic. You can enable network diagnostic by sending P56=32 from command windows. Then wait until another glitch reappear. Collect PCAP files within DIAG folder and email it to me. And make sure to disable network diagnostic (P56=0) after the test otherwise PCAP files will keep growing and taken out the memory space.

For temporary solution:

• You can try to upgrade the logger firmware to 9.22
• Since the logger is not crashed, it is possible to introduce hard reset at certain interval. This will unblock communication port for MODBUS (assuming the port closing was not done properly).

Best regards,
Rudy Gunawan