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.

Error Codes CR10X-PB error code 73


MikeW Dec 9, 2009 09:19 PM

Has anyone encountered this error? It's not on the list.....I have a site that was working fine (cold though..-30C) and I have been having bad connection rates and I noticed I had holes in the table (hourly,15min) after what I thought was a Telco/Raven issue. I had about 6 hours of holes with no lapse in rcd #'s. So I guess it wasn't the telco after all but an issue with connectivity with the cell and logger....logger locked...anyways, I have been collecting sucessfully for 3 hours without a problem......don't know if I should resend program..anyways, if someone has seen this error code, please respond..thks Mike


Dana Dec 9, 2009 09:41 PM

Hello Mike,

Error code 73 means there are skipped records in data table #3 (as you figured out). [7N = skipped record in table N.]

If you have a way to get into "terminal mode" (terminal emulation in LoggerNet for instance) or have a keyboard display, check the datalogger's *B mode and advanced to location no. 04: This is number of watchdog errors in the datalogger, which could indicate a problem. Also, *B 05: is the number of table overruns. If this value has some non-zero number in it(particularly if it continues to increment), I would look at increasing the scan interval so that it is large enough to accommodate all sensor measurements & processing.

Dana W.


MikeW Dec 9, 2009 09:54 PM

Thanks Dana for the quick reply..

its a remote site...and did I mention its -30C...(haha) This site has been operational for a couple of yrs w/no prob...no overuns have happened.....we've had a drastic temp change and maybe moisture is an issue here....its like the plug was pulled on the power for six hours and turned back on....except when that happens I can tell by batmins, flags resetting,....blah blah blah...

I have had moisture issues in the past and this wonky circumstance fits into the 10x with the PB O/S ......I'm just wondering (now that we are 3 hours into stability with comms and data) if a program reload would eliminate the poss of a reoccurrance( if it would re-occur?) or for sure fix by local, onsite O/S resend? Anyways thanks for reading....onsite in -30C is no fun.....thks Mike


Dana Dec 9, 2009 10:24 PM

Are you powered by a solar panel and lead acid battery? If so, I would suspect the battery... but that's just my swag. In *B :09 you can check the low 12 V counter to see if power has dropped below what the datalogger needs for operation (above 9.6V).

It was -3 F/-20 C here last night. Welcome Winter!

Dana

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