How to Get PIN Code when Bricks Renault 2015+ 4A System UCH?.Autel MaxiSys Ultra VS MaxiSys MS908S Pro.Launch X431 Pad VII “Serial Number Does Not Exist” Solution.
Sprinter 2014 Diesel 2.2 Liter ECU Info Add to Launch X431 Pad VII.How to Transfer Data from Autel IM608/IM508 to PC?.Will Autel IM608 /IM508 Still Work After Subscription Expired?.Repair Carprog A1 Adapter for CAN BUS cummunicationīMW INPA 6.4.3, 5.0.6,5.0.2 Free Download How to use BMW INPA software and cable K+DCAN
#Techstream bluetooth install
How to install TIS2000 for GM Tech 2 scanner Install BMW INPA on WinXP Win7 Win8 Win10įree Download BMW E-sys V3.22.5 v3.2.61 v3.2.71įree ECM Titanium 1.61 with 26000 drivers How to Install Toyota TIS Techstream 14.10.028 laptop without the need of a virtual machine. So be assured: Techstream can work on a Windows-10 64bit Prof. The interface is flashing green during communication with the vehicle. When I then connected to my RAV4 it connected nicely and I could readout my TPMS sensor ID’s which was my main objective. Then just connect to vehicle (without actually being connected, just have the MVCI cable connected to the USB port) and you should get no errors but Techstream should eventually (after time out…) come up with a window where you can manually select your vehicle code etc etc. When you now start Techstream with the TSloader make sure the correct interface is selectable (not grayed out) and selected, otherwise re-check the previous setting. If you get “unable to connect to MCI” when connecting to a vehicle most likely these registry settings are not fully correct. These settings point Techstream to the correct location of the XHorse driver used for the MVCI Cable.Īlso do not forget the TISFUNCTION=0 modification in the IT3System.ini file. You can also manually point the original Techstream interface entries in the registry (same location) to the same Xhorse files just to be sure.
#Techstream bluetooth mod
Then install Techstream and apply the registry fixes (either manually or by the downloadable registry mod file), also previously mentioned. If this is OK then at least your interface should be installed correctly, showing a red LED in the process. Just do NOT update, only use it to see if the cable is recognized and reports back its firmware version + “connected” status. When installed correctly you should be able to run the firmware update tool to check the firmware. You can actually check all stages of the installation without connecting to the car:įirst make sure to follow the unpacking/copying instructions in the 64-bit installation instructions before plugging in the cable in the USB port. Installed it using the 64bit for Windows 7/8 instructions previously mentioned and on Using Techstream 12.30.017 (newest: v14.20.019) with the cheap Mini VCI Cable J25345 over here (Firmware 1.4.1) on a HP-Zbook with Windows 10-64bits prof. Best I can tell the only XHorse interface firmware version that I used that worked with it is mini vci cable 2.0.4, these are cloned versions of Techstream and the XHorse cable interface, the real Toyota Techstream costs nearly $2000.