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.
Yes, I did that too. But, it never reads the lines that will allow me to connect. I might need to get the 10.30 version. Maybe.
Is the "cable test" a program comes with the CD? Mine (MVCI firmware update tool) is different. Without plugging the adapter into the vehicle, it checks the connection from PC to adapter/cable. If the "cable test" is doing something similar and fails, I guess the cable is bad. if the cable is good, turn the car to ignition on and hit the "Connect to Vehicle", it is supposed to show some pop up windows with wording "Initialize USB Communication", "Connecting to Vehicle".
Bought from this same seller for my 2nd set of MVCI + TIS. V13.00.022 could not work. V12.xx.xx works the same way as V10.30.029 but not fully functional. It can clear code, read ECU data but always have communication error when doing ECU data update/configuration. It will be interesting to know if it works on yours.
Installation was a breeze on Windows 10 with 64-bit.
But it kept crashing with "Fatal Error". I connected to ECU and was only able to view the monitoring portion. When I tried to click on Data List, it crashed with "Fatal Error". Is this the same problems you're experiencing with this version?
I also have a laptop with Windows XP 32-bit that I can also try to set up with Techstream.
Installation was a breeze on Windows 10 with 64-bit.
But it kept crashing with "Fatal Error". I connected to ECU and was only able to view the monitoring portion. When I tried to click on Data List, it crashed with "Fatal Error". Is this the same problems you're experiencing with this version?
I also have a laptop with Windows XP 32-bit that I can also try to set up with Techstream.
Yes, that's exactly what I have experienced. The version 13.00.022 does not work for these windows version (Win10 64, Win10 32, XP). The seller gave me a link to download version 12. It worked with "Data List", but failed when I tried to program the ECU (Tire Pressure Monitor ID update) using the "Utility" in that ECU sub menu. That's when I encountered the "Communication Error". I tried the version 10.30.029, it had the same error as version 12. From IS forum, some people connect 12V charger to the 12V battery and AC adapter to PC that resolves "Communication Error". I tried that and did not have any luck. According to Dennis, it needs firmware 2.0.4 on the MVCI adapter/cable.
Yes, that's exactly what I have experienced. The version 13.00.022 does not work for these windows version (Win10 64, Win10 32, XP). The seller gave me a link to download version 12. It worked with "Data List", but failed when I tried to program the ECU (Tire Pressure Monitor ID update) using the "Utility" in that ECU sub menu. That's when I encountered the "Communication Error". I tried the version 10.30.029, it had the same error as version 12. From IS forum, some people connect 12V charger to the 12V battery and AC adapter to PC that resolves "Communication Error". I tried that and did not have any luck. According to Dennis, it needs firmware 2.0.4 on the MVCI adapter/cable.
I'm going to try again tomorrow. I didn't get to play with it today. Maybe I'll get lucky. Wish me luck.
I do not believe you can download 2.0.4 firmware. It is programed into the cable when it is made I believe the drivers to load to your laptop are provided with the cable/cd. You cannot change a 1.4.5 firmware cable to a 2.0.4 cable.
The V12 version works better than V13 as I'm able to view more data lists from other ECUs on Windows 10 64-bit. But I'm still having problem with fatal error when trying to open data list for the engine ECU.
The seller also sent me a link to download the V13 version to run on virtual machine. I tried that and it was working the same as V12 version on my Windows 10 64-bit laptop. I like the virtual machine version as you don't have to install the software on your laptop. I also have the virtual machine setup for my BMW M5 which I also code (E-SYS).
BE SURE TO WAIT until the Virtual Machine has loaded and you are at the Techstream screen BEFORE inserting the USB end of the cable into your computer or else the virtual machine would not recognize the cable.
I've attached a PDF to read before downloading the file.
Screenshots below are the latest Techstream V13.30 on VMware. Good luck!
Virtual Machine Virtual Machine
Last edited by RA40; Aug 6, 2019 at 11:03 AM.
Reason: link removed
FWIW, I ran the firmware check on my cable and it's 1.4.1
I'm going to test the cable and the latest Techstream on a 2011 GX 460 and a 2015 Camry and see if I still get the same fatal error like with 2013 LS 460. I'll report back.
Experienced the same fatal error when trying to access data list for the Engine/ECT on a 2011 GX 460. I ordered a 2.0.4 cable from Amazon this morning and should be here Saturday. I will report back if the newer firmware cable works.
Experienced the same fatal error when trying to access data list for the Engine/ECT on a 2011 GX 460. I ordered a 2.0.4 cable from Amazon this morning and should be here Saturday. I will report back if the newer firmware cable works.
Good news! The 2.0.4 firmware works with version V12.30 for 2013 LS. I was able to access the data list for the engine ecu without any crashes.
I tried to run V13.0 but it kept crashing so I went back to V12.30, and it worked flawlessly. I also tried with the V13.30 through virtual machine but I couldn't get the cable to connect to the VIM.
Good news! The 2.0.4 firmware works with version V12.30 for 2013 LS. I was able to access the data list for the engine ecu without any crashes.
I tried to run V13.0 but it kept crashing so I went back to V12.30, and it worked flawlessly. I also tried with the V13.30 through virtual machine but I couldn't get the cable to connect to the VIM.
Experienced the same fatal error when trying to access data list for the Engine/ECT on a 2011 GX 460. I ordered a 2.0.4 cable from Amazon this morning and should be here Saturday. I will report back if the newer firmware cable works.
Who did you order the cable from with the 2.0.4 firmware?
