Good morning!
We have a CR10 datalogger that was working normally until a few days ago but suddenly stopped. Now, when trying to connect using the 4.1 PC200W it appears messages like below, even doing everything exactly the same as before (when it worked). COM port and SC32A are ok and the same as before. Others CR10 do connect.
Failed to connect to CR10.
Unable to communicate to the datalogger.
Log error message:
Warning: 9:23:41.482 05/12/2012
Classic: CmdClockSet
Warning: 9:23:41.950 05/12/2012
Classic: CmdClockSet
Warning: 9:23:42.418 05/12/2012
Classic: CmdClockSet
Warning: 9:23:42.886 05/12/2012
Classic: CmdClockSet
Is there a problem with this datalogger? Is it something that need to be hardware repaired?
Well, just to add some information:
The only unusual thing is that the datalogger was programmed to a Execution Interval of 0.3125 seconds.
It did work well for 3 or 4 hours. We downloaded the data and it was fine.
Then we left it logging for 3 days. In the fourth day, we tried to connect to the computer and the connection problem started.
When PC200W attempts to connect to a datalogger, one of the first things it does is try to get the datalogger's clock. The message means that the clock check failed, but there's really no additional information in the errors you've posted above.
I would start with checking the power supply to the datalogger. Do you have a keyboard display? If so, can you communicate with the datalogger using it? Check the condition of the cables, etc.
Dana W.
Hi Dana, thanks for your attention on this.
Power supply is ok and cables are good too.
We connected a Keyboard display and it appears “HELLO” and then “E08 00”. Nothing else happens. No response to keyboard entries.
Looking at the manual, in Table 3.10-1. Error Codes, it says Code “08”, Type “Run Time”, Description “CR10X reset by watchdog timer”.
Is there anything I could try to fix ?
Thanks,
* Last updated by: Jebam on 12/7/2012 @ 5:17 AM *
Does the E08 happen after you cycle the power too. If it does it probably means either the logger has a hardware fault or its operating system is corrupt.
You could try reloading the operating system by downloading the Device Configuration utility and the latest operating system from the Support section of this website and following the instructions in the utility.
Thanks, APS.
Yes, it does.
Now I am trying to reload the OS. I downloaded and installed Device Config Utility but I can't find the .OBJ.
I downloaded the "CR10X OS 1.23" in https://www.campbellsci.com/download?dl=dlf&au=0&dlid=36
but it comes as .exe file which cannot be installed (Failed to ensure dir exists). Does it only work if Loggernet is installed? I Tryied to download LoggerNet Trial but "File not found" at the website.
Thanks.
That seems to be a flaw in the installation program that simply copies the obj to disk. I will get the issue of the Loggernet Trial investigated.
Meanwhile if you email me directly I will send you the CR10X operating system back. Please also let me know the serial number of the datalogger, so I can check if it was subject to any recalls.
My email (a little cryptically) is:
andrew DOT sandford AT campbellsci.co.uk
Hi
I had the same trouble, I check the battery and the connection but it doesn't work
I'm using a RS 232 and de P400 software
Hi guys!
We solved the problem after we replaced the internal Li battery (coin shaped).
After we did that, everything became normal again.
Thanks,
Eduardo