Jump to content

Recommended Posts

Posted

I have a 2017 Silverado standard cab work truck, which has the standard basic manual seats. I found some power seats from a wrecked 2014 GMC sierra crew cab, will these fit in my standard cab? Also, will the power seats actually be able to work in my standard cab? 

Posted

My double cab 14 same basic setup had a diff wiring harness the upper level trucks. Mone of the wiring was there and i had to use the old harness for the seat belt or something. Iirc someone makes a harness for the swap. Maybe harnessdoctor.com 

  • Like 1
Posted

I have just purchased a full set of Denali heated/cooled 10 way power seats, and will be doing this upgrade soon on my 14 RCLB 2WT Silverado.

I have not looked at the wiring in my truck to see if the power wires are populated (I will be installing these one way or another regardless). There are a lot of discussions about this, but the general gist of things are two things:

 

1. You may or may not have the power feeds populated in the main seat connector (big yellow plug under seat).

2. Depending on the seats you buy (memory vs no memory, heated/cooled or not, Denali, etc) you may need to bypass  the memory seat module and/or reconfigure the seat position sensor.

 

Harness Dr sells some harnesses to resolve these issues (pgamboa on these forums).

 

If your capable of working with wiring (cutting, soldering, etc) then most of the work is fairly easy. If you do not buy seats  that have the memory module, then just power/ground is needed. Getting heated/cooling functionality working is much more involved process, not for the faint hearted. If you do have memory seats, the module is easily bypassed by applying power to pin23 red/black wire, in addition to the main power wire (red/yellow, pin 2).

Here is one of several threads, with a lot of posts, about seat swaps:

The vast majority of trucks are crew cab, but I see no reason seat upgrades cannot be done to regular cabs. If you like, I can post updates here on how my install results. It may take a month, depending on postage and delivery of the seats and my work schedule (75+ hours a week). First stage will be just getting the seats in, power movement working, and airbag system happy. Heated/cooling will be the second stage, but that will take much longer as I have to develop a controller to interface with the seats and the OEM controls. There is an option to have your BCM reprogrammed to enable heated seats (among other things), but this is $250USD+ ($600USD if you go the AutoSync method). I will be doing it my own way.

 

  • Like 1
Posted

Yeah the long work weeks has really been a drag, it was because the other tech for my area cold turkey quit... Now its just me, and it's hard to find any capable replacement. Basically doing the work of two, however, it has been great for making some goals finally fundable without any worry though :)

 

I have the Mcgaughys installed now. I had planned on doing a video and recorded the install I did in my garage, just never got to the editing as I didn't think there would be much interest. Kit has been great though... albeit now the 33" tires I have seem too small haha. Rubbing on these trucks an achilles heel.

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