Diagnose Toyota x1001 and x1002 Codes with Techstream

 How-to: Determine Toyota Maximum Engine Speed History (RPM) with Techstream software.

 

Disclaimer:

It is not our work. Credit to Pyrenees from GT86 forum.

 

Background: 

A member drives a 2023 Toyota 86 6MT, ~15k miles. Toyota mechanic has pulled the code x1002 and x1001 from the ECU and these codes indicate and “over-rev”. They cannot or will not explain what that means and if it is the policy for those codes to void the engine. Toyota denying warranty claim due to supposed abuse and the x1001 and x1002 codes being given as “over-rev”

It seems like this means they are accusing me of “money shifting” the car and destroying the engine, which violates the abuse clause in the GR86 warranty.

 

Purpose:

You can access x1001 and x1002 VCH/RoB codes as well as a bunch of other misc data from your GT86 with Techstream. Share it here in case people wanted to check their own cars.

 

 

Techstream Version & Installation

He used to utilize Techstream v14 for Toyota Sienna and LX470, but it was simply too old a version for the 2022/2023 GR86, so he would like v18 software for personal use and set it up.

He successfully installed Techstream v18.00.008 on an old Thinkpad with Windows 7 Pro after spending a ton of time on it.

The main thing to consider is that the drivers for Techsteam J2534 cable (Mini VCI cable, vxdiag vcx nano for Toyota, Xhorse MVCI pro etc) the interface between your OBDII port and the USB port on your laptop) are 32-BIT.

 

So this means that your best bet is to use a 32-BIT version of Windows, which is NOT common. Most Windows versions are 64-bit unless it’s for a particular reason like this. Anyway, you need to have patience and at least some level of technical skill to get it installed.

Once Techstream is installed, connect the cable to the OBDII port and the USB port on your laptop. You might get a “cannot connect to VIM” error or something like that when use the mini vci cable. That usually means your USB port setup or Mini-VCI driver isn’t working. Keep one other thing in mind, when you install the Mini-VCI cable driver, MAKE SURE the USB cable is plugged in during that process, not after.

 

 

How to Determine RPM?

x1001 and x1002 are individual codes, the first is Maximum Vehicle Speed and the second is Maximum Engine Speed.  x1001 shouldn’t mean a thing warranty-wise. x1002 is the one that they are looking for.

In Techstream, when the main page loads there will be a row of tabs across the top, System Select is the primary tab. Initially, you have to click on all of the individual ECUs to access them (you can run the health check to do this as well). Unless you are making active changes, poking around is unlikely to cause a problem.

If you’re looking for the supposed engine over-rev codes, click on the Engine Control System ECU. You can see live data there. Go to the “stored data” tab across the top, and there will be an option for the VCH (vehicle control history) and RoB (records of behavior). You’ll have to shut the engine off and put it back in ignition mode (2nd position/press), and then it will pull the data. You can also pull Health Check data in a similar way, but I found the screenshots to be more helpful than the exported CSV file, which was awkward to navigate though.

Without further ado, this is what the sanitized x1001 and x1002 data looks like from a 2022 GT86. screenshots are attached:

Engine Control System

Vch Rob

Max Engine Speed

Max Vehicle Speed

Health Check

It’s actually rather informative. It keeps the last four “highest” values with other data like odometer value. -3 is the oldest data column, 0 is the most recent. This seems to correlate with the elapsed time. Clutch switch “on” means the clutch is depressed (and if you think about how the clutch has to be depressed to start the car, this also makes sense). Current key cycle at the top, but the key cycle within the data was the key cycle where the data snapshot was collected. Then there’s a whole health check page you can poke around on.

 

Hope it helps.

www.obdii365.com

How to Choose a Techstream Cable for K-line Toyota?

 As titled, what is a better Techstream cable for K-line Toyota models?

 

Here is the clue.

 

1.Mini VCI cable

Firmware 1.4.1: The latest 1.4.1 firmware interfaces have both CAN chip (xx1050) and K-Line chip. so they may full support these 2 protocols for Toyotas since 1996+. Only missing VPW chip (and si9241a for L-Line).

Firmware 2.0.4: 2.0.4 cable is now only available in ali or ebay, they are clones of xhorse mini vci j2534. The geniune cable is discontinued. The clone cable is twice as expensive as 1.4.1 cable.  The Mini vci clone also has bugs in K-line Toyota. If you need to troubleshoot K-line Toyota/Lexus, 1.4.1 is fine.

 

Read more:

Toyota Techstream Cable: Mini VCI V1.4.1 vs V2.0.4

 

2.

Xhorse MVCI Pro

original XHORSE MVCI PRO J2534 (XDMVJ0) cable diagnose Toyota Land Cruiser 100 (2002-2005). TIS detects cable, but is not able to connect to vehicle, diagnose looks like this:

The issue is the K-line, because apparently the K-line is the only protocol in Land Cruiser 100.

Cable is updated to latest firmware (1.2.5)
Drivers for Toyota installed
Tested on TIS 17.00.xx and also on latest 18.00.xx, same result.

But sometimes the early versions of TIS will work where the later version won’t.
Ver 10 or 12 worked for me.

 

 

3. Old MVCI 1.4.3 cable

the old Chinese MVCI 1.4.3 cable is working, so TIS is fine

4.

VXDIAG VCX NANO for Toyota

VXDIAG only has partial K-Line support. It works better on 2005 up Toyota models.

We had some other customers reported that vcx nano failed to test on some 2002 2003 Toyota with K-line protocol.

 

vxdiag does not work on 2002 SC either. It works fine with 2007 SC. 

It is a known problem of vxdiag, failed to work on 02 03 Toyota K-line protocols.

But vxdiag can be used as j2534 passthru device for official techstream subscription.

With the Techstream legal subscription, you can do some software updates, sensor calibration and other things. You can never do it with the cheap cables.

 

 

5. Tactrix Openport 2.0

The Tactrix is fine for CAN bus devices, but has problems with some K-Line devices.

The hardware looks like it’s up to the job, and a driver update could solve the Toyota specific problems.

 

 

In sum:

K-line seems to only be required for older vehicles. It’s support for active tests that you need. If need to troubleshoot old k-line models, get the mini vci cable.

If don’t have k-line Toyota, get the mvci pro or vxdiag.

Both mini vci and mvci pro don’t do reprogram TPMS sensors when switching wheels, replacing sensors, etc. but vxdiag performs well. The hardware cable solution most frequently mentioned there is to get a VXDIAG VCX NANO.

Mini VCI Techstream V12 on Windows 10 64bit

I have a Mini-VCI J2534 cable which worked happily with my Techstream 10 install on 64 bit Windows 7, after some faffing. Anyway, had to give that laptop back last month when I left the job I'd acquired it from.

Windows 10 has a few more challenges. You need at least Techstream 12 (you could hack about with the registry to get Techstream 10 to work, nit don't waste your time). And you need to get Windows 10 to load 64 bit drivers for the cable. Windows 10 really doesn't want to let you load old, unsigned drivers. You can do it, but it'll make it hard for you.

So a bit of googling and a bit of trial and error and these steps seem to work.

http://blog.obdii365.com/2017/12/03/toyota-techstream-12-30-017-download-and-install/
Follow the steps under : Techstream install Windows 10.

Step 2. You want to run this from the cmd prompt as the admin user. (type "cmd" in the Type here to search box in the bottom left of your screen)

Step 4. Copy all of the contents of the file in the link to notepad (dont copy and paste from the steps, there are extra spaces in there), and save as filename.reg

You then import that file using Regisitry Editor (type "registry" in the Type here to search box). Select the import option from the File menu (top of the screen).

Some instructions suggest running a firmware update tool to confirm the cable install has worked; but the tool doesn't work in Windows 10. Don't waste your time like I did!

Step 7. You can get Techstream 12 online. I did virus check this, but .. at your own risk. To extract this file you need to copy it to the desktop then open it with a zip program, such as Winzip. You may need to download that from somewhere.

Check the instructions.txt in the unzipped files. Theres a few simple steps to complete the install.



All working fine now. 

How to Get Mini VCI COM3 Recognized by Mac Pro VMware

 If anybody is using a HOST (meaning your main computer you are using) Mac machine and a Windows VM using VirtualBox, here's how to also get your PORT(COM 3) recognized in the Windows VM. This is important because the cable I ordered needs the drivers for the USB AND the PORT(COM 3) installed. If your Mini VCI cable does not require for this, then please disregard.

On your host mac machine:
1. Plug in the cable to your computer
2. Open terminal
3. Type: ls /dev/tty.*
4. Press enter
5. You should see something like this listed: "/dev/tty.usbserial-A6007dAe". Copy this down.

On your VirtualBox with your cable plugged in:
1. Right click your VM and click "settings"
2. Click "ports" at the top
3. Click "serial ports"
4. Click "port 3"
5. Click the checkbox so that there is a check for "Enable Serial Port"
6. Where it says "Path/Address" paste in what you copied above ^ (/dev/tty.usbserial-A6007dAe)
7. This is the information you should have shown in the picture below
8. Start your VM
9. On the top of your VM, click "devices" -> "usb" -> click enable M-VCI
10. Go to your windows search bar and search and open "Device manager". Or, right click my computer, right click "C drive" and click settings. On the left you will see device manager
11. After opening device manager, click "PORT" and you should see "PORT(COM 3) there or something named similar.
12. In device manager, click USB and you should see your USB enabled there as well.

Hope this helps.


Verified working for Mac 10.14.13 and Windows 7 x64 VM and cable version 1.4.1
2005 LX470

Mini VCI Techstream Bleed the Brakes on Toyota

 Tutorial: how to bleed the Brakes on your Toyota/Lexus using Toyota Techstream software on a laptop.

So many ways to bleed brakes, just adding this one to the tool belt. Seems like an efficient way to push a higher volume of fluid so may be a good option for a full flush, especially when time is short.

 

Model example: Land cruiser LC200 series.

Background:

Finish a complete break upgrade on a Land cruiser 200 series.

 

Procedure:

Get a cheap mini vci cable and proper software version.

Here v12 (older version has the Unitiny feature) was used and set it up on VMware Win7 32bit.

Insert mini vci obd2 cable into car

Connect the vehicle, now go into the ABS vehicle stability control on traction

Go to Unitiny->Air Bleeding

It tells us here that this function is used to purge air from the hydraulic braking system

and then we just follow our prompts.

I am going to start with the rear left line which is the furthest line from the master cylinder.

i’ll hit the next button and it says here perform the following operations.

open the bleeder plug.

you see the bleeder plug is open.

because we’ve got gravity dripping fluid through it.

press the next and wait for the timer and it says note do not depress the brake pedal.

now we’ll hit our next button and you can hear funky stuff happening under the bonnet.

now it says please perform the following operations close the bleeder plug

close off our bleeder pug press next

wait for timer

hit our next button and it says resetting what that actual resetting is i’m not sure but it must have something to do with the master cylinder.

air bleed is complete. press next to select another line or press exit to exit the function.

i’m going to hit next i’m going to do that right rear line again and i will show you what it looks like at the master cylinder.

here’s what it looks like at the wheel cylinder

and our air bleed is complete on that right rear line.
now i will continue to  do this process i will repeat it about five times per wheel cylinder just to make sure that i get all of that air out.

i’ve got plenty of fluid i’m pushing dot four fluid through it now.

now the front left is a little bit different in that it asks you to hold the brake pedal

then press next let the timer run its course and then release the brake pedal and press next that’s quite interesting so it looks like it doesn’t actually bleed fluid through the wheel cylinder

and let’s try the front right same thing.

press and hold the brake pedal hit next, without releasing the bleeder plug then release the brake pedal and hit next.

so on those two front wheel cylinders i will open the bleeder plugs and just let gravity bleed through there and push any air out that might be sitting in those wheel cylinders.

CAUTION: If air is bled without using the Techstream,damage or accidents may result. Therefore, always use the Techstream when bleeding air​.
Worked great for me.

http://blog.obdii365.com/2023/05/16/bleed-the-brakes-on-toyota-with-mini-vci-techstream/

Mini VCI Tecshtream no Proace in Vehicle List Solution

 Some users reported that they got a problem connecting Toyota Proace 2017+ with Techstream. There is no Proace in the vehicle list. Try different techstream cables (mini vci, mangoose, vxdiag vcx nano toyota) and software versions, all the same.

Here is the clue.

Toyota Proace van is based on a PSA platform. Toyota Proace is a Peugeot Expert and Citroen Jumpy. PSA made Proace for Toyota.

For ProAce project TME has decided the adoption of PSA technical documentation and diagnostic tester.

So you cannot find Proace in Techstream. You will need Diagbox.

Techstream is for all Toyota and Lexus except Supra and ProAce. Supra needs Toyota ISTA* and Proace requires diagbox.

 

Where to download/get Diagbox for Proace?

Check and download ISTA & Diagbox license for Supra and Proace here.

*Toyota ISTA (which is based on the BMW ISTA) is a seperate software package from Techstream but it does need Techstream installed. It’s specifically for the new Toyota Supras since they’re made by BMW and have different ECUs.

How to Configure Vediamo with Mini VCI Cable?

 How to configure Vediamo for J2534 Devices (Here mini vci j2534 specifically).

If you do not know what anything in the title means, you probably should not try anything on this post.

Notes:
1. We will not be providing a link to download Vediamo or any J2534 products, just explaining how to configure the program settings in order to connect to your car.
2. Vediamo is a programming software that allows you to edit the code within the different onboard computers.  This post will only focus on configuring a certain cable – Mini VCI J2534 with the program.

3. You are at your own risk. We are not responsible for the damage.

STEP 1.
Get an activated version of Vediamo 4.2. HAS TO BE 4.2 otherwise you will not be able to configure a J2534 device like openport2.0 or MVCI with the program. You can find links to cracked versions on MHHAuto or you can buy a copy on ebay with a keygen for around $10. Not sure how trustworthy ebay is.

We have explained why only Vediamo 4.2 can be used with j2534 and how to configure 4.2 with openport in the previous post.

How to Configure Vediamo with OpenPort 2.0?

STEP2.
Buy a Mini VCI cable. I got mine on for less than $30. Spend as much or as little as you would like in order to make yourself feel comfortable with attaching it to your benz.

STEP3.
Plug in your MVCI and download any necessary drivers. If your computer recognizes it in Device manager as “Serial bus converter” then you do not need to use any install disk that came with the cable. It will be in Device manager – Universal Serial Bus controllers. There should also be another tab in device manager that says “Serial ports” and have your device listed along with “(COM3)”. Make sure it is COM3, otherwise you can right click, go to properties, and change to COM3.

STEP4.
Download Autokent MVCI MultiDriver x64 2.0.1. This can be found online (search our blog), you will have to turn off threat/virus protection in order to get it to work. Go through the install process and run the application as admin. The Splash screen should be a picture of a dude holding a gun with the words “Autokent” across the bottom. When prompted, select 2.0.1 from the dropdown menu and install.

STEP5.
Now comes the configuring part. Open your Vediamo file location (probably C:->ProgamFilesx86->Vediamo.
Then go to Caesar->driver, and right click on “slave”. Go to properties, security tab at the top, edit, add, and then type “everyone” in the box, and select check names on the right side. Then check off the boxes to allow everything. This will allow you to edit the file.

STEP6.
Open the “slave” file, scroll down to the “Part J” section. Under the “Device name:” section. Change whatever is inside the quotes to The name of the autokent driver you previously installed. The name should be “XHorse – MVCI Autokent-X64 – 2.0.1”. But, to be sure, you can find the driver name in Registry editor (Windows button, regedit). The location of the driver may be different, but you can find it by going to HKEY_LOCAL_MACHINE -> SOFTWARE and then doing ctrl+f and searching for “Autokent” and finding the next instance. You can then right click on the folder with that title, click rename, then ctrl+c to copy it exactly and paste it into the part J configuration device name in slave.ini. Save the slave file and close.

STEP7.
Open Vediamo start center, on Vediamo Server, select update. Uncheck all the boxes except for “Part J” and “Pinmapping”. Select Update. If prompted, select the Autokent MVCI driver from the dialog box as your part J. When working correctly, you should have a box that says “Part xxxxx” with some number as the x’s underneath the Vediamo server box.

STEP8.
Select the notepad icon 2 from the left at the tools window on the bottom right of the start center. Select Ecoute options -> format of the variant code string -> change decimal to hex.
Everything should be properly set up now. You will need to have the proper .CBF files (look up vediamodata downloads) and from there you can find youtube videos on the possibilities for working on the computer modules on your car.

IMPORTANT NOTE – When connecting to your vehicle, there will be a tab at the top left that shows a connection icon. It will default to saying “KLine1 Communications”. Right click on this, select properties, and then from the dropdown menu, select CANHS. You will have to do this every time otherwise you will not be able to connect to your car properly.

Openport Techstream V15 Review on Corolla

 I order a Tactrix Openport 2.0 clone with gold connector from a well-known Chinese online store (obdii365.com). Toyota techstream V15.30.026 downloaded from Rutracker. 

We put the drivers from the kit with an adapter, then install techstream.

Select vehicle.

Click Health Check and all modules are scanned for availability and errors

picture from the last scan, since erasing errors, the mileage is about 300 km

with such errors passed the first scan

after returning to the System select tab, it becomes clear which modules are polled and which are not (with *)

then I reveal the content of Customise, here is what we can customize,
I set myself a consumption in liters per 100 km, so it’s more familiar

You can see a lot of customize setting options, 

disable/enable slide roof open warning

disable/enable key remind sound

disable/enable side seatbelt warning buzzer

disable/enable front passenger side seatbelt warning buzzer

disable/enable tail remin buzzer

disable/enable refrigerant shortage check

disable/enable ODO display time after IG off setting

disable/enable lighting time

disable/enable I/L when ACC off

disable/enable I/L ON W/Door Key Unlock

and much more. 

Next Utility is tests or module calibrations