After several more hours of messing with this, I have been able to run GDS2 and communicate with a 2014 vehicle, but still no luck with tech2win. I never get the pop up to " select vehicle communication interface" and therefore tech2win opens without seeing a candi module... Therefore I get the 'mdi is not connected to tech2win' message...

​​​​​ I have installed and uninstalled and reinstalled in all of the orders people have recommended and even the very different order that was recommended on the VXdiag website. Clearly I'm missing something.

 

Here's the section that seems to be falling down:

..."As for tech2win, ... once you click the normal tech2win icon, select North America in the first screen, MDI1 in the second screen, then usb device in the third screen. If you do not get the third screen..."

After clicking 'north america' it simply launches the tech2 emulator, I never get the opportunity to select which device, which is clearly an important part of this setup

 

Apparently this is NOT an isolated incident:
http://blog.vxdiagshop.com/2020/08/0...-pro-3-0-port/

Note that I'm also using a surface pro, like the guy in the link above

I just tried his on an older Win 10 Pro Thinkpad and had no issues whatsoever installing. Operates as advertised. I considered whether this was due to the USB 3 vs 2, but the surface still acts the same way over wifi connection to the nano.

 

So you were able to get it working on the second machine? I went back thru the comments here and found what I used:
1. Load the device
2. Execute MDI.exe (THIS is what fixed my issue)
3. Install VXmanager
4. Execute auto install with VXmanager running.
Once I ran that first then followed Dano's recommendation to run autoinstall.exe then install the other programs thru VX Manager, it all worked perfect.

 

Yes, worked just fine the first shot on my Win10 pro Thinkpad, WITH defender disabled *grumble*.

I followed this instruction: https://www.vxdiagshop.com/upload/pr...5159427787.pdf

in summary:
1. GDS2AutoInstall
2. Tech2Win Autoinstall
3. install VXMANAGER
4. open VXmanager
4.1. Install (update) passthru app
4.2. Install (update) GDS2/T2W app
4.3. Upgrade firmware
4.4. Upgrade License

When you launch GDS2, click 'MDI2'
When you launch Tech2Win, select 'GM - MDI,'

 

Yep, slight changes in the Driver for the Nano in GDS2V19, so you have to select MDI2 when running GDS2 on inital set up the first time, and select MD1 each time after north america, when your running Tech2win isntead.

Also, before you install Tech2 win on the machine, get the VX manager installed, click on firmware and liscence icons in VX manger with the nano hooked to machine to get it up and running in VX manager, and leave VX manager open and the Nana connected to the machine when you run the Autoinstall .exe to install Tech2 win to start with, and once it has been loaded, go back into VX manager to install passthrou/GDS@-Tech2win/RDS. Hence they will not install into VX manager until after you have installed Tech2win in the first place.


And lastly, back to VX manager when you are installing it to begin with, if you do get a pop up from defender that is blocking something during the install, then click on the defender pop up, click on the file it just block, and allow it to run in windows through defender. At this point that the file can run through defender, do another install of VX manger to get it installed correctly to begin with.

 

I'm going to update this here because it may be useful. I just installed it and got it running on Windows 11 with no issues.

1. Plugged in the device to the computer.
2. Did the Auto-Install
3. Ran the VXDiag Install
4. Updated everything as necessary to the latest.

Just got done reprogramming the BPP Switch on a 2008 Buick Lucerne without issue.

 

OK so my Nano turned up a few days back and I have got round to having a go at setting it up. I'm ordinarily a Mac user but do have an old win10 64 bit machine I use for HP Tuners. I've learnt so much going through all the threads on here and elsewhere but seem a bit puzzled by the next bit..

I have impressed myself by getting VX up and running, along with T2W and today got hooked up to the car and had a look through some of the menus and read some codes.

My problem is I have an 05 with the dreaded Column lock fail, i'm trying to get to a point that I can flash in the new BCM software to remove the issue completely. I fitted an emulator and removed the physical lock pin about 5 years ago.

Am I right in saying that I need to access SPS through TIS2000 and not GDS? Does it have to be TIS2000?

If so, am I right in saying that I will not be able to install TIS2000 on my current machine and will need to find a 32bit win 7 machine (and install everything again!!) Is it TIS2000 that requires an XP install in VMWare?

Am I also right in saying that I am going to struggle to access SPS via TIS2000 from my location here in the UK?

I really need to work through this problem as the only dealer here that can help is admitting to being very unconfident in doing this! They bricked a car recently doing similar and did not fill me with confidence on the phone!

 

The Firmware version to delete the SCLM out of the BCM is not in Tis2000, and you have to use TDS instead. Hence Tis2000 has all the other firmware that you will needed for the car to reflash pretty much everything else up to 2009 on most GM cars (up to 2008 for the C6), but is does not have the latest BCM firmware version to flash out the SCLM, since it's that file just came out a few years ago.

So AC Delco for $40 for 24 months is the subscription you want.
Note, really a true 24 months version, but allows you to firmware flash each module once only in time period, up to 24 months instead. So on that note, TDS for this flash, while every other module, want to be using TIS2000 that will do unlimited amounts of flashes instead.

https://www.acdelcotds.com/subscriptions

Once you have the subscription paid for, going to log into your account, and go to use SPS.
The first time, it will load software on to your machine, you allow Java to connect, when you go back into SPS again, going to first get a pop up that is wants you to load Tech2 driver, MDI drivers, and J2534 wrapper driver. click and down load all of these.

Now in device driver, going to use VXDiag, which will be the driver for the Nano to run TDS, and with the Nano hooked up to your car, allow it to scan to pull the Vin number of your car (will lock your account to this vin number, so double check to make sure it right). In firmware method, your going to select replace and flash, over just update firmware, since this method will always make sure all the modules in the car are on the correct Vin security code number.

From here as you move farther into SPS, and comes to the module list, select BCM, and under its firmware, will just have the single firmware file to select to flash into the BCM normal method (not VIC). The flash will walk you through doing it, such as pulling the radio fuse before you flash, and once you have re-flashed the BCM with that firmware file, SCLM system will be flashed out of the BCM.

 

Dano,

Thanks for the response. As per my thread in scan/tune I actually managed to resolve the column lock issue by using Techline (SPS2) having stumbled across that on my searches. Over here in the UK the subscriptions are a little different but fellow Euro users should note the option for 1 hour for 4 euros allowed me more than enough time to download all the software as you outline above and get connected and flash the lock out of use - forever! I am currently drinking a bottle of beer that cost more than that so it is basically free...

With regards TIS2000...

I know all the info is probably on here somewhere but my confusion is as follows - what spec machine do I need for this should I want to use it in future? Is this the software that needs to be run under XP in a VM? Is this what I run the T2W software in pass thru mode?

Thanks man, your contributions are awesome

 

Down and dirty, you can run Tis2000 on windows 7 32 bit, with 16 bit suport turned on in windows.
Note, has to be 32 bit, since 64 bit win 7 does not have 16 bit driver suport/
As older than Win 7, problem will be the VX nano drivers that will not work with anything older instead.
As for win 10 and later (32 and 64 bit versions), it's pretty much a no go as well.

So solution, build a Windows 7 32 bit shell via VMWare, turn on 16 bit suport in that shell for windows, and you load it to that, run it under Windows 10 or later using VMWare or VM player.

As for Vm ware or VM player, laptop needs have a multi-core processor, since it needs a core to run the main OS, as well as a second core on the processor to run the VM shell at the same time.

 

Thanks for taking the time to give me the explanation, it helps very much!!!

 

No worries, and if you where not across the pound (or I was over on your side/ not in the states currently) that USPS Custom charges would not kill me tying to send you a Thumb drive in the mail, have working copies of TIS2000 already built in VM shells on USB thumb drives, that I could send you one, that you can run it using VM player on your machine.

And when I say built/plug and play ready, trust me, can use just about any device with it, since it's loaded with every driver known to man kind, over just the VX GM nano.
Want to use a Clone tech II, the usb cable driver is already loaded in the shell.
What to be different and use a clone GM mongoose, all the needed drivers and software is are already loaded in the shell as well.

Hence had some free time when someone sent me a Clone GM Mongoose (simple J2534 device) when they switched over to a VX GM nano( since they could not get it to work with the VX software), and the VX Tech2win and VX GDS2 loaded in the shell works with a GM clone mongoose since I loaded in those needed drivers in the shell on top of the VX drivers to bring all that together.
Note, Go with VX Gm Nano to begin with, over clone mongoose, since you have to get the VX software up and running with the VX gm Nano first, before you add in the extra mongoose software and drivers to make the mongoose work with the VX software in the end.

 

Sorry for bringing up this post. But I am new to all this and I’ve followed the instructions to setting this up and I’m having an issue in the passthru menus. GM Tech 2 is not appearing in the interface options. I’ve reinstalled many times many different ways and It is still not working. Could anyone help me out with this?

 

What program are you running?.

 

Dano523....i am getting the exact same 3 options on my interface as well....i am only after the tech2win part of the software but have down loaded multiple times and installed but it never is an option ....so when i start the tech2win it just goes right into the program and never ask's for the "mdi" option or the "usb nano" option
what am i missing?

 

i guess the tech2win software is not seeing anything from the VX manager?

 

Load VX manager first, then click on liscence and fimware to update the nano in VX manager with Nano plugged into the machine.


Now leave the nano plugged in, VX manager still open, and now install Tech2win. Hence VX manager with nano attached has to be open, so the Tech2 win program will be able to over write a few files in the VX manager program. Also, the quick start T2w icon on the desk top, delete it, since your never going to use it.

Now go back into VX manager, go to apps, and install pass through, T2w/gds, and SGM RDS.

Now do shut down the laptop and restart it. Now when you click on the tech2win on desktop, should get a pop up, select north america, next pop up, select MDI 1, then last pop up window, select the usb device in that list.

Now tech2wiin should finish loading to get the blue tech2win screen.

If no pop ups, then you installed wrong, and if you have xv manager seeing the nano, its firmware is updated, and liscence is currrently, then reinistall Tech2win again, and make sure Nano is plugged in, and VX manager is open.

 

Dano523
i believe i now know what the problem is....i have been trying to install this on a surface pro 5 for what seems like 100 times.....it always never finds the nano in the tech2win program.....i think there is some sort of issue with the com port configuration on the surface that wont allow it ????

i dug out an old dinosaur laptop i have and loaded it all on there and boom first time it's up and working.....thanks for all the help but i sure wish i could find a way to install it on the surface pro... the surface is a lot smaller....if anyone ever figures out how to make that work on one i'd sure be interested in how it was achieved

thank you again for the help and direction!!!

 

Your surface pro is a 64bit OS. Last i checked from VX the software and device is not compatible with 64bit OS. I tried everything and cant get it to work on 64bit OS.