View Single Post
Old Mar 24, 2019 | 12:24 AM
  #9 (permalink)  
John&Terry's Avatar
John&Terry
Joined: Sep 2016
Posts: 132
Likes: 13
From: Fortuna, CA
Default Re: TPMS Sensor ID Number Location

Originally Posted by KDW4Him
When you say "relearn" you are talking about placing the cars computer into "relearn" mode to learn NEW sensor codes, right? Regardless of who did what how... when clonable sensors are used there shouldn't be a tech in the world who would want to put the car into relearn mode.

If you are using the term "relearn" to apply to the cloning process then I might buy what they are trying to do.

"
Resetting the TPMS system failure code in the ECM" Clint may have to answer this one but what code is it? My light has always gone out by itself AFTER driving a while.

You see the part number is different in what Clint says here... TPMS explained
In this particular case, the history of "who did what how" can not be disregarded. And a relearn was necessary after installing cloneable sensors.

Replacement VDO Redi-Sensors (SE 10001HP) were installed in my vehicle the first time. This is a pre-programmed 315 MHz sensor. Unfortunately, it was the wrong frequency. The technician then attempted a relearn sequence, connecting the TPMS tool (Bartec 300SD) to the vehicle's diagnostic port. This appears to be the standard procedure when using this product: https://www.redi-sensor.com/video-it...r-programming/ This procedure probably works well for most of the vehicles they service (assuming the proper sensors are installed), but not for our vehicles. I saved the original (Schrader 52088990AC) sensors. Turns out I would need them later.

The Firestone shop also attempted a relearn process through the vehicle diagnostic port. They really tried hard to solve the problem, but because the wrong frequency sensors were installed, their Snap On tool could not perform a relearn of the TPMS. Their Snap On tool did appear to communicate successfully with the Crossfire TPMS system, and attempted to perform a relearn process. But the process was unsuccessful, and had to be aborted. In my opinion, this operation would have been successful if the proper 433 MHz VDO Redi-Sensor (SE 10004A) had been installed, because VDO indicates their sensors support the 2005 SRT6. There is a manufacturer stated caveat that specialized equipment will be required for the relearn process when using their product with Chrysler Crossfires. I've got to give Firestone a lot of credit for all their help, even though I didn't purchase the sensors from them. Had I gone there in the first place, I probably wouldn't have experienced all these problems.

I'm not sure what the dealer attempted to do except charge me a lot of money for something I didn't need. Maybe they did try to do more. I don't know. They usually come out of the building to see the unusual car, when we pull up.

After all this happened, without any results, I decided it was time to go back to square one. I started here, on this forum. EZ sensors were recommended. So that's what I got (Schrader 33500/400 at the time). The technician cloned the ID's from the original sensors into the new sensors and installed them. I hoped the problem would be solved, because the TPMS would recognize the original sensor ID's cloned to the new sensors. Or, as you said: "There is nothing new for the car to learn or know. It thinks the originals are out there with the original numbers!". Unfortunately that is not what happened. The TPMS would not recognize the new sensors, even though they were programmed with the original ID's, and operated at the correct frequency.

There was no resource available in my area to troubleshoot my TPMS. So I ordered a Micropod II/DRB III Emulator from China, and got it to work. That's a whole separate story.

Perhaps one of these failed operations (attempting a relearn process with the wrong frequency sensor installed) caused the original sensor ID data stored in the TPMS to become corrupted. That would help to explain why replacing the wrong VDO sensors with the correct EZ sensors, cloned to the original sensor ID's, would no longer be recognized by the TPMS. Or perhaps a previous failed relearn process triggers an error code in the TPMS (the DRB III seemed to indicate this). I don't know for sure.

I do know that after all these failed relearn attempts a trouble code (system failure) was set in the TPMS that could only be read and cleared using my DRB III. As soon as I requested the DRB III to test the TPMS system, the screen indicated that a TPMS system failure code (caused by a failed relearn process) was present and would need to be cleared by performing a new relearn sequence. After I confirmed that I was ready, it instructed me to activate each individual wheel sensor, starting with the front driver's side and going around the vehicle clockwise. It beeped each time I activated the requested wheel sensor (using an Autel TS601). After about two minutes and four beeps, everything worked fine again. What a relief. The nightmare was finally over!

So in this particular case, the history of "who did what how" is important. And a relearn was necessary after installing cloned sensors. However, this is an unusual case.

These are my replacement (Schrader 33500/33400) TPMS sensor ID's (433 MHz):
FL-5A0B54
FR-5AC39F
RR-5AC504
RL-5A037B
These ID's were cloned from my original (Schrader 52088990AC) sensors.
The current Schrader Part No. is 33700.

My TPMS light has also always cleared itself before, when I corrected the low tire pressure causing it, or after driving. But not this time. It took the DRB III to clear it.

I am providing this information in the hopes it might benefit others and help them avoid the problems I experienced.
Test your knowledge and enter to win a hat. Take the TPMS quiz: https://www.redi-sensor.com/quiz2016/

Thank you for all your useful TPMS information and expertise provided in this forum. I would not have been able to solve my problem without the resources available here.
See you at CAA 10 https://www.facebook.com/events/caa1...4606334392491/
 

Last edited by John&Terry; Mar 25, 2019 at 07:45 PM. Reason: Add additional information
Reply