The EtherCAT slave information is generated on the fly and by default is not stored anywhere, it’s simply emulated. However, the SDK provides a set of functions to store the EtherCAT slave information content in a physical storage. Therefore, after a hardware reset the SDK will use the content from the non-volatile memory instead of the content generated on the fly.

Function	Description
EC_API_SLV_cbRegisterFlashInit	Register non-volatile memory initialization function
EC_API_SLV_EEPROM_cbRegisterLoad	Register non-volatile memory read function
EC_API_SLV_EEPROM_cbRegisterWrite	Register non-volatile memory write function