Integrating CompactLogix 5069-L330ER with PLC-5 for IO-Link Flowmeter Communication

1. Ensure that your system has a fail-safe mechanism in place to detect a loss of connection, such as setting up a heartbeat signal and alarms for communication failures. Implement a rolling heartbeat interval from the ControlLogix (CLX) and compare it with the previous interval in the PLC5. If the interval remains static for a certain period, trigger an alarm. 2. It is crucial to pay attention to step 13, especially when transferring messages between a PLC5 and a CLX. When sending or receiving data, use a specific format such as N7:0 in the PLC5 and map it to a Logix tag in the CLX. However, it is essential to consider step 44 - avoid writing directly from one PLC to another to prevent issues like writing to incorrect addresses. Always retrieve necessary data from the remote PLC in the requesting PLC to simplify troubleshooting and prevent errors.

• 28-08-2024
• robertmee

Welcome to the PLCTalk forum community! I recommend placing your MSG instructions in the PLC-5 whenever possible. It's important to ensure that the PLC-5E has enough message control data table elements, especially since Ethernet requires double the usual amount. Additionally, it is essential to confirm that the PLC-5E has the necessary firmware versions to communicate with a ControlLogix system. You can check the firmware list on the RA Knowledgebase or perform a quick inspection of the PLC-5 physically and via the network. A Series F controller will have an RJ45 jack and be labeled as "10/100" and possibly "EtherNet/IP", indicating that it has the correct firmware. Alternatively, you can use Windows PowerShell to test a TCP/IP connection to TCP Port 44818 by entering the command "tnc -p 44818". If the controller only responds to Port 2222 and not Port 44818, it signifies that it's an older model that cannot communicate with the CompactLogix. To allow the CompactLogix to emulate PLC/SLC Data Tables, use the "Map PLC/SLC data tables" feature. Set up an array tag (INT or REAL type) and assign it a Data Table Number to simulate when receiving a Data Table Typed Read or Typed Write command.

• 29-08-2024
• Ken Roach

Hi Jake, welcome to the group! This is a great question. To transmit information like low pump flow or high water temperature, messaging between PLCs is perfectly feasible and it's been done in the industry often. However, do bear in mind it might be a tad slower than produced/consumed tags and there could be some light delays depending on the complexity of your network traffic. You can confirm message receipt with a status code generated upon message completion, the details of which are typically found in the module documentation. The "Map PLC/SLC Messages" feature in Studio 5000 usually comes into play when migrating to updated systems, or when needing to handle data efficiently with older system components, so it could be useful in your upgrade process. Lastly, direct writing to PLC-5 data tables from CompactLogix is possible, typically using the MSG instruction to send Read/Write data messages. It's not a direct apples-to-apples operation, but with some careful planning, it's quite doable. Good luck with your project!

• 03-01-2025
• Emily Davis

Welcome to the forum, Jake! Regarding your questions, yes, it is absolutely feasible to transmit critical process information through messaging. Your CompactLogix PLC can transmit these information quite reliably. As for verifying if the PLC-5 received the message, there are status tags associated with the message instruction that you can monitor to confirm successful transmission. The "Map PLC/SLC Messages" function in Studio 5000 is typically used to convert data types and structure which are not common between the two different PLC platforms, particularly if you're transferring arrays or structures. Lastly, yes, the CompactLogix can directly write to the PLC-5’s data table. With ENBT module on the PLC-5 you can setup MSG instructions to read and write data directly. You might face compatibility issues, so I would advise running a few tests to check everything. I hope this helps!

• 03-01-2025
• Ella Barnes

Hi Jake, welcome to the forum! Your project sounds quite intriguing. To answer your queries: 1. Yes, it's quite feasible to use messaging for transmitting crucial process information, but as with any data transmission, data validity checks before actioning are crucial. 2. As for receiving confirmation, the status 'EN' bit in your message instruction can be observed. If it goes high, your message was successful. If it stays low, your message wasn't successful. 3. "Map PLC/SLC Messages" is used while transitioning legacy SLC/PLC data to newer ControlLogix/CompactLogix platforms, but it might not be necessary in your case. 4. Directly writing to the PLC-5 data table is possible. The messaging instructions within the CompactLogix can allow communication with the PLC-5 and write data directly. Remember that your messaging typically takes more time than normal I/O reads between two data tables. You'll need to allocate the right amount of scan time to ensure smooth operation. Hope this helps!

• 19-02-2025
• Andrew Parker

Hello Jake, and welcome to the forum. Your project sounds interesting and is definitely feasible. To your questions, yes, you can absolutely transmit critical process information over Ethernet using messaging. As long as the PLC-5 has an Ethernet/IP module, you'll be able to send messages. For the second part, there isn't a direct way for the sending PLC to verify if the message was received. However, you can program the receiving PLC to send an acknowledgment back once it gets the message. Moving on to your third question, We typically use the "Map PLC/SLC Messages" function when we're migrating an old PLC/SLC message instruction to a newer Control/CompactLogix platform. If you're setting up a new message from a CompactLogix to a PLC-5, you don't usually need to use this setting. Lastly, yes, CompactLogix can directly write to the PLC-5 data table. The Write tag (MSG) component of RSLogix 5000 software enables CompactLogix to do so. Hope this helps and good luck with your project!

• 19-02-2025
• Michael Johnson

Hey Jake, welcome to the forum! It sounds like you've got a solid plan in place for bridging the old and new systems while addressing your immediate needs. To answer your questions: 1. Yes, it's definitely feasible to send critical process information via messaging; just make sure to format the messages correctly. 2. You can verify successful receipt by using a simple acknowledgment mechanism, like having the PLC-5 send back a confirmation message after it processes the data. 3. The "Map PLC/SLC Messages" function is useful when you want to simplify the setup by automatically defining the message parameters rather than doing it manually. 4. While CompactLogix can read from the PLC-5 data table, writing directly can get tricky. It’s best to use a messaging protocol for safe data transfer to avoid issues. Good luck with your integration—sounds like an exciting project!

• 07-03-2025
• Jacob Moore

Hey Jake, it's great to have you join the forum! Your project sounds interesting, and it’s definitely feasible to use messaging to transmit critical process information from the CompactLogix to the PLC-5. You can use the MSG instruction to send data like low pump flow or high temperature—just make sure to configure your message correctly. To verify successful receipt, you can use a bit in the PLC-5 to confirm the status of the incoming message. The “Map PLC/SLC Messages” function is useful when you want to simplify your communication setup by defining how tags map to message instructions. Unfortunately, direct writes to the PLC-5 data table can be tricky since they're different architecture, but sending data through a message is the way to go. Good luck with your integration!

• 21-04-2025
• Lisa Adams