SYNC 3 swap, It's all in here

Here's the APIM data:

7D0-01-01 022A 0502 202C
7D0-01-02 0298 0000 82F6

7D0-02-01 5553 0702 C04B
7D0-02-02 0200 8000 005D
7D0-02-03 0000 DC

7D0-03-01 0000 0101 00DD

7D0-04-01 0100 0000 06E3
7D0-04-02 0000 DD

7D0-05-01 1856 195A 29E7
7D0-05-02 D6B4

7D0-06-01 805E

7D0-07-01 1000 3300 0022
7D0-07-02 0000 0B65 0050
7D0-07-03 0056 566E 00FB
7D0-07-04 4C2E

This was copied from a 2016 GT350R with Electronics Package (Recaros, so no heated/cooled seats, but it does have dual-zone climate). My car is a 2016 GT350 Track pack, which had only the base radio, single zone climate, and Recaros.

My changes are:

7D0-01-01 0xxx xxxx xxxx (removesSirius from audio sources)
7D0-01-02 xxxx xxxx x2xx (disables TravelLink)
7D0-02-01 xxxx x7xx xxxx (GT350 boot screen)
7D0-04-01 xxxx xxxx 06xx (Bluetooth pairing name = Ford Mustang)
7D0-07-03 xxxx xxxE xxxx (tire circumference)

The Bluetooth pairing name and the delete Sync from sources are the two things that jump out at me. I have tried the Bluetooth name and it did the same thing to my car. I have combed through Sparts as built database and have yet to find a car that Ford used that hex bit on.
The Sirius thing has given several people issues. It usually deletes the on screen HVAC controls as well as causing issues with text to speech.

I made a harness for another GT350 so I’m planning on digging into this as built soon. I see your mindset as far as using a R VIN but I’m wondering how different the two are.

Patio208 said:

^Took a gamble on a crimper from Amazon. Should be here tomorrow, will post info if it works well enough.

Well I tried..... not good enough for me, I'm a perfectionist. Going to give the plug and play harness a go. It's worth the piece of mind.

Click to expand...

Which one did you get? I bought these $22 crimpers on Amazon: https://www.amazon.com/XH2-54mm-XH3...coding=UTF8&psc=1&refRID=ZA1MJ75XEREVQENPP205

It did a fine job crimping, but did not square the crimp. The fit of the terminal in the connector is so tight that I had to take my needle-nose pliers and use the crotch of the pliers to gently square the crimped part so that the connector would slide all the way in. Once I figured out the technique the rest of them went in easily.

Michael J said:

Which one did you get?

Click to expand...

https://www.amazon.com/gp/product/B078WPT5M1/ref=oh_aui_detailpage_o01_s00?ie=UTF8&psc=1
Similar to yours. They did an okay job after I learned a technique that seemed to work. I probably could've used them but in the end I just wanted as close to a factory install as possible. Not to mention an easy install, no splicing etc.

Got my wire harness from Mr HextallS550.
So ready to install everything!!! :cheers:

Simplyknown said:

Got my wire harness from Mr HextallS550.
So ready to install everything!!! :cheers:

Click to expand...

Got mine as well, well worth the money thats for sure. Just have to wait on the "A" usb cable to get here sometime in the next week or two and I'll be ready to go.

5pointOh said:

Got mine as well, well worth the money thats for sure. Just have to wait on the "A" usb cable to get here sometime in the next week or two and I'll be ready to go.

Click to expand...

I don't use the USB connectors so I went on and installed it and it's working great. I do need to buy it though. I did base to sync 2 as that's all I've been able to find. But it's still better than the base radio. And it has HD radio, also Sirius if I want to get it. And a surprise it also has navigation. So I'll have to buy an antenna. I'll keep an eye out for a sync 3 system but just won't be looking for it. I am happy with the mft unit.

HextallS550 said:

The Bluetooth pairing name and the delete Sync from sources are the two things that jump out at me. I have tried the Bluetooth name and it did the same thing to my car. I have combed through Sparts as built database and have yet to find a car that Ford used that hex bit on.
The Sirius thing has given several people issues. It usually deletes the on screen HVAC controls as well as causing issues with text to speech.

I made a harness for another GT350 so I’m planning on digging into this as built soon. I see your mindset as far as using a R VIN but I’m wondering how different the two are.

Click to expand...

Changed both to factory settings, deleted and re-paired the phone, and still the same results. The 2017 GT350s and GT350Rs are using 06 for the Mustang bluetooth name, FYI.

I'm beginning to wonder if I missed some wiring somewhere. Mine was a base unit, I did not replace the ACM, so no SAT or HD radio, and thus I did not add any wires from the ACM to the APIM connector. I did use a 2017 NAV APIM, but I wouldn't think that matters.

Text works on the phone as does media from the phone. It's only when trying to use the phone to send or receive calls. It switches the audio source to radio and does not mute, but does show the call in progress on the screen. I can still take the call if I switch it to the handset either on screen or on the phone. Very strange...

That wiring is only for TraveLink. A subscription service. Did you try to use the data from a GT350? Or have you compared a base, Tech Pack and Tech Pack R using the compare tool?

I compared 2016 GT350R w/electronics to 2017 GT350 and GT350R both with electronics packages because those are the cars with options as close as I could get to mine since I did the Sync 3 upgrade. Those cars have dual-zone climate, but not heated/cooled seats. Same as mine, except I don't have dual zone climate - the only difference.

There are some minor differences in the APIM data:

7D0-01-01
2016 GT350R: 222A 0502 20
2017 GT350: 622A 0502 00
2017 GT350R: 622A 0502 00

7D0-02-01 (only differences are splash screens)

7D0-02-03 (2016 has 0000 and both 2017s have 0005)

7D0-04-01
2016 GT350R: 0100 0000 00
2017 (both): 0100 0900 06

All other data is the same except the tire circumference in 7D0-07-03.

Could this be something in ACM that needs to be programmed differently? I haven't compared those yet.

Just looked through the ACM data...I'm wondering about 727-01-01 Xxxx xxxx xxxx. My base radio has a D in that position and if this matches the F150 spreadsheet information, means it is without SDARS and is expecting and APIM gen 1, which is the base APIM, not Sync 3 as is installed now.

[MENTION=25607]Spart[/MENTION] how similar is this to the issues you had with your phone?

HextallS550 said:

[MENTION=25607]Spart[/MENTION] how similar is this to the issues you had with your phone?

Click to expand...

It's been a while and I don't quite remember. BUT my phone stuff is working just fine now - Siri, speakerphone, whatever. I have a base ACM with Sync 3. I also had an unrelated TTS issue due to my attempt to remove SiriusXM from the source selections.

This is my detailed breakdown of the ACM as-built. Some of this info may be outdated by now, but again what I settled on is working for me with my setup: https://www.mustang6g.com/forums/showthread.php?p=1810550#post1810550

These are my finalized as-built changes: https://www.mustang6g.com/forums/showpost.php?p=1811217&postcount=1300

Did you ever remove Sirius? I was able to but I need to confirm that all Sync voice commands are working

I had some time today to go through my collection of AB files and find which options trigger which changes in the APIM as-built.

Also these could stand to have some confirmation, since I'm just looking at AB files and not actually trying any of this in a car.


Nav vs. Non-Nav

7D0-01-02 x0xx xxxx x0xx - Non-Nav
7D0-01-02 x2xx xxxx xAxx - Nav


Shaker vs. Shaker Pro

7D0-01-01 xxxx xxx2 xxxx - Shaker
7D0-01-01 xxxx xxx3 xxxx - Shaker Pro

As far as the APIM is concerned, 2 vs 3 in this position is the difference between HD Radio being available or not.


RPA vs. Non-RPA
(Reverse Park Assist aka Reverse Sensing System RSS)

7D0-01-01 xAxx xxxx xxxx - RPA
7D0-01-01 x2xx xxxx xxxx - Non-RPA

7D0-04-02 xxx1 xx - RPA
7D0-04-02 xxx0 xx - Non-RPA


Manual vs. Auto Trans

7D0-01-02 xx9x xxxx xxxx - Manual Master Race
7D0-01-02 xx8x xxxx xxxx - Autotragic

Tire Size

7D0-07-03 xxxx xxXX xxxx

Values I found here included 73, 6F, 6D, 68. According to the F150 spreadsheet, this relates to the tire circumference. It's in an area that has other settings for the backup camera, not sure if it affects the Reverse Sensing System.

I could take the time to probably decode what the value means exactly, but I'd bet on it not being super important. But if you'd like to figure it out, this thread where I decoded the method Ford uses to program tire size in the BCM might get you thinking in the right direction.

Options I found no differences for

Enhanced Security Package, Recaros, Adaptive Cruise, Vert vs. Coupe, EB vs. GT vs. GT350***

***I do not have many files for EB/GT350 cars, and virtually all of the files I looked at were coupes. That said, I do have a couple EB/Vert/GT350, and found no real differences aside from the already-known GT350 startup animations.