So far.... Nothing but Problems

[twintips_17]

Originally Posted by Power Hungry

An "F1" error can mean a couple things (in order of likelihood):

1) The calibration (HEX) code was not properly identified when the unit was plugged in. In most cases this occurs when then key is not in the ON position when plugging the unit in. This can also occur if the battery is disconnected or goes dead and the unit is not properly reinitialized (disconnect, turn key ON, reconnect) when power is restored.

2) The custom files built do not match the vehicle's HEX code. This can occur if the vehicle has been reflashed since the original order was placed or the since we were notified of the HEX code.

3) For canned tuning, the PCM calibration simply isn't supported yet. This can be resolved with future updates but we need to know what the calibrations are in order to make those updates.

As far as programming, if you do not turn the key to the off position after programming (including if the programming fails with an "F1" or "Checksum" error), the vehicle will not immediately start. This is because the PCM is still in "Programming" mode. You must return to the main menu, or in some cases disconnect the unit to exit the programming mode. Then you can simply turn the key "OFF" and restart the vehicle.

The Level 3 is written for 91+ octane. If you could let me know what your HEX code is I can take a look at the file and see what the problem is. Also, what is you dad's HEX code.

Not sure what the problem is with Pegasus. What do you mean by "it won't sync"? Does the software not detect the programmer? Does it not connect with the server?

Take care.

Thanks for the info. There is a lot there. First off I am running the canned tunes as I have not gotten my custom tunes.

Second I figured out that the vehicle will not start until it is turned off and then back on due to some trial and error.

I wrote down all my info when it through the code. IT is as follows.

Boot: 2.63.4860
Firmware: 3.2.596
Calibration: 1.4.580
Hardware: 13
Serial #: 1574
Bodyversion: 2.50.5734

Hex on my truck: 0DAL1EW1.HEX

I can’t get my dad’s as he away right now.

As far as the unit not syncing. I’m lost there. I synced it last night to do the first update. It did small vehicle calibration update or something. I can’t remember. All those numbers are before i did the update. After the update it worked on my truck only in level 2. Didn't try level 1. It worked on my truck and turned around and wouldn't work on his truck.

The unit synced last night to do the updates but I have tried to sync again sever different times and have even uninstalled/reinstalled the software and it still won’t sync.......

I am going to go out right now and program my truck back to level 2 and see if i get any errors or anything.....

[Jackpine]

Originally Posted by twintips_17

Thanks for the info. There is a lot there. First off I am running the canned tunes as I have not gotten my custom tunes.

Second I figured out that the vehicle will not start until it is turned off and then back on due to some trial and error.

I wrote down all my info when it through the code. IT is as follows.

Boot: 2.63.4860
Firmware: 3.2.596
Calibration: 1.4.580
Hardware: 13
Serial #: 1574
Bodyversion: 2.50.5734

Hex on my truck: 0DAL1EW1.HEX

I can’t get my dad’s as he away right now.

As far as the unit not syncing. I’m lost there. I synced it last night to do the first update. It did small vehicle calibration update or something. I can’t remember. All those numbers are before i did the update. After the update it worked on my truck only in level 2. Didn't try level 1. It worked on my truck and turned around and wouldn't work on his truck.

The unit synced last night to do the updates but I have tried to sync again sever different times and have even uninstalled/reinstalled the software and it still won’t sync.......

I am going to go out right now and program my truck back to level 2 and see if i get any errors or anything.....

Is it possible you tried using the Gryphon on your Dad's truck without first restoring yours to Level 0 (stock)? You can only program one truck at a time with these things, you know.

- Jack

[twintips_17]

Originally Posted by JackandJanet

Is it possible you tried using the Gryphon on your Dad's truck without first restoring yours to Level 0 (stock)? You can only program one truck at a time with these things, you know.

- Jack

Nope. I know that one....

So here is an update. I went out and programmed my truck to towing. Then I let it sit while i went in to workout. Afterwards I came out and tried extreme again. Except this time I didn't change the tire size. Just hit program and let it do its thing.

This time the tune worked. So that leads me to believe that I messed up the tire sizing adjustment. But would that effect how the engine ran? I didn't even move an inch when I tried the first time.

As far as it not syncing….. I have yet to try that. I know it has the most current updates cause i updated it last night.

I think I will try it again tonight on my dad’s truck. He wants to feel the difference before he shells out for one.... He has a more stock truck so he wants to do it on his.

The gryphon canned tunes are still not hex specific? Are they?

[Jackpine]

Canned tunes are not hex specific, and, since your truck is pre-04, I'm assuming your Dad's is too? If so, the programmer should work on either truck.

It seems to me that most of the problems I've read about concerning Edge and Gryphon programmers occur right after a firmware update. This leads me to think that there is something that is easy to do wrong in this process (but I can't think what it would be).

- Jack

[twintips_17]

Originally Posted by JackandJanet

Canned tunes are not hex specific, and, since your truck is pre-04, I'm assuming your Dad's is too? If so, the programmer should work on either truck.

It seems to me that most of the problems I've read about concerning Edge and Gryphon programmers occur right after a firmware update. This leads me to think that there is something that is easy to do wrong in this process (but I can't think what it would be).

- Jack

I dont know. THis is my first experiance with the new 13 firmware. ALl my past edges(3 of them) were version 4.xx.xx.

I have noticed quite the changes so far. You lose a lot of menu options like data streaming and stuff.... Maybe its still there and i just havn't found it but im pretty sure i have been through all the menus.

HIs truck is an 01 set up just like mine. Except bone stock.

He must have bad luck. The first time we tried to do it on his expy a year and a half ago we learned how important it is to have good battery voltage.... One reflash and we were back on the road. LOL So then we try on his newer screw...(01) And we run into problems. I have never once had a no start, false programing, or any other issue when programing one of my f150's.

Untell now.....

All seems ot be fine now. But it still puzzles me as to why it wont work on his truck.

[twintips_17]

Im going to try a few more things tonight with syncing hte unit and also programming my dads truck. You guys are to busy to waste your time if i can figure it out. Thanks.

[twintips_17]

I have narrowed it down to human error. LOL

I just did a "custom" canned towing tune and it wouldn't run. It would start.... Rev up and die..... I messed with the timing a bit due to the fact that I am running 91 octane. One version 4.xx.xx you could move it in .5 increments. So I went to move it and it was moving in .25 increments.....

So I was like maybe it’s a more precise way.... I went to go move it the normal 2.5 I have been doing for 3 years and it would only go as high as 2.00.

So I decided to only bump it .5 and see what happens.... And look what I got. LOL

The manual still states the same principle rule for timing adjustment. In fact the manual looks like its a bit out dated to the new version 13...

So any help with the timing adjustment?