Jump to content

Recommended Posts

Posted
4 hours ago, Cmen303 said:

Greetings all,

 

I have a 2016 high country with the same issue.  I've replaced both motors and both switches with no difference.  I'm in about 1200-1300 now.  unable to find anyone with a solution.  I've gone to a Chevy dealership and was told they couldn't help me with motor replacement and to just get rid of these steps.   If anyone has any info I'm all ears. 

Did you make sure you have voltage at the running boards? Check fuses if not, of course. If you have power at the boards, I'd say check the sensors next, and make sure the hinges aren't seized. I've seen that on a '14 Escalade. I'd lube the hell out of them with some PB Blaster. Then open the door and apply manual pressure down or up, whatever way they need to go, to see if you can get them to move.

Posted

Hey mtbadbob,

 

So I've also changed out the fuse, I've sprayed the PB blaster like crazy on all the joints. They do have voltage because they move a bit. like the want to come out.   My next step I thing is to take them down and take them apart, lube them up real good and see how that goes. I'm out of ideas. 

 

Posted

I think that may help. The sensor could be telling them to retract because of an obstruction also, especially if they're trying to move. The could just be full of crap inside. Did you try pushing down on them manually when you open the door??

Posted

My comment won't really be helpful in the sense of repairing power boards but last fall when I ordered my truck and was going through the list of things I wanted as well as making sure certain items were not mistakenly put on the order, the topic of power running boards came up. The salesman's comment when I said I do not want them, just the standard ones that come with this trim of a truck and he said good because they do not work up here in the winter with all the salt that flies around and gets into the motors and ends their life in fairly short order. Of course some people get them as some people want them and not all sales people are going to tell the customer its a bad idea if the vehicle gets used during the winter. They are a fair weather on pavement product ... I've seen those that have gotten their power board to go down and left it unhooked or set in that position so it behaves like a normal bolt on board, also heard power boards making horrible crunchy noises because they drove on a little gravel.

Posted

Power boards do require more maintenence, mainly keeping the hinge mechanism's cleared. I live in Montana, and have had relatively good luck with mine, once the program got updated. That being said, they will be more tempermental & require more attention in snowy/icey areas. 

  • Like 1
Posted
23 minutes ago, mtbadbob said:

Power boards do require more maintenence, mainly keeping the hinge mechanism's cleared. I live in Montana, and have had relatively good luck with mine, once the program got updated. That being said, they will be more tempermental & require more attention in snowy/icey areas. 

There would be various factors that would come into play with how good or bad the power board experience would be depending on your typical winter roads, how much crap they spread and what they are spreading on your winter roads, how much snow/ice builds up on them and if the vehicle is being kept outside or goes into a heated space to melt out the ice. I can pretty much guarantee a lot of vehicle owners that have power boards don't maintain anything to do with them, just go to a shop when they quit moving and then get the bad news as to how much it will cost to fix ! LOL

  • Like 1
  • 1 month later...
Posted
On 4/17/2025 at 9:23 PM, Cmen303 said:

Hey mtbadbob,

 

So I've also changed out the fuse, I've sprayed the PB blaster like crazy on all the joints. They do have voltage because they move a bit. like the want to come out.   My next step I thing is to take them down and take them apart, lube them up real good and see how that goes. I'm out of ideas. 

 

My understanding is there is a stainless bushing at the pivot points on the boards.  If they start sticking or running slow, disassembling the arms at that point and cleaning / lube with anti-seize is sometimes the cure.  If the joint is corroded beyond repair replacing the arm is the next step.  This is on the 15-18 design, not the newer trucks.  

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,759
    Total Members
    8,960
    Most Online
    DM22
    Newest Member
    DM22
    Joined
  • Who's Online   4 Members, 0 Anonymous, 1,691 Guests (See full list)


  • Latest Articles

  • Posts

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