The message above occurs sometimes when some CR1000 had restarted.
This CR1000 be connect to loggernet by call back.
Sometimes, with no razon, it restart and the only information tha I had is this message.
See below the Watchdoginfo.
2 3 2012 11:12:22
Watchdog timer PAKBUS COMMS triggered.
Slot Task Name Pri Status
12 SocketTask 200 waiting at mailbox 23 [Timeout=33], PC-> 13E88C
10 PeriphBusEvent 200 waiting at mailbox 22, PC-> 0D75D2
6 CommTask 200 waiting at mailbox 15, PC-> 05E6F0
5 CommTask 200 waiting at mailbox 14 [Timeout=176242], PC-> 05E6F0
3 Terminal 200 waiting at mailbox 11, PC-> 076B96
8 PakBusServer 200 waiting at mailbox 2, PC-> 05C964
11 Display 200 waiting for event 45 set, PC-> 0DC79E
9 VoiceTask 200 waiting for event 43 set, PC-> 074D96
16 SlowProcX 200 waiting for event 26 set, PC-> 08B458
15 RunDld 220 waiting for event 16 set [Timeout=125], PC-> 08BC00
19 SlowProcX 216 waiting for event 9 set, PC-> 08C166
18 SlowProcX 217 waiting for event 8 set, PC-> 08C166
17 SlowProcX 218 waiting for event 7 set, PC-> 08C166
14 BkgndSlowMeas 218 waiting for event 6 set, PC-> 09437C
7 NicheStack 200 in run queue, PC(qproc)-> 110798 , PC-> 000004
4 PakBusMain 200 in run queue, PC(qproc)-> 10F624 , PC-> A20000
1 Watchdog 220 => in run queue, PC(qproc)-> 0307DC
ChkMem results:
COLOR0: fail
fragments: 0, total_free: 0
largest free: 0, alloc blocks: 759
COLOR2: ok
fragments: 1, total_free: 6796
largest free: 6796, alloc blocks: 6
Slot 1, Stack base 0037BFD4, pointer 0037C782, See current sp Min 884
Slot 3, Stack base 0036A320, pointer 0036A8CA, remaining 1450, Min 1144
Slot 4, Stack base 00369B18, pointer 0036A21A, remaining 1794, Min 880
Slot 5, Stack base 00369310, pointer 00369A7A, remaining 1898, Min 1504
Slot 6, Stack base 00368B08, pointer 00369272, remaining 1898, Min 1712
Slot 7, Stack base 00367D90, pointer 00368932, remaining 2978, Min 1380
Slot 8, Stack base 00367188, pointer 00367D26, remaining 2974, Min 2284
Slot 9, Stack base 00366580, pointer 00367136, remaining 2998, Min 2996
Slot 10, Stack base 00365978, pointer 00366516, remaining 2974, Min 2972
Slot 11, Stack base 00364D70, pointer 003658D2, remaining 2914, Min 2880
Slot 12, Stack base 00346550, pointer 003470F2, remaining 2978, Min 1696
Slot 13, Stack base 0031CF48, pointer 0031EAEA, remaining 7074, Min 6024
Slot 14, Stack base 00316934, pointer 00316CEE, remaining 954, Min 640
Slot 15, Stack base 00315D2C, pointer 00316876, remaining 2890, Min 2052
Resources owned: 24
Slot 16, Stack base 00315924, pointer 00315C7E, remaining 858, Min 572
Slot 17, Stack base 00314D1C, pointer 00315882, remaining 2918, Min 2304
Slot 18, Stack base 00343BD4, pointer 0034473A, remaining 2918, Min 1772
Slot 19, Stack base 00342FCC, pointer 00343B32, remaining 2918, Min 824
Comms Mem: [0]= 14251405, [1]= 309, [2]= 3249.
fileopen_write
Anybody had got this before?
Thank you, in advance.
Make sure you have the most recent operating system in the datalogger. There have been some watchdog errors fixed in the last couple of OSes.
Dana W.
Dana,
We are use the last OS Version. When we was using the OS 20 we getting "Warning: Watchdog timer Out of Memory (IP) triggered." sometimes.
After the OS 24 we getting "Warning: Watchdog timer PAKBUS COMMS triggered."
Please see below the Datalogger information(Partial):
Datalogger Information
Reported Station Name: 39783
OS Version: CR1000.Std.24
OS Date: 111219
OS Signature: 12288
PakBus Address: 101
Security Settings(1): 0
Security Settings(2): 0
Security Settings(3): 0
Panel Temperature: 24,28 °C
Memory: 4194304 bytes
Watchdog Errors: 1 - Reset this value. If errors continue, contact Campbell Scientific.
Program Information Current Program: CPU:MSTK_INCOMEX_Enc.CR1
Start Time: 7/3/2012 20:04:56
Run Signature: 55349
Program Signature: 11432
Compile Results for Last Program Sent: Warning: Watchdog timer PAKBUS COMMS triggered.
CPU:MSTK_INCOMEX_Enc.CR1 -- Compiled in SequentialMode.
Can you please confirm if that watchdoginfo file was when using OS24 and also confirm if you are using TCP/IP communications.
* Last updated by: aps on 3/8/2012 @ 7:16 AM *
Dear Dana,
Please see below the contents the watchdoginfo.txt contents:
7 3 2012 20:04:54
Watchdog timer PAKBUS COMMS triggered.
Slot Task Name Pri Status
12 SocketTask 200 waiting at mailbox 23 [Timeout=33], PC-> 13E88C
10 PeriphBusEvent 200 waiting at mailbox 22, PC-> 0D75D2
6 CommTask 200 waiting at mailbox 15, PC-> 05E6F0
5 CommTask 200 waiting at mailbox 14 [Timeout=185205], PC-> 05E6F0
3 Terminal 200 waiting at mailbox 11, PC-> 076B96
8 PakBusServer 200 waiting at mailbox 2, PC-> 05C964
11 Display 200 waiting for event 45 set, PC-> 0DC79E
9 VoiceTask 200 waiting for event 43 set, PC-> 074D96
16 SlowProcX 200 waiting for event 26 set, PC-> 08B458
15 RunDld 220 waiting for event 16 set, PC-> 08BC00
7 NicheStack 200 waiting for event 13 set, PC-> 13F480
19 SlowProcX 216 waiting for event 9 set, PC-> 08C166
18 SlowProcX 217 waiting for event 8 set, PC-> 08C166
17 SlowProcX 218 waiting for event 7 set, PC-> 08C166
14 BkgndSlowMeas 218 waiting for event 6 set, PC-> 09437C
4 PakBusMain 200 in run queue, PC(qproc)-> 10F624 , PC-> B70000
1 Watchdog 220 => in run queue, PC(qproc)-> 0307DC
ChkMem results:
COLOR0: fail
fragments: 0, total_free: 0
largest free: 0, alloc blocks: 759
COLOR2: ok
fragments: 1, total_free: 6796
largest free: 6796, alloc blocks: 6
Slot 1, Stack base 0037BFD4, pointer 0037C3B4, See current sp Min 944
Slot 3, Stack base 0036A320, pointer 0036A8CA, remaining 1450, Min 1112
Slot 4, Stack base 00369B18, pointer 0036A17A, remaining 1634, Min 840
Slot 5, Stack base 00369310, pointer 00369A7A, remaining 1898, Min 1492
Slot 6, Stack base 00368B08, pointer 00369272, remaining 1898, Min 1736
Slot 7, Stack base 00367D90, pointer 00368932, remaining 2978, Min 1420
Slot 8, Stack base 00367188, pointer 00367D26, remaining 2974, Min 2312
Slot 9, Stack base 00366580, pointer 00367136, remaining 2998, Min 2996
Slot 10, Stack base 00365978, pointer 00366516, remaining 2974, Min 2972
Slot 11, Stack base 00364D70, pointer 003658D2, remaining 2914, Min 2880
Slot 12, Stack base 00346550, pointer 003470F2, remaining 2978, Min 2692
Slot 13, Stack base 0031CF48, pointer 0031EAEA, remaining 7074, Min 5976
Slot 14, Stack base 00316934, pointer 00316CEE, remaining 954, Min 612
Slot 15, Stack base 00315D2C, pointer 00316876, remaining 2890, Min 2096
Resources owned: 24
Slot 16, Stack base 00315924, pointer 00315C7E, remaining 858, Min 532
Slot 17, Stack base 00314D1C, pointer 00315882, remaining 2918, Min 2160
Slot 18, Stack base 00343BD4, pointer 0034473A, remaining 2918, Min 1772
Slot 19, Stack base 00342FCC, pointer 00343B32, remaining 2918, Min 732
Comms Mem: [0]= 13251504, [1]= 304, [2]= 2854.
my_fclose
If you would send me a copy of your program, we can work on looking into the issue in more detail. My email address is gtroberts at campbellsci dot com.
-Gary
Hi everyone,
I have the some problem.
Here is the status report.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Status Summary
2012/6/18 9:18:36
Datalogger Information
Reported Station Name: 6708
OS Version: CR3000.Std.24
OS Date: 111219
OS Signature: 56518
PakBus Address: 1
Security Settings(1): 0
Security Settings(2): 0
Security Settings(3): 0
Panel Temperature: 28.62 °C
Memory: 4194304 bytes
Watchdog Errors: 4 - Reset this value. If errors continue, contact Campbell Scientific.
Program Information
Current Program: CPU:Opec_basic_v3_0.cr3
Start Time: 2012/6/17 19:21:22
Run Signature: 47411
Program Signature: 40457
Compile Results for Last Program Sent: Warning: Watchdog timer PAKBUS COMMS triggered.
CPU:Opec_basic_v3_0.cr3 -- Compiled in PipelineMode.
Program Errors
Skipped Scans: 0
Skipped Slow Scans: 0
Skipped System Scans: 0
Skipped Records in delay_3d: 0
Skipped Records in delay_3d_2: 0
Skipped Records in comp_cov_3d: 0
Skipped Records in comp_cov_3d_2: 0
Skipped Records in delay_cs: 0
Skipped Records in delay_cs_2: 0
Skipped Records in comp_cov_cs: 0
Skipped Records in comp_cov_cs_2: 0
Skipped Records in flux: 0
Skipped Records in ts_data: 0
Variable Out of Bounds: 0
Battery Information
Battery Voltage: 13.75
Lithium Battery: 3.52
Number of times voltage has dropped below 12V: 0
Number of times voltage has dropped below 5V: 0
Card Information
Card Status: Card OK.
Bytes Free: 57344.00 bytes
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
FYI,TCP/IP communications is uesed.
The Campbell suport answered me, the solution is a firmware upgrade.
I have asked them but I'm without answers since March.
I'm still with the trouble.
There is another operating OS due out within a few days (I hope). That does fix one issue that can cause the above problem which can sometimes happen when a TCP/IP packet is lost during normal Pakbus communications with the logger. Please monitor the website for the new update or contact your normal support team who can send you a copy as soon as the firmware has finished testing.
Hi aps,
you mean cr3000 OS 25?
Yes I do, but it is not available yet I am afraid - it is still in final testing.
Has there been any progress with this? I've just encountered this error for the first time today. I have two CR1000s connected via Pakbus where the logger being interrogated has TCP/IP communications enabled with callback enabled from our Loggernet server. Both loggers are running the most recent OS.
This issue has been fixed in OS 25. It should be available for download from https://www.campbellsci.com/downloads any day now.
-Gary
Can you give a brief description of what is causing this? I'd assumed it was the logger trying to handle TCP/IP connections whilst receiving Pakbus requests from another logger. But even with the second, interrogating logger unplugged, the TCP/IP logger still displayed this error. I've now disabled the port (COM1) and there are therefore no beacons being sent and I'm hoping the problem has been resolved. The thing is, I have lots of other loggers with TCP/IP enabled and a COM open with 60 second beacons and never had this problem until now.
The operating systems are on the website now including the revision history.
We are guessing your issue will be caused by this bug/fix that is in the history:
"Changed PakBus Comms watchdog timeout from 30 seconds to 10 minutes so that an inadvertent watchdog does not occur while a valid process is active. Addresses triggering of PAKBUS COMMS watchdog timer."
I believe that timeout has been set at that level for somewhile but has only been triggered in this way in recent times as the logger has been loaded up with more complicated tasks, e.g. advanced TCP/IP functions. In the last couple of operating systems some additional tasks (e.g. file and email transfer, tablefile operations),have been split off as background tasks too which means the levels of interaction of different processes has become more complicated so non-measurement tasks are more likely to get held up.
If possible please try the latest operating system to confirm this fixes you problem.
OS 25 is now on the downloads page of our web site.
Dana