Option 1: Default Implementation (Slave 1)
Process data logic implemented by a customer application from the process data image.
Option 2: Integrated Sample Application (Slave 2)
Process data provided by a sample application, e.g., CiA402, instead of the process data image. Here the behavior of the sample application can't be changed. This can be selected from within EC-Engineer when building the EC-Simulator configuration.
Option 3: Actual Slave Application (Slave 3)
EC-Simulator now supports an interface for developing and testing actual slave device firmware. Software hooks are provided for connecting Slave Stack Code APPL_XXX() functions to the actual slave application code. Here it is possible to control the EtherCAT State Machine, handle process data, work with CoE objects, etc.