I've got DTCs everywhere.

 

Jim was trying to run on VISTA .. which Ford says is not supported .. he is going to install in Windows 7 and try again ..

Lexion .. Did IDS download the files from Ford for your ABS PMI? You can call me if you want

 

I will call you in a bit
LEXiiON

 

Ok still no success. I tried the PCM code from dmhines and entered a 2013 VIN. This time it was able to communicate to the module, download the calibration, i had to manually enter the AS built, however, the ABS light and the traction control light don't stop blinking. DTCs are Yaw Sensor test failed and Incompatible Software Component.
Interestingly, IDS can't communicate with my PCM with the 2013 PCM code and it can't communicate to the ABS Module with my original PCM Code and VIN. Something doesn't like each other.

Maybe Zero has an idea?

 

You did a full PMI right?

We just got JIM010's ABS module successfully installed and working.

 

Yes a full PMI.
Gee, I guess track apps and 2010 is further away now

 

So to be clear ... you entered the 2013 PCM part # and 2013 VIN during the new session startup. Then for the PMI for the ABS you entered the 2013 VIN again? That is what what just did on Jims car and it worked. So perhaps its not gonna work with the 2010. You could experiment with also doing a PMI and AS-BUILT on the SJB and BCM using 2013 calibrations.

 

Yes i did all of the above.. I think i know the VIN in my head now ...
I might try that, once i am back from my trip...

Although i have a suspicion. There are 2 modules apart from the PCM that the IDS can't read when i pull the DTC's with the 2013 PCM Code. I will try to see which ones that are.

The Two Modules are:
PAM (Parking Aid Module - i don't think that does something to my case)
PSCM (Power Steering Control Module - makes sense, as i do not have electric steering)
The other two it can't read are:
PCM (2010 PCM)
ABS (i put my old module back in, that's why)

That leaves the thought, that the ABS and PCM communicate with each other and I either need to swap both or forget Track Apps, unless Zero has an idea.
LEXiiON

 

Here is confirmation.....You DO have to do PATS RELEARN even with a new cluster from a dealer. We did the PMI for the cluster and PATS light is off. Ignition wouldn't start. Doing PATS relearn now.

 

Boss Cluster installed and working in a Base model '13GT.
We did the install using the cars own ASBUILT (base)
The LCD menu for gauges only displays the Mustang Running horse and "miles to empty" readout
The 4 way steering wheel switch is plug n play.
Now that we confirm everything is functional, no DCTs, plan is to go back Start new session and enter the VIN of a '13 Boss that has Track Apps and module programming using the Boss module programming.
This cluster looks sick in operation

 

Sheesh, the nerd power is strong in this thread lol

 

I can confirm that Track Apps is working.

I will see if I can get rid of all the DTCs showing in the various modules.

Thanks Lexxion and Dan!

 

Cleared all DTCs.

Since I retrofitted a nav, I get errors with the APIM, FDIM, GPSM, HVAC.

Also get U045A-55-0A for the IPC. Invalid data from the parking assist control module.

 

WOOOOHOOOOOO! SUCCESS!
Thank You DAN the man (DMHines) for the phone call
Being somewhat of a computer idiot, this scared the crap out of me prior to doing it but here in a nutshell

We have a BASE model '13GT track pack car
We installed a '13 Boss 302 Cluster with LCD Track Apps
Everything including the track apps, gauges, digital gauges to are 100% functional

 

Did you get mycolor working?

 

Jim ... is your parking assist working? You can do a PMI on you APIM and load a 2012 calibration in it .. you are still running it all as a 2010 right?

 

It works, but DTCs show up.

It is telling me that I need Oasis to program the APIM. Won't let me go further.

 

sorry .. I was thinking ACM ...

 

It is saying that Oasis is needed for Apim and PCM.

These are off limits to us?

 

I got it all working on Vista now, by the way.