Our automation and controls team utilizes a virtual machine to access our software, which has proven to be efficient in most cases. However, there is a common issue where the VM may fail. When needing to connect a CompactLogix or similar device using a USB cable to check settings, RSLinx on the physical machine is necessary as the USB driver on the VM may not recognize the PLC. Despite the PLC appearing in the removable devices menu on the VM with the correct model number, the USB driver fails to connect. This issue does not occur when using RSLinx on the physical machine, where simply plugging in the USB allows for easy access to the PLC. Have you encountered this problem before in your automation setup?
In order to establish a connection, it is essential to install the RSLinx drivers on the virtual machine (VM). Additionally, assigning a USB port to the VM machine is necessary. Although it has been some time since I last utilized my VM, I have not encountered any issues with it.
After troubleshooting with Rockwell support, the issue was identified as being caused by the Virtual Backplane driver (AB_VBP-1). They recommended re-installing the driver, as it can occasionally become unresponsive. Following their advice, the issue was resolved and the system immediately resumed normal operation.
Yes, I've experienced a similar issue. On the surface, this sounds like limitations in the virtual machine’s USB passthrough functionality. While VMs are great for many applications, handling the direct hardware communications necessary for device programming is often not their forte. One possible workaround might be to use a network-based connection rather than USB, depending on your PLC model and setup, which could alleviate the dependency on the VM's USB driver stack. It's something worth testing out.
Yes, I've definitely come across this issue in my own setup. It seems to be related to how the virtual machine handles USB pass-through. While the device may be correctly identified, the VM might still fail to establish a proper connection due to potential driver mismatches or conflicts. I've found a workaround through creating a network bridge between the physical machine and the virtual environment which allows for seamless communication. Your mileage may vary, of course, but it's an alternative you might want to consider.
Yes, I've encountered a similar issue in our setup as well. I suspect the issue might lie in how the VM interfaces with your physical machine's hardware. My workaround for this was establishing a network connection to the PLC, instead of relying on the USB connection. It demands a bit more setup, but it definitely seemed more reliable in a VM environment. Also, it's worth checking the settings on your VM for USB pass-through or USB compatibility mode. These could influence how the USB connection behaves within the VM.
I can definitely relate to your situation as I've encountered similar woes in my automation setup. The VM not recognizing the USB can be frustrating. It seems like the VM isn't able to correctly pass through the USB device in some cases, which seems to be a common issue with some virtualization software. One workaround I found was to use a network connection instead of USB whenever possible. This bypasses the USB complications and lets me interface directly with the PLC. For unavoidable USB connections, having a dedicated physical machine as a backup has been my go-to. Interested to hear if others have found better solutions!
I can definitely relate to the challenges you're facing with using VMs in an automation setup. It's frustrating when the USB recognition issues pop up, especially when you have a straightforward solution on a physical machine. One thing I've found helpful is using USB over IP solutions, which can sometimes bridge that gap between VMs and physical devices. It might be worth exploring the possibility of using software like USB Network Gate to help with the connections. That way, you could potentially access the PLC directly through the VM without the usual headaches. Have you tried any workarounds like that?
I've definitely run into similar issues with VMs and USB connections in automation setups. It seems like this is a common hurdle we face with virtual environments, especially when it comes to drivers and hardware recognition. One approach I've found helpful is using USB passthrough settings in the VM, which sometimes can help the virtual machine better integrate with the USB devices. If that doesn’t work, I usually end up accessing the PLC through the physical machine when I need to make configuration changes, as you mentioned. It can be a bit of a hassle, but it’s nice to know I'm not the only one dealing with this!
✅ 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 USB driver on the virtual machine may not recognize the PLC, causing the connection to fail even though the device appears in the removable devices menu with the correct model number.
Answer: - To resolve this issue, ensure that RSLinx is installed and running on the physical machine, as the USB driver may work more effectively in that environment compared to the virtual machine.
Answer: - One workaround is to use RSLinx on the physical machine to establish the USB connection to the PLC, allowing for easy access to check settings and configurations without encountering recognition issues in the virtual machine.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.