Can't Program TPMS IDs in Techstream: The Solution

The TLDR; trash the generic Mini-VCI cable you bought on Amazon/eBay and buy the VCX Nano.



What's up guys. I've been lurking around here for the past few months since I picked up a 2020 Taco. I recently installed a 3" lift, and naturally, got bigger tires (285/70/17) and new wheels. After a month long, painstaking experience with my local 4WP shop, I opted to not let them work on my truck and decided to do everything myself (minus the alignment and tire mount/balance).

Now. One of the many problems I had with 4WP, including waiting 4 days for my tires to be mounted and balanced, was that I had asked them to scan the new TPMS sensors that they installed so I could program the ECU w/techstream. I was told that's not how the TPMS (system) works and that "the truck will learn the TPMS sensor IDs itself". As a former diesel mechanic, I knew this to be bullshit, despite my very limited interaction w/the TPMS. This issue is what would be solely responsible for the rabbit hole that I would be diving down...that and my spitefulness.

So. Now begins the fun.

I found the model of the TPMS sensors that 4WP installed (Oro-Tek PDQ) and purchased a scanner/programmer that was compatible w/them (ATEQ VT37). Now, this part isn't technically needed if you were able to obtain the sensor ID's from the physical sensor itself or by asking a COMPETENT tire shop to write them down for you when they mount/balance.

I then, like many others, purchased a Mini-VCI cable off Amazon. It's just a cable right? Ha. No.

So I install the drivers for the cable and select the appropriate VIM on techsteam. I then connect to my truck via techstream and noticed that the vehicle information doesn't auto-populate like on the Mac/Volvo/Hino/Mitsu software I've used in the past. So, I manually inputted it, not thinking much of it.



I then go into the Tire Pressure Monitoring System and open the Utility to program the new TPMS sensor IDs input the IDs which I scanned off the sensors...and get this error:



At this point, I tried changing and reverting other settings from within techstream. They all worked fine. I then tried 3-4 other releases of techstream. Still won't work. After a crap ton of searching I never found a definitive answer. I saw the TSB about jumping pins on the OBDII plug, but noticed that one of the spots didn't even have a pin in it, so that was useless. I saw a few "your cable is bad" comments and several "I tried multiple of the same Mini-VCI cables" responses. I then found someone who had posted something about a "VXDIAG VCX Nano" claiming that it worked for them. I then found a VCX Nano for Toyota (it appears each manufacturer has it's own model) on Amazon for $100. That's ridiculous I'm not paying that! Well, I figured if this is what it costs to have something that actually works then I'll try it. I'll just return it if it doesn't work.

It arrived today and I once again found myself installing drivers and setting the VIM to what I now see as "Toyota J2534". This is beginning to look promising. I launch techstream and connect the truck and the first thing I notice is that it has auto-populated my VIN, model code, and vehicle spec. It also loaded much faster than the Mini-VCI cable.



Jump over to the TPMS menu again, try changing the sensor IDs and...


...Well hot dang...it actually worked. Proof below if you need more convincing to spend the money on a better cable:





As you can see, using a very scientific numbering scheme for my new sensors, it worked.

Morale of the story. I spent way too much time and money, purely out of spite for my local 4WP shop and for the future of tire changing freedom. But I hope that this post will help someone else who is struggling to figure out why they cannot program their TPMS sensor IDs with techstream.

Links to buy the VXDIAG VCX-Nano:

VXDIAG VCX Nano OBD2 for Toyota TIS Diagnostic Scanner Compatible for Toyota Software Programming Tool SAE J2534 WiFi Version

Amazon
VXDiag Direct (they also have a link to techstream v17 apparently)
The VXDiag Software/Drivers

I also realize this came off like one big sales pitch. I'm just happy I finally found a solution and if I can save people from spending $50 on a cheap POS cable, then so be it.

 

In to re-read this tonight

 

Nicely done!

We Neanderthals, OTOH, build TPMS bombs.

 

What was your total cost?

 

nice any links to the tech stream or you used the included software. I was looking into the same thing. I think I have OEM sensors or at least I think. Similar experience with 4WP they could program wheels if their live depends on it. Nothing but crap. I may have to pick up the same. If the ATEQ VT37 works for other sensors then sound like the way to go. I’d rather buy and spend then take it ti 4WP. Also had my wheel bust studs after they touched it.

 

See the 1st Post of the ECU Update thread.

 

$99.99 for the VCX Nano
$153.67 for the VT37
$53.99 for the Mini-VCI cable
So yea, over $300 purely out of spite/anger. But I'm also slowly gathering everything I need to do my own tire installs and alignments. And like I said, you don't necessarily NEED the TPMS programmer/scanner. The important thing in that list is the VCX Nano. Without it, you will not be able to program the TPMS ECU (at least w/3rd gens). Don't waste your money on the Mini-VCI. There are other brands out there as well, but from my research, they were far more expensive. The other option is to buy a $300+ TPMS programmer/scanner that comes with an OBDII cable. Should be able to program everything there.

The link to the VXDiag Drivers/Software has both V16 and V17. Or as @tonered said, it's in the ECU Update thread, link is in his sig. Also, I don't recommend installing it on a computer you use everyday. You'll need to disable the windows virus protection or it'll delete files it marks as malware. I use an old lenovo thinkpad that I had bought on eBay 2 years ago for use in my garage. Think I paid like $50-$60 for it. eBay is great for finding that kind of stuff.

You can probably get away with a scanner that just reads the IDs, or see if a tire shop can scan them for you real quick and write them down. They're a simple 7 digit hexadecimal code. You'll need to know the sensor brand before you buy a programmer, as not all programmers are compatible with all brands (such as the Autel programmers). However, as just a scanner tool, I believe all scanners can read any sensor. I could be wrong, but they all work off the same frequency (315mhz) so I don't see why not. Also, reprogramming the physical sensors only works on reprogrammable sensors. It will not work on OEM ones. So, you don't necessarily need to drop $150 on the VT37. I bought it because I plan on doing all of my own tire/alignment work in the future because I don't trust most of the shops in my area and the good ones are always backed up.

I guess 4WP shops just aren't that great in general then. It's a shame. The one near me just appears like the owner/manager has no idea how to actually run a shop. That coupled with their apparent high turn over rate made for the worse service I've ever had. The sales guy "forgot" about me multiple times despite me being in constant contact with him after they messed up my order several times, didn't give me my entire order twice, and somehow mounted 1 wrong tire out of 5. They did try to make things right and gave me an alignment for free after I installed the lift myself. But I feel that's hardly equal considering it took me a month to get my lift kit, tires, and wheels. I about snapped when they told me you can't just scan the sensors to pull a number off of them because they don't come with IDs. Lesson learned. They had the audacity to ask me to leave a positive review on their google page lol.

 

The reason I asked is that you could have gotten a proper Tactrix cable for $169 and
a pack of ITM tpms for about $130 for the same money and call it a day.
ITM tpms are popular in toyota crowd and come programmed with IDs.

 

Yea, that would have been nice, however, at the time I was under the impression that the VCI-Mini would've worked. So when I started down this journey, I was only $50 in. 4WP doesn't sell ITM sensors, nor had I heard of em before all of this. The plan was that this would be a one stop shop; have 4WP write down the IDs for me and I'd just plug the computer in and program it and be done with it. Besides, there doesn't seem to be any issues with the sensors I'm running now. They're working fine. They did in fact come pre-programmed with IDs, the issue was that 4WP refused to comprehend that. I had cloned them to my OEM IDs when I got the scanner because I was pulling my hair out figuring out how to program the ECU. I then changed the IDs because I still have the OEM ones and would like to use them for a snow tire.

So I will say, you can drop $170 on the Tactrix, or you can drop $100 on the VCX Nano. Just don't drop any money on the cheap VCI-Mini cables. And depending on your circumstances, you may or may not need to get a scanner/programmer. If you know the IDs, then you shouldn't need the scanner.

 

Great story! I think we've all done that! BTW- never let the idiots at Firestone touch your TPMS system either. They hosed mine!!! I actually got the local NAPA guy to reset them. They had the tool and actually knew how to use it (For $25!).

 

i have been wondering if the taco’s computer / tpms is capable of accepting 5 wheels, or if only 4 can be programmed in. The VT37 does show 5, and i wanted to rotate the same size and type spare.
Only 4 wheels displayed in carista and on my head unit screen, but i wondered if 5 would appear if techstream allowed them to be added?

 

unsure on the 3rd gens but 2nd gens only allow 4 wheels.

 

3rd gen only allows for 4 programmed.

 

My 2007 Prerunner has 5 one in the spare, Not sure where you got that info but is incorrect.

 

Did you try in Techstream or another way? Which year or trim of 3rd gen [2016 OR ?] /version of techstream?

Another possibility is different support depending on the year and trim level???

 

I use Techstream, but it's a pretty well known fact that NO 3rd gen to date has supported a 5th sensor.

The 2nd gen DID, though I don't know if it was every one or not.

 

Maybe it changed in later years. We could not get it to program. But also could have mixed up it being 3rd gens. I haven't had my tpms working in prob 5 years at this point.

 

some of the early 2nd gen years had the capability of 5 programmed sensors. For most 2nd gens though 2008+? 2009+? They only support 4.

 

ahh yes thank you that's what I thought.

 

Oh shucks, for sure the factory spare had no sensor inside, so that was not a good sign, but I thought the computer might have a hidden capability for 5 wheels somewhere in the settings, even if it's rarely enabled/used.