MEM_err01 upon installing custom europe maps

insaneinsanovich · 21 February 2024 19:06

I bought 2 months ago a full upgrade kit from Sync2 to Sync3. It was killing me that the SYNC2 APIM didn’t have Android Auto support so I finally decided to buy a SYNC3 from Aliexpress.

Installed it a week ago and it’s night and day how comfortable and handy is SYNC3. Even before upgrade I felt like my SYNC2 was a useless piece of garbage, but I digress.

Everything works fine except 2 things: the bloody watch when ignition is off has a mind of it’s own and GPS antena seems to no pick any signal, hence “reset time by GPS” doesn’t work.
I feel like this 2 problems are related to each other.

Tiny mention, my unit is a 32GB one and it didn’t come with maps pre-installed, because from what the seller mentioned is that European maps would take too much disk space. I still purchased the 32 GB version because I planned to use Android Auto anyway, and the diference in price between 8GB and 32GB was a just a couple of $, rather than spending another 70 dollars to upgrade to 64 GB.

1 month later I received the unit, and noticed that the seller disabled NAV by changing DE00/7D0-01-02, but with forscan I easily restored factory AsBuilt which enabled NAV back.

So back to the problem. In order to test GPS signal I decided to install the cut down map packages containing only Eastern and Central Europe + Voice packages containing Russian and English. Prepared a USB stick using Syn3 Updater where I chose “Only update maps” option, installed it in the console and after APIM restarted it threw me the MEM_err01 error.
Interogator log most probably shows me that there is not enough space to install all the maps:
<d2p1:AdditionalAttributes logGeneratedDateTime=“2014-01-01T07:25:59+00:00” RAM=“1430413312” vmcuVersion=“Vector_VMCU_05.02.08”>
<d2p1:PartitionHealth type=“/fs/sd/MAP/” total=“1.2G” available=“804K”/>
<d2p1:PartitionHealth type=“/fs/sd/MAP/” total=“3.8G” available=“21M”/>
<d2p1:PartitionHealth type=“/fs/sd/MAP/” total=“6.7G” available=“48M”/>
<d2p1:PartitionHealth type=“/fs/Nuance/” total=“5.0G” available=“29M”/>
<d2p1:PartitionHealth type=“/fs/Nuance/” total=“3.3G” available=“27M”/>
<d2p1:PartitionHealth type=“/fs/Nuance/” total=“1.3G” available=“4.7M”/>
<d2p1:PartitionHealth type=“/fs/Nuance/grace” total=“1.3G” available=“22M”/>
<d2p1:PartitionHealth type=“/fs/rwdata/” total=“1.2G” available=“932M”/>
<d2p1:PartitionHealth type=“/fs/rwdata/quip/” total=“35M” available=“35M”/>
<d2p1:PartitionHealth type=“/fs/rwdata/quip/” total=“90M” available=“88M”/>
<d2p1:PartitionHealth type=“/fs/mp/” total=“1.4G” available=“84M”/>
<d2p1:PartitionHealth type=“/fs/images/” total=“25G” available=“1.1G”/>

Another headache, and another 2-ish hours of research showed me that it is possible to empty the storage if I use reformat method, but only if the APIM itself is not a MY20 unit produced after 2020 which mine is not (NU5T-14G381-AD). After taking apart my console, AGAIN, discovered that it is an old unit from a Ford Focus ST from 2016. It even had a sticker on it with VIN number from the old car. Me being stupid, didn’t take a picture of it.

Anyway, I was more afraid of the screen itself, because when I initially installed it, it was brand new…which meant Old APIM + New Display. It didn’t have any stickers on the display body itself, however I found a part of the sticker in the display body crack (I guess it’s meant for passive cooling) which contained a QR code. Managed to scan it with my phone, and it returned “LQ080Y5DZ05 68121531”.

Now the million dollar question (not really, maybe 80-100 USD question). Will the reformat method work in my case, or it will not?
From what I understood the reformat method doesn’t contain the necessary display drivers, but I couldn’t find 100% sure information that my display is older than 2020.

If reformat method is a no go, from what I briefly read in other topics, is that in fact when creating the USB using the Syn3Updater, it creates a bash script, and when the usb stick is inserted in the console, the script is automatically executed.
Someone tried to just clean only the map files from the SYNC3 unit…and either succeeded or not. Someone could, someone not. What I understood is the map files could be somehow protected (this part I didn’t understand exactly). I’m working myself in Linux environment. Maybe I could look into it, but I need to know in more details what kind of distro or fork of which distro is used in Sync3, what is the directory tree structure, etc.

Your help will be greatly appreciated.

SYNC Region: EU

Navigation Variant: Nav

Manufacturer Year: Pre MY20

Install Type: Retrofit

Old SYNC Version: 0

New SYNC Version: 3.4.23188

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

Update Method: CyanLabs Syn3 Updater

Syn3 Updater Version: 2.12.5.0

Syn3 Updater Documentation Read: yes

Syn3 Updater Log File

CYANLABS - SYN3 UPDATER - V2.12.5.0
Branch: Stable
Operating System: Майкрософт Windows 10 Pro (2009)

PREVIOUS CONFIGURATION
Version: 3.4.23188
Region: EU
Navigation: True
Install Mode: Auto-Detect (autoinstall)
Install Mode Overridden: False
My20 Protection Enabled: Auto-Detect

DESTINATION DETAILS
Mode: Drive
Model: JetFlash Transcend 32GB USB Device
Size: 29.4GB
FileSystem: FAT32
Partition Type: MBR

AUTOINSTALL.LST
; CyanLabs Syn3Updater 2.12.5.0 Stable - Autoinstall Mode - Only Update Maps EU

[SYNCGen3.0_3.0.1_PRODUCT]
Item1 = RWDataCleaner TOOL - PU5T-14G386-BB_1690840002000.TAR.GZ
Open1 = SyncMyRide\PU5T-14G386-BB_1690840002000.TAR.GZ
Item2 = MAP_LICENSE - 1U5T-14G424-BM_1683133039000.TAR.GZ
Open2 = SyncMyRide\1U5T-14G424-BM_1683133039000.TAR.GZ
Item3 = MAP - 1U5T-14G421-BHK_1682468092000.TAR.GZ
Open3 = SyncMyRide\1U5T-14G421-BHK_1682468092000.TAR.GZ
Item4 = VOICE_NAV - 4U5T-14G422-BAK_1682464728000.TAR.GZ
Open4 = SyncMyRide\4U5T-14G422-BAK_1682464728000.TAR.GZ
Item5 = MAP - 1U5T-14G421-BBK_1682466740000.TAR.GZ
Open5 = SyncMyRide\1U5T-14G421-BBK_1682466740000.TAR.GZ
Options = AutoInstall

[SYNCGen3.0_3.0.1]
Item1 = MAP - 1U5T-14G421-BFK_1682467908000.TAR.GZ
Open1 = SyncMyRide\1U5T-14G421-BFK_1682467908000.TAR.GZ
Item2 = MAP - 1U5T-14G421-BGK_1682467948000.TAR.GZ
Open2 = SyncMyRide\1U5T-14G421-BGK_1682467948000.TAR.GZ
Item3 = MAP - 1U5T-14G421-BDK_1682467734000.TAR.GZ
Open3 = SyncMyRide\1U5T-14G421-BDK_1682467734000.TAR.GZ
Options = AutoInstall, Include, Transaction

[SYNCGen3.0_ALL]
Item1 = MAP - 1U5T-14G421-BAK_1682464992000.TAR.GZ
Open1 = SyncMyRide\1U5T-14G421-BAK_1682464992000.TAR.GZ
Item2 = VOICE_NAV - 4U5T-14G422-BCK_1682464838000.TAR.GZ
Open2 = SyncMyRide\4U5T-14G422-BCK_1682464838000.TAR.GZ
Item3 = MAP - 1U5T-14G421-BEK_1682467790000.TAR.GZ
Open3 = SyncMyRide\1U5T-14G421-BEK_1682467790000.TAR.GZ
Options = Delay, Include, Transaction


FILES (11)
PU5T-14G386-BB_1690840002000.TAR.GZ (3.2KB)
1U5T-14G424-BM_1683133039000.TAR.GZ (1.7KB)
1U5T-14G421-BAK_1682464992000.TAR.GZ (2.3GB)
1U5T-14G421-BBK_1682466740000.TAR.GZ (541.8MB)
1U5T-14G421-BDK_1682467734000.TAR.GZ (1.1GB)
1U5T-14G421-BEK_1682467790000.TAR.GZ (1.7GB)
1U5T-14G421-BFK_1682467908000.TAR.GZ (2.5GB)
1U5T-14G421-BGK_1682467948000.TAR.GZ (2GB)
1U5T-14G421-BHK_1682468092000.TAR.GZ (2.7GB)
4U5T-14G422-BAK_1682464728000.TAR.GZ (2.3GB)
4U5T-14G422-BCK_1682464838000.TAR.GZ (1.7GB)

LOG
[19-Feb-24 18:44:27] Selected Region: EU - Release: Only Update Maps - Map Version: EU - 2024-02-19 - 1708360463 
[19-Feb-24 18:44:27] Install Mode: Auto-Detect (autoinstall) Forced: False 
[19-Feb-24 18:44:27] MY20 Protection: Auto-Detect 
[19-Feb-24 18:44:27] Formatting USB drive
[19-Feb-24 18:44:27] Re-creating partition table as MBR and formatting as ExFat on selected USB drive
[19-Feb-24 18:45:15] Checking Existing File: PU5T-14G386-BB_1690840002000.TAR.GZ 
[19-Feb-24 18:45:15] Validated: PU5T-14G386-BB_1690840002000.TAR.GZ (Skipping Download) 
[19-Feb-24 18:45:15] Checking Existing File: 1U5T-14G424-BM_1683133039000.TAR.GZ 
[19-Feb-24 18:45:15] Downloading: 1U5T-14G424-BM_1683133039000.TAR.GZ
[19-Feb-24 18:45:15] Validating: 1U5T-14G424-BM_1683133039000.TAR.GZ 
[19-Feb-24 18:45:15] Downloaded: 1U5T-14G424-BM_1683133039000.TAR.GZ 
[19-Feb-24 18:45:15] Checking Existing File: 1U5T-14G421-BAK_1682464992000.TAR.GZ 
[19-Feb-24 18:45:22] Validated: 1U5T-14G421-BAK_1682464992000.TAR.GZ (Skipping Download) 
[19-Feb-24 18:45:22] Checking Existing File: 1U5T-14G421-BBK_1682466740000.TAR.GZ 
[19-Feb-24 18:45:23] Validated: 1U5T-14G421-BBK_1682466740000.TAR.GZ (Skipping Download) 
[19-Feb-24 18:45:23] Checking Existing File: 1U5T-14G421-BDK_1682467734000.TAR.GZ 
[19-Feb-24 18:45:27] Validated: 1U5T-14G421-BDK_1682467734000.TAR.GZ (Skipping Download) 
[19-Feb-24 18:45:27] Checking Existing File: 1U5T-14G421-BEK_1682467790000.TAR.GZ 
[19-Feb-24 18:45:31] Validated: 1U5T-14G421-BEK_1682467790000.TAR.GZ (Skipping Download) 
[19-Feb-24 18:45:31] Checking Existing File: 1U5T-14G421-BFK_1682467908000.TAR.GZ 
[19-Feb-24 18:45:39] Validated: 1U5T-14G421-BFK_1682467908000.TAR.GZ (Skipping Download) 
[19-Feb-24 18:45:39] Checking Existing File: 1U5T-14G421-BGK_1682467948000.TAR.GZ 
[19-Feb-24 18:45:44] Validated: 1U5T-14G421-BGK_1682467948000.TAR.GZ (Skipping Download) 
[19-Feb-24 18:45:44] Checking Existing File: 1U5T-14G421-BHK_1682468092000.TAR.GZ 
[19-Feb-24 18:45:44] Validate: 1U5T-14G421-BHK_1682468092000.TAR.GZ (Failed!, Downloading)
[19-Feb-24 18:45:44] Downloading: 1U5T-14G421-BHK_1682468092000.TAR.GZ
[19-Feb-24 18:47:21] Validating: 1U5T-14G421-BHK_1682468092000.TAR.GZ 
[19-Feb-24 18:47:29] Downloaded: 1U5T-14G421-BHK_1682468092000.TAR.GZ 
[19-Feb-24 18:47:29] Checking Existing File: 4U5T-14G422-BAK_1682464728000.TAR.GZ 
[19-Feb-24 18:47:29] Downloading: 4U5T-14G422-BAK_1682464728000.TAR.GZ
[19-Feb-24 18:48:55] Validating: 4U5T-14G422-BAK_1682464728000.TAR.GZ 
[19-Feb-24 18:49:02] Downloaded: 4U5T-14G422-BAK_1682464728000.TAR.GZ 
[19-Feb-24 18:49:02] Checking Existing File: 4U5T-14G422-BCK_1682464838000.TAR.GZ 
[19-Feb-24 18:49:02] Downloading: 4U5T-14G422-BCK_1682464838000.TAR.GZ
[19-Feb-24 18:50:16] Validating: 4U5T-14G422-BCK_1682464838000.TAR.GZ 
[19-Feb-24 18:50:21] Downloaded: 4U5T-14G422-BCK_1682464838000.TAR.GZ 
[19-Feb-24 18:50:21] Preparing USB drive
[19-Feb-24 18:50:21] Checking Existing File: PU5T-14G386-BB_1690840002000.TAR.GZ 
[19-Feb-24 18:50:21] Copying: PU5T-14G386-BB_1690840002000.TAR.GZ 
[19-Feb-24 18:50:21] Validating: PU5T-14G386-BB_1690840002000.TAR.GZ 
[19-Feb-24 18:50:21] Copied: PU5T-14G386-BB_1690840002000.TAR.GZ 
[19-Feb-24 18:50:21] Checking Existing File: 1U5T-14G424-BM_1683133039000.TAR.GZ 
[19-Feb-24 18:50:21] Copying: 1U5T-14G424-BM_1683133039000.TAR.GZ 
[19-Feb-24 18:50:21] Validating: 1U5T-14G424-BM_1683133039000.TAR.GZ 
[19-Feb-24 18:50:21] Copied: 1U5T-14G424-BM_1683133039000.TAR.GZ 
[19-Feb-24 18:50:21] Checking Existing File: 1U5T-14G421-BAK_1682464992000.TAR.GZ 
[19-Feb-24 18:50:21] Copying: 1U5T-14G421-BAK_1682464992000.TAR.GZ 
[19-Feb-24 18:53:28] Validating: 1U5T-14G421-BAK_1682464992000.TAR.GZ 
[19-Feb-24 18:54:00] Copied: 1U5T-14G421-BAK_1682464992000.TAR.GZ 
[19-Feb-24 18:54:00] Checking Existing File: 1U5T-14G421-BBK_1682466740000.TAR.GZ 
[19-Feb-24 18:54:00] Copying: 1U5T-14G421-BBK_1682466740000.TAR.GZ 
[19-Feb-24 18:54:43] Validating: 1U5T-14G421-BBK_1682466740000.TAR.GZ 
[19-Feb-24 18:54:44] Copied: 1U5T-14G421-BBK_1682466740000.TAR.GZ 
[19-Feb-24 18:54:44] Checking Existing File: 1U5T-14G421-BDK_1682467734000.TAR.GZ 
[19-Feb-24 18:54:44] Copying: 1U5T-14G421-BDK_1682467734000.TAR.GZ 
[19-Feb-24 18:56:12] Validating: 1U5T-14G421-BDK_1682467734000.TAR.GZ 
[19-Feb-24 18:56:15] Copied: 1U5T-14G421-BDK_1682467734000.TAR.GZ 
[19-Feb-24 18:56:15] Checking Existing File: 1U5T-14G421-BEK_1682467790000.TAR.GZ 
[19-Feb-24 18:56:15] Copying: 1U5T-14G421-BEK_1682467790000.TAR.GZ 
[19-Feb-24 18:58:30] Validating: 1U5T-14G421-BEK_1682467790000.TAR.GZ 
[19-Feb-24 18:58:43] Copied: 1U5T-14G421-BEK_1682467790000.TAR.GZ 
[19-Feb-24 18:58:43] Checking Existing File: 1U5T-14G421-BFK_1682467908000.TAR.GZ 
[19-Feb-24 18:58:43] Copying: 1U5T-14G421-BFK_1682467908000.TAR.GZ 
[19-Feb-24 19:02:05] Validating: 1U5T-14G421-BFK_1682467908000.TAR.GZ 
[19-Feb-24 19:02:41] Copied: 1U5T-14G421-BFK_1682467908000.TAR.GZ 
[19-Feb-24 19:02:41] Checking Existing File: 1U5T-14G421-BGK_1682467948000.TAR.GZ 
[19-Feb-24 19:02:41] Copying: 1U5T-14G421-BGK_1682467948000.TAR.GZ 
[19-Feb-24 19:05:21] Validating: 1U5T-14G421-BGK_1682467948000.TAR.GZ 
[19-Feb-24 19:05:40] Copied: 1U5T-14G421-BGK_1682467948000.TAR.GZ 
[19-Feb-24 19:05:40] Checking Existing File: 1U5T-14G421-BHK_1682468092000.TAR.GZ 
[19-Feb-24 19:05:40] Copying: 1U5T-14G421-BHK_1682468092000.TAR.GZ 
[19-Feb-24 19:09:09] Validating: 1U5T-14G421-BHK_1682468092000.TAR.GZ 
[19-Feb-24 19:10:12] Copied: 1U5T-14G421-BHK_1682468092000.TAR.GZ 
[19-Feb-24 19:10:12] Checking Existing File: 4U5T-14G422-BAK_1682464728000.TAR.GZ 
[19-Feb-24 19:10:12] Copying: 4U5T-14G422-BAK_1682464728000.TAR.GZ 
[19-Feb-24 19:13:14] Validating: 4U5T-14G422-BAK_1682464728000.TAR.GZ 
[19-Feb-24 19:14:16] Copied: 4U5T-14G422-BAK_1682464728000.TAR.GZ 
[19-Feb-24 19:14:16] Checking Existing File: 4U5T-14G422-BCK_1682464838000.TAR.GZ 
[19-Feb-24 19:14:16] Copying: 4U5T-14G422-BCK_1682464838000.TAR.GZ 
[19-Feb-24 19:16:32] Validating: 4U5T-14G422-BCK_1682464838000.TAR.GZ 
[19-Feb-24 19:17:17] Copied: 4U5T-14G422-BCK_1682464838000.TAR.GZ 
[19-Feb-24 19:17:17] Generating Autoinstall.lst
[19-Feb-24 19:17:17] ALL FILES DOWNLOADED AND COPIED TO THE USB DRIVE SUCCESSFULLY!

SaNdMaN · 21 February 2024 19:48

The map installation was not really necessary, but since you have the space, it won’t hurt installing native NAV.

You will need to get that fixed, 1.1G may not be enough for the APIM to process upgrades.
Since you didn’t share the log, I do not know what packages are installed.
If a reformat fails, remove Gracenotes, install the small voice package and/or downgrade to make enough room to process update packages.

Again, it’s a shame you didn’t provide the interrogator log.
What you linked there is just the Sync3 version, nothing more.
If the APIM is from 2016, you can reformat it, which does not mean you should.

A quick search on that code returns it’s the screen digitizer, nothing more.

Not enough information, I do now know.

Correct, you can’t reformat MY20 hardware with the leaked reformat tool.

At this point, unless you can get some guarantee about the screen not being MY20, the safest way would be to jailbreak the unit. FMODS has a mod for cleaning up maps without a reformat.
They even released an universal reformat package that can reformat MY20 hardware.

And since you are going to try activating NAV, let me tell you that Cyanlabs does not support changing regions, but you will find this guide quite helpful → Tutorial: Current EU Maps Installation on US Imported Vehicles

insaneinsanovich · 21 February 2024 19:56

Here it is

Sync_WW7J3SN9_WF06XXGCC6GB27048.xml (10.6 KB)

Is there any other way to find the model of the display with missing SN sticker?
Let me guess, I need to disassemble the this cage?

Wait a sec, my APIM is not from European Region?

SaNdMaN · 21 February 2024 20:12

I’ve merged your consecutive messages, please use the edit button instead of posting multiple messages.

Thank you for the log.
In what country is the vehicle located?.
About the free space the unit has, that’s a bit odd.
There may be packages that are not currently listed due to the mem issue, maybe.
Try with a master reset to see if new packages are displayed.
Also, you have voice packages for ANZ as well, so the unit has a mixture of packages installed.

I do not know if the model is listed somewhere else, no.

Of course it’s not, I thought you already knew this:

Why would an EU APIM not have enough space to contain EU maps?. EU NAV APIMS are 64GB because they need that much storage for the maps, other NON-EU NAV APIMs are 32GB, like yours.

insaneinsanovich · 21 February 2024 20:27

Sorry for that. Noticed afterwards that you merged my messages.

In Moldova. Eastern Europe

Ahhh, now I understand. The European market was supplied only with 64GB NAV APIM version.
32GB NAV APIM was used in the rest of the world.
For the last few years I was driving with SYNC2 unit and never had a chance to road test a SYNC3, so my experience with it is only a week old) . Never heard about FMODS and CyanLabs prior to 1 week ago, but like I said, I’m tech savy cause I work in IT so I am a very quick learner. Thanks for the FMODS tip BTW. Their mods and apps look really amazing. Very tempted to jailbreak my unit)

Okay, that’s really strange. I think the seller didn’t either bother to reformat the unit before sending it to me. Most probably he just updated the SYNC to the latest available build. I’ll do another master reset and pull another interogator.log

SaNdMaN · 21 February 2024 20:36

Well, the APIM does not have that country configured: DE01/7D0-02-01 should be 4D44-xxxx-xxxx, which is not your case.

Exactly. You could however install a cutdown maps package, for the countries you are likely to visit.
But you won’t be able to fit all the EU maps, no.

You won’t have issues then, this stuff is pretty straight forward. Just do your research before doing some stuff and you should be fine. If you JB the unit you will be able to safely reformat it regardless of the screen’s model year.

As far the configuration goes, he didn’t even programmed it (other than disabling the NAV as you originally said) to your country. I’m not sure from where the unit came (the ANZ map is puzzling, ANZ contains Latin America, New Zealand, Australia…), but you could convert it with “ease”.

Share the new log once you have the chance to see if more packages are listed as installed.
Nevertheless, you can remove gracenotes and install the small voice package to make enough room for other upgrade/install process to run.

insaneinsanovich · 21 February 2024 21:00

Originally, the car is from Germany. I was analyzing exactly this entry a couple of minutes ago). I will change it to my region when I have some spare time. Just out of curiosity, does changing the region give any benefits?

I knew it would not fit everything. I just chose 3 regions that I use the most for troubleshooting GPS issue, but considering that the seller didn’t make a clean SYNC3 install, and stupid me tried to write my maps on top of the old stuff…well, it didn’t end well))))

Thanks for the awesome tip.

I will do it on the first ocassion.

Found the navigation removal script on fmods. It’s basic stuff really. Looks like Ford are mounting the maps like a filesystem/partition and changing all the permissions for navigation files. Such operations can be done only by the root user or with sudo rights. Their ‘mod tool’ basically executes all bash scripts (or lets call them mods) with sudo rights.
I even found an SSH app. You can login to the SYNC3 remotely using car wifi))) If you know what are you doing, you can do pretty cool stuff with the APIM.

SaNdMaN · 21 February 2024 21:13

It’s a requirement for NAV, yes.
Now, you can try testing the GPS without NAV as well.
You can go into the bezel diagnostics menus, there’s an option to see GPS signal status.

That’s correct, that’s how you can remove/delete packages from storage, since there’s no official tool to remove maps. That’s why a reformat is mandatory for changing regions, because you can’t remove older maps from the original region. Well, with JB you can remove them by running that script…

I’m sure you will have fun with it.

insaneinsanovich · 22 February 2024 14:22

Jailbreak installed successfully. Also applied the AC button inverse fix mod and cleaned in just 1 minute all old map and voice files.

Managed to install only CIS region NAV maps.

Here is the interogator.log after all this procedures.
Sync_WW7J3SN9_WF06XXGCC6GB27048.xml (10.6 KB)

As I suspected, there are some issues with GPS. From bezel diagnostics looks like it gets all the info by GPS antenna. The only data missing is UTC time and UTC date, hence my problems with the stupid clock.

I change AsBuild to my country, but the compass doesn’t work at all.
Also, when trying to reset clock by GPS it returns:

Here is my APIM AsBuild
WF06XXGCC6GB27048_APIM_initial.abt (399 Bytes)

Do you have any ideas, sensei?

F150Chief · 22 February 2024 17:14

You can see 10 satellites and have a fix time of 132 seconds, which is very long. Are you under a structure or wooded area? The accuracy is way off, should be about 2 meters or so. You might want to take a look at the GPS antenna for corrosion, given the age of the vehicle.

insaneinsanovich · 22 February 2024 17:35

NAV GPS antenna is brand new. It was part of the upgrade kit from Sync2 to Sync3.

Also my car stays in front of a 5 store apartment building under clear sky. There is a tree nearby but I dont think it could affect that much the GPS accuracy.

Found the Pinpoint test for GPS troubleshooting on your awesome community. I’ll look into it when I find some spare time and let you know about my findings.

bill32399 · 22 February 2024 17:50

I am betting here lies the problem. The guys that make these kits dont put the best antenna’s in. Just the cheapest.

insaneinsanovich · 22 February 2024 17:52

okay, do you have any aftermarket models in mind that are reliable?

bill32399 · 22 February 2024 17:56

Nope, I always just convert everything to OEM. I am sure someone on here might have some recommendations though.

insaneinsanovich · 22 February 2024 18:47

the same stupid antenna I have, is everywhere: aliexpress, amazon, ebay. Found only one interesting option:

F150Chief · 22 February 2024 20:01

That will work.

bill32399 · 22 February 2024 23:36

Sometimes adding the OEM antenna is as simple as swapping a cable like the one below. Other times it requires the antenna to be swapped in addition to the cable. So if you ever get bored you can always go the OEM route. Really depends on how involved with it you want to get.

teiksef · 2 March 2024 16:48

Here you have some summary information on installing EU maps on an US 32GB Sync3 unit (MY20), and adapting it to your country language (proven it is among Ford supported EU languages): https://www.fordescape.org/threads/how-to-change-sync3-my20-nav-us-pl-eu.123362/
Maybe that can be of any help for you or anyone having similar needs.

F150Chief · 2 March 2024 18:39

Good writeup, but you should give sources and credit to the original authors.

teiksef · 2 March 2024 19:02

The detailed description (post #4 there) links to all sources and authors: FMods, Syn3 Updater, particular mods. If there’s some way other way of crediting interested parties, let me know and I can add/fix it. I don’t want to claim to be an author of anything but the writeup (the writeup itself is what I found lacking when I started to play with it).