Have some serious problems with CR1000 DL, which run on V21 Operating System. The have been operating for quite a long time. They are configured in a way that they log onto an Loggernet server and leave data there.
Suddenly 4 out of 6 systems went down and it was/is impossible to connect nor download data. The systems enter into compiling every 5 minutes and some strange black symbols appear on the screen or in the display.
What could that be? Does it sound familiar to anyone of you?
Battery voltage is fine by the way.
I investigated a little bit more.
The logger(s) recompile nearly every 5 minutes and return a watchdog error warning "Watchdog timer Ethernet triggered"
I just connected to one logger and in the Datalogger Status tab 11 watchdog errors are mentioned.
All loggers run on operation system V21. I am not sure if there is some known bug or if I have a problem with my program
Any help welcome
There is a WatchdogInfo.txt file created, which has the following content:
Watchdog timer Ethernet triggered.
Slot Task Name Pri Status
12 PeriphBusEvent 200 waiting at mailbox 22, PC-> 000006
7 CommTask 200 waiting at mailbox 15, PC-> 175A65
6 CommTask 200 waiting at mailbox 14 [Timeout=182007], PC-> 175A64
4 Terminal 200 waiting at mailbox 11, PC-> AA55AA
9 PakBusServer 200 waiting at mailbox 2, PC-> 000006
5 PakBusMain 200 waiting for resource 34, owner=8, PC-> 000FA0
10 VoiceTask 200 waiting for event 43 set, PC-> 0758CE
18 SlowProcX 200 waiting for event 27 set, PC-> AF1A44
17 SlowProcX 200 waiting for event 26 set, PC-> 2F67C5
11 RunDld 200 waiting for event 16 set [Timeout=159], PC-> 08BF3A
21 SlowProcX 200 waiting for event 10 set, PC-> 08C5D0
16 SlowMeas 253 waiting for event 1 set, PC-> 0914D6
2 CR800LED 200 waiting for event 0 set, PC-> 0BB97C
13 Display 200 in run queue, PC-> 5C000E
19 SlowProcX 200 in run queue, PC-> 210034
8 NicheStack 200 in run queue, PC-> 1198C2
14 SocketTask 200 in run queue, PC-> 1604DC
20 SlowProcX 200 in run queue, PC-> 119330
1 Watchdog 220 => in run queue
There have been many issues/bugfixes dealing with Ethernet/IP/Pakbus that have been fixed in later releases of the operating system. If you update your logger to the latest operating system (OS 26) you should see these watchdogs go away.
The strange thing is that these loggers were running for quite a long time and suddenly stopped working. This behavior was seen only in one particular region, so I am wondering if the cause of that behavior can be a lightning strike or electromagnetic discharge?
Per chance, do these have serial or sdi-12 sensors on them?
Nope, no serial nor sdi-12 sensors. The serial port is occupied by the modem.
The measurement system is composed out of 5 anemometer, 1 wind vane, 1 temp, 1 pressure and 1 humidity sensor and the CR1000 of course.
The watchdog file above seems to indicate this is a CR850 not a CR1000 as it includes these lines:
2 CR800LED 200 waiting for event 0 set, PC-> 0BB97C
13 Display 200 in run queue, PC-> 5C000E
You also mention a display? IS that a CR1000KD, which would explain one of lines above.
If it is a CR800 or the logger thinks it is one that would explain the ethernet watchdogs (as there is no direct ethernet module for a CR800).
If it is a CR1000 I can only guess the logger memory is very badly corrupted. You can do a full memory reset remotely but if doing that you would need to be careful you do not wipe anything that will prevent further communication with the logger.