VXDIAG VCX NANO GM Windows 10 Review

VXDIAG VCX NANO GM Windows 10 Review:
The software of  VXDIAG VCX NANO includes two parts: tech2win and GDS2. 
Version of tech2win: V33.003
Version of GDS2: V2016.1.0
Recently ran into an issue where i wanted to replace my aftermarket pioneer (didn't like it and much prefer my smart phone) with a stock unit. Found a cheap OEM unit on eBay. After install, i realized that factory head units are tied to the original cars VIN. No problem, i'll pay the dealership to fix the issue. Only problem they outright say they CANNOT guarantee they can fix the locked status of my radio and i'd still have to pay. As an IT/Network technician, i couldn't imagine telling people i can't guarantee i can fix your network or pc problems, but you still owe me full price plus tax.
Enter the VXDIAG VCX Nano. I was looking into gm tech 2 clone's for the past couple weeks and stumbled onto this gem. There is very little info on this product, but i still had more faith in this thing and myself more than my own dealership so i took the plunge. For $119 on chinacardiags.com, i basically have the software version of a tech II device. I was able to unlock my radio in a matter of minutes. Have never used a real or upscale scan tool device so i can't compare but just poking through some of the menus, it looks like i can do anything a tech II can. Cool thing is that the tech2win software runs just fine on my Windows 10 64bit laptop. Would be even cooler with a surface pro or similar tablet. I'm sure there are reasons for owning an actual tech II device over just software, but i wanted to try something different out of curiosity and explore other options for those that want an even cheaper alternative.

I am impressed so far....
Good tool!
I was only speaking for the tech2win software. That i did run straight from a Windows 10 64-bit laptop. Website says that GDS2 only runs from a Windows XP/7 32-bit computer. If there is a simple GDS2 test that anyone can think of for me to try, i then confirm or deny this claim. FYI i have a windows XP, 7, 8, and 10 32 & 64 bit laptops. So i could try on any operating system.
Important tips - Tech2Win GDS2 on Windows 10
On tech2win, although the op is stating that its working in 64 bit mode, really want to go through it to double check if it needs to run in win 7 compatible mode for everything to work "correctly" instead.
Putting tech2win into win 7 compatibility mode is the way and it’s not hard to do.
Go to the start icon for tech2win, right click it and go to properties, and see if you can click the box and make it run it in win 7 mod.
If the box is grayed out and you can not do it this way, click on the windows icon, type in run in the search box, then find run program made for a previous version of windows in list it will bring out and click on that to open that program. From here, it pretty straight forward to find Tech2 win, and change tech2 win so it running in win 7 compatible mode.
As for SDS, need to see that if it has for any type of account already set up in it's memory. Hence in VM, gds2 should run fine.
I fired up the GDS2 software and that indeed runs off Windows XP. But it does come with the VM software. So far everything works under my Windows 10, but like i said the GDS2 is running in the VM software
But without a active account in SDS, it’s never going to connect to GM to pull firmware files down that way instead.
Hell who knows, and if the SDS program on the disco does not have a hidden account on it, maybe you can access GMvia the cloud software instead.

Original:VXDIAG VCX NANO GM Windows 10 Review

VXDIAG VCX Nano GM working or not

I am using patched Tech2Win, as provided on CDROM purchased with device and VXDIAG VCX Nano GM off ebay and have not been able to communicate with any modules in a 2001 Holden Vectra JS, same as Opel/Vauxhall Vectra B, with a C22SEL engine. The ECU is identified as a Simtec 56.5.

I know that the ECU and Central Door Lock Modules and Immobiliser in the vehicle are not faulty because I can successfully communicate with them using Op Com v1.45 China Clone. I can read DTCs from the ECU module and I can perform Central Door Lock function tests and read the PIDs for the Central Door Lock Module and I have successfully programmed key to immobiliser.

I also have done a successful scan of ECU and Central Door Lock and immobiliser Modules using Autel MaxiDAS DS708.

I have installed the patched Tech2Win as provided on the installation disc with the VCX Nano GM device and it shows 42 days unlocked. It is installed on a Dell Inspiron 8600 Laptop, Intel Pentium M processor 2.00GHz, 2Gig of RAM, runninng Windows XP version 2002 Service Pack 3.

I am using Holden v157 and Opel v180 bins gratefully obtained from this forum with Tech2Win to communicate with the vehicle. The Tech2Win software appears to be communicating with the VCX Nano device, indicated by the green bidirectional arrows in the lower left corner of the Tech2Win app window.

When scanning the ECU Tech2Win indicates Identification Running … with green arrows in lower left of app window, then it would change to Loss of Communications with Vehicle… Then it will change to Unkown ECU. Then it would show the Abort and ID Data select keys at lower part of App Window. If I select the ID Data button, Tech2Win App will display the 5 ID Paramaters, usually with an asterix for all ids, only one time I was able to see the correct ID parameters, even though it said Unknown ECU. If I select MDI Bosch API at the interface select window instead of MDI2 Bosch API, No Communication Message is displayed on the Tech2Win app window.

I also tried to scan the Body Module – Central Door Lock, it would show waiting for data and never establish comms with module. With green bidirectional arrows displayed on the Tech2Win app in lower left corner.

I was using firmware version 1.2.2.1 and I updated the firmware to the latest version 1.2.3.11 from the VX Manager update window, did not help. I noticed in the firmware updates descriptions in some previous firmware updates are related to Opel KW82 protocol. Opel uses KW82 protocol on pin 3 for Body System Modules such as Central Door Locking and Immobiliser and uses KW2000 protocol on pin 7 for the ECU. I know this because Op Com Device shows this when it successfully connects to those modules.

I have not tried scanning any vehicles using GDS2 also provided on the CDROM with VCX Nano GM as I have not had access to any vehicles later than 2006.

Update: I saw this: http://blog.obd2diy.fr/2017/08/09/vxdiag-vcx-nano-gm-good-or-not/
decided to have another new one from obd2diy.fr

Update: Test on a 2009 GMC Savannah full size van:

So I just tested the VXDIAG VCX NANO GM interface and Tech2win on a 2009 GMC Savannah full size van. I was able to connect, read engine data, read other modules data ( BCM ETC) with no issues. Not sure if this vehicle uses the same low speed CAN in any way. But at least I know the interface and tech2win are working together.

I have screenshots if anybody is interested.

Test on 2008 Vauxhall Vivaro 2.0:

Have Vcx Nano GM with Tech2Win for speed limiter removal on a 2008 Vauxhall Vivaro 2.0 (90bhp m9r 782): success!

  

Test on a Buick 2008 GL8 Firstland:

Buick 2008 GL8 Firstland engine: (C) 3.0L V6 LZC

Worked perfect. Both OK in ECM & TCM programming! Online!

So far, satisfied with the second one from obd2diy.fr.

 Relate Product:  

Top Tech2 Clone Diagnostic Scanner For (GM SAAB OPEL SUZUKI ISUZU) with CANDI GM Tech 2 Scanner with tis2000 USBKEY by Carton

VXDIAG VCX NANO GM from order to diagnostic tests

Order & shipping:
I ordered one direct from vxdiag vcx nano for gm/opel gds2 for $129 with shipping, item from chinacardiags.com, but it will not be shipped out until around Oct. 8th due to the Chinese National Day and many companies basically shut down for the holiday.
They are offering the special price of $99 for the USB only version and $109 for the USB/wifi version until Feb 14th. $20 shipping on top of that for either unit. They say they have a 30 day return policy with buyer responsible for shipping back to them.
I already have Tech2Win setup and Saab GlobalTIS. With any luck, I am hopeful that this will work out and be a decent and inexpensive alternative at a low cost to either a clone GM Tech 2 at around $300 or the Mongoose at $480-$490.
Install:
I have tech2win and SaabglobalTIS.
The tech2win install will run under a normal XP install and I already have a version running that has the same 42 day never expires mod.
I also already have SaabglobalTIS running as well, installed in a parallels VM on my Retina MacBook Pro. I'm hoping that all I'll really need to do is install the specific software and drivers for the VCX nano.
Configuration settings:
Some minor progress. While I have not been able to try it out in the car yet. (EDIT - This is incorrect, it does not show up in the MDI Manager)> I have been able to get the interface to show up in the MDI Manager. The solution seems to be when setting up the Saab bin you need to create a new "button" in the configuration settings and make sure the interface is set to "search" and not a com port number.
I also had to launch the J2534 configurator directly from its own .exe icon. I then found the same tab for the ALLSCANNER-VXDIAG. Not sure if this is completely needed but some more testing should determine that
I have created a separate "button" for each of our 2 Saabs- one labeled "2004 Saab" and one "2008 Saab". When launching Tech2Win now the MDI manager shows a USB device as the interface and after accepting the MDI icon on the bottom of the Tech2Win screen shows the same interface after launching.
I hope to connect to the car before I drive to work in the morning to see if I can get communication established. I feel very positive that it will work. After I get it working "hopefully" and doing a few settings changes I'll experiment with the WiFi connection method.
Test on a 2009 GMC Savannah full size van:
So I just tested the VXDIAG VCX NANO GM interface and Tech2win on a 2009 GMC Savannah full size van. I was able to connect, read engine data, read other modules data ( BCM ETC) with no issues. Not sure if this vehicle uses the same low speed CAN in any way. But at least I know the interface and tech2win are working together.
The only real fault with the interface itself is the manufacturers decision to use a micro USB connector on the unit as those are somewhat fragile. A regular full size USB "B" connector would have been a better choice considering where this unit is used and by who.
P.s. I have played a bit with SaabGlobalTIS without being connected to any car and it seems to detect the interface OK for SPS programming. Will have to be cautious with this as I don't want to brick any modules.
when launching the Saab bin file the window that pops up to select an interface is shown and the VCX interface (22122458-USB) is what is shown. The VCX does not show up in the MDI manager as you have also found. The VX Manager must be the equivalent of the MDI Manager. I think I was assuming that the popup when launching tech2win was tied to the MDI manager somehow. Opening the J2534 Configuration utility shows the tab for the "ALLscanner-VXDIAG" where as you found you can select a box to "enable" monitoring. Sorry for causing the confusion. At first I was not getting the interface to show up at all in the pop up window for interface selection and reloaded a bunch of things and it then started to work properly (detection wise anyway).
The main issue I am having with the interface on the Saab is the I-Bus error - Pin 1 missing. I will have to check the connector under the dash as sometimes it is just a bad connection that can cause this error.
Test on a 2007 Saab 93:
Attempted to make the VCX Nano GM talk to 2007 Saab 93.
VCX refused to connect to the CIM. I believe its the equivalent error to using the DrewTech with the "feature" of dropping low CAN signals enabled.
I did try some other "vehicles" from the GM NAO bin file with not much success in getting engine data etc. Kept getting a wrong vehicle detected.
I did turn on the maximum amount of logging an will be looking at that file later.
Test on 2004 9-4 convertible:
I have just retested with the following configuration on 2004 9-4 convertible with the same I-Bus errors as always. But I can get Tech2Win to launch and see the VCX Nano interface with no issues as always. I can get the OBD2 functionality to work fine (High speed bus I'm sure). The VCX.BIN is a newer version released 07212016.
Mac running a WinXP VM via Parallels 11 (I know it is a VM but it seems to be OK unlike some other VM's)
Tech2Win 2.302 (cracked)
Saab Global TIS (cracked)
VCX.BIN Ver 1.2.2.9
VCXSDK ver 1.4.1.0
GM GDS2/T2W 2.2.0 160708
So it still seems as though even with this latest update that the bus speed issue is still just that, an issue. Admittedly, Allscanner has not said that this update will cure the issue.
Test on 2008 Vauxhall Vivaro 2.0:
Have Vxdiag Vcx Nano GM with Tech2Win on another laptop for speed limiter removal on a 2008 Vauxhall Vivaro 2.0 (90bhp m9r 782): success!

Test on a Buick 2008 GL8 Firstland:
Buick 2008 GL8 Firstland engine: (C) 3.0L V6 LZC
Worked perfect. Both OK in ECM & TCM programming! Online!

So far, satisfied.
I will report more of my findings here.

This from China OBD Diagnostic Online Supplier official blog:VXDIAG VCX NANO GM from order to diagnostic tests