Thank you both for your reply. I will try to disconnect those two plugs from the car before ordering a module to see which functionalities I lose and will update my findings.
Would anyone happen to have or know where I can find a diagram for the Chinese version (sync+) APIM connector to compare to the sync 4 diagram posted in this discussion?
motorcraftservice.com/Home/SetCountry?returnUrl=%2FAsBuilt
Pay for the 72 hour Oasis subscription. You will have everything you could want.
Thank you. I will definitely look in to it to find the diagrams before I pull the triger
You are correct. I unplugged this and lost the 360 camera. From the research Iâve done the same 4x square plug is found on the Telematics Communication module on EU spec cars, which I am also planning on getting (unless it requires programing for the vehicle VIN)
I also removed the other plug (the one next to the main APIM connector) and the screen in the mach-e wouldnât even turn on. The screens in the European and my (Chinese) version of the car have similar connectors which is why I am assuming there might be a third module that powers the screen that I need (apart from the APIM and Telematics Communication module)
I know I have recently bombarded this thread with possibly unrelated topics for which I apologize but this is the only thread I could find with people who know about this things that could direct me in the right direction.
I have tryed to make a base script for to get sync 4 booting on C1MCA requires knowledge of the carâs CAN bus architecture, message formats, and IDs. Below is a basic example using Python and the python-can library.
Note that this is a generic template, and youâll need to adjust it based on the actual specifications of the Ford Fiestaâs CAN bus.
import can
import time
class FordFiestaEmulator:
def __init__(self):
self.bus = can.interface.Bus(channel='can0', bustype='socketcan') # Adjust channel and bustype accordingly
self.setup_handlers()
def setup_handlers(self):
# Define message handlers for Ford Fiesta CAN bus
# Example: self.bus.set_filters([{"can_id": 0x100, "can_mask": 0xFFF}])
def send_can_message(self, can_id, data):
message = can.Message(arbitration_id=can_id, data=data, extended_id=False)
self.bus.send(message)
def receive_can_message(self):
message = self.bus.recv(timeout=1.0) # Adjust timeout as needed
if message:
print(f"Received CAN message: {message}")
def run_emulator(self):
while True:
# Emulator logic here
# Example: self.send_can_message(0x100, [0x01, 0x02, 0x03])
self.receive_can_message()
time.sleep(1) # Adjust sleep time as needed
if __name__ == "__main__":
fiesta_emulator = FordFiestaEmulator()
fiesta_emulator.run_emulator()
In this template:
- Adjust the channel and bustype based on your setup.
- Customize the message handlers, IDs, and data based on the Ford Fiestaâs CAN bus specifications.
- The
send_can_messagefunction is used to send CAN messages with the specified ID and data. - The
receive_can_messagefunction is used to print received CAN messages.
To create an accurate Ford Fiesta CAN emulator, you need to refer to the Ford Fiestaâs CAN bus documentation or reverse engineer the communication protocol used by the car.
1 Like
2022 Maverick Lariat. My friend and I are trying to upgrade from SYNC3 to SYNC 4. According to the service manual, the TCU and APIM communicate via HS4CAN. When using SYNC 4, Forscan no longer sees the TCU when scanning in a new profile. We are following Zackmd1âs (2022 XL Maverick) conversations in this forum and on the Maverick forums. We have working APIM builds but FordPass doesnât work due to no communication with the TCU. We have confirmation that the TCU is receiving commands from the network, but it is not communicating with the APIM. Apparently Zackmd1âs build worked because his TCU was already using hs3can. Did you solve all of your issues with your build?
Any ideas?
I am the aforementioned friend. One important note to add to the behavior that we are seeing with the SYNC4 APIMs in our Mavericks is that the âHS4 enabledâ option in FORScan, activated by code 7D0-02-02: xxxx-xx*x-xxâ, does not seem to actually enable HS4 on the SYNC4 APIM.
Per the SYNC3 APIM pinout, HS4CAN is on pins 41/42. However, I have not been able to find confirmation anywhere on this forum or elsewhere online that explicitly confirms the SYNC4 APIM still uses pins 41/42 for HS4 when it is supposedly enabled. Is anyone able to comment on the presence of HS4 network in the SYNC4 pinout?
Does anybody in the CyanLabs community know more about how changing the forscan configuration file to enable the HS4 network actually impacts the firmware on the APIM? In other words, why enabling HS4 in the APIM configuration appears to have absolutely no effect?
For full clarity on the scenario, we purchased 8" Navigation equipped APIMs from an F150. These SYNC4 APIMS do have the pink ethernet connector on them. I understand that in the F150, this connection would be used to reach the TCU through the GWM. A second question to anyone here who may understand the SYNC4 APIM hardware specifications: is it ONLY possible for this F150 APIM to reach the TCU over that ethernet network? Logically, one would think that by âenabling HS4 networkâ in the APIM, that the APIM would recognize incoming messages from the TCU, but it does not. Based on previous posts from zackmd1, who bought the exact same APIM, it seems that the APIM is smart enough to recognize the TCU without HS4.
As a part of troubleshooting, I disconnected pins 41/42 and disabled HS4 in FORScan to see if the APIM would pick up the L-series TCU on HS3CAN. It never did. What is incredibly confusing about all of this is that @zackmd1 mentioned in his posts during his dive into this that his TCU was not on the HS4 network, but rather HS3, while still being an L-series TCU. I had the understanding that L-series TCUs are newer and only communicate over HS4 or ethernet.
So, my running theories are: (1) enabling HS4 in forscan doesnât actually do anything (2) ford moved the HS4-related pins to 53/54 on the SYNC4 (3) something in the GWM is blocking the TCU comms from reaching the APIM over HS4.
GWM programming seems to be a black box that nobody ever talks about, but I donât understand why.
They took the SYNC 4 systems off the HS4 network with the APIM. Here are the APIM pins for a 23 Expedition with SYNC 4.
Here you can see the diagram for the TCU and you can see it is on the HS4 network still.
Here is the GWM schematic.
2 Likes
Thank you for sharing these. We have similar schematics available to us from the Maverick service manual.
We were wondering if there were any SYNC4 vehicles which still include the HS4CAN network but donât use it on the APIM. F150 does not meet those criteria, but your post confirms the Expedition/Navigator do.
So, the question remains for me, why does there exist an option in the sync 4 APIM configuration to enable it? Any ideas on why the APIM doesnât see the TCU anymore?
Would you happen to have an AsBuilt file for the Expedition configuration you shared? Interested to know what it has for APIM option 7D0-02-02.
1 Like
Update:
Turns out I had not removed pins 41/42 in their entirety. I went back, completely removed the connections for pins 41/42 in the wiring to the SYNC 4 APIM, and communication with the TCU over HS4-CAN was restored. This confirms two things for us:
(1) Pins 41/42 are grounded on the SYNC 4 APIM board directly, as are pins 53/54. The pinouts for the SYNC 4 APIM did not make this clear. This means: for any SYNC 3 to SYNC 4 swappers out there, you MUST remove connections from pins 41/42 AND pins 53/54.
(2) The suspected possibility of âenabling WiFi and OTA updatesâ by zackmd1 in his endeavors by enabling HS4-CAN in the SYNC4 is not possible. The necessity to remove pins 41/42 confirms that WiFi connectivity and OTA updates will never be possible in a SYNC 4 retrofit.
With TCU connection restored, I can successfully access and control the truck via FordPass. This was only achievable by NOT resetting the SYNC 3 APIM before I uninstalled it, hence leaving the TCU status as active. I am still unable to access âConnected Vehicle Functionsâ in the SYNC 4 APIM. Based on some research from other posts on this forum, it seems that CVF/CCS are controlled by a variety of settings in the APIM, TCU, and GWM jointly. First place I plan to start is with the L-series TCU, as I see there are a large variety of CCS setting controls in there, but they are not documented well.
@bill32399 , if you happen to have access to the APIM .abt for that Expedition, would you also be able to share the TCU .abt? I am looking for differences in TCU configurations to sort out discrepancies.
@zackmd1 showed in one of his updates that he did in fact have FordPass (and hence CVF/CCS) functionalities in his SYNC 4 APIM, though he has CCS disabled in his APIM .abt. So, I assume he must have a different TCU type or different TCU programming than the Lariat trim.
1 Like
I did not use a VIN for that info. I used Oasis. You could use any 23â Expedition VIN out there on car sales sites to get that info on Fords AB database.
I did try that already. Pulled a VIN for a 23 expedition limited from car fax and checked it against the motorcraft service asbuilt database. There was nothing populated except the BCM. I am not aware of any functionality in the databases on this website to search by VIN.
The GWM controls all the permissions for these functions now. The APIM and TCU are only for the menus and reporting activities for the most part. You are correct that these are not published.
1 Like
Do you know if it is possible to enable the functions as they are intended by modifying the GWM configuration, then?
Out of curiosity, why does it seem as if programming the GWM is voodoo?
You are programming licensed services and, in some cases, not paying for it depending on the function. If the vehicle reports this to Ford it can possibly be an issue.
1 Like
Ok, that makes sense. I would have expected Ford to restrict licensed services on a hardware basis.
In this case, I am just trying to re-enable features which came with the vehicle that have gone missing after the APIM swap. I find it unusual that Ford would change the GWM configuration requirements surrounding the CCS (i.e. the TCU) from sync 3 to sync 4. Are there any resources or knowledge about making the changes for this purpose? Or is it all completely in the dark?
Actually, apologies. I read this message wrong the first time.
I DO still have Connected Vehicle Functions enabled. The problem is I cannot see the menu to control which CVF options are enabled/disabled (e.g. the location data, insurance data options).
FordPass is still connected to my truck and all commands work, even with the new SYNC 4 APIM installed. It is only the menu features that I would like to reappear. Based on what you say here, it sounds like my initial expectations were correct, that the CVF (menu, not the features themselves) can be enabled in the TCU configuration?
Ford is making it so Cyanlabs and Forscan are much less relevant. You can thank all the people that screwed things up and then went to Ford to fix it after they told them what they did.
I have found Cyanlabs to be very useful during this SYNC 3 to SYNC 4 upgrade. I think Ford owners are still able to modify their vehicles with Forscan fairly easily.
2 Likes
There is a complete change in the way Ford manages services between Sync 3 and 4.
Yes