2006 Mk7 Transit Replacement BCM PATS Error Code 23

[jww9999]

Hi All.

I've recently replaced the BCM on my 06-reg Mk7 Transit Jumbo T350EF (2.4L RWD 140ps GLX) as the old one was suspected to be faulty.
Managed to successfully re-code in the keys before programming the replacement BCM via Forscan, however I am now getting a PATS flashy code of 23 whenever I try to start the van with any of the keys.
Online research tells me that 23 means "ECU ID Mismatch" so does that mean my van requires a replacement ECU to programmed in? Or could it be something else?
I have tried re-programming the BCM and keys again from scratch but no improvement.

Error Codes obtained from Forscan after clearing all legacy ones are as follows:

PCM
U0426:00-2F Invalid Data Received From Vehicle Immobilizer Control Module
P2265:64-28 Water in Fuel Sensor 'A' Circuit Range/Performance
U0140:00-28 Lost Communication with Body Control Module

BCM
B1048 Brake Fluid Level Switch
B10DA PATS Target Identifier
U2101:00-0A Control Module Configuration Incompatible

RCM
U0155 Lost Communication with the Instrument Panel Cluster Control Module

Any help would be greatly appreciated thanks!

[tranmx2]

2011 changes were made to Mk7 Transits. Mine is a 2012 Mk7 which is supposedly different than a 2006 Transit.
Looking at your post with some knowledge of the 2012 system could be the wrong thing to do.

PATS flashy code of 23 - 23 means "ECU ID Mismatch

PCM
U0426:00-2F Invalid Data Received From Vehicle Immobilizer Control Module. The imobiliser is part of PATS. The PCM on the 2012 does the same as an ECU or EDC.
Water in fuel - drain fuel filter.
U0140:00-28 Lost Communication with Body Control Module. On the 2012 the modules are linked. Could be poor electrical contact.

BCM
B1048 Brake Fluid Level Switch. Easy enough to access and check.
B10DA PATS Target Identifier. Could be associated with the imobiliser - keys - key header.
U2101:00-0A Control Module Configuration Incompatible. Have the same code on the 2012 which does not seem to affect the running of the vehicle. Could be poor electrical contact.

RCM
U0155 Lost Communication with the Instrument Panel Cluster Control Module. Could be poor electrical contact. There are two U - DTCs = communication - could be both in one connector. There can be corrosion and bent pins in connectors.

A low V front battery is often referred to as being the source of DTCs/problems.
Sometimes it is reported that solving problems like water in fuel and brake fluid level removes other DTCs.

When using Forscan a battery maintainer is recommended.

Would have thought it better to programm the BCM then do the keys.
Did you make a backup of the old BCM with Forscan or did you use the backup available from Motorcraft?

[Frag]

You need to initialize the new bcm,I don’t know if this can be done using forscan.
In ids it’s in the same menu as the other security and key options as initialize modules or module reset.
This will match the pcm,bcm and keys.

[jww9999]

2011 changes were made to Mk7 Transits. Mine is a 2012 Mk7 which is supposedly different than a 2006 Transit.
Looking at your post with some knowledge of the 2012 system could be the wrong thing to do.

PATS flashy code of 23 - 23 means "ECU ID Mismatch

PCM
U0426:00-2F Invalid Data Received From Vehicle Immobilizer Control Module. The imobiliser is part of PATS. The PCM on the 2012 does the same as an ECU or EDC.
Water in fuel - drain fuel filter.
U0140:00-28 Lost Communication with Body Control Module. On the 2012 the modules are linked. Could be poor electrical contact.

BCM
B1048 Brake Fluid Level Switch. Easy enough to access and check.
B10DA PATS Target Identifier. Could be associated with the imobiliser - keys - key header.
U2101:00-0A Control Module Configuration Incompatible. Have the same code on the 2012 which does not seem to affect the running of the vehicle. Could be poor electrical contact.

RCM
U0155 Lost Communication with the Instrument Panel Cluster Control Module. Could be poor electrical contact. There are two U - DTCs = communication - could be both in one connector. There can be corrosion and bent pins in connectors.

A low V front battery is often referred to as being the source of DTCs/problems.
Sometimes it is reported that solving problems like water in fuel and brake fluid level removes other DTCs.

When using Forscan a battery maintainer is recommended.

Would have thought it better to programm the BCM then do the keys.
Did you make a backup of the old BCM with Forscan or did you use the backup available from Motorcraft?

Thanks for this I will check connectors etc. - would they just be the ones going into and out of the BCM or are there any others I should be aware of as well?

Re the batteries they're both brand new Yuasa's with good Voltage and were installed only a few days ago.
I've not heard of using a battery maintainer while using Forscan however I do have a portable battery charger.
Re the water in fuel filter DTC this code was there before the van stopped running and I managed to drive the van from Sheffield/Worksop (where I bought it) all the way to Reading with no issues.
As for BCM and then keys Forscan mandates that you must code in two keys before doing anything else (such as programming in the BCM) and I used a save file from the old BCM when programming in the replacement one.

[jww9999]

You need to initialize the new bcm,I don’t know if this can be done using forscan.
In ids it’s in the same menu as the other security and key options as initialize modules or module reset.
This will match the pcm,bcm and keys.

I'm not fully sure if this can be done through Forscan either.
I've cycled and searched through all the possible service procedures available to me on Forscan but with no luck.
I know someone who has an IDS laptop though so I can try via IDS.

[MinorMatt]

You need to initialize the new bcm,I don’t know if this can be done using forscan.
In ids it’s in the same menu as the other security and key options as initialize modules or module reset.
This will match the pcm,bcm and keys.

If he can't sort it with Forscan in the next few days I will head there with IDS

[jww9999]

You need to initialize the new bcm,I don’t know if this can be done using forscan.
In ids it’s in the same menu as the other security and key options as initialize modules or module reset.
This will match the pcm,bcm and keys.

Just had a fresh go with Forscan again on this sunny Sunday afternoon (where I am at least) and realised I didn't do a "BCMii Local Interconnect Network New Module Calibration" however whenever I try to run the procedure it is interrupted after the first step and it does not complete the test.

Perhaps IDS is required.

[jww9999]

Hi All.

I've recently replaced the BCM on my 06-reg Mk7 Transit Jumbo T350EF (2.4L RWD 140ps GLX) as the old one was suspected to be faulty.
Managed to successfully re-code in the keys before programming the replacement BCM via Forscan, however I am now getting a PATS flashy code of 23 whenever I try to start the van with any of the keys.
Online research tells me that 23 means "ECU ID Mismatch" so does that mean my van requires a replacement ECU to programmed in? Or could it be something else?
I have tried re-programming the BCM and keys again from scratch but no improvement.

Error Codes obtained from Forscan after clearing all legacy ones are as follows:

PCM
U0426:00-2F Invalid Data Received From Vehicle Immobilizer Control Module
P2265:64-28 Water in Fuel Sensor 'A' Circuit Range/Performance
U0140:00-28 Lost Communication with Body Control Module

BCM
B1048 Brake Fluid Level Switch
B10DA PATS Target Identifier
U2101:00-0A Control Module Configuration Incompatible

RCM
U0155 Lost Communication with the Instrument Panel Cluster Control Module

Any help would be greatly appreciated thanks!

To add to the above, my front passenger side door is now completely deadlocked and will not open at all.
Does anyone know how to un-deadlock a Mk7 front passenger side door?
I am suspicious that it might be BCM related given the recent issues with this van.

[tranmx2]

2012 2.2 RWD.
I cut an oblong out of the driver's side sliding door.
Can be done by drilling a series of small holes or with a disc cutter.
Needs to be at about the right height and about200mm x 250 mm across the top then bend the flap down or up as required. Needs to be about these dims so you can see inside with a torch.
Cut a notch out of the end of a lathe.
The black knob at the back of the sliding door can be moved to open the sliding door. The top of the knob needs to move forward.

A metal plate can be sealed riveted/bolted over the hole.

Knob lhs slide door.png

Rhs cut out .png

[jww9999]

2012 2.2 RWD.
I cut an oblong out of the driver's side sliding door.
Can be done by drilling a series of small holes or with a disc cutter.
Needs to be at about the right height and about200mm x 250 mm across the top then bend the flap down or up as required. Needs to be about these dims so you can see inside with a torch.
Cut a notch out of the end of a lathe.
The black knob at the back of the sliding door can be moved to open the sliding door. The top of the knob needs to move forward.

A metal plate can be sealed riveted/bolted over the hole.

Knob lhs slide door.png

Rhs cut out .png

Thanks, but it's actually the front passenger's door in the cab not the sliding one which has deadlocked

[MinorMatt]

Its up and running now using IDS...

But apparently some new issues!

[jww9999]

Its up and running now using IDS...

But apparently some new issues!

Yes thanks to IDS I could initialise the modules and get it to start and run again however the indicators now all flash very fast (all bulbs are good) and of course the front passenger door (not the sliding one) is still deadlocked.
This van is getting better one step at a time it seems.

[jww9999]

Its up and running now using IDS...

But apparently some new issues!

Yes thanks to IDS I could initialise the modules and get it to start and run again however the indicators now all flash very fast (all bulbs are good) and of course the front passenger door (not the sliding one) is still deadlocked.
This van is getting better one step at a time it seems.

Update: deadlocked door is now fixed and I have replaced both front door locks in the van. I still have other central locking issues however I seem to be getting there one lock at a time. As for the indicators, they are still flashing too fast with no obvious reason why.