Jump to content

Recommended Posts

Posted

Hey everyone! I love the little bit of added rumble the muffler delete gave me on my 5.3 - 2016 Chevy Silverado 1500. I left the resonator on, as I cannot deal with drone. I am wondering if deleting the third cat will do anything to add a little more sound? Again I think I definitely want to leave the resonator on as I am very fearful of having drone.  Any advice is greatly appreciated!

EA067DE2-DE0F-4AD5-A88D-6169B9158F18.jpeg

Posted

You're not going to notice much of a difference in my opinion. The 3rd cat is just a mini resonator and not worth the hassle of removing.

Posted
7 hours ago, CamGTP said:

You're not going to notice much of a difference in my opinion. The 3rd cat is just a mini resonator and not worth the hassle of removing.

In my experience when I put loud mufflers on a vehicle adding  small glass packs down stream would deepen the tone. And quiet it down a bit. I left it on.

Posted (edited)

Cool thank you both, guess I’ll leave it on.  What about deleting the resonator at the rear? Obviously it’s going to be louder but do you think there’ll be terrible drone? I run a Range AFM disabler so it’s V8 all the time,  so don’t have to worry about the v4 drone but wondering if if get any v8 drone?  Thanks again!

Edited by SMID333
Posted

I have a dynomax system on my truck, so it's just the dynomax muffler with no resonator and I don't have any drone.

 

Never did it with just a muffler delete but it's likely to be the same.

Posted
10 hours ago, pokismoki said:

if you activate enrichent function in the ECU , I would delete the 3rd cat. 

First time I've ever heard anyone say that. I've been tuning my trucks for years, even running E85 and never removed the 3rd cat. Never lost performance or melted down a cat with any modification to the power enrichment settings or commanded air fuel ratio.

Posted (edited)

I've had them melt down before on stock tune, i always figure that GM designed the cats to operate under their lean tune to last the 100K warrantee on this emmissions part.  i would remove it so, at a later date one can reinstall it and it will perform to spec, by not getting cooked with excessive fuel.. its just a thought I had, i doubt anyone will do it , unless they want a higher flowing exhaust

 

better yet take down the factory exhaust dont cut it up,  and buy the offroad system and add your own mufflers

Edited by pokismoki
Posted (edited)

What part of the tune in lean though?

 

You have tuning software just like I do, it's not hard to see that they run them rich like they always have since I don't know, forever? Sure stoich was changed to 14.1 for the E10 fuels but these DI trucks run 11's AFR right from the get go, that's not lean at all.

 

Lean would be 13's or higher at full throttle. And there is no lean burn mode on these trucks that are from North America. In fact in many calibration files the Cat Over Temp Protection is actually richer than the commanded AFR at full throttle, the idea is that the rich air fuel ratio will lower EGT's to try and save the cats. At a certain point too much fuel would be a bad thing and start doing the opposite.

 

If you ask me, changing the enrichment settings to a more respectable setting of around 12.5ish AFR would make the cats lasts the longest. It's not rich and it's not lean, so best of everything. Enough fuel to keep the cats working correctly and enough fuel to keep EGT's down. Plus ignition timing is a big factor as well, too low of timing would just be sending fire balls straight into the exhaust and melting them down.

Edited by CamGTP
  • 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...