Mitsubishi GX Works on a VM

[Phrog]

Hello,

I have GX Works 2 installed on a VM.  I am using a USB to ethernet adapter on the PC that connects to the VM over an RDP session.  I can configure the USB to ethernet device IP, and ping the Mitsubishi Q PLC from the VM.  If I try to connect to the PLC using GX Works it moves slow, says it connects after about 20 seconds, but will not upload.  It makes me think that the software is not using the USB to ethernet device (at least initially because it say it does connect after a long delay), but the embedded one in the laptop.  

Is there any way to select which card the software driver connects to (Like AB has in RSLinx)?  

I need to use the USB to ethernet driver to forward info over RDP.

 

Thanks. 

[pcmccartney1]

What are you RDPing into?

Seems that the driver needs to be installed on that PC rather than the VM you are using.

[Phrog]

I am RDP'ng (from a laptop) into a VM (server 2012) that has the PLC software on it.  Drivers are loaded on the both.  The USB to ethernet adapter works with the software if I'm not within the VM (it's on other laptops).  The USB to ethernet adpater shows up in the VM with no conflicts or driver issues.  With the laptop RDP'ng into the VM, I am able to ping the PLC.  It doesn't appear to be the USB to ethernet adapter, or a driver issue. 

[pcmccartney1]

Forgive the stupidity of the questions.  Which end of the adapter is plugged into the PLC and the server?  What is the OS for the VM?  Is the driver enabled in the VM's Removable Devices? Is the driver installed in the base OS of the server or in the VM or both?

Edited April 1, 2019 by pcmccartney1

[Phrog]

The USB to ethernet adapter is plugged into the laptop, taking the ethernet PLC connection to USB on the laptop.  The VM OS is server 2012 R2.  Does not appear to be a driver issue as the device itself works (I can ping the PLC).  I can also use rockwell software with this same setup.  The driver is installed on both.

[pcmccartney1]

Then in the laptop that is connected to the PLC, is there any chance that something else is using that comm port, so something like RSLinx?

Please understand that different vendors softwares do work well together on the same PC.

Edited April 1, 2019 by pcmccartney1

[Phrog]

Also, it pops up when I use the Find CPU within the connection settings.

 

[pcmccartney1]

Couple more silly questions.

In the Laptop that contains the GX Works (and presumable Rockwell Softwares as well), does it have a NIC?  Can you use it rather than the USB to EtherNet adapter?

[Phrog]

No known conflicts.  RSLinx isn't running.  The USB port is functional because I can ping the PLC, and it does show up in the find CPU.  I've worked with the software a few years so I know the typical comm conflict issues and I'm not seeing those.  It crawls when I go to do a connection test, but eventually says it does connect after about 20 seconds.  When I go to upload it timesout and fails.

[Phrog]

Can't use the built in NIC because I need the port info (for the comm setup) to be forwarded over RDP.

[pcmccartney1]

One last idea, can you setup a Wifi Router and enable the laptops wifi and connect directly to the Mitsubishi PLC directly via Ethernet rather than USB to Ethernet?

other than that, I'm out of ideas.  Maybe a real MItsubishi expert has an idea.

Edited April 1, 2019 by pcmccartney1

[Phrog]

I tried the USB cable connection and it will work, but is incredibly slow (12 min before it starts to read from PLC).  Anybody have any ideas as to why GX Works has connection issues running on a VM? 

Edited April 4, 2019 by Phrog