We've got a Dataker DT85 logger which scans data every 15s and logs the average of 4 readings every minute. The data is captured via DigiRails.

For quite sometime now, the logger keeps on crashing after a a few hours of operation. We've tried various settings and even had a replacement logger but even the replacement logger crashes after a while. Both the original and replacement loggers are running the latest 9.18 firmware.

After the constant crashing of the existing DT85, the replacement logger was tested on site, and the command line input was also tested. Remote access to logger was also confirmed from back at base, but after a few hours of operation, the remote connection stopped working, and the logger is now not responding. it has also stopped collecting data. The remote comms to site are still operational as we can still access our CCTV cameras and can see the logger is not collecting any data (no activity light). I can send the system log in a PM in order to help identify any issues.

These crashes are causing us significant delays and costs on a major project, any help is greatly appreciated.

Hi mpb,

Can you tell me about the communication between dataTaker and DigiRails?
If it is a MODBUS, does dataTaker write to DigiRails or DigiRails read into dataTaker?
How many parameters involved in the reading?

I believe there is an issue between read and write at the same time.
While RAM can handle it, it may eventually fail.
So you must trick the system to run into a sequence which will separate read and write action.

Best regards,
Rudy Gunawan

Hi Rudy,

I've replied to your PM. The comms between the DigiRails is via MODBUS. DigiRails are read by the DataTaker. There are approximately 42 DigiRails.

How can we separate the read/write sequence?

HI mpb,

You may separate read/ write sequence by using MODBUS write to DigiRail.
So it will be dataTaker which push the data.

Best regards,
Rudy Gunawan