Has anyone successfully programmed TPMS IDs on 2015+ using MiniVCI (1 Viewer)

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

Joined
May 13, 2018
Threads
33
Messages
337
Location
Cudahy,WI
Guys, I am racking my brain on this one. Wrongfully assumed loading new TPMS IDs was as easy as my 2006LC.

Vehicle in question is a 2015 LC, 09/2014 build date

Steps I have taken so far
  • Attempted with Techstream V13 something and a V1.4.1 cable
  • Attempted with Techstream V14 something and a V2.0.4 cable
  • Attempted with Techstream V14 something and a V1.4.1 cable

Cables connect, Techstream works fine, fails on the same screen when it tries to write sensor IDs to the vehicle, gives the famous "ground terminal blah blah blah

All other parts of techstream seem to work ffne.

One thing I noticed is that both cables pass the CAN test but both fail the K line and L Line test. Do I need those protocols to write to the TPMS computer on a 2015?
 
I've never been able to do it either. And a few weeks ago when I swapped to my summer rims/tires, I went over to the local Town Fair Tire to have the codes updated, they had a hell of a time doing it as well. Had to try 3 different readers to get it to work, 2 guys over 30 minutes. And they did it for free (although I did give them a $20 tip). So I'm not gonna even try.
 
I eventually gave up with techstream for TPMS and bought a Carista module for $20. Then you can get a one-week "pro" subscription for $9 to program TPMS (have verified it works, easily), or I think it's $40/yr

If someone figures out the MiniVCI route I'll start using that but despite my cable having the necessary chips (according to posts on this board) I couldn't get it to work.
 
That Carista app looks promising. I have two more cables coming to try via Techstream, another variant on the same cheap MiniVCI cable everyone uses and a VXDiag VCX Nano that looks more robust.

I emailed Drew Tech regarding their Mongoose cable and they could not confirm or deny that it would allow you to set TPMS IDs on a 2015 LC. Thats a little disappointing for a $500 cable.
 
Guys, I am racking my brain on this one. Wrongfully assumed loading new TPMS IDs was as easy as my 2006LC.

Vehicle in question is a 2015 LC, 09/2014 build date

Steps I have taken so far
  • Attempted with Techstream V13 something and a V1.4.1 cable
  • Attempted with Techstream V14 something and a V2.0.4 cable
  • Attempted with Techstream V14 something and a V1.4.1 cable

Cables connect, Techstream works fine, fails on the same screen when it tries to write sensor IDs to the vehicle, gives the famous "ground terminal blah blah blah

All other parts of techstream seem to work ffne.

One thing I noticed is that both cables pass the CAN test but both fail the K line and L Line test. Do I need those protocols to write to the TPMS computer on a 2015?

I went through the same process (multiple versions of techstream and the 1.4.1 cable followed by more expensive 2.0.4 cable) and ended up using Carista. If you have a Discount Tire near you, they will also program TPMS for free.
 
I eventually gave up with techstream for TPMS and bought a Carista module for $20. Then you can get a one-week "pro" subscription for $9 to program TPMS (have verified it works, easily), or I think it's $40/yr

If someone figures out the MiniVCI route I'll start using that but despite my cable having the necessary chips (according to posts on this board) I couldn't get it to work.
I went through the same process (multiple versions of techstream and the 1.4.1 cable followed by more expensive 2.0.4 cable) and ended up using Carista. If you have a Discount Tire near you, they will also program TPMS for free.

Another vote for Carista. Now easily running both highway and daily/off-road tire sets with working TPMS for both. Carista TPMS change is a matter of minutes and very intuitive.

HTH
 
Not a 2015, but I did program a 2009 LX570 successfully using tech stream v12 and a 2.0.x cable.
 
One thing to point out, if you are going to run two sets of wheels, Carista will require you to have the sensor IDs for the second set, so write them down before mounting your tires.
Does TPMS management require the monthly subscription?
You can read the tpms without a subscription to get the current sensor ids, but to change them a subscription is required.
 
That Carista app looks promising. I have two more cables coming to try via Techstream, another variant on the same cheap MiniVCI cable everyone uses and a VXDiag VCX Nano that looks more robust.

I emailed Drew Tech regarding their Mongoose cable and they could not confirm or deny that it would allow you to set TPMS IDs on a 2015 LC. Thats a little disappointing for a $500 cable.

@ArnieC, let me try my techstream tonight. I'm using VXDiag VCX nano.

As for Mongoose cable, you will need subscription to Techstream to maximize it. Else, a MiniVCI does most programming as needed.
 
OP does your techstream successfully show the datalogging screen? Mine won't and I wonder whether this is related to its TPMS issues.

If you have a Discount Tire near you, they will also program TPMS for free.

The capability of discount tire can vary significantly though. They COULD NOT program my cruiser for the new denso/pacific sensors in my rock warriors because they wouldn't activate as the sensors they usually use do. Turns out these need pressure rise, then fall, then rise to activate. Their programmer apparently didn't have a function to type in the codes that I brought in... or they didn't know how to use it.

Either way, I don't expect much out of discount doing TPMS anymore.

Not a 2015, but I did program a 2009 LX570 successfully using tech stream v12 and a 2.0.x cable.

Do you know whether this was with a 32-bit or 64-bit OS? That seems to be a factor in whether this works.
 
OP does your techstream successfully show the datalogging screen? Mine won't and I wonder whether this is related to its TPMS issues.



The capability of discount tire can vary significantly though. They COULD NOT program my cruiser for the new denso/pacific sensors in my rock warriors because they wouldn't activate as the sensors they usually use do. Turns out these need pressure rise, then fall, then rise to activate. Their programmer apparently didn't have a function to type in the codes that I brought in... or they didn't know how to use it.

Either way, I don't expect much out of discount doing TPMS anymore.



Do you know whether this was with a 32-bit or 64-bit OS? That seems to be a factor in whether this works.

Arguably the same issue could arise using Carista. I've successfully had Discount program two sets of those same sensors. No idea why your discount couldn't activate them. I had one tech tell me I had a dead sensor. Went back a few days later and a different guy activated the supposedly dead sensor. I don't expect every tech to know how to do it, and for the price it is ok to have a bit of a hassle. Still, the $10 for techstream is the easiest way to do it.

As with the 32 or 64 bit, have you gotten it to work with either? I've tried both and neither works. I honestly think it just doesn't work, at least with the 200 series and the 2.0.4 or 1.4.1 cables available. I'd love to hear if anyone has actually gotten it to work on a 200 and what cable they used.
 
Regarding IDs - I took a photo of each sensor before I had them installed so I have the codes. OEM Denso sensors.

Regarding OS - I am running Win 7 64 Bit on a Lenovo W540 with i7, 16gb RAM, etc, I have an old XP Laptop I will try to install it on if I get a wild hair up my butt.

Regarding the datalogging screen - are you referring the live data from the TPMS ECU or a different screen. Live data from TPMS ECU is displayed normally with all cable and software iterations I have tried.

Nearest I can tell the earlier LC200s and LXes are programmable with Techstream, the 13-15s and newer seem to be the problem children.

There is a very cryptic release notes on Techstream about TPMS data not being readable, many errors, multiple attempts will get it to work, etc. but it is still an open issue and very unclear about the actual issue. Mongoose would likely have the same issue if its a Techstream problem and not a cable issue. Considering Mongoose only said "call Toyota for tech support" I don't have a lot of faith in their solution.

I can clear codes and see live data just fine, just cant program the (*&@*&^ Sensor IDs!

One thing I did want to add is switching from a 1.4.1 cable to a 2.0.4 cable did show a few additional data screens, stuff loaded faster, and so on. But it did not solve the Sensor ID issue.
 
I've never been able to get live data to work with techstream on my 13. 64-bit OS. Reading/resetting codes and programming modules seems to work fine.

Getting it all working in the first place was a chore, but it was a year ago so I'm fuzzy on exactly how I did it.

Arguably the same issue could arise using Carista. I've successfully had Discount program two sets of those same sensors. No idea why your discount couldn't activate them. I had one tech tell me I had a dead sensor. Went back a few days later and a different guy activated the supposedly dead sensor. I don't expect every tech to know how to do it, and for the price it is ok to have a bit of a hassle. Still, the $10 for techstream is the easiest way to do it.

As with the 32 or 64 bit, have you gotten it to work with either? I've tried both and neither works. I honestly think it just doesn't work, at least with the 200 series and the 2.0.4 or 1.4.1 cables available. I'd love to hear if anyone has actually gotten it to work on a 200 and what cable they used.

These sensors seem to be different than what Discount normally uses. They are apparently used to clones where the cloning process activates them, or other ones that need a low-frequency signal sent to wake up and start transmitting. According to the toyota dealer and some documentation I found online ours (pacific industries, reboxed as denso) just look for pressure rise/fall and/or the centrifugal force of driving above a certain speed. Then they transmit. I'm guessing mine hadn't seen the proper pressure inputs to wake up, so Discount's reader couldn't get a signal, so they couldn't get codes to program my vehicle (as stated they couldn't input manually) even if the sensors would have later woken up and started transmitting. They could read the signal off my spare which was original with the vehicle.

The toyota tech just programmed in the codes I gave him and it worked. No "wake up" signal sent. I then verified carista can be used by rearranging the codes and therefore readout order on my dash.
 
One thing to point out, if you are going to run two sets of wheels, Carista will require you to have the sensor IDs for the second set, so write them down before mounting your tires.

Does the 200 have the ability to store 2 sets of sensors or do we need to get it reprogrammed everytime we do a wheel swap?
 
Does the 200 have the ability to store 2 sets of sensors or do we need to get it reprogrammed everytime we do a wheel swap?

One set only.

This is why some people prefer to use clones for summer/winter sets vs all new sensors. If you do that make sure the second set is far away enough to avoid the vehicle picking up both sets. That'll make it go haywire.

Personally I preferred OEM-like durability/lifespan.
 
OP does your techstream successfully show the datalogging screen? Mine won't and I wonder whether this is related to its TPMS issues.



The capability of discount tire can vary significantly though. They COULD NOT program my cruiser for the new denso/pacific sensors in my rock warriors because they wouldn't activate as the sensors they usually use do. Turns out these need pressure rise, then fall, then rise to activate. Their programmer apparently didn't have a function to type in the codes that I brought in... or they didn't know how to use it.

Either way, I don't expect much out of discount doing TPMS anymore.



Do you know whether this was with a 32-bit or 64-bit OS? That seems to be a factor in whether this works.
32 bit os. Win 7 on a circa 2008 netbook. Performance is poor on the pc but it does work, just takes a while.

I’m working on a 64 bit install right now. It’s botched and I have read only mode. I have the usb driver working so am hopeful I can get ts licensed correctly. Same thing happened on my 32 bit install and it’s been long enough I don’t remember how fixed it.
 
One thing to point out, if you are going to run two sets of wheels, Carista will require you to have the sensor IDs for the second set, so write them down before mounting your tires.

You can read the tpms without a subscription to get the current sensor ids, but to change them a subscription is required.
That's what I figured. I can't believe they charge $40/yr for access to expanded capabilities.
 
Tonight's update:

Dug up my old Win XP laptop and installed Techstream V14 on it...and...no customization options were present at all. Didn't matter what cable I had, V1.4 or V2.0. Uninstalled Techstream V14 and backdated to V10, now customization options are present and functional but still getting the same error when I try to write TPMS sensor IDs. Same exact issues with V1.4 or V2.0 cables.

Throughout this all I can read TPMS codes, read live data, clear codes, all other modules perform normally.

Will get one more cable that claims to be able to read and write to the K line (will verify - not even sure this is my issue) and also the VCX Nano. May not have time to work with it tomorrow much but will certainly get some time this weekend. If everything fails, I will go with the Carista module and report back how it works. Hopefully I can avoid a trip to the dealer.

Slightly off topic, has anyone found some non-subscription based tools that would let you write the TPMS IDs to the vehicle - not clone TPMS sensors since I want to use another set of OEM sensors not cloned sensors.
 
No options is an install that didn’t register correctly. That’s where mine is at right now too
 

Users who are viewing this thread

Back
Top Bottom