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

2016 Code Tantrum - What Happened?

Thread Tools
 
Search this Thread
 
Old Jul 28, 2022 | 01:06 PM
  #1  
mountaintruck's Avatar
Thread Starter
Senior Member
5 Year Member
Liked
 
Joined: Jan 2017
Posts: 152
Likes: 57
Default 2016 Code Tantrum - What Happened?

2016 XLT, Supercrew, 5.0
Weather was hot: 35C / 95F

So my truck had a fit the other day resulting in multiple codes being triggered. It may be as simple as over heating, but some strange things happened.

Heres what happened: Truck was parked and idling with AC on for less than 5 minutes. No warnings or signs of issues. Turned the truck off and opened the door and the stereo remained on and would not turn off when pushing the power button. Restarted the truck and the entire gauge cluster had no power, but truck was running. No cluster lights, no rpm reading, no temp reading etc.. At this point, feeling frustrated, I walked away for a few minutes to think about next steps.

Returned 10 minutes later, stereo sill on and when starting the truck the same issue with no power to the gauges was happening. Turned the truck off, disconnected the negative power cable for 1 minute, reconnected and everything was back to normal, with the exception of the check engine light was now on. Engine and tranny temps looked normal. Drove 10 minutes to my destination and turned off the truck for the night.

Next morning the check engine light was off. I connected my phone and pulled the multiple error codes listed below. I understand what the codes are, but I have no clue why it happened. One of the codes says "engine overheating condition" yet no warnings were displayed and the temp gauge looked normal.

Truck has operated normally since.

Thoughts??





?
Reply
Old Jul 28, 2022 | 01:17 PM
  #2  
52merc's Avatar
5 Year Member
5 Year Member
Community Builder
Liked
Loved
 
Joined: Nov 2018
Posts: 6,727
Likes: 3,947
From: Calgary, Alberta
Default

Load test your battery. If it tests good then put a smart charger on it and make sure it is fully charged. Multiple communication DTCs (the "U" codes) on start-up is often caused by battery voltage dropping too low during the engine crank cycle. Low voltage causes some electronic modules to not boot up fast enough. The error messages are the result of these slow booting modules not sending out the appropriate messages on the CAN buses as expected.

High temperatures effect the output of the alternator and the ability of the battery to accept a charge.

Last edited by 52merc; Jul 28, 2022 at 01:20 PM.
Reply
Old Jul 29, 2022 | 10:25 AM
  #3  
mountaintruck's Avatar
Thread Starter
Senior Member
5 Year Member
Liked
 
Joined: Jan 2017
Posts: 152
Likes: 57
Default

Thank you for the quick and detailed response. I checked the battery yesterday morning before starting and it was 11.7v, so looks like the battery is on the way out.

Originally Posted by 52merc
Load test your battery. If it tests good then put a smart charger on it and make sure it is fully charged. Multiple communication DTCs (the "U" codes) on start-up is often caused by battery voltage dropping too low during the engine crank cycle. Low voltage causes some electronic modules to not boot up fast enough. The error messages are the result of these slow booting modules not sending out the appropriate messages on the CAN buses as expected.

High temperatures effect the output of the alternator and the ability of the battery to accept a charge.
Reply




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