Jump to content

Recommended Posts

Posted

2025 Silverado 1500 High Country with power tailgate (non multi flex). Looking for a way to delete the power raise/lower feature and have the tailgate operate in the same way it would on a lower trim model without the power actuator. It seems like it should be possible because in some situations you can raise and lower it without the actuator assist and it feels just like the normal manual tailgate. 

 

I don't really have a use for this feature, and what I'm trying to be able to do is open the tailgate just a few inches to access the tonneau cover latch in situations where the tailgate can't open all the way (backed in against a fence, bike hitch rack installed). You can press the tailgate button a second time to stop the motion, but sometimes the actuator will resume if you subsequently lower the tailgate a little bit. It's already gone rogue on me once and gotten a pretty good scratch against a bike pedal. The only other way I've found to stop it is to block its motion, but that can't be good for the actuator in the long term. 

 

Does anyone know any kind of button-pushing cheat code to disable it? 

 

I tried unplugging the harness from the actuator, but somehow the actuator is tied into the logic for the latch. Having the actuator unplugged prevents the tailgate from unlatching and opening. 

 

Unless there's an easier way, it shouldn't be too hard to install a switch that would interrupt power to actuator motor, essentially allowing you to toggle the feature on and off. Does anyone know where to find a wiring diagram for the tailgate harnesses? 

 

Any ideas are appreciated. Thanks for the help. 

 

 

 

 

IMG_20250118_165750980_HDR.jpg

IMG_20250118_164813823_HDR.jpg

IMG_20250118_164809436_HDR.jpg

Posted

I don't think there's a real way to stop it. I was lucky one time where I opened the tailgate and didn't let it finish opening all the way and pulled it shut as it was still opening. This caused the tailgate to lock itself out and I couldn't get the bastard open until I went back out to my truck a half hour later. When it locked out, it would not pulse the locks to unlock the tailgate but the parking lights would flash and the door speakers would chime like normal for an unlocked tailgate but it wouldn't budge.

 

With that knowledge and experience I had, I think if you defeat the motor you would likely not be able to just remove the connector going to the motor as I would imagine it would still cause you to not be able to release the lock on each side of the tailgate.

 

Your only options I believe are to push the button to get it to start opening and press it again to stop the motion and let it go free range, don't open it up too far because the tilt sensor would see you're opening/closing it and begin engaging the motor again. Or you could open the tailgate and as it's opening, pull up on it to make resistance and it will give an error beep at the tailgate but it would stop the motion and as long as you don't tilt the tailgate too much the tilt sensor will not engage and tell it to open/close further again.

 

My experience is if you force the tailgate, it thinks something is in the way and it stops the motor in that direction. Example, you're opening it and you pull the tailgate upward like you're closing it, it will stop it from trying to re-engage the opening sequence until you latch the tailgate shut again BUT it will let you tilt it up and it will engage the motor to shut it.

Posted

@kickass audio, everything you said matches the experience I've had so far. You can definitely work around it if you know exactly how it works. I'd love to find a way to simplify it for people who aren't experts in defeating GM power assist technology (like anybody but me trying to open the tailgate and not damage it). 

  • 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,758
    Total Members
    8,960
    Most Online
    Randy Ginoza
    Newest Member
    Randy Ginoza
    Joined
  • Who's Online   3 Members, 0 Anonymous, 1,916 Guests (See full list)

  • Latest Articles

  • Posts

    • I thought I would use your thread and add to it as I just did my first longer drive with my truck in the last couple of days. I drove from the Grande Prairie area of Alberta down to Edmonton and most of where I drove in the city was the ring road so fairly free flowing but a bit of stop and go as well in the city. Stayed the night and returned home and not too many stops along the way each way but every restart and certainly every cold start sets it back for fuel mileage. Why I say that is I see some people will cherry pick a fuel mileage leg after the vehicle had been warmed up driveline wise before hand and its a forgiving ( easy rolling drive leg for example ) and call that their fuel mileage which can give a false perception of reality. I was not heavily loaded at all but never the less the flip bak cover, rubber bed mat, various tools etc and extra jerry cans of fuel all way up to a few hundred pounds of dead weight so its not an empty truck. The cold inflation tire pressures are set more near the freezing point so once they are warmed up driving I was showing 45 front and over 40 rear and realize high inflation pressures would help a little in fuel mileage but certainly not the ride on our crap sections of highway. The weather was good so was not raining as that can really drag mileage down, in fact I had a bit of a tail wind on average driving home. Most people on here would never have driven on that freeway to visualize it but its got a fair bit of rolling type of landscape with numerous river valleys. For the most part I had it on cruise set to 62 although kicking it off if I caught it in time before it started down shifting and self braking going down the grades. Most of the more substantial grades its shifting into 7th I believe as 8th just doesn't have it. Total distance round trip was 643 miles and my overall average and I did refuel three times in all, figured out to 17.65 miles per US gallon. My best fuel mileage section refuel within all of this figured out to 18.46 and these are all hand calculated figures. I find if anything that the trucks computer can be over optimistic, sometimes its pretty close but other times its stretching it. On paper persay in theory the truck would have just about made it on fumes for that whole drive without refueling once.    Which made me think of the topic thread of the wonder if these trucks could do 20 mpg and that is a good question, certainly would have to be on an easy going flat highway, no head wind, the right temperature, not packing around a bunch of dead weight and puttering along even slower than I was I would suspect and going steady and not stopping to smell the flowers or take a piss !. It probably is possible but not without effort to attain that with the wind resistance and weight of these trucks. Of course on my drive most people are passing me if they have the power as per loaded highway tractors, never mind a lot of speedy vehicles but the speed limit is 68 and most are at or well over that. 
    • 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?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...