Dear All,
In our current Beta version there are sometimes watchdog errors occuring. The straingh thing is, that it sometimes runs without and sometimes with watchdog errors. I am using the Email send instruction. Sometimes during the execution the datalogger is restarting the program.
I am using the instruction without any problems and in the same way with same code in our current version of the program code... There was TCPOpen() added in the beta and some smaller changes.
On one of our test- loggers I found the following file on the CPU:
Slot Task Name Pri Status
12 PeriphBusEvent 200 waiting at mailbox 22, PC-> 000006
7 CommTask 200 waiting at mailbox 15, PC-> 17371B
6 CommTask 200 waiting at mailbox 14 [Timeout=182032], PC-> 17371A
4 Terminal 200 waiting at mailbox 11, PC-> AA55AA
16 SlowMeas 253 waiting at mailbox 6 [Timeout=191], PC-> AA55AA
9 PakBusServer 200 waiting at mailbox 2, PC-> 000005
5 SocketTask 200 waiting for resource 34, owner=8, PC-> 000FA0
14 SocketTask 200 waiting for resource 34, owner=8, PC-> 5D3E18
10 VoiceTask 200 waiting for event 43 set, PC-> 07BD46
18 SlowProcX 200 waiting for event 27 set, PC-> ACEA21
17 SlowProcX 200 waiting for event 26 set, PC-> 2CD2BF
2 CR800LED 200 waiting for event 0 set, PC-> 0BE002
13 Display 220 in suspend queue <SUSPENDED>, PC-> 0F40F4
11 RunDld 200 in run queue, PC-> A00022
19 SlowProcX 200 in run queue, PC-> 00005C
8 NicheStack 200 in run queue, PC-> 11F9D0
1 Watchdog 220 => in run queue
Could you please help me to find out why that happens? The dataloggers are running OS18/OS19 or OS09/OS10 CR800Series
best regards,
Johannes
* Last updated by: JBecker on 4/12/2010 @ 3:26 AM *
I am told your TCP/IP stack has stuck. Can you tell us if this is running over a possibly unreliable TCP/IP connection, e.g. GPRS where the connection could have been lost and left the TCP/IP connection in limbo.
If so, we have had one report of a similar issue and will be addressing this shortly.
I will contact you by email when we have something to try.
Yes, the connection is running via GPRS or via Ethernet with wireless modem connected. In both cases we can observe this from time to time. Sometimes regular everytime the instruction is called, sometimes not.
(Well, I would suspected the connection itself but what I find curiouse is that exactly the same code is running absolutly stable in another version of the program... )