UCDS Forum

Hi,
due to a dead module, can anyone let me know which files in which arrangement (Bootloader, File1, File2,....) needs to be programmed via VBF-Loader to get it live again?

Secondary Bootloader: GB5T-14G376-AA
Vehicle Manufacturer ECU Software File: GB5T-14G374-CB
ECU Cal-Config Part: GB5T-14G379-AA
ECU Calibration Data #1: GB5T-14G375-FA

Do not program ECU Cal-Config #2 Part: GB5T-14G379-BA. This will end in a dead module with Vehicle Manufacturer ECU Software File: GB5T-14G374-CB.
The ECU Cal-Config #2 Part: GB5T-14G379-BA does work with the Vehicle Manufacturer ECU Software File: GB5T-14G374-CD and ECU Calibration Data #1: GB5T-14G375-FB. But this will cause a DTC U2100 in the APIM.

My apim seems to be dead
No ford logo, no menu..from time to time only reading disc

IT seams that it cannot starts its build software. What files should I fill into to have it back again?

SEC bootloader ??????
Vehicle Manufacturer ECU Software Number" Data="1U5T-14G374-DA"
Ecu call conf part ??????
ECU Calibration Data #1 Number" Data="1U5T-14G375-HA"

<m module="APIM">
<d DID="F110" Desc="On-line Diagnostic Database Reference Number" Data="DS-1U5T-14G371-DA"/>
<d DID="F111" Desc="ECU Core Assembly Number" Data="GU5T-14G380-FD"/>
<d DID="F113" Desc="ECU Delivery Assembly Number" Data="KU5T-14G371-GDE"/>
<d DID="F124" Desc="ECU Calibration Data #1 Number" Data="1U5T-14G375-HA"/>
<d DID="F141" Desc="Private Sub Node #1 Serial Number" Data="NXB5002J"/>
<d DID="F162" Desc="Software Download Specification Version" Data=""/>
<d DID="F163" Desc="Diagnostic Specification Version" Data="0x03"/>
<d DID="F188" Desc="Vehicle Manufacturer ECU Software Number" Data="1U5T-14G374-DA"/>
<d DID="F18C" Desc="ECU Serial Number" Data="0xFF0xFF0xFF0xFF0xFF0xFF0xFF0xFF0xFF0xFF0xFF0xFF0xFF0xFF0xFF0xFF"/>
<d DID="F1D0" Desc="ECU MAC Address 1" Data="L?0xD3N0x8Cc"/>
<d DID="F1D1" Desc="ECU MAC Address 2" Data="L?0xD3N0x8Cd"/>
</m>

regards
rfr78

Load your .uuw-file into the update wizard, then you will see all necessary information.

AmigaSurfer писал(а): Do not program ECU Cal-Config #2 Part: GB5T-14G379-BA. This will end in a dead module with Vehicle Manufacturer ECU Software File: GB5T-14G374-CB.
The ECU Cal-Config #2 Part: GB5T-14G379-BA does work with the Vehicle Manufacturer ECU Software File: GB5T-14G374-CD and ECU Calibration Data #1: GB5T-14G375-FB. But this will cause a DTC U2100 in the APIM.

Hi, please can you explain this?

What's the problem with ECU Cal-Config #2?
It's the audio profile and illumination strategy, i flashed it many times but i never faced any problem.

Do you have ever flashed the following files with the Update-Wizard in this order:
GB5T-14G376-AA
GB5T-14G374-CB
GB5T-14G379-AA
GB5T-14G375-FA
GB5T-14G379-BA

My APIM was dead after this and some others too. See here (German language) https://mondeo-mk5.de/forum/index.php?t ... #post50250.
If you use the VBF-Loader and leave the GB5T-14G379-BA away, then you can get the dead APIM working again.
With GB5T-14G374-CD or HB5T-14G374-CA you have not this problem.

I thought the audio profile is "F10A ECU Cal-Config Part Number", not "F16B ECU Cal-Config #2 Part Number". Because on some Mondeos there are the text "DEMOAUDIOPROFILE" in "F10A ECU Cal-Config Part Number".

The DTC U2100 in the APIM can be fixed by backup the asbuilt data from the APIM with FORScan and write the whole backup back to the APIM.

Why are you flashing GB5T-14G375-FA if you are from German? This is for 32GB APIM

64GB EU APIM should flash XXXX-14G375-H*.

The order

GB5T-14G376-AA
GB5T-14G374-CB
GB5T-14G379-AA
GB5T-14G375-FA
GB5T-14G379-BA

is not correct.

This is the correct order, you can choose to NOT use the last two vbf files which are audio profiles and illumination calbirations.

GB5T-14G376-AA.vbf (Bootloader) //Mandatory
XXXX-14G374-EF.vbf (Diret Config Configuration) //Mandatory
XXXX-14G375-FA.vbf (ECU Calibration Data) //Mandatory
GB5T-14G379-AA.vbf (ECU Cal-Config #1 AKA Audio Profiles) //Facoltative
XXXX-14G379-BA.vbf (ECU Cal-Config #2 AKA Illumination) //Facoltative

Where i put XXXX is because these files change based on calibration version, the other ones (bootloader and audio profiles) never change, because even cars with new version 3.4 produced last week in ford factory use the same GB5T version.

Regarding the correct 14G375 files here a short summary:

XXXX-14G375-A*.vbf 8GB / 16GB EU without NAV
XXXX-14G375-B*.vbf 8GB / 16GB NA without NAV
XXXX-14G375-C*.vbf 8GB / 16GB ROW without NAV
XXXX-14G375-D*.vbf 32GB NA with NAV
XXXX-14G375-E*.vbf 32GB CHINA with NAV
XXXX-14G375-F*.vbf 32GB XX (i think it means ANY region) with NAV (Telenav)
XXXX-14G375-G*.vbf 32GB ROW With NAV (NNG)
XXXX-14G375-H*.vbf 64GB EU with NAV
XXXX-14G375-J*.vbf 32GB TURKEY with NAV
XXXX-14G375-K*.vbf 32GB UAE with NAV (NNG)

I've collected the data of some Mondeo MK5. Except one, all have GB5T-14G375-FA, GB5T-14G375-FB or HB5T-14G375-FA. Only the new module from 2019 have 1U5T-14G375-HA. See attached picture.

Does this mean, that APIMs in the European Mondeo MK5 are all shipped with only 32 GByte until end of 2018?

Does this mean, that APIMs in the European Mondeo MK5 are all shipped with only 32 GByte until end of 2018?

No way, maps and other packages are too big for 32GB flash. (actually, they does fit, but then it's no longer possible to update maps)

It could be that this is valid for MY18.5 apim then...

Hi,
Does anybody know a solution or have the files to be loaded into an APIM NA version (with NAV) to be converted in EU version?
Cheers.

Who can help with Death APIM VIN 1FA6P8CF8H5286771?
APIM Part Number GB5T-14G371-BFC

What Files i have to use in VBF-Loader?

Thx

SoerenGT писал(а):Who can help with Death APIM VIN 1FA6P8CF8H5286771?
APIM Part Number GB5T-14G371-BFC

What Files i have to use in VBF-Loader?

Thx

Try in the following order

GB5T-14G376-AA
GB5T-14G374-CB
GB5T-14G379-AA
GB5T-14G375-CA
GB5T-14G379-BA

Sleep all modules too, if the APIM is already dead you may need to select forced programming.

Good luck let us know how you get on

Hello,
How can I know the internal memory size of an APIM?
When I use the utility (xml creator) I get the following which looks different than a "regular" result:

<d2p1:AdditionalAttributes logGeneratedDateTime="2019-11-16T21:15:41+00:00" RAM="1091031040" vmcuVersion="Vector_VMCU_02.02.20">
<d2p1:PartitionHealth type="/dev/hd0t180" total="21105421312" available="115781600"/>
<d2p1:PartitionHealth type="/dev/hd0t181" total="758272000" available="2097120"/>
<d2p1:PartitionHealth type="/dev/hd0t177" total="136776704" available="2097152"/>
<d2p1:InstallationLog/>

Cheers.

rob180 писал(а):

SoerenGT писал(а):Who can help with Death APIM VIN 1FA6P8CF8H5286771?
APIM Part Number GB5T-14G371-BFC

What Files i have to use in VBF-Loader?

Thx

Try in the following order

GB5T-14G376-AA
GB5T-14G374-CB
GB5T-14G379-AA
GB5T-14G375-CA
GB5T-14G379-BA

Sleep all modules too, if the APIM is already dead you may need to select forced programming.

Good luck let us know how you get on

no, its not working.
you must know it interupts after reformat an trying to install the 3.4 software,
so there is only the formated apim i think.
perhaps there is someone who can help (also via teamviewer between 16-20h CET/MEZ)

Hi,

I currently have
GB5T-14G379-AA
HB5T-14G371-CA
HB5T-14G380-CA
HB5T-14G371-FAH
HB5T-14G375-FA
HB5T-14G379-BA
HB5T-14G374-CA

can I flash it with newer version ?
GB5T-14G376-AA
1U5T-14G374-EE
1U5T-14G375-HA ( or maybe FA - but i have 64 GB EU )
GB5T-14G379-AA
5U5T-14G379-BA

thank you for support