GmanSC

Again, to install TechStream to 64-bit Window, you will have to swap some files and also modify the registry. I tried but got frustrated and gave up. My vendor helped via TeamViewer less than 5 minutes ( he knew what he’s doing). If you successfully installed as instruction below, let us know.


Installing MVCI Driver for TOYOTA:

This is the step most people stumble on as “MVCI Driver for TOYOTA.msi” installer indeed does not work on Windows x64. The workaround is to install it manually, as follows:

Open the Command Prompt in Administrator Mode, and run the following command line:

msiexec /a "C:\temp\MVCI Driver for TOYOTA.msi" /qb TARGETDIR=c:\temp\mvci

This will extract the content of the MSI file to the c:\temp\mvci folder. Go ahead and close the Command Prompt window, and open up the c:\temp\mvci folder :

1. Delete the “MVCI Driver for TOYOTA.msi” there. (Now go into C:\Program Files (x86) and then create a new folder called "XHorse Electronics" and then inside of that folder create another called "MVCI Driver for TOYOTA TIS") Then copy the whole content of c:\temp\mvci to "C:\Program Files (x86)\XHorse Electronics\MVCI Driver for TOYOTA TIS"
2. Plug the MINI VCI cable to the USB port.
3. Open the Device Manager and locate the two failing devices in the list. Both will appear with yellow icon (usually under “Other”), indicating that Windows failed to install drivers for them. Now, right click each failing device, select Install Driver, then “Browse my Computer…” and point it for "C:\Program Files (x86)\XHorse Electronics\MVCI Driver for TOYOTA TIS" (enable the “include subfolders” flag). Click “Next” and wait until drivers are installed.
   
   You should now see two new devices: “Universal Serial Bus Controllers\USB Serial Converter” and “Ports (COM & LPT)\USB Serial Port (COM5)”.
4. Run the FirmwareUpdateTool.exe from the "C:\Program Files (x86)\XHorse Electronics\MVCI Driver for TOYOTA TIS"
5.  
   1. If you see this, it means your MINI VCI is up and running under Windows x64 and can be used by other programs, such as Techstream.
      
      IMPORTANT: Some people have reported that updating firmware on this “cheap clone” cable may render it dead. So, the Firmware Update Tool should NOT be used for anything, but checking that the device is connected and working properly.
6. Now install the Techstream software using "Techstream 8.00.034.exe" and then after installation, open up the "Techstream_Update_V8.10.021.exe" file to update it. DO NOT launch it yet.
   
   To activate it, drag the IT3System.ini you extracted before to the desktop over into "C:\Program Files (x86)\Toyota Diagnostics\Techstream\Env". When prompted, overwrite the preexisting file with the new one you are dragging over.
7. Registry Hack: for Techstream to recognize MINI-VCI under Windows x64, the Registry has to be modified as:
   
   
   Windows Registry Editor Version 5.00
   
   [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\PassThruSu pport.04.04]
   
   [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\PassThruSu pport.04.04\XHorse - MVCI]
   "Name"="XHorse - MVCI"
   "Vendor"="XHorse ELECTRONICS Co.,Ltd."
   "ConfigApplication"="C:\\Program Files (x86)\\XHorse Electronics\\MVCI Driver for TOYOTA TIS\\FirmwareUpdateTool.exe"
   "FunctionLibrary"="C:\\Program Files (x86)\\XHorse Electronics\\MVCI Driver for TOYOTA TIS\\MVCI32.dll"
   "APIVersion"="04.04"
   "ProductVersion"="1.1.0"
   "ProtocolsSupported"="J1850VPW:1, J1850PWM:1, CAN:1, ISO9141:1, ISO14230:1, ISO15765:1"
   "J1850VPW"=dword:00000001
   "J1850PWM"=dword:00000001
   "ISO9141"=dword:00000001
   "ISO14230"=dword:00000001
   "CAN"=dword:00000001
   "ISO15765"=dword:00000001
   "SCI_A_ENGINE"=dword:00000000
   "SCI_A_TRANS"=dword:00000000
   "SCI_B_ENGINE"=dword:00000000
   "SCI_B_TRANS"=dword:00000000
   
   
   The attached "mvci-x64.reg" contains the *.REG file that has to be imported to the Registry (all you have to do in this step is just extract the file to the desktop, right click, then click Merge)
   
   A trick here is the "Wow6432Node" in key path, which is the location the 32-bit applications running on 64-bit OS get redirected to when accessing Registry. The "PassThruSupport.04.04" seems to be the place Techstream looks into for available VIMs (sub-keys appear in the "VIM Select" menu in Techstream).
8. Run Techstream. Go to Setup | VIM Select menu and select the “XHorse - MVCI”
9. Connect MVCI cable to your car’s OBDII interface, turn ignition on, then click “Connect to Vehicle” in Techstream. Wait. Then wait again (by the way, you'll be doing that a lot with this cable ). If everything works, you will be prompted to confirm car year/model after which you'll get to the diagnostic interface.
10. 
    
    
    
    Just to clear it up, you do not have to register this software after this is all done, it is yours forever (almost). Mostly all of the customizable options can be accessed with this update so I would not mess with it and try to get anything new as it is not needed!
    I

DJWLDW

BGW70

No problem I guess I was confused when you said there was a 32 bit and 64bit version that you were talking about the V15 Techstream software. Now I understand that it was the driver firmware for the cable not the program software..

iolmaster thanks for catching that and sitting me straight.

Dennis

Oldsig

Maybe I missed this but was is the advantage of using the v2.0.4 cable vs the v1.4?
I'm using a v1.4 cable with Techstream 15.xx on a Win 7 laptop. That combination seems to work fine for both my '06 SC430 plus my '15 RX350.
Bob

iolmaster

iTrader: (1)

for some of us the version 1 firmware cable would not connect to our car. I have no idea why. I then tried the version 2 firmware and had no problem. I haven't tried what I have right now (version 2 firmware cable on a 32 bit W10 laptop) on my 2015 RX so I don't know if it will connect. I haven't had the need. So, to answer your question, there is no advantage if yours is connecting properly. Interesting that I also have an 06 SC.

DJWLDW

I also have an 06 and I use the V 2.0.4 cable with no issues. We are about to try my V 2.0.4 cable on my sons 05 SC as his V 1.4 cable is having a problem with the V15 Techstream Software.

Dennis

iolmaster

iTrader: (1)

Let us know how that works. Just curious.

DJWLDW

Will do, although it might be a couple of weeks. The sons SC is with his daughter who got rear ended and has her Dad's SC down at UNCW where she is going to school.

Dennis

iolmaster

iTrader: (1)

Ahh yes, UNC Wilmington I am a grad of NC State and have been to UNCW a number of times. Much smaller when I was there. Early 70s.

oneround

To @Harold57 and/or @Bgw70 : I read about the OBDII extension cable that has only pins 4, 5, 7, 15 & 16 connected and that is sufficient connectivity for 1st gen SC430s to fully interact with Techstream.

I have sourced what I need to replicate your work, however...

I want to plug in a Bluetooth OBDII dongle and be able to look at data through an Android version of an app such as Torque Pro. As I understand it, if I ever needed Techstream all I would have to do is remove the dongle and connect a Techstream cable. Also, for my 2002, if I read the posts correctly, with only pins 4, 5, 7, 15 & 16 connected, I shouldn't have to worry about setting off the VSC light, etc., using the dongle or Techstream. I can put in a 4 & 14 switch if the Bluetooth dongle fails, so that's not really a worry.

The actual reason for this post -- To avoid doing something dumb (one of my best talents) I was wondering if you had any experience with products other than Techstream using the reduced pin count cable.

Harold57

Not per se. However, without specialized software to interpret the custom Toyota messages, I don't see what it will gain you. I'm not sure just what it is you are asking though.

If it helps, I currently use a OBDII device (the Panlong Mini OBDII) and read it through Torque and have no issues with hooking it up directly.

oneround

I can read my OBDII dongle as well, it just sets the VSC light. So, I have to break out the 4 &14 pin plug. I was hoping I could use the dongle, with the cable you guys posted, and not have to mess with the 4 & 14 pin plug anymore.

Harold57

You should be able to use it, that is assuming that your dongle is causing the VSC light the same way that the Techstream does. So I'd suggest that you give it a try, there's no reason to believe that it won't help.

oneround

I made up an extension cable and installed in the car with the open end attached to the top of the carpeted kick panel next to the door panel -- works as described. I would provide a link, but the one I purchased doesn't seem to be on Amazon anymore. Basically, it is a right-angle male connector that attaches to the car's OBDII port, and a female end that has an exposed back with open wiring for about two inches. The exposed end allowed me to see, and snip off, all but the necessary wires (pins 4, 5, 7, 15 & 16) mentioned in the earlier posts.

In car I have an Xtrons Android car head unit. It came with the Torque app pre-installed. I also have an Xtrons Bluetooth OBDII dongle that has a built-in on/off switch (to avoid battery drain).

As a result, with Torque I can read codes and monitor performance while rolling down the road vice waiting until I got home to break out the Techstream laptop -- All without setting the VSC light, etc. Plus, I can still get to the unmodified OEM OBDII connector if I need pin 13 (or other connection) for diagnostics.

Thanks to all those who helped lay out this path. Notably @Retroplay , yourself, @Bgw70 -- and my apology if I forgot a critical player in this topic.

Sherl

http://blog.obdii365.com/2022/10/16/...e=pocket_saves

Sherl

On another note, anybody have reliable vendor links for mini vci with V2. 0.4?