/eh/2025-01-08/173633966714069467/picture.png)
/eh/2024-12-24/173503345348979036/Favorite-Icon.png){kind=icon}
/eh/2025-07-08/1751962110204480194/picture.png)
/eh/2025-06-21/1750485478958537574/countryInfoIcon.png)
/eh/2025-06-21/1750485741321434291/Hi-Sign-in-My-Nihao.png)
/eh/2025-06-21/1750485837193896318/cart.png)
/eh/2025-06-21/1750485968202533847/cart.png)
/eh/2025-04-17/1744862476612819675/hot-img.png)
/eh/2025-11-07/1762504524550532584/header-icon.jpg){kind=icon}
/eh/2025-07-07/1751875582852206790/header-icon.png){kind=icon}
/eh/2025-07-07/1751875587886277738/header-icon.png){kind=icon}
Best in 7 days
Object dictionary
According to the profiles and input the object dictionary is generated as C source code file that is integrated as interface for the stack into the application. As defined in the configuration it is possible to access the objects of the object dictionary directly as C variable from the application. Alternatively, the access to functions is possible via index and subindex.
EtherCAT stack configuration and initializing
According to the definitions of the object directory a configuration- and initializing file is created which secures that only the used services of the EtherCAT stack will be compiled and initialized. By doing so a memory saving configuration of the EtherCAT stack is achieved.
Electronic data sheet (ESI)
All EtherCAT devices must have an electronic data sheet that describes the parameters of the object directory electronically. The EtherCAT DeviceDesigner creates the EDS file in XML format. The files are always according to the recent object dictionary. This helps to avoid error prone work.
Device documentation
A device documentation will be created in HTML and text format. It covers the object dictionary with all its adjustments and descriptions and all other device specific adjustments. The generated documentation reflects always the recent adjustments and latest implementations. It is always up to date. The use of the generated documentation as part of the user documentation of the device is possible.
Device profile
EtherCAT DeviceDesigner profile files for the communication profiles of ETG and device profiles of CiA are available. A profile file includes templates for all object types of a profile with standard features and descriptions of the object. Objects can be imported, duplicated and adjusted to individual characteristics of the device. By use of predefined objects, the time for development shortens significantly and the error prone work of manual data input falls away.
Following profile files are momentarily available for device and communication profiles:
- ETG.1000 – CAN application layer over EtherCAT (CoE)
- CiA 401 – Device Profile for Generic I/O Devices
- CiA 402 – Device Profile for Motion and Drive Controller
- CiA 419 – Device Profile for Battery Charger
