f1 error and timing

[drug delivery]

Per an e-mail sent to Corey this morning.

I tried to load the 93 performance tune this morning but got the "f1" error. This error stayed on no matter what so I unplugged the Gryphon and plugged it back it. The Gryphon never went through the procedure where you see the program load and update from 0% to 100%, so I assume it never took. Prior to the error, I changed the timing since I only had 87 octane in the tank at that time.

My question is, was the time change saved or no?

When I plugged the Gryphon back in I returned the truck to the stock tune then loaded the 93 tune again without issue. This was later in the day. When I loaded the 93 tune the second time, I asked the programmer to go back to the previous setting, so I suppose this should have undone the timing change, but again, I just want to be sure.

I did follow the turn key on/off procedure but I don't recall if the error popped up before or after that.

thanks,

Phil

[Power Hungry]

If the programming session did not complete successfully, then the timing adjustment was not stored. The next time you programmed, it was with an unmodified 93 Performance tune.

Hope this helps.

[drug delivery]

If the programming session did not complete successfully, then the timing adjustment was not stored. The next time you programmed, it was with an unmodified 93 Performance tune.

Hope this helps.


:2thumbs:

thanks.

Going back to the previous setting is back just one right? So if you make 10 changes and go back to the previous setting, you only go back to the 9th change right?

[Jackpine]

:2thumbs:

thanks.

Going back to the previous setting is back just one right? So if you make 10 changes and go back to the previous setting, you only go back to the 9th change right?

No, I don't think that's right at all. As far as I can tell, the custom option changes you make are cumulative - so any change you make is "added" to any previous changes you had.

You could go through and "zero" them all out though.

- Jack

[Power Hungry]

Load previous settings will load the LAST custom options entered. There is no buffer or history.

[Jackpine]

Load previous settings will load the LAST custom options entered. There is no buffer or history.

Wait, stop! We may be saying the same thing under different assumptions. I enter Custom Options and "Load Previous Settings" as my first option. Now I make a few changes, and select "Done" to start the programming. Doesn't this create a new "Previous Settings" file that is the sum of both the previous options and new ones I've entered? So, couldn't this be thought of as cumulative?

But, if you chose a tune, then open the Custom Options menu and select "Done" as your first action - I believe you are saying this will effectively "wipe out" all previous custom settings you may have had (and additionally may load bogus values for GR and TS).

AND, I want to verify one more thing. Custom options are not tune specific are they? In other words, if I set custom options for a Level 1 tune, then later change to Level 3 and "Load Previous Settings", I get the options I set for Level 1 back again, don't I?

(I'm glad you live as far away as you do - I might be afraid you'd come beat me up over my failure to understand this "feature" if you were closer). :o

- Jack

[JWBFX4]

wow I feel like I start figuring it out about this load previous settings...then I get more confused:hehe:

[drug delivery]

Wait, stop! We may be saying the same thing under different assumptions. I enter Custom Options and "Load Previous Settings" as my first option. Now I make a few changes, and select "Done" to start the programming. Doesn't this create a new "Previous Settings" file that is the sum of both the previous options and new ones I've entered? So, couldn't this be thought of as cumulative?

Boy, I am confused. For example. If someone changes their timing +1, then at a later time changes the timing again by +2, then the net effect is +3. However, if before making the second change they had loaded previous settings, then the second change of +2 is a net of +2. Under this scenario it's only cumulative based upon what was done post "previous settings".

But, if you chose a tune, then open the Custom Options menu and select "Done" as your first action - I believe you are saying this will effectively "wipe out" all previous custom settings you may have had (and additionally may load bogus values for GR and TS).

Are you saying when you simply select "Done" that the original tune loads? I thought that the custom changes would basically wipe out the original tune and you are left with what changes you've made, cumulative or not.

AND, I want to verify one more thing. Custom options are not tune specific are they? In other words, if I set custom options for a Level 1 tune, then later change to Level 3 and "Load Previous Settings", I get the options I set for Level 1 back again, don't I?


I too would like an answer to this.

:crazy:

[Power Hungry]

With examples, this will be a long post so bear with me. (Just don't bare with me... :1moon:)

Starting with selecting Custom Options, you make the following changes:

WOT 1-2: 5300 RPM
WOT 2-3: 5300 RPM
WOT 3-4: 4800 RPM

Rev Limit: 5800 RPM
Speed Limit: 140 MPH

Tire Size: 2662mm
Gear Ratio: 3.73

Timing: +1.5 Deg.

You program the vehicle and everything is fine. Then you decide to make changes. You go into Custom Options and then select Load Previous Settings. Here's what you end up with:

WOT 1-2: 5300 RPM
WOT 2-3: 5300 RPM
WOT 3-4: 4800 RPM

Rev Limit: 5800 RPM
Speed Limit: 140 MPH

Tire Size: 2662mm
Gear Ratio: 3.73

Timing: +1.5 Deg.

Now you make the following changes:

WOT 1-2: 5200 RPM

Timing: +2.0 Deg.

Idle: +50 RPM

What you end up with is this:

WOT 1-2: 5200 RPM
WOT 2-3: 5300 RPM
WOT 3-4: 4800 RPM

Rev Limit: 5800 RPM
Speed Limit: 140 MPH

Tire Size: 2662mm
Gear Ratio: 3.73

Timing: +2.0 Deg.

Idle: +50 RPM

These options do not change depending on the level you are programming. +2.0 Degrees of timing is the same for 87 Towing as it is for 93 Performance (ie. Level 2 and Level 3 respectively.)

If you select Custom Options, do NOT do Load Previous Settings, and then hit Done to begin programming, it does NOT clear any stored custom option status, it just doesn't use them this programming session. However, the next time you program and press Load Previous Settings, they will still be active. In this sense, all custom settings are cumulative, even those you made multiple sessions ago. Once an Option has been flagged as custom and a value selected for it, it will always be included in the Load Previous Settings.

What I do think would be handy is a way to clear out any currently flagged custom options so it would be possible to start from scratch. I'll probably use a manual option like "Clear All Custom Settings" which will reset the status of all custom options.

Does this make any more sense now?

[drug delivery]

To help me further clarify this issue. Regardless of what changes are made, once they are activated by completing the programming session, these settings, whatever they may be, load each time. If this is the case, I'm not seeing the usefulness of the load previous setting options since the programmer would only be loading what is already saved, as shown in the first two tables of your example. The feature seems redudant in this format. I think this quote it what summarizes this.

However, the next time you program and press Load Previous Settings, they will still be active. In this sense, all custom settings are cumulative, even those you made multiple sessions ago. Once an Option has been flagged as custom and a value selected for it, it will always be included in the Load Previous Settings.

However, the next quote below seems to be saying that the Load Previous Settings options can clear stored custom options, but only when chosen in the proper sequence. The two quoted statements seem to contradict each other regading the use of Load Previous Settings.

If you select Custom Options, do NOT do Load Previous Settings, and then hit Done to begin programming, it does NOT clear any stored custom option status, it just doesn't use them this programming session.


What I do think would be handy is a way to clear out any currently flagged custom options so it would be possible to start from scratch. I'll probably use a manual option like "Clear All Custom Settings" which will reset the status of all custom options.

It's people like me who need this option to be sure we don't screw anything up. :crazy: I'll get it eventually, but there doesn't seem to be any way to know if we are running the original tune or a custom, unless the unit is reflashed with an update back to original form.