When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
Thanks for the info, Dano. That's pretty much what I expected. I'll probably just buy a surplus MDI further down the road. But it'd be nice to be able to use the tool I already have. Having generic scan tools was supposed to be the whole point of J2534. Maybe I'll dig into it some more once I clear a few more projects off my plate.
@Dano523 - Got everything up and running. I noticed the VX Manager license showed an expiration of 12/31/2020. That about right?
Yea, about right, and when I was setting up Tis200 and upgraded the license for it, noticed that it was slightly longer date than the initial nano license to start with when I was setting up T2w. So got a feeling that is only upgrades the license for so long from a given date,, but if you go in later, it will further the license by the same time frame for a later date instead.
The only really downside I see, is in GDS2 for the MDI side of things, and wondering if there is going to be any updates to the cracked version. Hence in GDS2, GM global 2016.4.0 , the latest corvette is the 2016 model, with nothing listed for 2017, nor 2018 models.
With any luck, they get the on cloud version completed for GM, and it will either have the updates, or at least allow you to use the online version for the 2017 and later GM models isntead.
If you did not see the cloud version, go to VX manager, to the far right tab, and will bring you up to speed.
I got a copy of a GDS2 VM, and was able to manually load the Tactrix J2534 drivers to it. GDS2 actually allows you to select the OpenPort 2. It does warn you that this is an unsupported/unapproved driver, but everything seemed good. Unfortunately it refused to connect to my car (2014 C7). The car was in the correct ignition on / engine off mode. I tried several different modules and it was always "no communication with vehicle". I don't know if it's because of how I'm running GDS2, or if it's because the Tactrix driver doesn't support the latest J2534-1 and -2 versions. There's some device driver logging features I may fiddle with later. But it's an encouraging start.
Where did you find device explorer to open it? I have looked in the GDS2 program once opened, and have yet to find any settings there to select for the driver device.
It did it automatically. I opened GDS2, clicked the big "Diagnostics" link, and it popped that window. At the top left of the window are buttons for "disconnect" and "select device" as well. I'm on v17.0.08000.
BTW, I think the problem with the Tactrix device is only implements some of the CANbus pins. Tactrix promised a whole bunch of capability when it first came out, but they seemed to give up halfway through development. They didn't even finish some of their promised Mitsubishi support, and that was the bulk of their market along with Subaru.
It did it automatically. I opened GDS2, clicked the big "Diagnostics" link, and it popped that window. At the top left of the window are buttons for "disconnect" and "select device" as well. I'm on v17.0.08000.
BTW, I think the problem with the Tactrix device is only implements some of the CANbus pins. Tactrix promised a whole bunch of capability when it first came out, but they seemed to give up halfway through development. They didn't even finish some of their promised Mitsubishi support, and that was the bulk of their market along with Subaru.
Nope, must be your Tactrix device that is giving you the window, since all I get is the the red line going from yellow to green as it selected the MDI 22124708 all on it own isntead.
Also to point out, the cracked version that comes with the GM nano is V15.0.12600. If you need this version to try, drop me a private message and will see about getting you a copy of it.
Now if one is not getting a device that auto selects with the Nano, then click on the windows icon in VM, select control panel on the right hand side, select system, go to hardware tab, select device manager, and make sure that your nano is showing up in Ports as USB serial port (com 3). If it's not showing up in device manager, then disconnect the nano from the usb port, and reconnect it and give it a second so it shows up in the device manage as USB serial port (com 3), then close GDS2, and reopen the program; and this time is should self load in diagnostics window button when selected.
As for the problem with the Tactrix, may be a pin thing, or could just be that the VM program does not have the needed drivers instead with the V15.0.12600 version.
The Tactrix had to have come with a pass through drivers for it, so try loading that driver in the VM shell, and see if this allows the device to connect to the GDS2 software instead. Hence go to device manager in the Vm shell as pointed out above, the USB serial port (com 3) device in ports, click it, and update the driver for it with the one that comes with the Tactrix device instead (again, in the VM shell, and not in the native OS machine).
Hence VM machine only has the GM Nano driver loaded for it to start with in the VM shell, have a feeling that the driver loaded for the Nano device in the VM shell, is not the same one needed for the Tactrix device in the VM shell isntead. So by upgrading the drivers in the VM shell, may just load the needed drives in the shell for the GDS2 program to work correctly.
Note, the VM shell is not going to access the web due to that way that the VM shell is set up, so should be able to just load the Drivers on a USB thumb drive to load them into the VM shell that way.
Next, once you upgrade the the new drivers in the VM shell, make sure that the device is still on the com 3 port. If it not, then go to ports, select advance and change the device back to Com 3 in the VM shell.
Also, if you ever go to use the Tactrix with TIS200, load the above DLL over the one in folder of the write up as the pass through driver as well.
________________________________________ ____________
A little tape trick I found useful with the GM nano, since I kept disconnecting the micro USB connector to the device when pumping the brakes by hitting the cable with my foot for the T2W brake bleed procedure.
Hence it first has you pump the brakes for a few second, then has you come off the brake pedal so the ABS can drive fluid next, then you do the same thing for the remaining 3 calipers.
Hence tension the connector so it upwards against the face of the device with the cable pulled towards the pin side of the device, get a few winds of tape, then loop the cable back and add a few more winds. This will hold the Micro usb connector with it pins tight to the socket pins so your not knocking it loose with your foot when you do hit the cable, and the small loop helps so the wire does not become slack again over time.
The Tactrix had to have come with a pass through drivers for it, so try loading that driver in the VM shell, and see if this allows the device to connect to the GDS2 software instead.
The first thing I did was load the standalone Tactrix J2534 drivers into the VM via a USB/SD card. That may be why I get the additional pop up. GDS detects that there are drivers in addition to the default MDI/MDI2, and allows you to chose.
GDS successfully connects to the OpenPort 2. I can see the lights on the device blink when GDS attempts to connect to the car. It's the connection to the car itself that fails. I can't read the VIN, or communicate with any module manually. Every attempt ends with "no communication with vehicle".
It may still work with Tech2WIN, or with GDS connected to a pre-2010/Global A car, but I don't have a car I can test with.
I'm not going to worry about it too much. It'd be really nice to not need to buy another tool, but it's not a huge loss. I'll buy a VCX or a cheap MDI later.
BTW, the version I have supposedly supports a variety of 2018 cars. It's easily available if you search around for it.
I loaded V17 and installed it, it's another VM folder. After loading the VX drivers, it does work with the Nano. Can't verify everything it is supposed to do as mine is an 05, but it did pull the VIN. And it did have a lot more vehicles in the list, as well as the '17 Corvette.
I loaded V17 and installed it, it's another VM folder. After loading the VX drivers, it does work with the Nano. Can't verify everything it is supposed to do as mine is an 05, but it did pull the VIN. And it did have a lot more vehicles in the list, as well as the '17 Corvette.
You bring up a good point, and maybe if Jeff loads in the VX manager alone (not his other driver for the Tactrix), and lets the program think that its a VX nano, his Tactrix may work that way isntead.
Also, had a chance to download VM GDS2 v17, and was pretty straight forward with just having to install VM manager of that VM shell to load the needed drivers for the Nano to work. Still not getting the select window that Jeff gets, since it just loads the Nano in as a MDI device itself instead.
I tried setting up my Ford/Mazda VCX as a generic J2534 device, and it still wouldn't talk to the car. It had the same problem as the Tactrix. I'm done messing with it, because I just scored a used, genuine MDI on eBay for $99.
I've also read that AC Delco is changing to per-VIN licensing as of Feb 16th. You'd get unlimited access to SPS programming for a single VIN for 24 months, for $40. I don't know yet if that's just for SPS programming, or if that'll include GDS2 as well. Tech2WIN is supposed to change to a one-time fee, and then you have it forever. Right now it's $750/yr.
Getting cheap access to module programming updates would be huge. If they have a similarly affordable single-VIN package for GDS2, that'd get rid of all this VM nonsense and shady cracked software. I'd gladly pay a reasonable subscription fee for that.
I'd gladly pay a reasonable subscription fee for that.
So would I !! The setup I'm using now with Tech2Win and GDS2 (under VMware) is doing all I need without SPS, but that will most likely change one day as the cars age a bit.
I tried setting up my Ford/Mazda VCX as a generic J2534 device, and it still wouldn't talk to the car. It had the same problem as the Tactrix. I'm done messing with it, because I just scored a used, genuine MDI on eBay for $99.
I've also read that AC Delco is changing to per-VIN licensing as of Feb 16th. You'd get unlimited access to SPS programming for a single VIN for 24 months, for $40. I don't know yet if that's just for SPS programming, or if that'll include GDS2 as well. Tech2WIN is supposed to change to a one-time fee, and then you have it forever. Right now it's $750/yr.
Getting cheap access to module programming updates would be huge. If they have a similarly affordable single-VIN package for GDS2, that'd get rid of all this VM nonsense and shady cracked software. I'd gladly pay a reasonable subscription fee for that.
You can thank all of the GM changes to the farmers, and the battles that they where having with John Deer for new laws so they had the needed programs to work on the machines themselves. Hence like this, they where having to use hacked software to just trouble shoot the machines to start with.
Hell, $40 for two years and having access to all the firmware/upgrade firmware files at will for your car, is deal no way you look at it.
The glitch is the C7 guys with the new MRC handling firmware upgrades instead.
GM does not keep these firmware files in the same location as the other firmware files on the server to select by car model/module type.
So to get the these MRC firmware upgrade files, you have to call up GM and give them your Vin number, and they will take the needed file, Vin it to only that vin number for a $350 charge, then you can now access it on the GM server (again, only by that car's Vin number alone, and the only what is going to come up to select the file to flash it in).
Hence GM has stated all along that if you tune the car (change the firmware files in any way), it will void the warranty. But if you want to tune the suspension with GM suspension new improved firmware file, they they will sell you that file for $350 a pop per car, that can be flashed in without voiding the warranty instead.
Hence lets face it, it really just a firmware upgrade for a something that they got wrong from the start, and to make each C7 vet owner have to pay $350 for the firmware upgrade, its all kinds of wrongs instead.
Its like the 2005 radio firmware upgrade they added to the vet to allow it to read MP-3 files and fix static problems, and had they charged the 2005 guys for that firmware re-flash, a lot of dealers would be hung on the spot. Hell, just think of all the firmware upgrade re-flashes on the C6's over the years, and not once has anyone been charged for the upgraded firmware files themselves to start with.
Here's the new pricing from AC Delco. Looks like the $40/VIN is just for programing. It doesn't include GDS2. The one time download for the Tech2 is just the memory card updates for the actual Tech2. It's not Tech2WIN.
Vehicle Programming Software
Includes: 24 months access to program all modules for one vehicle (VIN)
1 Vehicle $40
Tech 2 Diagnostic Software
North American version 33.004
Released Aug. 14, 2013
Here's the new pricing from AC Delco. Looks like the $40/VIN is just for programing. It doesn't include GDS2. The one time download for the Tech2 is just the memory card updates for the actual Tech2. It's not Tech2WIN.[/list]1 Year $775
So is there a "repository" of cached files for the C6 or is each VIN specific to each update?
I don't mind paying the $40 to store everything I might need for my 05, just in case. But if the files are already out there... ???
So is there a "repository" of cached files for the C6 or is each VIN specific to each update?
I don't mind paying the $40 to store everything I might need for my 05, just in case. But if the files are already out there... ???
The short version, TIS2000 (or better yet, the SDS in Tis2000), uses the car's Vin number to select the needed firmware files needed for your car modules. Hence on some of the module reflashes, it needs to registry it to the other modules, and why the SDS program is so Vin relevant. Hence take of the case of replacing the dash gauge cluster in the vet, and for full flash since it stores the Milage of the car as well, the mileage is pulled from the BCM module to be flashed into the clusters programming.
As for a repository of files in the open internet, not in a sense that they would work with Tis200g communicating with GM to pull down the correct files for your Vin modules instead.
But to back up all up, its only if you need to flash in or upgrade the module firmware, hence get the files from GM, that you need to be connected to GM in the first place.
After all these posts,,,is there a concencus on the best price/place of purchase for a full function real or clean Tech2 with 32mb card with Candi module? Anyone want to sell? Don't need 2014+
After all these posts,,,is there a concencus on the best price/place of purchase for a full function real or clean Tech2 with 32mb card with Candi module? Anyone want to sell? Don't need 2014+
If your looking for a none clone, Bosch Tech II, then GM AC/Delco is where your going to buy a new one, or find a dealer/shop that is selling off their used one instead.
New, they run about $3700, while used, you can find then for around $1,550 instead. This will get you the unit, and genuine GM software, and to connect it to GM via TIS200 to download any firmware files to flash a module, this is where you get into the subscription part.
I'm a little lost after reading a lot of the computer technical stuff in here, but I have a generic question.
This is a C6 forum, and I bought a VCX Nano GDS2 while just skimming some of this thread and also seeing a youtube video of a guy using this with a C6 to reset some things.
Now that I have some time to read this thread I'm seeing now that C6's all used tech2/tech2win/TIS2000 or whatever.
It wasn't until 2014 that Corvette was GDS2.
I saw a youtube video of a guy plugging in the VCX Nano GDS2 into his 2011 Grand Sport and was able to get into all of the menus and sub functions, but what I'm seeing in this thread is that all C6's would need TIS2000 support?
Please help me understand! Did I just waste my money?
I have a 2008 A6 and was looking to investigate some BCM/TCM faults without having to go to the dealership
Last edited by jonathans2k; Mar 2, 2018 at 03:42 PM.
The C6 uses a Tech 2 for dealer-level diagnostics. The VCX Nano you purchased comes with software called Tech2Win, which is the Tech 2 functionality running on a laptop. You do not need to have a subscription to an online service UNLESS you are flashing a module on the car which is not something often done by most DIYers.
Take a look at the software disc that came with your Nano. It will have a readme file on it, and there it will outline how to load the Tech2Win software on a Windows laptop. You will not need to install the GDS2 software for a C6 or earlier.
