Jump to content

Recommended Posts

Posted

Finally had a dealer take the time to diagnose the loud metallic sound under our truck on cold starts.  They confirmed my suspicion that its something in the exhaust system and they suspect the flapper valve.  Unfortunately, the exhaust is one giant piece and the flapper is unserviceable, AND exhaust components aren't covered under the GMPP warranties.   Therefore, the repair is a $2,400 replacement of the exhaust using GM parts.  Is the Borla made GM performance exhaust the only option out there that retains a similar flapper device, ?  Trying to decide if its worth it to replace with factory exhaust or go aftermarket, and don't want any drone. 

Posted

Some people will just cut out the flapper valve, or jam/weld it open.  You might do this, just to see how it sounds.

 

And, depending on what's wrong with the valve, perhaps it could be fixed, if it's say, just the plate inside has come loose from the shaft that moves it.

 

You could advertise for a replacement valve, as some people do cut them out and likely just toss the valve.  You could buy it and have it welded in place for way less than $2400.

  • Like 1
Posted

Clamp it open or have a muffler shop cut it out and install a straight pipe. I've removed 2 flapper valves on T1s and never had any drone.

  • Like 1
Posted
32 minutes ago, Bikerjon said:

Clamp it open or have a muffler shop cut it out and install a straight pipe. I've removed 2 flapper valves on T1s and never had any drone.

I've tried clamping it open and it still rattles.  I've heard a few straight pipe videos, but they all left the flapper in ahead of the straight pipe.  Did you remove the flapper AND straight pipe on any with a 5.3? Hate to get it too loud and end up with drone as much as I drive on the highway.  Still under a GM extended warranty and know several guys who've had issues with the Range OBDII devices causing other problems.  

Posted
On 9/3/2025 at 11:04 AM, tjonesdfw said:

I've tried clamping it open and it still rattles.  I've heard a few straight pipe videos, but they all left the flapper in ahead of the straight pipe.  Did you remove the flapper AND straight pipe on any with a 5.3? Hate to get it too loud and end up with drone as much as I drive on the highway.  Still under a GM extended warranty and know several guys who've had issues with the Range OBDII devices causing other problems.  

OK sorry if I wasn't clear in my reply. Both exhaust systems I modified were 5.3L. I did not straight pipe the entire exhaust system. I cut out the flapper valve and replaced it with a straight pipe. Then cut out the stock muffler and installed a high flow glass pack muffler. Both of these Silverados were under factory warranty. Both mods on both trucks were done at a muffler shop for under $300.00. $2400.00 for a new exhaust is crazy. I would not straight pipe the entire exhaust. My advice is take it to a good muffler/exhaust shop and have them remove the flapper valve and install a nice high flow glass pack muffler. Neither of my trucks had any drone. Lastly I have used Range Technologies DFM disable module on all my T1 trucks and never had a problem (2 5.3L and my current 6.2L).

  • Like 1
Posted

I clamped the flapper open today and also tried the resonator screen mod.  So far it sounds ALOT better… no more rattle, clank, or chirp.  It’s a touch louder on cold start and at low speeds, but no drone or flutter yet.  We don’t have a Range device installed either.  

Posted
On 9/3/2025 at 8:29 AM, Bikerjon said:

Clamp it open or have a muffler shop cut it out and install a straight pipe. I've removed 2 flapper valves on T1s and never had any drone.

i took out my flapper and 2.5 exhaust pipe went with 3 inch and a 3 inch stock muffler sounds good no drone

  • Like 1

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

    • 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
    • And use RA's 5% discount code if you buy from them.  google for the code, one is always available.
    • Just don't turn the steering wheel as much?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...