How-To: TechStream In 5 Minutes (25 Viewers)

This site may earn a commission from merchant affiliate
links, including eBay, Amazon, Skimlinks, and others.

Anyone have thoughts on why I'm only seeing one engine option, which isn't the one I have, when I connect tech stream to my 2005 LC120
Are you just going off the initial "finding" when you connect to the vehicle? You should be able to have a drop-down that changes for year, model, etc. However, the version of the software may not be "EU/UK" compatible so if you have the 1HD/1HZ you may need a different version. Just speculating though.
 
I didn't try it yet, but the posts above yours mentioned virtualbox, so I assume the software is run on virtual machine, like we do with DIS for BMW. If this is correct, then it doesn't matter what OS you have. There is a virtualbox for linux, I used it on my laptop with ubuntu
The download link provide by the OP I believe is a VB instance that will work in any virtual environment, so you are correct in the OS doesn't necessarily matter as long as you can run a VB on your OS. However, if you are trying to install the software directly to your laptop, that is where Windows OS is required.
 
Are you just going off the initial "finding" when you connect to the vehicle? You should be able to have a drop-down that changes for year, model, etc. However, the version of the software may not be "EU/UK" compatible so if you have the 1HD/1HZ you may need a different version. Just speculating though.
I select the year etc but there's no other engine listed in the drop down. Didn't occur to me that tech stream might have different region releases. If I download a new version, can I install that into the windows OS that's already in the virtual box do you know? Not used anything like this before. Thanks for your help.
 
Last edited:
I select the year etc but there's no other engine listed in the drop down. Didn't occur to me that tech stream might have different region releases. If I download a new version, can I install that into the windows OS that's already in the virtual box do you know? Not used anything like this before. Thanks for your help.
Sorry that is outside of my knowledge base. I would assume that they would have a full version provided to everyone but makes sense to have regional. If you can find an appropriate version that has other "features" unlocked or whatever you may be able to install in that virtual environment. Or if you are tech-savvy enough you could create your own virtual environment and do the install there.
 
Found this video on installing the software on Windows 10 x64. Not sure if anyone has tried this method, when I get a dedicated laptop for this purpose I will try. But otherwise, one of you new install guys may want to try.
 
Well just won a little Lenovo Thinkpad Yoga 12 on eBay for $125 shipped. Always loved Lenovo laptops so stoked to get this. Has Win10 Pro on it so will try the above process when I get in hand. Will be a neat little machine to have for this purpose as it is a "convertible 2-in-1 ultrabook" that allows for laptop mode or tablet mode with a pen. Will be good too that it is only 12.5" seeing as the laptop I have been borrowing is a 17" and I have to move the drivers seat all the way back to use it in my lap and still have it resting up against the steering wheel!
 
Why do people prefer to buy a dedicated laptop to run this program? Besides the above argument about having a laptop that’s too big to work on. Is it just so you have a ‘shop’ computer that you don’t mind getting dirty, or is it really that intensive of a program?
 
Why do people prefer to buy a dedicated laptop to run this program? Besides the above argument about having a laptop that’s too big to work on. Is it just so you have a ‘shop’ computer that you don’t mind getting dirty, or is it really that intensive of a program?
For me it is two things...
1. Having a dedicated WINDOWS pc (we are a purely Apple Ecosystem household), and
2. Having something that will not be futzed with program-wise

I think the main concern for a lot of people is not so much about having a dedicated laptop for it but rather having something small and portable for the diagnostics. Something that is old enough or cheap enough that if you drop it on the driveway by accident or it gets kicked around or whatnot, there is little to lose. Outside of that, there is the Amazon/eBay cables that come with software and you don't know what all is on there disc aside from the software (my disc is literally a CD-R, not an official disc) so if it does get borked by malware of whatever, there is no real issue with wiping and starting over.
 
Just wanted to say thanks to the original poster @getco for putting together the pieces that made this all work.

This afternoon my cheap amazon cable arrived. Previously I created a virtual xp on my dell win10 laptop, so today it was simply a matter of plugging it in.
IMG_20191201_135709.jpg


My JDM uzj100 doesn't do obdII so being able to query the ecu was invaluable for me! (I was confirming a failed ignition coil on cylinder number 2).

It also gives full access to AHC, etc. I haven't tried it on my diesel 90 series yet (kzj90) but I see no reason why it won't be able to at least read dtc's if I ever find it necessary?

So thanks to all who've contributed to this thread, and esp getco!

Cheers
Phil
 
Quick question: Would either of these tools allow you to monitor and adjust parameters and settings similar to Techstream? I realize Techstream is software, and I don’t know what software these tools use (and probably don’t wanna know since it’s Harbor Freight), but does anyone have any experience with them? Or is it just a glorified ScanGauge with the ability to also read ABS codes?

6B5B0CF5-356B-4FD0-85F3-F0FD122A0C5B.jpeg
 
Good luck to whoever reads this.
I hate to feel like I'm hijacking this thread but I tried downloading and installing the program but in order to unzip that file it's telling me I need a decryption password. How did you get around this?

EDIT: Ahh nevermind I figured it out..
 
Last edited:
That would actually be pretty good as the VirtualBox that is linked in the first post is running Windows XP in 32-bit if I remember correctly. Techstream is not a speedy program so there is no real need for an uber fast machine, you just need enough to either run the virtualbox provided or run the application alone which does not seem to be incredibly resource intensive.


A little update on this..

I ordered a VCI cable and disc from a seller on EBay that had pretty decent feedback and was one state away.

His listing was slightly higher than the China based sellers, but it came with a full sized CD (not the little Panda mini disc) that had both 32 and 64 bit versions as well as older versions and simple instructions.

Took about 15 minutes to install cause my little Sony laptop is pretty slow, but everything was straight forward and I was able to connect :)

Unfortunately, the battery in my laptop was running a bit low and I forgot to bring the power cable with me to work, so I had very little time to play with it.

It's version 13.00.022 and from what I saw listed in the options, it's good up to 2018 models.

I was able to connect and pull a radar fault code, but it was kinda slow

Just got home and when I fired it up, it asked me for the serial number again :confused:

Used the same one I used before, but now it just keeps asking for it
 
OK, just uninstalled and reinstalled and it's working again :cool:

Unfortunately, I'm not able to clear a couple of codes (C1A11 and B2090)

It actually says the DTC's are cleared when I try, but both codes still remain.

Tried clearing both with the engine on and off, but they're still there :(


According to this pdf on Pre-Collision adjustments I just found on Google, it states that 13.10.019 or later is required.




Perhaps this is why I'm not able to clear them? :confused:
 
A little update on this..

I ordered a VCI cable and disc from a seller on EBay that had pretty decent feedback and was one state away.

His listing was slightly higher than the China based sellers, but it came with a full sized CD (not the little Panda mini disc) that had both 32 and 64 bit versions as well as older versions and simple instructions.

Took about 15 minutes to install cause my little Sony laptop is pretty slow, but everything was straight forward and I was able to connect :)

Unfortunately, the battery in my laptop was running a bit low and I forgot to bring the power cable with me to work, so I had very little time to play with it.

It's version 13.00.022 and from what I saw listed in the options, it's good up to 2018 models.

I was able to connect and pull a radar fault code, but it was kinda slow

Just got home and when I fired it up, it asked me for the serial number again :confused:

Used the same one I used before, but now it just keeps asking for it
What OS are you installing this on?
Yesterday I got my Thinkpad Yoga 12 that has Win10 Pro on it and have been fighting with the install of the XHorse drivers since. Cannot get it to recognize the cable in techstream when I am manually installing the drivers (MVCI.msi file) so I know I am missing something somewhere. Most videos don't seem to have this issue as once the move/copy the files for the .msi file over to the appropriate folder in the Program Files (x86) folder they are able to use the MVCI Updater exe file to recognize the cable then the cable seems to show up in the VIM Selection in TIS.

So where am I missing a step?
 
What OS are you installing this on?

I'm running XP on an old mini notebook (Sony Vaio TX750)

20200305-190217.jpg



I started with version 13.00.022 (32 bit), but it was a bit laggy, so they sent me 12.30.017, which seems to run much smoother.


Still have an issue not being able to clear the a couple of codes though :(

Even though it says all DTC's are were cleared, the two still remain.

DTCnot-Clear1.jpg


DTCnot-Clear2.jpg
 
Can anyone please tell me what is this connector in the driver's foot well:
20200306_142737.jpg


It looks like OBD, but I am asking because I have a connector under the bonnet and it says DIAG or something on the cover.


20200219_094639(1).jpg

Could it be that the plug in engine bay is for some modules, while the one under the steering wheel is for others?
 
Drivers footwell is the OBDII port. One in the engine bay is a different diagnostics port, NOT OBDII. Techstream cable is plugged in the footwell.
 
Drivers footwell is the OBDII port. One in the engine bay is a different diagnostics port, NOT OBDII. Techstream cable is plugged in the footwell.
Thank you!

The cable I ordered has OBDII connector AND a certain 22 pin connector converter too. I am trying to figure out what did I pay extra $5 for. What can be done via that port and what can't.
 

Users who are viewing this thread

Back
Top Bottom