Thread: F1 code
View Single Post
  #9  
Old Sun, November 28th, 2010, 08:09 PM
Jackpine's Avatar
Jackpine Jackpine is offline
PHP Groupie
 
Join Date: Nov 2008
Location: Among Elk, Deer and Javalinas on the Mogollon Rim in Aridzona
Posts: 3,243
Jackpine is a name known to allJackpine is a name known to allJackpine is a name known to allJackpine is a name known to allJackpine is a name known to allJackpine is a name known to all
Default

Quote:
Originally Posted by RedFX4 View Post
I checked the HEX code in my Pegasus registration and it no longer matched what the Gryphon reads in my truck once I got the Gryphon unfrozen.

Pegasus : RDXG3B3
Gryphon/Truck : RDXG6B3

I think I'm just SOL. Is there a quicker turn around on getting tunes reworked for a new HEX than getting them from scratch? I put in a request already.

I should also mention that when I tried programming the custom tune in again I got the same message. Error code F1 (no 0x before). The file is not yet supported. I've seen the same issue posted but never an explanation of the issue, except for one where the S/N was buggered. I've used the tunes prior with no issues so why would it give me that error? Can this same error be displayed when the PCM has a different HEX code than what the tunes were for?
Well, you now have a different "version number" in the identification for the "stock coding" of your PCM, and yes, this means you were "reflashed". It's a puzzle to me why they would have changed the version and nothing else though. Was your truck built for a different part of the country/world than where it is now?

And sadly, this looks like a remake of the tunes you have. Custom tunes will not work with a new hex code.

- Jack