Mondeo V Update Module IPMA
Добавлено: 02 ноя 2017, 17:34
Module Update failed with Update Wizard; thereafter the module is no longer listed with "Get info from Vehicle" in Wizard.
V.2.0.003.001
In order to give it a second try via the VBF-File Loader (and changing download sequence for files 4 and 5 and setting CanBus HS 2 as it is suggested in a German forum, where people succeeded in overcoming the problem), I need to list the files for the update in the VBF-Loader. And here starts the trouble: I certainly have all required files in the download folder as I downloaded them before using the Upd.-Wiz, but as the Upd.-Wiz. no longer lists the IPMA-Module I don't know for sure the correct file names for the newest update. Of course, I could go back to the software-level before the failed update by using infos form the "uuw" file in the Sessions folder in order to hope that thereafter the Upd.-Wiz. again lists this module and the files required for the update, but this is a rather tedious procedure.
Can somebody list the files here?
From the uuw -file I took this section to identify the module:
<m module="IPMA">
<d DID="F10A" Desc="ECU Cal-Config Part Number" Data="DS7T-14G024-EE"/>
<d DID="F110" Desc="On-line Diagnostic Database Reference Number" Data="DS-FU5A-17E678-SC"/>
<d DID="F111" Desc="ECU Core Assembly Number" Data="DS7T-14G025-EK"/>
<d DID="F113" Desc="ECU Delivery Assembly Number" Data="DU5A-17E678-EL"/>
<d DID="F120" Desc="ECU Software #2 Part Number" Data="FT4T-14G082-HD"/>
<d DID="F162" Desc="Software Download Specification Version" Data=""/>
<d DID="F163" Desc="Diagnostic Specification Version" Data="0x03"/>
<d DID="F16B" Desc="ECU Cal-Config #2 Part Number" Data="FT4T-14G081-HD"/>
<d DID="F188" Desc="Vehicle Manufacturer ECU Software Number" Data="DS7T-14G019-EH"/>
</m>
This is my best guess for the VBF-Loader, based on this data and my Downloads-folder:
Problem solved: After confirming the correct files, an attempt to update via the VBF-loader failed, when it came to the 15MB-file. I loaded the 15MB-file then separatly in a second run of the VBF and it worked. Forced programming of DEAD-module was not used.
V.2.0.003.001
In order to give it a second try via the VBF-File Loader (and changing download sequence for files 4 and 5 and setting CanBus HS 2 as it is suggested in a German forum, where people succeeded in overcoming the problem), I need to list the files for the update in the VBF-Loader. And here starts the trouble: I certainly have all required files in the download folder as I downloaded them before using the Upd.-Wiz, but as the Upd.-Wiz. no longer lists the IPMA-Module I don't know for sure the correct file names for the newest update. Of course, I could go back to the software-level before the failed update by using infos form the "uuw" file in the Sessions folder in order to hope that thereafter the Upd.-Wiz. again lists this module and the files required for the update, but this is a rather tedious procedure.
Can somebody list the files here?
From the uuw -file I took this section to identify the module:
<m module="IPMA">
<d DID="F10A" Desc="ECU Cal-Config Part Number" Data="DS7T-14G024-EE"/>
<d DID="F110" Desc="On-line Diagnostic Database Reference Number" Data="DS-FU5A-17E678-SC"/>
<d DID="F111" Desc="ECU Core Assembly Number" Data="DS7T-14G025-EK"/>
<d DID="F113" Desc="ECU Delivery Assembly Number" Data="DU5A-17E678-EL"/>
<d DID="F120" Desc="ECU Software #2 Part Number" Data="FT4T-14G082-HD"/>
<d DID="F162" Desc="Software Download Specification Version" Data=""/>
<d DID="F163" Desc="Diagnostic Specification Version" Data="0x03"/>
<d DID="F16B" Desc="ECU Cal-Config #2 Part Number" Data="FT4T-14G081-HD"/>
<d DID="F188" Desc="Vehicle Manufacturer ECU Software Number" Data="DS7T-14G019-EH"/>
</m>
This is my best guess for the VBF-Loader, based on this data and my Downloads-folder:
Problem solved: After confirming the correct files, an attempt to update via the VBF-loader failed, when it came to the 15MB-file. I loaded the 15MB-file then separatly in a second run of the VBF and it worked. Forced programming of DEAD-module was not used.