Jump to content

Recommended Posts

Posted

 

If you go the turndown method, whether its before or after the cab, I would do Single in/Dual out. From my experience if your going to dump it, it kinda looks better with duals. Not that you will ever really see it unless your looking for it, but if you bend over right and looking in from the back right wheel well, you can see it. Also, if you are to run over the axle, you can have a pipe on each side of the truck so the sound is balanced.

 

Hey no worries man. I've done my good share of research over the years so I don't mind helping out. There's some things I know more about than other things. I know exhaust pretty well so just trying to spread the knowledge and help out where I can. That's why I made that video. When I was looking, I couldnt find a video that showed me everything I wanted to see so I solved that problem for anyone else who's looking.

Yeah I like the idea of the balanced sound. So looking at magnaflows, I can only find a 3" with a dual 2.5" out. Is that what I would be looking to get?

Also, so even though the tips will be hidden, is it better to get tips instead of just cutting the pipe?

Posted

The tip is a single outlet also instead of Corsa's dual outlet. The Corsa also has a section of flex pipe in the intermediate pipe but other than that I cannot explain the $600 price difference. I got the 304 info from autoanything.com also as it doesn't specify which type of stainless on Volant's website.

I was going to put the black corsa tips on it anyway haha

 

Sent from my Note 4 on Tapashit

Posted

Yeah I like the idea of the balanced sound. So looking at magnaflows, I can only find a 3" with a dual 2.5" out. Is that what I would be looking to get?

Also, so even though the tips will be hidden, is it better to get tips instead of just cutting the pipe?

Yea that should work. If your going to do turn downs, you probably don't need tips. Up to you tho.

  • Like 1
Posted

Yea that should work. If your going to do turn downs, you probably don't need tips. Up to you tho.

right on thanks for all the help!

Posted

It sounds killer when you get on it. Cruising at 65 yesterday I couldn't hear it with the radio on.

And V4 mode really isn't bad at all.

 

And it may just be a convenient coincidence, but my 25mile mpg avg went up almost 3 mpg already with typical driving in the city i do almost every day.

I'll let you know if that holds true.

A week later and a couple hundred miles of driving and my gas mileage is still up and I havent been anywhere out of the ordinary. And the "drone" that everyone talks about, if the radio is even on a little bit I can't hear it. It's still got a phenomenal tone upon acceleration and when cruising it is low enough that it is hardly noticeable.

I drove at 65 - 75 for a little bit this weekend and the drone can still hardly be heard with the radio on even a little bit.

 

So for anyone debating on a 14" Magnaflow. I don't think it's too loud at all.

I got a 14" Magnaflow, cut the third cat and did 3" pipe from the Y all the way out.

  • Like 2
Posted

I just dropped mine off at the muffler shop to have my 14" magnaflow installed. Will be cutting out the resonator and flapper... will update after I pick it up! Ready to hear some rumble!

  • Like 2
Posted

I love my hidden dump before axle. I wanted exaust for better performance and because I wanted to hear my truck without having to roll my windows down

 

Sent from my SM-N920V using Tapatalk

Posted

 

and there is a video of it

 

Sent from my SM-N920V using Tapatalk

Posted

Just picked mine up... swapped out for 14" magnaflow muffler, resonator and flapper delete. LOVE IT! I was on way to an appt so never got on the highway but many times from 0-50ish and dont have a single complaint. No chopper, etc but as I said I will update again later after I can get it out on the highway. It is pretty quiet at a stable mph but any acceleration and it sounds great with a deep growl. I will try to get a video or two this weekend. Couldnt be happier... highly recommend this setup.

  • Like 1
Posted

Installed the Borla muffler that they have on clearance now. It was an easy quick install at home. I just clamped it in to make sure I like it. I'll have my shop weld it in and remove the flapper and resonator at a later time. I have the flapper clamped open for now. It sounds nice. A little louder than stock but a nice low tone growl when the throttle is pressed. It's not overpowering and the V4 change is almost non existent. It's really a nice muffler for those that only want a moderate increase in sound but with a lower tone. I drive the same routes a lot and have noticed over a 1mpg gain. I put over 200mi on it today alone. I also want to note that at first it was very quiet (close to stock) and started to change after an hour or 2 of driving to get to where it is.

http://www.borla.com/products/muffler:_675_rd__x_2400_lon_part__19131347.html

82e0ea600a8385ffa76a644f06c03bb7.jpg

 

 

Sent from my iPad using Tapatalk

Posted

please advise on drone and chopper!

I personally love the drone. It's too quiet when it's in v8 causing on the highway.....I have a Flowmaster 40 series
Posted

Local shop I nstalled the Borla XR-1 part #40722 last Friday. Left the flapper and resonator for now to keep wife happy. One small road trip and a week later I'm very happy happy (i.e. No wife complaining). Hear it upon startup and when you get on it but not while cruising.

 

 

Sent from my iPhone using Tapatalk

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

    • Did have to make 1 modification because of the WeatherTech rear mud flaps and that was needing 3 longer screws than what came with the install package. 😄
    • Picked up the liners yesterday. Installed passenger side WITHOUT any modifications. All mounting holes lined up perfectly. Rain is interfering today with drivers side. Very Happy! Will add pics when finished
    • As a matter of amusement I’ll leave this conversation with this. Do you beat the government average fuel estimate? Statistics are a guide to me. Not a rule. Someone once said I have to have the last word. If true and possible may be. I’ll blame that on working in a family business.
    • That is a fair point, and I agree that trying to log “everything in the truck” would be the wrong direction.   There are a lot of modules and a lot of traffic. If the product became a full-truck datalogger, the amount of data would get huge very quickly, and most owners would never use it.   I think the first useful version would need to be narrow: - powertrain-side event evidence - selected high-value parameters - communication / voltage / reset events - pre/post event window - short report first, raw log only as backup   One distinction I should make is between active OBD/PID polling and passive bus capture. If you are polling PIDs through OBD, then yes: the more parameters you request, the lower the effective sample rate becomes, and you are adding diagnostic traffic to a vehicle that is already busy running itself. With passive CAN capture, the recorder is not asking all the modules for data. It is listening to traffic that is already on the bus. So it does not consume vehicle bus bandwidth in the same way that a scan tool polling hundreds of PIDs would. But your point still applies in a different way.   Even if passive capture does not add bus traffic, the recorder still has limits: - processing rate - storage rate - timestamp accuracy - decoder workload - event filtering - report size - user attention span   So the answer cannot be “log everything and let the user figure it out.” The product would need to store enough raw evidence to be useful, but only decode, graph, and present the important parts around the event.   A practical report should probably show: - what triggered the capture - how much pre/post data was preserved - which selected parameters changed - how those values compared to baseline - whether the same pattern happened before - whether any voltage, reset, bus-off, lost-message, or communication fault occurred - selected graphs around the event - raw data only as supporting evidence   So I agree with you. More data is not automatically better. The real product is the reduction from raw data into a useful event report.
    • That makes sense, and I agree with most of that.   I think the product would need both: 1. a default powertrain template, so it is useful out of the box; 2. user-selected priority parameters, so the owner or shop can choose what they want to see first.   Different users are going to care about different things. One owner may care about oil pressure and voltage. Another may care about misfire trend, AFM/DFM behavior, or U-codes. A shop may want communication events and repeatability first. Your baseline point is probably the most important one. Raw data is not very useful unless the report can show what normal looked like for that vehicle under similar conditions.   The way I would think about it is: - start with a basic known-good baseline - learn normal behavior for that specific vehicle over time - allow the event to be overlaid against baseline - show whether the event was a one-time spike or a repeatable pattern - provide a simple severity level, but with clear limits on what that severity means   For example, early severity could be something like: - Info: event captured, no obvious abnormal pattern - Watch: value moved outside baseline, but not repeated - Warning: repeatable abnormal pattern under similar conditions - Critical: communication loss, voltage drop, bus-off, reset, or severe repeated event   I would not want the first version to say “replace this part.” That would be overclaiming unless there is repair-confirmed data behind it. It would be more honest to say “this pattern deserves inspection.”   On the OBD port question, I think OBD absolutely has a role. OBD is probably the right place for: - DTCs - freeze frame - VIN - calibration information - normal scan-tool parameters - Mode 6 / enhanced diagnostic data if available The reason I am still looking at an ECM-side recorder is that the failure may happen before anyone connects a scan tool. If the owner plugs in a scanner after the event, the pre-event evidence may already be gone unless the ECU happened to save it. So I do not see this as “OBD versus ECM-side.” I see it more like: - ECM-side recorder: always armed, rolling buffer, event evidence - OBD/DLC companion: DTCs, freeze frame, VIN, calibration, normal scan data - phone/cloud: status, notes, upload, report generation, notifications   I agree that phone connection and push notifications would be useful. I just would not want the phone or cloud connection to be required for capture. The recorder should save the event locally even if the phone is not connected. The phone should help with event marking, download, notes, upload, alerts, and report viewing.   For a default GM V8 event report, would this list make sense? - RPM - calculated load / MAP - throttle position - vehicle speed - gear / torque converter state if available - coolant temperature - oil pressure - oil temperature if available - battery voltage - commanded AFM/DFM state if available - actual AFM/DFM state if available - misfire counters / roughness by cylinder if available - fuel trims - relevant U-codes / communication events - bus-off / lost periodic message / module reset / voltage drop events Which of those would you remove, and what would you add?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...