Not creating interrogator .xml file Syn3 Updater

Steps I did
1.) Used a new USB (2gb) drive
2.) Prepared USB Drive via Syn3 (current stable version) (Step 1)
3.) Inserted USB into USB port of truck
4.) Turned on ignition
5.) Received message “Installation Complete” (Step 2)
6.) Removed USB, turned off truck
7.) Plugged into Laptop to interrogate and looked for .xml file and none was on drive. (Step 3)
8.) Tried a few times


SYNC Region: North America & Canada

Navigation Variant: No

Old SYNC Version: 3.4.21265

New SYNC Version: 3.4.22020

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

Update Method: CyanLabs Syn3 Updater

Syn3 Updater Version: 2.10.8.0

Syn3 Updater Documentation Read: Yes

Syn3 Updater Log File

CYANLABS - SYN3 UPDATER - V2.10.8.0
Branch: Stable
Operating System: Microsoft Windows 11 Pro (2009)

PREVIOUS CONFIGURATION
Version: 3.4.21265
Region: NA
Navigation: False
Install Mode: Auto-Detect (autoinstall)
Install Mode Overridden: False
My20 Protection Enabled: Auto-Detect

DESTINATION DETAILS
Mode: Drive
Model: SanDisk Cruzer Glide USB Device
FileSystem: exFAT
Partition Type: MBR

AUTOINSTALL.LST
; CyanLabs Syn3Updater 2.10.8.0 Stable - Autoinstall Mode - Sync 3.4.22020 NA

[SYNCGen3.0_ALL_PRODUCT]
Item1 = APPS - 5U5T-14G381-EV_1644243443000.TAR.GZ
Open1 = SyncMyRide\5U5T-14G381-EV_1644243443000.TAR.GZ
Options = AutoInstall


FILES (1)
5U5T-14G381-EV_1644243443000.TAR.GZ (868.2MB)

LOG
[3/28/2022 14:06:43] Selected Region: NA - Release: Sync 3.4.22020 - Map Version: Non Nav APIM 
[3/28/2022 14:06:43] Install Mode: Auto-Detect (autoinstall) Forced: False 
[3/28/2022 14:06:43] MY20 Protection: Auto-Detect 
[3/28/2022 14:06:43] Formatting USB drive
[3/28/2022 14:06:43] Re-creating partition table as MBR and formatting as ExFat on selected USB drive
[3/28/2022 14:06:50] Checking Existing File: 5U5T-14G381-EV_1644243443000.TAR.GZ 
[3/28/2022 14:06:50] Downloading: 5U5T-14G381-EV_1644243443000.TAR.GZ
[3/28/2022 14:07:41] Validating: 5U5T-14G381-EV_1644243443000.TAR.GZ 
[3/28/2022 14:07:44] Downloaded: 5U5T-14G381-EV_1644243443000.TAR.GZ 
[3/28/2022 14:07:44] Preparing USB drive
[3/28/2022 14:07:44] Checking Existing File: 5U5T-14G381-EV_1644243443000.TAR.GZ 
[3/28/2022 14:07:44] Copying: 5U5T-14G381-EV_1644243443000.TAR.GZ 
[3/28/2022 14:09:19] Validating: 5U5T-14G381-EV_1644243443000.TAR.GZ 
[3/28/2022 14:09:44] Copied: 5U5T-14G381-EV_1644243443000.TAR.GZ 
[3/28/2022 14:09:44] Generating Autoinstall.lst
[3/28/2022 14:09:44] ALL FILES DOWNLOADED AND COPIED TO THE USB DRIVE SUCCESSFULLY!

That log is not for an interrogator log creation, but to upgrading Sync3 (only APPS).
Based on that, you didn’t create an interrogator log, thus not finding any XML file is expected.

Does the “Create Interrogator Log USB” under the under the Utility Tab format a USB to create the .xml file that is written to the USB after installation complete message or am I mistaken?

That’s what I’m having issue with. I created an USB to get the .xml file, but a .xml file was not written to the Interrogator USB I formatted via SYN3.

My USB after making an Interrogator USB

No XML file will be created during the USB creation, since there is nothing to interrogate at that point.

Once the USB is created, you need to use it on the car. It will then generate the XML file, since it will interrogate the APIM.

Understood
its this part It will then generate the XML file, since it will interrogate the APIM. that’s it’s not doing

My Steps
1.) Used a new USB (tried 2gb, 8gb, 32gb, 64gb) drive
2.) Prepared USB Drive via Syn3 Updater (current stable version) (Step 1)
3.) Inserted USB into USB port of truck
4.) Turned on ignition
5.) Received message “Installation Complete” (Step 2)
6.) Removed USB, turned off truck
7.) Plugged into Laptop to interrogate and looked for .xml file and none was on drive. (Step 3)
8.) Tried several times

Oh, I see. Ok, do this: recreate the USB, then post the log for its creation. Interrogator package is version dependant, make sure your current version is correctly configured in Syn3Updater.

For clarification, On the Home Tab populate all the fields. Do I need to select “start” or move onto the Utility tab and create the LOG USB?

I’m confused you have updated apps package, no where does it suggests you tried to create a interrogator USB

Not having issue with APPS updating… I’m having issue with the .xml file writing to the USB using the “Create Interrogator Log USB”… Step 1 (Prepare Drive), Step 2 (Install Drive in Car await “installation complete”) and Step 3 (Open Interrogator File). I noted all these steps in my list.

I don’t have the .xml on my APPS update USB either. That’s why I tried the “Create Interrogator Log USB” . I’m also assuming that the APPS doesn’t make the .xml file, because package GB5T-14386-ADxxx isn’t included on the APP download. That GB5T… is the instructions to tell it to interrogate and write to the USB.

I was just trying to see the information about my unit.

You need to make sure that your current version is set right.
The move into the Utilities Tab, select the drive and the prepare drive.

All of these things that we are discussing are well documented here → Explanation of each Syn3 Updater tab - Docs - CyanLabs Official Community

Also, if you create one again, do not start the vehicle with the USB connected.
Try turning the unit on, and once it’s fully initialized then connect the USB.

I read the Explanation of each Sync3 prior to posting. So I wouldn’t waste peoples time.

Thanks for help… I will try again tomorrow.

Don’t worry about it.

If for some reason your unit is not responsive for the interrogator log, then there’s something wrong with it.

Got the .xml (10kb), but it’s unreadable. Tried opening up in Excel and get "

an invalid character was found in text content Line 66, Position 28. d2p1:Response"

Does it open in notepad text editor?

<?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="2022-03-31" xsi:schemaLocation="urn:ford/Vehicle/Module/Information/v3.0 ModuleSnapshot.xsd">
  <p:VIN>1FTFW1EG6JFC18852</p:VIN>
  <p:ModuleName>ECU</p:ModuleName>
  <p:RequestRole>
    <d2p1:Role>CONSUMER</d2p1:Role>
    <d2p1:RoleSource>OTA</d2p1:RoleSource>
    <d2p1:RoleDesc>SYNCGEN3</d2p1:RoleDesc>
    <d2p1:RoleID>OTA</d2p1:RoleID>
  </p:RequestRole>
  <p:BroadcastDTCType/>
  <p:Node isFlashed="false" specificationCategory="GGDS">
    <d2p1:Address>7D0</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:Response>5U5T-14G381-EV</d2p1:Response>
            <d2p1:IsConfig>false</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didFormat="Packeted" didType="Embedded Consumer Applications Part Numbers 1" didValue="8060" responseLength="384">
            <d2p1:Response>355535542d3134473339312d435000000000000000000000345535542d3134473432332d434300000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000</d2p1:Response>
            <d2p1:IsConfig>false</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didFormat="Packeted" didType="Embedded Consumer Applications Part Numbers 1" didValue="8061" responseLength="384">
            <d2p1:Response>000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000</d2p1:Response>
            <d2p1:IsConfig>false</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didFormat="HEX" didType="ECU Checksum 1" didValue="D704" responseLength="4">
            <d2p1:Response>Blank</d2p1:Response>
            <d2p1:IsConfig>false</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didFormat="HEX" didType="ECU Checksum 2" didValue="D705" responseLength="4">
            <d2p1:Response>Blank</d2p1:Response>
            <d2p1:IsConfig>false</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didType="Direct Configuraation DID DE00" didValue="DE00">
            <d2p1:Response>Blank</d2p1:Response>
            <d2p1:IsConfig>true</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didType="Direct Configuraation DID DE01" didValue="DE01">
            <d2p1:Response>Blank</d2p1:Response>
            <d2p1:IsConfig>true</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didType="Direct Configuraation DID DE02" didValue="DE02">
            <d2p1:Response>Blank</d2p1:Response>
            <d2p1:IsConfig>true</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didType="Direct Configuraation DID DE03" didValue="DE03">
            <d2p1:Response>Blank</d2p1:Response>
            <d2p1:IsConfig>true</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didType="Direct Configuraation DID DE04" didValue="DE04">
            <d2p1:Response>Blank</d2p1:Response>
            <d2p1:IsConfig>true</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didType="Direct Configuraation DID DE05" didValue="DE05">
            <d2p1:Response>Blank</d2p1:Response>
            <d2p1:IsConfig>true</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didType="Direct Configuraation DID DE06" didValue="DE06">
            <d2p1:Response>Blank</d2p1:Response>
            <d2p1:IsConfig>true</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didFormat="ASCII" didType="On-line Diagnostic Database Reference Number" didValue="F110" responseLength="24">
            <d2p1:Response>
</d2p1:Response>
            <d2p1:IsConfig>false</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didFormat="ASCII" didType="ECU Core Assembly Number" didValue="F111" responseLength="24">
            <d2p1:Response>
</d2p1:Response>
            <d2p1:IsConfig>false</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didFormat="ASCII" didType="ECU Delivery Assembly Number" didValue="F113" responseLength="24">
            <d2p1:Response>
</d2p1:Response>
            <d2p1:IsConfig>false</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didFormat="ASCII" didType="ECU Calibration Data #1 Number" didValue="F124" responseLength="24">
            <d2p1:Response>
</d2p1:Response>
            <d2p1:IsConfig>false</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didFormat="ASCII" didType="Private Sub Node #1 Serial Number" didValue="F141" responseLength="16">
            <d2p1:Response>VX2604D8</d2p1:Response>
            <d2p1:IsConfig>false</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didFormat="State Encoded" didType="Software Download Specification Version" didValue="F162" responseLength="1">
            <d2p1:Response>00</d2p1:Response>
            <d2p1:IsConfig>false</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didFormat="State Encoded" didType="Diagnostic Specification Version" didValue="F163" responseLength="1">
            <d2p1:Response>00</d2p1:Response>
            <d2p1:IsConfig>false</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didFormat="ASCII" didType="Vehicle Manufacturer ECU Software Number" didValue="F188" responseLength="24">
            <d2p1:Response>
</d2p1:Response>
            <d2p1:IsConfig>false</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didFormat="ASCII" didType="ECU Serial Number" didValue="F18C" responseLength="16">
            <d2p1:Response>
</d2p1:Response>
            <d2p1:IsConfig>false</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didFormat="HEX" didType="ECU MAC Address 1" didValue="F1D0" responseLength="6">
            <d2p1:Response>90:70:65:64:09:5d</d2p1:Response>
            <d2p1:IsConfig>false</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didFormat="HEX" didType="ECU MAC Address 2" didValue="F1D1" responseLength="6">
            <d2p1:Response>90:70:65:64:09:5e</d2p1:Response>
            <d2p1:IsConfig>false</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="2022-03-31T07:35:55+00:00" RAM="338980864" vmcuVersion="Vector_VMCU_02.02.20">
      <d2p1:PartitionHealth type="/fs/Nuance/" total="465M" available="3.2M"/>
      <d2p1:PartitionHealth type="/fs/Nuance/grace" total="775M" available="5.8M"/>
      <d2p1:PartitionHealth type="/fs/rwdata/" total="1.2G" available="1000M"/>
      <d2p1:PartitionHealth type="/fs/rwdata/quip/" total="35M" available="35M"/>
      <d2p1:PartitionHealth type="/fs/rwdata/quip/" total="90M" available="89M"/>
      <d2p1:PartitionHealth type="/fs/mp/" total="1.4G" available="85M"/>
      <d2p1:PartitionHealth type="/fs/images/" total="3.0G" available="1.7G"/>
      <d2p1:InstallationLog/>
      <d2p1:SyncData>MIIEdAYJKoZIhvcNAQcDoIIEZTCCBGECAQAxggG4MIIBtAIBADCBmzCBhjEbMBkGA1UEChMSRm9yZCBNb3RvciBDb21wYW55MQswCQYDVQQGEwJVUzERMA8GA1UEBxMIRGVhcmJvcm4xHjAcBgkqhkiG9w0BCQEWD21nbXNlY0Bmb3JkLmNvbTEnMCUGA1UEAxMeU3luYyBNb2R1bGUgRW5jcnlwdGlvbiBHZW4zIEEyAhDfwyMpAoa+v0vYmqleqJR7MA0GCSqGSIb3DQEBAQUABIIBAFa+wGXv32ZY1CNbPdy3vmDk1XFj6dzrTNHUufJT5E31vjDsA3IkTvqoE+HYVMhrTR044CYrFTqNBie5wER5t6bhLXUH0MqvPqWu8+DDWZNhn8Zdp2Jwu9kGeb5cvnQ5segWxlS5t4Ud2AAR7oHnaha3AQlv+FSjip2wO8Wc82oL3L4ug6NRYy7WO6XOdmCMx3r3oszA6Y/PEMDtQaCUMMpW6o1e5Y1aQNYMyRY+lmMyry8iaTxb9bVT9YUvINLAqh9FkkjzXsAlFA4qBgnQefVZ+0Q+Gz8SKw5tyaQm7uNXGA2PSiJ/g70vZyScfDgMR1ttuJY+ZlBAeVh/HaFRuREwggKeBgkqhkiG9w0BBwEwHQYJYIZIAWUDBAEqBBDChcZ2YQEq2xWG2Gvx8YeGgIICcDHiUy6tvtit3FudnD/gC2Q06N+OEIDe9C5UNcWEwcfHIjYGDSJq7oxYatN/3i9OvwpCGDA2NmQvLFKqTTVdpdyG5d+gB5Q1RFoouKrBu4souVoT79DRRMpbJ9KKwhgjpd6MsSpA6tqJ+A9a8Hx1oBxaaGIctasL31QhqCeKAaXmvDSZrifj7hnO41XYoL1no9dVxspHGL4gSfblyaA0ZFB+epg+te+AVLUqx4mgbXiOuvX5GOkPbZUgz622Ebm3AcV56RTa426AqvVNsrGivrUHTQqWx1PJqrCykx2Qy9meMh4dBMuIoynr19h9HX+bjHCOO88HaPMlS0WQVYqv6jriGcXYOZfsg7MM7+2KUS1gUkFLwSBGFmLbISE6YnJb1aqlmXQTMyRIoNB5MeVGZ7xujWBX/CCwjQIBa/p1RSD6a/A0NTI+AEw8QH5xbrtbaZ03/6aCA2RNvUPxWMrUI4a4PZpnr4epbBEWNbX11SmyWVz9jFQUpPJxV36IIPlHe0VLOSMBeMcwBpZI9hnhDCmZaXMIEccSFGmciTMQRfit5ga5ryqAdwgqM7yVMUZg9Se00EEVnNSrzbD+FSmbpBSh81oaGNTnMzp4WkhExXH6ki4UOETOEMDu5txyrIttogSNVHlMJdTQmw0KK6kg84On08Qw44sGASb7LQnhHNLOZWAYKdXx/il/oAb/L3Lnpx53Hf8O1MwqT8MZEJDq5zpl9Si0advSWkd7Qnn5mW68mdZL6FprZ1LYMSNagYvWS28PVBuBNXGWLQFye5Lt6JI9ceE1MHjGUAowfob3LmU5wjIb/nFZIgkXpNSeRJxrmQ==</d2p1:SyncData>
    </d2p1:AdditionalAttributes>
  </p:Node>
</p:OTAModuleSnapShot>

It’s not supposed to be opened with excel.
You can open it with Syn3updater as described in the documentation, it will then be processed and “formatted” and will give you information in a simpler way.
You can also edit it with a text editor to see the raw data.

Understood, however SYN3Updater gave me an error about not being able to read it. So I wanted to see if it would open using Excel.

Do you still have the USB you created for that interrogator?
What package was used?
-AC or -AD?

-AD

Yes Still have the USB.
The package on the it is GB5T-14G386-AD
AD…