To get straight to the point, whether other servo drives can receive commands from the PLC (master) depends on the network topology and configuration that allow for continued communication. Here is a detailed analysis of this issue:
1. How EtherCAT Networks Work
EtherCAT is a real-time industrial fieldbus protocol based on Ethernet, utilizing a “Processing on the Fly” mechanism. The master sends a data frame, which is processed (read or written) at each slave and then returned to the master. EtherCAT networks support various topologies (such as line, ring, star, or tree) and have high fault tolerance and flexibility.
2. Impact of Slave Power Loss
When a slave servo drive in an EtherCAT network loses power, the specific impact depends on the network topology and configuration:
-
Line Topology (Daisy Chain): In a line topology, EtherCAT slaves are connected sequentially through input (IN) and output (OUT) ports. If one slave loses power, its output port will be unable to forward data frames, causing subsequent slaves to be unable to receive data frames sent from the master. Therefore, in a line topology, a powered-off slave will interrupt communication for the entire network, and subsequent slaves will be unable to receive PLC commands.
-
Ring Topology or Redundant Configuration: If the network is configured in a ring topology with cable redundancy enabled, EtherCAT can bypass the powered-off slave through an alternate path, continuing communication with other slaves in the network. In this case, other servo drives can still receive PLC commands. The EtherCAT protocol supports automatic detection of disconnected nodes and returns data frames to the master via the reverse path, thus maintaining communication.
-
Star Topology or Using Couplers: If a star topology is formed using EtherCAT couplers (such as Beckhoff’s EK1100 or EK1122), the powered-off slave will only affect the branch directly connected to it, without impacting communication for slaves on other branches. Therefore, other servo drives can still receive PLC commands normally, provided they are on unaffected branches.
3. Handling Mechanisms for Slave Power Loss
-
Distributed Clock (DC) Synchronization: EtherCAT uses a Distributed Clocks mechanism to achieve high-precision synchronization. If a slave loses power, the distributed clock in the network may be affected, but the master will automatically recalibrate the clock to maintain synchronization with other slaves.
-
Error Detection and Diagnosis: The EtherCAT master can detect the power loss state of a slave through the Working Counter (WcState). If a slave loses power, the master will report communication errors (such as “network adapter open” or “device ID does not match”), but this will not prevent the master from continuing communication with online slaves.
-
Hot Connect: EtherCAT supports hot connect functionality, allowing slaves to be dynamically added or removed during operation. If the network configuration supports hot connect, the powered-off slave can be recognized by the master as offline without affecting normal communication with other slaves.
4. Mitigation Measures in Practical Scenarios
To ensure that the power loss of one slave does not affect communication with other slaves, the following measures can be taken:
-
Use Redundant Topology: Configure a ring topology or use EtherCAT couplers to increase network fault tolerance.
-
Enable Hot Connect Functionality: Enable hot connect in the master configuration to allow dynamic adjustments of slaves in the network.
-
Monitor Slave Status: Implement slave status monitoring in the PLC program (e.g., through NodeName_EtherCAT.wState enumeration) to timely detect power loss and take appropriate actions (such as ignoring offline slaves).
5. Considerations
-
Slave Configuration: Ensure that each slave’s EtherCAT address (EtherCAT Addr) and auto-increment address (Auto Inc Addr) are configured correctly so that the master can accurately identify the network status when a slave loses power.
-
Synchronization Signal (Sync0): Some servo drives (such as Delta servo drives) require receiving the Sync0 signal to enter operational status. If the powered-off slave affects the distribution of the synchronization signal, it may be necessary to check the master’s distributed clock configuration.
In summary, in an EtherCAT network, whether other servo drives can continue to receive PLC commands when one slave servo drive loses power depends on the network topology and configuration:
-
In a line topology, a powered-off slave will interrupt communication for subsequent slaves, causing other slaves to be unable to receive commands.
-
In ring or star topologies (with couplers or redundant configurations), other slaves can typically continue to operate normally.
-
By implementing sound network design (such as redundant topology and hot connect) and monitoring slave status, the impact of power loss can be minimized.