We are encountering a persistent issue with our machine equipped with 3 Kinetix 5500 servos that are linked in a daisy chain configuration. The last servo is linked to a switch, which is then connected to the network. Throughout the day, the servos experience time sync faults around 4 to 5 times, requiring frequent machine resets to resolve the faults. Interestingly, a similar machine without network connectivity does not encounter any servo issues. We are exploring options to either deactivate the time sync feature on the servos or disconnect them from the network. The PLC (RSLogix 5000) shares the same switch as the servos but necessitates network connectivity. Unfortunately, altering the switch settings to disable time sync is not feasible. One potential solution we are considering is implementing a NAT device between the switch and the network to prevent servo communication with the network. However, we are open to alternative suggestions and would appreciate any input or ideas you may have.
If you are experiencing synchronization issues, make sure to verify if your network switch is equipped with IEEE-1588 Sync capabilities. If it lacks this feature, that may be the root cause of your problem.
I searched for information on the Spider II 16TX EEC switch's IEEE-1588 sync capabilities but couldn't find any. I'm unsure how frequently the servos attempt to sync - is it limited to 5 times a day, or does it try more often but only fails occasionally due to the switch? Despite having time synchronization enabled in the plc, the servos are consistently 3 hours ahead. I'm uncertain if this discrepancy is affecting the syncing process.
The interaction between PLC and Servo is crucial, as disabling time synchronization on the PLC can lead to issues with program compilation and downloading. For more information on this topic, refer to Rockwell's resources. It is essential to ensure that the switch supports this functionality to avoid any unexpected or problematic outcomes.
If you're unsure about the specific PLC model you're using, such as the 1769-L30ERM with 2 ports, it's best to connect the servo chain directly to the PLC's second port to avoid any compatibility issues with PTP/sync support. Upon further consideration, it seems unlikely that the switch is causing the problem given its frequency. It's worth investigating potential network configuration issues leading to packet loss or FSC errors. Try connecting the chain directly to a spare PLC port and check the PLC's web page for any missed or rejected packets, network utilization percentage, and other factors affecting the servo's performance in relation to packet loss.
We will attempt to connect the chain to the plc. A peculiar aspect is that we have not encountered this issue until recently, despite the wiring remaining unchanged throughout. The only notable change is that we have been operating the machine more frequently as of late.
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: - The servos are encountering time sync faults due to the network connectivity, which might be causing disruptions in the synchronization process.
Answer: - The servos are connected in a daisy chain configuration, with the last servo linked to a switch that is connected to the network.
Answer: - While it might be an option, the thread mentions exploring alternatives due to limitations in altering the switch settings to disable time sync.
Answer: - One potential solution being considered is implementing a NAT device between the switch and the network to prevent servo communication with the network.
Answer: - The absence of network connectivity in the similar machine indicates that the network might be the source of the time sync faults experienced by the servos.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.