Hello everyone! I am seeking some recommendations, thank you for taking the time to read =) I have two Allen Bradley PLC 5380 devices, one running on firmware version 32 and the other on version 36. I am attempting to set up produced/consumed tags through a 1783-NATR setup. The PLC_A is located on the private network with the IP address 192.168.1.2, while PLC_B is on the public network with the IP address 153.0.0.2. I have configured the translation table on the NATR to translate the IP of PLC_A to 153.0.0.3. The gateway for PLC_A is set to the IP of the NATR on the private network. I have added PLC_A to the I/O Tree of PLC_A using the translated IP from the NAT, and I have added PLC_B to the I/O Tree of PLC_A using its original IP from the public network. There is an "Advanced" menu available for configuring the ethernet address, especially useful for NAT devices, which I have not been able to utilize effectively. I have ensured that the tags have the same name and UDT, which were copied and pasted from one project to another. I have also enabled the necessary settings for the produced and consumed tags. The results indicate that PLC_B is able to consume from PLC_A. However, on PLC_A, PLC_B in the I/O tree shows a fault with "16#0117 Connection Request Error: Invalid Connection Point." Despite this, I can see the information of PLC_B in the "Module Info" and "Internet Protocol" tabs, which were previously empty before the correct configuration was applied. I would appreciate any guidance or ideas you may have to resolve this issue. Thank you!
The error message "Invalid connection point" often indicates that the tag you are attempting to use has not been configured as a produced tag or does not exist. It is important to verify the correct spelling of the tag on both ends and ensure that it has been properly set up as a produced tag. Double-checking these details can help resolve the issue and establish a successful connection.
It is essential to verify the firmware compatibility, as we encountered an issue requiring a processor upgrade to enable smooth data exchange between two firmware versions. Although the specifics escape me currently, we were able to resolve the issue by referring to a relevant technote. This underscores the importance of keeping firmware updated for seamless operations.
Hey there! It seems like you have done a lot of troubleshooting already. While I am not an expert at this, I presume this might be a routing issue. Double-check the NATR configuration, ensuring the correct port forwarding, considering NATR is notorious for causing connection issues. You could also try resetting the PLCs or even updating the firmware, in case this issue is a firmware bug. Another option might be to try giving both PLCs static IP addresses if you haven’t done so already. Also, check if you have an option to manually set the connection point in the "Advanced" settings of the ethernet address configuration, as the error indicates an "Invalid Connection Point." Just throwing some ideas out there, hope something clicks and your issue gets resolved soon!
It seems like you have done a lot of groundwork. Good job! However, considering the error "16#0117 Connection Request Error: Invalid Connection Point", it seems like there could be an issue with the setup of your connections. You might want to double-check your setup, especially the path information on the produced/consumed tags. Remember the setup should resemble something like this: LocalENB, 2, ip_address, 1, 0 on the producing side and LocalENB, 2, ip_address, 1 on the consuming side. Additionally, when using the NATR, you should use the translated address while setting up your paths. Just a thought!
✅ 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: - To set up produced/consumed tags with Allen Bradley PLC 5380 using 1783-NATR, ensure that you have the correct firmware versions on your devices, configure the translation table on the NATR, add the devices to the I/O Tree with the appropriate IP addresses, and properly configure the ethernet addresses.
Answer: - The "160117 Connection Request Error: Invalid Connection Point" fault on PLC_A could be due to incorrect configuration settings, mismatched tags, or issues with the network setup. Double-check the settings, ensure tags have the same name and UDT, and verify the network configurations to troubleshoot this issue.
Answer: - To resolve the issue of PLC_B consuming from PLC_A despite the fault on PLC_A, review the configuration settings, ensure proper tag matching, check network configurations, and troubleshoot any potential issues with the setup. You may also need to verify the translation table and gateway settings on the NATR for correct communication.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.