F1 code

RedFX4 · #1 Fri, November 26th, 2010, 04:53 PM

What the devil does it mean? Showed up while trying to upload my custom tunes again after being at the stealership. I assume the buggers reflashed my PCM.

Please tell me I don't have to wait another 6 weeks to get my tunes redone

I hate this truck on its stock setting sooooo much. Drives like total crap.

RedFX4 · #2 Fri, November 26th, 2010, 06:07 PM

Can I re-download canned tunes and run them in the meantime?

ticopowell · #3 Fri, November 26th, 2010, 11:31 PM

Firstly what truck do you have? and I dont have a clue what that error means, but I do know you can run your truck on canned while you are waiting on custom tunes.

RedFX4 · #4 Sat, November 27th, 2010, 03:26 AM

Sorry its an 08 F150. The code popped up while it was writing the checksum file. After I wouldn't go away or anything until I unplugged it. I'm guessing it has everything to do with the PCM being reflashed.

***Jackpine*** · #5 Sat, November 27th, 2010, 09:51 AM

Red, I doubt you were "flashed" - The error code 0xF1 can sometimes appear during programming. Try this:

1. Leave the ignition key in the ON position.
2. Disconnect the Gryphon at the OBDII port.
3. Plug the Gryphon back into the OBDII port.
4. After getting to the main screen, wait 15 seconds for needed parameters to be loaded.

If you still cannot program the PCM successfully, contact PHP for assistance.

I THINK your programmer simply did not boot properly after you got your truck back from the dealership.

AND - please insure your battery is fully charged and that both the truck and the Gryphon are "warm" (now that cold weather is here).

- Jack

RedFX4 · #6 Sat, November 27th, 2010, 03:04 PM

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?