Sync3 Navigation not staying on course

[jhedfors (Jeff H)]

It looks like it is already set correctly:

720-03-01: 5553-xx

[F150Chief]

Are you saying the IPC shows KPH while you drive, or is it just the AA display in KPH? Never mind…
I looked at the pic, you IPC is set for US and is displaying MPH. It’s the Google app showing KPH.
If you did not do this:
A master rest should have removed the phones from the Sync system. While the phone is removed from the Sync system, go to the AA settings on the phone and wipe the settings to default and forget the vehicles. Then pair the phone back to Sync and see how it does. You need to wipe the cache in the devices.

[F150Chief]

@jhedfors

I have attached the log in case you can see anything else that may need to be adjusted to fix that issue. Should I create a separate post for this remainig issue?

All part of the same issue…it’s easier to track what has been done in 1 post.
Installed:
NU5T-14G381-AD
4U5T-14G421-CAH
4U5T-14G421-CBH
4U5T-14G421-CCH
4U5T-14G421-CDH
4U5T-14G421-CEH
4U5T-14G421-CFH
4U5T-14G421-CGH
4U5T-14G421-CJH
4U5T-14G421-CHH
5U5T-14G391-CS
4U5T-14G422-CAP
4U5T-14G422-CBP
4U5T-14G422-CCP
4U5T-14G423-CC
Looks fine…
Firmware and storage look fine. It is the original firmware for the APIM. Other than the DTC’s in the APIM all looks ok. Find out what those are…

<d2p1:DTC DTCValue=“c1590048”/>
<d2p1:DTC DTCValue=“e1010008”/>
<d2p1:DTC DTCValue=“c1400048”/>

[jhedfors (Jeff H)]

@F150Chief

Other than the DTC’s in the APIM all looks ok. Find out what those are…

<d2p1:DTC DTCValue=“c1590048”/>
<d2p1:DTC DTCValue=“e1010008”/>
<d2p1:DTC DTCValue=“c1400048”/>

I can reach out to the vendor to see as I have no clue…
I see that those are listed twice:
||Line 12: <d2p1:DTC DTCValue=c1590048/>|
||Line 13: <d2p1:DTC DTCValue=e1010008/>|
||Line 14: <d2p1:DTC DTCValue=c1400048/>|
||Line 117: <d2p1:DTC DTCValue=c1590048/>|
||Line 118: <d2p1:DTC DTCValue=e1010008/>|
||Line 119: <d2p1:DTC DTCValue=c1400048/>|

Edit: So many acronyms… I just realized those are Diagnostic Trouble Codes. I will see if I can find out what they could be.

[F150Chief]

You can read them directly with FORScan. DTC tab.

[jhedfors (Jeff H)]

@F150Chief

Are you saying the IPC shows KPH while you drive, or is it just the AA display in KPH? Never mind…
I looked at the pic, you IPC is set for US and is displaying MPH. It’s the Google app showing KPH.
If you did not do this:
A master rest should have removed the phones from the Sync system. While the phone is removed from the Sync system, go to the AA settings on the phone and wipe the settings to default and forget the vehicles. Then pair the phone back to Sync and see how it does. You need to wipe the cache in the devices.

I did a master reset and cleared the cache/data on two separate phones, and both continue to show the “6554km” and “0h00m” information with Google Maps. Very strange. I tried Waze to see if a similar issue exists, and it looks like Waze does not send any infomation to this secondary display at all (not sure if that is expected or not). I don’t use Waze, but only did as a test.

[F150Chief]

Did you disconnect the other antenna?
What did the DTC errors say?

[jhedfors (Jeff H)]

@F150Chief

Did you disconnect the other antenna?
What did the DTC errors say?

I did not disconnect the other antenna as the Sync3 Nav worked after the changes you suggested. From what I understood @bill32399 was suggesting was that disconnecting would come with other issues, so I did not pursue that further as the satnav was now accurate.

@bill32399

You will need to pull out the IPC to get to it. The downside is that you will no longer have a direction indicator on the IPC since it looks for the signal on the MS-Can bus.

I will be honest though I have a 2015 and I have both connected with no issue, but I retrofitted an Explorer 2017 OEM Sharkfin antenna with an OEM splitter.

Here are the DTC errors:

DTC.txt (3.5 KB)

[F150Chief]

OK, looks like they all cleared but pay attention to this one if it keeps coming back…you could have a bad sensor in the PSCM (power steering). Just a note…

===PSCM DTC U0121:00-08===
Code: U0121 - Lost Communication With Anti-Lock Brake System (ABS) Control Module ‘A’

Status (-08):

• Previously Set DTC - Not Present at Time of Request
• Malfunction Indicator Lamp is Off for this DTC

Module: Power Steering Control Module

Freeze Frame #1:
-SWRS: 0 1/min - Steering Wheel Rotation Speed
-SW_ANGLE: -0.10 ° - Steering Wheel Angle
===END PSCM DTC U0121:00-08===

===PSCM DTC C1B00:64-08===
Code: C1B00 - Steering Angle Sensor

Additional Fault Symptom (:64):

• Signal Plausibility Failure

Status (-08):

• Previously Set DTC - Not Present at Time of Request
• Malfunction Indicator Lamp is Off for this DTC

Module: Power Steering Control Module

Freeze Frame #1:
-SWRS: 0 1/min - Steering Wheel Rotation Speed
-SW_ANGLE: -86.10 ° - Steering Wheel Angle
===END PSCM DTC C1B00:64-08===

[F150Chief]

So, I was looking up the IPC asbuilt for your 2015 Explorer XLT to see if the nav repeater settings were correct, NAV is Present.

EB5T-10849-GK
Instrument Panel Control Module
IPC 720-01-01 FDC2 6FBE 2439
IPC 720-01-02 F42C 0842 982C
IPC 720-01-03 002B
IPC 720-02-01 0309 0700 3D
IPC 720-03-01 5553 D3
IPC 720-04-01 3018 3C80 0030
IPC 720-04-02 0000 0000 002D

Other than there being a firmware incompatibility, which is a possibility, there are no other settings in the APIM or IPC that would affect this, that I know of.

[jhedfors (Jeff H)]

@F150Chief

IPC 720-01-03 002B

Thank you so much for looking into this. This was the only one that was different from what I had. This is the Remote Start - I had enabled it as my vehicle has an aftermarket remote start installed, so I enabled it (not sure if it will actually do anything though).

OT: Do you know if I can get individual tire pressure readings to display? My Pathfinder had this and it was really nice to be able to monitor it.

[F150Chief]

You need to enable it in the BCM also…It’s in the FORScan easy menu for that.

[bill32399]

So the BCM will get the data from the pressure on each wheel but it will not display it on the 11-15. You can see this in Forscan. It was not added to the IPC calibrations until 2016+ where you can see all 4 wheels. You cannot use an IPC from a 2016+.

Also you can enable the Ford Remote start. All you need is the correct key and a hood switch if you don’t already have one. I have done this with my 15.

[jhedfors (Jeff H)]

Bummer you can’t see the individual tire pressure - thanks for that info.

I will make sure I update the Remote Start in the BCM as well. The previous owner had installed an aftermarket remote starter. The two stock keys (double-press lock, I think) work as well as a special extended range dongle (with antenna mounted behined the rearview mirror).

[F150Chief]

@jhedfors

I did a master reset and cleared the cache/data on two separate phones, and both continue to show the “6554km” and “0h00m” information with Google Maps.

Try this:
I told you to change this…
7D0-01-02 C 201 09 00 02xx
needs to be…
7D0-01-02 02 01 0A 00 02xx
This is causing the NAV not to work because it is set for Intel vs Motorola format. Motorola format is used for NA and EU, ROW uses Intel.

Change the ‘A’ back to ‘9’ to test if Google Maps is expecting an Intel format. Being this is a 2015 Explorer (CGEA 1.2) with the old Sync 2 map format. Not sure if it will resolve the issue but worth a check.

Does the Sync 3 onboard Nav repeat to the IPC properly?
Did you disconnect the GPSM to see if that solved the issue?

[bill32399]

A 16-19 Flex used Sync 3 and still had CGEA 1.2 so the settings from that will also work perfect in a 15 Explorer that has Sync 3.

The Taurus did also but I am not as familiar with those years.

[jhedfors (Jeff H)]

@F150Chief

Try this:
I told you to change this…
7D0-01-02 C 201 09 00 02xx
needs to be…
7D0-01-02 02 01 0A 00 02xx
This is causing the NAV not to work because it is set for Intel vs Motorola format. Motorola format is used for NA and EU, ROW uses Intel.

Change the ‘A’ back to ‘9’ to test if Google Maps is expecting an Intel format. Being this is a 2015 Explorer (CGEA 1.2) with the old Sync 2 map format. Not sure if it will resolve the issue but worth a check.

Does the Sync 3 onboard Nav repeat to the IPC properly?
Did you disconnect the GPSM to see if that solved the issue?

Thank you. I tried changing the ‘A’ back to ‘9’ to see if that solves the issue with the invalid distance and time showing, but it seemed to have no affect. The Sync 3 onboard Nav repeats to the IPC with no issues that I can see.

I did not disconnect the GPSM as unless I misunderstood @bill32399 comment below, I will no longer get the direction indicator on the IPC (is that all Nav info or just the compass?).

@bill32399

It is located above the IPC. You will need to pull out the IPC to get to it. The downside is that you will no longer have a direction indicator on the IPC since it looks for the signal on the MS-Can bus.

I will be honest though I have a 2015 and I have both connected with no issue, but I retrofitted an Explorer 2017 OEM Sharkfin antenna with an OEM splitter.

@bill32399

A 16-19 Flex used Sync 3 and still had CGEA 1.2 so the settings from that will also work perfect in a 15 Explorer that has Sync 3.

Thanks! What settings would I want to change?

[bill32399]

Start with the ones F150Chief mention above.

[jhedfors (Jeff H)]

@bill32399

Start with the ones F150Chief mention above.

Thanks. I only saw this one change which I tried:

@F150Chief

7D0-01-02 02 01 0A 00 02xx

Did I miss other changes?

[F150Chief]

You got it, thanks for testing that. If the onboard Nav is repeating to the cluster ok then this really looks like an AA issue. I recently read there was an AA update that messed up some Nav stuff for them related to the 'Timeline" feature on Android phones while I was researching this issue. I’m not familiar enough with Android Timeline feature to really explain it…unfortunately.