Galaxy / EU - Climate Domain weirdness after 23188

Ford SYNC 3 Support CyanLabs Update Support
, , , , ,
1

I used the Syn3 Updater to go from SYNC 2.5 to the latest 3.4 and read all the manuals on my Ford Galaxy 2015. Overall, the update went well and there’s no error, just weird behavior - front window heating does not switch on (button lights up but it does not defrost). Also, fan speed acts weird: switching back from “max” to “auto” keeps the fan at a very high level (and noise). No issues working with Forscan and I have taken a screenshot of the settings but am having issues interpreting the APIM database from https://cyanlabs.net/asbuilt-db/sync3-apim/ and understanding if there’s an issue and what I’d need to set to fix the problem.

Really appreciate feedback from experienced fellas here and - if you can make time - some context of what’s going on. Cheers!

SYNC Region: EU

Navigation Variant: Nav

Manufacturer Year: Pre MY20

Install Type: OEM

Old SYNC Version: 3.0.20204

New SYNC Version: 3.4.23188

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

Update Method: CyanLabs Manual Method

Galaxy APIM Orig
Galaxy APIM Orig588×536 9.77 KB

3

You may want to drop to 3.4.21265, its not unusual for 3.4.23188 to have issues with older non-Sync3.4 APIMS.

4

I considered that as a plan B as I believe people reported that APIM module configuration can fix such glitches, too. One I found is changing

7D0-04-01 0100 1B00
to
7D0-04-01 0100 0000

Which should change the communication with the climate domain back to what it should be. However, I was hoping someone could confirm this.

The front window heating seems to be due to battery level being down at 65% (I understand below 75% can lead to such issues). However, I’d take that glitch as solved for now and focus on fan speed and behavior.

Cheers

5

I downgraded to 21265 and also made he changes from 1B00 to 0000 - will report back if there’s anything worth reporting ;-).