My tune author was not familiar with that error.
I am trying to get my car to pass emissions so the only things he had changed was to enable rear O2 sensors and enable adaptive learning. That tune file caused the P060C error.
He sent me another tune file that only had the rear O2 sensors enabled ...
Search found 4 matches
- Tue Dec 01, 2009 4:06 pm
- Forum: Predator Ford Gas
- Topic: Mustang gt throwing P060C PCM error with custom tune
- Replies: 2
- Views: 2674
- Mon Nov 30, 2009 9:20 pm
- Forum: Predator Ford Gas
- Topic: Mustang gt throwing P060C PCM error with custom tune
- Replies: 2
- Views: 2674
Mustang gt throwing P060C PCM error with custom tune
I have a U7140 Predator for 06 mustang gt running latest firmware (9r03).
When I transfer a custom tune file I get two error codes:
P060C - PCM internal control module main processor performance
P1000 - OBD not ready
When I revert back to stock tune, I get no trouble codes. I saw in another post ...
When I transfer a custom tune file I get two error codes:
P060C - PCM internal control module main processor performance
P1000 - OBD not ready
When I revert back to stock tune, I get no trouble codes. I saw in another post ...
- Mon Nov 30, 2009 9:10 pm
- Forum: Custom Tune Support
- Topic: Predator won't take the custom tune file anymore.
- Replies: 2
- Views: 2991
RE: Predator won
I called tech support and talked with Mike. He said the error was most likely caused by the tuning file not being associated with the original stock backup. I contacted my tuner and gave him my stock file. He then rebuilt the tune file and it loaded on the diablo correctly.
This problem is now ...
This problem is now ...
- Sat Nov 28, 2009 4:24 pm
- Forum: Custom Tune Support
- Topic: Predator won't take the custom tune file anymore.
- Replies: 2
- Views: 2991
RE: Predator won
I am having this exact same problem with the exact same error message.
I saw the other posts regarding the error and all seem to mention checking/unchecking the compress send option. I have tried both options and both produce the error. What I noticed is the message appears at the same file ...
I saw the other posts regarding the error and all seem to mention checking/unchecking the compress send option. I have tried both options and both produce the error. What I noticed is the message appears at the same file ...