Have you encountered an unexpected Sercos ring fault while working with a CompactLogix L43 and three Kinetix 6000 drives? After running a non-stop process for about 3 hours, a sudden Sercos fault with code 16 #204 occurred, causing two drives to go into state 2 and the third to display chasing LEDs. Upon unplugging and re-plugging one of the fiber optic cables, the system was back up and running. However, this solution may not be practical for customers. Technical support suggested a potential backplane communication issue, but provided no concrete steps to diagnose or resolve it.
To enhance your search engine optimization, I recommend reviewing the settings in the module properties, specifically in the connection tab. It's important to understand the RPI and the settings for connection failure. Additionally, consider how you are connecting your devices, including any flex cards in use. Lastly, identify whether the error is occurring on the sercos card or on a specific drive module. This information will help troubleshoot and resolve any issues more efficiently.
Currently, I am 400 miles away from the processor, leading to the absence of an RPI value in offline mode. Despite not being marked as a major fault, the Sercos card located in the same rack as the processor is connected to the drives via the power bus. While the Sercos card displays no faults, the final drive on the bus is displaying code 16# 204, and attempts to access it result in a "drive not configured" message.
It is uncertain whether or not the CPX is impacted by this issue. Some CLX processors and network cards manufactured between late 2008 and mid-2009 may have a defective backplane communication chip, which was addressed in a Technical Service Bulletin (TSB). The affected cards may include sercos cards with an Atmel chip ending in *****64. Cards with chips ending in *****65 or from other brands are not affected. If you have a card with the faulty chip, you can get it replaced for free by AB. These chips have been known to cause intermittent communication issues, as experienced by a user trying to connect a nearly new machine to a C# application. Make sure to check for this issue if you encounter any communication problems - it could save you months of frustration. Good luck!
The settings appear to be correct. It is common for the drive to not be configured during a connection issue. Have you tried swapping out the drive or backplane with a spare to troubleshoot the problem?
Can the chip number be found within the serial number on the Sercos card? Unfortunately, I was unable to swap out any components due to being on-site at the customer's plant when this issue arose, and our distributor was located 400 miles away.
It appears that this kind of Sercos ring fault might be a result of fiber optic cable wear and tear or some interference. This could cause a sudden drop in communication, forcing the drives into a fault state. You can attempt using new cables and ensure that they're carefully routed away from possible high-interference devices. Also, it's important to check the status of the CompactLogix's backplane and monitor its performance using a diagnostic tool. If the problem persists, the issue may lie deeper, possibly in the network card's functionality or within the drives themselves.
I experienced a similar situation once and it turned out to be a problem with the fiber optic cables. The unexpected Sercos ring fault was due to some hairline fractures in the cables that disrupted communication at intermittent intervals, especially as the system heated up during prolonged operation. I'd suggest doing a thorough check of your fiber optic cables for any possible damage. Also, ensure your firmware is up to date as outdated software can sometimes cause such issues. If it's a backplane communication error as suggested, you might need to inspect the backplane for possible faults, but fiber optic issues are more common in my experience.
I've encountered similar Sercos ring faults with the Kinetix 6000 drives before. Sometimes, it's not necessarily a backplane communication issue but could be an issue with the fiber optic cable connectors or the Sercos module itself. I'd recommend checking the quality of your connectors and ensuring they are dust-free. You can also try changing the order of your drives to help pinpoint if the problem lies with a particular drive or the network. If this doesn't resolve it, it might be worth considering a replacement for the Sercos module. These steps might be more practical to implement in a customer environment compared to unplugging and re-plugging the cables frequently.
✅ 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: A Sercos ring fault is an error related to the communication ring in a Sercos network, often causing disruptions in data exchange between devices.
Answer: Possible causes could include issues with the backplane communication, faulty fiber optic cables, or configuration errors in the network setup.
Answer: Troubleshooting steps may involve checking the integrity of fiber optic cables, verifying network configurations, examining backplane communication, and ensuring proper grounding and power supply.
Answer: Practical solutions may include checking and replacing faulty cables, updating firmware, adjusting network settings, verifying device compatibility, and consulting technical support for further guidance.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.