Jump to content

Tailgate sometimes takes 2-3 tries to open

megatron51
 Share

Recommended Posts

megatron51 New Member

megatron51

Posted
Posted

2019 Silverado TrailBoss LT with power tailgate. Roughly half the time I go to open my tailgate it doesn't open on the first try. I'll push the button on the tailgate itself, the button on the dash, or the button on the remote, and it clicks like it's trying to open, but it doesn't move. Very annoying! Anyone else having this issue and/or know what the problem is?

Frank20LT Enthusiast

Frank20LT

Posted
Posted

If i'm parked slightly downward the tailgate will pop open but not automatically drop. Have to be parked on a level surface or uphill for it to drop.

Btown Enthusiast

Btown

Posted
Posted

Mine too! Sometimes takes 5 pushes to release the lock and I am pulling on the tailgate. One of these times I fear it won’t open at all.  I drove a new one a few weeks ago and it opened after one push of the button. 

Dunn Senior Enthusiast

Dunn

Posted
Posted (edited)

my 2019 RST needed 2 very rarely 1.......thought 2 was just the standard

 

2020 2500 is 1 time  every time so far......

 

with more electronics and computers this is the future ( maybe has been for awhile)

 

god help those who buy these things outside 5 yrs and no warranty.......just too many things to go haywire

 

kept my last truck for 15 yrs but this one probably only 5 yrs max and onto a base model as my last truck....will be really old by than, lol...(no issues so far)

 

it does have a click in tailgate if i try to use key fob to raise tailgate like LTZ and HC have.....like feature is already there but just has a lock on it........try it yours and youll hear it

Edited by Dunn
Dersch Enthusiast

Dersch

Posted
Posted

Mine does this too. From the day i picked it up ive always had to double click the button for it to work (not sure if that's normal but one click doesnt drop it) but probably 75% of the time i have to do a 2nd double click to drop it. 

 

Ive not had an issue with the remote or button in cab dropping it though 

batman900 Enthusiast

batman900

Posted
Posted

Bout half the time it takes more than 1 try to open it. Did it on my 19 and this 20 and I park in a way that gravity is in my favor.

grrr027 Enthusiast

grrr027

Posted
Posted

I've had this issue a bit too and like some of the others... have noticed it will happen with only a slight decline in wherever I am parked. My driveway is sloped upward toward the house and I prefer to back in, which makes it a royal pain in the ass, actually. @megatron51 does this happen to you also when you're parked uphill? If so, there could definitely be something else at play.

megatron51 New Member

megatron51

Posted
  • Author
Posted (edited)

I haven't noticed it happening more often in any specific conditions. I'm bringing it into the dealer to have it looked at next week so I'll post about what they end up finding. The good news is they're covering it under the 36k warranty.

Edited by megatron51
Gangly Senior Enthusiast

Gangly

Posted
Posted

I had the same issue when parked on a decline.  However, I noticed it getting worse to the point where sometimes it wouldn't open properly on level ground either.  While washing the truck one afternoon, I opened the tail gate and thoroughly cleaned the hinge roller at the bottom of the tail gate and I have had zero issues since.  It has worked flawlessly since, regardless of incline or decline.

 

If you get the chance and can remove the tailgate, do so and rinse off the roller hinge.  If you are not able to, then simply rinse the hinge roller down as best you can while on the truck and see if that helps.  

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

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