...
As mandatory element, each EtherCAT slave has a slave information interface (SII) which is accessible by the slavemaster.
Physically, this is a special storage area for slave-specific data in an EEPROM memory chip. Its size is varaiable in the range of 1 kBits – 512 kBits (128 – 65536 Bytes).
...
After configuration, the firmware writes the content of the SII to the virtual EEPROM.In case the application has created a custom object dictionary, the EtherCAT Slave does not have enough information to write the whole SII image.
In this case, the application has to write the SII data starting from address 0x80 using the SII related funtions at every startup of the device.
Please find more informations about the SII in the EtherCAT Slave Protocol API:
...
- Open the Conformance Test Tool.
- Scan for any device and open the SII tab.
- Select the ESI file from the tab on the right side "ESI Files Repository" and add it to the SII tab via drag and drop.
- This can be saved in a *.BIN file now.
- Open the *.BIN file in an Hexeditior öffnen.
- Delete every entry before address 0x080 (first 128 bytes). This area will we written by the stack and is therefore not needed.
- change the *.BIN file to a *.c formatted file.
...
Therefore the Bus Startup should be changed from "Automatic" to "Controlled by Application" when you confgure the stack with a database.
This is how it needs to be configured in Sycon.net (other configuration Tools may vary):
...