[etherlab-users] UNMATCHED and SKIPPED datagrams

[Florian Pose]

Hi,

On Wed, Jan 14, 2009 at 11:10:24AM +0100, Erwin Burgstaller wrote:
> [57061.710532] EtherCAT DEBUG: skipping datagram f4d85640.
> [57061.711383] EtherCAT DEBUG: UNMATCHED datagram:
> [57061.711388] EtherCAT DEBUG: 0C 44 00 00 00 00 60 80 00 00 00 00 00 00 00 00 
> [57061.711415] EtherCAT DEBUG: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
> [57061.711429] EtherCAT DEBUG: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
> [57061.711443] EtherCAT DEBUG: 00 00 00 00 00 00 00 00 00 00 00 12 0C 90 01 02 
> [57061.711457] EtherCAT DEBUG: F7 00 00 00 00 00 00 00 00 20 E6 E5 DD 03 E0 03 
> [57061.711471] EtherCAT DEBUG: 02 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 
> [57061.711486] EtherCAT DEBUG: 00 00 00 00 00 00 00 00 00 00 05 00 
> [57061.711497] EtherCAT WARNING: Datagram f4d85640 (domain0-0) was SKIPPED 1 time.

skipped datagrams mean, that the datagram is sent again, although the
answer to the last sending hasn't been received yet. This usually means
that the realtime cycle was executed too short after the last one (maybe
because the last one was delayed for some reason).

The unmatched datagram you see after one was skipped is the one that was
sent out in the last cycle. This can't be matched because the
corresponding 'sent' datagram was skipped.

> There's another strange warning in there, but maybe harmless:
> EtherCAT WARNING: Unknown category type 0x003C in slave 0.

Category type 0x003C is not part of the specification. If this is your
own slave, please check, if there are valid data in the SII.

-- 
Best regards,
Florian Pose

http://etherlab.org