Our full technical support staff does not monitor this forum. If you need assistance from a member of our staff, please submit your question from the Ask a Question page.


Log in or register to post/reply in the forum.

Table collection - Missing data


MAS Jul 19, 2010 08:48 AM

Hi everybody,
I wrote two programs one for CR200 and one for CR800. Both programs have some tables: 3 tables with 10, 15 and 60 minutes data interval (for CR200) and 2 tables with 10 and 60 minutes for the CR800.
CR200 collects data every 10 seconds from WXT520 with SDI12 communication protocol. CR800 works with 2 remote A/D converters connected on COM1 port (with RS232 to RS 485 converter at 9600 baud). A/D converters are called every 20 seconds.
Stations data are collected with LoggerNet every hour.
The problem comes looking collected data: in a random way, considering for example CR800, records with time mark 00:00:00 are sometimes missing. It looks like a problem on the data processing that happens at midnight.
Can anyone give me some help ? Thank you in advance.


Dana Jul 19, 2010 10:01 PM

Check the datalogger's status table (any easy way to do this is using LoggerNet's Station Status on the Connect window). Are you getting skipped records reported there?

Dana


MAS Jul 20, 2010 10:32 AM

Thank you,
I checked the status table of the CR800 and I can find the field "Skipped Record(1)","Skipped Record(2)" and "Skipped Record(3)". All these 3 fields are set to 4. Four records skipped for each table.
Which can be now the reason ?


Dana Jul 20, 2010 03:30 PM

A skipped record could be due to the clock being set, where the difference in the old time/new time causes a data output interval to be missed.

You will also get skipped records if you have a skipped scan, and that scan was supposed to output data. If you have skipped scans, you'll need to change the execution interval of your program.

Regards,

Dana


MAS Jul 20, 2010 04:41 PM

Thank you Dana,
values in fields "SkippedScan" and "SkippedSistemScans" are zero, so I believe I can exclude a problem on the the execution interval.
The allignemnt of the logger clock with the PC clock is made automatically whenever a deviation of more than 1 second is detected. Data are collected every hour.
I remove this check hoping that this can solve the problem.

Regards.
Mas

Log in or register to post/reply in the forum.