Jump to content

Recommended Posts

Posted

I'm going to be a little stubborn here. I'm not going to remove the car wash membership sticker.  I have removed all other RFID signals one by one.  and removing those didn't stop this from happening.  So I don't believe its getting confused with other signals. If it is then GM needs to fix truck.  I'm sure there are thousand of GM Cars/trucks working just fine with a easypass transponder stuck to the windshield.   

Posted

I would agree. It would seem logical that if the easypass was the cause, it would fail everytime.

 

 

 

 

 

Posted
7 hours ago, rlambert said:

I'm going to be a little stubborn here. I'm not going to remove the car wash membership sticker.  I have removed all other RFID signals one by one.  and removing those didn't stop this from happening.  So I don't believe its getting confused with other signals. If it is then GM needs to fix truck.  I'm sure there are thousand of GM Cars/trucks working just fine with a easypass transponder stuck to the windshield.   

Those transponders are passive (at least all the ones I have had) and are not the problem. They work like the chip on a credit card active only when put under a transponder reader.. I would be looking for something interfering with the remote to truck signal. Could be something on the truck or something in the area you live causing issues. Aftermarket wireless cameras have been known to cause issues with keyless entry/starting.

 

Jay

  • 3 weeks later...
Posted

Here is a update on this after happening 2 more times.  My dealer service rep. contacted GM cooperate for Tech support on this issue.  He sent them my videos and they took a few days and reviewed them.. The Technician at cooperate came back and suggested that the dealer replace the drivers door latch and locking mechanisms. The thought is that the drivers door is not communicating that its been opened and someone got in the truck, therefore the push button wouldn't work because it thinks no one is in the truck to push that button.  So 3 days in and so far the issues has not presented itself.   Time will tell. 

 

        Its no wonder these trucks need all these computer chips and cost so darn much. Who would have thought the drivers door tells the truck when its been opened?  I would rather just put a key in the dash and turn it. Than to have this ridiculous push button, And I never know what to do with the remote once I'm in truck.  then I always forget to take it with me after driving. and I get the 3 horn beeps reminding me....... 

  • 2 weeks later...
Posted

Back to square one! 

   Went to get in the running truck Sat. morning and once again it wouldn't let me take control.  Had to take another vehicle to do what I set out to do, came home 7 hours later, tried truck and worked like nothing happened.  This is so frustrating  because the dealership can't get it to do it when it at the shop. Its been a little over 3 weeks since the last incident. 

  • 4 weeks later...
Posted

Any luck with this issue? Very similar issues happened to me about a month ago (2019 Silverado LTZ) chalked it up to a dead battery and switched to the spare fob. Replaced the battery in both to be safe, and this past week it has done it at least once every day. I can lock an unlock the truck, remote start, drop the tailgate.. everything but actually drive the thing. It will give me the same DIC message every time.. "Press Engine Start Button To Learn" (you cannot start the truck). The next message is "Remote Learn Pending Please Wait" and I have to go through the whole cycle as if I'm programming the fobs right out of the manual. I intentionally reprogrammed both fobs last night and everything worked until I tried to leave work. I have to wait for the 30 minute timeout before I can start the truck. Can't get into the dealership until Monday.

Posted

Hey Doug1234  

      They (GM) has not figured this out for my truck as of yet.  About a month ago they replaced my drivers door latch?  Telling me that it wasn't telling the computer that someone entered the truck So, it wasn't looking for the Start Button to be pushed. That didn't help. About a week later the truck acted up again and it spent over a week at the dealership.  They came back and said they were going to try a new drivers door window switch.  Telling me that everything loops through the door and that is what GM wants to do for the next troubleshooting idem?   So, I really have no faith that it will solve the issue but its been 5 days now without it happening.   

     Please update me here as to what they tell u.     My service rep actually told me that he was surprised that GM hasn't done a "buy back" on my truck.  I told him they won't because I'm the 2nd owner. I bought it as a GMC certified vehicle with 12K miles on it. He says yes being the 2nd owner I lose those rights.  Kind of stinks for me.  so I all I can do is be a pain in their side until this is fixed.  I have 20,000 more miles to get it right.  fingers crossed.  Hope u get better results. 

Posted

A couple of months ago I purchased a wireless charger for my iPhone to mount in the truck. Some kind of interference  was happening with the electronics as I started receiving the Remote Not Detected message almost immediately. The manufacturer of the charger sent me an older model (the previous model of the New & Improved version) and the problem went away.

Posted

Dejadoo, I wish my problem was as simple as interference lol Glad you got your issue figured out! My truck has no issue recognizing the fob, it just puts itself into key learning mode (which should only be possible through inserting the key in the driver's side door and turning CCW 5 times in 10 seconds) and I can't get out of it until 30 minutes is up, even holding the start/stop button for 12 seconds does nothing until that timer is up. No shot the dealer is going to be able to replicate, even with my videos.

Posted
On 4/20/2022 at 10:02 AM, rlambert said:

Hey Doug1234  

      They (GM) has not figured this out for my truck as of yet.  About a month ago they replaced my drivers door latch?  Telling me that it wasn't telling the computer that someone entered the truck So, it wasn't looking for the Start Button to be pushed. That didn't help. About a week later the truck acted up again and it spent over a week at the dealership.  They came back and said they were going to try a new drivers door window switch.  Telling me that everything loops through the door and that is what GM wants to do for the next troubleshooting idem?   So, I really have no faith that it will solve the issue but its been 5 days now without it happening.   

     Please update me here as to what they tell u.     My service rep actually told me that he was surprised that GM hasn't done a "buy back" on my truck.  I told him they won't because I'm the 2nd owner. I bought it as a GMC certified vehicle with 12K miles on it. He says yes being the 2nd owner I lose those rights.  Kind of stinks for me.  so I all I can do is be a pain in their side until this is fixed.  I have 20,000 more miles to get it right.  fingers crossed.  Hope u get better results. 

I can kinda see where they are coming from but if you have the same thing as me, it's not an issue of not recognizing the RKE, it's that it (the immobilizer or some related component) is putting itself into key learning when there's no way it should be, according to what the manuals states it requires to do so. I have been able to replicate the issue when entering through other doors, but it's completely random. 

Posted

Doug1234,   

    my truck does give me the "Learning remote please wait" message in the DIC when it acts up.  I've had the remote batteries replace twice now over the last year and had them reprogramed as well.  Did not solve the issue.  Its been a week now since the window switch has been replace and so far no issues. If its going to follow the previous patterns it should act up here soon. 

Posted

Dejadoo  the dealer did suggest that I might have something interfering.  I removed everything. The E-Z pass, the RFID chip to my house door and anything else I could think of and did not help my issues. 

 

Doug1234   sounds like you and I have the same issue going on.  when my issue come up my fob works for everything.  doors, tailgate, remote start but I would get the learning remote message and the trucks push start button won't let me go anywhere.  I wait and hour or so and come back to truck and everything is fine and works as it should until the next random time it decides to act up. 

Posted

rlambert, I got lucky (or unlucky) that I got to the dealership today before they opened and they asked me to bring it into the service bay, go out and it happened! Had a service tech come out and remote started it and he's like put it in drive and I'm like good luck, here's the fob, wait 30 minutes and you can move it 😂 

  • Haha 1
Posted

Keeping yall updated. Yesterday, the dealership gave me a new fob since they thought that was the issue (told them highly doubtful, but I'll take their word for it) and got stranded twice today to and from work using the new fob.. taking it back in next week when they have time to look at it again. I still believe it's whatever component/software that stores the RKE codes and authorizes new codes that's fubar. 

Posted

Doug1234  That is very interesting to me that it happened to them.  Please keep me updated as to what they do.  I am now a week and 5 days since they replaced my drivers window switch.  So far no issues but it has to work correctly for a few months before I say that fixed the problem.   Keep us updated. 

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Latest Articles

  • Posts

    • I'm sure if you went to a junkyard where you go in and pull the part off the truck yourself, not a used part place where they do it for you, you can get that part on it's own.  Depending on if and what else you would be buying, and time of day, they might even just skip over adding it as a item to the bill.
    • No, we trade them like pokeman cards.
    • It would be sold as a "kit", lights + auth/programming code.   You can resell the code to someone else, if they just buy the lights, either new or used, and they can then use the code to get them to work on their truck.
    • Apologies in advance, this is a long post, there's a lot to explain.   A friend had a 2010 Avalanche with a 5.3 (LMG) that blew the head gaskets (amount other problems). He gave me a donor motor out of a 2007 suburban (LC9). I got it all installed, and everything hooked up. Went to go start it, and it stumbled a bit at first and died a couple times, but after trying a few times it sounded like it was running very well. Went out to go get some coolant, and came back the next day.    Upon trying to start it, the truck will crank and fire normally and the RPMs will raise to around 1,200 or 1,500, sounding great, and then the RPMs will decrease and it will just die. Repeat that a dozen or two dozen times, and eventually it will fire and idle beautifully. As soon as you touch the throttle, it will start misfiring and sound like absolute trash. When you let off the throttle it will come down and hunt around shaking and misfiring like crazy. A message will come up on the dash saying reduced engine power.    It is throwing codes for a map sensor circuit voltage High, as well as MAF sensor low frequency. With key on engine off, the map sensor reads about 4.8 volts on the vout pin, which the PCM interprets as about 17.8 PSI, contrasted to the barometer which my scan tool tells me reads about 13.5 PSI. However, once the engine starts and is idling this reading drops to about 5-6 PSI at a stable idle, and varies significantly when the engine is misfiring/ hunting like I said before. I should note that I used the intake and MAP sensor from the LC9 engine. I changed the connector on the 2010 harness to The 2007 connector. The pinouts for the sensors were printed right on the top, and I triple-checked that I put the correct wire into the correct place.   On the other hand, the MAF sensor reads consistently 0.0 g/s regardless of State. I have pulled my hair out trying to figure out this last detail. I have tried three different sensors, (all of which should be good, one of which was new), I have verified all the wiring from the sensor going back to the PCM, and have verified that the readings at the PCM are the same readings as at the sensor itself. The intake air temperature sensor is also functioning as normal. I verified all the voltages and grounds etc, and everything is as it should be. I don't have an oscilloscope to verify, but I probed with my multimeter (Klein mm720) on frequency Mode, and it reads that on initial cranking, the maf is producing between 3000 and 7000 HZ, and as soon as the engine fires that falls off to below, 1000, and if the engine continues to run, it will produce somewhat erratic readings between 5 and 100-200 HZ. It does increase notably when the engine is revved despite the misfirings. As I said before, I have verified all of the wires going to the PCM, and I have tried multiple known good sensors. I've tested all the pins and voltages from the sensor and verified them against the manual that they are what they should be. I tested all the wiring for both ohms and voltage drop, and everything tested fine. Like I said I tested at the sensor as well as right at the PCM, everything checked out.   The only other thing of note at least I think is the fact that the engine originally in the truck had VVT, but the engine I put in, the lc9, does not have VVT. I modified the cam sensor plug to work. I reference the wiring diagrams and double-checked that I modified the harness correctly to adapt it. There is obviously a code for the VVT solenoid, but I don't think that's the cause of my problems, and this friend will probably have the PCM sent off to tune out the codes at some point.   I'm writing this for my bed so I don't recall the exact codes, but I'll update the post tomorrow morning with the exact codes. And ideas or feedback much appreciated. 
    • It's possible the two trucks are using different body control modules which is why yours works and the OP's doesn't.   So much in these newer vehicles depends on model/trim configurations, production date. They don't all use the same modules like back in the day.
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...