I want to install Sync 3.4, but I have problems.
I’ll write everything from the beginning, all the actions, mistakes.
I have a Ford Escape USA 2017 Titanium.
APIM - Additional protocol interface module:
Part Number: HB5T-14G371-CCA
Calibration Level: HB5T-14G371-CCG (last known: HB5T-14G371-CGF)
Strategy: GB5T-14G374-CB
Calibration: GB5T-14G375-CA
Sync 3.0.16280.
Block settings in APIM (AS Build):
;Block 1
7D0G1G1AB2845038074
7D0G1G202AA15000AA5
;Block 2
7D0G2G15253010440C4
7D0G2G202401000002D
7D0G2G30005E1
;Block 3
7D0G3G10000010200DE
;Block 4
7D0G4G10100060108EC
7D0G4G20001DE
;Block 5
7D0G5G118061810294C
7D0G5G25F3D
;Block 6
7D0G6G1805E
;Block 7
7D0G7G116043300002C
7D0G7G2000000FA00DA
7D0G7G3000430700085
7D0G7G45739x
Sync poll log by GB5T-14G386-AC utility:
d2p1:DLCName=“SAE J1962” d2p1:Pins=“6,14” />
<d2p1:AdditionalAttributes logGeneratedDateTime=“2022-06-02T21:18:24+00:00” RAM=“1109291008” vmcuVersion=“Vector_VMCU_02.02.20”>
<d2p1:PartitionHealth type=“/dev/hd0t180” total=“9396216832” available=“54710240” />
<d2p1:PartitionHealth type=“/dev/hd0t181” total=“686877696” available=“2097120” />
<d2p1:PartitionHealth type=“/dev/hd0t177” total=“136776704” available=“2097152” />
<d2p1:InstallationLog />
Actions:
-
Unsuccessful attempt to flash APIM calibrations to My20+: Sync’a corruption of the Chinese ELM.
Experience has shown that the purchased Chinese ELM 327 (USB connector, with HS / MS CAN switch, using PIC18F25K80 and FT232RL chips, Kingbolen manufacturer) works well for changing the module settings. Sufficient speed and absence of errors on the CAN bus are required to flash the modules. Various driver settings, settings in Forscan did not give sufficient speed for flashing (maximum speed 38400bps, minimum delay 11ms, CAN Error increased after unsuccessful firmware from 0% to 16%, and there is still one unknown command, which is 0.1% ). A bunch of warnings, the probability of getting a brick is more than 50% with firmware, it did not stop me. As a result - a brick, ordering the recommended cable, while waiting for delivery - trips with a black screen in silence (so-so pleasure). -
Successful flashing of APIM calibrations up to My20+ with the recommended Forscan cable.
A very detailed article on firmware Firmware APIM.
Firmware:
APIM - Additional Protocol Interface Module
Part Number: HB5T-14G371-CCA
Calibration level: HB5T-14G371-CCA
Strategy: 1U5T-14G374-EM
Calibration: 1U5T-14G375-FAx
Block settings in APIM (AS Build): block 2 settings changed, blocks 8 and 9 added:
;Block 1
7D0G1G1AB2845038074
7D0G1G202AA15000AA5
;Block 2
7D0G2G15253010440C4
7D0G2G20240900000AD
7D0G2G30005E1
;Block 3
7D0G3G10000010200DE
;Block 4
7D0G4G10100060108EC
7D0G4G20001DE
;Block 5
7D0G5G118061810294C
7D0G5G25F3D
;Block 6
7D0G6G1805E
;Block 7
7D0G7G116043300002C
7D0G7G2000000FA00DA
7D0G7G3000430700085
7D0G7G45739
;Block 8
7D0G8G10000000000E0
7D0G8G20000000010F1
;Block 9
7D0G9G10000000000E1
7D0G9G20000000000E2
7D0G9G30000000000E3
7D0G9G40000000000E4x
Comments:
Forscan recommended vLinker FS cable: 300000bps, 3ms, no errors.
After the firmware, errors appeared:
- Standard:
APIM: Code: U2100 - Primary configuration not configured
APIM: Code: U3000 - Control Module - Non-standard:
IPC: Code: U0558 - Invalid data received from front control/display interface module.
Generally stopped turning off Sync.x
- Changing block 6 settings in APIM (AS Build):
Constantly working Sync obliged to immediately take measures to eliminate this shortcoming:
- a solution was found on the Internet with the replacement of a byte in Apim (As Built): Block 6: 7D0G6G1805E with 7D0G6G1815E.
- Changing block 2 settings in APIM (AS Build):
During the operation of the car and the search for a solution to upgrade Sync 3.0 to 3.4 on a strange APIM, another problem appeared.
Another Sync poll log by the GB5T-14G386-AC utility - nothing has changed.
Issues, possibly unrelated to APIM, prompted me to continue tweaking it:
- the car stopped opening when you put your hand to the door handles with sensors, on the contrary, it began to close by sound (it opened before).
- when pulling the handle once - no reaction (earlier the car opened, in the sense that all the doors were unlocked)
- Intermittent IPC Error (Code: U0558) - Invalid data received from Front Control/Display Interface Module.
It was decided to write to APIM the old values of block 2, which changed after flashing to My20:
Changed value in Apim (As Built) :Block 2: 7D0G2G20240900000AD to 7D0G2G202401000002D.
As a result, even more problems appeared: - Sync’s language has changed to English without the possibility of choosing Russian,
- instead of navigation, a compass was displayed.
Returning block 2 values to Apim, resetting Apim and Sync does not give any results, which is very strange, because. in the APIM settings: COUNTRY CODE = RS, it’s not clear what happened in navigation.
All proceedings take a lot of time, and when you get unexpected results, you fall into a stupor.
I already want to reformat Sync to 3.4 in order to avoid the problems received, but I feel that I have misunderstood the file system and will break sync.
SYNC Region: EU
Navigation Variant: Nav
Manufacturer Year: Pre MY20
Install Type: OEM
Old SYNC Version: 3.0.16280
New SYNC Version: 3.4.22251
Do you have a error message, if so what is it?
Sync poll log by GB5T-14G386-AC utility:
d2p1:DLCName=“SAE J1962” d2p1:Pins=“6,14” />
- <d2p1:AdditionalAttributes logGeneratedDateTime=“2022-06-02T21:18:24+00:00” RAM=“1109291008” vmcuVersion=“Vector_VMCU_02.02.20”>
<d2p1:PartitionHealth type=“/dev/hd0t180” total=“9396216832” available=“54710240” />
<d2p1:PartitionHealth type=“/dev/hd0t181” total=“686877696” available=“2097120” />
<d2p1:PartitionHealth type=“/dev/hd0t177” total=“136776704” available=“2097152” />
<d2p1:InstallationLog />
Update Method: CyanLabs Manual Method