We are experiencing issues with the connection between the IT2I thermocouple card and the RTD temperature sensor card when connected through a Point IO AENTR. The Point IO itself connects seamlessly, but the cards keep attempting to connect and then faulting out. We have tested each card individually, adjusting the chassis size each time. On the web server, the IO module is visible and in Studio, the serial number is detected. We have tried various firmware revisions, different Point IO bases, IT2I cards, thermocouples, and installed new add-on profiles. It is important to ensure the correct chassis size is configured in the web server and PLC as the module is visible in RS linx. Our hardware/software setup includes Studio 5000 V32, AENTR/B Point IO V5.019, IT2I card with IT2I base V 3.014, standard dumb switch, L72 PLC, and ENBT Ethernet card. Could this issue be resolved by implementing a DLR, given that it is a 2-port Point IO system?
Is the AENTR included in the dimensions of your chassis size?
Inquired Cheeseface, "Does the chassis size account for the AENTR module?" Upon expanding, it was confirmed that a 2-slot chassis accommodates the AENTR module along with a plus card.
Glazedgater mentioned that a aentr plus card was used to create a 2 slot chassis. Currently, only one card is connected.
Have you ensured that the ethernet port settings are configured properly? Check if one side is set to a specific speed like 10/100, while the other is set to auto-negotiate.
Error 16#0203 indicates a communication issue between the controller and IO module. This error occurs when the controller is unable to receive data from the module or may have lost the data transmission. To resolve this issue, it is recommended to verify the ENBT version (preferably version 6.006) and review the media counters on both devices for any discrepancies. This step can help in identifying and troubleshooting the communication problem between the controller and IO module.
While a DLR implementation might help, it seems like you've pretty much covered every aspect of the typical troubleshooting steps. I'm wondering if this could be a baud rate or a network communication setup issue at its core. Baud rate mismatch is a common cause of faults in communication between these devices, and it might be worth a look under the advanced settings of the module configuration for the IT2I. Also, make sure that the IP address, subnet mask, and default gateway are correctly defined, and the communication parameters are rightly set up as sometimes even a minor mismatch could cause the module to fault and attempt to reconnect. Good luck!
It sounds like you've narrowed things down pretty well, so it might not be a hardware issue. From what I'm hearing, it could indeed be a network communication issue, and implementing a DLR could potentially resolve this. However, before moving forward with a DLR, have you ensured that your Point IO and the IT2I card are on the same firmware revision? When setting up a Point IO system, especially when using 2-port modules, it is recommended that the module and any others connected to it are on the same firmware revision to avoid any unexpected issues. Before any extensive rearrangement, I would also suggest checking the controller setting in Studio 5000 to make sure the IP settings match your network and that the network's subnet is properly set. Sometimes, especially in a crowded network architecture, the simplest things can be overlooked and end up being the culprit.
It sounds like you've done a thorough job troubleshooting, and it's frustrating when everything seems to point towards a connection issue. Given that the Point IO is a 2-port system, implementing a Device Level Ring (DLR) could indeed enhance the reliability of your network by providing redundant paths for communication. This might help mitigate any intermittent connection issues you’re experiencing between the thermocouple card and the RTD card. Also, double-check any grounding or power issues, as these can sometimes lead to erratic behavior. Have you considered reaching out to Rockwell support for assistance? They might have seen this specific issue before and could provide more targeted insights.
It sounds like you've already put in a ton of work troubleshooting this setup! Given that you’re experiencing communication issues with the IT2I and RTD cards specifically, I would suggest checking the wiring and termination of the communication links, as intermittent faults can sometimes stem from signal integrity issues. Also, implementing a DLR (Device Level Ring) could potentially improve the reliability of your connections, especially in a dual-port scenario like yours. Just make sure to revisit the device configurations to support DLR; sometimes a simple oversight there can cause similar connectivity problems. Good luck—I hope you find a resolution soon!
It sounds like you've gone through quite an extensive troubleshooting process! Since you've already confirmed the visibility of the IO module in both the web server and RS Linx, it might be worth checking the wiring between the cards and the Point IO; sometimes, simple physical connection issues can cause persistent faults. As for implementing a DLR (Device Level Ring) on a two-port system, it could improve your connection resilience, but make sure your network topology supports it and that you have the correct settings in place. If the DLR doesn't help, consider reaching out to Rockwell support or checking forums specific to your hardware setup for more targeted advice!
It sounds like you’ve really covered a lot of ground troubleshooting so far! Given your detailed setup, I wonder if the fault might be related to the configuration of the DLR (Device Level Ring) in a 2-port Point IO system. While the standalone connections seem fine, enabling DLR might help manage redundancy and ensure better communication between your cards. Also, double-check the baud rate settings and ensure they match across devices; sometimes, mismatched settings can cause connection issues even if everything else appears correct. It could be worth giving that a shot along with a fresh look at the firmware compatibility across your components. Good luck!
✅ 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 issues could be related to firmware revisions, chassis size configuration, hardware compatibility, or add-on profiles. It is important to ensure proper settings and compatibility between the devices.
Answer: You can troubleshoot by testing each card individually, adjusting the chassis size, checking firmware revisions, trying different Point IO bases, and ensuring correct configuration in the web server and PLC.
Answer: Implementing a DLR might help improve the network reliability and fault tolerance in the Point IO system, but it's essential to address the root cause of the connection faults first before considering additional network configurations.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.