Asbuilt change

Hi,

I have changed a line in BCM asbuilt with Forscan and Vlinker FS adapter and after writing it I got some errors. Some cleared but the ones in ABS remained. I restored the Asbuilt from backup but the errors remained the same.

Errors are:

===ABS DTC U2101:00-2F===

Code: U2101 - Control Module Configuration Incompatible

===ABS DTC U2100:00-2F===

Code: U2100 - Initial Configuration Not Complete

===ABS DTC P05D3:86-2F===

Code: P05D3 - Driver Mode Select Switch ‘A’ Range/Performance

Additional Fault Symptom (:86):

- Signal Invalid

===IPMA DTC U0418:86-AF===

Code: U0418 - Invalid Data Received From Brake System Control Module ‘A’

Can someone please help on what to do next?

You will need to run a PCM module calibration now to get rid of those errors.

Thanks for the reply

Can you please explain a little more how to do it exactly?

Curious, what did you change?

I changed in the BCM the 726-04-01 line, to what I believed it’s the battery type.

Of course I made backup before this and reverted back.

Everything is fine except ABS, it’s like it is security locked or something like this.

Unfortunately I don’t know what to do anymore so most probably I will have to go to the dealership to see if they can fix it

If you have your OEM asbuilt you could try rewriting the ABS asbuilt and resetting the module.

I tried with factory asbuilt file from Ford, the one you download with tour VIN, but the outcome was the same.

I tried writing the ABS module, without changing nothing but it couldn’t perform it. One block was written, the others 5 or 6 can’t remember now it couldn’t rewrite them and said writing failed.

Tried module reset for BCM, ABS, GWM, IPMA but same errors, nothing changed.

It’s like the ABS module is security locked or Forscan doesn’t have enough privilege

I have found on a forum that Forscan can no longer write in the ABS module. Not sure if it’s correct.

I asked AI and this came back

Ford has implemented a “Fire Diagnostic” security system on models after 2021, blocking forscan from writing to ABS modules and other safety systems [1]. Only the official Ford tester, FDRS, can obtain the necessary digital certificate in real time, making dealership the only solution for reprogramming modules through the PMI procedure [1].

This is a thing. There are modules that can only be written to so many times before they lock up and need to be replaced.

P05D3 often appears when drive mode / terrain mode configuration no longer matches what ABS
Check if you changed a line tied to Drive Modes

Your P05D3 is the clue.

If you enabled or disabled:

  • Sport mode

  • Drive mode select

  • Terrain management

  • GOAT modes

  • Tow/haul

  • Off-road screens

…without enabling the matching ABS/IPC/APIM configuration, ABS will reject it.

This is especially true on:

  • Ranger

  • Maverick

  • Bronco

  • Escape

  • Explorer

  • F150

If you remember the exact BCM line you edited, I can probably tell you which companion modules also need matching changes.

I have changed in BCM 726-04-01 but changed it back after

Restored everything from backup, but still didn’t fixed it

I can’t see how changing the battery type did this to the ABS. For years people have changed the batteries in Ford vehicles without incident. This is likely due to either an asbuilt corruption when written or an existing issue.

Check this setting in the BCM:
726-68-01 **xx xxxx xx--
ABS_Available_Cfg: 00=Absent 01=Present

I don’t have that line in BCM

Last one is 726-28-01

Some time ago I was curious why battery disconnects have broken my AutoHighBeam. Couldn’t think of anything else that would do it.
A week or two later I found a clue leading to SCCM, and I remembered I did change one bit in SCCM some time in the past. Seemed harmless. It was not.
I am writing this to show grounds to say: it’s not likely the BCM battery change caused the ABS errors you have.
These errors are exactly what I got when I tried to make my ABS accept switching mode changes from SCCM (which got a switch pack from Puma ST).
Check ABS’s 760-04-01, or even go to the Forscan’s Easy Mode. you should have the SDM (Selectable Drive Modes) source set to HVAC, and type to Push Button. This is reflected by “0102” at the start of 760-04-01.

I had a look yesterday in the ABS and to my amazement or horror to say all hex inside is with 0000

Don’t know why or how this was possible as I never touched it

And this is from Ford site

I put everything back, manually :grimacing: and everything is fine now

Maybe this helps someone

Still, I don’t know why this happened

Did you have to replace the battery lately?

No, but the resting voltage on it is pretty low

After a day or two it sits around 12.2V sometimes 12.1V

If you use the FordPass app, have you ever received the “Remote functions disabled to save battery” message in less than 14 days of the vehicle not being used?

12V is fine, should not be an issue. If the battery is falling off to say 11.6V then you might start seeing issues like Sync asking about nav permissions each time you start the vehicle. This is a symptom of the battery getting weak.

I receive it after 3 or 4 days or if I want to inflate a bicycle tyre, then I get it instantly

This is why I got in this mess. I wanted to modify battery capacity in the easy menu, but there is only undefined, 54Ah or 60Ah EFB or AGM type, however the battery for Ecoblue 2.0 is 70Ah. So I tried as-built. That went well :man_facepalming:

Now the strange thing is that if you put 60Ah in the live monitoring appears as 35Ah, the 54Ah appears as 70Ah and undefined appears as 60Ah.

This is with 60Ah EFB from the easy menu