VXDIAG VCX NANO ODIS V3.03 replace VAS 5054A

VXDIAG VCX NANO 5054a with ODIS v3.0.3 diagnostic scanner for Volkswagen Group VW Audi Skoda Seat Bentley Lamborghini is verified working.

Software version: ODIS V3.0.3

Top feature:
1. Replacement of OEM VAS 5054A
2. Support UDS Protocol
3.Multi-languages: English/Japanese/Portuguese/Romanian/Korean/Dutch/Polish/Turkish/Spanish/ French/Italian/Croatian/Danish/German/Swedish/Finnish/Slovenian/Czech/Russian/Greek/Chinese
4. Supported Car Models: VW, AUDI, SKODA, SEAT Bentley and Lamborghini
5. Update from download weblink
6. Support WIFI/USB Connection

VXDIAG VCX NANO 5054 VAG Computer Requirements:
Windows System Language: American English
Operating system: WIN 7 32 bits/WIN 7 64 bits
System C: // have to be NTFS format
C: // need to have at least 40GB space for installing ODIS

The Following Vehicle Bus Systems are supported:
K line (ISO9141-2)
High-speed CAN (ISO 11898-2)
Low-speed CAN (ISO 11898-3)
J1850 (SAE J1850)
UDS Protocol
PWM Protocol



VXDIAG VCX NANO GM "Manager Initialization Error"

Here is the solution to VXDIAG VCX NANO for GM/Opel GM MDI Manager Initialization Error.


I have a new VXDIAG VCX NANO for GM.
It worked yesterday with Saab 9-5 2006 (9.250 bin, with problems but it can read trouble codes and make some config).
Today I want to make a clean installation on VMware with Windows XP image.
After installation I can not run GM MDI Manager.
1. If I choose UNINSTALL in "MDI Select" I can open MDI Manager and manager can not find any interface. (drivers installed properly)
I have only "Not connected to MDI".
2. If I choose INSTALL - I have an error.
"Manager Initialization Error [Failed to initialize Vetronix Runtime rc = -5]"
Also I don`t have any table with interface option to choose at the start of Tech2Win.
(because MDI Manager didn`t find pluged any interface?)
I can find VCX Nano and configure with VX Manager.

GM MDI Manager Initialization Error

If your running in VM make sure your OS didn't connect to it via wifi etc. You want your VM to set up the drivers not the primary OS. If it did just disconnect in primary OS on network and try again in VM.

Please refer to the following:
Tech2Win Install(WIN XP or WIN 7)
1. Run Tech2Win\AutoInstall.exe, Everything will be done.
2. install VX Manager.
3. Open VX Manager, install GM Driver.

Running GDS2 with VMWare
1. Install VMware-player-6.0.6-2700073.exe
2. copy GDS2 VM to harddisk.
3. open GDS2 VM with VMware Player

Video instruction:
How to install VXDIAG VCX NANO GM GDS2

How to install VXDIAG for GM Tech2Win 11.27


VXDIAG VCX NANO for Ford and GM Feedback

Like some of you I was interested in some Allscanner products, so I went ahead and purchased 2 pieces of VXDIAG VCX NANO scanners.

-VXDIAG VCX nano for Ford & Mazda ($99)
-VXDIAG VCX nano for GM ($119)

Both without WiFi, i do not need wifi connection.

It's been over a month now that I have both adapters and had time to play around a bit with them and I must say I'm a bit more positive about the GM unit even if it's not perfect.

Now you could stop reading here or keep going and find out what's the problem with these adapters.


When I got these tools I bought from obdii365.com, I was at first impressed by the quality of the packaging. Great quality box, long USB cable (yeah I purchased the usb version). All looked very professional.


Both tools came with software CDs including GDS2, Tech2win, Mazda IDS and Ford IDS. I was pretty happy with it, they all installed flawlessly.

-Tech2win installed on host machine is forever activated (read patched),

-GDS2 works good on the provided VM

-Mazda IDS VM works good

-BUT.... Ford VM need the host machine to be in Bejing time zone in order to work.... that's a bit frustrating to me as I need to change my time zone in host machine everytime I want to use Ford IDS VM... even more, they installed a time freezing app on this one without installing the vcx nano driver so EVERYTIME you boot this VM , you need to install the vcx nano driver in order to use it... This is the downside.

still 3 out of 4 software running great, I was pleased.

THIRD: VEHICLE DIAGNOSTIC (what really matter)

Tech2WIN & GDS2

The first vehicle I hooked up was a 2004 Chevy cavalier running tech2win. The car was recognized by the software and I was able to read codes, live data, activate special functions. First good impression. 

Then I decided to push a little more and I tried reprogramming a 2006 chevy trailblazer using tis2000. All went well. 

Then I went back to the 2004 Chevy cavalier and also tried to replace and reprogram the PCM with tis2000. Failed to attempt. GM Tech2 clone does this well.

Since then, I played a bit with tech2win software (since I don't have many 2013+ GM car on hand to try GDS2) and I must admit 80% of what I tried worked. This leave me a 20% of fail attempt. If you use the tool to play with your personal car that may be fine.

Ford & Mazda IDS

First attempt, connect to a 2005 Ford Five Hundred : good, the car is recognized

Record and play back live data for ABS, PCM…tested ok

Program and Install new ECUs (PCM, ABS)…tested ok

Read and Clear DTCs…tested ok

Program New Keys for Mazda 6…tested ok

Set, adjust or remove speed governors…tested ok

DPF Regeneration…tested ok

Automatic vehicle recognition…tested ok

All other dealer functions…tested ok

Reset steering angle…tested ok

Find guided fault…tested ok

Injector Coding…tested ok


If you want to play around with your personal car, it is very good.
If you need it professionally, i prefer GM Tech II and GM MDI.


If you need to read codes and live data, very cheap and good choice.
If you need do programming, VCM2 works more for me.