Our DT85 inexplicably neglected to log 7 minutes of data on a minute schedule. The last successful data record logged before the data loss had a time stamp of 12:00(noon). I glanced through the service log to see if there was an error around the time of the data loss and I found this:

2014/09/24,12:01:24

An error occurred at buf.c:19
Task: HTTP 2

Current task : HTTP 2
Error location : 000264A0
Exception 200 at 0x000f18bc
SRR1=00009032 DSISR=00000809 DAR=00000000 BAR=00000000 MSTAT=00000080
LR=000eb76c CR=24000022 CTR=0000005d XER=20000000
R00:07 0000002a 0417dfc8 00140680 001397d3 0000000a 00000030 00000041 00000034
R08:15 00000036 00000000 041cfd7b f00d4321 00000000 040612a8 53535353 53535353
R16:23 53535353 53535353 53535353 53535353 53535353 53535353 53535353 53535353
R24:31 53535353 0417e93c 0406f188 04060000 00051720 04060000 04063b50 0417a890
Call stack: 000264a0 000f1fa8 00080a74 00079310 000ecc04 000ecb98 ffffffff ffffffff
ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff

Notice that the time stamp is for the minute after the last successful data record. There are several errors very similar to this in the service log going back to when the logger was put into service. Looking back at the data, these errors coincide with data loss every time. I've looked into the datataker literature, but I can't find anything that refers to this type of error. Any help would be appreciated. We need to try to preserve as much data as possible.

Thank you

Hi Mike,

That error indicates somewhere in your program caused software exception.
Software exception will definitely reset the logger, on some occasion it may stop the logging until the problem is fixed or the logger is being restarted.

Could you send me service log from that logger and your program detail?

Best regards,
Rudy Gunawan

Hi Rudy,

Thank you for taking the time to review our issue. I’ve attached a text file of the service log for your viewing. I removed all the usernames and passwords from the text file for security purposes, but it is complete. The program is included in the service log.

This problem results in just a few minutes of data being lost, so it could very well be resetting the datataker. The program is quite long and the employee who wrote it has since left the company. I’m still a novice working with datatakers so any insight would be very helpful. Thank you again for taking the time to help me with this issue.

Best regards,
Mike Varney

Hi Rudy,

Also, one other thing that may be unrelated. Just lately, we started getting this error, or something similar:

Modbus RX
INVALID RX MSG (calc CRC=fe05)
Modbus RX
INVALID RX MSG (calc CRC=f8a5)
Modbus RX
INVALID RX MSG (calc CRC=3d94)

This appears in the receive window of the command tab of the web interface. It seems to be a checksum error in the data coming from a modbus node. Is there a way to find out what piece of equipment we are getting this data from? Is the modbus address indicated by the string: “HOST: 02”?

Thanks again,
Mike Varney

Hi Michael,

There are several things I would like to discuss with you:

1. Reading error I saw errors when dataTaker tried to read Wind Speed parameters.

EVENT ,2014/09/29,01:01:02,0.130371,"E82 - Serial device data not available (8SDI12:AD0:R105)"
EVENT ,2014/09/29,01:02:01,0.661499,"E82 - Serial device data not available (8SDI12:AD0:R105)"
EVENT ,2014/09/29,01:03:01,0.669555,"E82 - Serial device data not available (8SDI12:AD0:R105)"

And it is related to schedule B:

'Data Recording Schedule---------------------------------------------------------
RB("B:",DATA:6H)1M
'1. Outdoor Reference Measurements'
8SDI12(R201,CM,=101CV,FF1,"TAO~degF") 'TAO Temp, outdoor air'
8SDI12(R202,CM,=102CV,FF1,"RHO~%") 'RHO, outdoor air'
8SDI12(R105,CM,=103CV,W) 'WS Wind speed
103CV(FF1,"WS~mph")=103CV*(103CV>0)
8SDI12(R102,CM,=104CV,FF1,"WD~deg") 'WD Wind direction
8SDI12(R301,CM,=105CV,FF1,"RAIN~mm") 'RAIN Rainfall
8SDI12(R203,CM,=106CV,FF1,"OAP~hPa") 'OAP Barometric pressure
8+V(S1,=107CV,FF1,"INSOL~W/m^2") 'INSOL Incident Solar Radiation'
8SDI12(R304,CM,=108CV,FF1,"HAIL~hits/cm^2") 'HAIL

Is there something wrong with WS reading?
These repeatable error might cause the logger to reset.

1. Error log entry

2014/09/24,12:01:24

An error occurred at buf.c:19
Task: HTTP 2

Current task : HTTP 2
Error location : 000264A0
Exception 200 at 0x000f18bc
SRR1=00009032 DSISR=00000809 DAR=00000000 BAR=00000000 MSTAT=00000080
LR=000eb76c CR=24000022 CTR=0000005d XER=20000000
R00:07 0000002a 0417dfc8 00140680 001397d3 0000000a 00000030 00000041 00000034
R08:15 00000036 00000000 041cfd7b f00d4321 00000000 040612a8 53535353 53535353
R16:23 53535353 53535353 53535353 53535353 53535353 53535353 53535353 53535353
R24:31 53535353 0417e93c 0406f188 04060000 00051720 04060000 04063b50 0417a890
Call stack: 000264a0 000f1fa8 00080a74 00079310 000ecc04 000ecb98 ffffffff ffffffff
ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff

Unfortunately the link between error entry and event entry has been lost, so I can’t find any correlation from both entries.

The above error log entry showed HTTP request failed which might related to the internal web server failure.
This failure might possibly comes from the installed version of firmware (9.14).
That version has several bugs and has been withdrawn.
Could you downgrade your logger firmware to 9.10 version?
You may download 9.10 firmware files from our website: http://www.datataker.com/downloadsDT80.php

1. Programming insight. Yes, you have a long program but it is quite straight forward. It has 3 schedules: A, B and D.

Schedule A has 15 seconds interval which reading thermocouple type T, MODBUS sensor and Flow meter through counter.
Some flow figures require further calculation which you can see in the program.

Schedule B has 1 minute interval, which reading SDI12 sensors, voltage sensors, thermocouple type T and MODBUS sensor.
Some parameters are derived through calculation, therefore you find a massive formula in this schedule.

Schedule D has specific interval which run on specific time 1 AM, 7 AM, 1 PM and 7 PM.
It will send the measurement data to USB stick and your FTP server.

And about your unrelated question:
That is right, HOST:02 indicates the sensor address 2 for MODBUS.

Best regards,
Rudy Gunawan