abhas.blogg.se - Techstream cannot connect to vim

Techstream cannot connect to vim install#
Techstream cannot connect to vim update#
Techstream cannot connect to vim driver#
Techstream cannot connect to vim upgrade#
Techstream cannot connect to vim pro#

Now open TS and BEFORE you do anything else, check that the TIS Techstream VIM is NOT selected, but rather the other choice (e.

Switch off the TIS Function by changing TISFunction=1 (or what ever value it is) to TISFunction=0.

Scroll down to AVAILABLE FUNCTION SETTING.

Within this folder locate IT3System.ini and open it in TextEdit.

BEFORE opening TS (big temptation, but resist), open a Finder window and locate C: Program files\Toyota Diagnostics \Techstream\Env.

Techstream cannot connect to vim install#

Install the TS software that came with your cable.

Run the X-Horse Firmware Updater Tooland confirm you see all the fields populated with data, including the Firmware version.

(IIRC you should see some Windows install activity in the bottom right-hand side of the screen.)

Techstream cannot connect to vim driver#

Install the MVCI driver MSI that came with your cable.

I’ll quickly list the steps, then follow that with an explanation of my logic. I beg your indulgence, and figure it should translate to both environments. This seemed to be a happy medium to get the VM running at a reasonable speed.Īnyway on further reflection, I decided to do an overview of what I believe to be the logical steps to install MVCI/TS and try not to get too bogged down in the technical minuté of the detail. In the VM I am running Win XP Pro, SP3 to which I have allocated 2 GB.

Techstream cannot connect to vim pro#

My setup is a MacBook Pro with 8 GB RAM running VMware. My set up is not, because of a number of ducks that happened to line up and also having worked a lot with Windoze (probably not so much these days, but hey old prejudices die hard – please don’t flame me ) computers a lot (back in the day) I usually opted for the path of least resistance. On reflection, I’m in two minds whether to do my “quick set up guide” post, mainly on re-reading the the OP’s post and subsequent replies the essence of this thread is getting TS to work in the 64-bit environment. Obvious when you say it out loud, but not so much when you’re in the thick of it. I’ll do another post shortly with my thoughts from my install experience about the way I believe one should go about installing MVCI/TS more as an ideological overview rather than in technically minute detail – there are plenty of those out there and some have been referenced in this thread already.ĮDIT: One other thought that just popped up, if you are using a VM (like I am) make sure you connect the host USB port to your VM. (I started off with v7.x.x and updated to v8.30.23 and found not tangible difference in the way TS worked.) Although there are bug fixes in newer TS s/w the main updates are to do with the newer model vehicles being recognised, so any version from v7.x.x onwards should be fine for Gen II’s. I don’t believe that the version of TS has too much to do with your problems. Incidentally, while I’m talking about versions, the X-Horse Firmware Updater Tool reports my firmware version as 2.0.4, where as TechStream reports it (in the status bar) as v1.4.6, so don’t worry about that. Subsequently I found that I did not need to worry about it as the version I had worked fine. But my experience with that was I could not find a file to use.

Techstream cannot connect to vim update#

You could theoretically update the driver version, if you had an update file. This is funny because the X-Horse is a knock off of the Mongoose Cable. The story I heard was because they became inundated with update requests from Chinese knock-offs of the X-Horse product. The Online Update function, does not so much cause the cables to fail as it just does not work due to (long story short) the X-Horse update servers being shutdown. The only tangible use for the X-Horse Firmware Updater Tool is to check that you have a connection to the MINI VCI cable – if you have the driver installed correctly you will get the firmware version num and other info.

Techstream cannot connect to vim upgrade#

However, it has been reported that using this software to upgrade the cable firmware can cause some cables to fail… The XHorse installation software will tell you if you have a good cable and let you know what version of the driver is installed.