We have an NL115 connected to one of our CR1000's, and I lose communication with it every week or so. It still responds to pings, but I cannot connect to it, even directly from a laptop through Connect or Device Config. As soon as I toggle the power, everything is fine again. However, this is a problem since it is at a remote location.
The CR1000 appears to still be functioning fine while the NL115 is not. Some values read from the keyboard that may be of use are:
No Watchdog errors
StartUpCode = 1
ProgErrors = 0
MemoryFree = 20888
CommsFree(1) = 251505
CommsFree(2) = 307
CommsFree(3) = 3260
Card Status OK
CardBytesFree = 24576
MeasureTime = 432400
ProcessTime = 163000
MaxSystemProcTime = 35774
Could this be a problem with the time difference between the datalogger and network time, that I have the PakBus port always open, or something else? Is there anything I can do to troubleshoot this when it happens again? -Thanks.
Matthew,
To help, make sure your logger is running the latest version of the datalogger operating system. We have fixed memory issues similar to this one. Also, you can create a basic diagnostics table in your logger that will store the information you have listed above. That would be very useful.
Some like
Public CommsMemoryFree(3)
DataTable (Diagnostics, 1, -1)
DataInterval(0, 1, Min, 10)
Sample(1, Status.MemoryFree, IEEE4)
Sample(3, CommsMemoryFree, IEEE4)
Sample(1, Status.SkippedScan, FP2)
Sample(1, Status.SkippedSystemScan, FP2)
Sample(1, Status.CompileResults, String)
Sample(1, Status.CardStatus, String)
Sample(1, Status.CardBytesFree, String)
Sample(1, Status.MeasureOps, FP2)
Sample(1, Status.MeasureTime, IEEE4)
Sample(1, Status.MaxProcTime, IEEE4)
Sample(1, Status.StartTime, String)
EndTable
And somewhere in the main part of the program:
CommsMemoryFree(1) = Status.CommsMemFree(1)
CommsMemoryFree(2) = Status.CommsMemFree(2)
CommsMemoryFree(3) = Status.CommsMemFree(3)
CallTable Diagnostics
That will help get us some diagnostic information as things are running.
Also, there might be an issue with the program. Feel free to pass it along to me at gtroberts -at- campbellsci.com.
-Gary
Hi Gary,
Thanks for the help. I am running the latest OS (v.27), but I will add your diagnostic code to the program and see if that gives any clues. -Thanks.
* Last updated by: MatthewBoyd on 5/22/2014 @ 6:42 AM *