Sync3 Interrogator Log is not readable by Syn3 Updater

Hi All,

I’ve created an interrogator log into an USB drive but the XML generate will cause an error when read with Syn3 Updater.

The only information that I get out of it is the following:

Version JR3T-14G381-AX
APIM Model: HB5T-14G371-FFB

I’ve recently installed version 3.0.20204 upgrading from 2.3.17109 on a Ford Kuga 2018 model. Now I wanted to understand if I can upgrade to the latest Sync version (3.4.x) but I’m not sure if this is allowed for my APIM model?

Is there a way to find out about this?


SYNC Region: EU

Navigation Variant: Nav

Manufacturer Year: Pre MY20

Install Type: OEM

Old SYNC Version: 2.3.17109

New SYNC Version: 3.0.20204

Do you have a error message, if so what is it?
The interrogator log cannot be read.

Update Method: Official Ford


Our records show that APIM model HB5T-14G371-FFB is a 32GB NAV APIM, so no issues about storage there.

Also, that APIM should not be MY20, so you should be fine.
I’m using “should” since I’m saying this based on the APIM’s model , which is an H series APIM that should not be MY20.
The same applied to the J series, until Ford started pushing out J series APIMs with MY20 components…

We have not seen any issues with H series so far , so if your unit was never serviced then it’s ok.

Thanks for your reply.

So with the assumption that MY20 is not there do you think I can try to update to the latest version?
Will the upgrade process be able to auto determine if it can continue before reformatting the device etc?

Yes, assuming your unit is not MY20, it’s safe to proceeded.
No, the process won’t validate anything and will try to upgrade the system.

On a side note, Syn3Updater’s validation is based on the APIM model. It cannot read the manufacturer date.
Based on the H series APIM, it would flag the APIM as not-MY20, as I did.

But as said before, there are gray areas.

Thanks again.

Is there a way however to generate a log that is correctly parsed by Syn3Updater to remove any doubts on the Hardware I own? Before continuing I mean?

You are not following me…
It does not matter, the information you provided (APIM model) is the information Syn3Updater would use for flagging a MY20 model, and in your case, would not flag it as MY20.

So if you were to use a different interrogator log version to produce a valid log, Syn3Updater would say it’s not MY20.

If you want to be 100% sure, you need to gain physical access to the unit and check the APIM and screen manufacture date.


sorry I don’t understand.
What is the reason that Syn3updated is not able to read a log file generated with interrogator?

The info regarding the APIM model is read from that log file right?

Actually please ignore the last message…I ran again the interrogator log and now Syn3updater correctly parsed the log file.

Here is the output:

Version JR3T-14G381-AX
APIM Model: HB5T-14G371-FFB
APIM Type: Navigation
APIM Size: 64GB
APIM Free Space: 20G
04/01/2023 15:52:34 +00:00

Partition Type = Free / Total
/fs/usb0/ = 965M / 966M
/fs/tmpfs/ = 127M / 128M
/fs/sd/MAP/ = 4.5M / 1.5G
/fs/sd/MAP/ = 79M / 14G
/fs/Nuance/ = 843M / 15G
/fs/Nuance/ = 7.6M / 1.9G
/fs/Nuance/grace = 6.1M / 1.0G
/fs/rwdata/ = 730M / 1024M
/fs/mp/ = 40M / 1024M
/fs/images/ = 20G / 55G

APIM AsBuilt
DE00: 0B6845929002BC570002
DE01: 535001044002480000000005
DE02: 0300010000
DE03: 01001C01250001
DE04: 18061810295F
DE05: 80
DE06: 17003B0000000000FA00000430750057

Do you think I can proceed with the upgrade to 3.4 safely?

I will take notice of the 64gb instead of 32gb for APIM HB5T-14G371-FFB.

I have answered that question multiple times already.

This topic was automatically closed 4 days after the last reply. New replies are no longer allowed.