Tire pressure sensors

[allen.xu]

1. i-TPMS and d-TPMS cannot be used simultaneously, only one can be selected.

2. The frequency of the TPMS needs to be the same as the frequency of the car key, because the CEM (central electronic module) receives the TPMS signal through an antenna on the roof (shared with the remote control antenna).

3.  After the installation is completed, you can click on the CCD (central display screen) to calibrate the tire pressure. At this time, it is best for the vehicle to drive at a higher speed, but it should not exceed 80Km/h. This process is TPMS self-learning, and the tire pressure will display a number after success.

4. In rare cases, Volvo's tire pressure monitoring tools are required to learn, which simply means writing the ID, temperature, tire pressure and other data of the tire pressure sensor into CEM storage.

Hi iamyxy，Can you contact me, I need to see you for something please? You can send me a forum text or email. I tried to send you an email and a forum text and you didn't reply to me! Thanks!

[quattro4awd]

Finally had a chance to take the S60 out for an hours drive yesterday with both freeway and side street driving. did the "calibrate" sequence one time on the way out (it failed again and I just "canceled" it). rolling time on the road was continuous without interruption (no putting the vehicle in park, no cycling the ignition key on/off, etc.) . brought it home, closed, locked, sat overnight. 

I took it out today on an errand for a 10-15 min drive...Still no pressure values on the IHU screen (displays a _._ symbol and that is it).

Listed below is the DTC:

IHU:
U2122E - Invalid Data Received From Vehicle Connectivity Module (VCM)

this particular DTC is and has been persistent long before any attempts at configuration with OrBit and at least on the surface does not appear to be a TPMS related issue (DTC code was present under the OEM Volvo build configuration when indirect TPMS configuration was active).

according to OrBit my vehicle is equipped with a total of 4 wireless receivers... On a side note I also saw a wireless transmitter frequency setting, there was no option for 433Mh  (mine is currently set to 434Mh)

I will say this much, it does appear that changes to the "tyre circumference" setting does work for compensating for the speedometer error that was induced by my changing from a 45 series tire to a 50 series.

[Power6]

quattro4awd... hmmm interesting, the VCM is what processes the signals for the TPMS, and the keyless entry and basically everything wireless in the car. Hard to know what that error means and what should be done about it. My first thought is software updates or otherwise ugh...dealer diagnosis time :-( 

BTW no worries on the 433 vs 434...just depends on semantics, industry seems to call it "433 Mhz" mostly, when the actual freq is 433.82Mhz, some places you might see that rounded up to 434Mhz, it's the same thing.

On the others... I end up hearing from a bunch of people trying to get the TPMS working, and 100% of the time so far, when they solve it, it's the sensors. They get new ones, different ones...and it works. It's a little bit hard to get sensors compatible I think because: You have a car that doesn't have TPMS sensors so you can't just "look it up" to get the right sensor (but 2016 XC90 compatible should work, and the proper 433/315 Mhz) as well as the older chassis P3 Volvos used a different sensor, so one compatible with those Volvos I believe is not compatible with the SPA Volvos. I do think the SPA Volvos use a Schrader brand TPMS sensor, which may be helpful for compatibility. There is not any specific clear info out there on exact spec or protocol of TPMS, just a bunch of fluff.

[quattro4awd]

quattro4awd... hmmm interesting, the VCM is what processes the signals for the TPMS, and the keyless entry and basically everything wireless in the car. Hard to know what that error means and what should be done about it. My first thought is software updates or otherwise ugh...dealer diagnosis time :-( 

BTW no worries on the 433 vs 434...just depends on semantics, industry seems to call it "433 Mhz" mostly, when the actual freq is 433.82Mhz, some places you might see that rounded up to 434Mhz, it's the same thing.

On the others... I end up hearing from a bunch of people trying to get the TPMS working, and 100% of the time so far, when they solve it, it's the sensors. They get new ones, different ones...and it works. It's a little bit hard to get sensors compatible I think because: You have a car that doesn't have TPMS sensors so you can't just "look it up" to get the right sensor (but 2016 XC90 compatible should work, and the proper 433/315 Mhz) as well as the older chassis P3 Volvos used a different sensor, so one compatible with those Volvos I believe is not compatible with the SPA Volvos. I do think the SPA Volvos use a Schrader brand TPMS sensor, which may be helpful for compatibility. There is not any specific clear info out there on exact spec or protocol of TPMS, just a bunch of fluff.

a couple days ago we took the S60 up into the foothills for a couple hours drive (lota twisties and elevation changes), still no luck, this morning I checked and TPMS id's are still all zeros.



as far as wireless receiver freq. there were two other options "315Mhz" and "434Mhz narrow band" neither of which seemed like it would be a better option as a setting so I left it at the "434Mhz" setting.
I am quickly coming up on the end of the Volvo factory warranty, so at this point I have set the S60 back to the OEM programing logic config and will be scheduling a visit to the dealer in hopes of getting some of the extraneous item concerns covered under warranty including the persistent U2122E code from the IHU (I've been dragging my feet on sending the S60 back to the dealer... the idea of having to return the S60 back to OEM config from the various hardware mods is not something I am looking forward to). hopefully Volvo will cover the affected items and provide any software updates the S60 needs while it is there.

[BorD]

Has anyone tested TPMS sensors sold in EU (link is for 2016-2022 V90CC) or any other model from long list available?
 https://www.ebay.com.au/itm/274757322093...SwpkJknDEy 
As all sensors listed as direct replacement for OEM would selecting different configuration of TMPS using Orbits all what is needed to have pressure readings displayed?

[mccoy0007]

After installed compatible sensors and modified the configurations (019-03;020-08;267-01), the tire pressure cannot be displayed, and it has been a long and long drive. I read the DTC information of the CEM, and the information as follows.



OrBit DTC Report for YV
06/17/2023, 17:16:51

BCM2:
C0563 - **No description found in ECU database**
C10D0 - **No description found in ECU database**

CEM:
C11062 - Right Rear Tire Pressure Sensor and Transmitter Assembly- System Programming Failures- Not configured
C11060 - Left Rear Tire Pressure Sensor and Transmitter Assembly- System Programming Failures- Not configured
C11058 - Right Front Tire Pressure Sensor and Transmitter Assembly- System Programming Failures- Not configured
C11056 - Left Front Tire Pressure Sensor and Transmitter Assembly- System Programming Failures- Not configured

After install the so-called OEM 31362304 from Taobao, the Chinese version of Ebay, I have experienced same codes. I have driven my XC90 around 15 mins I got a pop-up window remind me that "failed to calibrate, try again?". Yellow tire Pressure warning light keep illuminated. 
The seller provides the sensor IDs and advise me to write them to Sensus system, I will try that later today using Orbit. 
However, I doubt whether this could help. If that were the case, I could only assume that something is wrong with the sensors. Since there's no guarantee for the so-called OEM quality sensors.

I got same issues. But I already wrote IDs to Sensus system using Orbit, but it was useless. After this weekend, I driven over 50 miles, it always showup  "failed to calibrate, try again?".

I tried a different set of sensors, and it works! If it shows "Failed to calibrate, try again?" then this means the sensors are not compatible, even one sensor is broken the entire system won't work. I'd recommend checking the customers' reviews before purchasing those 3rd party aftermarket sensors, or at least find a local workshop which has successful experiences on these sensors. The sensor is not expensive however the labor cost could be more expensive if things goes wrong.

[Partridge]

So now what we need is a list of known good sensors….


Sent from my iPhone using Tapatalk

[ztsoft]

[quote pid="1414" dateline="1688444495"]
PartridgeSo now what we need is a list of known good sensors…. 


Sent from my iPhone using Tapatalk
[/quote]

I tested the following ID sensor is good in my car. 
ID is 31362304 or 50662193
It's best to ask the dealer, tell them about your model, and ask them to recommend compatible sensors or just tell him the two ID numbers I mentioned.

[Power6]

I would start the sensor list, but quattro4awd bought the same sensors I did and his don't work yet! It sounds like they are either wrong or faulty though, by the "failed to calibrate" message. I feel like I should wait on recommending those until we know what's up. The Velospinner brand only seem to be available in the USA anyways.

quattro4awd: Yup if you don't see any IDs in there, they aren't learning. That's why I don't reccomend programming the IDs, at least from what I know right now. the IDs showing up is your clue that the sensors are good, the learning worked. But of course it's not working in your case...

One thing to try here...sounds simple, but connect OrBit, and reset the VCM. ECU Tools tab, choose VCM in Active ECU dropdown, click the "Reset ECU" button. This one will cause OrBit to reconnect (the VCM is the diagnostic gateway). You'd be surprised...the ECUs can run a long time with some software fault, and if the car never loses power like a flat battery or such, the "troubled" ECU can run a looooong time wit some little fault in running memory or such, otherwise working fine. I get to see all the wierd stuff via supporting OrBit, and it pops up from time to time, sometimes ECUs that were working fine, no faults in the car, but yet don't respond at all to diagnostics when OrBit is connected, in some cases reset doesn't even work, only disconnect/reconnect battery or pull the ECU fuse will "reboot" it and bring it back to good.

Anyways, it might not fix anything but worth a try!

[quattro4awd]

I would start the sensor list, but quattro4awd bought the same sensors I did and his don't work yet! It sounds like they are either wrong or faulty though, by the "failed to calibrate" message. I feel like I should wait on recommending those until we know what's up. The Velospinner brand only seem to be available in the USA anyways.

quattro4awd: Yup if you don't see any IDs in there, they aren't learning. That's why I don't reccomend programming the IDs, at least from what I know right now. the IDs showing up is your clue that the sensors are good, the learning worked. But of course it's not working in your case...

One thing to try here...sounds simple, but connect OrBit, and reset the VCM. ECU Tools tab, choose VCM in Active ECU dropdown, click the "Reset ECU" button. This one will cause OrBit to reconnect (the VCM is the diagnostic gateway). You'd be surprised...the ECUs can run a long time with some software fault, and if the car never loses power like a flat battery or such, the "troubled" ECU can run a looooong time wit some little fault in running memory or such, otherwise working fine. I get to see all the wierd stuff via supporting OrBit, and it pops up from time to time, sometimes ECUs that were working fine, no faults in the car, but yet don't respond at all to diagnostics when OrBit is connected, in some cases reset doesn't even work, only disconnect/reconnect battery or pull the ECU fuse will "reboot" it and bring it back to good.

Anyways, it might not fix anything but worth a try!

Thanks for the heads up, I will look into the VCM reset and see if it has any effect. the S60 is scheduled for a dealer visit first thing next week to get the 4 year service and hopefully resolve the IHU issues. service writer said they would also update the vehicle software in the process without additional cost (at $600USD+ charge for the 4 year service, I would certainly hope not)
a little patience please as the end of this week means returning the S60 back to its OEM origins (not really looking forward to pulling everything out) and next week I will be doing shocks and struts on the wife's Santa Fe before sending it to the dealer for service (more like another hijacking of my wallet... but some things I do not have the proper tooling for and unfortunately it's just more cost effective to pay to have it done)