- Project file handling and comparing
- Topology creation via bus scan, read from file or drag-and-drop
- Comparison between configured and real networks
- Process Image with scaling
- S2S Editor
- Handling for FSoE Master and Slaves
- Various Sample Rates
- Distributed Clocks (DC) settings
- Import signal names from CoDeSys
- Export network configuration files
- ETG.2100 with extensions of koenig-pa GmbH, ETG.2100
- IEC 61131-3 Standard, Export of “C” header files
EtherCAT master network configuration
EtherCAT Cable Redundancy
Slave-to-Slave communication
Slave-to-Slave (S2S) communication allows logical communication of slaves in input-output matrix of the Process Image without direct physical wiring.
By means of Slave-to-Slave communication is performed the management of safety system. Safety uses so called black channel approach, where FailSafety over EtherCAT (FSoE) is sitting on top of EtherCAT slave stack in slave device. Here safety and usual process are mixed in one media. EtherCAT Master has to route safety message(s) from safety slaves to safety masters using Slave-to-Slave communication. In case of safety situation, the Slave-to-Slave is unable to send data and in connections, crc and status will be zeros instead of valid data. In this case safety logic starts according to defined behavior.
