Jump to content

Recommended Posts

Posted (edited)

There are three kits: 

1. Outlaw - Most aggressive https://www.holley.com/products/exhaust/exhaust_systems/flowmaster/flowfx/parts/718111

2. American Thunder - mid aggressive https://www.holley.com/products/exhaust/exhaust_systems/flowmaster/american_thunder/parts/817933

3. FlowFX - least aggressive.  https://www.holley.com/products/exhaust/exhaust_systems/flowmaster/outlaw_series/parts/818112

 

Who has had the FlowFX?  Does it drone bad?  I know, it's all relative, give me some feedback.

 

On Friday afternoons after a couple beers I'm more along the lines of, "F-it.  I'm getting the Outlaw kit".  The 6 other days, I'm thinking FlowFX.  I hate my moments indecision.  

 

 

Edited by NWSierra
  • Haha 1
Posted
On 3/22/2023 at 12:47 PM, NWSierra said:

There are three kits: 

1. Outlaw - Most aggressive https://www.holley.com/products/exhaust/exhaust_systems/flowmaster/flowfx/parts/718111

2. American Thunder - mid aggressive https://www.holley.com/products/exhaust/exhaust_systems/flowmaster/american_thunder/parts/817933

3. FlowFX - least aggressive.  https://www.holley.com/products/exhaust/exhaust_systems/flowmaster/outlaw_series/parts/818112

 

Who has had the FlowFX?  Does it drone bad?  I know, it's all relative, give me some feedback.

 

On Friday afternoons after a couple beers I'm more along the lines of, "F-it.  I'm getting the Outlaw kit".  The 6 other days, I'm thinking FlowFX.  I hate my moments indecision.  

 

 

Your links are reversed. I listened to them and was like wow the first one seems mild and it’s supposed to be the loudest?

 

I like the outlaw sound. 
 Isn’t the stock exhaust 3.5” why would these neck down to 3”?

  • 1 month later...
Posted

Just wondering, the own muffler being so large, if larger pipes would be any benefit without the little glass pack, or if it would still be to restrictive to matter. Honestly, it's the pipes in front of the muffler at the cats, that's looking quite rusty already.

Posted
On 4/3/2023 at 2:55 PM, Cheekster96 said:

I put in a cat-back from MBRP.  LOVE IT!!

mbrp.jpg

I like the sound of those too. Dual's are probably half for looks, just partial to dual pipes on what I ride. 

Posted

I think my perfect exhaust would sound exactly like the factory system but getting rid of that huge muffler.  Does that exist?

  • Like 1
Posted
8 hours ago, Jettech1 said:

I think my perfect exhaust would sound exactly like the factory system but getting rid of that huge muffler.  Does that exist?

The manufacturers has  done the research as far as noise vs flow. Restrictions cost HP. I’ve seen exhaust test versus exhaust configuration and large single exhaust won. The muffler is large to reduce sound keep flow. 

  • Like 1
Posted
12 hours ago, KARNUT said:

The manufacturers has  done the research as far as noise vs flow. Restrictions cost HP. I’ve seen exhaust test versus exhaust configuration and large single exhaust won. The muffler is large to reduce sound keep flow. 

You're right...I had a vision.....lol...it doesn't exist right now.  Maybe someday...

Posted
10 minutes ago, Jettech1 said:

You're right...I had a vision.....lol...it doesn't exist right now.  Maybe someday...

The avalanche is the only one I haven’t put loud exhaust on. I still may I never say never. It actually has some sound stock. 

  • Like 1
Posted
On 4/3/2023 at 5:55 PM, Cheekster96 said:

I put in a cat-back from MBRP.  LOVE IT!!

mbrp.jpg

 

just ordered.  Love the MBRP, put it on everything.

 

With that said, I think I see the answer, but you have to cut it to get the old one off?  

Posted

You can probably get away with not cutting it. But I did and was alot easier to remove it around the rear axle.

About 3000 miles on it, still sounds good and I love it!

Posted

If you buy Flowmaster keep the stock so in 2 years when it rusts off you can reinstall the factory 

  • Like 2

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
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts
  • Member Statistics

    342,758
    Total Members
    8,960
    Most Online
    Randy Ginoza
    Newest Member
    Randy Ginoza
    Joined
  • Who's Online   5 Members, 0 Anonymous, 1,769 Guests (See full list)


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