Subject: Persistent 16#0203 Fault with PointGuard Card - Seeking Solutions Hello everyone, I've reached out to Rockwell multiple times regarding the recurring 16#0203 fault related to the PointGuard card, and despite following all of their recommended troubleshooting steps, I continue to encounter this issue. I’d like to share the specifics of my setup and seek your guidance. I am operating with a 1768-L45S controller alongside a 1768-ENBT module, which communicates with four 1734-AENTR units. Each of these racks comprises various standard and safety Point I/O modules. Notably, all but one of the racks adhere to the maximum CIP connection limit of 20 and comply with the power specifications for the AENTR modules (I added 1734-EP24DC power supplies where needed). Occasionally, approximately every 5 to 10 minutes, one of the safety I/O cards experiences the 16#0203 fault. This disruption temporarily disables the safety elements connected to that specific card (such as Emergency Stops and Guard switches), leading to a loss of communication with the processor. Shortly thereafter, the card returns to operational status; however, the fault has significant implications for safety. Rockwell's recommendations have included increasing the Requested Packet Interval (RPI), adjusting the network timeout settings, verifying that power limits are not being exceeded, updating firmware, ensuring CIP connections remain below 20, and altering the rack configuration to "none." I have diligently implemented all of these suggestions except for one AENTR rack. Unfortunately, the faults persist. Could anyone offer insights into a potential resolution? Is it possible that the unmodified rack could be the source of the issue, potentially causing faults in safety cards at other racks with the 16#0203 error code? If you require further information or specifics about my configuration, please don't hesitate to ask. Thank you for your assistance! Best regards, Eric
Certainly! Here's a rephrased version of your text that enhances its quality, uniqueness, and SEO-friendliness: --- Attempting to establish more than 20 CIP connections to a single AENTR is likely to cause significant issues. In my experience, when there have been complications in the past, they primarily stemmed from the overloaded AENTR itself. However, I don't believe that exceeding this limit would necessarily lead to failures in other network components, particularly regarding the 16#0203 error. It's important to note that you are already aware of the challenges associated with excessive CIP connections, and addressing these issues will be essential moving forward. I recommend prioritizing known problems before venturing into uncertain territory. --- This revised text incorporates clearer language while maintaining the original message and enhancing its SEO potential.
By the way, what do you mean by network topology? I presume you are referring to a device-level ring or linear network configuration, given that you're utilizing AENTR devices.
The network topology in use features a linear/star configuration. Thank you for your response. I am planning to address the issue with the rack that has an excessive number of CIP (Common Industrial Protocol) connections. However, given that the other two racks on the network have also been non-operational despite attempts to fix them, it's uncertain if the CIP connections are the cause of the problem. I am continuing to experience issues with the 1734-IB8S/OB8S module, which frequently faults with error code 16#0203. Interestingly, I've observed that it typically occurs with just one card at a time rather than multiple cards, and I am unsure if this detail is significant.
It appears that there may be a firmware problem affecting both the 1734-AENTR and potentially the 1768-ENBT devices. Additionally, we are encountering a PointGuard error, specifically Error 16#0203, within RSLogix 5000. Access Level required for this issue is TechConnect. Best regards, George
The current firmware version is 3.012, which is the latest available from Rockwell. Following their instructions, I've successfully updated both the Ethernet card and the processor. Thank you for your assistance!
✅ 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: - Increasing the Requested Packet Interval (RPI). - Adjusting the network timeout settings. - Verifying that power limits are not being exceeded. - Updating the firmware. - Ensuring that CIP connections remain below 20. - Altering the rack configuration to "none."
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.