I am currently in the process of establishing a connection between two 1756-L72 processors for the purpose of exchanging alarms. One processor is running on rev 26.13 while the other is on rev 32.11. They were initially on different networks but have now been linked at a central point within the control room. By adjusting the IP address, it is possible to access both processors from a single PC. To ensure they are on the same network, I added an EN2T to one of the processors and connected it to an available port on the nearby Stratix switch. While using Linx, I can observe the connection between the processors through their respective IP configurations. However, I am facing difficulties in adding them to the controller tree in Studio as they are not communicating effectively. In the 26.13 project, I encountered a problem where the revision required to add the processor to the controller tree was missing. In the 32.11 project, the processor does not appear when attempting to discover devices. It is essential to take note that both versions of the software are running on the same computer within the control room, making it a straightforward task to adjust the IP addresses for connectivity. My goal is to streamline the project path to avoid changing the IPs repeatedly in the future. If anyone has insights on what could be missing in this setup, I would greatly appreciate your input.
If you are able to successfully ping both devices using the same ethernet connection, it indicates that there is data routing between them. You should be able to manually establish the producer in the PLC's tree that is receiving the data, even if it is not an exact match in terms of PLC type or firmware. What truly matters is the structure of communication, specifically how the data is being transmitted to the PLC - whether through the CPU ports or via the network card. Browsing is not essential as this process can be carried out offline without the need for a network connection.
In terms of data routing between devices, it is crucial to ensure that both can be pinged from the same ethernet connection. Manually creating the producer in the PLC tree that is receiving the data is key, regardless of an exact match in PLC type or firmware. The focus should be on the structure of communication and how the data reaches the PLC, whether through CPU ports or a network card. Browsing is not necessary as this can be done offline with no network connection. Understanding the system setup, such as having separate software instances instead of versions through studio, is essential for successful connectivity. Connecting to the processor through administrator and Windows XP sp3 may require specific configurations, but ensuring the correct revisions and communication protocols are in place is paramount for smooth operations.
It sounds like you've done a good job trying to troubleshoot the issue so far. One thing that stands out to me is the revision disparity between the two processors. Having different revisions can sometimes complicate communication, especially when trying to add devices to the controller tree. You mention the 26.13 project missing the necessary revision - have you considered upgrading this to match the 32.11 rev? That kind of harmony might help with seamless communication. As for your objective to streamline the project path to avoid changing IPs, you might want to consider implementing a DHCP server for dynamic IP addressing, if that’s feasible in your setup. Of course, just remember to reserve the IP addresses for your PLCs to prevent them from changing. Hope this helps, and kind wishes on your project!
✅ 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: Some challenges include difficulties in adding the processors to the controller tree in Studio, communication issues between processors, missing revisions required for adding processors, and processors not appearing during device discovery.
Answer: Answer: To ensure effective communication, ensure both processors are on the same network, adjust IP addresses for connectivity, add an EN2T module to one of the processors and connect it to a Stratix switch, and verify the IP configurations using Linx.
Answer: Answer: To streamline the project path, consider running both software versions on the same computer, adjust IP addresses to establish connectivity, and troubleshoot any issues with adding processors to the controller tree or during device discovery.
Answer: Answer: Possible missing elements could include incorrect IP configurations, communication issues between processors, missing software revisions required for adding processors to the controller tree, or connectivity problems with the network setup.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.