Jump to content

Horn went out

Zrodie21

By Zrodie21
in Troubleshooting & Recalls

 Share

Recommended Posts

Zrodie21 Enthusiast

Zrodie21

Posted
Posted

Anybody had there horn go out? I checked my fuse and it was good to go. What else could I checked? I believe it went out once I lifted the truck. Thanks in advance

 

 

Sent from my iPhone using Tapatalk

  • 2 weeks later...
tbarn Senior Enthusiast

tbarn

Posted
Posted

Update. Actually it is sold as 2 horns on a bracket. Not serviced individually.

8lugCT Enthusiast

8lugCT

Posted
Posted

One of the horn pressure points on my trucks steering wheel doesn't work anymore lol

FL335i Enthusiast

FL335i

Posted
Posted
On 11/1/2017 at 5:40 AM, thewhitestallion said:

My horn intermittently works when I lock my truck. But it works every time I honk the horn at some stupid driver...

This is the same issue I have bud!!!  I had the dealer look at it and they could not find why it was doing this.  It did the issue right there with the dealer folks.  No problem replicating the issue. 

8lugCT Enthusiast

8lugCT

Posted
Posted
9 hours ago, FL335i said:

This is the same issue I have bud!!!  I had the dealer look at it and they could not find why it was doing this.  It did the issue right there with the dealer folks.  No problem replicating the issue. 

Isnt this an option in the vehicle settings?

  • 2 weeks later...
FL335i Enthusiast

FL335i

Posted
Posted

No, the issue I have is intermittent non-horn sound when locking.  I can hit the button 100 times and no horn beep.  Drive to work and hit the lock button twice and it beeps as it should. 

  • 1 month later...
2014 All Terrain Enthusiast

2014 All Terrain

Posted
Posted

I have the exact same issue. The horn either doesn't work or is really quiet when I try and lock the vehicle, happens randomly. And yes all my doors are closed. I can hear the truck locking, and if I keep hitting lock eventually the horn will beep as normal. Any ideas?

  • 1 month later...
  • 4 weeks later...
bkesting Enthusiast

bkesting

Posted
Posted

I noticed this on my 2016 tonight. Press lock twice and the horn sounds really muted or like it's going out

bkesting Enthusiast

bkesting

Posted
Posted
15 hours ago, Colossus said:

Warranty?

Mine is still under a little warranty, so I will visit the dealer about this.  Anyone have any thoughts as to what causes this?

nluchau Enthusiast

nluchau

Posted
Posted

Mine does this too and its a 2016.  My only thought is condensation getting into the horn and freezing.  Seems to work better when its warmer out.  Same thing for the steering, mine is stiff when its cold but is normal when its warm out.  These are poorly designed IMO

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

    • 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?
    • 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?

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...