OTA Software Update 10.3.0 - Powertrain, Battery, Parking Brake

[GDN]

I haven’t really had any issues with my truck except for occasional, random parking brake deployments. Maybe this will fix that if I ever get this update.

Are you sure those parking brake deployments are random? If the truck is on a slope it will set it automatically. Time is not my friend and I get more forgetful every day, but I believe it was the '24's that the SW was updated to set the parking brake every time you put the truck in park. The brake will automatically release many times too, more in Drive vs Reverse.

Sponsored

 

[richguy82]

Are you sure those parking brake deployments are random? If the truck is on a slope it will set it automatically. Time is not my friend and I get more forgetful every day, but I believe it was the '24's that the SW was updated to set the parking brake every time you put the truck in park. The brake will automatically release many times too, more in Drive vs Reverse.

It’s random in my case because it happens maybe 1 out of 10 times I park in my slightly sloped driveway. It doesn’t automatically disengage either. It will still be engaged when I try to depart the next day.

 

[P-38]

My '24 only auto deploys parking brake on slopes. At least as far as indicator lights go and causing a jerk if not manually released. If it auto does it anytime I'm in Park I cannot tell.

 

[Jim Lewis]

Another weird thing in FordPass post PowerTrain update. Not only will the truck charge at higher rate, but I can drive forever according to the guessometer!

 

[Jim Lewis]

So, I deleted my vehicle from FordPass, deleted FordPass from my iPhone, shut down iPhone, rebooted, installed a fresh copy of FordPass, and set up PAAK again. Started charging my truck and ignored the update instructions to first set up my charging location, target charge limit, and preferred charging times via the truck's SYNC screen. I found that after ~10 minutes of charging, I could set all that up in FordPass. When I checked the truck SYNC screen, the information had carried over to the truck.

When I tried to set the charging location via FordPass, it offered me my exact street home address. It looked liked it was culling that info from the address provided when I first set up the FCSP via the Ford Charge Station Pro setup app, quite a contrast to setting up a charge location via the truck SYNC screen where the truck might have used faulty GPS data and had picked my next-door neighbor's house as my charging location!

I did "edit" the settings transferred to the truck, confirmed that they were all as I had entered them on my iPhone, and then "saved them" (again) in the truck. So, unlike the first go-round following Ford's instructions exactly, I now have my home charging location, (preferred) target charge limit, and preferred charging times both in the truck and in iOS Ford Pass 5.21.0.

 

[Ekiehn]

Ugh... so I had the 10.3.0 update pip up on Saturday with the note with low battery (LVB) was low postponed, will try again at scheduled time... My LVB reported via Carscanner was 80%. Should have been fine. Went ahead and drove around to 82% tried again, no luck... Trickle charged to full, rest BMS tried agin same message. Let it try automatically, failed. Pulled negative for 10 minutes.. Reset BMS, carscanner reports 89% LVB with everything off, tried again still reporting low SOC % on LVB update postponed.. I'm out of ideas, as all ive do e has usually worked in the past to get an update to work... Any additional suggestions?

 

[tearitupsports]

Ugh... so I had the 10.3.0 update pip up on Saturday with the note with low battery (LVB) was low postponed, will try again at scheduled time... My LVB reported via Carscanner was 80%. Should have been fine. Went ahead and drove around to 82% tried again, no luck... Trickle charged to full, rest BMS tried agin same message. Let it try automatically, failed. Pulled negative for 10 minutes.. Reset BMS, carscanner reports 89% LVB with everything off, tried again still reporting low SOC % on LVB update postponed.. I'm out of ideas, as all ive do e has usually worked in the past to get an update to work... Any additional suggestions?

I would turn the truck on for like 6 hours to let it charge the LVB battery. I assume you got the sensor recall done already long ago? The truck only charges the LVB when it is on, or is actively charging the HVB.
i had good success on the past just leaving it on for hours and hours with the climate and lights turned off.
Your LVB has to be above 92% for an update.

 

[Ekiehn]

I would turn the truck on for like 6 hours to let it charge the LVB battery. I assume you got the sensor recall done already long ago? The truck only charges the LVB when it is on, or is actively charging the HVB.
i had good success on the past just leaving it on for hours and hours with the climate and lights turned off.
Your LVB has to be above 92% for an update.

Interesting... In all the years of dealinf with updates i've never had to be above 90% SOC on the LVB for updates to work.. 92% seems almost unobtainable unless you have a brand new battery and mine is just about four months old.. but given all the old tricks haven't worked i'll see if I can get it up over 90% and report back..

 

[Maxx]

Anyone getting this? Really looking forward to my 500A charging, someday…

I have not had this update in my 23 Pro yet.

 

[Jim Lewis]

For any of you who are "Whole Home Backup"/Home Integration System owners, one thing to check after receiving the 10.3 Powertrain update is whether it messes up the Bluetooth pairing of your truck with your FCSP. I didn't check that. We had a power outage today, and initially, I couldn't get the HIS backup started because I'd lost the BT pairing between my truck and FCSP.

The last time I bothered to test backup power transfer was on March 19, 2025. It worked fine for me using the charging port UNLOCK button trick (push UNLOCK, remove charger head, wait 10 to 15 secs, reinsert charger head).

Since then, I've had the BC 1.4 update (3/24), the Window Performance update (DDM-25.12.0, 4/19), and the Powertrain update (10.3.0, 6/13). I didn't bother checking pairing settings after any of those.

The UNLOCK button trick wouldn't work for me today (failed 2x in a row). I got in the truck to try to start a manual power transfer and noticed, "Oops! No paired FCSP anymore!"

No evidence, but since the 10.3 update trashed charging locations, target charge limits, and preferred charging times, it seems likely to me that it also trashed BT pairing to the FCSP.

I found that the FCSP was still broadcasting its SSID during the outage, perhaps powered by the HIS Dark Start battery. I could connect to it using the Ford Charge Station Pro setup app, initiate pairing on the truck SYNC screen, easily get the BT pairing code displayed back on my iPhone, and confirm the pairing code at both locations, all during the outage. Pairing worked faster than ever before (and did 2x in a row, as I messed up my first try).

So, if you get the 10.3 Powertrain update and have a Ford Home Integration System, you might want to check whether your truck and FCSP are still BT-paired and not wait to discover they aren't, like I did, during a real power outage. Here's hoping that the 10.3.0 Powertrain update offered some as yet unrevealed HIS enhancements, like the seemingly improved BT pairing I observed between my truck and FCSP.

 

[Ekiehn]

Well update on my 10.3.0 low LVB Soc issue. I did everything under the sun yesterday to try and get my LVB up over 86%. Used charger, drove around on a day trips for hours, let it sit running in the driveway for hours, charged the HVB back up to 80 % AND had a charger on the LVB at 10A till I gave up at 9:30 last night still stuck at 86%... of course the update failed at 1am for low Soc on the LVB. Drive to work this morning (3.5 miles) and LVB Soc immediatly starts climbing. By the time I'm at the office it hits 88%. I figure okay ill give it a shot to update again, just as I hit update Soc hits 89%. Update successfully executed! So the magic Soc number appears to be around 88 or 88... when finished LVB Soc was at 75% so it did suck down some juice... now I am happily (i think) on 10.3.0

 

[Ekiehn]

For any of you who are "Whole Home Backup"/Home Integration System owners, one thing to check after receiving the 10.3 Powertrain update is whether it messes up the Bluetooth pairing of your truck with your FCSP. I didn't check that. We had a power outage today, and initially, I couldn't get the HIS backup started because I'd lost the BT pairing between my truck and FCSP.

The last time I bothered to test backup power transfer was on March 19, 2025. It worked fine for me using the charging port UNLOCK button trick (push UNLOCK, remove charger head, wait 10 to 15 secs, reinsert charger head).

Since then, I've had the BC 1.4 update (3/24), the Window Performance update (DDM-25.12.0, 4/19), and the Powertrain update (10.3.0, 6/13). I didn't bother checking pairing settings after any of those.

The UNLOCK button trick wouldn't work for me today (failed 2x in a row). I got in the truck to try to start a manual power transfer and noticed, "Oops! No paired FCSP anymore!"

No evidence, but since the 10.3 update trashed charging locations, target charge limits, and preferred charging times, it seems likely to me that it also trashed BT pairing to the FCSP.

I found that the FCSP was still broadcasting its SSID during the outage, perhaps powered by the HIS Dark Start battery. I could connect to it using the Ford Charge Station Pro setup app, initiate pairing on the truck SYNC screen, easily get the BT pairing code displayed back on my iPhone, and confirm the pairing code at both locations, all during the outage. Pairing worked faster than ever before (and did 2x in a row, as I messed up my first try).

So, if you get the 10.3 Powertrain update and have a Ford Home Integration System, you might want to check whether your truck and FCSP are still BT-paired and not wait to discover they aren't, like I did, during a real power outage. Here's hoping that the 10.3.0 Powertrain update offered some as yet unrevealed HIS enhancements, like the seemingly improved BT pairing I observed between my truck and FCSP.

Good to know, my HIS has been inoperable due to Bluetooth issues for so long that I had pretty much given up... Now that I have 10.3.0 ill give ti a try and maybe (fingers crossed) I will actually be able to use the system.. given we are in hurricane season down here in SoFla it would be nice to have operational.

 

[Jim Lewis]

Some evidence that the 10.3.0 Powertrain update revamped the truck-FCSP BT pairing scheme: the name of the paired FCSP is different now in my new pairing. The wording and design of the Intelligent Backup Power SYNC screen is different, too (although I may have capture the screen in different states in the two pictures, without paying attention....).

Ford Charge Station Pro1 in new pairing

Ford3000 in old pairing

 

[tearitupsports]

Some evidence that the 10.3.0 Powertrain update revamped the truck-FCSP BT pairing scheme: the name of the paired FCSP is different now in my new pairing. The wording and design of the Intelligent Backup Power SYNC screen is different, too (although I may have capture the screen in different states in the two pictures, without paying attention....).

Ford Charge Station Pro1 in new pairing

Ford3000 in old pairing

The Bluetooth change is from a firmware update of the FCSP a couple months ago, not the 10.3 software. I did not have to redo mine in 10.3 but mine was already set to FordChargeStaionPro1 from when I reset it back in March/April.

That being said I think there is something in this update related to HIS. It can’t be coincidence that this weeks reports of getting this all have the HIS.

 

[Jim Lewis]

That being said I think there is something in this update related to HIS. It can’t be coincidence that this weeks reports of getting this all have the HIS.

After I repaired the truck/FCSP BT connection, I was surprised that manually initiated backup power transfer worked straightaway for me during our outage yesterday. IIRC, it usually hasn't for me in the past.

Sponsored