Topic Sponsor
2015 - 2020 Ford F150 General discussion on the 13th generation Ford F150 truck.
Sponsored by:
Sponsored by: Worksport

Was off roading, had a weird dash error

Thread Tools
 
Search this Thread
 
Old Dec 16, 2019 | 09:39 PM
  #1  
KDH92's Avatar
Thread Starter
Member
 
Joined: Apr 2016
Posts: 41
Likes: 1
Default Was off roading, had a weird dash error

16 XLT, 5.0 4x4.

I was climbing a muddy hill in 4hi and going nowhere. Decided to give 4lo a shot to see if I could get unstuck. The truck indicated on the dash, "Hillside assist not available" and "Check advancetrac." I may have the wordings slightly off, but hopefully the point is the same. Anyways, the error appeared while in 4lo. I saw that error, and was confused, so I put it back in 4hi. I managed to get unstuck, and got back to the pavement switching back to 2wd. The yellow traction control indicator was stuck on the dash, and I noticed cruise control didn't work anymore. I parked the truck, turned it completely off, and restarted the engine. The light is gone, cruise works, and it shifts in and out of 4hi and 4lo just fine. What the heck was that all about? Anyone ever have an experience similar to this?
Reply
Old Dec 16, 2019 | 09:48 PM
  #2  
ronemca's Avatar
Senior Member
 
Joined: Feb 2019
Posts: 477
Likes: 66
Default

Possible loose ground up near the headlights. Semi-extreme body movement may have caused intermittent continuity disruption(s).
Reply
Old Dec 16, 2019 | 09:50 PM
  #3  
Wanna Ride's Avatar
Senior Member
 
Joined: Jun 2013
Posts: 1,703
Likes: 542
Default

Wouldn't be the first time a computer behaved erratic, and then was fine after a reboot.
Reply
Old Dec 16, 2019 | 11:58 PM
  #4  
caperJ's Avatar
Community Team
Veteran: Canadian Forces
15 Year Member
Liked
Top Answer: 1
 
Joined: Mar 2010
Posts: 4,917
Likes: 873
From: Winter Wonderland Alberta
Default

This just happened to me but in 4A. I read there are a number of things that could cause this behavior. 1 being unable to read an ABS sensor due to obstruction. I did the same shut off and on and its gone.
Reply
Old Dec 17, 2019 | 12:16 AM
  #5  
52merc's Avatar
5 Year Member
5 Year Member
Community Builder
Liked
Loved
 
Joined: Nov 2018
Posts: 6,714
Likes: 3,933
From: Calgary, Alberta
Default

Originally Posted by KDH92
16 XLT, 5.0 4x4.

I was climbing a muddy hill in 4hi and going nowhere. Decided to give 4lo a shot to see if I could get unstuck. The truck indicated on the dash, "Hillside assist not available" and "Check advancetrac." I may have the wordings slightly off, but hopefully the point is the same. Anyways, the error appeared while in 4lo. I saw that error, and was confused, so I put it back in 4hi. I managed to get unstuck, and got back to the pavement switching back to 2wd. The yellow traction control indicator was stuck on the dash, and I noticed cruise control didn't work anymore. I parked the truck, turned it completely off, and restarted the engine. The light is gone, cruise works, and it shifts in and out of 4hi and 4lo just fine. What the heck was that all about? Anyone ever have an experience similar to this?
Roll Stability Control, Electronic Stability Control, and Traction Control System are all disabled in 4L. Without these I don't think hill descent control works. It was just a regular message telling you that. Nothing wrong. Depending on the sequence of shifting from 4H to 4L on the hill you may have confused the traction control functions a little. It might not be anything more than that. Shutting the truck down and restarting probably cleared the error.
Reply
Old Dec 17, 2019 | 02:38 AM
  #6  
caperJ's Avatar
Community Team
Veteran: Canadian Forces
15 Year Member
Liked
Top Answer: 1
 
Joined: Mar 2010
Posts: 4,917
Likes: 873
From: Winter Wonderland Alberta
Default

He should not have received a warning indicator on the cluster when shifting to 4L. Done this many times no cluster error.
Reply
Old Dec 17, 2019 | 02:42 AM
  #7  
KDH92's Avatar
Thread Starter
Member
 
Joined: Apr 2016
Posts: 41
Likes: 1
Default

That makes the most sense. I'm not worried that there's a problem, it's acting just fine. But man that was weird.
Reply




All times are GMT -4. The time now is 01:25 PM.