Jump to content

Recommended Posts

Posted

Long story short, I traded my 2020 trailboss for this truck and I’m pretty happy minus a few luxury items missing. I’ve noticed that slow speeds turning or where the truck bed shifts, I hear a pop and I don’t like it. I’ve read maybe just the leafs doing it and a piece of rubber will fix it? Also, I notice with no music on, truck running, I hear a hissing sound from the steering wheel…hard to explain but it changes when I turn the wheel and sounds like a hydraulic line!? Normal?? Any insight because I know dang well what the stealership will say and I don’t want to go through it all if it’s actually normal. Thanks 

Posted

Steering is normal and even more normal if it has the digital assist steering.

 

Rear noise its likely the leaf pack.  "20-NA-022 Squeak, Grind or Clunking Noise from Rear Leaf Springs" and "21-NA-138 Squeak, Grind or Clunking Noise from Rear Leaf Springs" are the two bulletins on leaf pack noise.  

Posted
17 minutes ago, newdude said:

Steering is normal and even more normal if it has the digital assist steering.

 

Rear noise its likely the leaf pack.  "20-NA-022 Squeak, Grind or Clunking Noise from Rear Leaf Springs" and "21-NA-138 Squeak, Grind or Clunking Noise from Rear Leaf Springs" are the two bulletins on leaf pack noise.  

Are those bulletins for 2020-2021 is that what the 20 and 21 stands for? What about 22+

Posted

Same with the hissing on my 2022 lt…..only hear it with no music on in park or at idle and reacts to steering wheel moving or once you start moving…..annoying but have had no issues with it other then being annoying 

Posted

Well glad to hear it’s “normal” now to decide if I want to try and make the leaf noise go away with rubber strips or leave alone. I read some guys had the noise go away after 1000 miles or so and I’m only at 88 so I got time lo. The steering is so odd, mine is a Custom trim so I don’t think I have that digital assist but it’s definitely noticeable 

Posted
3 hours ago, Npd15 said:

Well glad to hear it’s “normal” now to decide if I want to try and make the leaf noise go away with rubber strips or leave alone. I read some guys had the noise go away after 1000 miles or so and I’m only at 88 so I got time lo. The steering is so odd, mine is a Custom trim so I don’t think I have that digital assist but it’s definitely noticeable 

The creaking in the rear goes away if the underside is drenched. Mine creaks when dry. 5100mi 

Posted

The hiss noise you hear is the power steering system. Its a hydraulic system and the noises are perfectly normal.  You hear a howl noise at idle with no movement on the steering wheel. Noise changes when moving the steering wheel.  Totally normal.  6.6 gas comes with hydraulic power steering and hydraulic brakes. 

  • Thanks 1
Posted
20 hours ago, Pryme said:

Are those bulletins for 2020-2021 is that what the 20 and 21 stands for? What about 22+

 

 

Covers multiple years yes.

 

  • Thanks 1
Posted

These are noisy trucks, every single T1 2500 I've had made that steering noise.....I am not concerned unless the basic function is affected.....but yeah my 1500s were much quieter vehicles ......

 

I have digital steering now and it sounds sane as my LT's DID AT HARD LOCK on steering

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

    • Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • Paid $2.72 for E85 today.
    • Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • 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?
    • 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
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...