PATS and how it works

[LarryJM]

I am about to install a Track Apps Cluster in my 2014 Base Mustang GT. The Mileage matches. I intend to use Forscan. I have tested the Forscan system and everything seems to work. I have four working keys to the original cluster. It seems I am only talking to the cluster in PATS with Forscan. What I want to do is take out the original cluster and install the Track Apps Cluster and run PATSs with two of the four working keys I have using Forscan. The original cluster and two other working keys will be set aside. So if Forscan fails, will I be able to reinstall the original cluster as a back up using the two other original keys or is somehow the ECU has been changed? I am trying to avoid bricking the car.

 

[13v6]

If you haven't already done it:
First, you shouldn't have a problem with Forscan. Even I got it done correctly. It's pretty straightforward if you find the right youtube video with instructions. It's about as scary as using a tuner on your car the first time. This was the best video that I found.

Second, I believe you are only touching the PATS in the cluster and not the ECU so your old setup and keys should still work. I can't say for sure if it'd be plug & play after you change it but the keys will be programmed to that cluster still.

 

[LarryJM]

If you haven't already done it:
First, you shouldn't have a problem with Forscan. Even I got it done correctly. It's pretty straightforward if you find the right youtube video with instructions. It's about as scary as using a tuner on your car the first time. This was the best video that I found.

Second, I believe you are only touching the PATS in the cluster and not the ECU so your old setup and keys should still work. I can't say for sure if it'd be plug & play after you change it but the keys will be programmed to that cluster still.

Have not done it yet. I watched that Video and it's really not correct. You must do two 12 minute waits. One 12 minute wait to access the cluster and the second 12 minute wait to erase and reprogram the keys. All the videos also show the cluster just pops out. Well you really got to manhandle it to get it out. You must also have a PAID license to program the keys to the cluster. For sure a battery charger is also in order as the power must be over 11.7 volts at all times in the half hour to program.

 

[Juice]

Trial license has full functionality, but it expires in 2 months.

 

[LarryJM]

Trial license has full functionality, but it expires in 2 months.

To do key work, you must have a paid license of some type. My issue, is this program actually talking to the keys and ECU or is it just the cluster?

 

[Juice]

ECU and Cluster.
Keys are stored in the cluster, ECU just gets flagged ok/not ok to start.
Nothing really "talks" to the keys, they just have a unique RFID. It is this RFID that you are storing in the cluster.

 

[LarryJM]

ECU and Cluster.
Keys are stored in the cluster, ECU just gets flagged ok/not ok to start.
Nothing really "talks" to the keys, they just have a unique RFID. It is this RFID that you are storing in the cluster.

So the keys and cluster go together. If that is the case, then you could avoid PATS all together buy getting the Keys and Cluster together and just replace the blades for recut. So all said and done, I could go back and forth with the Base and Track Apps cluster as long as I have keys that match each cluster.

 

[Juice]

So the keys and cluster go together. If that is the case, then you could avoid PATS all together but getting the Keys and Cluster together and just replace the blades for recut. So all said and done, I could go back and forth with the Base and Track Apps cluster as long as I have keys that match each cluster.

Maybe. There is a PATS initialization step to establish the cluster-pcm handshake. Not sure if you can just plug in a programmed w/keys cluster and the pcm accept the new hardware without the handshake.
Than all a thief would need is a programmed cluster to steal the car. Swap the cluster and drive away. Thats the whole point of those 10 minute waiting for access periods during PATS programming.