Key Fob TPMS Conversion Issue
Thread Starter
Intermediate
Joined: Sep 2011
Posts: 29
Likes: 0
Key Fob TPMS Conversion Issue (SOLVED)
Hello, I could use some advice. When I plug the remote control receiver into the plug, it causes me to get "no comm" for all systems with no DTCs. Also the reduced power, no shocks, etc errors. It also pegs the temp gauge and makes the fuel go to zero. I checked the 3 wires and they are correct per the write ups and I capped the remaining wire. I understand that all these systems are connected and when one is grounded (?) they all become nonfunctional. When I unplug the receiver everything goes back to normal and I have a couple dozen codes to clear. I had no other issues with the other systems before. Battery is fully charged. So am I safe to assume that the receiver is faulty or am I missing something.
Last edited by detroitr; Feb 11, 2016 at 03:02 PM. Reason: solved
Tech Contributor
Joined: Dec 1999
Posts: 32,910
Likes: 2,402
From: Anthony TX
CI 6,7,8,9,11 Vet
St. Jude Donor '08
Here is the schematic that you need to PROOF your installation.
Make sure that the wires inside the connector are in the correct locations & are NOT touching each other.
That's about as simple as it gets.
Bill
Make sure that the wires inside the connector are in the correct locations & are NOT touching each other.
That's about as simple as it gets.
Bill
Thread Starter
Intermediate
Joined: Sep 2011
Posts: 29
Likes: 0
I appreciate the quick replies, working 2 12 hour night shifts this weekend, but I will investigate further and let you know. I got it from Cultrag and got the wiring info from the page posted above by 8vette7.
Thread Starter
Intermediate
Joined: Sep 2011
Posts: 29
Likes: 0
This is a pic showing how I wired it (I'm no expert). You can trace the wires to the connector. Black/white to the far left with the tabs at top, etc. I will get on youtube this weekend to see how to test the wires with a multimeter.
Thread Starter
Intermediate
Joined: Sep 2011
Posts: 29
Likes: 0
I will rewire the connector per your instruction. I must be in a reverse logic vortex because the pic with the red numbers seems to show the black wire going to the far left pin. I guess the digram of the connector you posted represents the back of the connector. Oh well fml and thanks for the help you guys.
Thread Starter
Intermediate
Joined: Sep 2011
Posts: 29
Likes: 0
OK I took a close look at the receiver and it is labeled 4 3 2 1 and the wires definitely go to the indicated pins. The wires couldn't be crossed before the receiver because it would short without it being plugged in. I totally appreciate the advice so far. I guess I could try to put the old one back in and make sure the same thing doesn't happen, but it was benign when it was in there. I don't have anyone here that I could swap with. Failing that I guess I'll have to ask Cultrag for a replacement, I've read about at least one going bad from the factory on the forum.
Corvette Stories
The Best of Corvette for Corvette Enthusiasts
150 hp to 1,250 hp: Every Corvette Generation Compared by the Specs That Matter
Joe Kucinski
8 Coolest Corvette Pace Cars (and Replicas) of All Time
Verdad Gallardo
Top 10 Corvette Engines RANKED by Peak Torque (70+ Years of Muscle!)
Joe Kucinski
Corvette ZR1X Will Be Pacing the Indy 500, And Could Probably Race, Too!
Verdad Gallardo
Top 10 Corvettes Coming to Mecum Indy 2026!
Brett Foote
Top 10 C9 Corvette MUST-HAVES to Fix These C8 Generation Flaws!
Michael S. Palmer
10 Revolutionary 'Corvette Firsts' Most People Don't Know
Joe Kucinski
5 Reasons to Upgrade to an LS6-Powered Corvette; 5 Reasons to Stay LT2
Michael S. Palmer
2027 Corvette vs The World: Every C8 vs Its Closest Competitor
Joe Kucinski
Thread Starter
Intermediate
Joined: Sep 2011
Posts: 29
Likes: 0
I just received my replacement receiver, plugged it in and it worked fine (so far). If anyone has a problem like mine, don't let anyone tell you the receiver can't be bad. Just check everything else first carefully. And thanks again for all the replies I got before.
Last edited by detroitr; Feb 11, 2016 at 03:05 PM. Reason: additional statement