UCDS Forum

Hi,

A friend of me updated his IPC with UCDS, but now he thinks UCDS flashed the firmware for a gasoline version instead of those of a diesel.

So he has a diesel, but the tachometer doesn't show the red zone anymore (a gasoline goes higher in rpm than a diesel)

I wonder how to fix this?

Thanks!

Please give more information. Vehicle, HW number, Old SW Number, New SW Number.
If you make this operation from Upadate Wizard, it auto save poll to session folder.
Find you session with older date of file, and open in update wizard

Vehicle is a ford mondeo 2.0 TDCI 2015 Clipper This is what i retrieve from the session poll.

<d DID="F110" Desc="On-line Diagnostic Database Reference Number" Data="DS-EM2T-1A292-JAA"/>
<d DID="F111" Desc="ECU Core Assembly Number" Data="DS7T-14F094-AJA"/>
<d DID="F113" Desc="ECU Delivery Assembly Number" Data="FS7T-10849-ALB"/>
<d DID="F120" Desc="ECU Software #2 Part Number" Data="FS7T-14C026-BJG"/>
<d DID="F124" Desc="ECU Calibration Data #1 Number" Data="FS7T-14C088-AJG"/>
<d DID="F125" Desc="ECU Calibration Data #2 Number" Data="FS7T-14C088-BJG"/>
<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="FS7T-14C026-AJG"/>
<d DID="F18C" Desc="ECU Serial Number" Data="RGLB010652"/>
So no red zone on my RPM meter.
I have also noticed now that the sound of my park distance sensors in the back is turned down really quietly. In the front there's no problem. When i'm in the red distance zone the sound level is back to normal.
Also my adaptive headlights only turn to the right and go back to the center. They never go to the left anymore.
Would you know any resolutions for my problems?
Thanks in advance

This might be a problem of the IPC donor. I suggest it was from a Galaxy or a S-Max from the Database reference number. Do you have the original module data, e.g. the session poll before updating?

I thought the firmware comes from the Ford servers...

So in fact it needs to check what model, engine,... it is, u need firmware for

The firmware is identical for Diesel or Gasoline as well as for left or right hand driving, the difference (my knowledge from the MK4!) should be coded in the eeprom 24c32 of the IPC. Once we know more about the donor car, we can trace this back...

Why the need of a donor car if the software comes directly from the Ford server?

I guess FDRS works in a different way, no?

I want to update my IPC aswell, but not with this kind of bugs in it, where u loose the red zone.

This is the very first session so i'm guessing that this is the one needed?
<m module="IPC">
<d DID="F110" Desc="On-line Diagnostic Database Reference Number" Data="DS-DS7T-1A292-BJA"/>
<d DID="F111" Desc="ECU Core Assembly Number" Data="DS7T-14F094-AJA"/>
<d DID="F113" Desc="ECU Delivery Assembly Number" Data="FS7T-10849-ALB"/>
<d DID="F120" Desc="ECU Software #2 Part Number" Data="FS7T-14C026-BJB"/>
<d DID="F124" Desc="ECU Calibration Data #1 Number" Data="FS7T-14C088-AJB"/>
<d DID="F125" Desc="ECU Calibration Data #2 Number" Data="FS7T-14C088-BJB"/>
<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="FS7T-14C026-AJB"/>
<d DID="F18C" Desc="ECU Serial Number" Data="RGLB010652"/>
</m>

I hope your problem is solved soon!

Short Update
(1) I flashed the Mondeo Mk5 IPC update (on a Diesel engine Mondeo) via the update wizard and my red line is also gone.
(2) The tachometer is displaying the rpm correctly, so it's not a gasoline/diesel thing
(3) If you look at Drive2.ru you will find several guys who updated their IPC's and some have the red line (e.g. geny4, "https://www.drive2.ru/l/10603549/" or rfkeuf40 "https://www.drive2.ru/l/451362993293232421/"), some others not (alex2ford, "https://www.drive2.ru/l/10519948/" or PasserSBP "https://www.drive2.ru/l/455102982095110919/")...
(4) I observed no strange behavior of the adaptive head lights, their are moving left and right, so this seems to be another issue..

I hope the UCDS developers may help?!!!

The moving right and left thing of the headlamps is indeed a different thing, maybe he changed some hex codes or something and that gave the error of the headlights.

For the IPC, only happened after the flash, no hex changed!

Indeed the moving of the headlights is something different but most likely a defective headlamp (since the hex are still original)
The red line I still don't know how it comes. I am dropping off my car tomorrow for a global checkup of the lights and some ratteling noises.
I hope they don't go and downgrade the IPC and such. Anyways i'll see..

So it seems some tachometers are working correct and some not...

Another update...

I found that the upgrade (via the update wizard) to the AJG version changed the content of the 24C32 eeprom of the IPC. I found another VIN beside my VIN in the eeprom, a VIN from an american Ford Fusion?!!
I flashed back the original eeprom content from the AJB version, but the red line is still absent. Next step was a downgrade via the VBF loader to the AJB version, which brought back the red line....
That's really strange....
Why does the update wizard change the eeprom content? Is there a tool to read out the eeprom without disassembling of the IPC?

Hey as2222us
How did you downgrade via the VBF loader? I would like to see if this resolves my problems as well. Would you be willing to explain it to me via here or via private message?
thanks!
I just got my car back from the garage but am still having the problems with my adaptive lights not fully moving. They told me it's normal but i beg to differ. I used to see them turn both ways...