Jump to content

Close any door and get three chirps

Jackson out west
 Share

Recommended Posts

Jackson out west New Member

Jackson out west

Posted
Posted (edited)

After 15 months of ownership my 2019 GMC Denali 3500 started giving 3 chirps every time any of the four doors was closed.  In Setting/Vehicle there is nothing in the menu to catch this.  The Gm tech who called didn’t have an idea at this point.  I should add that the keys are outside the truck with me.  And, it chirps when I close the door when I’m inside with the key in the ignition and the truck running.  

Edited by Jackson out west
Added detail.
brianf60 Enthusiast

brianf60

Posted
Posted

This alert can be modified in Settings I believe. I have keyless start and mine is set to do this if I exit the truck with the engine off and the keys left inside.

forest Enthusiast

forest

Posted
Posted

definitely remote in truck ... you dont have your second remote in there as well do you

Gangly Senior Enthusiast

Gangly

Posted
Posted

Like mentioned above, mine will do this if I leave the remote in the vehicle.  Check to make sure your second remote isn't in the vehicle as well by leaving your primary set in the house while trying to enter and start your truck.  If your able to enter and start your truck while your main set of keys is in the house, then you need to start searching the truck for your second set.

Jackson out west New Member

Jackson out west

Posted
  • Author
Posted
Quote

No keys in the truck at all.  But, catch this, the problem stopped the next day!  Just posting on this site produces miracles, I guess.  Or, there is something in the alarm system (not he software) that I hit when poking around in and under the dashboard.  GM in the meantime didn’t have a clue.  Anyone out there figure it out?

 

bshort Enthusiast

bshort

Posted
Posted

It will do it with the engine running, key in pocket and you exit the vehicle.  The fix is in settings.  

DaveHC Enthusiast

DaveHC

Posted
Posted

its a warning the remote is in truck with two beeps, but could beep different with the second remote inside too. 

  • 3 years later...

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

    • 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?
    • scotthvac.net
      2022-24 halogen - led grille swap

      By scotthvac.net · Posted

      2024 Silverado 2500 HD LTZ grille no camera Parts list   84603331 84913656 84913657 84913654 84913655 84911567 84911568 85646092 85646093 85797921 85797922   11570637  x10-15   grille/bumper bolts 11546500  x10      grille clips 11571006  x10      push/retainer clips 11546454  x6       nut retainers 11611609  x6       M5 bolts 11610700  x6       molding/trim retainers
    • davester
      Replacement Radiator

      By davester · Posted

      And use RA's 5% discount code if you buy from them.  google for the code, one is always available.
    • davester
      Turning radius

      By davester · Posted

      Just don't turn the steering wheel as much?
    • Snowcamo
      Replacement Radiator

      By Snowcamo · Posted

      Rockauto bud. I pass local stores for parts.   Findya something online. 

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...