Hello everyone, I am currently facing an issue with my 1756-EN2TR dual-port Ethernet IP Module connected to my 1756-L73 PLC. Both ports in my project tree are showing hazard symbols. I previously had hazard symbols on two 1783-ETAP modules connected to the ports of the 1756-EN2TR, but I resolved this by running the eds file and power cycling. However, I am unable to find an eds file for the 1756-EN2TR, so this solution may not work for my current issue. I have changed the IP addresses of the ports, but I am unable to access the module info under properties due to an invalid path. Can anyone provide insights on why my PLC is unable to communicate with either port of the 1756-EN2TR Ethernet IP module?
It is beneficial to include context and screenshots when seeking assistance. Are you experiencing issues with accessing the Property in RSLinx or the Studio Project tree? If you changed the IP, what method did you use - such as the bootp-DHCP Tool? Are the ports assigned separate IPs or a single IP (DLR)?
It is possible that the specified path is attempting to access the original IP address before any configuration changes were made. If browsing the entire subnet displays devices as "unknown" or indicates IP conflicts, consider uploading screenshots for further assistance.
To begin with, an en2tr module is assigned a single IP address. Both of its ports share this IP address in a linear or ring configuration. You can configure the IP address using BootP, network settings, or by accessing the PLC online through another port to set the card's IP address. It's important to note that the IP address set in the offline module configuration may not be the same as the module's actual IP address. While they are usually set to be the same, they operate independently from each other. If you see a yellow triangle, navigate to the lower left panel in the project tree to identify the error. When online, access the module properties and view the module info tab to compare the configuration in the project with the actual module settings. This difference could be due to a version mismatch.
It's always beneficial to include context and screenshots when seeking assistance. Are you unable to pull up the Property in RSLinx or the Studio Project tree? How did you change the IP address - using a bootp-DHCP Tool? Are you assigning separate IP addresses to ports or a single IP for DLR? I didn't assign the IPs, but I will discuss it with the engineer who did. The hazard symbols can be found in the project tree. I'll attempt to provide screenshots, although I'm working on a secure lab PC, so it may not be possible. Thank you!
Robertmee explained that an EN2TR module only utilizes one IP address, with the two ports operating in a linear configuration or ring. The IP address must be configured within the module using BootP, network configuration, or by accessing the PLC online through another port. It's important to note that the IP address set in offline module configuration may not be the actual IP of the module. Although they are usually set to be the same, they are independent from each other. If encountering a yellow triangle error, expand the lower left panel in the project tree to view the error details. While online, access the module properties and navigate to the module info tab for information on any configuration discrepancies. This could potentially be caused by a version mismatch. In response, the individual stated that they would investigate the IP configuration further and consult with the previous engineer.
It sounds like your RSLogix 5000 software might not have the EDS files for the 1756-EN2TR module. These files are usually required for your PLC to recognize and communicate effectively with the hardware. I would suggest checking Rockwell Automation's website, as they have a vast library of EDS files. Also, you might want to verify the firmware versions on both the Ethernet module and PLC are compatible. An invalid path issue could be related to incorrect file or folder references as well, so try double-checking your project tree for any discrepancies. Let us know if these suggestions work!
Have you tried checking the redundancy link on your 1756-EN2TR? Sometimes, the hazards can indicate a redundancy issue that might not be addressed by eds files or IP adjustments alone. Also, try checking your RSLogix 5000 configuration for any anomalies - often it's an overlooked setting that throws off the communication. Remember, ensure that your 1756-EN2TR is showing the correct firmware version that matches up with what is in your PLC, as this is a prevalent cause for communication issues as well.
It's quite possible that the module might not have been configured properly. Make sure that the firmware version of your 1756-L73 PLC and 1756-EN2TR are compatible. Also, if it's possible, give it a try by swapping the module with another one to isolate the issue. Regarding the eds file, you should be able to download it from the manufacturer's website. If you're still unable to access the module info under properties, it sounds like it might be a browser issue. Try doing it from a different web browser or PC. Remember, the issue might be as simple as network connectivity - so ensure your ethernet cable is functioning properly.
✅ 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: Answer: Hazard symbols on the ports could indicate communication issues or configuration errors.
Answer: Answer: Try running the Electronic Data Sheet (EDS) file for the module and power cycling. Ensure correct IP addresses and configurations are set.
Answer: Answer: EDS files for Rockwell Automation products are typically available on their website or through their support services.
Answer: Answer: Invalid path errors, inaccessible module info, or incorrect configurations could prevent successful communication. Double-check settings and troubleshoot step by step.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.