I recently acquired a 5069-L330ER PLC that we are integrating into our current system to establish communication with a 1747-L551C PLC. When setting up interPLC communications, I typically include the PLC as an ethernet device in the project tree. However, I am unable to locate the 1747-L551C in my modules list, and I cannot find AOP or EDS downloads in Rockwell's download catalog. Is there a way to add the 1747-L551C to the ethernet tree, or will I need to manually input the IP address into the MSG instruction? If manual input is necessary, how can I determine the necessary prefixes for the ethernet route, such as the "2,1," in 2,1, 192.168.1.1 ?
There are a couple of methods to achieve this. One option is to incorporate the SLC5 into your I/O tree as a generic module connected to the ethernet network. Ensure to set the "Comm Format" selection to "None". This will establish the connection pathway from the 5069 through the ethernet port to the SLC5's IP address. Alternatively, you can manually input the pathway, although the specific port numbers for the 5069-L330ER are unknown to me. I speculate that they might be 2 and 3, but this is not confirmed. Ultimately, the pathway will conclude at the IP address of the SLC5. - Keith
When utilizing the I/O tree method, it is advised to not only select the Comm Format as "None", but also to prevent the connection from being established. This will prevent the CompactLogix from trying to establish a cyclic I/O connection with the SLC-500, and instead, the path will be solely used by Studio 5000 for addressing MSG instructions. Keep in mind that SLC-5/05 controllers do not support cyclic "Produced / Consumed Tags" unlike ControlLogix-family controllers. Therefore, you will need to rely on using MSG instructions with the SLC Typed Data Table Read and Write services for communication.
In utilizing the I/O tree method, it is advisable to not only configure the Comm Format as "None," but also to inhibit the connection. This will prevent the CompactLogix from attempting a cyclic I/O connection to the SLC-500, with the path solely used by Studio 5000 for addressing MSG instructions. It is important to note that SLC-5/05 controllers do not support cyclic "Produced / Consumed Tags" like ControlLogix-family controllers do. Therefore, MSG instructions must be used alongside the SLC Typed Data Table Read and Write services. Is it necessary to "inhibit module"? Yes, because even when the data connection is set to "None," the RPI remains at 0.
As far as I know, when you set the Connection Type to "None" in the CompactLogix, it still attempts to establish a connection with the field device to display any bridged connections. The SLC may decline this request, but it still consumes time and resources. By disabling the fake module, the CompactLogix will not initiate a connection at all. There is ongoing discussion on whether future users will find the fake adapter object in the I/O tree and Controller tags reassuring or perplexing. Alternatively, you can manually determine the CIP path.
On a 5069 controller, the Ethernet port is labeled as "2" in DLR/Linear mode with a single IP address. In dual-port mode, A1 corresponds to CIP Port "3" and A2 to CIP Port "4". The path from a 5069 CompactLogix to an SLC-5/05 on the same TCP/IP network is represented by two values separated by a comma: "Port Number,
If you are dealing with a complex CIP Path that includes navigating ControlLogix backplanes or ControlNet bridges, there is a cheat-sheet method you can use: Create the I/O connection, set up your MSG instruction using it, and then remove the I/O connection. This will keep the MSG instruction configured with the decoded CIP path from the I/O tree. This trick can save time and simplify your setup process for I/O connections in your industrial automation system.
The 1747-L551C belongs to the older generation of PLCs, SLC 500 series, which unfortunately may not be directly recognized by newer software that primarily focuses on the ControlLogix or CompactLogix platform. That said, there is an option you can consider. You might need to use a communication bridge such as Data Highway Plus (DH+), or Ethernet/IP. In this case, you will still have to manually input the IP addresses into the MSG instruction, but you can use RSLogix5000 or RSLinx Classic software to guide you with the prefixes. Often, the path will be something like 1,3, where '1' represents the backplane of the local Ethernet module and '3' designates the DH+ / Ethernet/IP channel. The final piece, the IP address, will be the address you assigned to your SLC 500 PLC. Remember, it might require trial and error to get it right. Good luck with your project!
Unfortunately, the 1747-L551C PLC is a SLC 5/05 series and doesn't support being added like ControlLogix or CompactLogix PLCs in the Ethernet tree. However, you're right in proceeding with using the MSG instruction for communication. As for the "2,1," it refers to the path configuration where "2" designates the Ethernet module in the local chassis and the "1" designates the port on the Ethernet module. That said, before entering the destination IP address, make sure your SLC 5/05 is able to communicate over Ethernet by confirming it's on the right subnet. Hope this helps!
The 1747-L551C is actually part of the SLC 500 series of controllers, which aren't ethernet-enabled by default. Your typical method of including the PLC as an Ethernet device in the project tree wouldn't be applicable here. Typically, for communication, you'd establish a channel through the RS-232 communication port, using either a DF1 or DH-485 protocol. If you still want to integrate it via Ethernet, you might consider adding an ENI (Ethernet Network Interface) or ENBT (Ethernet/IP 10/100 Mbps adapter) to your SLC 500. Then establishing communication with your 5069-L330ER PLC will be much smoother. Regarding IP addressing and prefix route, that will depend on the specific ENI/ENBT module you're using and your network configuration, but in most cases, the route would reflect the path through the backplane to the ethernet module, such as 1,0.
✅ 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: To establish communication between these PLCs, you may need to manually input the IP address into the MSG instruction if the 1747-L551C is not automatically detected in the modules list.
Answer: Answer: If the 1747-L551C PLC is not automatically detected, you may need to manually input the IP address into the MSG instruction for communication.
Answer: Answer: To determine the necessary prefixes, such as the "2,1," in 2,1, 192.168.1.1, you may need to refer to the specific documentation or guides for the PLC models being used.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.