Hi We have a trainee that will use the next months to implement support for the EtherCAT Network Information (ENI) XML in the userspace library (libethercat).
The ENI file is defined in ETG.2100 and can be used as an option by EtherCAT masters with filesystem support. We plan to extend the application interface with an option to import (and maybe export) an ENI file. The ENI file will be processed by the userspace library and setup SDOs, PDOs and domains accordingly. We also plan to extend the application interface with the required functions to allow registered PDOs to be read and written by specifying the slave position, index and subindex of the mapped entries. The ENI support will be an optional feature because it will have some dependency to the presence of a not yet chosen XML parser. Any comments on this planned implementation is welcome. Others might have had similar thoughts and we can still benefit from inputs. Best regards Knud Baastrup Software Designer Platform Software & Tools DEIF A/S Email: k...@deif.com<mailto:k...@deif.com> Tel.: +45 9614 8458<tel:+45%209614%208458> [cid:image001.jpg@01D69CFB.9B964810]<https://www.deif.com/> deif.com<https://www.deif.com/>
-- Etherlab-dev mailing list Etherlab-dev@etherlab.org http://lists.etherlab.org/cgi-bin/mailman/listinfo/etherlab-dev
