Wheel Ticks update issue(related with Sync3 GPS coordination)

I just updated Sync3 version from 3.4.21265 to 3.4.23188. (with the help of removing gracenote package)
But navigation via carplay problem is also occurred.
After googling related with Sync3 GPS problem, I found ASbuilt should be update correctly.

When the speed does not reach to 80km/h, GPS coordination is correct.
But over 80km/h, navigation does not find correct way.

My machine 2016 MKZ Hybrid and Forscan result is below.

7D0-07-01 0700 3300 0019
7D0-07-02 0000 171C 0013
7D0-07-03 0056 566D 00FA
7D0-07-04 6A4C

I think Wheel Ticks to Revolution(7D0-07-03) and Tire Circumference value should be update.
Would you guide to me the correct value ?

SYNC Region: NA

Navigation Variant: Non Nav

Manufacturer Year: Unknown

Install Type: Replica

Old SYNC Version: 3.4.21265

New SYNC Version: 3.4.23188

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

Update Method: CyanLabs Syn3 Updater

Syn3 Updater Version: 2.12.5

Syn3 Updater Documentation Read: yes

Syn3 Updater Log File

Branch: Stable
Operating System: Microsoft Windows 10 Enterprise (1709)

Version: 3.4.21265
Region: CN
Navigation: False
Install Mode: Auto-Detect (autoinstall)
Install Mode Overridden: False
My20 Protection Enabled: Disabled / Not MY20

Mode: Drive
Model: USB Device
Size: 7.5GB
FileSystem: exFAT
Partition Type: MBR

; CyanLabs Syn3Updater Stable - Autoinstall Mode - Sync 3.4.23188 NA

Item1 = RWDataCleaner TOOL - PU5T-14G386-BB_1690840002000.TAR.GZ
Open1= SyncMyRide\PU5T-14G386-BB_1690840002000.TAR.GZ
Item2 = VOICE - 5U5T-14G391-CS_1660783942000.TAR.GZ
Open2 = SyncMyRide\5U5T-14G391-CS_1660783942000.TAR.GZ
Item3 = APPS - NU5T-14G381-AD_1689364279000.TAR.GZ
Open3 = SyncMyRide\NU5T-14G381-AD_1689364279000.TAR.GZ
Options = AutoInstall

PU5T-14G386-BB_1690840002000.TAR.GZ (3.2KB)
5U5T-14G391-CS_1660783942000.TAR.GZ (385.5MB)
NU5T-14G381-AD_1689364279000.TAR.GZ (869.8MB)

[2024-06-02 오후 7:53:04] Selected Region: NA - Release: Sync 3.4.23188 - Map Version: Non Nav APIM 
[2024-06-02 오후 7:53:04] Install Mode: Auto-Detect (autoinstall) Forced: False 
[2024-06-02 오후 7:53:04] MY20 Protection: Disabled / Not MY20 
[2024-06-02 오후 7:53:04] Formatting USB drive
[2024-06-02 오후 7:53:04] Re-creating partition table as MBR and formatting as ExFat on selected USB drive
[2024-06-02 오후 7:53:13] Checking Existing File: PU5T-14G386-BB_1690840002000.TAR.GZ 
[2024-06-02 오후 7:53:13] Validated: PU5T-14G386-BB_1690840002000.TAR.GZ (Skipping Download) 
[2024-06-02 오후 7:53:13] Checking Existing File: 5U5T-14G391-CS_1660783942000.TAR.GZ 
[2024-06-02 오후 7:53:15] Validated: 5U5T-14G391-CS_1660783942000.TAR.GZ (Skipping Download) 
[2024-06-02 오후 7:53:15] Checking Existing File: NU5T-14G381-AD_1689364279000.TAR.GZ 
[2024-06-02 오후 7:53:17] Validated: NU5T-14G381-AD_1689364279000.TAR.GZ (Skipping Download) 
[2024-06-02 오후 7:53:17] Preparing USB drive
[2024-06-02 오후 7:53:17] Checking Existing File: PU5T-14G386-BB_1690840002000.TAR.GZ 
[2024-06-02 오후 7:53:17] Copying: PU5T-14G386-BB_1690840002000.TAR.GZ 
[2024-06-02 오후 7:53:17] Validating: PU5T-14G386-BB_1690840002000.TAR.GZ 
[2024-06-02 오후 7:53:17] Copied: PU5T-14G386-BB_1690840002000.TAR.GZ 
[2024-06-02 오후 7:53:17] Checking Existing File: 5U5T-14G391-CS_1660783942000.TAR.GZ 
[2024-06-02 오후 7:53:17] Copying: 5U5T-14G391-CS_1660783942000.TAR.GZ 
[2024-06-02 오후 7:54:46] Validating: 5U5T-14G391-CS_1660783942000.TAR.GZ 
[2024-06-02 오후 7:54:47] Copied: 5U5T-14G391-CS_1660783942000.TAR.GZ 
[2024-06-02 오후 7:54:47] Checking Existing File: NU5T-14G381-AD_1689364279000.TAR.GZ 
[2024-06-02 오후 7:54:47] Copying: NU5T-14G381-AD_1689364279000.TAR.GZ 
[2024-06-02 오후 7:58:11] Validating: NU5T-14G381-AD_1689364279000.TAR.GZ 
[2024-06-02 오후 7:58:13] Copied: NU5T-14G381-AD_1689364279000.TAR.GZ 
[2024-06-02 오후 7:58:13] Generating Autoinstall.lst

Best to find the VIN of a 2017 that had SYNC 3 with nav. Run the VIN in the Ford AB database and use the setting from that.

Did you do a Master Reset after installation?

Yes, after installation I did master reset.

I wonder why the asbuilt shows different result.
According to the database, DE06/070-07 section consist of 3 hex code(xxxx-xxxx-xxxx).

Forscan result is 7D0-07-03 0056 566D 00FA, then Wheel Ticks to Revolution(Front/Rear) is 56(hex, dec 86) and Tire Corcumfers 6D(hex, dex 109).
But, Bezel Diagnostic APIM configuration shows different value.
(Wheel Ticks to Revolution Front: Max value violated)
(Wheel Ticks to Revolution Rear: 41.000000
(Tire Circumference: 100.000000 cm)
(Distance from IP to rear axle: 100.000000 cm)

How can I adjust this value correctly ?

Do not go off Bezel Diagnostics. It is not a true representation of the values. Trust Forscan on these.

You might try using the non AB mode that is under the AB mode in Forscan. It is must more user friendly.

Carplay doesn’t use ANY data from the vehicle with the exception of GPS coordinates.
The wheel tick etc doesn’t matter, you’ve got an app problem on the phone.

This is true with the exception it uses speed input from the vehicle also. 13 min mark will tell you all about how it uses a couple sensors in the car including the wheel tick.

Developing CarPlay Systems, Part 1 - WWDC16 - Videos - Apple Developer

It depends on the level of integration the vehicle manufacturer allows.

As an example BMW went down the full integration path, others did not.
Friend of mine has a 2022 Chevy and it didn’t use the vehicle GPS, he has to put his iPhone on his dash in order for NAV to work right. Last week it had him 3/4 of a mile from where he actually was when he had the phone in the cup holder.

Its not just CP that is limited by what the manufacturer allows, Ford always uses Google Maps if you use AA even though the default map app is set to something else like Sygic or Here. Use Google Maps and the turn by turn in the cluster works, use something else and it doesn’t.

With the help of member’s reply, I expect this problem will be solved.

Before update, 2D accuracy shows up to 1480 (meters) when the speed exceed 80km/h.

I just update two values via Forscan tool.
7D0-03-01 0555 xxxxx xxxx (update to ‘0’ Sync3, previous 1555)
7D0-07-03 0056 5671 00FA (update to ‘71’, previous 6D)

After update asbuilt and reboot APIM, 2D accuracy does not settle down immediately.
But sometimes later, 2D accuracy does not exceed 20 (meters) regardless of speed.
I’m not sure yet whether this problem has been solved or not.

Anyway, Thank you so much everybody.

Where did you get the originally loaded AB from?
Since this is a 2016 MKZ it would have had to started life with MFT, not Sync3.
Unless the unit came out of a 2017 Fusion Hybrid/Energi (those use MKZ firmware modules for the PDM/DDM/DSM etc) or an MKZ Hybrid you wouldn’t have been able to just drop it in.

Thank you for your mention.

I am a beginner trying out using Forscan and ASbuilt data update.
I just changed APIM(bought from aliexpress) and connect Forscan and update just 2 value 070-03-01 and 070-07-03.

Until now, all the control works properly. Is it harmful ?

This gets into what market the AB was for.
Wheel ticks and the like can throw off the reverse camera lines.

Here’s the APIM AB that I use for a base when I do a NA market Fusion MFT to Sync3 conversion, it has NAV enabled so you’ll need to disable that.

And here’s also the AB for a NA market 2017 MKZ.
APIM 09072020.abt (495 Bytes)

3LN6L5FC1HR612957.ab (35.9 KB)

APIM AB that you upload is so helpful to me.
(Thank you so much warlock12118.)
Compair with mine(2016 MKZ), I can understand how AB works.

After update some value, GPS is working properly when I use carplay navigation.
2D accuracy value does not exceed 15 meters regardless of speed.

I does not update 7D0-03-01 GPS Mount type value.
If 2D accuracy value exceed 20 meters, I’ll modify this value to 1(IP Mount, no heated windshield. current value is 5(reserved)).

Finally, I can use carplay navigation without wrong GPS position.
Thank you so much.

5 is an illegal value, hence the reserved, keep in mind that Sync2/MFT & Sync4 values do not necessarily correlate to valid Sync3 values so be careful what you use since blind Googling can yield garbage results.
Just because you can set a value doesn’t mean its going to work and non-supported public values can also be deprecated from one build to another.

Use the allowed values these are still used world wide:
7D0-03-01: x_xx-xxxx-xxxx
0=Roof Mount (UK Default)
1=Instrument Panel (IP) Mount (Non Heated Windscreen)
2=Instrument Panel (IP) Mount (Heated Windscreen)
3=Windshield Mount (Non-Heated Windscreen)
4=Windshield Mount (Heated Windscreen)