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.

WatchDog Error: WatchDogInfo.TXT - IP Panic: Out of memp. (CR300)


DAriushop Feb 23, 2023 06:29 PM

I am getting a watchdog error and an error txt file that i cannot understand. I see an "Out of memp" at the top of the  text file but cannot desifer anything after that.

If anyone has any idea what any of these lines of text indicate let me know please!

Here is the entire text file:

CR3000.Std.32.03 23 8 2022 02:01:27
IP Panic: Out of memp.

Slot Task Name Pri Status
9 PeriphBusEvent 200 waiting at mailbox 22, PC-> 0CC8D2
13 CommTask 200 waiting at mailbox 16 [Timeout=3813], PC-> 11C8D2
6 CommTask 200 waiting at mailbox 15, PC-> 11C8BA
5 CommTask 200 waiting at mailbox 14, PC-> 11C8D2
3 Terminal 200 waiting at mailbox 11, PC-> 0FEC50
7 PakBusServer 200 waiting at mailbox 2, PC-> 10B80C
4 PakBusMain 200 waiting for resource 34, owner=11, PC-> 1845AC
8 VoiceTask 200 waiting for event 43 set, PC-> 11F5E6
16 SlowProcX 200 waiting for event 26 set, PC-> 0782BE
15 RunDld 220 waiting for event 16 set [Timeout=160], PC-> 078B02
12 IpServerTask 200 waiting for event 13 set, PC-> 17B586
18 SlowProcX 217 waiting for event 8 set, PC-> 07913C
17 SlowProcX 218 waiting for event 7 set, PC-> 07913C
14 BkgndSlowMeas 218 waiting for event 6 set, PC-> 085BC0
1 Watchdog 220 waiting for event 2 set, PC-> 06445A
10 Display 220 in suspend queue <SUSPENDED>, PC-> 0E22C4
11 IpTask 200 => in run queue, PC(qproc)-> 0029D1
ChkMem results:
COLOR0: ok
fragments: 17, total_free: 46680
largest free: 16392, alloc blocks: 2364
COLOR2: ok
fragments: 1, total_free: 4672
largest free: 4672, alloc blocks: 5
Slot 1, Stack base 005F8BD4, pointer 005F937E, remaining 1962, Min 1592
Slot 3, Stack base 005F4FC4, pointer 005F591A, remaining 2390, Min 2388
Slot 4, Stack base 005F47BC, pointer 005F4EE2, remaining 1830, Min 1144
Resources owned: 31
Slot 5, Stack base 005F3FB4, pointer 005F471A, remaining 1894, Min 1820
Slot 6, Stack base 005F37AC, pointer 005F3F12, remaining 1894, Min 1688
Slot 7, Stack base 005F2BA4, pointer 005F374A, remaining 2982, Min 1876
Slot 8, Stack base 005F1F9C, pointer 005F2B56, remaining 3002, Min 3000
Slot 9, Stack base 005F1794, pointer 005F1F32, remaining 1950, Min 1948
Slot 10, Stack base 005F0B8C, pointer 005F1712, remaining 2950, Min 2064
Slot 11, Stack base 005EFB74, pointer 005F05A6, See current sp Min 1216
Resources owned: 34
Slot 12, Stack base 005EEF6C, pointer 005EFB2E, remaining 3010, Min 3008
Slot 13, Stack base 005D7434, pointer 005D7B9A, remaining 1894, Min 1536
Slot 14, Stack base 005C07A4, pointer 005C0B5E, remaining 954, Min 552
Slot 15, Stack base 005BFB9C, pointer 005C069E, remaining 2818, Min 2096
Slot 16, Stack base 005BF794, pointer 005BFADA, remaining 838, Min 456
Slot 17, Stack base 005D3034, pointer 005D3B7E, remaining 2890, Min 1952
Slot 18, Stack base 005D242C, pointer 005D2F76, remaining 2890, Min 2260
CommsMemFree:
302
97(96),31(17),14(13),14(0),20(15),15(13),25(23),0(0),0(0)
fileopen_write
CS9 service 0: IP mem pools total free min
RAW_PCB 4 4 4
UDP_PCB 10 9 9
TCP_PCB 100 97 96
TCP_PCB_LISTEN 20 18 18
TCP_SEG 50 50 45
REASSDATA 5 5 5
FRAG_PBUF 15 15 15
ARP_QUEUE 30 30 28
ND6_QUEUE 20 20 20
IP6_REASSDATA 5 5 5
PBUF_REF/ROM 30 30 30
PBUF_POOL 32 31 17
MALLOC_24 20 14 13
MALLOC_100 15 14 0
MALLOC_270 20 20 15
MALLOC_532 15 15 13
MALLOC_1584 25 25 23
MALLOC_2220 15 0 0
MALLOC_18000 0 0 0


JDavis Feb 23, 2023 07:03 PM

The IP stack in the CR3000 ran out of buffer memory. The logger was overrun with network traffic.

It is confirmed with the values from CommsMemFree.

CommsMemFree:
302
97(96),31(17),14(13),14(0),20(15),15(13),25(23),0(0),0(0)

Notice the 14(0). A buffer pool that had 14 allocated dropped to a minimum of 0.

The Communication Allocation setting on the datalogger can be increased to avoid or at least delay the watchdog. The default is an allocation of 50. I recommend trying a setting of 100. IMPORTANT: collect all data before changing the setting.

Newer dataloggers like the CR1000X have faster processors, and newer IP stack versions. Those make them less susceptible to being overrun with network traffic.


DAriushop Feb 23, 2023 07:15 PM

Thanks for the fast response.

Would you mind guiding me through this proces?  

I have little datalogger knowledge, Where can i go to increase the allocation from 50 to 100?


JDavis Feb 23, 2023 08:15 PM

https://www.campbellsci.com/videos/connect-settings-editor

The setting is in advanced settings. You can access with the settings editor in PC400 or Loggernet. Device Configuration Utility also provides access to change the setting.


tsenghan May 22, 2023 11:29 PM

This post is under review.

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