#gm mdi2

[myemilyzhang]

How to select/change diagnostic tool in TIS2Web for MDI2

GM has recently updated the Service Programming System (SPS) with a new method of selecting a J2534 tool in TIS2Web.

A J2534 tool (GM MDI, GM MDI 2, or other J2534 device) is required in order to manage the transfer of data between a vehicle’s onboard network and a service technician’s PC. J2534 is an interface standard designed by the Society of Automotive Engineers (SAE) and mandated by the US Environmental Protection Agency (EPA) for vehicle Electronic Control Unit (ECU) reprogramming.

Selecting a Diagnostic Tool

From the Select Diagnostic Tool and Programming Process screen, select the J2534 Tool option for all J2534 tools (MDI, MDI 2, or other J2534 device).

The first time the J2534 Tool option is selected, a screen will appear asking the user to select a device type, such as the MDI, MDI 2 or other tool.

Changing a Diagnostic Tool Selection Once a J2534 tool has been selected, reprogramming of a control module can be completed. If the J2534 tool selection needs to be changed, there is now a check box that must be selected next to the Select Programming Process menu on the Select Diagnostic Tool and Programming Process screen. (Fig. 10) Select the Reset J2534 Tool box and then select Next to set up a different J2534 tool.

– Thanks to Chris Henley loading..

[myemilyzhang]

2020 GM MDI2 vs GM MDI diagnostic programming tool

2020 GM MDI2 shares the same functions and vehicle coverage as GM MDI. GM MDI 2 features in a light blue color shell and brand-new shape, GM MDI features in dark blue shell.

2020 GM MDI2 is optional with Wifi version and USB version (means wired network connection is not allowed) GM MDI is only optional with Wifi version.

Image 1: 2019 GM MDI2 in light blue (WIFI or USB options)

Image 2: GM MDI in dark blue.

Similarities: 1. Both GM MDI2 and MDI are compatible with GDS2 Tech2Win

Software version: 2019.3 OS: WIN7 64bit Computer: the year after 2008, 4GB RAM Pros: gds2 software needs no activation The method to use: Insert the HDD with GM MDI gds2 software into your computer; the software can be used directly with the GM MDI scanner.

Tech2win is the program that works just like a Tech II, but the program running on a laptop for the MDI (clone MDI device which the Nano is). GDS2 is the program for the C7, like the tech II and tech2win with midi is for the C6 instead. On the VM GDS 2, you don’t need an account with GM to use it, short of needing to do SPS programming, which you will need a TDS SPS subscription instead ($40 for 2 years per car).

So the low down for most laptops, Wants to be running in win 10 for TDS SPS programming. Needs to be running a multi-core chip in win 7 or above to run VM player for VM GDS2. Need to be running in Win 7 native (32 or 64 bit) to run Tech2win (will not work in a VM shell).

2. Both GM MDI2 and MDI have the same capabilities Full dealer level diagnostics and programming for all Vauxhall /Opel 16 pin vehicles from 1996 to 2017.

1). Clone GM MDI Review Compatibility: Device works with GDS2 (Opel) Device works with Tech2Win (Opel, Hammer) The device does not work with SAAB via Tech2Win

GM MDI is working in Consult 3 plus

Cars tested- success & failure list: 1: SAAB 9-5, 2003, 3.0 TID- works mine is a clone from China. MDI Software 8.1.135.13 GT32 SAAB NAO V9.250 Simply pressed OK when Candy detected and all worked. Tested on SAAB 9-5, 2003, 3.0 TID

2: 2014 model – works SAAB NAO V9.250 is from 2014. Already tested. The 2003 year too old – not interesting for me.

3: Saab 9-5, 2003, 3.0 – works Tested by my own, works with Saab 9-5, 2003, 3.0

Online or offline issues: 1: online – good, offline – bad GM MDI good, interface works online. update mdi 100%. offline too bad for new cars.

2: wifi card compatible at now, Chinese clone GM MDI with the squ wifi card

3: wifi not working but works well with USB I bought a cheap one and it only worked with USB. The wired network and wifi did not work. In fact, the card flash socket was missing from the board. Build quality was not to bad. I just use it to flash newer PCM/ecm’s.

GM MDI WIFI version:

https://www.obd2tool.com/goods-2802-Best+quality+For+GM+MDI+Scan+tool+with+Wifi.html

GM MDI USB version:

https://www.obd2tool.com/goods-1621-GM+MDI+Scan+tool.html

Quoted: a man of his words to trust in: I would not go by pictures posted on the web as vendors share the same photos but the MDI had a different ethernet connector and missing card flash socket. It was advertised as (without wifi). It does work fine on USB and for flashing PCM/ECM because at 480 Mbit/s it is almost 5 times faster than ethernet.

The MDI clone works fine with tech2win and also TIS2000. Used it for diags and PCM flashing with no problem (through USB port only)

2). GM TECH2 TIS2000 VS VXDIAG Nano VS MDI in the installation ON the VX nano, sometimes you can get Tech2win to run on win 10 (maybe if you have an AMD chip or not, but have not figured that one out yet), while on my i7 machine, Tech 2 win will not run in win 10 instead. Tech2win is the program that works just like a Tech II, but the program running on a laptop for the MDI (clone MDI device which the Nano is). GDS2 is the program for the C7, like the tech II and tech2win with midi is for the C6 instead. On the VM GDS 2, you don’t need an account with GM to use it, short of needing to do SPS programming, which you will need a TDS SPS subscription instead ($40 for 2 years per car).

So the low down for most laptops, Wants to be running in win 10 for TDS SPS programming. Needs to be running a multi-core chip in win 7 or above to run VM player for VM GDS2. Need to be running in Win 7 native (32 or 64 bit) to run Tech2win (will not work in a VM shell). Tis2000 needs to run in WinXP or built the VM XP shell, so it can be native in XP or in a VM shell so long as you have a multicore processor.

So the way I do it, since Tech2win will not run native on my machine with an I7 process in win 10, I have a dual boot up in win 7 and win 10 both.

Win 10 is used to run pretty much everything I run, short of Tech2 win, which I use the win 7 64 boot up to run it.

So in the Win 7 dual boot up (small 40 gig partition off the drive), have tech2win to use the Nano as a Tech II, plus VM GMSI, and Tis2000 in a VM shell since I may need them as well for the VX nano running as a tech II when running in win 7.

In win 10 boot up, VM GDS2 V17 TDS using internet explorer native with account VM Tis2000 built on a full XP OS with account VM GMSI

If you want to just run a single OS system, instead of a dual boot up machine since you can’t get Tech2 win to run in win10, then you can run pretty much run everything in win 7 (32 or 64 bit), so long as you have a CPU that has multicores. Hence you going to need to run at least VM player for the VM shells, and it takes as a multi-core processor to run VM player (or VM workstation). Note, I have VM workstation, instead of just VM player, since I build other VM shells to run in windows as well.

So again, it really just depends on your machine, and if you Tech2win will run correctly on it or not. Hence the problem is when you open Tech2win, you need to get three pop up screens once Tech2win start the program.

The first screen will ask you what country, and you select North America.

The second pop up will ask you if the device is an MDI 1 or MDI 2, and you select GM Scanner MDI 1.

The third pop up screen will ask you if you want to select the USB device (the nano plugged into a USB port), you select it, then it will take you to the Tech2win start screen.

So if you open Tech2win, and you don’t get the three pop up screens but just goes directly to tech2win main start screen below instead, then Tech2win is not going to work on your machines win 10. Hence the problem is a glitch in midi and tech2 win interface to select the nano, to begin with (what the pop-up screens are), and if you can’t select the nano via the pop-up screens, tech2win will not connect to the nano in the first place.

Again don’t know if this is an AMD verse Intel CPU problem in win 10, but the only laptops that I have seen run Tech2win in windows 10, just happened to be laptops running an AMD CPU instead. And yes, have tried to skin the cat many way with added drivers and compatibility modes, and it’s driver/code line that Win 10 does not have for the Intel CPU (but seems to to have for the AMD CPU that is a carry over from the win 7 days to make the AMD chip work with win 10 instead).

Please enjoy.

[myemilyzhang]

1999 – 2002 GMT-800 Fog Light SPS programming

About: 99–02 Fog light SPS programming Silverado Sierra Tahoe Yukon Suburban

The proper way to program 99-02 GMT-800 Fog lights into the BCM. We quickly cover the use of SPS and the proper calibration selection for fog light addition.

GMT-800-SPS-Programming-Fog-Light-1 GMT-800-SPS-Programming-Fog-Light-2 GMT-800-SPS-Programming-Fog-Light-3 GMT-800-SPS-Programming-Fog-Light-4 GMT-800-SPS-Programming-Fog-Light-5 GMT-800-SPS-Programming-Fog-Light-6 GMT-800-SPS-Programming-Fog-Light-7 GMT-800-SPS-Programming-Fog-Light-8 GMT-800-SPS-Programming-Fog-Light-9 GMT-800-SPS-Programming-Fog-Light-10

Service Programming System (SPS)

The Service Programming System (SPS) updates the flash calibration files that are stored in a vehicle onboard controller (e.g. PCM, ABS, VTD). The calibration file custom-tailors a module to a certain vehicle. The calibration file contains data such as spark curves and fuel control. When troubleshooting a drivability condition, diagnosis may call for reprogramming the controller with newer calibration information to correct a customer concern.

The Service Programming System (SPS) updates the flash calibration files that are stored in a vehicle onboard controller (e.g. PCM, ABS, VTD). The calibration file custom-tailors a module to a certain vehicle. The calibration file contains data such as spark curves and fuel control. When troubleshooting a drivability condition, diagnosis may call for reprogramming the controller with newer calibration information to correct a customer concern.

Programming Interface

The SPS application is part of the TIS2Web system. To program an ECU, the SPS application must communicate with the vehicle control modules using the proper J2534 programming interface tool. A Programming Interface tool is your connection between your computer and the vehicle’s J1962 DLC connector for pass-thru programming of the vehicle’s ECUs.

The following are the supported interface tools:

Tech2 scan tool GM MDI interface J2534 Programming Interface Tool

Successful Control Module Programming

It’s becoming second nature for many repairs — reprogramming vehicle control modules with updated calibration files using the Service Programming System (SPS). The calibration files contain the data that manage vehicle control functions. The programming process uses Pass-Thru Programming through the Multiple Diagnostic Interface tool (MDI/MDI 2).

But successful reprogramming of an existing control module as well as programming a new module, including for installation of GM Accessories, requires that the programming process be followed properly every time, including correctly preparing the vehicle for programming, setting up the necessary tools, and reviewing the Service Information.

Check the Service Information Every Time

The Service Information should always be reviewed for the appropriate programming and set-up procedures of an individual module. Based on the control module being programmed, some vehicle modules will require configuration, reset or learn functions to be performed after programming. Review the Control Module References in the Service Information for module-specific programming and related procedures. These procedures must be completed in the correct order. Failure to perform all programming actions at the same time on a vehicle may result in additional drivability concerns.

Programming Basics

There are a number of steps that should be followed for all programming events

Do not program a control module unless directed to by a service procedure or a Service Bulletin. Programming a control module at any other time will not permanently correct a customer concern. GM does not recommend reprogramming with the same calibration. If the Same Calibration/Software Warning is noted on the SPS Controller screen, do not attempt to program the module. Ensure the programming tool is equipped with the latest software and is securely connected to the Data Link Connector. If there is an interruption during programming, programming failure or control module damage may occur. The MDI 2 has wireless capability; however, it is recommended when programming a control module that it is hard wired to the programming tool with the SPS application. Maintain stable battery voltage during programming by installing the EL-49642 SPS Programming Support Tool. Any fluctuation, spiking, over voltage or loss of voltage will interrupt programming. If the EL-49642 tool is not available, connect a fully charged 12V jumper or booster pack disconnected from the AC voltage supply. Do not connect a battery charger. Turn off or disable systems that may put a load on the vehicle battery such as: interior lights, exterior lights (including daytime running lamps), HVAC, radio, etc. During the programming procedure, follow the SPS prompts for the correct ignition switch position. To help avoid damage to vehicle control modules, do not turn off the ignition during reprogramming unless instructed to do so. Clear Diagnostic Trouble Codes (DTC) after programming is complete. Clearing powertrain DTCs will set the Inspection/Maintenance (I/M) system status indicators to NO. Refer to the appropriate Programming and Set-up procedures in the Service Information for the control module being programmed for additional information on programming. Always record the SPS Warranty Claim Code on the job card for warranty transaction submission.

USB Programming

USB port programming allows for Human Machine Interface (Infotainment, Navigation, XM, and Audio programming) and Instrument Cluster programming. A USB File Transfer is used to transfer data files from SPS to a USB flash drive, or memory stick. Using the USB flash drive reduces the programming time of large calibration files. The USB flash drive should have a USB 2.0 specification with a minimum of 512 MB.

When using a USB flash drive, follow the precise order outlined in the programming procedures. Performing the steps out of order or not completing all steps may cause the programming to be unsuccessful or cause features to work improperly.

Before programming, be sure to check the appropriate Service Information to determine the correct USB port in the vehicle to use for programming. The USB port used for programming depends on the optional equipment on the vehicle.

Once the USB flash drive is installed in the proper USB port in the vehicle, the system will recognize that update files are available and the download will start automatically. Instructions will appear on the infotainment display. After the USB programming is completed, SPS programming should be performed.

TIP: Instrument Cluster Module Programming requires SPS programming first, then set-up and configuration, before USB file transfer.

Do not use the software on the USB flash drive to update multiple vehicles. A USB software validation must be done for each vehicle to be properly updated. This may or may not require writing new files to the USB flash drive.

Solenoid Valve Characterization Reprogramming

The solenoids in some transmissions require unique performance characteristic data in order to function at maximum efficiency. The data is stored in the Transmission Control Module (TCM). When a transmission assembly, TCM, or valve body is replaced, the performance characteristic data for the solenoids must be retrieved from an online web server and reprogrammed into the TCM using SPS.

Before beginning repairs, document the new Transmission Unique Number (TUN) on the transmission or the Part Unique Number (PUN) on the control valve solenoid body. These numbers can be difficult to access when the components are installed on the vehicle.

In SPS, once on the MCVM (Mechanical Characterization and Virtual Matching) Operation Selection screen, the TUN or PUN will be needed if replacing a transmission part. SPS will read the VIN from the Engine Control Module and retrieve the applicable genealogy data tree from the online web server. The data tree includes the original characterization data so that it can be updated with the new component information. The TCM is updated with the correct solenoid characterization data, and the online server is updated with the new genealogy relationship.

Solenoid valve characterization reprogramming must be completed before performing a transmission Service Fast Learn procedure. The characterization data is needed in order for the TCM to learn the individual clutch apply pressures during the Service Fast Learn procedure. Be sure to follow the exact sequence of the Service Fast Learn procedure as outlined in the appropriate Service Information.

Electrical Procedures

Following is a list of electrical procedures that are associated with reprogramming or control module replacement.

[icarscan-blog]

Difference Between Original MDI 2 and China MDI2

                        Product GM MDI2 (Original) GM MDI 2 (China Version) Photo Original Original from Dealer China UOBD2 version Price More than $1200 ONLY $229 WiFi Yes Yes Speed Fast Fast Security Good,it is relief Good Update Yes Update via CD Operation System You can try MDI2 software on any possible systems ONLY Win 7 64 bit Global TIS Yes Yes GD2 Yes Yes Tech 2 Win Yes Yes TISWeb-SPS Yes Yes,SPS programming for existing and future SGM Vehicle OBDII Diagnosis Yes Yes ECU Programming Yes Yes Key Programming Yes Yes Pass-Thru programming Yes,done by TISWeb-SPS Yes Hidden Function Reflashing Yes Yes Vehicle Coverage Vauxhall Opel, Buick, Chevrolet1996-2017-future all Vauxhall/Opel 16 pin vehicles from 1996 to 2017

[icarscan-blog]

Setting Up Wireless Communications

The GM MDI II is capable of communicating on your workshop network over Wireless. The Network Setup tab in the MDI Manager software provides a number of functions used to select and configure the MDI 2network connection interfaces including wireless access and security settings.

You must be connected to the MDI 2via USB to access the settings on the Network Setup tab. If you are not connected via USB, the controls on the Network Setup tab are disabled.

The MDI 2supports two methods for wireless communication. With the Access Point Wireless Communication method the MDI 2connects to your PC through an access point in your workshop. With the Point-to-Point Wireless Communication method the MDI 2connects to your PC directly using a USB wireless adapter. Each of these methods are described in the following sections.

Enabling Access Point Wireless Communication Your MDI 2can be configured for Access Point Wireless Communication. Before starting, you need to know the following: 1.An IP Address and Subnet Mask to assign to your MDI 2 (if your LAN does not automatically assign IP addresses) 2.Wireless communication access point SSID (network name) 3.Wireless security password (encryption key) 4.The illustration below shows several MDI 2s connected to a single laptop PC using a wireless access point.

Use the following procedure to configure your MDI 2 for wireless communication in your environment. Before modifying the MDI 2 communications interface, contact your IT Administrator. 1.Start the MDI Manager software by clicking on the MDI Manager icon. 2.Plug the MDI 2 into external 12v power. 3.Plug the USB cable into the PC and MDI 2 and allow the MDI 2 to boot completely. 4.Select and Connect to your MDI 2 in the MDI Manager software MDI 2 Explorer tab. 5.Select the Network Setup tab. 6.From the Wireless tab, select the Enable Wireless Interface check box in the Interface Control section. Once you enable the interface, the IP Address Configuration box and the Apply and Cancel buttons become active. 7.Select Obtain an IP address automatically if your LAN automatically assigns IP addresses. Otherwise enter the assigned IP Address and Subnet mask given to you by your IT Administrator. 8.Select Access Point to begin wireless access point configuration. 9.Specify the network name:a.If your access point usesa hidden SSID or if you are not within range of the access point you will select the Enter Network Name [SSID]: radio button and type the network name.b.If you are within range of your wireless access point, choose the Select from available network list radio button and then select Refresh to cause the MDI 2 to search for wireless network signals. The detected networks are displayed in the Network Name box. 10.  After you have entered the network name, select Configure.11.  Enter the security settings thatare required by your network, then select Next. 12.  Select Yes to reconfigure your OBD2 Scanner MDI 2, or if you want to start over select No. 13.  Choose the Properties tab to verify that the MDI 2 is configured correctly. You can also disconnect the USB cable to verify that the wireless connection is working. 14.  Record or print your settings as they are displayed on the Properties tab for future reference.Enabling Point-to-Point Wireless CommunicationYour MDI 2 will initiallybe configured for Point-to-Point Wireless Communicationon the PC you are connected to. Before starting, please verify your MDI 2kit is the Wireless-Point-to-Point kit 8200171 (Bosch p/n 1699200171)which includes the MDI 2 assembly with twoD-Link Wireless 802.11n USB Adapters.The illustration below shows a single MDI 2connected to a laptop PC using Point-to-Point Wireless communication.

Enabling Point-to-Point Wireless CommunicationYour MDI 2 will initiallybe configured for Point-to-Point Wireless Communicationon the PC you are connected to. Before starting, please verify your MDI 2kit is the Wireless-Point-to-Point kit 8200171 (Bosch p/n 1699200171)which includes the MDI 2 assembly with twoD-Link Wireless 802.11n USB Adapters.The illustration below shows a single MDI 2connected to a laptop PC using Point-to-Point Wireless communication

If you need to re-configure Point-to-Point on your MDI 2, use the following procedure. Note that the steps presented below assume you are running the Windows 7 operating system on your PC. The steps for other versions of the Windows operating system may be slightly different. 1.Insert the Wireless USB adapter in an available USB port on your PC. Do not plug the wireless adapter into a USB hub. Power-on your PC. 2.Connect the MDI 2 to your PC using the USB cable and allow the MDI 2 to boot completely. Do not plug the MDI 2 USB cable into a USB hub. 3.Start the MDI Manager software by double-clicking the icon on the PC desktop. 4.The Point-to-Point connection isautomatically configured. Wireless communication will be available when you are powered through the DLC Cable.If you have the need to reset your Point-to-Point passphrase, you can use the following steps.

The following steps assume you are running the Windows 7 operating system on your PC 1.On the right-hand side of the Windows Task Bar, click the View Wireless Networks button. A list of the available wireless networks in range of your PC is displayed. 2.Select Open Network and Sharing Center. 3.Select Manage Wireless Networks from the left column. 4.Select Change adapter menu and choose MDI from the list. 5.Remove your stored Point-to-Point network. The name will contain MDI and the last 8 digits of the MDI 2 serial number, (MDIXXXXXXXX). 6.When you reconnect the MDI 2 to the PC using the USB cable, a new passphrase will be established.

Set Factory Default

Selecting the Set Factory Defaultbutton on the Network Setup tab reconfigures your MDI 2to the Point-to-Point communications settings it had when it left the factory. Any software upgrades that have been installed to the MDI 2are still installed. When the car diagnostic scanner MDI 2 reset is finished, the MDI Manager software displays the MDI 2Explorer tab.All wireless AP configurations will be lost.

[youobd88]

V2019.07 Best quality GM MDI 2 Diagnostic Tool GM Multiple Diagnostic Interface with WIFI

Overview

The Multiple Diagnostic Interface 2 (GM MDI 2) is used by professional technicians as an aid in diagnosing and repairing automotive electrical and electronic systems. The MDI 2is designed to connect the vehicle to a host PC computer application which then functions through the MDI2for data transfer and Electronic Control Unit (ECU) reprogramming.Using the MDI Manager

PC application software, you configure the MDI 2to communicate with a host computer. The MDI 2is capable ofcommunicating over a USB cable, Ethernet cable, or wireless network (WLAN).

User group

The product may be used by skilled and instructed personnel only. Personnel scheduled to be trained, familiarized, instructed or to take partin a general training course may only work with the product under the supervision of an experienced person.

PC System Requirements

The MDI 2 Software runs on a PC/Laptop. The user interacts with the MDI 2 software for device setup, and configuration for SAE J2534 or ISO 22900 data transfer and ECU reprogramming.The following table lists the minimum PC/laptop requirements for installing and running the MDI2 Software.

MDI 2 Kit ContentsThe MDI 2 Kit includes hardware and cables needed to transfer data and reprogram ECUs on vehicles through the DLC connector.

The Wireless Auto Scan Tool MDI 2 Kit (Bosch p/nEL-52100) US and Canada-Includes the MDI 2 assembly with two USB Wireless Adapters, DLC Cable, USB Cable, and Ethernet Cable.  The Self Test Adapter is sold separately.MDI 2 Connectors and ControlsA number of standard connectors and controls are available on the MDI 2to facilitate operation and communication with vehicles and workshop networks. These connectors and controls are shown in the following illustrations

The MDI 2has a fixed USB configuration which cannot be changed. This ensures that the MDI 2can always be connected to a single PC running the MDI Manager software so you can configure LAN or WLAN settings required by your local network. In addition, it is important to note that a USB connection is recommended to configure and update the firmware on the MDI 2. USB connection must be made directly with the PC port.  Do not connect through a USB hub.

[qingqin]

2019 GM MDI2 shares the same functions and vehicle coverage as GM MDI. GM MDI2 features in a light blue color shell and brand-new shape, GM MDI features in dark blue shell.

2019 GM MDI2 is optional with Wifi version and USB version (means wired network connection is not allowed) GM MDI is only optional with Wifi version.

Image 1: 2019 GM MDI2 in light blue (WIFI or USB options)

Image 2: GM MDI in dark blue.

Similarities: 1. Both GM MDI2 and MDI are compatible with GDS2 Tech2Win

OS: WIN7 64bit Computer: the year after 2008, 4GB RAM Pros: gds2 software needs no activation The method to use: Insert the HDD with GM MDI gds2 software into your computer; the software can be used directly with the GM MDI scanner.

Tech2win is the program that works just like a Tech II, but the program running on a laptop for the MDI (clone MDI device which the Nano is). GDS2 is the program for the C7, like the tech II and tech2win with midi is for the C6 instead. On the VM GDS 2, you don’t need an account with GM to use it, short of needing to do SPS programming, which you will need a TDS SPS subscription instead ($40 for 2 years per car).

So the low down for most laptops, Wants to be running in win 10 for TDS SPS programming. Needs to be running a multi-core chip in win 7 or above to run VM player for VM GDS2. Need to be running in Win 7 native (32 or 64 bit) to run Tech2win (will not work in a VM shell).

2. Both GM MDI2 and MDI have the same capabilities Full dealer level diagnostics and programming for all Vauxhall /Opel 16 pin vehicles from 1996 to 2017.

1). Clone GM MDI Review Compatibility: Device works with GDS2 (Opel) Device works with Tech2Win (Opel, Hammer) The device does not work with SAAB via Tech2Win

GM MDI is working in Consult 3 plus

Cars tested- success & failure list: 1: SAAB 9-5, 2003, 3.0 TID- works mine is a clone from China. MDI Software 8.1.135.13 GT32 SAAB NAO V9.250 Simply pressed OK when Candy detected and all worked. Tested on SAAB 9-5, 2003, 3.0 TID

2: 2014 model – works SAAB NAO V9.250 is from 2014. Already tested. The 2003 year too old – not interesting for me.

3: Saab 9-5, 2003, 3.0 – works Tested by my own, works with Saab 9-5, 2003, 3.0

Online or offline issues: 1: online – good, offline – bad GM MDI good, interface works online. update mdi 100%. offline too bad for new cars.

2: wifi card compatible at now, Chinese clone GM MDI with the squ wifi card

3: wifi not working but works well with USB I bought a cheap one and it only worked with USB. The wired network and wifi did not work. In fact, the card flash socket was missing from the board. Build quality was not to bad. I just use it to flash newer PCM/ecm’s.

Quoted: a man of his words to trust in: I would not go by pictures posted on the web as vendors share the same photos but the MDI had a different ethernet connector and missing card flash socket. It was advertised as (without wifi). It does work fine on USB and for flashing PCM/ECM because at 480 Mbit/s it is almost 5 times faster than ethernet.

The MDI clone works fine with tech2win and also TIS2000. Used it for diags and PCM flashing with no problem (through USB port only)

2). Tech 2 Scan Tool TIS2000 VS VXDIAG Nano VS MDI in the installation ON the VX nano, sometimes you can get Tech2win to run on win 10 (maybe if you have an AMD chip or not, but have not figured that one out yet), while on my i7 machine, Tech 2 win will not run in win 10 instead. Tech2win is the program that works just like a Tech II, but the program running on a laptop for the MDI (clone MDI device which the Nano is). GDS2 is the program for the C7, like the tech II and tech2win with midi is for the C6 instead. On the VM GDS 2, you don’t need an account with GM to use it, short of needing to do SPS programming, which you will need a TDS SPS subscription instead ($40 for 2 years per car).

So the low down for most laptops, Wants to be running in win 10 for TDS SPS programming. Needs to be running a multi-core chip in win 7 or above to run VM player for VM GDS2. Need to be running in Win 7 native (32 or 64 bit) to run Tech2win (will not work in a VM shell). Tis2000 needs to run in WinXP or built the VM XP shell, so it can be native in XP or in a VM shell so long as you have a multicore processor.

So the way I do it, since Tech2win will not run native on my machine with an I7 process in win 10, I have a dual boot up in win 7 and win 10 both.

Win 10 is used to run pretty much everything I run, short of Tech2 win, which I use the win 7 64 boot up to run it.

So in the Win 7 dual boot up (small 40 gig partition off the drive), have tech2win to use the Nano as a Tech II, plus VM GMSI, and Tis2000 in a VM shell since I may need them as well for the VX nano running as a tech II when running in win 7.

In win 10 boot up, VM GDS2 V17 TDS using internet explorer native with account VM Tis2000 built on a full XP OS with account VM GMSI

If you want to just run a single OS system, instead of a dual boot up machine since you can’t get Tech2 win to run in win10, then you can run pretty much run everything in win 7 (32 or 64 bit), so long as you have a CPU that has multicores. Hence you going to need to run at least VM player for the VM shells, and it takes as a multi-core processor to run VM player (or VM workstation). Note, I have VM workstation, instead of just VM player, since I build other VM shells to run in windows as well.

So again, it really just depends on your machine, and if you Tech2win will run correctly on it or not. Hence the problem is when you open Tech2win, you need to get three pop up screens once Tech2win start the program.

The first screen will ask you what country, and you select North America.

The second pop up will ask you if the device is an MDI 1 or MDI 2, and you select MDI 1.

The third pop up screen will ask you if you want to select the USB device (the nano plugged into a USB port), you select it, then it will take you to the Tech2win start screen.

So if you open Tech2win, and you don’t get the three pop up screens but just goes directly to tech2win main start screen below instead, then Tech2win is not going to work on your machines win 10. Hence the problem is a glitch in midi and tech2 win interface to select the nano, to begin with (what the pop-up screens are), and if you can’t select the nano via the pop-up screens, tech2win will not connect to the nano in the first place.

Again don’t know if this is an AMD verse Intel CPU problem in win 10, but the only laptops that I have seen run Tech2win in windows 10, just happened to be laptops running an AMD CPU instead. And yes, have tried to skin the cat many way with added drivers and compatibility modes, and it’s driver/code line that Win 10 does not have for the Intel CPU (but seems to to have for the AMD CPU that is a carry over from the win 7 days to make the AMD chip work with win 10 instead).