Everyone,
I have a Cr1000 that is working 100%, but two days ago it stopped logging any data. Any help ?
Sincerely
James
Hi James,
Could be any number of reasons, can you give more specifics about the application, power supply, sensors, etc.
IslandMan
James,
What OS is running in the logger? What is the logger doing? Some of your previous posts related to ftp communications. Is the program still running, taking measurements? Just not storing data to the tables?
Janet
Please confirm if you are doing ftp transfers and also perhaps communicating with the logger at the same time via a Pakbus connection, via TCP/IP. I ask as we have been investigating a similar problem.
The more common causes though would be a low battery where the logger will stop scanning and storing data but still communicates. That is a function that is built in to try to preserve the battery.
We are keeping the logger busy. The RS232 port is connected to a GPRS modem for sending and receiving TEXT messages. The CSIO port is connected to PC that download the data every 10 minutes and then there is about 5 other PC's that is connected to it via an NL120 Network Interface. In the past we had no problems and then we connected the logger to the University's emergency power supply and in hindsite it is when the problems started !!!. It also restarted a few times and according to my experince the only time wehn a Cr1000 will restart is when the power is cut.
The OS is version 12.
In the past we had no problems and then we connected the logger to the University's emergency power supply and in hindsite it is when the problems started !!!
There are a few status values you can check in the datalogger. If you are using LoggerNet 3.4.1, Connect to the datalogger via the Connect window and go the the Datalogger menu | View Station Status. Any errors detected in datalogger status will be highlighted in red, including low battery errors and watchdog errors. (In LoggerNet 4.0, Station Status is a more prominent button at the top of the Window.)
If you are getting watchdog errors, one of the things I would check is grounding. Is that emergency supply an A/C supply? If so, improper grounding could cause all sorts of headaches with the datalogger.
Also, if there is anyway you can upgrade to the latest datalogger OS, I would. There have been quite a few changes since OS 12, including some related to RS232 communication. It never hurts to be running the latest OS (they can be downloaded free of charge from our web site).
Regards, Dana
Dana,
Thanks. Will do.
Sincerely, James
