Got mine back yesterday - out of service from January 10 - February 4. Replaced modules 5 and 6, the BECM, and, I think, the HVBJB. Also replaced the LVB as that was dead but wasn't really the cause of the problem. It was the first such repair dealer had ever done, which I think goes to notion...
In this process now. 21 SR AWD. They just got the battery array and are starting balance process. Also replaced LVB and BECM. How long did it take for dealer to get car back to you? After you got it back, what did you need to do to recalibrate BMS?
That being said, would the DTC on either module indicate HVBJB problem? Dealer believes (and I guess Ford persuaded as they approved the warranty claim) problem is faulty battery cell, so new battery array on order, waiting for delivery. But I do see reports that even SR batteries of 2021...
Thanks Mike, really appreciate it. Sounds, then, hopeful that replacing the LVB, the BECM, and the battery array with the faulty cell should have things working right again...
Thanks so much Mike! The BECM has been replaced however dealer is waiting for the battery array to be delivered; battery currently dropped out of vehicle. Charging was at home - level 2 (24 amps). Had charged overnight to 90%; I got a charge fault in the morning after using app to charge to...
Just an update, Ford authorized dealer to replace battery array, ordered new battery array service kit. If anyone is able to run the VIN for DTC alerts, I'd be grateful! Seems like proximate cause had something to do with charging at fairly cold temperatures (teens), to which it should have been...
Can I get some help with 3FMTK3SS6MMA06567?
It was towed to the dealer for a SSN warning (with total loss of power) Replaced the LVB, dropped the battery and replaced the BECM (said showed burn marks), now got text from service rep they are running tests, they think they know what damaged the...
Hey forum members -
Grateful for any help diagnosing 21 MME4 Premium VIN - 3FMTK3SS6MMA06567 . Seems like HVBJB, charged overnight outside in cold, got in this morning and got warning lights as below, car would not shift into drive.
I'm experiencing much the same; 21 MME4 Premium - no mechanical problems until today. Car parked outside last night - temps in teens - charged to 90%. Was headed on a longish trip (Baltimore to IAD and back) and so started at 6 am to charge to 100%, got charge fault. Went out to car - doors...
If PaaK works on lightning even after the security patch, is it software or is it the hardware in the Mach E? I'd kinda think the Ford PaaK software is basically the same, but the transmitters might be different. And if it is a hardware problem, I'd imagine there isn't really a fix for it.
For those in the thread with IT knowhow, is the fix more likely to come from Samsung as an update to the security patch to fix what they broke or from Ford as an update to PaaK software to update compatibility to Samsung's new protocol?
You can also reboot the phone while you're setting backup code up. Just needs to be working while code is authorizing. That said, if you're on the forum looking for a solution BEFORE you've deleted PaaK, that will certainly be easier than trying to add it back while the security patch is...
On phone reboot PaaK will connect but only for about 30 seconds. After that PaaK disconnects. Car and phone then stuck at handshake-PaaK shows "connecting " but won't connect.
I set up backup code during brief window that phone was connected after reboot.
This is on a couple of threads. I don't think it matters what carrier but it does seem limited to the latest security update on Samsung S24 series phones, maybe other current Samsung phone models. Not all Android, not even older Samsung (although those may not be getting the most recent security...
Yes, there seems to be a global problem where the (at least) most recent security update pushed in the last week to Verizon Samsung S24 series phones is interfering with PaaK connection to the vehicle.