Instrument cluster & Infotainment (12.3") on the fritz....again.

Cokes

Tremor Buff
Joined
Nov 23, 2021
Messages
45
Reaction Points
35
Location
Lino Lakes, Minnesota
Current Ride
2022 F-250 Lariat 6.7
Once again I will need to bring the truck into the dealership for this issue. Both screens do not turn on when started and when the truck tries to reboot it will again say "blind spot monitor fault" and immediately after "cross traffic alert fault" then gauges shutdown. This time around it's throwing more and different faults like "monitor tire pressure" , "transmission not in park" and a few others. It has to be something with the ECU or one of the other "brains" of the truck but I guess my question to all of the knowledgeable guys on this forum is, is this more than just a software malfunction? The last time this happened they reprogramed the truck and updated the TRM (trailer module) and it fixed it...until now. That fix was done back in March. Should I be asking the dealer to replace anything or just keep having them update whatever module needs to be updated?

Also has anyone else experienced this?

It's been frustrating not being able to see the instrument cluster and the fairly constant dinging from it rebooting and the erroneous faults. They can't get me in until 11/28 but I will update this post when I find out more.

Thanks in advance.
 
Have dealer check for rodent chewn wiring. And, inspect the connectors near spare tire area for corrosion and repack with di-electric grease.
 
Thanks for the reply. I will mention that to them and will try to inspect any wiring and connections I can see. The truck typically sits in a garage each night, but I have been on a few hunting and camping trips where it sits for a few days at a time in the woods or campground where it's possible for a critter to chew on something.
 
Have dealer check for rodent chewn wiring. And, inspect the connectors near spare tire area for corrosion and repack with di-electric grease.
Also the infamous fuse panel water leak and front passenger water intrusion. Both should be low probability on a 22 but are areas to inspect.
 
Many times, "software" is the common blame when things go haywire in a computer driven instrument. (Your truck) Software is a code and does not go intermittent, rather in many cases, the computer is a "learning" computer which generally periodically scans and can make adjustments based on the algorithm it uses to analyze any variables. (Driving conditions, etc.) If one of the MUX points (multiplexor point of test) has a fault, the computer can learn incorrectly. The next scan can then see an unacceptable change and throws a fault, or it can render that condition as nonfunctional. The end result is intermittent behavior or failure. Flashing the computer is simply a refresh to start over at a known state. This can be setting a default loaded in ROM, (Read Only Memory) or possibly updating the firmware in a programmable ROM, either of which will not fix the condition that caused the problem in the first place. But since flashing "temporarily" fixes the issue, the fault is blamed on the software or firmware.

In high end equipment, many of the intermittent conditions are the result of the scanning hardware itself. Sometimes a parameter is tested too tight and is relaxed in a firmware "update" where the intermittent condition now has a larger variable window and prevents a failed condition. Intermittent connections, faulty relays, ("relays" can be hardware or electronic) and even cross conduction can throw errors. In the trucks case, cross conduction is very likely due to corrosion. (As @Modman pointed out) It's also very likely a connection is intermittent rendering the above result.

This isn't a direct answer to the question you have, but it does give some insight on why "software" is blamed for a hardware failure. Most likely, you have a hardware issue that is going to be difficult to find unless they have an electronic/mechanical person at the dealership that can relate the scanning algorithm with the possible MUX point. (The computer may/should hold those numbers) Whatever they jostled the last time it was fixed, is very likely where the issue lies. I have seen many intermittent computer-driven equipment fixed by replacing or flashing the processor only to find out, a board was not seated correctly in the slot.

As always, hope this helps.
 
This very much helps ME understand some of the fundamentals on which the truck operates and I appreciate the reply. Since I have some time before it goes to the dealership I may try to educate myself further with doing some checks of my own both visually and with a voltage meter. I do know some about electrical circuits, but if this were you, where would you start looking? Again thank you for your reply.

I will take a look tonight and see if I can't get a little lucky and find something out. :)
 
Honestly I'm surprised there isn't more guys that this has happened to which may point to the fact that maybe something was chewed or is loose or corroded and it's not a design or component issue.
 
Also the infamous fuse panel water leak and front passenger water intrusion. Both should be low probability on a 22 but are areas to inspect.
Agree on this, sounds like body control module water intrusion. BCM is located in passenger footwell and I was told water coming in from cowl/A pillar. I had this issue with '22 and dealer had to take dash out for water intrusion specialist to seal leak that was allegedly behind the air box. Of course I never got an opportunity to see it apart or where the leak was located.
 
Im betting either rodent damage, or a pin is bent in a connector during truck assembly.
 
This very much helps ME understand some of the fundamentals on which the truck operates and I appreciate the reply. Since I have some time before it goes to the dealership I may try to educate myself further with doing some checks of my own both visually and with a voltage meter. I do know some about electrical circuits, but if this were you, where would you start looking? Again thank you for your reply.

I will take a look tonight and see if I can't get a little lucky and find something out. :)
I would start looking for water intrusion. Not just the BCM but any point where the sensors are located, or the tie in point such as the indicators in the mirrors. Unfortunately, I don't know the hierarchy of the scan, but any faulty sensor can throw unusual codes. Though this is rare.

Scans are usually done through some kind of serial bus that can be thrown off by a faulty sensor. The fault can emanate from the BCM itself, faulty signals from the mirrors, the taillights, etc. If any of the sensors are damaged, it can result in a corrupt data which can throw "false" codes. In your particular case, the blind spot and cross traffic alert may come from a taillight fault. I'd check for cracks that may allow water in. And certainly, check for water in the fuse boxes, there are what seems like too many unrelated errors. The fact that your monitors are affected really screams CPU. (Central Processing Unit) I don't think there is an easy way to check this without pulling panels. Admittedly, I am not that familiar with the computers on these new trucks.

True story: When I first picked my 22 up last November, the salesman noted a cracked lens on the passenger side mirror clearance light. He told me that they already ordered the mirror and to go ahead and drive it home. I did, and there was no codes present, all seemed fine. A few days later, I was told the mirror was in and they could install it that day if I could bring it in in the morning, so I dropped it off. I work late, so I went in the evening before they closed to pick it up and started it up. I had several codes pop up, predominantly, the blind spot monitor code. Being unfamiliar with the new truck, I showed the salesman, he said bring it back the next morning. I did, they took the truck in the garage for about 10 minutes and re-programmed the truck to fix the codes. I have not had an issue since, 1 year later.

Moral of the story, the new mirror and sensor caused a fault to be thrown. Apparently, no one considered a new mirror should cause such a failure and most likely didn't see the problem, or the truck threw the code after the fact. I still don't know why; I keep this in the back of my mind all the time. I imagine water in it could also cause similar issues. I do know that the tie-in to the blind spot monitor is the communication of the taillights radar to the mirror's indicator. So, I keep an eye on it.

I wish you luck with your dealer, I hope they can find the core problem.
 
Thanks for all the responses. I visually inspected any wiring and connections that I could see without manipulating things to much. I did not disconnect any of the wiring connections, but I did try disconnecting both batteries for 15mins to see if a hard reset may help the issue but it did not. It's going down to the dealer today to wait for them to diagnose it. Guy at the dealership looked at it remotely and said there are so many different codes that he's having a "specialist" come out and look at it. I don't know if that's true or not and he's feeding me something since they can't get to it until the 28th but in any case I hope they figure it out sooner than later.

Until then I will wait and see what they come up with.
 
Update: I had the truck into the dealership today and the tech said all issues and warnings point to the trailer brake module. They are getting one on order and will be able to install next week sometime. They were very understanding and straight forward and said if it takes multiple days they have a loaner truck ready for me to use.

They reset everything and no faults or warnings (as of now) but I assume will come back without replacement. Once replaced I would imagine this issue would be fixed permanently, oh so I hope.

Thanks for listening. :)
 
Here's to hoping it's just the trailer brake module. I had my '20 in to the dealer a few times for the Blind Spot issues, there appeared to be some frayed wires under the dash; my truck was built during COVID so something might not have gotten zip tied out of the way. Since they found the problem no further issues.
 
Fucking canbus strikes again...

It seems all good to have every module communicate through every other module until you have 1 module, not associated with what "seems" broken, cause issues to wonder if it's really a great idea.
 

Latest Discussions

Back
Top