Experimental Physics and
Industrial Control System

I suspect your problem is indeed that suspended task.  Are you sure there was no error message when the task got suspended?

You can learn something about the task status by running the “tt” command on it:

tt 0x16963d0

Mark

 

 

Mark,

The problem happened again yesterday, I've attached files with the result of the several commands.
What I've noticed is that there is a PLC task that is suspended with a error code:
Errno 0x110003 => S_memLib_BLOCK_ERROR

  NAME         ENTRY       TID    PRI   STATUS      PC       SP     ERRNO  DELAY

----------  ------------ -------- --- ---------- -------- -------- ------- -----

LBE1-PLCV   a4c48c        167fb20 149 PEND         2c9038  1682b70       0     0

LBE1-PLCV-> a4c48c        1686000 149 PEND         2c7154  1689080       0     0

LBE1-PLCV-> a4c48c        168a9e0 149 PEND         2c7154  168c990      46     0

LBE1-PLCV-> a4c48c        168f510 149 PEND         2c7154  1692420       0     0

LBE1-PLCV-> a4c48c        16963d0 149 SUSPEND      2ce5c4  1699110  110003     0

LBE1-PLCV-> a4c48c        169c1b0 149 PEND         2c7154  169f0c0       0     0

LBE1-PLCV-> a4c48c        16a29c0 149 PEND         2c7154  16a58d0       0     0

LBE1-PLCV-> a4c48c        16a87c0 149 PEND         2c7154  16ab6d0       0     0

LBE1-PLCV-> a4c48c        16ae5c0 149 PEND         2c7154  16b14d0       0     0

LBE1-PLCV-> a4c48c        16b4280 149 PEND         2c7154  16b7190       0     0

LBE1-PLCV-> a4c48c        16ba620 149 PEND         2c7154  16bd6a0       0     0

LBE1-PLCV-> a4c48c        16c0420 149 PEND         2c7154  16c34a0       0     0

LBE1-PLCV-> a4c48c        16c6230 149 PEND         2c7154  16c92b0       0     0

LBE1-PLCV-> a4c48c        16cc030 149 PEND         2c7154  16cef40       0     0

- I don't think there is a deadlock, but I don't know what to expect with the output of the command in this case.
- There is no task overflow, especially the one that is suspended.
- The result of Asyn report is in attachment

I've added your Asyn record and there was the following errors when I tried to connect to the READ  port or set ON/OFF a trace:

iocVMELB1 > 2015/09/08 11:29:24.509 [LBE1-PLCV-READ,0,0] [../../asyn/asynDriver/asynManager.c:1509] [CAS-client,0x8f70500,20] LBE1-PLCV-READ addr 0 queueRequest priority 3 not lockHolder

2015/09/08 11:29:24.509 [LBE1-PLCV-READ,0,0] [../../asyn/asynDriver/asynManager.c:1520] [CAS-client,0x8f70500,20] LBE1-PLCV-READ schedule queueRequest timeout

2015/09/08 11:29:27.925 [LBE1-PLCV-READ,0,0] [../../asyn/asynDriver/asynManager.c:637] [timerQueue,0xc04f20,60] LBE1-PLCV-READ asynManager:queueTimeoutCallback

2015/09/08 11:29:27.925 [LBE1-PLCV-READ,0,0] [../../asyn/asynRecord/asynRecord.c:2003] [timerQueue,0xc04f20,60] LBE1-PLCV-asyn: special queueRequest timeout

2015/09/08 11:29:34.509 [LBE1-PLCV-READ,0,0] [../../asyn/asynDriver/asynManager.c:637] [timerQueue,0xc04f20,60] LBE1-PLCV-READ asynManager:queueTimeoutCallback

2015/09/08 11:29:34.509 [LBE1-PLCV-READ,0,0] [../../asyn/asynRecord/asynRecord.c:2003] [timerQueue,0xc04f20,60] LBE1-PLCV-asyn: special queueRequest timeout

 

 

 

iocVMELB1 > 2015/09/08 11:31:44.577 [LBE1-PLCV-READ,0,0] [../../asyn/asynRecord/asynRecord.c:899] [CAS-client,0x8f70500,20] LBE1-PLCV-asyn: exception 3

2015/09/08 11:31:51.910 [LBE1-PLCV-READ,0,0] [../../asyn/asynRecord/asynRecord.c:899] [CAS-client,0x8f70500,20] LBE1-PLCV-asyn: exception 4

2015/09/08 11:31:54.527 [LBE1-PLCV-READ,0,0] [../../asyn/asynRecord/asynRecord.c:899] [CAS-client,0x8f70500,20] LBE1-PLCV-asyn: exception 4

2015/09/08 11:31:57.244 [LBE1-PLCV-READ,0,0] [../../asyn/asynRecord/asynRecord.c:899] [CAS-client,0x8f70500,20] LBE1-PLCV-asyn: exception 3

2015/09/08 11:32:00.077 [LBE1-PLCV-READ,0,0] [../../asyn/asynRecord/asynRecord.c:899] LBE1-PLCV-asyn: exception 5

2015/09/08 11:32:03.277 [LBE1-PLCV-READ,0,0] [../../asyn/asynRecord/asynRecord.c:899] [CAS-client,0x8f70500,20] LBE1-PLCV-asyn: exception 5

Thanks for your help
best regards

Hi Christophe,

Here are some things to look for:

- On vxWorks perhaps a task has been suspended.  Issue the "i" command to look at the status of all of the tasks.

- Perhaps there is a deadlock.  Issue this command several times in a row to see if there is a mutex that is always locked:

epicsMutexShowAll 1

- Perhaps there was a stack overflow.  Issue this command and look for tasks with a margin of 0

checkStack

If you don't find anything there then send us the output of "asynReport 10" on the Read port and Write port.

Mark

-----Original Message-----

From: [email protected] [mailto:[email protected]] On Behalf Of haquin

Sent: Wednesday, September 02, 2015 9:00 AM

To: tech-talk

Subject: Asyn ModbusTCP communication KO without error messages

Hi all,

I have a VxWorks IOC (with MVME-CPU using both eth interfaces) communicating with a siemens S7PLC via Asyn/ModbusTCP.

EPICS release 3.14.12.4 Asyn v4.22

After a while  (1 or 2 days), the communication is not working anymore ... but I have no error messages (no timeout nor 

disconnection ...).

 From IOC side I a have "Read Multiple Register" function reading the whole modbus table (109 registers) every second

and a "Write Multiple Register" function writing the value of a counter incremented every seconds from record level.

When I activate AsynTrace on IP Port or Read or Write ports there is no messages ...

asynReport on Read port indicates only 1 Read OK

asynReport on Write port indicates 0 Write OK

I can read the PLC register via "modpoll" tool from a Linux PC

I can start a Linux IOC connected to the same PLC

The netstat command on IOC shell tells that the TCP port is established but the Recv-Q is not equal to 0 (12 for example)

What can explain this behavior ?

thanks in advance !

-- 

Christophe Haquin

Control and Real Time systems Engineer

+33 231454661 office

+33 231454728 fax

SdA/GIM

GANIL

Bd Henri Becquerel BP 55027

14076 CAEN CEDEX5