# Apim not seen via ODB2 **URL:** \ **Category:** Non SYNC 3 Support\ **Tags:** SYNC4, SYNC3, APIM\ **Created:** [4 October 2024 17:52 UTC](https://community.cyanlabs.net/t/apim-not-seen-via-odb2/15372 "2024-10-04T17:52:19Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![zeroday](https://community.cyanlabs.net/letter_avatar_proxy/v4/letter/z/6de8d8/32.png) [@zeroday](https://community.cyanlabs.net/u/zeroday)\ **Post date:** [4 October 2024 17:52 UTC](https://community.cyanlabs.net/t/apim-not-seen-via-odb2/15372/1 "2024-10-04T17:52:19Z")
I’ve been working on doing a sync 3 to sync4 apim swap. However I now have an issue where I cannot see my sync 3 apim via odb2 scan including Forscan. I previously could see my sync 3 apim via forscan. So my question is where do I start troubleshooting the issue? Is there a pair of wires on the APIM that directly connects to the ODB2 that could be causing the issue? Is there a fuse that would cause the APIM to not be detected but still allow the APIM to function? Any help would be appreciated. 2018 expedition with factory sync 3 APIM. ---
**Author:** ![bill32399](https://community.cyanlabs.net/user_avatar/community.cyanlabs.net/bill32399/32/2724_2.png) [@bill32399](https://community.cyanlabs.net/u/bill32399)\ **Post date:** [5 October 2024 02:57 UTC](https://community.cyanlabs.net/t/apim-not-seen-via-odb2/15372/2 "2024-10-05T02:57:54Z")
There are pins you will need to remove in the 52 pin plug to get it to work. Here are the Pinout for the APIM plug for a Sync 4 Expedition that you will need and no more than this shows… ![C2383A APIM](https://community.cyanlabs.net/uploads/default/original/2X/f/f50772b5d4d53440ca81bf91fe0c4fcc64af9824.png) ---
**Author:** ![zeroday](https://community.cyanlabs.net/letter_avatar_proxy/v4/letter/z/6de8d8/32.png) [@zeroday](https://community.cyanlabs.net/u/zeroday)\ **Post date:** [5 October 2024 19:17 UTC](https://community.cyanlabs.net/t/apim-not-seen-via-odb2/15372/3 "2024-10-05T19:17:35Z")
So my problem is I can’t see the sync 3. I’m assuming something I the wiring harness is messed up which is the reason I can longer see the sync 3 but not sure which wires send the signal from the apim to the odb2 ---
**Author:** ![zeroday](https://community.cyanlabs.net/letter_avatar_proxy/v4/letter/z/6de8d8/32.png) [@zeroday](https://community.cyanlabs.net/u/zeroday)\ **Post date:** [10 October 2024 14:48 UTC](https://community.cyanlabs.net/t/apim-not-seen-via-odb2/15372/4 "2024-10-10T14:48:28Z")
Anyone have any clue on this. Sync 3 apim not visible from ODB2 port. I’m assuming its a pair on the APIM that does not have a good connection. ---
**Author:** ![bill32399](https://community.cyanlabs.net/user_avatar/community.cyanlabs.net/bill32399/32/2724_2.png) [@bill32399](https://community.cyanlabs.net/u/bill32399)\ **Post date:** [11 October 2024 01:31 UTC](https://community.cyanlabs.net/t/apim-not-seen-via-odb2/15372/5 "2024-10-11T01:31:24Z")
> [@zeroday](#): > > So my problem is I can’t see the sync 3. Well, you keep bouncing around on your info. Now you can’t see your SYNC 3 APIM? Or do you mean the SYNC 4 APIM you’re trying to get to work? ---
**Author:** ![zeroday](https://community.cyanlabs.net/letter_avatar_proxy/v4/letter/z/6de8d8/32.png) [@zeroday](https://community.cyanlabs.net/u/zeroday)\ **Post date:** [11 October 2024 13:00 UTC](https://community.cyanlabs.net/t/apim-not-seen-via-odb2/15372/6 "2024-10-11T13:00:19Z")
I was trying to explain what happened prior to not being able to see the APIM. I cannot see my SYNC 3 APIM via ODB2 port on 2018 expedition. Radio works fine just not detected via ODB2 ---
**Author:** ![bill32399](https://community.cyanlabs.net/user_avatar/community.cyanlabs.net/bill32399/32/2724_2.png) [@bill32399](https://community.cyanlabs.net/u/bill32399)\ **Post date:** [11 October 2024 13:39 UTC](https://community.cyanlabs.net/t/apim-not-seen-via-odb2/15372/7 "2024-10-11T13:39:36Z")
Did you delete your vehicle profile in Forscan and start a new one every time you swapped modules or do a calibration update? Also what OBD connector are you using? ---
**Author:** ![zeroday](https://community.cyanlabs.net/letter_avatar_proxy/v4/letter/z/6de8d8/32.png) [@zeroday](https://community.cyanlabs.net/u/zeroday)\ **Post date:** [11 October 2024 13:50 UTC](https://community.cyanlabs.net/t/apim-not-seen-via-odb2/15372/8 "2024-10-11T13:50:54Z")
I did delete the profile. I just upgraded forscan to the newest version but generic automotive odb2 readers give a APIM not detected error. One of the adapters listed on the forscan website. I have not done a calibration update. How would I do that? I also read pulling a fuse can reset apim but the fuse suggested is not on my 2018 model. I’m guessing the issue is from a lose wire or pin at apim connection but not sure which pair would cause the issue. ---
**Author:** ![F150Chief](https://community.cyanlabs.net/user_avatar/community.cyanlabs.net/f150chief/32/14712_2.png) [@F150Chief](https://community.cyanlabs.net/u/F150Chief)\ **Post date:** [23 October 2024 23:55 UTC](https://community.cyanlabs.net/t/apim-not-seen-via-odb2/15372/9 "2024-10-23T23:55:12Z")
> [@zeroday](#): > > I’ve been working on doing a sync 3 to sync4 apim swap. However I now have an issue where I cannot see my sync 3 apim via odb2 scan including Forscan. I previously could see my sync 3 apim via forscan. You’ll need to be more clear about what the issue is really… Can you see the **Sync 3 APIM** after it is installed in the vehicle and you scan a NEW PROFILE with FORScan? Can you see the **Sync 4 APIM** after it is installed in the vehicle and you scan a NEW PROFILE with FORScan? Did you remove pins to get Sync 4 to work? Did you put them back when you installed Sync 3? ---
**Author:** ![system](https://community.cyanlabs.net/letter_avatar_proxy/v4/letter/s/bcef8e/32.png) [@system](https://community.cyanlabs.net/u/system)\ **Post date:** [22 November 2024 23:55 UTC](https://community.cyanlabs.net/t/apim-not-seen-via-odb2/15372/10 "2024-11-22T23:55:55Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.