Car not recognizing universal TPMS?

[PoorOwner]

Background: The sensors are made by Launch, which the previous set works fine on my Mitsubishi. It emulates the OE Continental sensor I think similar to one used in Chrysler, just saying, the sensor itself is not that obscure.

I got another set this time they have revised the sensor, which required a firmware update to program.
Programming (Launch tool) and trigger scan from different TPMS tools (Launch, Autel) is always successful. The car throws "no reception" DTC code on ALL 4 tires. (active) and cannot be erased.

The car seems to NOT find the sensors therefore cannot relearn (it has to check after uploading the IDs), I put my known good wheel tire set placed in each wheel well, and it relearned successfully, DTC code also gets erased by the tool.

Just wondering if anyone seen a programmed sensor NOT being to emulate for the car to recognize at all.

 

[BombShelter]

I bought a set of nearly new snow tires (that came off a nearly new car) for my older car. The signal on the newer TPMS wheels did not work with my older reciever. The seller pulled up a cool tire information website that has everything on it and showed me something like they had changed the signal band since my car was built.

 

[PoorOwner]

That I could understand you cannot always put another cars sensor and expect it to work.

What I have is programmable to 315 to 433mhz. There is different communication protocol also in the each frequency. I think maybe they have some bad code in there that messed up the protocol part

 

[39CAMC]

Will the tool trigger the sensors?

What kind of car? With both my Autel and Ateq tools, there are a lot of cars that have extremely specific build date requirements and other data needed to program the sensor. Chevy is the worst, but they all have oddities. My point is that a given model may have one frequency or programming code for units built 1-2010-through 12-2010 and 1-2011 may have a different one. Or one set for clamp in stems versus rubber (from the factory). Or allow versus steel wheels.

So step 1 is to 100% make sure you have the correct build date and options in the tool before programming the sensors. And then if it doesn't work, try another one. I have had a lot of cars not work with the "proper" build date or whatever but work fine with another one.

DaveW

 

[gizardlizard]

so tired of TPMS issues and all the headaches that come with them. After putting new wheels on my Tundra and struggling to get the sensors to communicate with my scanner, I got fed up with the whole thing and jumped them out. Never going to see that stupid light on the dash again.

 

[PoorOwner]

Will the tool trigger the sensors?

What kind of car? With both my Autel and Ateq tools, there are a lot of cars that have extremely specific build date requirements and other data needed to program the sensor. Chevy is the worst, but they all have oddities. My point is that a given model may have one frequency or programming code for units built 1-2010-through 12-2010 and 1-2011 may have a different one. Or one set for clamp in stems versus rubber (from the factory). Or allow versus steel wheels.

So step 1 is to 100% make sure you have the correct build date and options in the tool before programming the sensors. And then if it doesn't work, try another one. I have had a lot of cars not work with the "proper" build date or whatever but work fine with another one.

DaveW

The tool will trigger and read the pressure just fine, but the car will not.
It is 2012 mitsu outlander built 2011. Which I have chosen that date range, the part number matches the OE sensor (4250B975).
Same as my last time. But maybe there is a bug and the launch tool programmed the wrong protocol on that entry and require another build date.

 

[2ndGearRubber]

Most of the issues I see with non-recognizing TPMS is install/programming error. A popular issue was Honda Odyssey vans, the Touring models had a different communication protocol than all the other trims. TPMS function was built into the BCM or something rather than its own module? Anyways somebody would say "it's all ****** odyssey vans", program to the wrong trim, and set infinite errors with NO way I have found to identify that a sensor was programmed as a Touring model or standard model. You could manually write the ID numbers, clear codes, it would always set codes when the sensors communicated. My fix was anytime a TPMS sensor had an issue, unless I replaced it personally, it was replaced again. These types of issues can exist on many makes and models.

I have seen issues with tools needing to go up/down a year in programming. Not a big deal if you can reprogram wirelessly with the sensor installed, massive PITA if you need to remove the sensor to program. Mainly this is an issue on the first/last years of body styles, although I have seen issues within a chassis.

The most reliable way to do TPMS work, IMO, is with a scan tool. I program the sensor with the TPMS programmer tool, then "chirp" all the other sensors and make a list of ID numbers. Then I manually write them to the TPMS module, or "chirp" them with the programmer tool with the car in learn mode. I have had very little luck using the TPMS programmer tools to actually deal with the vehicle itself. In fairness, I have little paitence for TPMS, so I typically default to the scan tool if I am unlucky enough to deal with a TPMS ticket.


In your situation, I would want to compare the IDs and positions of the sensors in the tires, to those within the TPMS module data list. I have seen a few situations, very rarely, where a specific brand of aftermarket TPMS sensor is simply not compatable with the system. Typically this situation results in setting fault codes for "no signal sensor X" becuase the way or timeline in which the sensor intitally wakes up and transmits data is not within the acceptable range the module is looking for. Sensor will test good every time, only option is trying another brand or OE. I would believe if all 4 sensors are not reading, you either have a programming error, or a bad run of sensors. Finding the ID list in the module will point you towards whether your tool is at least inputting the data into the module properly.

 

[39CAMC]

The tool on the same settings will trigger/read the working sensors?
if yes, however unlikely, it is probably the sensors themselves. The universals have 99% coverage and there can be some oddities.

Autel sensors wouldn't work on new Mazda miata's in 2019, exact same symptoms as you are having. Program up fine, and scan with tool but car does not see.

Universals of any brand are also very dicey with Porsche. HUF (oem) always work, but others, not so much.
I assume you have tried to reprogram the sensors?

DaveW

 

[PoorOwner]

I have had a lot of cars not work with the "proper" build date or whatever but work fine with another one.

This is not a bad idea. I will try to reprogram to one wheel to the "other" 315Mhz. Drive it to see if it throw code for that wheel.
Maybe someone made a typo in the table and it's actually loading the wrong code.

It is supposed to need to air down to program it but I was able to reprogram them with air in the tire.

 

[PoorOwner]

Exhausted all options and proved this model of programmable sensors just don't work for my car.
Going the route of cloning is not always ideal because it could end up in my situation.

I got the Autel MX. I know some people don't like Autel but they are one tier above the rest.
It can program 4 sensors at once (up to 16) and really quick. I rested the sensors on top of each tire and did a relearn, no pressure and it still worked fine then just installed the sensors.

Mitsubishi and some Lexus since the 2010s are tricky when it comes to writing IDs (if you don't have dealer's software) Autel seemed to have cracked the code for this already they have a video about it.

 

[ex-x-fire]

Why is cloning is not always ideal? We use Autel MX at work and have very few problems. The only issue I see coming up is when people have to sets of sensors near by, like winter and summer tires.

 

[Kpaige]

Some cars will not. My Tacoma will not recognize anything accept the Toyota sensors

 

[ex-x-fire]

My wife's Toyota did just fine with MX sensors, the first week though was a head scratcher. When at home the tire light would be on in the morning. Found out it was still reading the oem sensors (over the cloned MXs) that were in a trashcan inside my garage 20 feet away.