F13 EU Maps Released

Introduction

F13 Maps for EU has been found online and added to Syn3 Updater! thanks once again to @AuRoN

Important Notes

This release only updates the Nav, Voice Nav package no new application etc.

It is not ESN locked as per other EU map packs

Rules

  • Do not reply to this thread with general issues that are not specific to F13 Maps
  • If you notice a bug or change specific to this feature report it below

Failure to follow the above rules will result in your post either being moved (if moderators or myself are feeling generous) or deleted without prompt

To clarify, MEM_ERR’s, Missing Logos, LST_ERRS etc should not be posted here, make a new thread using this Support Link

Install Methods

Syn3 Updater

You can update using Syn3 Updater

Manual Method

It’s also added to the manual method available at the below link

Cutdown Maps

It’s also added to the cut down maps at the below link

Package URLs

License:
1U5T-14G424-BN

Nav Voices:
4U5T-14G422-BAL
4U5T-14G422-BBL
4U5T-14G422-BCL
4U5T-14G422-BDL

Maps:
1U5T-14G421-BAL
1U5T-14G421-BBL
1U5T-14G421-BCL
1U5T-14G421-BDL
1U5T-14G421-BEL
1U5T-14G421-BFL
1U5T-14G421-BGL
1U5T-14G421-BHL
1U5T-14G421-BJL

SYNC 3 Common Issues and FAQ’s

Technical Information from FMods

— New Sync 3 EU F13 Maps Released —
Release Date: 2024-10-17 and 2024-10-25

5 Likes

Hey,
Thanks for update.
Which month or quater are this update.
Q2, Q3 or Q4 2013.
Thanks
Regards
Bostjan

Hi
Has anyone successfully downloaded EU F13 maps?
Each time I try, there’s the same corrupt file detected.
See attached screenshot.
I also tried with cut-down version as I only really need UK maps. Same issue.
I tried a couple of different USB sticks, both of which worked to install maps previously, and never used for any other purpose.

It’s not a file issue.
Configure a single download in syn3updater and try again.

Thanks for your reply.
As a test, I attempted to download again the EU F12 maps which I’d already installed when they were first available.
The download fails part way through the first map file.
PU5T-14G386-BB_1690840002000.TAR.GZ downloads correctly.
1U5T-14G421-BAK_1682464992000.TAR.GZ fails part way through, I think.
With the F13 files, a couple of small files were on the USB stick, but the first map file appeared to fail with the error shown.
Could you please be more precise in what you mean by “configure a single download”? Does that mean deselect all but one of the files in the list?
What would the expected result be, and what would it tell us? I’m guessing I should be sure to select a map file, and a different one from the one which shows as corrupt?
Would a momentary interruption of the server data stream, or overloading, cause this issue?
My internet connection is 500Mbit full fibre, and always previously rock solid. I do daily cloud backups and occasional disk image downloads with no issues.

Go to the settings tab, it’s documented in the instructions → Settings Tab - CyanLabs

Once it’s set to 1, try again.

Thanks again.
You are referrring to No of Connections. It’s 1 and I’ve never changed it.
It occurs to me that as the new maps have only been made available only a few days ago, demand for downloads may exceed the available bandwidth. That could affect any downloads from the same cloud provider, for both the latest maps and any earlier ones, which might explain why I had the same issue when I tested downloading F12 maps.
On the other hand, if all files are downloaded to my hard drive before being transferred to to the USB stick, that might not explain the issue I have.
The total size of the download folder is 46Gb, which would roughly equate to a complete set of each of F12 and F13 maps, which is what I have attempted to download today. The filenames also seem to correspond to that theory, with some prefixed 1U5T and others 4U5T.
Are all files saved to the download folder before anything is written to the USB stick? The stick has a light that flashes when it’s being written or read, but it flashes all the time the download is in progress.

I already had 3.4.23188 so I choose to update maps only from F11 to F13. USB preparation went well, also installation in the car started fine and took around 1h. At the end I got no note to remove USB, only that first part was installed successfuly and that I should restart vehicle as soon as possible. Then soon Sync 3 rebooted, after that stated that SW upgrade was successfull and then started installation all over again - I guess I should remove USB by myself when Sync rebooted itself? Anyway, after waiting for second installation to complete I pulled out USB when noted again that first part was done.
Then I restarted vehicle, rebooted Sync 3 (normal, not master reset), but it still says maps are F11, not F13.

Any clues?

This has nothing to do with the nature of this thread, you have incomplete map installation and no following the process. If you have issues create a new thread for troubleshooting.

Downloaded and installed without issue (2019 Focus). Thank you :grin:

I already have the Sync version 3.4.23188 of the F12 map and I chose to install maps only. the update lasted about 1 hour, the system reset but I still have the F12 map version in the settings.

Any solution?

I did the update yesterday and have the same issue.
It took me more than 90 minutes to update. Did a master reset too. But still showing F12 instead F13…

1 Like

The same for me …installed F13 (only maps) twice …successfully updated…but in about Sync is still F12 reference…Could be an issue just for Only Download Maps?

I think I`ll try to install the entire software Software & Maps.

I’ll try that too…
If i install the same version do i have to use autoinstall or downgrade?
Thank you…

Everything good now… i installed the system and the f13 maps. Automatically it selected the downgrade mode .
Everything fine now… thanks :+1:

68 plate Focus, Sync 3.4 build 23188 with F12 maps. All working fine.

Installed F13, the maps installed but the audio stopped working. Tried master reset, and then disconnecting the battery for an hour but still no audio. Reformatted and reinstalled 23188 and F13 again but still no audio.

Ended up reformatting and going back to F12 but the audio is still not working. The display says audio off.

Any advice appreciated.

Edit: Looks like the ACM is not communicating.

image

Log:

Installed files:
1U5T-14G421-BAK
1U5T-14G421-BBK
1U5T-14G421-BCK
5U5T-14G391-AT
4U5T-14G422-BAK
4U5T-14G423-AC
1U5T-14G658-AH

<?xml version="1.0" encoding="UTF-8"?>

<p:OTAModuleSnapShot xmlns:d2p1=“urn:ford/Vehicle/Module/Information/v3.0” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance” xmlns:p=“urn:ford/com/productdesign/ipp/ModuleSnapshot/v2.0” version=“2024-11-03” xsi:schemaLocation=“urn:ford/Vehicle/Module/Information/v3.0 ModuleSnapshot.xsd”>
<p:VIN>XXXXXXXXXXXXXXXXX</p:VIN>
<p:ModuleName>ECU</p:ModuleName>
<p:RequestRole>
d2p1:RoleCONSUMER</d2p1:Role>
d2p1:RoleSourceOTA</d2p1:RoleSource>
d2p1:RoleDescSYNCGEN3</d2p1:RoleDesc>
d2p1:RoleIDOTA</d2p1:RoleID>
</p:RequestRole>
<p:BroadcastDTCType>
<d2p1:DTC DTCValue=“c100000b”/>
<d2p1:DTC DTCValue=“c184000b”/>
</p:BroadcastDTCType>
<p:Node isFlashed=“false” specificationCategory=“GGDS”>
d2p1:Address7D0</d2p1:Address>
<d2p1:ECUAcronym name=“APIM”>
d2p1:State
<d2p1:Gateway gatewayType=“NONE”>
<d2p1:DID didFormat=“ASCII” didType=“Embedded Consumer Operating System Part Number” didValue=“8033” responseLength=“24”>
d2p1:ResponseNU5T-14G381-AD</d2p1:Response>
d2p1:IsConfigfalse</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didFormat=“Packeted” didType=“Embedded Consumer Applications Part Numbers 1” didValue=“8060” responseLength=“384”>
d2p1:IsConfigfalse</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didFormat=“Packeted” didType=“Embedded Consumer Applications Part Numbers 1” didValue=“8061” responseLength=“384”>
d2p1:IsConfigfalse</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didFormat=“HEX” didType=“ECU Checksum 1” didValue=“D704” responseLength=“4”>
d2p1:Response27feeaa1</d2p1:Response>
d2p1:IsConfigfalse</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didFormat=“HEX” didType=“ECU Checksum 2” didValue=“D705” responseLength=“4”>
d2p1:Response206f1387</d2p1:Response>
d2p1:IsConfigfalse</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didType=“Direct Configuraation DID DE00” didValue=“DE00”>
d2p1:Response086a04de1002fc4640c2</d2p1:Response>
d2p1:IsConfigtrue</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didType=“Direct Configuraation DID DE01” didValue=“DE01”>
d2p1:Response554b010bc00a488028b01205</d2p1:Response>
d2p1:IsConfigtrue</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didType=“Direct Configuraation DID DE02” didValue=“DE02”>
d2p1:Response0000010000</d2p1:Response>
d2p1:IsConfigtrue</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didType=“Direct Configuraation DID DE03” didValue=“DE03”>
d2p1:Response00001de1020102</d2p1:Response>
d2p1:IsConfigtrue</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didType=“Direct Configuraation DID DE04” didValue=“DE04”>
d2p1:Response190519052653</d2p1:Response>
d2p1:IsConfigtrue</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didType=“Direct Configuraation DID DE05” didValue=“DE05”>
d2p1:Response80</d2p1:Response>
d2p1:IsConfigtrue</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didType=“Direct Configuraation DID DE06” didValue=“DE06”>
d2p1:Response0b0033000000005ef100005656630061</d2p1:Response>
d2p1:IsConfigtrue</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didFormat=“ASCII” didType=“On-line Diagnostic Database Reference Number” didValue=“F110” responseLength=“24”>
d2p1:ResponseDS-1U5T-14G371-AE</d2p1:Response>
d2p1:IsConfigfalse</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didFormat=“ASCII” didType=“ECU Core Assembly Number” didValue=“F111” responseLength=“24”>
d2p1:Response1U5T-14G380-FD</d2p1:Response>
d2p1:IsConfigfalse</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didFormat=“ASCII” didType=“ECU Delivery Assembly Number” didValue=“F113” responseLength=“24”>
d2p1:Response3U5T-14G371-GDD</d2p1:Response>
d2p1:IsConfigfalse</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didFormat=“ASCII” didType=“ECU Calibration Data #1 Number” didValue=“F124” responseLength=“24”>
d2p1:Response1U5T-14G375-HA</d2p1:Response>
d2p1:IsConfigfalse</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didFormat=“ASCII” didType=“Private Sub Node #1 Serial Number” didValue=“F141” responseLength=“16”>
d2p1:ResponseLX5G009D</d2p1:Response>
d2p1:IsConfigfalse</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didFormat=“State Encoded” didType=“Software Download Specification Version” didValue=“F162” responseLength=“1”>
d2p1:ResponseBlank</d2p1:Response>
d2p1:IsConfigfalse</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didFormat=“State Encoded” didType=“Diagnostic Specification Version” didValue=“F163” responseLength=“1”>
d2p1:Response03</d2p1:Response>
d2p1:IsConfigfalse</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didFormat=“ASCII” didType=“Vehicle Manufacturer ECU Software Number” didValue=“F188” responseLength=“24”>
d2p1:Response1U5T-14G374-AE</d2p1:Response>
d2p1:IsConfigfalse</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didFormat=“ASCII” didType=“ECU Serial Number” didValue=“F18C” responseLength=“16”>
d2p1:Response</d2p1:Response>
d2p1:IsConfigfalse</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didFormat=“HEX” didType=“ECU MAC Address 1” didValue=“F1D0” responseLength=“6”>
d2p1:Response0c:b2:b7:c9:e2:92</d2p1:Response>
d2p1:IsConfigfalse</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didFormat=“HEX” didType=“ECU MAC Address 2” didValue=“F1D1” responseLength=“6”>
d2p1:Response0c:b2:b7:c9:e2:93</d2p1:Response>
d2p1:IsConfigfalse</d2p1:IsConfig>
</d2p1:DID>
</d2p1:Gateway>
</d2p1:State>
</d2p1:ECUAcronym>
<d2p1:ODLNetwork d2p1:NetworkDataRate=“500” d2p1:NetworkName=“HS-CAN” d2p1:NetworkProtocol=“CAN” d2p1:DLCName=“SAE J1962” d2p1:Pins=“6,14”/>
<d2p1:DTC DTCValue=“c100000b”/>
<d2p1:DTC DTCValue=“c184000b”/>
<d2p1:AdditionalAttributes logGeneratedDateTime=“2024-11-03T14:13:56+00:00” RAM=“1015939072” vmcuVersion=“Vector_VMCU_05.04.10”>
<d2p1:PartitionHealth type=“/fs/sd/MAP/” total=“1.2G” available=“804K”/>
<d2p1:PartitionHealth type=“/fs/sd/MAP/” total=“2.4G” available=“14M”/>
<d2p1:PartitionHealth type=“/fs/sd/MAP/” total=“3.2G” available=“26M”/>
<d2p1:PartitionHealth type=“/fs/Nuance/” total=“5.0G” available=“29M”/>
<d2p1:PartitionHealth type=“/fs/Nuance/” total=“1.9G” available=“8.4M”/>
<d2p1:PartitionHealth type=“/fs/Nuance/grace” total=“1003M” available=“21M”/>
<d2p1:PartitionHealth type=“/fs/rwdata/” total=“1.2G” available=“988M”/>
<d2p1:PartitionHealth type=“/fs/rwdata/quip/” total=“35M” available=“35M”/>
<d2p1:PartitionHealth type=“/fs/rwdata/quip/” total=“90M” available=“90M”/>
<d2p1:PartitionHealth type=“/fs/mp/” total=“1.4G” available=“84M”/>
<d2p1:PartitionHealth type=“/fs/mp/resources” total=“72M” available=“332K”/>
<d2p1:PartitionHealth type=“/fs/images/” total=“54G” available=“37G”/>
d2p1:InstallationLog/

This has nothing to do with the update. check wiring, battery, fuses, etc

I’m such an idiot. It was fuse 23 in the passenger fuse board. My dashcam was using it, I moved it to a better fuse (number 3) just before updating to F13 and forgot to replace it.

Thank you.

Had 3.4.23188 already installed and used a random usb 3.0 flashdrive to update to F13 (selection of EU). 60 minuten of processing time and removed the flashdrive after Ford logo appeared. F13 is there, without having to reset to factory default. Thanks and enjoy the coffee.

My compliments to the whole team. I can’t reach the F13 maps. An error appears, like the attached photo. Thank you.
Uploading: IMG_20241105_211208.jpg…