TPMS pids

Has anyone been able to find TPMS pids to use with an app such as Torque? I have a 2015 CM and use Torque Pro. I can see TPMS info for each tire with Techstream so I'm thinking there has to be a pid that could be entered. It would be great to see tire pressure info for each tire on the screen.

Thanks

 

ScanGuage has the X guage commands listed here but I don't know if they will help you at all. I'm not familiar with X commands versus PIDs. Now the new ScanGuage 3 will give you all of the displays.

https://www.scangauge.com/support/x-gauge-commands/toyota-lexus-scion/

 

They aren't there. 2.0s use LIN while 2.5s use CAN for TPMS. PIDs are mfg agnostic and are actually callbacks. You need to get on the appropriate vehicle network to sniff. I've done this for CAN, as have others, but nobody has gotten onto LIN that I'm aware of (I paused effort on this front because it wasn't worth the amount of work to solely bring in tire pressures). One option @Jeff_5_7 was looking into (not sure where he ended up) was swapping in a 2.5 TPMS ECU which is CAN-based. It'd save having to integrate a SPI <--> LIN chip onto a daughter board.

*Edit - just saw this is in the 2.5 forum. Ignore all LIN comments.

 

The 2007-2017 Tundra communicated the data on the LIN network, well K-LINE ISO 9141-2 which I really dont know much about.
In 2018 the TPMS Ecu became a part of the CAN network, much easier to communicate with. (FYI I still have not powered up my 2018 TPMS ECU to see if it will communicate on my 2007 CAN network)

However with some clever work people have figured out to get TPMS data out of the DLC connector using OBD commands for the 2007-2017 trucks. The OBD Fusion App was the first one I saw that could do it. I assume they and Scangauge all kind of figured this out around the same time.

Toyota has some clever network programming that essentially allows you to communicate with the Body Control Module on CAN but use it as a Master Node to talk to Salve Node ECUs on LIN.

Essentially with the right message structure, you can tell the Body Control Module (master) to ask the TPMS Ecu (Slave) for the values. Then the Body Control Module will relay this data back in the CAN OBD response. It is a really cool concept when you understand it.

It requires extended ECU addressing, meaning your message is sent to Address 0x750 (generally the body control module) but the first value of the message is the extended address of the Slave ECU (say A1), then you send the data mode/request/identifier.

 

Long story short, yes it can be done.
Does anyone have the answer written out clear in black and white? No, not that I am aware of.

I could probably figure most of it out with a day or two playing with my truck. Somthing I have been meaning to do. I do have some logs from a 2018 Camry that a user recorded the request and response message for TPMS data from the OBD Fusion App.

I would start by logging the same out of my OBD Fusion app. Then solve the math for scaling, units ect.

With some work, Tire Pressure and Time Temp can be reported. As you can see in the link above Scan Gauge has figured all of this out and list 3 different options for coding it in. It would be my assumption the extended address changed across year models. IE the setup for my 2007 might not work exactly the same on your 2015 but would be close.

Once you fully understand message address, structure, data, response, and scaling. I dont think it would be hard to translate that into a custom user entered PID in Torque.

 

Have a link to getting OBD Fusion logs? I need to look into this. Modified BCM poll requests would be pretty easy to pull off in my script.

 

Aftermarket stereos have had tire psi and temps, why can’t my torq app?!