Techstream answers needed
08-02-23, 06:19 PM
#1
Driver
Thread Starter
Techstream answers needed
I've been searching these forms for a while trying to understand Techstream and what to install it on. The more I read the more questions I have. I've heard it works best on a 32bit machine so I found a Dell windows 7 / 32 bit machine. I went with Techstream V18.00.008 I got a 5000 day activation key for it. I still have issues getting it to connect to the car. With the laptop I have is V18.00.008 the one to be using? What does this version allow you to do as opposed to older versions? I guess I'm looking for a tried and true way of getting this to work? Anyone have any proven methods that work?
08-02-23, 08:44 PM
#2
Lexus Test Driver
The newer versions may be for newer models…I run TechStream on a 64 bit machine using a virtual version of TSv12…no issues with my 2007 SC430.
08-03-23, 08:31 AM
#3
I didn't know that it has a 32-bit limit. I'm running mine on a 64-bit older intel machine using a VXdiag nano. I think my techstream version is 16.00 something. It took me a long time to get it working but it's worth the time.
08-03-23, 11:29 AM
#4
Pole Position
If techstream is working but not talking to your car, I would guess you did not load the special driver for your cable. It probably came on a disc.
08-03-23, 11:42 AM
#5
Pole Position
I've been searching these forms for a while trying to understand Techstream and what to install it on. The more I read the more questions I have. I've heard it works best on a 32bit machine so I found a Dell windows 7 / 32 bit machine. I went with Techstream V18.00.008 I got a 5000 day activation key for it. I still have issues getting it to connect to the car. With the laptop I have is V18.00.008 the one to be using? What does this version allow you to do as opposed to older versions? I guess I'm looking for a tried and true way of getting this to work? Anyone have any proven methods that work?
1. Make sure you install TechStream to a 32-bit Window. It WILL install to the 64-bit Window but WILL NOT CONNECT to the SC VIM. If you want to use it to the 64-bit Window, you will have to modify the registry and swap some files. The easiest way to install to the 64-bit Window is to install VIRTUAL 32-bit Window.
2. Use Cable firmware Ver 1.4 for older SC, and Ver 2.04 for 06+ SC. They are some what not interchange. You will run into some functions.
3. TechStream software newer versions are for newer model vehicles. For the SC, Ver 10 and up is fine.
4. TechStream does not require internet connection, so disconnect your WiFi when installing or using. You might run into the activation issue if your computer connects to Toyota homepage ( not sure it’s true)
Read this thread:
https://www.clublexus.com/forums/sc4...er-1-41-a.html
And this:
https://www.clublexus.com/forums/sc4...solutions.html
Hope it helps.
Last edited by GmanSC; 08-03-23 at 12:06 PM.
08-03-23, 03:18 PM
#6
Driver
Thread Starter
Great replies! Mine is a 2004 SC. I have a Dell win7/32 bit machine running V18.00.008. I believe my cable is the earlier 1.4. Techstream loaded just fine and I plugged in the activation key. I'm going to attempt hooking up to the car in the morning. Thanks.
08-04-23, 05:36 AM
#8
Lexus Test Driver
the links are in the description under the video. You need to open the video in YouTube to see the description.
Last edited by Bgw70; 10-23-23 at 04:36 AM.
08-04-23, 12:28 PM
#9
Driver
Thread Starter
if ya cannot figure it out, just load this on any laptop, 32 or 64 bit, new included. It creates a virtual window running V12 on WinXP and will it will work just fine on your 2004 SC430.
https://www.youtube.com/watch?v=OyBwz3GT2g8
https://www.youtube.com/watch?v=OyBwz3GT2g8
08-06-23, 04:44 PM
#10
Lexus Test Driver
The following users liked this post:
DshngDaryl (08-07-23)
08-20-23, 03:56 PM
#11
Driver
Thread Starter
Maybe I'm just frustrated with trying to get Techstream to work but I gave up and went and bought the BlueDriver bluetooth scanner. This thing is slick.So simple to use. Look into it. About $100.
The following users liked this post:
Oldsig (10-29-23)
08-26-23, 08:27 PM
#12
Driver School Candidate
I bought VXDiag Nano scanner from Amazon for ~$90 and installed it on my Windows10 Laptop with VirtualBox running 32bit Windows10. Took me about 2 hours to install everything and about an hour to do full scan on the car for DTCs.
The following users liked this post:
Oldsig (10-29-23)
08-28-23, 07:33 PM
#13
Another vote here for using virtual box plus the 32bit XP image with v12 Techstream and the cable drivers pre-installed.
I used an old Dell i5 laptop with a clean install of Win 10 64bit, downloaded the files from ih8mud referenced above, installed virtual box, loaded and started the image. Plug in the cable and then you have to attach the usb device so it sees the cable but that’s the only non obvious step (right click the little usb plug on the bottom right and select the cable). You can use the firmware updater tool to verify the cable firmware and function by pressing device info. Start the Techstream and another clue is you should see the driver version displayed at the bottom of the program window… 1.4.7, etc.
With my 2005 I was able to do the following…
1.4.1 cable - connect to car and recognizes model, vin, etc., run full health check, access customizable options, see live data for the tpms, etc.
I also previously purchased a 2.0.4 cable. My understanding from reading a lot of threads was that this cable would have issues or limited functionality with a < 2006 vehicle like not seeing live data but I was able to do everything I did with the 1.4.1 cable successfully on my 2005 using the 2.0.4 cable.
My 1.4.1 cable came with a copy of v18 Techstream so I decided to clone the v12 image in virtual box. When I ran the v18 installer, it upgraded the v12 install and kept the default settings. This version uses a “launcher” file to start the app. You just copy this to the Techstream install directory, create a desktop link and start the app this way. If you don’t you will be prompted for a key.
I was able to connect to my 2005 with v18, using both cables and although I didn’t test as deeply as I did with v12, I didn’t notice anything obviously missing and was able to see real time tpms data, turn off the telescopic steering wheel, etc.
I can’t vouch for anything but 2005 and I didn’t try every option but I saw no functional difference between the cables and v12 and v18 of Techstream. However, I did see missing functionality if I connected to the car with the key in acc and not on. I’m assuming some of the ecu’s only communicate when the key is in the on position.
Note that I also created an adapter cable as detailed in other posts and removed the connections not needed to avoid the vsc light and clearing issue.
I used an old Dell i5 laptop with a clean install of Win 10 64bit, downloaded the files from ih8mud referenced above, installed virtual box, loaded and started the image. Plug in the cable and then you have to attach the usb device so it sees the cable but that’s the only non obvious step (right click the little usb plug on the bottom right and select the cable). You can use the firmware updater tool to verify the cable firmware and function by pressing device info. Start the Techstream and another clue is you should see the driver version displayed at the bottom of the program window… 1.4.7, etc.
With my 2005 I was able to do the following…
1.4.1 cable - connect to car and recognizes model, vin, etc., run full health check, access customizable options, see live data for the tpms, etc.
I also previously purchased a 2.0.4 cable. My understanding from reading a lot of threads was that this cable would have issues or limited functionality with a < 2006 vehicle like not seeing live data but I was able to do everything I did with the 1.4.1 cable successfully on my 2005 using the 2.0.4 cable.
My 1.4.1 cable came with a copy of v18 Techstream so I decided to clone the v12 image in virtual box. When I ran the v18 installer, it upgraded the v12 install and kept the default settings. This version uses a “launcher” file to start the app. You just copy this to the Techstream install directory, create a desktop link and start the app this way. If you don’t you will be prompted for a key.
I was able to connect to my 2005 with v18, using both cables and although I didn’t test as deeply as I did with v12, I didn’t notice anything obviously missing and was able to see real time tpms data, turn off the telescopic steering wheel, etc.
I can’t vouch for anything but 2005 and I didn’t try every option but I saw no functional difference between the cables and v12 and v18 of Techstream. However, I did see missing functionality if I connected to the car with the key in acc and not on. I’m assuming some of the ecu’s only communicate when the key is in the on position.
Note that I also created an adapter cable as detailed in other posts and removed the connections not needed to avoid the vsc light and clearing issue.
09-16-23, 08:06 AM
#14
I have already have the Bluedriver for my other cars and it does work well but I don't think it will access the functions and different settings in the car. I have not plugged it in yet though.
09-16-23, 08:07 AM
#15
Another vote here for using virtual box plus the 32bit XP image with v12 Techstream and the cable drivers pre-installed.
I used an old Dell i5 laptop with a clean install of Win 10 64bit, downloaded the files from ih8mud referenced above, installed virtual box, loaded and started the image. Plug in the cable and then you have to attach the usb device so it sees the cable but that’s the only non obvious step (right click the little usb plug on the bottom right and select the cable). You can use the firmware updater tool to verify the cable firmware and function by pressing device info. Start the Techstream and another clue is you should see the driver version displayed at the bottom of the program window… 1.4.7, etc.
With my 2005 I was able to do the following…
1.4.1 cable - connect to car and recognizes model, vin, etc., run full health check, access customizable options, see live data for the tpms, etc.
I also previously purchased a 2.0.4 cable. My understanding from reading a lot of threads was that this cable would have issues or limited functionality with a < 2006 vehicle like not seeing live data but I was able to do everything I did with the 1.4.1 cable successfully on my 2005 using the 2.0.4 cable.
My 1.4.1 cable came with a copy of v18 Techstream so I decided to clone the v12 image in virtual box. When I ran the v18 installer, it upgraded the v12 install and kept the default settings. This version uses a “launcher” file to start the app. You just copy this to the Techstream install directory, create a desktop link and start the app this way. If you don’t you will be prompted for a key.
I was able to connect to my 2005 with v18, using both cables and although I didn’t test as deeply as I did with v12, I didn’t notice anything obviously missing and was able to see real time tpms data, turn off the telescopic steering wheel, etc.
I can’t vouch for anything but 2005 and I didn’t try every option but I saw no functional difference between the cables and v12 and v18 of Techstream. However, I did see missing functionality if I connected to the car with the key in acc and not on. I’m assuming some of the ecu’s only communicate when the key is in the on position.
Note that I also created an adapter cable as detailed in other posts and removed the connections not needed to avoid the vsc light and clearing issue.
I used an old Dell i5 laptop with a clean install of Win 10 64bit, downloaded the files from ih8mud referenced above, installed virtual box, loaded and started the image. Plug in the cable and then you have to attach the usb device so it sees the cable but that’s the only non obvious step (right click the little usb plug on the bottom right and select the cable). You can use the firmware updater tool to verify the cable firmware and function by pressing device info. Start the Techstream and another clue is you should see the driver version displayed at the bottom of the program window… 1.4.7, etc.
With my 2005 I was able to do the following…
1.4.1 cable - connect to car and recognizes model, vin, etc., run full health check, access customizable options, see live data for the tpms, etc.
I also previously purchased a 2.0.4 cable. My understanding from reading a lot of threads was that this cable would have issues or limited functionality with a < 2006 vehicle like not seeing live data but I was able to do everything I did with the 1.4.1 cable successfully on my 2005 using the 2.0.4 cable.
My 1.4.1 cable came with a copy of v18 Techstream so I decided to clone the v12 image in virtual box. When I ran the v18 installer, it upgraded the v12 install and kept the default settings. This version uses a “launcher” file to start the app. You just copy this to the Techstream install directory, create a desktop link and start the app this way. If you don’t you will be prompted for a key.
I was able to connect to my 2005 with v18, using both cables and although I didn’t test as deeply as I did with v12, I didn’t notice anything obviously missing and was able to see real time tpms data, turn off the telescopic steering wheel, etc.
I can’t vouch for anything but 2005 and I didn’t try every option but I saw no functional difference between the cables and v12 and v18 of Techstream. However, I did see missing functionality if I connected to the car with the key in acc and not on. I’m assuming some of the ecu’s only communicate when the key is in the on position.
Note that I also created an adapter cable as detailed in other posts and removed the connections not needed to avoid the vsc light and clearing issue.
