Jump to content

Short tube and long tube


Recommended Posts

Posted

Might have a ridiculous question but I cant see the issue in theory so I am consulting the experts.

I have a 2015 2500 HD 6.0 4x4. I recently had long tubes installed. First finding long tubes for this application is insane. I could not specifically find anything that guaranteed fitment for this year. I ended up with speed engineering stainless that was made for the 6.0 up to 2013 according to them it should carry over in later years which is true given the L96 has changed little to none. I had zero fitment issue with the passenger side but the left was awful...... hit the motor mount, frame, and drive shaft. I had the shop modify the header to fit......being honest he did exactly that and I'm impressed but I believe the header is leaking like nobody's buisness due to the 8 different cuts and bends he made. and makes an awful sound I do not feel like going through hell and back or spend the money on another long tube header for that side to run into the same issue...... so what if I ran a shorty 1 7/8 stainless on the driver side and a 1 7/8 long tube on the passenger side? It's off the wall but why not? If the true duals x and I have a custom tune in theory it should not be an issue right?

Posted

I would not advise that one bit. I most certainly would have sent them back asap with pictures. To much money to throw away. My guess is they mig welding vs tig? I would keep what you have go back an have the fix it. Are you positive its not the collector leaking or flange? Now that you have heat cycled they will need to be tightened up almost always. Good luck! Lets see photos to.

Sent from my SM-G930V using Tapatalk

Posted

The cross over is for unequal exhaust after it not before. They have headers the you can assemble yourself. I would have went with the shorties or find a better welder.


Sent from my iPhone using Tapatalk

Posted

I wouldn't run a short and long.  The exhaust pulse should be equal for each side.  I can't really explain it but for the engine to run correctly they need to mirror each other.  That is why you see on stock vehicles like the Acadia the back side against the fire wall is looped before it meets the main tube. To equal the length of the front manifold exhaust tube.  If it didn't matter they would have just ran it into the main tube without the loop.

Posted
7 hours ago, Texas45 said:

Might have a ridiculous question but I cant see the issue in theory so I am consulting the experts.

I have a 2015 2500 HD 6.0 4x4. I recently had long tubes installed. First finding long tubes for this application is insane. I could not specifically find anything that guaranteed fitment for this year. I ended up with speed engineering stainless that was made for the 6.0 up to 2013 according to them it should carry over in later years which is true given the L96 has changed little to none. I had zero fitment issue with the passenger side but the left was awful...... hit the motor mount, frame, and drive shaft. I had the shop modify the header to fit......being honest he did exactly that and I'm impressed but I believe the header is leaking like nobody's buisness due to the 8 different cuts and bends he made. and makes an awful sound I do not feel like going through hell and back or spend the money on another long tube header for that side to run into the same issue...... so what if I ran a shorty 1 7/8 stainless on the driver side and a 1 7/8 long tube on the passenger side? It's off the wall but why not? If the true duals x and I have a custom tune in theory it should not be an issue right?

Be aware that headers are made to fit the vehicle, not just the motor.

 

Just because the same motor is in two different generations of vehicle, does not mean that headers will fit between the cars.

 

I had headers on my 2008 Pontiac G8 GT. Those headers would not work on my 2016 Chevrolet SS, despite both cars being LS V8s with the same overall exhaust port design on their heads, and both vehicles being a Holden Commodore manufactured in Australia.  The G8 is a VE Commodore, the SS was a VF II Commodore.

 

Now, shorties? May fit between generations, but IMO shorties are a waste; if you're going to get headers, get long tubes.

  • 1 year later...

Archived

This topic is now archived and is closed to further replies.

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