In my facility, I have a ring network controlled by a Logix5000 L72 v20 PLC that manages the HVAC system. This network includes 2 PLC chassis equipped with 1756-EN2TR and 17 1794-AENTR Flex IO modules, as well as 24 1783-ETAPs. The main EN2TR is currently running on version 5.08. Is there a way to detect the location of a ring break or fault in the network from the PLC? When checking the network through the master ethernet card properties, it only indicates a Ring Fault with Supervisor mode enabled. While I am monitoring the connection to each device, it only shows when communication is lost, requiring 2 breaks in the ring to be identified. I am looking for a method to monitor each individual connection to easily pinpoint a single break, display it on an HMI for quick identification, and resolve the issue without the need to physically inspect each device.
If a fault occurs in a ring network, the Ring Supervisor in RSlinx will display the IP and MAC addresses of the broken node under the Network tab. This feature is useful for quickly identifying and troubleshooting network issues within a ring topology.
Monitoring network devices programmatically is made easy with AB's faceplate for panelviews, which includes an AOI providing necessary examples. By utilizing a MSG instruction to each device on the ring, you can access a variety of diagnostics and graphics that indicate the type of device and ring master. According to EIP standards, all qualified devices will respond to CIP Message instructions in a similar manner, allowing for programmable monitoring. For more information on port monitoring, remote interface status, and other features, refer to the documentation provided at https://literature.rockwellautomation.com/idc/groups/literature/documents/um/1756-um004_-en-p.pdf. Alternatively, download the DLR networks faceplate from AB to simplify the monitoring process.
When there is a fault in the ring, RSlinx will display the IP and MAC addresses of the break in the Network tab of the ring supervisor. After troubleshooting, I discovered the issue was caused by having some Ethernet taps configured as ring supervisors instead of the en2tr card in the primary PLC.
Idiotsecant mentioned the ability to monitor devices programmatically by using a faceplate created by AB for PanelViews. This faceplate includes an AOI with examples and graphics for different devices, including a crown for the ring master. By using MSG instructions to each device on the ring, you can effectively monitor EIP-qualified devices and DLR participants. The document linked provides further information on port monitoring, remote interface status, and more starting from page 43. Consider downloading the faceplate for DLR networks to simplify the monitoring process. In my experience, I have implemented logic in all my PLCs with rings to monitor ring health and automatically reset a ring fault when connections are restored. If you're interested, I can provide more details on the MSG instruction tomorrow.
Robertmee mentioned having logic in all of his programmable logic controllers (PLCs) that includes rings for monitoring ring health and automatically resetting a ring fault when the connection is restored. This is achieved through two Message Instructions. If you're interested, I can provide more details on the MSG instruction tomorrow. I found the Allen Bradley Ethernet/IP DLR Operating Manual through Idiotsecantlink and am currently setting it up, along with monitoring the loop.
Absolutely, troubleshooting in such intricate network systems can present quite the challenge. Unfortunately, within the current built-in capabilities of Rockwell PLCs, precise fault detection down to the device level remains a bit elusive. However, one solution could involve using an intermediary device, a Managed Ethernet Switch perhaps, along the ring network to help you identify the location of a break or fault more accurately. This could provide visibility at the device level directly. Additionally, using proper IP address schemes and subnet masks along the ring can also ease the process of identifying and isolating faults. It may also be beneficial to consider seeking an Integrated Architecture solution from Rockwell Automation, providing a cohesive HMI and control platform, for tackling the very kind of problem you're encountering.
Yes, there are a few strategies to detect ring breaks or faults more efficiently. One would be to add diagnostic routines to your PLC code. By polling each Ethernet node for status periodically, your PLC can approximate the broken segment between the last known good node and the first non-responsive node, thus narrowing down any potential issues. This status could be displayed on your HMI, helping speed up the troubleshooting process. Additionally, consider using managed switches, which can provide more detailed diagnostic information. Also, it's crucial to maintain thorough documentation of your physical ring layout and connection order, as it makes it easier to physically inspect the correct segment if a fault is detected.
You brought up a great point. Unfortunately, your current setup using a PLC will not directly provide individual device health status or ring breaks. You might have to add a network diagnostic tool to catch these kind of situations, however, incorporating network diagnostic equipment into an industrial setup might introduce new complexities and costs. Ideally, there should be a blend of software and hardware tools which can give you metrics about network health continuously and this should be integrated to the PLC in such a way that it can be visualised in the HMI. Also, remember that the choice of network diagnostic tools depends heavily on the specifics of your local network architecture and compatibility with your existing Logix5000 L72 v20 PLC setup.
It sounds like you're dealing with quite a complex setup! One approach you might consider is implementing a periodic ping or heartbeat check from the PLC to each device on the network. You could create a routine that sends a simple command to each Flex IO module and the 1783-ETAPs; if the response times out, you'll immediately get a flag indicating which device isn't communicating. This way, you'll be able to pinpoint a single break without having to wait for multiple faults. Also, integrating this into your HMI can give you real-time updates on the network status, allowing for quicker troubleshooting. Just make sure the polling interval is reasonable so you don’t overwhelm the network with requests. Good luck!
You might want to consider implementing a more robust monitoring strategy by utilizing added diagnostic tools or protocols that can help identify the exact location of the fault. For instance, looking into enabling Link Layer Discovery Protocol (LLDP) on your network devices could provide more detail on the state of each connection. Additionally, if possible, configuring your EN2TR modules to send alerts to the PLC when a device loses communication might help isolate faults faster, instead of waiting for the ring status to indicate a more severe issue. Integrating these features into your HMI display could allow operators to diagnose issues at a glance without needing to inspect each node physically.
It's definitely tricky with ring networks since they can mask faults until you have multiple breaks. One way to improve your fault detection is to implement periodic diagnostics or use the event-driven features of the EN2TR module. You might consider setting up a "ping" or a heartbeat signal for each device in the network. This way, the PLC can continually check the status of each connection and can actively report individual device failures to your HMI. Additionally, if you can customize the error reporting in your PLC logic, you could create a routine that logs specific faults as they occur and provides more detail on which segment of the network is affected. This would streamline your ability to identify and address faults without additional physical checks.
✅ 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: To detect ring breaks in your network, you can utilize the Supervisor mode on the master ethernet card properties. However, this method may only indicate a Ring Fault without specifying the exact location of the break. Consider implementing a monitoring system that can track individual connections to quickly pinpoint single breaks for easier identification and resolution.
Answer: In a ring network controlled by an Allen Bradley PLC, components such as the Logix5000 L72 v20 PLC, 1756-EN2TR, 1794-AENTR Flex IO modules, and 1783-ETAPs are typically utilized. These components work together to manage the HVAC system and monitor network connections.
Answer: To upgrade the version of the main EN2TR in your Allen Bradley PLC network, you would typically need to follow the specific upgrade procedures provided by Allen Bradley for that particular device. Ensure you have the necessary firmware files and follow the instructions carefully to avoid any issues during the upgrade process.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.