When you say FCIM you mean the button panel (EFP)? Not the screen?
You need to scan the vehicle CANBUS without using a profile.
Ok hoping to get some help from people more knowledgeable then me in this areaā¦ I have a 2022 Maverick that I am attempting a Sync 4 Swap into. I got Sync 4 to boot but it refuses to see/communicate with the ACM. I either get audio off with no response to turn it on, or if I turn the ACM on through the instrument cluster, I get a constant loading message on the APIM. I have no external temp reading, and for some reason the APIM likes to reboot every 5 min or so (my guess is due to incorrect config?). I have tried to go through the sync 4 ABD database and edit the first line in the APIM with no success. The most I get to change is the clock going to 12:00 or displaying the correct time. Anyone got any ideas?
Oh and the rear camera does not workā¦ Just gives a blue screen when put into reverseā¦
Solved the rear camera issue. Loose wire in the APIM connector. Still no luck communicating with the ACM.
What is the trim level of your 2022 Maverick? XL and XLT models are not equipped with Sync 3, so essentially that would be Sync 2.5. If this is the case, you will need a compatible ACM.
So I am currently attempting to use a 2020 Escape ACM. It has As Built entries down to 727-08-06 which seems to be rare for Ford ACMs. Most ACMs I have pulled As Built for end at 727-04-08 including all variants of the Maverick with Sync 3. I programmed the 2020 escape ACM with ABD from a 21 Bronco and it made the ACM happy in the vehicle (communicates with the vehicle, can be controlled from the cluster, door chimes pass through speakers, etcā¦) but flashing the APIM with the ABD from that very same Bronco results in what I described above.
What is the trim level of your 2022 Maverick?
Asbuilt DB can be found here: AsBuilt Databases - CyanLabs
Most ACMās since 2015 go to 727-08-xx. This is the extension for the presets. The new ACMās for the 2021 Sync 4 vehicles go to 727-24-xx.
|727-05-01|xxxx|xxxx|xxxx|AM Presets|
|727-05-02|xxxx|xxxx|xxxx||
|727-06-01|xxxx|xxxx|xxxx|FM Presets|
|727-06-02|xxxx|xxxx|xxxx||
|727-06-03|xxxx|xxxx|xxxx||
|727-06-04|xxxx|xxxx|xxxx||
|727-07-01|xxxx|xxxx|xxxx||
|727-07-02|xxxx|xxxx|xxxx||
|727-07-03|xxxx|xxxx|xxxx||
|727-07-04|xxxx|xxxx|xxxx||
|727-08-01|xxxx|xxxx|xxxx|Sirius Presets|
|727-08-02|xxxx|xxxx|xxxx||
|727-08-03|xxxx|xxxx|xxxx||
|727-08-04|xxxx|xxxx|xxxx||
|727-08-05|xxxx|xxxx|xxxx||
|727-08-06|xxxx|xxxx|xxxx||
Most likely the Bronco asbuilt would not be completely compatible with a Maverick which is not produced with Sync 4. Mavericks are designed for Sync 3 or 2.5. If you have a Sync 2.5 Maverick, you will most likely need wiring adjustments/additions to make Sync 4 work.
As far as the Sync 4 unit rebooting every 5 minutes, this is due to CANBUS messaging you may be missing on the Maverick. It could be an asbuilt adjustment, but if the messages are actually missing, you would need to find out how to simulate the messages to keep the unit turned on.
Thatās correct, although mine shows up in ForScan as FCIM when it shows up (Front Control Interface Module Iād assume is the acronym). Iāll try a completely fresh instance of ForScan with no profiles and see what happens. ForScan should still be able to see it with pins 53/54 removed from the APIM harness?
Yes. 53/54 is HS1-CAN, which is not used for Sync 4, as it communicates on HS3-CAN for vehicle systems.
Maverick XL here. My vehicle did not even have an APIM connector from the factory. Looks like the APIM is integrated into the ACM from the factory.
I have made a passthrough harness that converts the XL wiring to that of a Lariat with sync 3 in terms of the ACM side and APIM side. I have triple check the wiring against Fords wiring diagrams so I am confident that the wiring is not an issue. I did however not populate pins 53/54 and pins 41/42 for HS CAN and HS4 CAN as the F150 Sync 4 pinout do not have these populated.
Here is the wiring for all of the versions of Sync, except Sync 2.5 which is integrated to the ACM.
APIM Connector Versions.pdf (201.5 KB)
Check that you have the DRDL and all of the media GW wiring correct and present. The APIM communicates with the ACM via private connections.
Sync 4 relies on the TCU and GWM for time and GPS via the ethernet network. You do not have this, so you need to set your APIM for āNO TCU Presentā via the asbuilt.
This is basically the same as converting from Sync 2.5 to Sync 3. You might want to find out how those harnesses are wired.
Since your vehicle did not come with Sync 3, there may be differences in the CAN messaging. You may need to change the firmware in other modules to get the consistent CAN messaging to keep the Sync 4 APIM alive. Other folks on this thread have identified CAN messaging issues with Sync 4 conversions in various vehicles. You might want to reach out to them for advice on this issue.
Re-checked the wiring harness and can confirm that those pins are present and correctly wired between the ACM and APIM. Its got to be a software compatibility issue between the APIM and ACM.
I have this set in the asbuilt. Side note, noticed that HS4 with HS4 TCU is an option in the asbuiltā¦
I hope this is not the caseā¦ I am going to attempt to use this harness with a Sync 3 gen 4 APIM to see what results I get (with the addition of pins 53/54)
1 Like
This is the best thing you could do to prove out the setup on Sync 3, then swap in the Sync 4 unit. I was going to suggest this but didnāt think you had access to a Sync 3 unit.
Let us know what happensā¦
FYI:
These are the 2 flavors of LDVS connectors used on Sync 4. C2383C is for 8" screens, C2383CA is for 12" screens. The pinouts are different, thus the importance of specifying the correct module for your retrofit.
The connector in this pic posted by @JHForman812 is the 12" variety.
Ok so interesting update on my Maverick swap project. My initial tests with a non nav unit resulted in what I described above. I swapped with a nav 8ā unit and it works perfectly. Not sure why a non nav unit would not work unless it was simply a bad APIM. Need to figure out a permanent mounting solution and then button a few things up in the as built (wireless CarPlay does not work for instance when it did before I edited a few things) and I should have a fully functional swap.
2 Likes
Can you post both asbuilts for the NAV and NON-NAV units?
Weird, still cannot get the APIM to show in ForScan. Fresh profiles on both latest release and beta versions. Other HS3CAN devices show up fine.
If you are still having an issue with the Sync 4 APIM and the FCIM, there is probably an issue with the CAN-BUS, like an address contention with the Sync 4 unit. Have you tried to disconnect the FCIM and find the Sync 4 APIM? There are a number of folks that have the Sync 4 APIM showing in FORScan, itās not the issue there.
You added a GWM to your vehicle. This tells me the 2015 Lincoln MKZ is CGEA 1.2 architecture. We already know there are issues with C1CMA vehicles. CGEA 1.3 vehicles seem not to have any real issues.
@avdonr might have some insight here on the Fusion/MKZ installation.
1 Like
So Iāve removed the FCIM from the equation with no luck sadly. One thing I have noticed is that I do get a DTC from the BodyCM saying it lost communication with the APIM. Not sure if thatās an As-Built issue with the APIM or a compatibility issue entirely.
One thought I have is that in the release notes of ForScan, it shows very specific cars being supported for the Sync 4 Retrofitā¦ My car not included. Have we seen anyone successfully get the APIM to show in ForScan on a car not listed as supported? Either way I have sent an email to ForScan support so I hope they may have some more insight there
1 Like
The MKZ is the same as the Fusion. They had CGEA 1.3 since 2013. I believe he upgraded the GWM from a 2018.