'13-14 Cluster into '10-12 car (with TrackApps) retrofit
#1243
Legacy TMS Member
![](https://themustangsource.com/forums/images/rank.gif)
![](https://themustangsource.com/forums/images/rank.gif)
![](https://themustangsource.com/forums/images/rank.gif)
![](https://themustangsource.com/forums/images/rank.gif)
#1245
Mach 1 Member
![](https://themustangsource.com/forums/images/rank.gif)
![](https://themustangsource.com/forums/images/rank.gif)
I wish we knew how to re-create this bug.
IDS has a built in check that prevents loading calibrations on different ECU part numbers. My original thought was to change the Part Number of the ECU (internally), but now I'll start looking at how to re-create this. (Disclaimer, I do not have a VCM anymore)
-Matt
IDS has a built in check that prevents loading calibrations on different ECU part numbers. My original thought was to change the Part Number of the ECU (internally), but now I'll start looking at how to re-create this. (Disclaimer, I do not have a VCM anymore)
-Matt
#1246
Legacy TMS Member
![](https://themustangsource.com/forums/images/rank.gif)
![](https://themustangsource.com/forums/images/rank.gif)
![](https://themustangsource.com/forums/images/rank.gif)
![](https://themustangsource.com/forums/images/rank.gif)
If you can understand the data log, we could do a remote session and you can have a look to see what I did?
All I know is I was trying to do a PMI on the ACM. Wouldn't let me. Kept saying I had to do a PMI on the PCM, so I tried that. Eventually, it actually did program the PCM.
All I know is I was trying to do a PMI on the ACM. Wouldn't let me. Kept saying I had to do a PMI on the PCM, so I tried that. Eventually, it actually did program the PCM.
#1247
Legacy TMS Member
![](https://themustangsource.com/forums/images/rank.gif)
![](https://themustangsource.com/forums/images/rank.gif)
![](https://themustangsource.com/forums/images/rank.gif)
![](https://themustangsource.com/forums/images/rank.gif)
I tried everything thing I could think of ... I could not get my IDS to go straight into PCM PMI like yours is doing. I did discover the you can change your VIN by just loading the PCM AS BUILT ...
Maybe its a VISTA Bug?? I have no idea ... but no matter what I do ... it says my calibration is incorrect and got go to Module Programming and PMI the PCM. But it does not do it automatically ... and he always complains my PCM is part number CR3A and not DR3A ...
Maybe its a VISTA Bug?? I have no idea ... but no matter what I do ... it says my calibration is incorrect and got go to Module Programming and PMI the PCM. But it does not do it automatically ... and he always complains my PCM is part number CR3A and not DR3A ...
Last edited by jim010; 3/23/14 at 10:02 PM.
#1248
Shelby GT350 Member
![](https://themustangsource.com/forums/images/rank.gif)
![](https://themustangsource.com/forums/images/rank.gif)
![](https://themustangsource.com/forums/images/rank.gif)
Join Date: September 11, 2006
Location: Cumming, GA
Posts: 2,349
Likes: 0
Received 4 Likes
on
3 Posts
I just spent another hour messing with it. I was able to get a copy of the AS-BUILT for the PCM and even edit that and either trick the 2013 Calibration to load on the 2012 PCM or load the 2013 Part # in the 2012 PCM .. Niether worked.
Jim .. I think you should try again and see if it automatically sends you into a PMI ... if it doesn't .. then we know you did SOMETHING that we need to figure out how you did it.
Jim .. I think you should try again and see if it automatically sends you into a PMI ... if it doesn't .. then we know you did SOMETHING that we need to figure out how you did it.
#1250
Shelby GT350 Member
![](https://themustangsource.com/forums/images/rank.gif)
![](https://themustangsource.com/forums/images/rank.gif)
![](https://themustangsource.com/forums/images/rank.gif)
Join Date: September 11, 2006
Location: Cumming, GA
Posts: 2,349
Likes: 0
Received 4 Likes
on
3 Posts
Could you have possibly cancelled IDS while it was doing a PCM AS-BUILT Load?? That is the only thing that I could possible think of that may have corrupted your PCM. I do remember that your vehicle started and ran fine prior to you loading the new calibration.
What I remember you did is ...
1) You started a new Session
2) You typed in the 2013 PCM part Number
3) It immediately went into a PCM PMI
4) You typed in your own VIN ??? or 2013 VIN ??
5) It went to Ford and downloaded the files
6) It then started programming the 2013 Calibration.
What VIN were you using for your 2013 PCM ? Perhaps it had something to do with the VIN # and the PCM Part # ??
What I remember you did is ...
1) You started a new Session
2) You typed in the 2013 PCM part Number
3) It immediately went into a PCM PMI
4) You typed in your own VIN ??? or 2013 VIN ??
5) It went to Ford and downloaded the files
6) It then started programming the 2013 Calibration.
What VIN were you using for your 2013 PCM ? Perhaps it had something to do with the VIN # and the PCM Part # ??
#1252
Legacy TMS Member
![](https://themustangsource.com/forums/images/rank.gif)
![](https://themustangsource.com/forums/images/rank.gif)
![](https://themustangsource.com/forums/images/rank.gif)
![](https://themustangsource.com/forums/images/rank.gif)
Could you have possibly cancelled IDS while it was doing a PCM AS-BUILT Load?? That is the only thing that I could possible think of that may have corrupted your PCM. I do remember that your vehicle started and ran fine prior to you loading the new calibration.
What I remember you did is ...
1) You started a new Session
2) You typed in the 2013 PCM part Number
3) It immediately went into a PCM PMI
4) You typed in your own VIN ??? or 2013 VIN ??
5) It went to Ford and downloaded the files
6) It then started programming the 2013 Calibration.
What VIN were you using for your 2013 PCM ? Perhaps it had something to do with the VIN # and the PCM Part # ??
What I remember you did is ...
1) You started a new Session
2) You typed in the 2013 PCM part Number
3) It immediately went into a PCM PMI
4) You typed in your own VIN ??? or 2013 VIN ??
5) It went to Ford and downloaded the files
6) It then started programming the 2013 Calibration.
What VIN were you using for your 2013 PCM ? Perhaps it had something to do with the VIN # and the PCM Part # ??
I used a 2013 VIN for a GT auto:
1ZVBP8CF4D5209248
#1253
Shelby GT350 Member
![](https://themustangsource.com/forums/images/rank.gif)
![](https://themustangsource.com/forums/images/rank.gif)
![](https://themustangsource.com/forums/images/rank.gif)
Join Date: September 11, 2006
Location: Cumming, GA
Posts: 2,349
Likes: 0
Received 4 Likes
on
3 Posts
Yes, I did cancel IDS when I tried to load as built for the ACM, come to think of it. I did that because it was only allowing me to enter as built for a regular radio, and not for a nav. I couldn't get out of it, so I just closed IDS.
I used a 2013 VIN for a GT auto:
1ZVBP8CF4D5209248
I used a 2013 VIN for a GT auto:
1ZVBP8CF4D5209248
That was the only time you cancelled IDS? You did ATL CTL DEL and forced it ? Not sure how IDS forced during an ACM AS BUILT load would let you load the PCM .. but that is why its called a bug I guess ..
![Big Grin](https://themustangsource.com/forums/images/smilies/biggrin.gif)
#1255
Shelby GT350 Member
![](https://themustangsource.com/forums/images/rank.gif)
![](https://themustangsource.com/forums/images/rank.gif)
![](https://themustangsource.com/forums/images/rank.gif)
Join Date: September 11, 2006
Location: Cumming, GA
Posts: 2,349
Likes: 0
Received 4 Likes
on
3 Posts
I'm also thought a PMI would required reprogramming your keys ... but it did not ...
Also .. did you verify that your VIN is correct in the PCM now?
#1257
Shelby GT350 Member
![](https://themustangsource.com/forums/images/rank.gif)
![](https://themustangsource.com/forums/images/rank.gif)
![](https://themustangsource.com/forums/images/rank.gif)
Join Date: September 11, 2006
Location: Cumming, GA
Posts: 2,349
Likes: 0
Received 4 Likes
on
3 Posts
This sorta sounds like it ... Guy unplugged his VCM while programming.
Recovering a PCM/SJB when Programming has resulted in a Blank module:
NEVER DELETE THE ORIGINAL SESSION!
1. Obtain the original IDS that was used when the programming error occurred during Module
Reprogramming (MR) or Programmable Module Installation (PMI).
2. Disconnect the VCM from the DLC and the IDS.
3. Reconnect VCM to the IDS and then the DLC. Once reconnected the VCM icon should appear in the
corner of the IDS screen. If it does not, troubleshoot the IDS to VCM connection.
4. Locate the ORIGINAL vehicle session used when programming failed. This should be the last session
used in most cases. If it is not, use the session created on the date that the programming failed.
Starting with IDS release 71.01 and later, the IDS will highlight sessions with the failed programming
in red.
Note: If the original session is not listed in the previous session list, click the Recycling bin icon at the
lower right of the previous sessions screen. This will load any deleted sessions and allow you to look
through them. Double click to restore that session.
5. Once the session is loaded, the failed process should resume automatically.
6. If programming does not resume automatically, proceed to the Module Programming menu and select
the previously attempted process, Programmable Module Installation or Module Reprogramming.
7. Follow all On-screen instructions to complete the programming process.
8. Near the end of programming, the IDS will prompt you to select certain parameters. It is important to
make a selection for ALL parameters listed. If the correct selection is already highlighted, you must
still click that selection before clicking the Tick mark to complete the configuration.
9. The last screen on the IDS may list additional steps required to compete the programming process.
Recovering a PCM/SJB when Programming has resulted in a Blank module:
NEVER DELETE THE ORIGINAL SESSION!
1. Obtain the original IDS that was used when the programming error occurred during Module
Reprogramming (MR) or Programmable Module Installation (PMI).
2. Disconnect the VCM from the DLC and the IDS.
3. Reconnect VCM to the IDS and then the DLC. Once reconnected the VCM icon should appear in the
corner of the IDS screen. If it does not, troubleshoot the IDS to VCM connection.
4. Locate the ORIGINAL vehicle session used when programming failed. This should be the last session
used in most cases. If it is not, use the session created on the date that the programming failed.
Starting with IDS release 71.01 and later, the IDS will highlight sessions with the failed programming
in red.
Note: If the original session is not listed in the previous session list, click the Recycling bin icon at the
lower right of the previous sessions screen. This will load any deleted sessions and allow you to look
through them. Double click to restore that session.
5. Once the session is loaded, the failed process should resume automatically.
6. If programming does not resume automatically, proceed to the Module Programming menu and select
the previously attempted process, Programmable Module Installation or Module Reprogramming.
7. Follow all On-screen instructions to complete the programming process.
8. Near the end of programming, the IDS will prompt you to select certain parameters. It is important to
make a selection for ALL parameters listed. If the correct selection is already highlighted, you must
still click that selection before clicking the Tick mark to complete the configuration.
9. The last screen on the IDS may list additional steps required to compete the programming process.