Corrupted log file after updating (Sync 3.0)

Ford SYNC 3 Support
, , , , ,
1

I updated my maps today to F11 from the official Ford site in Germany (Sync 3.0.20204). The process went smoothly up until I wanted to upload the log file to Ford. The file is incomplete and strangely corrupted. I have in the meantime reproduced it twice by using the interrogator tool. No changes. To the Cyanlab tool it’s not readable. I would be happy to send it, if anyone would try to make sense of it. I haven’t found an online solution or even explanation, yet. Thanks for any ideas.

SYNC Region: EU

Navigation Variant: Nav

Manufacturer Year: Pre MY20

Install Type: OEM

Old SYNC Version: 3.0.20204

New SYNC Version: 3.0.20204

Do you have a error message, if so what is it?
No error message. The update of the maps went smoothly and was completed. I was told to remove my USB drive. When trying to upload the log file there’s the message that something went wrong and I should come back later. Looking at the log-file with an editor, the first part is obviously incomplete and messed up.

Update Method: Official Ford

2

Does it make any sense to use another version of the interrogator? I clearly operate Sync 3.0 and have used the AA version of the tool. Maybe I will try the AB version tomorrow anyway… Could the update to the F11 maps have changed the applicable tool version?

3

And here is the mutilated xml file:

…¹a hWiWhW d À %“A b b Á u t l o g g i n g u t i l i t Á y . I n t e r l o g _ u t i l Á i t y . l o g …þÐ iWiWiWdd À «! :slight_smile: :slight_smile: Á I n t e r r o g a t o r _ L o Á g . x m l sponse>
d2p1:IsConfigtrue</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didType=“Direct Configuraation DID DE03” didValue=“DE03”>
d2p1:Response01001a01020001</d2p1:Response>
d2p1:IsConfigtrue</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didType=“Direct Configuraation DID DE04” didValue=“DE04”>
d2p1:Response17e8179828be</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:Response15033300000000135600000430670069</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-HB5T-14G371-CA</d2p1:Response>
d2p1:IsConfigfalse</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didFormat=“ASCII” didType=“ECU Core Assembly Number” didValue=“F111” responseLength=“24”>
d2p1:ResponseHS7T-14G380-CB</d2p1:Response>
d2p1:IsConfigfalse</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didFormat=“ASCII” didType=“ECU Delivery Assembly Number” didValue=“F113” responseLength=“24”>
d2p1:ResponseJS7T-14G371-NED</d2p1:Response>
d2p1:IsConfigfalse</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didFormat=“ASCII” didType=“ECU Calibration Data #1 Number” didValue=“F124” responseLength=“24”>
d2p1:ResponseHB5T-14G375-FA</d2p1:Response>
d2p1:IsConfigfalse</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didFormat=“ASCII” didType=“Private Sub Node #1 Serial Number” didValue=“F141” responseLength=“16”>
d2p1:ResponseNX3900QD</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:ResponseHB5T-14G374-CA</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:Response58:7a:62:6c:6c:81</d2p1:Response>
d2p1:IsConfigfalse</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didFormat=“HEX” didType=“ECU MAC Address 2” didValue=“F1D1” responseLength=“6”>
d2p1:Response58:7a:62:6c:6c:82</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:AdditionalAttributes logGeneratedDateTime=“2023-08-02T00:27:17+00:00” RAM=“948527104” vmcuVersion=“Vector_VMCU_02.02.20”>
<d2p1:PartitionHealth type=”/fs/usb0/" total=“59G” available=“59G”/>
<d2p1:PartitionHealth type=“/fs/tmpfs/” total=“128M” available=“126M”/>
<d2p1:PartitionHealth type=“/fs/sd/MAP/” total=“1.1G” available=“6.2M”/>
<d2p1:PartitionHealth type=“/fs/sd/MAP/” total=“19G” available=“28M”/>
<d2p1:PartitionHealth type=“/fs/Nuance/” total=“18G” available=“48M”/>
<d2p1:PartitionHealth type=“/fs/Nuance/” total=“1.9G” available=“7.6M”/>
<d2p1:PartitionHealth type=“/fs/Nuance/grace” total=“1.0G” available=“6.1M”/>
<d2p1:PartitionHealth type=“/fs/rwdata/” total=“1024M” available=“730M”/>
<d2p1:PartitionHealth type=“/fs/mp/” total=“1024M” available=“40M”/>
<d2p1:PartitionHealth type=“/fs/images/” total=“55G” available=“13G”/>
d2p1:InstallationLog/
d2p1:SyncDataMIIEtAYJKoZIhvcNAQcDoIIEpTCCBKECAQAxggG4MIIBtAIBADCBmzCBhjEbMBkGA1UEChMSRm9yZCBNb3RvciBDb21wYW55MQswCQYDVQQGEwJVUzERMA8GA1UEBxMIRGVhcmJvcm4xHjAcBgkqhkiG9w0BCQEWD21nbXNlY0Bmb3JkLmNvbTEnMCUGA1UEAxMeU3luYyBNb2R1bGUgRW5jcnlwdGlvbiBHZW4zIEEyAhDfwyMpAoa+v0vYmqleqJR7MA0GCSqGSIb3DQEBAQUABIIBACD60T0ucOY7v8DNJYDmIqF11gZEABECfKX4i49IWoqiTIGWO80snxXswcSktROFOU1RuPEWKDEtvEtmq45gu6v4Iiw/EGThB0ERBdS68TSMZqDReoxgwdF5rXofNnx0d8X5b0uqhZLy2ltmzxyJyx4V75UPhsumYdviWp42TT5Xcf2RJD63hZ3rcXV31Jj2sbSQA6Utnb8KXONahd9vTI3+gVb8GYDho0JF5KtOWItYFBUkXZyPPvqZ+f0OCuycBoXlDziWGGrZbV6HAiIX6Vf5wO6pty+eBk0UZl4r0IDlmhiHjEFvceZYJE30xsUgr4B9D5z9gKCEQkOH6xuRAPUwggLeBgkqhkiG9w0BBwEwHQYJYIZIAWUDBAEqBBBsmgvr++8YfgM90ZTZGdXkgIICsEuWefCk7sMO8yb7us6CqTqrKHFUeufM0uwozuZPFwDp5a2baeKoR/ure43BZLCPIhqCSPWTofjsAIf/6CGjxpYTr46xJkMTqjMV5M6LfaIHtiC9K+a50SeI8QL/Vh83Gv/HvVje1WUwhocMG46bWZpIxR50TI6f0JfG0cm6/eNtgxS2hlIzHC3xZ++6Tssl0Hi3P2JxUMFmjRtqDCK/zwwJdopQr2dpDRUgaqRrVVI4CBDdJa/Um843+OgwvgibkSz0R2NOsIx6CIhzGqrYlIJsIvt877hATwfveYJbl2WvFW7jTePir/3o5plzIWgD7TCqKqYr38Lf2Mwht/HtggcEo5j29/WMJGOZd5mKwfr6fgjbO4BZAqnzkiniHUlb7DDcoyBF6/mc9Sf7PYmrdy3GTfMuo0ERLBkq793O+uLMTtmk8zQCjcMDzh0qmx831lwX+43UIaScTe5IXOmVnRuh+/yLgi4DsajUA+itSle0Hs5KJvqQtTU6S9PUTvm0y2tFVPhC0QBT/fYDbfmYG9zu+gFkJM1I6eE7vclpR/jKTOGUgO+DUlQJYyHdk3L/7x6xH4oklDLKcYuTgBS6oqxyTmuD/Ij4f3UXxfc+SDhK6lJcnATvKArc7fDVG08YLwo1v/GWbIYNrpHdDPQipRAMcyZE9KasCx8v7S+wO2Q0tE/qXvwDHPOxW026oeYlHyzt9pjdBQvoK3o0AbQ7Dd1GvK6uXHAq66OWZFoXNEjbYshtS3AIsi6a+RBd2O1occsQrI2BLDOCGSlb8jbv4jOa03fgfud3Xvvh7rAQ1jQrt8lTqB3HqkQspZuGzdFPtltBRztRo+LLkxcS2Un8gk2WYdn40yO3U5VHmOSg2I1PbX9uG2YuGsjMldgVTu8HatwPHykZZi4OSzhozd32g+4=</d2p1:SyncData>
</d2p1:AdditionalAttributes>
</p:Node>
</p:OTAModuleSnapShot>

4

Do you have the actual file instead of a copy/paste?.
By the way, there’s nothing we can do about it.
If for whatever reason the log is not properly formed, that’s the APIM’s fault.
Try a master reset, but that’s unlikely to fix anything.
Can Ford’s servers read that log?.