VXDIAG VCX NANO, VCX SE, VCX Plus, VCX DoIP multi diagnostic tool software and hardware support from vxdiagshop.com
Problem:
I got a problem when installing GDS2 software for vxdiag vcx nano gm. It won’t let me select the VXDIAG device type. It says contact the device manufacturer. Any idea
Solution:
Select MDI2 device type instead of VXDIAG Allscanner to connect.
SOme third party devices had been removed from GM GDS2, i.e VXDIAG, NEXIQ.
Select MDI2 you will be ok.
https://www.vxdiagshop.com/service/cannot-select-vxdiag-allscanner-in-gds2-solution.html
Here are some suggestions or using tips on running vxdiag vcx nano gm vx manager, GDS2, tech2win software on windows 10.
1. About license and vx manager
if license is expired, before you update the licenses, update the firmware on the device. Update VX manager to 1.8.4, via the top tab far right in VXmanager/all scanner. Once VX manager is updated to 1.8.4, update the Nano firmware, update the liscences, then make sure to click on diagnostic top second from the left, go to apps, and make sure to uninstall/then reinstall Passthru, GM GDS2/T2w, and SGM RDS. Hence do this every time up update VX manager. License for nano, as well as pass through/Tech2win-GDS2/SMGRDS should be good until 2030 as well. It requires every 60 days to update the license. Normal, and just a glitch in the last few VX Manager. Make sure toggle the button to green, and once it updates firmware, will auto update the licenses and kick every thing back to 60 days again for the new count down.
As for Vx manager, it upgrades about three times a year, so make sure to check from time to time for the updates.
2. About GDS2 Tech2win tis2ooo TDS
Better open vx manager and do the above when go to use the VCX NANO each session.
As for the latest VX manager and Nano upgrades, it really about the VX version of GDS2V19 that runs on win 10 desktop, isntead of the older version that you had to run in VM instead. So ONLY in regards to GDS2V19 (that is a background thing only), it makes the Nano look like a MDI 2, so with it plugged into the laptop, when you start VX GDS2V19, it runs correctly. As for the rest of the programs like Tech2win, still select MDI1 and usb device, and in Tis2000, still use the driver you built, hence passthrou.
Note, Nano has to be plugged into the computer, before you start VX GDS2V19 or you will get an error.
The down side to this to make VX GDSv19 work in windows 10, is that when you go to run Tis2000 in VM shell, since it has to run on an older VX manager that runs in XP, you have to down grade the nano firmware back to older version with the older version of VX manager/All scanner in the VM shell (make is look like a MDI 1 again), use the nano with older firmware in the TiS2000 with the passthrou driver, then once out of VM TIS2000, upgrade the Nano’s firmware again with the latest VX manager in Win 10 again.
Simply, it is what it is, with the nano still the best thing going for tech2win,GDS2, Tis2000, as well as TDS online as well.
Note, in TDS on line, still going to use the VXdiag for the device type in that screen, not MDI2, and makes sure to download the J2534 wrapper driver when you start TDS and get the pop up. Same goes if you have a MDI 2 clone, since its really a MDI 1 clone with WiFi module soldered onto the board and still uses VxDiag device driver in TDS.
As for if you need to run TIS2000, is not longer works in a XP shell since VX manager 1.3 will not update liscences (and no later version of VX manager will work with windows XP), and need to build a VM Win 7 32 bit shell, and make sure you turn on 16 bit drivers/NTVDM in the win 7 to start with.
https://www.wintips.org/how-to-fix-n…ows-10-solved/
From here, you can built the VM Tis2000 the same way you built the XP shell, but using VM manager 1.8.4. since it will run under win7 32 bit.
Note, can not use win 7 64 bit (or any other later windows 64 bit OS), since it can not run 16 drivers of Tis2000.
Hence 64 bit OS can only step back to 32 bit driver, not 16 bit of the XP days. Also, windows 8 and up, locks some files in the OS that will not allow Tis2000 to change, so for cracked VX (NAO) Tis2000, Win 7 32bit is the ticket/replacement XP OS that works for VM Tis2000.
http://blog.vxdiagshop.com/2021/06/30/vx-manager-gds-tis2000-tech2win-tips-on-win10/
Here are some tips on setting up Jaguar Land rover SDD and Pathfinder software for VXDIAG JLR DoIP VCI (VCX SE JLR or VCX DoIP JLR).
1.Update VX Manager, VCI and DoIP firmware to latest verison, otherwise the device will report “Error License for Function JLR” and will not detect network connection.
Click icon below to directly download latest VX Manager 1.8.4
Update both VCI and DoIP firmware
2. It is recommended to install SDD and Pathfinder software separately if running Windows 10.
3. Disk C should have enough space for Pathfinder DoIP update. Otherwise will fail to update VCI.
Problem:
I downloaded newer v122 IDS software and patch for vxdiag vcx nano Ford, it failed to install and said not support. How to fix it?
Solution:
You have installed the wrong (version) of patch.
Download the new patch for IDS V122 here.
https://mega.nz/folder/OV4RRC6B#seCWP6UCzOPWEDYlQxZ1iQ
Note:
Only firmware update with vx manager only but not VCI Ford manager.
Wrong firmware update will kill the vxdiag device.
VXDIAG Benz C6 and VCX SE Benz Xentry new software 06/2021 was released in Junee 2021.
Software including:
BENZ 2021.06, xentry 29.8.2,
DTS 8.13.029
EPC/WIS
StarFinder
SDmedia
Supports Benz from year 2004-2021
VXDIAG Benz C6 Xentry Language List:
Bulgarian, Danish, Greek, Spanish, French, Italian, Korean, Polish, Romanian, Serbo-Croatian, Swedish, Chinese, Czech, German, English, Finnish, Hungarian, Japanese, Dutch, Portuguese, Slovenian, Turkish
2021.06 Xentry Software Display:
VXDIAG Multi Tool BMW new software 2021.06 is available in vxdiagshop.com.
Software including:
ISTA-D 4.28.22
ISTA-P 68.0.800
E-sys 3.35/3.34
E-sys Pro
E-SysPlus 3.7
NBT_reader
BMWAiCoder
BMW coding tool
HUTool2
INPA
NCS Expert
WinKFP
BMW ETK
KSD
CIC Reader
Ncs Dummy
BMW FSC
ISTA-D Language: English
ISTA-P language:
English, Chinese, Czech, Dutch, German, French, Greek, Indonesian, Italian, Japanese, Korean, Polish, Portuguese, Russian, Spanish, Swedish, Thai, Turkish
ISTA-D 4.28 ISTA-P 68 Software Display:
Dear Vxdiag VCX SE user: do you notice there are two new cables available: one is Type-C cable, another is OBD extension cable. Generally speaking, they are used for working together with the VXDIAG VCX SE series scanners to perform DoNET remote diagnosis.
Look at the image of Type-C cable:
Look at the image of OBD extension cable:
These 2 adapters are not necessity and not included in the package in default. Type C converter is used when your computer does not have a USB port, but with LAN Port. The Type-C converter can be used to connect to the PC with USB cable provided with the VCX SE device.
The 1.2m OBD extension cable is used to connect VCX SE interface to the car by OBD2 to achieve an extended effect.
Newer version Ford and Mazda IDS V122 has been tested and verified working with VXDIAG Scanners.
Compatible all vxdiag Ford device: vxdiag vcx nano for Ford/Mazda USB and WiFi, vxdiag vcx pro, vxdiag full , vcm2 clone (using vxdiag solution) etc
Including
FordIDS-122.01_full.exe
VCI_Software_1.0.0.10.exe
VX Manager 1.8.4.0315.exe
Including
MazdaIDS-122.00.exe
VX Manager 1.8.4.0315.exe
Free Download Ford Mazda Patch
Multi-languages: English, German, French, Italian, Dutch, Spanish, Swedish, Finnish, Danish, Norwegian, Portuguese (European) , Portuguese (Brazil)
Operating system: Windows 7, Windows 8, Windows 10
Ford IDS V122 Installation Instruction
1. Install Ford IDS-122
2. Wait for the installation of Ford IDS – 122, and restart the computer
3. Install the Ford original VCI software_ 1.0.0.10.exe
4. Install VX manager and Ford IDS driver
5. Wait for VX manager and Ford IDS driver installation to complete
6. Connect VCX device and install idspatch
7. Use idspatch to open IDs and start diagnosis.
Mazda IDS V122 Installation Instruction
1. Install mazdaids-122
2. Wait for mazdaids – 122 installation to complete and restart the computer
3. Install VX manager and Ford IDS driver
4. Wait for VX manager and Ford IDS driver installation to complete
5. Connect VCX device and install idspatch
6. Use idspatch to open IDs and start diagnosis.
Note:
1. Ford IDS requires VCI Manager driver, Mazda IDS does not.
2. Ford IDS and Mazda IDS need to be installed on separate systems.
3. Don’t install IDS on Home version windows.
Read also:
