Jump to content

Remote lock and unlock problem...

Mike Hamm

By Mike Hamm
in Troubleshooting & Recalls

 Share

Recommended Posts

Mike Hamm Enthusiast

Mike Hamm

Posted
Posted

Ok, something just started happening with our 2016 GMC 2500HD Denali 4x4 with the diesel.

The remote door lock and unlock won't work every time from either of our fobs. We bought this truck last August so I can't imagine the batteries in both of our fobs have died at the exact same time and only 7 months in. My fob gets used the most with my wife's fob barely getting used at all.

Anyone else experience/experiencing this? And, what did you do to remedy it? I guess we can try replacing batteries first, but batteries only lasting 7 months in a fob? And both failing at the same time, especially given one gets frequent use and one barely gets any use.

We know it's not a fuse because it does work from time to time.

  • Replies 34
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

Colossus
Colossus

Given that batteries are so cheap, I'd go that route first. If no joy and you can duplicate the issue easily, this sounds like something for the warranty. Perhaps the sensor in the vehicle just need

Mike Hamm
Mike Hamm

Well, it's good I took it in to the dealer. Turned out there was a service advisory for an upgrade to the Body Control Module (BCM) which is what controls the remote entry system, among other things.

JNK13
JNK13

Just wanted to add my two cents to this older post. I have a 2016 GMC 2500 Denali Diesel. A few weeks ago I noticed that my FOB would not lock or unlock the doors. The alarm would set, but the door lo

Colossus Senior Enthusiast

Colossus

Posted
Posted

Given that batteries are so cheap, I'd go that route first. If no joy and you can duplicate the issue easily, this sounds like something for the warranty. Perhaps the sensor in the vehicle just needs an adjustment or computer re-programmed.

  • Like 1
Mike Hamm Enthusiast

Mike Hamm

Posted
  • Author
Posted

Colossus, agreed. We will change out the batteries just for that reason. Cheap enough to try. Yeah, I have an appt at the dealer on Monday if the battery doesn't do it.

waumo1 Enthusiast

waumo1

Posted
Posted

Change the batteries. Then do you have any aftermarket devices in the vehicle? They can create RFI/EMI that interferes with the remote. USB chargers, Cell phone chargers, dash cams, tuners, anything electrical/electronic that stays powered on?

Mike Hamm Enthusiast

Mike Hamm

Posted
  • Author
Posted

Change the batteries. Then do you have any aftermarket devices in the vehicle? They can create RFI/EMI that interferes with the remote. USB chargers, Cell phone chargers, dash cams, tuners, anything electrical/electronic that stays powered on?

Waumo1, no devices. Thanks for the idea though.

Mike Hamm Enthusiast

Mike Hamm

Posted
  • Author
Posted (edited)

Definitely weird. It started working yesterday (no battery swap yet) and worked all day. This morning, nada. Swap in a new battery, still nada.

Intermittent problems are the worst.

Now that I put in a new battery I will try the reprogram steps and see if that works.

Edited by Mike Hamm
Mike Hamm Enthusiast

Mike Hamm

Posted
  • Author
Posted

Well, it's good I took it in to the dealer. Turned out there was a service advisory for an upgrade to the Body Control Module (BCM) which is what controls the remote entry system, among other things. Upgrade done. Now hoping the problem is resolved.

  • Like 1
Mike Hamm Enthusiast

Mike Hamm

Posted
  • Author
Posted (edited)

Do you have the tsb service advisory number for the bcm

Here is what it says on the invoice - "155 updated bcm software 2810215.5" In looking up other service advisories, I don't see any number format that matches other advisory numbers format so I'm thinking they didn't put it on the invoice.

Edited by Mike Hamm
Mike Hamm Enthusiast

Mike Hamm

Posted
  • Author
Posted

Oh boy. I don't know if it's related to the leak I had but now the keyless entry stopped working. AGAIN! Criminy. Good thing it's going in for the leak.

Mike Hamm Enthusiast

Mike Hamm

Posted
  • Author
Posted

Ah, ze plot zickens. On the way to the dealer, the TPMS stopped working! Well, there is a module for the keyless entry and the TPMS. Remote Function Activation Module, I think it was called. Those 2 things go to that module. So, now the thought is the module needs replacing. It'll be at the dealer on Wednesday and I'll get the truck up there ASAP to get it replaced. Stand by.

dasimmon Enthusiast

dasimmon

Posted
Posted

Ah, ze plot zickens. On the way to the dealer, the TPMS stopped working! Well, there is a module for the keyless entry and the TPMS. Remote Function Activation Module, I think it was called. Those 2 things go to that module. So, now the thought is the module needs replacing. It'll be at the dealer on Wednesday and I'll get the truck up there ASAP to get it replaced. Stand by.

when it rains it pours....

Mike Hamm Enthusiast

Mike Hamm

Posted
  • Author
Posted

when it rains it pours....

LOL, yup. Hope this puts a stop the rain for awhile.

Coby7 Senior Enthusiast

Coby7

Posted
Posted (edited)

The module that takes care of the TPMS and door locks is called the RCDLR and usually sits under the dash pad. These can fail especially if water gets in there. RCDLR Remote Control Door Lock Receiver

Edited by Coby7

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
 Share
Go to topic listing

  • Latest Articles

  • Posts

    • Chuck FB
      summer road trips in the 2026 2500HD

      By Chuck FB · Posted

      I thought I would use your thread and add to it as I just did my first longer drive with my truck in the last couple of days. I drove from the Grande Prairie area of Alberta down to Edmonton and most of where I drove in the city was the ring road so fairly free flowing but a bit of stop and go as well in the city. Stayed the night and returned home and not too many stops along the way each way but every restart and certainly every cold start sets it back for fuel mileage. Why I say that is I see some people will cherry pick a fuel mileage leg after the vehicle had been warmed up driveline wise before hand and its a forgiving ( easy rolling drive leg for example ) and call that their fuel mileage which can give a false perception of reality. I was not heavily loaded at all but never the less the flip bak cover, rubber bed mat, various tools etc and extra jerry cans of fuel all way up to a few hundred pounds of dead weight so its not an empty truck. The cold inflation tire pressures are set more near the freezing point so once they are warmed up driving I was showing 45 front and over 40 rear and realize high inflation pressures would help a little in fuel mileage but certainly not the ride on our crap sections of highway. The weather was good so was not raining as that can really drag mileage down, in fact I had a bit of a tail wind on average driving home. Most people on here would never have driven on that freeway to visualize it but its got a fair bit of rolling type of landscape with numerous river valleys. For the most part I had it on cruise set to 62 although kicking it off if I caught it in time before it started down shifting and self braking going down the grades. Most of the more substantial grades its shifting into 7th I believe as 8th just doesn't have it. Total distance round trip was 643 miles and my overall average and I did refuel three times in all, figured out to 17.65 miles per US gallon. My best fuel mileage section refuel within all of this figured out to 18.46 and these are all hand calculated figures. I find if anything that the trucks computer can be over optimistic, sometimes its pretty close but other times its stretching it. On paper persay in theory the truck would have just about made it on fumes for that whole drive without refueling once.    Which made me think of the topic thread of the wonder if these trucks could do 20 mpg and that is a good question, certainly would have to be on an easy going flat highway, no head wind, the right temperature, not packing around a bunch of dead weight and puttering along even slower than I was I would suspect and going steady and not stopping to smell the flowers or take a piss !. It probably is possible but not without effort to attain that with the wind resistance and weight of these trucks. Of course on my drive most people are passing me if they have the power as per loaded highway tractors, never mind a lot of speedy vehicles but the speed limit is 68 and most are at or well over that. 
    • Aimatdeer
      Ac not keeping up

      By Aimatdeer · Posted

      Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • CamGTP
      Gas Prices

      By CamGTP · Posted

      Paid $2.72 for E85 today.
    • Atlas
      Gas Prices

      By Atlas · Posted

      Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That makes sense, and I think you are describing the real product problem. Capturing data is the easy part. If the owner or technician has to manually dig through five minutes of millisecond-level logs, the product has already failed. The device would be at the ECM harness, not at the OBD port, so I agree that data retrieval and event marking need to be thought through carefully. The way I am thinking about the architecture is: The recorder itself should not depend on a phone, app, Bluetooth, Wi-Fi, or cloud connection to capture the event. It should always keep a local rolling buffer and lock the event locally. A button, phone app, or small cabin device would only act as an event marker. If the driver feels a stumble and presses the button 10–30 seconds later, the pre-buffer has to already contain the useful data. For data retrieval, the practical options would be a sealed service USB lead, Wi-Fi download, or a phone/cabin companion device. I would not expect the owner to remove the ECM-side module or work with raw files directly. The cloud or AI side would be for interpretation, not for capturing the event. The truck may have no connection when the issue happens, so the evidence has to be saved locally first. After that, cloud processing could help decode the data, compare it against baselines, and generate a readable report. For the first version, I would keep the automatic triggers conservative and objective: driver event marker bus-off error passive voltage drop / brownout device reset FIFO or queue overflow a normally periodic message disappearing side-to-side communication mismatch, if the topology supports that For “learning normal,” I agree with your point, but I would not want to overclaim it as automatic root-cause diagnosis at first. A realistic first step would be learned baseline comparison for that specific vehicle and operating condition. For example, a value would only be compared against similar conditions: RPM range load / MAP throttle position gear / vehicle speed coolant and oil temperature battery voltage AFM/DFM state, if decoded and validated Then the report could flag things like: this periodic message disappeared compared with its normal timing this value deviated from this vehicle’s normal range under similar conditions the same abnormal pattern repeated after the same type of event the anomaly occurred together with voltage, oil-pressure, misfire, or communication changes But I would still call that “abnormal pattern detected,” not “replace this part,” unless there is enough validated repair data behind it. So the intended product would not be “here is a huge log.” It would need to be an event package: what triggered the capture how much pre/post data was preserved what changed before and after the event whether the device itself reset, overflowed, or saw a bus error selected graphs around the event raw data only as supporting evidence From your perspective, what would make this kind of report useful instead of just another datalog? For example: What are the top 5 parameters or events you would want highlighted first? Would you trust a learned baseline for that specific vehicle, or would you prefer fixed thresholds? How much false-positive flagging would be acceptable before you stopped looking at the reports? What would a one-page report need to show for an independent shop to take it seriously? For misfire, AFM/DFM, oil pressure, or U-code complaints, what would you want the tool to flag automatically?

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...