Sync 3 to Sync 3

Hi all,

Have access to a reasonably cheap 4U5T-14G371-GFA apim that runs Sync 3.3, from a Euro Focus mk4. Idea was to put it in a 2017 Kuga, just for the sake of having stronger hardware base before updating to Sync 3.4 . Now, had it briefly in the car with following issues;

Won’t turn off with ignition off/door open
No RVC/PDC display
No outside temp display

Otherwise works well :slight_smile:

Would it be possible to configure it to my Kuga eventually or is the hardware too advanced for my car?

Thanks,

Dean


SYNC Region: EU

Navigation Variant: Nav

Manufacturer Year: Pre MY20

Install Type: OEM

Old SYNC Version: 3.0

New SYNC Version: 3.3

Do you have a error message, if so what is it?
No

Update Method: Official Ford

You need to drop in the AsBuilt from your Kuga so that it matches the logic/hardware in the car.
You’ll still have the same interface as the newer version of Sync not the old 3.0 one.

Yeah, did that already, quite a mismatch between the two in terms of number of fields. Symptoms are after original as built was loaded and master reset done.

Dean

Please post your original Sync 3.0 and the new asbuilt from the -GFA if you have it. (Always save)

The unit not shutting down is an Illumination Gateway issue, needs the proper settings for the asbuilt. The others are asbuilt settings also.

You can look these up in the Sync 3 database here on the site.

Sory, tried to post something…in a sec

Just post them as text files if it’s easier. Drag and drop to the edit screen.

Top row would be the old, original one.

Dean

Second part

Vehicle Make: Ford
Vehicle Model: Kuga C520 (C1CMA platform)
Vehicle Year: 2017
Vehicle Region: EU
HB5T-14G371-FAH, 64GB, WITH NAV with Sync 3.0
4U5T -14G371 -GFA, 64GB, WITH NAV with Sync 3.3

Adding the -GFA changed the way the lighting strategy performs. Since this is a EU C1CMA vehicle, the value at 7D0-06-01 should likely be 81 instead of 80. In the original APIM, the value is 80, but that APIM Strategy file is -FA (US export) vs -HA (EU 64G NAV). The difference in the strategy files will change settings in the vehicle. Also, Sync 3.2+ handles lighting differently than 3.0.

You can see that all the way thru the new asbuilt it is defined for C1CMA, whereas the original asbuilt was defined for CGEA vehicles. (Thus the -FA strategy file.)

Ensure 7DO-01-02 xxxx xxxx Xx is set for C1CMA. Change the 8 to 0.

The strategy file difference is the culprit here, but you can’t really change it back to the original. The Illumination Cal file is likely different from previous also. Performing a firmware change could just fix all this if the C1CA settings don’t, but there is no guarantee.

These are the firmware versions for the 2 APIM’s. It looks like the -GFA contains specific regional firmware.
JX7T-18K811-AC
H1BT-14F571-HA
JX71-18B955-FC
K1BT-14F180-FB
Also, I would be careful reformatting this unit as it may be MY20+ eMMC.
1U5T-14G380-FE

7D0
F110>DSGB5T-14G371-CB
F111>HB5T-14G380-CA
F113>HB5T-14G371-FAH
F124>GB5T-14G375-FA
F141>LV9C005M
F188>GB5T-14G374-CB
F18C>
F1D0>B0:D5:CC:A5:96:E1
F1D1>B0:D5:CC:A5:96:E2

7D0
F10A>GB5T-14G379-AA
F110>DS1U5T-14G371-DA
F111>1U5T-14G380-FE
F113>4U5T-14G371-GFA
F124>1U5T-14G375-HA
F129>JX7T-18K811-AC
F12A>H1BT-14F571-HA
F12B>JX71-18B955-FC
F12C>K1BT-14F180-FB
F141>LY5F01M8
F142>B92012593
F143>20190424102738
F16B>JB5T-14G379-FA
F188>1U5T-14G374-DA
F190>WF0NXXGCHNKL52247
F1D0>0479B70F6D57
F1D1>0479B70F6D58

That block I tried with 81, nothing happened.

Have to try that.

Are you saying that it’s probably impossible to make it work? Including the RVC & PDC & Temp display?

Thank you,

Regards,
Dean

Requires a master reset.

Not impossible, just maybe impractical. With the proper firmware I believe it will work, but you’ll have to change the firmware on that APIM or acquire another with the proper firmware. Changing the firmware does not come without risks, especially for the GFA unit with specific regional firmware.

Here are the 2 firmware sets for FA and HA.
Calibration MY20 Navi 32G FA.zip (285.1 KB)
Calibration MY20 Navi 64G HA.zip (285.1 KB)

Did a master reset and the setting remained saved, but the lighting strategy remained. AFAIK GFA is not a MY20 emmc unit.

I’m not too concerned about frying it, so I might give it a go, but I’m not sure I follow your firmware logic here :slight_smile: why 32G, both are 64G. Sorry about that. In plain english - which FW should I load, both? And if successful, I should be able to configure it?

Dean

BTW, GFA equipped vehicle was a UK model.

D

How do I load these with FS? I choose custom, and then? Will FS suggest the correct file or I have to choose specific file for it’s intended location?

Thank you,

Dean

First you Unzip the files and move them to Forscan calibration folder, usually found in your user document folder.

Yes, but how do I choose proper files, between the two zips. I’m on fs, not ucds

Thanks,
Dean

Do you have a 32Gig APIM or a 64Gig

The files are posted to give you the option as to what you would like to do about fixing the issue. This is your decision alone. ˝o back and read my reply and you will see the options presented.

Thank you Chief. @Rollback_Jockey , it’s 64GB.

Dean