VXDIAG NANO Software
I have a laptop with 5 VM's running multiple versions of windows with both a clone MDI and the nano,
Lets look at the com ports and see if it is seeing the nano like Bronxtech mentioned.
look in device manager at the com ports and USB controllers prior to plugging in the nano then plug it in and watch for changes.
under USB controllers mine shows up as USB Serial Converter, manufactured by FTDI with driver version 2.12.36.4
under Ports it shows up as USB Serial Port (COM7) with port settings at 9600 BPS, data bits at 8, parity at none, stop bits at 1 and flow control at none
under advance settings under miscellaneous options Serial Enumerator is checked with everything else not selected.
Neal
Lets look at the com ports and see if it is seeing the nano like Bronxtech mentioned.
look in device manager at the com ports and USB controllers prior to plugging in the nano then plug it in and watch for changes.
under USB controllers mine shows up as USB Serial Converter, manufactured by FTDI with driver version 2.12.36.4
under Ports it shows up as USB Serial Port (COM7) with port settings at 9600 BPS, data bits at 8, parity at none, stop bits at 1 and flow control at none
under advance settings under miscellaneous options Serial Enumerator is checked with everything else not selected.
Neal
the laptop i got tech2win running on has windows 10 pro as well.....32bit......the laptop also says USB com port 3...it all works fine
i think the issue with the surface is they all have a usb-c port...and only 1 port and the tech2win software when it loads it also loads a usb driver...i think the driver that is with the tech2win software is not compatible with the surface drivers...i have even tried to load different drivers in the surface in the usb port with no luck....now the surface will load and run GDS with no issues....it even see's the nano in the gds software so it's down to a glitch in the tech2win software that needs some sort of tweak to make it work
i think the issue with the surface is they all have a usb-c port...and only 1 port and the tech2win software when it loads it also loads a usb driver...i think the driver that is with the tech2win software is not compatible with the surface drivers...i have even tried to load different drivers in the surface in the usb port with no luck....now the surface will load and run GDS with no issues....it even see's the nano in the gds software so it's down to a glitch in the tech2win software that needs some sort of tweak to make it work
I found this on the subject, not sure if you seen this one;Here’s the VXDIAG VCX NANO GM GDS2/Tech2Win working experience on Surface Pro (Windows 10) tablet:
“I tried on three of my Surface Pro 2017 models (Windows 10 Pro) Everything would work except the Tech 2 software. CANDI not connected. Not matter what I tried. When launching Tech2 the popup to choose connection to the MDI wasn’t appearing. I looked everywhere for the usb drivers with no luck.
After messing around a couple days with it, I got it to work with another laptop running Windows 10 Pro.
I think the problem is that the Surface Pro runs a usb 3.0 port and the other laptop has a 2.0 port. So if you only have a 3.0 port you may run into issues. A possible workaround would be a usb port splitter that supports usb 2.0. I haven’t tried this because I didn’t have one on hand.
Are you using a usb 2.0 adapter to go from the usb c connection?
Neal
“I tried on three of my Surface Pro 2017 models (Windows 10 Pro) Everything would work except the Tech 2 software. CANDI not connected. Not matter what I tried. When launching Tech2 the popup to choose connection to the MDI wasn’t appearing. I looked everywhere for the usb drivers with no luck.
After messing around a couple days with it, I got it to work with another laptop running Windows 10 Pro.
I think the problem is that the Surface Pro runs a usb 3.0 port and the other laptop has a 2.0 port. So if you only have a 3.0 port you may run into issues. A possible workaround would be a usb port splitter that supports usb 2.0. I haven’t tried this because I didn’t have one on hand.
Are you using a usb 2.0 adapter to go from the usb c connection?
Neal


