Good morning! Today, I made an effort to enhance communication between several of our Programmable Logic Controllers (PLCs). Everything seemed to be working smoothly, except for a minor issue. I encountered an invalid connection fault between two PLCs and I'm struggling to identify the mistake. I updated the Ethernet configuration by adding the necessary modules. The first PLC has a 1756-L72S Safety Controller, which cannot be manually added. Instead, I included the ethernet bridge it connects to and located it from there. The second PLC is a 1756-L83E controller, and I successfully added it to the 1756-L72S. For the 1756-L72S, my tags are as follows: - Consumed: InterlockFromBBT1 (Connection: BBT_Skid:InterlockToCanFiller1) - Produced: InterlockToBBT1 And for the 1756-L83E, the tags are: - Consumed: InterlockFromCanFiller1 (Connection: Can_Filler:InterlockToBBT1) - Produced: InterlockToCanFiller1 I am receiving a module fault on the 1756-L83E with the message (Code 16#0117) Connection Request Error: Invalid connection point. Symbol: InterlockToBBT1. Despite double-checking, the setup seems correct to me. I even tried deleting the tags and starting over, but the error persists. Could it be that there is something additional I need to do to establish the connection between the 1756-L72S and the ethernet bridge for the tags to function properly? Any guidance on this matter would be greatly appreciated. Thank you.
When dealing with invalid connection points, it typically indicates a discrepancy between the tag in the Producing PLC and the data entered into the Consuming PLC. This mismatch can arise from incorrect names or data types that do not align. A common error when using Produce and Consume is failing to ensure data types match. For example, if the Produce tag is a DINT, the Consume tag must also be a DINT. Similarly, if the Produce Tag is a User-defined Data Type (UDT) or from an Add-On Instruction (AOI), the definition in the Producer must precisely match in the Consumer PLC. These issues can often cause Invalid Connection Points errors.
Operaghost explained that an Invalid Connection Point error typically occurs when the tag in the Producing PLC does not align with the information entered in the Consuming PLC. This discrepancy could result from incorrect tag names or mismatched data types. One common issue encountered with the Produce and Consume process is failing to ensure data type consistency. For instance, if the Produce tag is a DINT, the Consume tag must also be a DINT. Similarly, if the Produce Tag is a User-defined Data Type (UDT) or from an Add-On Instruction (AOI), the definitions in both the Producer and Consumer PLCs must be identical. Despite believing that all names are accurate and data types are DINT, the error persists.
To ensure proper configuration, refer to Chapter 6 pages 109-111 of the official manual available at Rockwell Automation's website. In the General tab of the L72S properties, the "Safety Network Number" (SNN) should align with the General SSN of the L72S bridged module. This is a crucial step for maintaining network consistency and safety protocol adherence.
Have you ensured that InterlockToBBT1 is properly configured as a generated tag?
Prior to adding any tags, it is essential to confirm if the L72S is properly displayed in the L83 I/O tree. Ensure that a connection is configured beforehand to avoid multiple errors. Upon inspection of the L83, verify that the L72S, L72SP, and ENxT module are all running smoothly without any yellow triangles present.
Hi there, It sounds like you've been thorough in your troubleshooting, so it's frustrating that your connection issue persists. I'd suggest looking into the error more specifically - Code 16#0117 typically points towards an issue with the 'unicast connection'. This could mean that your connection path within your controller tags might not be defined correctly, or that you are running out of connections, due to which, it may fail to reserve for the respective link. Additionally, cross-check if there are any restrictions with the quantity of unicast and multicast connections for your models. Also, you may want to check the firmware revision is the same in both PLCs and everything is updated. Lastly, double-check the PLC's IP addresses, subnet mask, and gateway which are often the culprit for such issues. Hope this helps, good luck!
Hi there! First off, kudos to you for making such a detailed effort. From your explanation, it sounds like you've put considerable thought into the setup. Regarding the 1756-L83E's fault code, it's plausible that the issue is an unrecognized tagname rather than a physical connection error. You could, therefore, try double-checking whether the InterlockToBBT1 tagname is correctly defined in your 1756-L72S program and matches exactly with your consumed tag in the 1756-L83E. Minor oversights such as typos or case sensitivity mismatch could result in such error messages. Another course of action could be to verify that your produced and consumed tags are well-configured under each controller's I/O configuration and that there aren't any hardware configuration mismatches between the PLC and the modules it's trying to communicate through the bridge. Keep at it and let us know how things go!
From your description, it seems like you've done much of your homework already. One thing you might consider is to verify the PLC firmware versions. Mismatched firmware versions between the two controllers could potentially cause this 'Invalid connection point' issue. Another thing to check is whether the consumed/produced tags are configured correctly in their respective PLCs with the correct data types. Lastly, it might be a firewall issue. If there's a firewall on the network, it might be blocking the connection between the two PLCs. Hope this helps!
Good morning! It sounds like you’ve done quite a bit of troubleshooting already. One thing to consider is ensuring that the data types for your produced and consumed tags match exactly between the two PLCs. If they’re not aligned, it can often lead to connection request errors like the one you’re seeing. Also, double-check the connection's cyclic or change-of-state settings, as discrepancies there might affect communication as well. Lastly, if you’re using any additional configuration parameters within the ethernet bridge, make sure those are set correctly. Sometimes a little detail can make a big difference! Good luck—I hope you get it sorted out soon!
Good morning! It sounds like you're already on the right track, but an invalid connection fault like that can definitely be tricky. One thing to check is whether the communication parameters like connection size and requested packet interval match on both PLCs. Also, ensure that the Ethernet bridge settings are properly configured for both PLC types, as some settings may need to be explicitly defined for safety-related controllers. Lastly, it might help to reboot the PLCs after making changes, just to refresh their connections. Keep at it; you're almost there!
✅ 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: 1. What could be causing the "Invalid connection point" error (Code 160117) between the 1756-L83E and 1756-L72S PLCs in Studio 5000? - The error could be caused by a mismatch in the tag connections or configurations between the two PLCs. Double-check the tag configurations and ensure they are correctly mapped between the PLCs.
Answer: - Start by verifying the tag configurations on both PLCs to ensure they are correctly set up to communicate with each other. Check for any inconsistencies or errors in the tag mappings.
Answer: - When working with safety controllers like the 1756-L72S, ensure that the Ethernet configuration and tag mappings are accurately set up. You may need to add the safety controller through the ethernet bridge it connects to rather than manually adding it.
Answer: - If the error persists even after reconfiguring the tags, try deleting the tags and recreating them from scratch. Ensure that the tag connections are accurately established between the Consumed and Produced tags on both PLCs.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.