How to Establish Communication between PLC5 and CompactLogix using Ethernet Interface AB-1761-NET-ENIW

Question:

Hello experts, I am seeking assistance in establishing communication between a PLC5 and a CompactLogix PLC. Would it be feasible to utilize the Ethernet Interface (AB -1761-NET-ENIW) for this purpose? Thank you.

Top Replies

Using the NET-ENI with an ethernet switch is essential when connecting it to the CompactLogix PLC system. In my experience, I have found that the NET-ENI does not function properly without the use of an ethernet switch. Despite its discontinuation many years ago, I continue to use the NET-ENI due to the necessity of replacing old equipment and salvaging them before disposal. What is the significance of utilizing the NET-ENI in your setup?

In order for the PLC5 to communicate with the Compact, it is essential to properly map an array of the right data type. N files in PLC5 are of type INT, while F files represent Reals and ST files are used for strings. PLC5 does not support BOOL type; instead, it uses B files which operate similarly to N files but with bit-level addressing.

To establish a connection between the Net-ENI and PLC-5, you will need to create a serial cable. Ensure to configure the PLC-5 serial port for CRC error checking as the Net-ENI does not support the default BCC error checking. The recommended settings are 19200 baud rate, 8 data bits, no parity, 1 stop bit, and DF1 Full Duplex protocol. Utilize a CompactLogix MSG instruction with PLC-5 Typed Read and Typed Writes to access the B, N, and F data tables in the PLC-5.

Additionally, the PLC-5, SLC-500, and ControlLogix systems all feature "DTE" type serial ports. To connect the DB25F port on the PLC-5 to a DB9F connector for the 1761-CBL-PM02 cable, you will require a standard 25/9 converter. Opt for a low-profile converter for convenience. A null-modem converter or one with built-in handshaking is not necessary for this setup.

When integrating a PLC5 with a CompactLogix for data transmission, it is essential to map an array of the correct type. Remember, N files are of the INT type, F files are Reals, and ST files are strings. While PLC5 does not have a BOOL type, it utilizes B files with bit-level addressing, similar to N files. To map an array effectively, consider using RSLogix 5 or RSLogix 5000. If you are unsure about how to proceed, there are sample configurations available to guide beginners through the process. By establishing proper data transmission between PLC 5 and CompactLogix, you can optimize communication efficiency.

Yes, it's absolutely feasible to use the Ethernet interface (AB-1761-NET-ENIW) to establish communication between a PLC 5 and a CompactLogix PLC. However, please keep in mind that the entire process is not straightforward but requires setting up explicit messaging between the two. It can be a little tricky if you're not familiar with it. I'd recommend checking out some online tutorials or manuals to guide you through, or you might want to consider seeking professional assistance if the process becomes too complicated. Be sure to maintain a backup of your existing PLC data before proceeding, to prevent any potential losses. Good luck!

Absolutely, you can utilize the Ethernet interface (AB -1761-NET-ENIW) for this purpose. However, the process might be quite involved. You would essentially have to create messages in both the PLC5 and CompactLogix for the two to communicate. But remember, a key aspect is to maintain the same data mapping on each side. A thing to note is in overdoing this, you may violate best practices for PLC design by adding complexity and potentially slowing down your scan times. I'd recommend a PLC upgrade if it falls within your budget.

Absolutely, using the AB 1761-NET-ENIW is a viable option for facilitating communication between a PLC5 and a CompactLogix PLC. It can serve as a bridge since the PLC5 typically communicates over DH+ while the CompactLogix uses Ethernet/IP. Just ensure you properly configure the ENIW for protocol translation, and keep in mind that you might need to deal with some latency or data mapping depending on your specific application. Good luck with your project!

Absolutely, using the 1761-NET-ENIW can work for communication between a PLC5 and a CompactLogix PLC, as it allows for Ethernet connectivity with legacy systems. Just make sure to set up the appropriate protocols and address settings on both sides. Also, keep in mind that while this bridge works great, you might face some limitations in terms of speed and data handling compared to fully integrated systems, so testing your configuration thoroughly will be key. Good luck!

Yes, using the 1761-NET-ENIW for communication between a PLC5 and a CompactLogix is definitely feasible! This interface allows for Ethernet/IP connectivity, which can bridge the older PLC5 to the more modern CompactLogix. Just make sure to properly configure the communicating protocols and data mappings, as the differences in architecture can sometimes complicate the integration. Your network setup and application logic will play a crucial role in ensuring smooth communication. Good luck!

More Replies →

Streamline Your Asset Management
See How Oxmaint Works!!

✅   Work Order Management

✅   Asset Tracking

✅   Preventive Maintenance

✅   Inspection Report

We have received your information. We will share Schedule Demo details on your Mail Id.

To add a comment, please sign in or register if you haven't already..   

Frequently Asked Questions (FAQ)

FAQ: FAQs:

Answer: 1. Can the Ethernet Interface AB-1761-NET-ENIW be used to establish communication between a PLC5 and a CompactLogix PLC? - Yes, it is feasible to utilize the Ethernet Interface AB-1761-NET-ENIW for establishing communication between a PLC5 and a CompactLogix PLC.

FAQ: 2. What are the steps involved in setting up communication between a PLC5 and CompactLogix using the AB-1761-NET-ENIW Ethernet Interface?

Answer: - The specific steps may vary, but generally, you would need to configure the IP addresses, set up the communication parameters in the programming software, and establish the connection between the two PLCs.

FAQ: 3. Are there any compatibility issues or considerations to keep in mind when using the AB-1761-NET-ENIW Ethernet Interface for communication between PLC5 and CompactLogix?

Answer: - It is important to ensure that both PLCs support Ethernet communication and that the communication settings (such as IP addresses, communication protocols) are properly configured to enable successful data exchange.

FAQ: 4. Are there any limitations or performance considerations to be aware of when using the AB-1761-NET-ENIW for communication between PLC5 and CompactLogix?

Answer: - Depending on the specific application and data transfer requirements, it is advisable to consider factors such as network bandwidth, data traffic, and the overall performance capabilities of the PLCs involved in the communication setup.

Ready to Simplify Maintenance?

Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.

Request Demo  â†’