SCT might have boned me indirectly

TopherSho

New member
Long story really short..

AJPTurbo tunes are about 2 years old.  Was running the last rev without issue. reverting stock == no issues...

Tried a GH tune. It applied but that tune file broke the SCT handheld's flash file system. 

SCT fixes the SCT handheld with a bunch of SCT device firmware updates to handle newer tune files

Thought everything was ok..

Decided to go back to AJPTrubo tune

Revert to stock -  FAILED

--ACC disabled > 'malfunction' on dash
--collision disabled  > 'malfunction' on dash
--Running rich by 10% but no codes
--p1000 DTC  OBD II Monitor Testing Not Complete
--p1639 DTC    Vehicle ID Block Corrupted, Not Programmed
--p163f DTC  Transmission ID Block Corrupted, Not Programmed

Called SCT,  SCT reports 17 other cases with same/or extremely similar errors .. there is a firmware revision for SCT that may help.  we tried .. It did not.

So now im off to get the car flashed by IDS to rewrite the whole unit and cross my fingers.

But after that .. I have a feeling I cannot flash the car any more now that the SCT firmware is modified/updated because any flash back to stock will fail likely again... as a software guy I just cant shake the feeling i'm boned and flashing a tune will be a one way trip.


SCT advised the 2010/2011 Tarsus have a much larger number of flash related issues versus the remaining years.

also of note I have a fellow tuned SHO owner in town who has the EXCAT SAME issues after a GH update.
 
TopherSho said:
Long story really short..

AJPTurbo tunes are about 2 years old.  Was running the last rev without issue. reverting stock == no issues...

Tried a GH tune. It applied but that tune file broke the SCT handheld's flash file system. 

SCT fixes the SCT handheld with a bunch of SCT device firmware updates to handle newer tune files

Thought everything was ok..

Decided to go back to AJPTrubo tune

Revert to stock -  FAILED

--ACC disabled > 'malfunction' on dash
--collision disabled  > 'malfunction' on dash
--Running rich by 10% but no codes
--p1000 DTC  OBD II Monitor Testing Not Complete
--p1639 DTC    Vehicle ID Block Corrupted, Not Programmed
--p163f DTC  Transmission ID Block Corrupted, Not Programmed

Called SCT,  SCT reports 17 other cases with same/or extremely similar errors .. there is a firmware revision for SCT that may help.  we tried .. It did not.

So now im off to get the car flashed by IDS to rewrite the whole unit and cross my fingers.

But after that .. I have a feeling I cannot flash the car any more now that the SCT firmware is modified/updated because any flash back to stock will fail likely again... as a software guy I just cant shake the feeling i'm boned and flashing a tune will be a one way trip.


SCT advised the 2010/2011 Tarsus have a much larger number of flash related issues versus the remaining years.

also of note I have a fellow tuned SHO owner in town who has the EXCAT SAME issues after a GH update.




Can you please define "boned" for the class since we're not all software guys? 8)
 
SilvererSHO said:
TopherSho said:
Long story really short..

AJPTurbo tunes are about 2 years old.  Was running the last rev without issue. reverting stock == no issues...

Tried a GH tune. It applied but that tune file broke the SCT handheld's flash file system. 

SCT fixes the SCT handheld with a bunch of SCT device firmware updates to handle newer tune files

Thought everything was ok..

Decided to go back to AJPTrubo tune

Revert to stock -  FAILED

--ACC disabled > 'malfunction' on dash
--collision disabled  > 'malfunction' on dash
--Running rich by 10% but no codes
--p1000 DTC  OBD II Monitor Testing Not Complete
--p1639 DTC    Vehicle ID Block Corrupted, Not Programmed
--p163f DTC  Transmission ID Block Corrupted, Not Programmed

Called SCT,  SCT reports 17 other cases with same/or extremely similar errors .. there is a firmware revision for SCT that may help.  we tried .. It did not.

So now im off to get the car flashed by IDS to rewrite the whole unit and cross my fingers.

But after that .. I have a feeling I cannot flash the car any more now that the SCT firmware is modified/updated because any flash back to stock will fail likely again... as a software guy I just cant shake the feeling i'm boned and flashing a tune will be a one way trip.


SCT advised the 2010/2011 Tarsus have a much larger number of flash related issues versus the remaining years.

also of note I have a fellow tuned SHO owner in town who has the EXCAT SAME issues after a GH update.




Can you please define "boned" for the class since we're not all software guys? 8)


My fear is for MY car and at least one other Taurus I can see/touch locally .. that now the SCT handheld 4x is updated past 'whatever' was working it will not allow me/us to flash back to stock on 'new tunes' produced on updated ADVANTAGE systems.

What concerns me is the SCT team has not identified the issue.  They are aware it exists, but there is not a fix once the state I am in hits.

Ford will re-apply the full DMKJBLA firmware using IDS tomorrow.  Stay ''tuned'' .... /sad trombone/
 
bamsho said:
Thanks, I hwve updated tunes from Gearhead coming for my 2016 F150.  Putting on a XDI35 HPFP.


You should be fine,  you have newer ECU,  MUCH wider supported strategy .. my strategy code has ALWAYS been a f^&#king nightmare.  the ONLY tuner I have never had an issue with is AJPTURBO. 



 
Admin said:
@mattr66 might be able to provide some insight here?
It has nothing to do with the EPA unless it was the device update that removed egr delete functionality for the diesel tuning from years ago

Sent from my motorola edge plus using Tapatalk

 
TopherSho said:
bamsho said:
Thanks, I hwve updated tunes from Gearhead coming for my 2016 F150.  Putting on a XDI35 HPFP.


You should be fine,  you have newer ECU,  MUCH wider supported strategy .. my strategy code has ALWAYS been a f^&#king nightmare.  the ONLY tuner I have never had an issue with is AJPTURBO.


So my 2010 had the same strategy code. There were only 3 tuners who were able to get it tuned.. the other tuners had MAJOR issues... Gearhead, AJPTurbo, and LMS were the only three that could actually tune that strategy. Its a PIA for sure, cause even then, there were some interesting characteristics.
 
TopherSho said:
130$ for the flash.. fyi .. fingers crossed.. sphincter puckered

Mine as $125, and worked like a champ when I had ford update my strategy. I would make sure to remove the 3BAR and anything else you might have that would cause an issue with the stock tune. Usually its just the 3BAR.
 
;)  did that last night ... :D hung a note on the mirror with the requested strategy,  talked to the shop manager and pointed them to a previous Ford service ticket when we did this in 2017 :D..


I think that is as covered as I can get .. no more alternative vendors. :P  Back to the last AJPTurbo tune and get the RMA pipes installed and call it good.  sheesh!

1st world issues .... for sure ... but man im annoyed :D 
 
Ford service department trip #1
No CEL,  but still getting -

Collision warning - malfunction
p1000
p1635

Ford ''called it good'',  I had them take it back in as i code scanned it right in front of the service advisor and gave her a polite wtf eyeball ...


 
The 1635 is internal voltage reference bad... May be the reason the pcm bricked in the first place...

Sent from my motorola edge plus using Tapatalk

 
mattr66 said:

The 1635 is internal voltage reference bad... May be the reason the pcm bricked in the first place...

Sent from my motorola edge plus using Tapatalk



hmm got a link? 

I found this on DTC which logically sounds more likely since it is a muffed write to the ecu/pcm


https://www.dtcdecode.com/Ford/P1635


Make:Ford
Code:P1635
Definition:Tire/Axle Ratio Out Of Acceptable Range
Description:This DTC sets when the tire and axle information contained in the vehicle identification (VID) block does not match the vehicle hardware.
Cause:Incorrect tire size,  Incorrect axle ratio, Incorrect VID configuration parameters
Diagnosis: Using the scan tool, view the tire and axle parameters within the VID. They must match the vehicle hardware.
Component: PCM
 
TopherSho said:
mattr66 said:

The 1635 is internal voltage reference bad... May be the reason the pcm bricked in the first place...

Sent from my motorola edge plus using Tapatalk



hmm got a link? 

I found this on DTC which logically sounds more likely since it is a muffed write to the ecu/pcm


https://www.dtcdecode.com/Ford/P1635


Make:Ford
Code:P1635
Definition:Tire/Axle Ratio Out Of Acceptable Range
Description:This DTC sets when the tire and axle information contained in the vehicle identification (VID) block does not match the vehicle hardware.
Cause:Incorrect tire size,  Incorrect axle ratio, Incorrect VID configuration parameters
Diagnosis: Using the scan tool, view the tire and axle parameters within the VID. They must match the vehicle hardware.
Component: PCM

I am betting the p1635 is a result of the PP 3.15 axel ratio being programed in instead of the non-pp 2.77 .. fingers crossed.  HOPEFULLY the bad axel ratio is what is disabling the ACC/Collision warning system
 
TopherSho said:
TopherSho said:
mattr66 said:

The 1635 is internal voltage reference bad... May be the reason the pcm bricked in the first place...

Sent from my motorola edge plus using Tapatalk



hmm got a link? 

I found this on DTC which logically sounds more likely since it is a muffed write to the ecu/pcm


https://www.dtcdecode.com/Ford/P1635


Make:Ford
Code:P1635
Definition:Tire/Axle Ratio Out Of Acceptable Range
Description:This DTC sets when the tire and axle information contained in the vehicle identification (VID) block does not match the vehicle hardware.
Cause:Incorrect tire size,  Incorrect axle ratio, Incorrect VID configuration parameters
Diagnosis: Using the scan tool, view the tire and axle parameters within the VID. They must match the vehicle hardware.
Component: PCM

I am betting the p1635 is a result of the PP 3.15 axel ratio being programed in instead of the non-pp 2.77 .. fingers crossed.  HOPEFULLY the bad axel ratio is what is disabling the ACC/Collision warning system
That is in the vid block normally....

Sent from my motorola edge plus using Tapatalk

 
Back
Top