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!
Hi there, it sounds like you're doing everything right, especially in terms of your NATR connections and tag setups. The "16#0117 Connection Request Error: Invalid Connection Point" error usually presents itself when there's a mismatch in consumption configurations. Make sure that the consumed tag on PLC_A matches the produced tag on PLC_B exactly - not just the name but also the UDT. Also, remember to ensure the "Connection Point" values for the consumed and produced tags are matching on both your devices. Another point to check is your RPI times for the produced/consumed tags, these must be identical on both PLCs. In rare cases, these issues can be firmware-related, so if everything else fails, a firmware upgrade could resolve this. Hope this helps, good luck!
It sounds like you're on the right track with your setup! The "Invalid Connection Point" error usually indicates a mismatch in the connection settings. Double-check that you've properly configured the connection parameters on both PLCs, especially the produced/consumed tag settings and the I/O configuration for PLC_B in the tree of PLC_A. Additionally, make sure that the Network Address Translation (NAT) settings are accurately forwarding the traffic, and that the connections are specified for the right types (using the correct TCP or UDP protocols). Sometimes, rebooting the PLCs after making changes can help clear up lingering issues. If you still face problems, consider looking into the connection settings, IP addresses, and ports being utilized; ensuring everything aligns could help resolve the fault. Good luck!
Hey there! It sounds like you've made some solid progress with your setup, but that connection error can be tricky. Given that PLC_B is recognizing PLC_A's information but still showing a fault, I’d suggest double-checking the connection parameters in the produced/consumed tags configuration. Sometimes, issues with the connection point can stem from mismatches in the expected and actual IP addressing or even the port assignment if you're using custom settings. Additionally, since you’re working with different firmware versions, ensure that both devices are compatible in terms of communication protocols. If all else fails, rebooting the devices and checking your NAT settings once more might help. Good luck!
Hey there! It sounds like you’ve done a thorough job with the setup, but that "Connection Request Error" can definitely be frustrating. One thing you might want to check is the configuration of the Ethernet connection settings on PLC_A for PLC_B. Make sure that the connection parameters (like the path and connection type) match exactly, including the socket settings. Sometimes, adjusting the "Advanced" settings for the NAT configuration, especially regarding connection points and timeout settings, can also help. Additionally, verify that the produced/consumed tags are fully synchronized and compatible in both PLCs regarding their Data Type IDs. Good luck, and I hope you get it sorted out soon!
It sounds like you've done quite a bit of troubleshooting already! The "Connection Request Error: Invalid Connection Point" could be related to a few things—first, double-check that the IP address in the I/O tree for PLC_B is correctly set as the one that matches its configured IP on the public network. Additionally, since you’re working across different firmware versions, make sure that there are no compatibility issues between the two PLCs regarding the produced/consumed tag setup. Sometimes, settings in the "Advanced" menu related to connection types or timeouts can also impact things like this. If possible, try rebooting both PLCs after all configurations to see if that helps clear the error. 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: - 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.