Support Forums
DT85v3 Always shows Offline in DEX2

I have multiple DT85 devices (both 3 and 4). One of the series 3 units can be seen by DEX2 using either USB or ethernet connection but when I try and check connectivity it always says "Device Offline". It changes the light indicator on DEX2 from red to yellow.

I saw another post that said to check the console errors. Unfortunately, I do not have any console errors as DEX is seeing that there is a device but the device is sending back that it is offline.

Another suggestion was to try a non-network computer, same result as my office laptop.

Running Firmware 9.22 on the DT85 (updated via USB thumb drive after this problem started happening), DEX version 2.1.25.

I have multiple DT85 devices (both 3 and 4). One of the series 3 units can be seen by DEX2 using either USB or ethernet connection but when I try and check connectivity it always says "Device Offline". It changes the light indicator on DEX2 from red to yellow. I saw another post that said to check the console errors. Unfortunately, I do not have any console errors as DEX is seeing that there is a device but the device is sending back that it is offline. Another suggestion was to try a non-network computer, same result as my office laptop. Running Firmware 9.22 on the DT85 (updated via USB thumb drive after this problem started happening), DEX version 2.1.25.

As an update. I can get it to connect in safe mode (reset 3 times 3s apart). As soon as I reset it I have to go through that procedure again. to get it to reconnect.

As an update. I can get it to connect in safe mode (reset 3 times 3s apart). As soon as I reset it I have to go through that procedure again. to get it to reconnect.
edited Feb 10 at 6:49 pm

Hi averymechanix,

The yellow indicator will not trigger any error as it was not an error, the yellow means the dEX manage to detect the logger but the logger is yet to send back a response. The delay appeared most of the time because of a busy logger or you may have a fast sampling speed.

A logger can become busy because of waiting time, for example, if you set the program to read MODBUS sensor but there is no sensor connected. A default MODBUS timeout is 3 seconds, if you have more than 5 channels and try to read them in 15 seconds, the logger will be busy finishing the timeout.

Please check your program and send me a copy.

Best regards,
dataTaker Expert

Hi averymechanix, The yellow indicator will not trigger any error as it was not an error, the yellow means the dEX manage to detect the logger but the logger is yet to send back a response. The delay appeared most of the time because of a busy logger or you may have a fast sampling speed. A logger can become busy because of waiting time, for example, if you set the program to read MODBUS sensor but there is no sensor connected. A default MODBUS timeout is 3 seconds, if you have more than 5 channels and try to read them in 15 seconds, the logger will be busy finishing the timeout. Please check your program and send me a copy. Best regards, dataTaker Expert
edited Feb 28 at 5:02 am
41
2
2
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