I am utilizing a CompactLogix 1769-L32E with firmware version 20.14 and attempting to establish communication with a remote 7-segment display through ethernet using messaging commands. This setup has been successfully implemented on other machines equipped with a 1769-L30ER PLC without any issues. I exported the functioning routine and imported it into the current PLC, carefully verifying all tags to ensure the configurations match. The only modification made was adjusting the Path from "1, 0" to "LocalENB, 2, 172.23.23.171, 1, 0". The initial command executed is a DeleteAllSockets. Upon triggering it, there is an attempt for a few seconds followed by error code 16#0001 and extended error code 16#0000_0204 "Connection failure". Any suggestions for troubleshooting this issue would be greatly appreciated.
Why was the path changed? The error code suggests that a valid path to the message recipient is missing. This could be due to disconnected devices or problems with IP addresses and configuration settings.
In response to voos.charley's question about changing the path, the error code indicates that there may be an issue with the path to the message recipient due to a lack of connection between devices or problems with IP addresses and path configuration. Continuing with the current path setting of "1, 0" may result in a different error message, such as "Class or instance not supported," as newer PLCs typically support this format while older ones may require more specific information. After researching this issue extensively, I am open to recommendations for the optimal path configuration. I have been exploring various options in the last few days, but welcome any suggestions for a resolution.
I am unfamiliar with how newer PLCs handle the "1, 0" format, but if that method is effective, I believe you should try using "2, 172.23.23.171, 1, 0". Is the IP address 172.23.23.171 the designated target device for communication?
In newer PLC's, the configuration of "1, 0" may not work as expected. To establish a connection, consider using the format "2, 172.23.23.171, 1, 0" with 172.23.23.171 as the target device's IP address. Despite attempting this setup, the connection still resulted in a "Connection failure" error message.
It appears that your program is utilizing Logix Sockets, which is not supported by the L32E model. The DeleteSockets error provides a clear indication of this issue. To enable Socket functionality, you will require a 5370 or 5380 CompactLogix controller. Please note that the L32E and L35E models are older versions that do not support this feature.
It definitely sounds like you've done a thorough job of troubleshooting already. The error code you're receiving usually pertains to a problem related to the ethernet/IP routing. One area to investigate could be the network setup. Double-check all your IP addresses, subnet masks, and gateways on every device in your network— not only the 1769-L32E and the 7-segment display, but also any switches or routers in between. Ensure they're aligned and there are no IP conflicts. Furthermore, have you verified the availability of the necessary outgoing connections on your 1769-L32E? It's worth noting that this model allows a maximum of 32 ethernet connections, including explicit messaging and I/O. These are just a few extra areas to consider— I hope one of them helps out!
It sounds like you've done a thorough job checking your tags and the communication path! Since you're getting a "Connection failure" error, it might be worth double-checking the network settings for both the PLC and the 7-segment display to ensure they are on the same subnet and there are no firewall issues blocking the communication. Also, try testing the connection with a simpler command or tool like Ping to see if you can reach the display. Sometimes, even slight differences in firmware or configuration can cause unexpected issues, so if possible, verify if there are any differences in settings or versions between the two setups that might be affecting connectivity.
It sounds like you're on the right track with transferring your routine! Since you're getting a connection failure, you might want to double-check the IP address and subnet mask of your CompactLogix versus the display to make sure they're on the same network segment. Also, confirm that the remote display is configured to accept incoming connections and hasn't reached any connection limits. It could be helpful to monitor the network traffic to see if there's any response from the 7-segment display when you issue the command. Finally, ensure that the Ethernet settings in your new PLC are fully compatible with the setup from the previous machine, as sometimes slight differences in configuration can lead to communication hiccups. 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: - The error code 160001 with extended error code 160000_0204 "Connection failure" typically indicates a problem with the communication setup or network configuration. Check the IP addresses, routing, messaging commands, and firewall settings to ensure they are correctly configured.
Answer: - Start by verifying the messaging commands, IP settings, and network connections on both the PLC and the 7-segment display. Ensure that the firmware versions are compatible and that the Path parameter is correctly set. Check for any firewall restrictions or network issues that could be blocking the communication.
Answer: - The transition from one PLC model to another may require adjustments in the communication settings due to differences in hardware or firmware. Ensure that all parameters, especially the Path setting, are correctly configured for the 1769-L32E PLC to establish successful communication with the 7-segment display.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.