Chimes from ipc instead speakers

Hi everyone. I have a problem with my Mondeo Mk5. The parking sensor chimes are coming from the dashboard buzzer instead of the speakers. I’ve upgraded Sync2 to Sync3, but after the upgrade, everything worked fine for a while. I’ve loaded the original configuration into the IPC and ACM, reset the modules, and Forscan shows no errors. I even replaced the battery with a new one. Today, I changed the chimes to the dashboard buzzer in the IPC configuration. I locked the car, and after 10 minutes, I changed the option back to “audio only.” I locked the car for 10 minutes, and after restarting, the sensors returned to the speakers. Unfortunately, after a few hours, the chimes are back in the dashboard again. How can I fix this? Its possible problem in apim configuration? I’ve checked almost all the options and I have no idea what could be causing this problem.

Can you post the Asbuilt from the APIM and the IPC?

Of course, I also upload acm asbuilt.

WF0DXXWPCHFK26378_IPC_20250920_203826 ipc zs.abt (336 Bytes)

WF0DXXWPCHFK26378_APIM_20250926_222837.abt (495 Bytes)

This is usually a communication issue between the APIM and ACM on boot up. Look in FORScan at the APIM and ACM for DTC’s and see what they say. There is a setting in the ACM for Sync APIM generation. Make sure that is selected as Gen 2.

In ACM I have apim gen 2 set, unless there is another way to set it, but I haven’t found such an option

1 Like

What about DTC’s?
If you have FORScan, You can force reset te modules, which is always a good thing to do when any change is made to a module.

Forscan shows no errors. After each coding, I reset the ACM, IPC, and APIM modules. Recently, after the reset, I also leave the car locked overnight.

Have you modified the audio system?

What year is the Mondeo?

The audio is standard, nothing has been changed except sync. The car is from 2015.

Check the IPC with ForScan.

What is 720-01-01 set to? xxxx xxx4 xxxx sends the chime to the ACM, 0 uses the IPC speaker.

in 720-01-01 xxxx xxx4 xxxx I have it set to 5, but that’s because my instrument cluster is the visteon l3 version

Actually its because your unit has City Safety Enabled, that’s the difference between having a 4 and a 5.

Location

720-01-01: xxxx-xxx*-xxxx

Values

0=CCDCF Disabled, CG Cluster only, CS Disabled
1=CCDCF Disabled, CG Cluster only, CS Enabled
2=CCDCF Disabled, CG Audio, Dual, CS Disabled
3=CCDCF Disabled, CG Audio, Dual, CS Enabled
4=CCDCF Disabled, CG Audio, Single, CS Disabled
5=CCDCF Disabled, CG Audio, Single, CS Enabled
6=CCDCF Disabled, CG Not Used, CS Disabled
7=CCDCF Disabled, CG Not Used, CS Enabled
8=CCDCF Enabled, CG Cluster only, CS Disabled
9=CCDCF Enabled, CG Cluster only, CS Enabled
A=CCDCF Enabled, CG Audio, Dual, CS Disabled
B=CCDCF Enabled, CG Audio, Dual, CS Enabled
C=CCDCF Enabled, CG Audio, Single, CS Disabled
D=CCDCF Enabled, CG Audio, Single, CS Enabled
E=CCDCF Enabled, CG Not Used, CS Disabled
F=CCDCF Enabled, CG Not Used, CS Enabled

Either setting will work for the Chimes…when did you last replace your battery?

I replaced the battery three weeks ago. I thought it might be the battery’s fault. The BMS shows about 88% battery efficiency. Of course, I reset the BMS after replacing it.

1 Like

Did this start to happen before or after the battery replacement?

There are various differences in your Sync 3 asbuilt that do not align with your previous Sync 2 configuration concerning C1CMA and CGEA 1.3 configurations. The Sync 3 asbuilt you have installed will need to be changed…I’ll post a file for you to try in a bit.

The problem existed before I replaced the battery. The strangest thing is that the ACM has the factory AS-Built, and the IPC has the same settings in the sound lines. I also checked this against the data on the Motorcraft AS-Built website. Is it possible that the apim configuration is causing such confusion?

1 Like

Absolutely.

Do you have a KEY start or PUSH BUTTON?

I have a button

This file has the first 2 lines (7D0-01-01) changed to better reflect the data from Sync 2 that is still applicable.

WF0DXXWPCHFK26378_APIM.abt (495 Bytes)

When you load this, FORScan will ask you about the checksum bits. Have FORScan write those automatically. You should reset the APIM afterwards.