Jump to content

Recommended Posts

Posted

Yes, If you drop the spare tire. Mine came out in one piece.

Posted

I think its possible to even w/o removing the spare, if you're on a lift, it may be easier.

Posted

You will have a lot more room if the rear axel is hanging down (Wheels not on the ground)

 

Posted

Yes this is possible at least for a crew cab short bed.  As NHUSA mentioned if you can get the right rear wheel off of the ground then you can get it out.  I did this alone and without removing the spare and it wasnt too bad.  A helper and removal of the spare would have saved me a good bit of time and effort of going back to front to make adjustments.  

  • Like 1
Posted

I did it on a lift and still needed to drop the spare to have room to come out the back on my 2018 crew cab 6.2.

Posted

Yes. I did mine by jacking passenger side up so the rear wheel is just on the ground. Drop the spare and get it out of there (check the psi in the spare when it is off). The trick is you have to move the exhaust to the rear, and you will get it to a point where the muffler is just before (or after cant remember) the axle, you need to rotate the entire exhaust system (don't remember which way try both). Then you can slide it out the back. I had my neighbor hold the end of the tail pipe when I was sliding it back to keep it from hitting the truck paint but you can do it yourself.

Sent from my Pixel 2 using Tapatalk

Posted
Excellent. Thanks for the feedback guys. So it's much easier to put the frame on jackstands so the rear axle is at full droop?
I only did the passenger rear corner. I out the jack on the frame about where the muffler is as far back as I could go before the frame starts to curve up. Then put a few jack stands extra safety.
Others may have done it differently but that's how I did it.

Sent from my Pixel 2 using Tapatalk

Posted (edited)

Anyone looking to sell there stock exhaust take off? My exhaust shop butchered mine and i'm now looking to trade my truck in for a car as I've sold my boat and race car so the Sierra needs to go. Maybe i'm blind but i'm struggling to find a used classified page on here. Trying to limit creating a new thread and getting stoned to death for doing so. 

 

Just looking from the converter back in one piece. So just the exhaust pipe and mufflers if possible. 

 

 

gmc exhaust.png

Edited by SprinterNick
Posted
Anyone looking to sell there stock exhaust take off? My exhaust shop butchered mine and i'm now looking to trade my truck in for a car as I've sold my boat and race car so the Sierra needs to go. Maybe i'm blind but i'm struggling to find a used classified page on here. Trying to limit creating a new thread and getting stoned to death for doing so. 
 
Just looking from the converter back in one piece. So just the exhaust pipe and mufflers if possible. 
 
 
5c76cf4752320_gmcexhaust.png.d9fd4b1eeb754b86c3f0abb9bacd5696.png
Did you check your local Craigslist? Seems like every time I look on mine someone has a factory exhaust for $150.

Sent from my Pixel 2 using Tapatalk

Posted

Yeah i see few on my local CL for 150 range. 

Why not just trade it in as is, they want the stock muffler back on?

Posted
Anyone looking to sell there stock exhaust take off? My exhaust shop butchered mine and i'm now looking to trade my truck in for a car as I've sold my boat and race car so the Sierra needs to go. Maybe i'm blind but i'm struggling to find a used classified page on here. Trying to limit creating a new thread and getting stoned to death for doing so. 
 
Just looking from the converter back in one piece. So just the exhaust pipe and mufflers if possible. 
 
 
5c76cf4752320_gmcexhaust.png.d9fd4b1eeb754b86c3f0abb9bacd5696.png

For Sale/Wanted
https://r.tapatalk.com/shareLink?share_fid=33003&share_sfid=14&url=https%3A%2F%2Fwww%2Egm-trucks%2Ecom%2Fforums%2Findex%2Ephp%3F%2Fforum%2F14-For-Sale-Wanted&share_type=sf
  • 2 years later...
Posted

I just removed a exhaust for the second time  in a Chevrolet Silverado 1500 from the Cat on and its hard but doable, this one was a 2010 and for the second time I remember removing the spare tire ahead of time would have saved me a hour of work.

  • Like 1

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,759
    Total Members
    8,960
    Most Online
    DM22
    Newest Member
    DM22
    Joined
  • Who's Online   5 Members, 1 Anonymous, 1,741 Guests (See full list)

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