We have a CR1000 (OS18) based instrument that has been working fine for over a month of deployment.
Operation of the logger is:
- Scan every 10 minutes
- Save to USR drive using TableFile every 12 hours
- Send same file via FTP over PPP connection
Recently the logger has stopped recording altogether although communications to it are fine. It seems the logger stops when the TableFile command is run. Restarting the program starts logging again, however at the 12hr mark the logging stops.
No errors are recorded in the station status summary. The latest file in the USR drive has no size information however. Removing the FTP part of the code still results in the error.
There is a high current draw operation that occurs immediately after the CallTable command, could this perhaps cause the error by putting noise on the 12V line? I'm testing for this now.
Any ideas?
There is a know issue with FP2 data in TableFiles. This is fixed in CR1000 OS19. An easy work around is to store data in IEEE4 format until you can upgrade the OS. CR1000 OS19 is not on our web site yet; so, you'll need to contact your favorite Applications Engineer to get a copy if you don't want to wait.
Let us know if you have other question.
Regards,
Janet
It is out in the field so the IEEE4 fix will do the trick for now. Thanks for the update.