Jump to content

Recommended Posts

Posted

 

Hello Everyone!

 

Its been some time since i installed a set of Speed Engineering Long Tubes on My 2015 5.3 and i thought it would be a good idea to make a YouTube Review on Them.

 

I had been looking at Long Tube Header options without much intention of buying, because i was pretty happy with my exhaust set up (Stock Manifolds, Deleted Cats, Deleted Muffler, Deleted Flapper and just leaving the stock 12" resonator).

 

 Also with most Long Tube Header prices from reputable brands like kooks being north of $1,000.00 Dollars, lets just say i felt a bit disencouraged, since the only brand that was even remotely affordable for me was Texas Speed.

 

Keep in mind that i live in Mexico, so shipping a big heavy box and taxes will add about $400 dollars to the price on the product.

 

The first time i found the Speed Engineering Headers it was on eBay, and I of course, dismissed them as being cheap chinese headers, but boy was i wrong to prejudge.

 

My Best Friend and CoWorker Jose Angel was also looking into Long Tube Header Options for his 2010 6.2 Camaro SS, and he was the one that convinced me that Speed Engineering would be a good option. To be honest, i just let him order his Headers first so i could see them in the flesh and checked them one they were installed, since i was concerned about the quality of the materials and how well the headers would fit.

 

Once they arrived, Surprise, they are good stainless steel, high quality welds and fit his Camaro Perfectly, so im inmediatly hooked and Jose does me a solid by orderng a set for my truck.

 

In the end, i had them installed at a good shop, because i have never installed a set and i didnt want to mess anything up. 

 

After almost 2 years of daily use and almost daily hooning, the Headers have held up perfectly, no cracks, no leaks, no problems at all (knock on wood), so i can very much reccomend them knowing that they have also been flawless in Jose´s Camaro.

 

The Headers were installed with a custom exhaust:

 

-Speed Engineering Long Tubes, 1 7/8" primaries to 3" Collectors

-2 Cherry Bomb 3"X- Pipes welded together (Double X Pipe)

-2 3" Small Magnaflow Mufflers

-Full 3" Dual Exhaust

-2 4" Tips to the side

 

I will leave a link to the final custom exhaust video at the end.

 

TL;DR They are very much worth it and im actually impressed with the Quality for that Price, and here is a video about it:

 

 

 

 

 

Full Custom 3" exhaust on the truck:

 

 

  • 1 year later...
Posted
6 hours ago, Lowz71 said:

Hey do you know if the driver side primary had to be modified in order to clear your drive shaft ? 

Mine did not

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