Closed Tomisacats closed 4 days ago
Making a wireshark capture and posting it here would allow to investigate the cause. As it stands now there is not much information to work with.
This is a screenshot. I hope it helps to understand the problem. Thank you
Thanks for the screenshot, however this is not very helpful. I need a full .pcap file from init to OP (or as far as you get). The capture files compress very well so even large ones can be posted here. I need to see all interaction from SOEM with the slaves as well as any timing of the packets.
Thanks for the data. This is not what I requested. I asked a capture starting from init. This is something between pre-op and safe-op. And it is a set of over 200.000 packets.
Anyway. Even here I could figure out that there is something wrong with the slave structure data. Slave numbering in SOEM is normally starting from 0x1000. This is true for most of your slaves, however slave 7 and 10 are addressed as 0x61f7 and 0x061fa for Adp. I am quite sure the configuration address is 0x1007 and 0x100a. This is the reason the SDO requests return with zero for workcounter.
Please send a file with the correct information, then I can be of more help.
Sorry, we cannot provide the communication data related to initialization. Thank you for your answer
First, the device name is garbled Second, when I connect 20 devices, the seventh and tenth devices can't read data using SDO, but separate connections can The above issues only occur in versions above V1.3.3-beta.1 I hope the author can fix it, thank you very much