Jump to content

Recommended Posts

Posted

Dtom, is it loud like, " holy f don't wake the neighbors!!!" ? From the clips I've heard it sounds amazing but just nervous on after the install thinking the cops are gonna wanna talk to me all the time or be "that guy". Not to worried about drone really but do you get any? And is it noticeable in cabin and is it quiet enough that you can talk to someone in the truck or listen to the radio? Any sound clips?

 

Sent from my Nexus 6P using Tapatalk

It won't draw any attention from the cops whatsoever. It can be loud on start up but calms down as the engine warms up. Under acceleration it sounds great but not obnoxious. I have a regular cab pickup and with the music at a comfortable listening level it drowns out the exhaust, and drone hasn't been a problem for me at all. Even though it sounds great I'll be changing my system for something a little louder since I like my trucks on the louder side.

 

Sent from my SAMSUNG-SM-G890A using Tapatalk

  • Like 2
Posted

It won't draw any attention from the cops whatsoever. It can be loud on start up but calms down as the engine warms up. Under acceleration it sounds great but not obnoxious. I have a regular cab pickup and with the music at a comfortable listening level it drowns out the exhaust, and drone hasn't been a problem for me at all. Even though it sounds great I'll be changing my system for something a little louder since I like my trucks on the louder side.

 

Sent from my SAMSUNG-SM-G890A using Tapatalk

Any way for a video clip on the sound. Now I'm at a cross between this and that are rebel posted a bit ago

 

Sent from my Nexus 6P using Tapatalk

  • 2 weeks later...
Posted (edited)

Finally got a min to make a quick video of the aFe Rebel exhaust. Sorry for the bad quality, the gopro didn't work out sound wise so this is from my iphone on lunch real quick. Didn't come through as loud as it really is.

 

 

 

 

What is the 'Range' device you mentioned?

 

Sorry, I found it. It is the V4 disabler. Was hoping for an in-line exhaust flap for the pipes.

Edited by TedH
Posted

Update.

 

Got my Borla on! I absolutely love the sound. Its a deep sound. Good at startup, nice cruise, no drone, and great under acceleration. Its a bit different under v4 mode, I can definitely tell when it goes into it. Its not annoying, or helicopter sound though. I'm going to give it a week or two and then decide if I throw the valve back on.

 

5.3 exhaust diameter is 3 inches <- search purposes.

 

You're a god among men for the last line of this post. I've been searching forever for the stock exhaust size so I can just cut mine off and replace with the XR-1, THANK YOU!

Posted (edited)

CaptainMcfunk What year is your truck? The stock piping on the newer 5.3's is 2.75". You still want a 3" muffler, just need an adapter or the stock piping flared up to 3".

Edited by Mh167002
  • Like 1
  • 2 weeks later...
Posted

CaptainMcfunk What year is your truck? The stock piping on the newer 5.3's is 2.75". You still want a 3" muffler, just need an adapter or the stock piping flared up to 3".

 

You're right on this one, I went to install it last night, and realized the 3" borla was bigger than the stock piping, so i need to get adapters.

 

Also, for anyone running the XR1 muffler on a 2014+ 5.3 -- Did you remove the resonator at the rear of the truck (that's over the rear axle)? I have the 3" in/out XR1 muffler that i'm going to replace the stock with, but need to know if I also need to remove the stock resonator at the back of the truck, or leave it in place?

 

Thanks all!

Posted (edited)

 

You're right on this one, I went to install it last night, and realized the 3" borla was bigger than the stock piping, so i need to get adapters.

 

Also, for anyone running the XR1 muffler on a 2014+ 5.3 -- Did you remove the resonator at the rear of the truck (that's over the rear axle)? I have the 3" in/out XR1 muffler that i'm going to replace the stock with, but need to know if I also need to remove the stock resonator at the back of the truck, or leave it in place?

 

Thanks all!

I have my resonator in place still.

 

I had it out, but with Catless headers, it was too raspy.

 

If you have the factory manifolds on still, I'd remove the resonator.

 

 

Sent from my SM-G930V using Tapatalk

Edited by Rawyzf
Posted

This is what I want. The borla s-type exhaust sound. The problem is the borla is a 2.25 inch system. I want a 3 inch system. Is there another muffler that compares to the borla s-type. I was thinking the magnaflow 18 inch is comparable but I'm not sure. I want to have the 3inch system after watching this video. 2.25 restricts the engine too much.

 

 

Posted

 

You're right on this one, I went to install it last night, and realized the 3" borla was bigger than the stock piping, so i need to get adapters.

 

Also, for anyone running the XR1 muffler on a 2014+ 5.3 -- Did you remove the resonator at the rear of the truck (that's over the rear axle)? I have the 3" in/out XR1 muffler that i'm going to replace the stock with, but need to know if I also need to remove the stock resonator at the back of the truck, or leave it in place?

 

Thanks all!

I second what RAWYZF said. Which XR-1 did you go with and what are your future plans with manifolds and cats?

  • Like 1
Posted

This is what I want. The borla s-type exhaust sound. The problem is the borla is a 2.25 inch system. I want a 3 inch system. Is there another muffler that compares to the borla s-type. I was thinking the magnaflow 18 inch is comparable but I'm not sure. I want to have the 3inch system after watching this video. 2.25 restricts the engine too much.

 

 

ProXS?

I really like my Blackwidow exhaust.

 

 

 

 

 

Sent from my SM-G930V using Tapatalk

Posted
ProXS?

 

Yes I like the pro xs but it's still 3 in in 2.25 or 2.5 out. like the video attached says lots of decreased hp with 2.5 in exhaust. Also backpressure is a myth IMO. IM learning towards Magnaflow 14 inch. I think that is more inline with the agressiveness of the borla s-type. Unless someone disagrees?

Posted

ProXS is 3 in and out.

 

Sent from my SM-G930V 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

    • 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?
    • I went to the county a few years back to dispute my property taxes. To do that I hired an appraiser and a lawyer. The County Assessor wished to argue that the homes in my neighborhood the appraiser used were all 'distressed properties" and not representative of the "Market Average".    My response was," Of the 50 homes in our subdivision 43 of them were "distressed properties" under bank foreclosure and as such "Distressed IS the market". Lawyer about choked on his coffee and handed the Assessor the 'receipts'.    I won that case on the evidence provided by the Lawyer and the Appraiser.    We have the same thing going on here. My statements were based on the GOVERNMENTS NATIONAL DATA and yours on local markets in areas of your interest. They are both correct....   Thing is, this divergence was based on NATIONAL and not on LOCAL. I think you even understand that. But like you said, we are both stubborn and hardheaded.    I do not see any advantage to disengagement.  But that said we can step back to compose ourselves. 
    • Trust me I appreciate the comments and concerns. It's what I was looking for to help me evaluate the situation and what I want to do. I have decided to move forward with the BORA hubcentric slip on 3/8" (.375") with the extended lugs nuts. Fedex says they should be here Monday :). Meanwhile, the dealer got the remote start and Patriot spray in bed liner done over the last couple of days. Also, I installed an inline stop/start eliminator today. Starts back up in what whatever mode you shut it off in, so you don't have to hit the button every time you fire up.
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...