Greetings, I am currently working with a 1756-L81E PLC equipped with an EN2T module in slot1 for network communication. Additionally, there is an EEN2TR module in slot2 communicating with rack 2 1756-L81E. Following the instructions provided by Rockwell, I successfully imported and configured the Modbus Client AIO. I specifically set the .LocalSlot to 1 for the purpose of retrieving data from a Scadapack on the network to perform calculations. Upon enabling Client_01_EN, I encountered an immediate fault activation with a last error code of -8 (Create Soc Failed). The PLC I am using is operating on version 30.011. It is worth noting that we have another PLC (1769-L33ER) running the same Client AIO without any issues. The only discrepancy being that the Ethernet connection on this PLC is directly from the processor, rather than through a separate Ethernet card, and it is operating on version 33.11. I am seeking advice on any potential oversights on my end or if the issue may be related to a network firewall. Your insights are greatly appreciated. Thank you.
If you are facing uncertainties about your task involving a path, it is crucial to ensure the correct configuration of the path. Implementing a pathway through an ENxT varies significantly from a direct connection to the processor. Proper navigation through the backplane is necessary in order to establish successful communication.
Our physical network at the location is equipped with numerous devices operating on a 10.1.5.1 gateway. The PLC communicates within this network using the 1756-EN2T card in slot 1 on the gateway, which is assigned the IP address 10.1.5.10. Additionally, there is a Scadapack connected to the same gateway with the IP address 10.1.5.11. In the Client AIO configuration, the .LocalSlot is configured to 1 to specify the slot of the EN2T Ethernet card on the network. The .LocalAddress is left blank, as the processor is the 5580 model as indicated in the manual. The .DestAddress is set to 10.1.5.11 in order to retrieve information from the Scadapack. The .DestinationPort is standardized at 502 for both devices, ensuring seamless communication between them.
To ensure proper communication with the PLC, it is essential to determine the slot it is located in. This entails setting up a path from the enbts IP address, through the backplane, to the PLC processor. The connection is successful on the 1769 compact model as the IP address corresponds to the processor, utilizing the built-in port. While I am not well-versed in the scadapack AOI, in a typical message path, the format would be xxx.xxx.xxx.xxx,1,Y, with 1 indicating the backplane and Y representing the PLC slot. This information is crucial for establishing a seamless and efficient communication network within the system.
To troubleshoot error -8, start by verifying the firmware version of your EN2T module, ensuring it is either EN2T or EN2TR, not ENBT. Next, review the "Create" message configuration to identify any fault codes. Share RSlinx screenshots for further analysis. This process will help diagnose and resolve error -8 issues effectively.
It appears to be an EN2T device. Here is some information on the EN2T module and instructions on how to create a message.
Interesting situation you're in. The Rockwell PLC you're using certainly should be able to handle a Modbus AIO client. The error code you're getting indicates an issue with socket creation, which could indeed be related to network settings. I'd suggest checking if there are any restrictions in place on the PLC itself or on the network it's on, such as restrictions in the number of created sockets. You mentioned a firewall - could there be a port blocked happening in there? You might also want to double-check your .LocalSlot configuration; sometimes it could be a simple setup issue. Lastly, I'd recommend looking into a firmware update for your PLC to match the version of the processor in the other PLC you mentioned, just in case this is a compatibility issue.
Hi there, it seems you've done a thorough job checking the configuration. As per my experience, this error often arises due to IP address conflicts or issues related to the firewall blocking certain network communication. Since you mentioned the working PLC has a direct Ethernet connection, it could suggest that the EN2T card might not be properly configured or having some compatibility issue. Double-check the IP settings for your Modbus client and ensure they're consistent with your EN2T card's configuration. Also, confirm your firmware version compatibility. Additionally, you should also inspect the firewall settings; ensuring that it's not blocking any communication from your EN2T module or affecting your configuration.
✅ 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 code -8 (Create Soc Failed) could indicate issues with socket creation for communication. Possible causes could include network configuration errors, firewall settings, or compatibility issues with the firmware version of the PLC.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.