A setup is being attempted on a MicroLogix1100 to read a DINT value in a ControlLogix5561. The direction has been successfully set up for a read message in the ControlLogix program, executing every 5 seconds. However, the result of the message is an error. The error description indicates an issue with the Comms module or CIP device, showing an error code in the upper byte of MGx:y.22. In the ControlLogix program, the PLC 3,5 / SLC Mapping has been configured with File Number "10" and Name "MyDINT", a DINT[2] data type. The message instruction in the MicroLogix has been set up with specific parameters. When checking the web interface for the ControlLogix processor and enabling the message instruction from the MicroLogix, the Message Connection shows up with the Originator as the MicroLogix processor and Target as the ControlLogix processor, with an "Active" connection State. Despite this, updating the value of "MyDINT[0]" does not reflect in the L10 Data File of the MicroLogix controller. Any assistance on this issue would be highly appreciated.
To simplify the connection, consider using 16-bit Integer (N) datatypes. Set the ControlLogix tag as an INT[4] array and define the "This Controller" data table as Integer, Address N10:0, with a length of 4. The Target Device data table should be set at address N10:0. Although the MicroLogix 1100 has limited 32-bit integer support, you may be able to utilize a local data table defined as "L" data type. However, the PLC-5 Read/Write communications protocol may not support this data table type code. Experiment with SLC-500 Typed Read/Write, where the word "Typed" designates the B, N, F, etc data table types for binary, integer, and floating-point. Ensure the multi-hop section in the MicroLogix includes the destination IP and the Slot number of the ControlLogix. By default, it may enter 0 for the slot number, which is standard for 1756 ControlLogix and fixed for CompactLogix systems.
The problem I encountered was with the multi-hop setup as I forgot to include the path to slot 0. I was looking at an example that utilized the built-in Ethernet port of an L81, while I have a 1756-ENBT module in slot 1. Thank you for your assistance with this issue!
From what you're describing, it sounds like there might be an issue with the CIP routing path you've set up, which might be causing this communication error. Alternatively, the Setup in Local MSG instruction might not be properly configured. Take another look at those parameters, specifically the Destination Element and Size in particular. Also, it's good practice to check the firmware version and communication speed of both processors, ensuring they are compatible for smooth data transfer. Sometimes a minor detail can create a major roadblock.
It sounds like you've done a thorough job of setting up so far, although I'm thinking the issue might reside in the path you've established for your read message. Make sure that your CIP path is correctly set to reach your target device in the ControlLogix processor, especially if there are multiple devices on the network. Additionally, ensure that the Message Configuration in the MicroLogix controller is set to the correct data type and is referencing the correct tag name in ControlLogix. This is crucial for proper communication between the processors. You might also want to check if there's any access protection or routing issue preventing your MicroLogix from obtaining the values. Also, consider increasing the RPI if your network is heavily loaded, as the communication may not be able to keep up with the 5 second pace. Hope this helps.
It seems like you've done a solid job with your initial setup, but this issue could be related to the routing path you're using. Make sure you've set it correctly in your MicroLogix message instruction, as it doesn't sound like it's a problem with your data types or message instruction setup. Also, it might be worth checking whether the read/write permissions on the ControlLogix are properly configured for the MicroLogix to access the data. Sometimes, security settings can interfere with these sorts of communication setups. Lastly, a firmware mismatch could also cause this issue, so ensure both your ControlLogix and MicroLogix are running on compatible versions.
It sounds like you've set up everything correctly, but the communication issues can be tricky. Have you double-checked the network configuration and IP addresses on both PLCs to ensure they're on the same subnet? Sometimes the mapping of SLC data types can lead to discrepancies, so you might want to verify that the DINT data type in ControlLogix aligns with how you’re referencing it in the MicroLogix. Also, make sure that the ControlLogix is not experiencing any issues like memory corruption or a crash affecting message execution. If those all check out, you might want to check the firmware versions of both PLCs to rule out any compatibility issues. Good luck!
It sounds like you’ve set up most things correctly, but the error you’re seeing could stem from a few common issues. First, double-check the message settings in the MicroLogix; make sure the path to the ControlLogix is accurate and that the data types match up appropriately. Also, verify the permissions and make sure the ControlLogix is allowing the MicroLogix to read the specified memory location. Sometimes, even small typographical errors in file numbers or data types can lead to communication failures. If everything looks good on that front, consider looking at the network configuration – any issues with IP addresses or subnet masks could be causing the data not to update.
It sounds like you're on the right track with the setup, but have you double-checked the configuration of the Path in your message instruction on the MicroLogix? Sometimes, the connection issue can stem from an incorrect path format—for the ControlLogix, it should match the routing exactly, including the right slot number and the correct syntax for the connection type. Additionally, ensure that the ControlLogix program is properly handling the read request and that there aren't any inadvertent settings in the MSG instruction that might be limiting the data size or type it can access. It could also help to verify that the DINT is correctly defined in both the ControlLogix and MicroLogix; any mismatch there might lead to the error you're seeing. Good luck!
✅ 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: The error in the messaging connection could be due to issues with the Comms module or CIP device, as indicated by the error code in the upper byte of MGx:y.22.
Answer: Answer: To troubleshoot the error, ensure that the setup for the read message in the ControlLogix program and the parameters in the MicroLogix message instruction are correctly configured. Review the PLC 3,5 / SLC Mapping configuration and check for any discrepancies that may be causing the issue.
Answer: Answer: The issue could be related to incorrect mapping of the DINT value or data type mismatch between the ControlLogix and MicroLogix controllers. Verify that the File Number and Name configurations match between the controllers and ensure the data types are consistent.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.