Hi
I usually check my cr5000 through loggernet to make sure everything is recording properly. Recently there have been issues with the data freezing up. I connect to the logger and attempt to graph my data but all my variables are stuck on one value. It's as if the logger freezes on one value then stops recording any new data. Could this be an issue with the program I am loading on to the logger or an issue with the logger itself?
I am new to using this equipment so this may be an easy fix that I am unaware of. Thanks for any advice.
There could be several things causing this.
It would be nice if you could post your program.
Do you have the FillStop command in your DataTable definition ?
Is the record number in the Public table still incrementing ?
When you look at the Status Summary (Connect Screen | Station Status button) does it show any errors, watchdogs, skipped scans or skipped records ?
I see this occassionally when the logger has a program that is taking up most of the resources. Communication to the computer is a lower priority so I find that cycling the Stop/Start button on the monitor window usually gets it started.
Two things to look at from the monitor window are the public table's logger time stamp and record number. Both of those should increment each time the program starts a new scan.
If those are incrementing you know the progam is running and the communication is working insofar as to be able to transfer data.
If you are monitoring other tables and they are not updating it is most likely that the tables are not actually being written to. In my case it is most often that a condition needing to cause table writes is not true. It can be that the condition is not true or that the progam logic causes the table statement to be bypassed.
Is there a way I can monitor the public table's time stamp and record number through loggernet? The tower that has this logger is four hour away so accessibility is limited.
I am not sure there is a problem with the program. This program has been in use for close to a year and problems are just now arising.
Thanks for the suggestions!
When you say you are connecting through LoggerNet, is that when you are actually with the logger and connected with a cable direct to your PC?
Do you have other connection options such as cell phone or wireless modems, or even a ground line telephone. If you have any of those options available, then yes, you can use LoggerNet to monitor the public tables.
If the system has been in place for some time but just now giving problems, check the battery voltage. If you are not making that measurement in the program, you can get battery information from the status table.
It will help if you provide a description of your logger set up including communication hardware, power supply hardware (battery with solar recharge for example).
Did you ever get a solution to this? I am having the same problem recently. I am running a remote EC system using an RF450 radio and a CR5000. The CR5000 freezes up unexpectedly without warning. This has happened a couple times with a program that I've been using for a while. One of the things I've noticed is that failure occurs after the total number of samples exceeds what it is supposed to be (i.e. >18000 running at 10 Hz at half hourly averages). I checked the status table and the slowsequence scan is stuck at the timestep where the failure occured. Would really appreciate any help.
How are you connecting the RF450 to the CR5000 ? Is it via the RS-232 port or via the CS I/O port ?
If you are using CS I/O then there are some limitations that are different on the CR5000 than on a CR1000 or CR3000:
* When using the ME channel of CS I/O, you are limited to the following baud rates: 9600, 19,200, 38,400 and 57,400. The rate of 115,200 will *not* work properly.
* You can use the ME channel or the SDC7 channel. (SDC8 is not supported).
Also, are you using OS Std 6 or OS Std 7 ? I recommend you update to OS 7 if possible. CS I/O doesn't
work properly with the RF450 in OS versions before Std 6.
Our CR5000 freezed up 3 times in the last month. Last time there were 2 skipped scans, and all other checks were OK. When checking with LogerNet remotely, the time is changing when pressing Start/stop, but the RecNum stays the same, evenif a new half hours has begun. No new records are written to the datatables.
The datalogger program is running for ages with small modifications. Last was in March, but some sensors were removed.
The OS is STD 7.
What should I check in the program?
Are you using FillStop on your final storage table ?
Does the RecNum increment for the Public table ?
Do you have a trigger or conditional that causes your table to store data only under certain conditions ?
What kind of sensors were removed ? Is the program still measuring those sensors and reporting NAN ?
How is the internal battery doing ? Could it be approaching end of life ? (i.e. check its voltage in Status).
It would also be nice if you could post the latest record in your Status table.
Hi!
Sorry for the short answer, I am on my way to the field. .;-) So I am not able to post the status table.
Final storage tables are used in ring mode. The rec num is not incrementing, only the time. The datatables are trigerred by iftime.
Gmp343 sensors were removed in December, and their measurement in March, the failure started later.
The lithium battery is in opetation since 2005... but its status value is -1.