Is there anyone who can help me understand why I'm able to ping a node (specifically an HMI) but RSLogix 5000 or RS Linx is unable to recognize it when I use the Ethernet/IP driver? My Rockwell software is currently running in a virtual machine with the network adapter configured to NAT. This setup typically functions well for me, but I'm unsure about what might have changed recently. I appreciate any guidance or troubleshooting tips. Thank you! - Gareth
Manually configure the Ethernet driver by adding the device's IP address in Linux.
I gave that a try, and it actually worked! However, I find myself even more confused now. Thank you for your response!
I’m not entirely sure why it functions this way, but I believe the more experienced users here might have insights. I simply attribute it to one of Rockwell's unique 'features' that adds character to the system.
Gareth_mint shared, "I attempted that solution, and it worked for me, but it's left me even more puzzled! Thank you for your response." To elaborate, if you're using the EtherNet/IP driver with RSLinx and receive no results, but the Ethernet RSLinx driver connects successfully (similar to the standard CMD 'Ping'), this issue is likely due to specific network topology configurations. It is probable that the Network Interface Card (NIC) on your PC is not on the same subnet as the intended device. It’s important to note that EtherNet/IP RSLinx drivers cannot cross different network segments (subnets), even if both the PC and network switches are properly configured to do so. Therefore, when your target devices are situated on network segments different from the subnet connected to your PC's NIC, utilizing the Ethernet RSLinx driver is essential for establishing the desired connectivity.
dmargineau makes a valid point. Additionally, the issue you're experiencing with your virtual machine (VM) stems from your current use of NAT mode. To resolve this, consider switching your VM's network interface card (NIC) to bridged mode. Once you've done that, configure your VM's IP address to match the same network as your Human-Machine Interface (HMI). By making these adjustments, you will be able to utilize the Ethernet/IP driver as intended.
Hey Gareth, it sounds like you're dealing with a tricky situation! Since you're able to ping the HMI, it indicates that there's basic network connectivity, but the issue with RSLogix 5000 and RS Linx might stem from the NAT configuration. Sometimes NAT can complicate how devices are recognized on the network, as it may prevent certain broadcast communications necessary for device discovery. I’d recommend checking if your virtual machine’s network settings can be adjusted to a bridged connection, allowing it to behave like any other device on the same subnet. Also, make sure to verify that the appropriate ports are open for RS Linx to communicate with your HMI. Good luck!
Hey Gareth, it sounds like you're facing a tricky issue! Given that you can ping the HMI but not see it in RSLogix 5000 or RS Linx, I'd start by checking the network settings in your virtual machine. Sometimes, NAT can prevent certain devices from being discovered over the network. You might want to try switching to bridged mode, which can help with direct communication. Also, double-check that the IP address of the HMI is in the same subnet as your VM to rule out any routing issues. Lastly, make sure that any firewalls or antivirus software are not blocking the traffic. 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.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.