Techstream error when registering TPMS sensor IDs

Yes check that out, I just had bent pins on a computer monitor plug, which is what made me think of that.

PS- No my pins do not seem to stick out.

 

Can they be pushed back a little? Those are likely the power pins; that's pretty much the only pins I have on an OBD memory saver cable.

 

Hmm, I do have third pin on my memory saver, lower left corner of pic. Maybe that's 12 volt.

 

For once.

 

Extending the ground pins is a common strategy for a connector that's intended to be hotplugged. That way, you connect the grounds first, so the connector is grounded before the rest makes contact. Makes things safer for things on both sides of the connection that way. USB, SATA, and a few other connections use the same technique.

 

The mating connector has to be designed to accept that, though. Otherwise some of the other pins may not make proper connection.

 

Offset ground pins are required by the SAE J1962 and ISO/DIS 15031-3 specifications. So, anything OBD-II is required to handle that.

 

Yes upon closer exam mine has that too, after I saw the pic I thought I better look again, sorry about that.

 

There have definitely been reports of bad older joints inside the connector, on Amazon, and I think we have had at least one person here with a faulty miniVCI connector. Yours looked maybe better quality than some of the $20 knock-offs from Amazon/EBay.

 

Hello there,
Bumping this thread after I found it googling for the exact same situation as the OP. It is on a 2017 Prius Prime (PHV in Europe).
Thank you for posting the Toyota instructions for this situation. I did not try to short the two pin yet, will try tomorrow.
Did you, BigFan, eventually sort it out ? Being the same kind of engineer, I'll not give up on it after I bought 4 genuine Toyota TPMS for my winter wheels. In the worst case, I'll go to Toyota service to have it done, but it's a long drive away and that's why I bought a mini-VCI in the first place.

 

Sorry I can't answer your questions, but welcome to Prius Chat. Guaranteed it won't be long before someone comes in with a bit more help.

 

Well, I had some hope when I found a thread on a Lexus forum (no link allowed yet). But had no luck to succeed, even using the workaround of powering the laptop and adding an usb hub to give more power to the mini-VCI. Several reports on the web for failure to set TPMS IDs with TS. Looks like I'll have to go to a Toyota dealer to set theses IDs in.

 

I noticed the original post mentioned a communication issue. I've had similar errors with communication "problems" using my TS (10.30.029) and I'm able to eliminate it by doing a complete ECU health check first. Now, every time I go online with a car, the first thing I do is a complete health check. Following the health check, it shows that each ECU has been identified and communicated with. (each ECU changes from white to yellow, if I remember correctly). Then I go about performing whatever else I need to do.

 

Exact same problem here with a 2017 Prius Prime. I'm trying to connect to OE Toyota sensors from a 2010 Prius, but i think this discussion has gotten to the point we believe the issue in the TS and the sensors.

Also worth pointing out that i have used this exact same setup (laptop w/TS 12.00.127 + mini VCi from ebay) to change the TPMS registration on my 2015 Sienna with zero problems. So this seems to be a problem with newer MY vehicles or possible Prius specific?