Jump to content

Recommended Posts

Posted

Hello all,

I'm looking to upgrade just the muffler on my 2020 Denali 6.2L. Has anyone done this on the new generation Sierra? I want to keep the cat, flappers, resonators, and just swap out the muffler. I just want a little deep rumble, but I don't want piss of the neighbors either. I also don't want any drone. Not even sure I can do just the muffler using Borla, but I know I can using Flowmaster. Any incite would be appreciated

Posted

I have some insight for a bit of a different setup.
I’ve tried both magnaflow (installed ~2 months ago) and now flowmaster (swapped yesterday) cans on the 2020 Sierra AT4 5.3L. Full dual exhaust from front to back straight off the headers.

Sounds great start up on both. But once idling, it’s too quiet. If that’s a thing. I mean I paid for a growl, and it’s there, but it sounds stock at idle. With this 10 speed, any cruising or stable speed, it’s also too quiet for what I was expecting. I’ll have to break this one in a bit. I was expecting something like Borla s-type sound out of the flowmaster, but it’s definitely under that.

My Acura was louder at start up and idle by far, and that was Apex’i Touring, nothing like the massive Greddy exhausts others were using.

I’ll see if I can get you a clip of the flowmasters.


Sent from my iPhone using Tapatalk Pro

  • Like 1
Posted

I just had the same debate on my 6.2 and decided to muffler delete it. Man... what a difference. I left all flappers and resonators in. Cost me $75 and sounds incredible. No drone under 80mph and then a very, very slight drone afterwards. The flappers really help. It isn't too rowdy for neighbors in my opinion. Here's a cold start for you. It calms down really quickly after. I would try it out and worst case scenario, you don't like it and stick a muffler back in its place. 

 

 

  • Like 1
Posted

I did the gmc performance exhaust on my 19 before it got totaled, I just picked up my twenty and not sure what to do either.  I may just do the Borla touring... we will see.  Your truck sounded good at idle.

Posted

As promised.

2020 GMC AT4 5.3L

Cold start up with full dual exhaust, headers to tips. 1 x-pipe, Flowmaster mufflers.

Cold start to idle, thought it was done spinning down, but it actually got even a little more quiet.

It’s doing well, but not quiet as aggressive as the Borla S-type cat-back. It’s in a bit of a corridor, so sound might be bouncing back a bit.

 

 

 

 

 

  • Like 1
Posted

My brother did the flowmaster outlaw. It's definitely not too quiet haha. It's loud on start up and then mellows down to a growl that's just enough on highway and around town until you get on it. It crackles a bit on start up too which is sorta fun.


Sent from my iPhone using Tapatalk

Posted
On 9/24/2020 at 8:37 PM, BluegrassMotorsport said:

I just had the same debate on my 6.2 and decided to muffler delete it. Man... what a difference. I left all flappers and resonators in. Cost me $75 and sounds incredible. No drone under 80mph and then a very, very slight drone afterwards. The flappers really help. It isn't too rowdy for neighbors in my opinion. Here's a cold start for you. It calms down really quickly after. I would try it out and worst case scenario, you don't like it and stick a muffler back in its place. 

 

 

Thanks. Sounds good. Definitely something to think about

 

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...