I have four DT800s logging data on 15 minute intervals at a remote location. One logger has been locking up intermittently (stops logging, does not communicate).

Only way to reestablish communications has been by doing a hardware singlepush reset. After reset, the job is still okay but not running and data logging has stopped sometime previously. The event log shows nothing.

Other three loggers have been working fine. Only significant difference in programs is that this logger has a frequency channel scanned on a 15 second basis: P12=200 ' scan 200ms RB15S 11-F(W,GL100MV,Y23,=71CV) ' Scan wind speed and save 11#R(W,#,2W,S24,=72CV) ' Scan wind direction and save Is it possible for software to cause this crash?

I would like to eliminate any possibility before swapping out the logger.

Regards,
Leo

Good morning Leo,

Could you please drop me an email? I think this might take some time to identify exactly what is happening. We need to look at your communications, how the system is powered, firmware versions, complete program etc. My email is support@datataker.com.au

The first thing to check is the flow control. Please make sure you are using software flow control. Also if you program is written to flash memory then the program will automatically run if the logger resets.

Looking forward to your email.

Cheers,
Roger

Would be interested to hear what was the problem and how solved. Just to learn something. Having sort of similar problem now and then.

Good morning fredflinstone,

We have added in a whole new set of diagnostic features in the DT80 and DT800 loggers. If the logger crashes it creates a error log which our embedded systems engineers can use to help diagnose the problem.

If you logger does crash and reset then please send to us;

1. A copy of your dataTaker program.
2. A copy of the event log.
3. A copy of the error log.

I would recommend you use DeTransfer to recover the error and event logs. the commands to use are UEVTLOG to unload the event log and UERRLOG to unload the error log.

This will greatly assist us in improving the dataTakers loggers and give you a better product.

Cheers,
Roger

I had this problem with several DT800's in the field. The solution was indeed to take care of software flow control. The problem was that the RS232 buffer exceeded its limit causing the logger to crash.

But if you ask me it should be able to work with hardware flow control too. Why it doesn't still bothers me?

Sorry but i can't find the UERRLOG in the manual. If i type it in nothing happens. So how can i get the errorlog?

And what does the following line in the eventlog mean?
DEBUG ,2007/01/12,10:32:52,0.629760,"ENOTCONN"

Bye Flo

Good afternoon Flo,

What version of firmware is your DT800 running? You might have an earlier version of firmware that may not have the event log or there might not have been an error log created.

The current DT800 firmware is 4.10.0001.

Cheers,
Roger

Hi Roger,

We use the following:
dataTaker 800 Version 4.08.0001 Flash 2004/12/16 10:34:54

And I got the eventlog but there was nothing special at the time it crashed. It crashed at 2007/01/12 at approximately 15:20. Afterwards it didn't log data and we can't login. So we make a reset at 2007/01/13.

EVENT,2007/01/08,08:49:04,0.941162,"Reset 4.08.0001 COMMAND (10)"
EVENT,2007/01/09,13:58:10,0.941284,"Reset 4.08.0001 COMMAND (10)"
DEBUG,2007/01/12,10:32:52,0.629760,"ENOTCONN"
EVENT,2007/01/12,10:34:59,0.941284,"Reset 4.08.0001 COMMAND (10)"
EVENT ,2007/01/13,12:08:47,0.941650,"Reset 4.08.0001 POWERUP/BUTTON (2)"

Bye Flo

Good morning Flo,

It is possible one of the logger process thread was stopped thus crash the logger.
Can you check if removing that wind parameters scan can stop this crash?

Please send this issue to support@datataker.com.au

Cheers,
Roger