[etherlab-dev] 1 datagram UNMATCHED! / working counter changes

[Daniel Bechter]

> Does this mean, that the sniffer does not see any frame with unanswered
> datagrams, or do you see datagrams with working counter 0 when the frame
> comes back from the bus?

I spent quite some time looking through thousands of packets but could not
find an LWR datagram that did not leave with WC0 and return with WC3.
BTW is there a parser for pcap sniffs which can perform some EtherCAT
datagram analyzation? Or is there something that can analyze the frames
within the debug ring?

> I guess the first one is the case, that would fit to the unmatched
> datagrams.

What is meant by "unanswered datagram"? How does performance of the PC
running the master play a role in this scenario?

> Could you please post the logs with 'ethercat debug 2' (be careful,
> this will blow up your logs, please post only the interesting parts,
> when an unmatchable datagram is received).

Hope I am not missing the most important parts:

Aug  3 10:27:13 SWES-Linux kernel:  00 00 0cU E]<7>[3250077.7103C <7A7T40d:
U50Et: Received 07r40<7>[3250077.7107 a7E.t00R 307E.TA 00 00 00 07179G:
sendin070B8 <0rE 0 rd 3C 00 00 00h7BC1 00 00 00D C0 91A]G      
Aug  3 10:27:13 SWES-Linux kernel: [37BC0 00 00 00 00 00DD7 D 8CU[9  
Aug  3 10:27:13 SWES-Linux kernel: 
Aug  3 10:27:13 SWES-Linux kernel: <37Bh3 00 00 00 00 00 D C3 D7g>t  00    
Aug  3 10:27:13 SWES-Linux kernel:                     
Aug  3 10:27:13 SWES-Linux kernel: [3250077.712482] EtherCAT DEBUG:
UNMATCHED datagram:
Aug  3 10:27:13 SWES-Linux kernel: [32500Geh008F[7t000055h0 00[7therCAT
DEBUG: ec_master_send_datagrams
Aug  3 10:27:13 SWES-Linux kernel: [3250077.712646] EtherCAT DEBUG: adding
datagDDDD   77     77    77  D6tas06CBnEA z>08[7]T191     01    
Aug  3 10:27:13 SWES-Linux kernel:                     
Aug  3 10:27:13 SWES-Linux kernel: [3250077.712893] EtherCAT DEBUG:
UNMATCHED datagram:
Aug  3 10:27:13 SWES-Linux kernel: 30T0701hB00705hB00707C:0 00 00 00 00 00
00 00 00 00 00 00 
Aug  3 10:27:13 SWES-Linux kernel: [3250077.713013] EDDDDD   77 C   77 C  77
8ta702C:gA z>.]7]rG173    772   
Aug  3 10:27:13 SWES-Linux kernel:                     
Aug  3 10:27:13 SWES-Linux kernel: [3250077.713261] EtherCAT DEBUG:
UNMATCHED datagram:
Aug  3 10:27:13 SWES-Linux kernel: [30T8700hB00704C:00776C:0 00 00 00 00 00
00 00 00 00 00 00 
Aug  3 10:27:13 SWES-Linux kernel: [3250077.713407] DDDDD   77     77
00hD0]ts31h dEA z>.]7]T197     06    
Aug  3 10:27:13 SWES-Linux kernel:       
Aug  3 10:27:13 SWES-Linux kernel:              
Aug  3 10:27:13 SWES-Linux kernel: [3250077.713654] EtherCAT DEBUG:
UNMATCHED datagram:
Aug  3 10:27:13 SWES-Linux kernel: <730T9701hB00701CB00703C:0 00 00 00 00 00
00 00 00 00 00 00 
Aug  3 10:27:13 SWES-Linux kernel: [3250077.713773] EDDDD   770C   37
707CD8tas01hBdEA z>.]7]TG01    770   
Aug  3 10:27:13 SWES-Linux kernel:                     
Aug  3 10:27:13 SWES-Linux kernel: [3250077.714020] EtherCAT DEBUG:
UNMATCHED datagram:
Aug  3 10:27:13 SWES-Linux kernel: [3250077.71400T9701hB0B708hB00700C:0 00
00 00 00 00 00 00 00 00 00 00 
Aug  3 10:27:13 SWES-Linux kernel: [3250077.714149] EDDDDD   77     31hD3 00
00 00 00 0C 00 00 00 67 EB 00 00

I used the 3 GHz P4 and set up a loop with 10 kHz (user space app without
realtime patches applied).

Greets,
Daniel