If it can't cope with both complete and incomplete transfers in PDO configuration, then it is not compliant with the EtherCAT specification, and you should throw it away and find a better slave instead.
Gavin Lambert Senior Software Developer COMPAC SORTING EQUIPMENT LTD | 4 Henderson Pl | Onehunga | Auckland 1061 | New Zealand Switchboard: +49 2630 96520 | https://www.tomra.com The information contained in this communication and any attachment is confidential and may be legally privileged. It should only be read by the person(s) to whom it is addressed. If you have received this communication in error, please notify the sender and delete the communication. -----Original Message----- From: Eibach, Dirk Sent: Friday, 5 March 2021 2:59 am To: Eibach, Dirk <dirk.eib...@cloos.de>; Richard Hacker <h...@igh.de>; etherlab-users@etherlab.org Subject: Re: [Etherlab-users] Estun EE-R0: Invalid input configuration An interesting difference I found is that the Acontis master does all SDO-writing on block(like ecrt_slave_config_complete_sdo()), whereas Etherlab does it in single transfers. I already realized that the Estun slave has problems with this when mapping PDO entries. So I had already patched this in fsm_pdo_entry.c. But maybe the same applies also to the other SDO transfers? I will check if I can patch this too. -- Etherlab-users mailing list Etherlab-users@etherlab.org https://lists.etherlab.org/mailman/listinfo/etherlab-users
