Jump to content

$300 Blackleather Seats !

madupree55

Recommended Posts

madupree55 Enthusiast

madupree55

Posted
Posted

Well I went by my local GMC Dealership to see about getting some Katzkins or some kind of leather put in my truck. I happen to know the guy in the accessory dept and he informend me that they had just changed out some black leather seats for a elderly guy who wanted two-tone leather seats. He ended up letting me get the factory black leather seats from him for $300 i figured it was a pretty good deal and gave him the money right then and there without thinkin twice about it. Now comes the fun part of installing it this weekend. He said it is really simple installing it on the seats and the hardest part is gonna be actually removing the seats and center console (w/underseat storage)from the truck itself to install the leather. Anyone know of any type of tutorials i could find on the internet anywheres that would speed up the process????

RayGMC Enthusiast

RayGMC

Posted
Posted

Congrats on the awesome deal!! The seats are straight forward. The hardest part will be physically lifting them out of the truck. You will want to make sure you have the correct size socket for the job. I don't know the size off the top of my head but you will probably need the size in a deep socket and standard depth. If you have the money buy the ratchet wrench as well. You can use JL Audio's instructions to install the JL Stealthbox to guide you through the console removal. They make a sub box that replace the factory bose subwoofer. The back seat may require two people to remove and place back into the truck. When I took mine out to mount the amp on the back wall it was cumbersome to maneuver do to its split design. It tends to flop around while you are trying to move it.

madupree55 Enthusiast

madupree55

Posted
  • Author
Posted

Hmm i could use a set of them ratchet wrenches; they would be very beneficial huh??? Am i gonna need any of them hex wrenches or like them big allen head screws or star heads???

Jfriday Enthusiast

Jfriday

Posted
Posted

I did the same thing that you are going to. I just used a standard socket to get the seats out, but i don't remember the size. You will need a torx head socket to disconect the seatbealts from the front seats. The back seats were the hardest for me but after them the fronts were a breeze. It is a little time consuming, but be patient and remember that everything goes back on the same way it comes off. After I finished mine i was really wishing i had installed a heated seat kit. Its the perfect time to do it and it may be something you want to check into.

Hacker Enthusiast

Hacker

Posted
Posted

Get yourself some kind of pipe to put on your ratchet for more leverage. They use some kind of industrial strength lock tight on all the bolts and those things are TIGHT.

Hawaiian06 Enthusiast

Hawaiian06

Posted
Posted

You will nee a deep whell external Torx socket. For the front seat, the front mounting bolts are E18 and the rear bolts are E14. I'm not sure what size is required for the rear seat.

I replaced my jump seat with a center console and it went pretty smoothly with the right sockets.

External Torxs are kind of hard to find, but I was able to pick up a set at "Harbor Freight" for under $20.

Please post some pictures once you get done.

Archived

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

Go to topic listing

  • Latest Articles

  • Posts

    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      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. 😄
    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      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
    • KARNUT
      OCI, not when but why?

      By KARNUT · Posted

      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.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      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.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

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