Jump to content

2021 Trailboss Manual to Electric Driver Seat

Sloanie

By Sloanie
in Modifications, Wheels & Tires

 Share

Recommended Posts

Sloanie New Member

Sloanie

Posted
Posted

I have read your forums about installing an electric seat in place of a manual on a Silverado Trailboss. I wanted to share my experience. On a 2021 Tail Boss I removed the manual driver seat. I was able to purchase an electric seat out of a 2020 Silverado with 23 miles on it ($400). Attaches below is a Power Point I put together to help explain or guide you threw the installation. The seat I purchased had the side air bags in it. Seat bolts right in. Plug the truck harness into the seat and the air bag system works as it should. There are three wires to terminate. The black one is ground, Red is seat power 12 volts, and the small yellow/black strip wire is the lumbar 12 volts. I found no 12vt power in the two wires. I broke these out of the harness and wired them together and connected 12 volts to them. Simply Ran a Red 12vt wire using a 30 amp fuse. Grounded the black wire under the seat to the body. The electric seat including the lumbar works fine. The air bag system is still happy and working. I'm 5'2" and needed the addition. 

image.thumb.png.e7aac63336541f3ab51eee1118c23660.png

  • Like 2
  • 2 weeks later...
Jason k Enthusiast

Jason k

Posted
Posted

Thank you, this is absolutely amazing, ive been trying to figure this out since I got mine, i might actually be able to keep it now

Dunn Senior Enthusiast

Dunn

Posted
Posted

seats are really low in these trucks....i am 6ft and still it would be an issue if i didnt have power seats

  • 3 months later...
Dunn Senior Enthusiast

Dunn

Posted
Posted

i would be interested in doing passenger seat but the ebay link doesnt work

Djr1209 Enthusiast

Djr1209

Posted
Posted

I wish I could find an electric seat like you did to replace my manual seat. Did you find yours locally or somewhere online? Thanks. 

Dunn Senior Enthusiast

Dunn

Posted
Posted

Actually I use a seat cushion and seat cover in my truck and stock settings on the seat aren't bad now....prior to that they felt too low...

Would just like to match the driver seat someday though....

  • 4 weeks later...
Smeastman Enthusiast

Smeastman

Posted
Posted

I have the front seats and center console with storage from my SLE for sale. The drivers seat is power, the owner Passengers seat is manual, both with airbags. 

GreatWhiteMexican Enthusiast

GreatWhiteMexican

Posted
Posted
On 6/13/2021 at 5:28 PM, Smeastman said:

I have the front seats and center console with storage from my SLE for sale. The drivers seat is power, the owner Passengers seat is manual, both with airbags. 

What color and type of material are you seats?

  • 2 weeks later...
  • 6 months later...

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
 Share
Go to topic listing

  • Latest Articles

  • Posts

    • Jake87
      2027 GMC Sierra: Official Discussion

      By Jake87 · Posted

      I hope to high heaven this is wrong. My Chevy farm trucks frame is lasting way longer than a newer Nissan Titan XD I got for a steal, and it only pulls trailers. A decade younger and it's frame is already way rustier than the waxed Chevy I drive across longs and ditches. Also, hasn't Ford been having tones of troubles with rusted frames? 
    • Coastie05
      2027 GMC Sierra: Official Discussion

      By Coastie05 · Posted

      Batteries don’t always show signs of a few years ago my vehicle started fine in the morning and took me to work. After work the battery was completely dead and I needed a jump. No, I didn’t leave anything on and the battery was only a couple months old. It was replaced under warranty. 
    • Jake87
      2027 GMC Sierra: Official Discussion

      By Jake87 · Posted

      AFM is confirmed in the Corvette engine, so I'm assuming the higher volume trucks will get it as well
    • NDKoze
      2027 GMC Sierra: Official Discussion

      By NDKoze · Posted

      If his battery was that bad I would think it would have been showing signs before this that were ignored. Stinks that it happened the way it did in rush hour traffic, but this seems like a pretty fringe scenario. I don't mind it that bad and never turn it off. The only slight annoyance for me is the slight delay between brake to gas, but I have gotten used to it and figure if it can save a little gas why not.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That is a good correction. I think “severity” was probably the wrong word for what I meant. What I really mean is closer to event priority, relevance, and actionability — not “this code is severe” or “replace this part.” I agree that a truck can have a lot of trivial or historical communication codes, and if the product starts pushing alerts for every stored or low-value event, people will ignore it very quickly. So the alert logic would need to be filtered. For example, I would not want a random old communication code to generate a push notification by itself. A useful alert would probably need to be based on things like: - new vs historical - active vs stored - repeated vs one-time - duration of the event - whether it happened near the driver-marked symptom - whether it happened together with voltage drop, reset, bus-off, misfire, oil-pressure change, etc. - whether the same pattern repeats under similar conditions So instead of saying “severity,” maybe the product should organize events by affected system and priority. For example: Misfire event: Show misfire counts / roughness first, then fuel trims, RPM/load, DFM/AFM state if available, coolant/oil temp, voltage, and related DTCs. Oil-pressure event: Show oil pressure first, but only in context — RPM, load, oil temperature, coolant temperature, DFM/AFM state if available, voltage, and baseline comparison. Communication event: Show which module/network/message dropped, whether voltage dropped, whether the recorder reset, whether it was active or historical, and whether it repeated. Voltage/reset event: Show battery voltage, crank/wake/sleep state, module reset, communication dropouts, and what came back online first. That also solves the display-order problem you mentioned. The main report should not always show the same fixed list first. It should show the system that appears abnormal first, and then the supporting values for that system. I also agree that the truck already has an oil pressure gauge and MIL. The point would not be to duplicate those. The value would be in showing what else was happening before and after the warning or symptom. For example, if the MIL comes on for a misfire, the truck already told the driver there is a problem. The useful part would be: - which cylinder or bank looked abnormal first - whether it happened after an AFM/DFM transition - whether fuel trims were already moving - whether oil pressure or voltage changed at the same time - whether the same pattern happened previously without a MIL On the OBD port point, I think you may be right for a consumer-facing version. OBD is much easier for the average owner: - easier install - easier removal - inside the cabin - easier phone connection - easier data download - easier to include a pass-through port for another scanner OBD is also the right place for DTCs, freeze frame, VIN, calibration information, Mode 6, and normal scan-tool parameters. The reason I was looking at ECM-side recording is that some events may be gone by the time someone plugs in a scanner, and some powertrain-side network evidence may not be available the same way through the DLC. But I agree that if an OBD-based version can capture enough useful evidence for most owners, that is probably the cleaner consumer product. Maybe the split is: - OBD/DLC version for most consumers - ECM-side version only if it proves it adds evidence that the OBD version cannot get - shop/pro version if deeper powertrain-side event evidence is actually useful So I would not want to force the inline approach if the OBD workflow solves most of the real-world problem. Your last point is probably the key product requirement: the report should be specific to the system showing the abnormality. Not “here are 50 parameters.” More like: “Misfire-related event detected. Here are the misfire/fuel/DFM/context values.” or “Oil-pressure-related event detected. Here is oil pressure compared with RPM/load/temp/baseline.” or “Communication event detected. Here is what dropped, when, and whether voltage/reset happened first.” That is a much better way to think about the report.

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...