I tried the APIM interogator but I’m not getting the .XML file. I downloaded the Syn3 updater, prep the USB, left it in vehicle, it said updating then went to complete. Inserted it into the laptop and still no .XML. I tried it twice and still the same result?
The surround buttons. The screen / touch works, steering wheel controls works just the surround buttons.
Not sure this helps but this is the file I’m using from the syn3 updater:
GB5T-14G386-AD_1606255780000.TAR
The xml file will be in the SyncMyRide folder on the usb. Or did it not generate at all? -AC should work.
The panel with the play/FF, volume and tuning control is the FCIM. This panel my also control AC, etc. Connect FORScan and see if there are any DTC’s for the FCIM and APIM. It might be a simple fix.
Sorry, yes it did not generate at all. I had the message say updating, successful and then the restart but when I plug USB back into computer no .xml in the folder.
Ah right okay, I will be connecting it back up for shortly and I will get back to you.
The VIN comes from the FCIM - well that certainly makes sense then, because my SYNC3 (Focus) FCIM did come from a different car - I actually had two of them to choose from, so I tested them both and picked the one that was in the best cosmetic condition.
So, then is the VIN hard coded to the FCIM at the time of production, or can it be reprogrammed with my actual VIN via Forscan or some other method ?
OK good to know on the SiriusXM logos. If I wanted to pursue this by sourcing a later ACM, what model year minimum should I be looking at ? And are the newer units also different with regard to the wiring and connector interfaces (power, speakers etc) ?
Late 2019, it will be a K or 4 starting the part number. You want one that is manufactured late 2019 at least. This will maintain the wiring format. You might have to add either 2 or 4 wires directly to the APIM, as your car will not have them. You can research this in this thread, it has most of the info.
i would like to update the APIM Firmware, you already have done this as i read in an thread. Can you help me in that case to understand how to perfom this?
i already ordered obdlink ex, have FORScanSetup2.4.3.test20210808
iam it systemadministrator and have got extended technical knowledge
Sorry for the delay. Yes, the VIN can be programmed in the FCIM with FORScan. Attached is a FORScan codes sheet for the FCIM. You can see at the bottom there is an area for the VIN encoding, This is the alphanumerical VIN converted to HEX.
If you like, just PM me the FCIM asbuilt in the vehicle now and the VIN of your vehicle and I can fix the asbuilt, or you can do it. You just need a hex converter to convert the VIN. Here is an online one that works well. Keep in mind these converters are CASE SENSITIVE.
This is fantastic - thank you very much indeed. I should be able to handle this myself from here - I will report back when done and with any other observations that may be relevant or useful to others.
Save the asbuilt info from the currently installed FCIM in a safe place.
I looked up the VIN for the donor. It might be it cannot be changed in this module because it’s from a 2014 model. The vehicle has a FCDIM, which does not have the same coding format. But maybe this doesn’t relate… 1FADP3L92EL169084.ab (7.0 KB)
I see a few units 2019/2020 F150 on EBay with part numbers starting with K - the FM only units are not much $$, but those that support both FM and SiriusXM are much more $$…I see that the case mounting support at the rear for the F150 (single center post) is also different from my current Focus ACM, which has a short support peg at each side - I suppose that can be corrected by transferring bracketry…? Do we know that these 2019/2020 also support HD Radio (maybe that is standard by now ?)
The label will indicate HD Radio, SiriusXM, etc. Don’t worry about the CD player, unless you really need it. It can be deleted from the Sync audio sources. And you can just swap the brackets for the mounting.
Checked this evening - unfortunately the FCIM in my car has no option for an as-built change via Forscan - only an option to update the firmware - I guess I’m stuck with it…