Stumble/Miss/Hesitation

[lbjailer]

Can someone please have Bill look at my Trouble Ticket, #94? I need to know if it is safe for me to plug my Gryphon in. I purchased a tune change at the same time I entered a trouble ticket about rough running. Theres been no action, and now I'm afraid to plug in the Gryphon. I cut and paste the results of the data reading from my Gryphon and it doesn't look right.

[Jackpine]

Originally Posted by lbjailer

Can someone please have Bill look at my Trouble Ticket, #94? I need to know if it is safe for me to plug my Gryphon in. I purchased a tune change at the same time I entered a trouble ticket about rough running. Theres been no action, and now I'm afraid to plug in the Gryphon. I cut and paste the results of the data reading from my Gryphon and it doesn't look right.

If you're asking, "Is it safe to plug the Gryphon into your truck?", the answer is YES. As long as all you do is plug it in, it simply acts as a monitor and cannot/will not modify anything in the PCM.

But if the question is, "Is it safe to program my truck?", I don't know. I'd have to know more about the "rough running" problem. Did you have it on all tunes? If it was just one tune, I'd stay away from that one unless you want to do more troubleshooting.

However, if there was never a question of getting the truck started after a tune, I can't imagine it would be dangerous to try a tune again. What did Bill tell you when the problem first surfaced?

- Jack

[lbjailer]

Hi Jack,
2 days (October 28th) after I submitted the ticket it was replied to from Bill. At the same time I also purchased a new tune. Since then I have not heard anything. I know I can plug it in and just use it to monitor functions on the truck, but because of what the log says (see below), I don't want to risk programming a tune. Luckily I had returend to stock.

Here is what my data reteivel says about the Gryphon.


The file -> stock_0.bin <- was not located.

The file -> stock_cs.bin <- has been stored as:
C:\Program Files\Power Hungry Performance\Pegasus Update Client\Data\1863_2010-12-27_12-55-13_stock_cs.egc

The file -> level1_0.bin <- was not located.

The file -> level2_0.bin <- was not located.

The file -> level3_0.bin <- was not located.

The file -> custom.bin <- was not located.

[Jackpine]

I'll see if I can get something off my Gryphon to validate what you got. At the moment, we're about to go out the door, so it will be tomorrow before I get back to this.

- Jack

[lbjailer]

thanks

[Jackpine]

OK, lb - I connected my old Gryphon to my PC, hit [Utilities]->[Read Critical Files], and this is what I got:

The file -> vid.bin <- has been stored as:
C:\Program Files\Power Hungry Performance\Pegasus Update Client\Data\1047_2011-01-15_17-13-36_vid.egc

The file -> stock_0.bin <- has been stored as:
C:\Program Files\Power Hungry Performance\Pegasus Update Client\Data\1047_2011-01-15_17-13-36_stock_0.egc

The file -> stock_cs.bin <- has been stored as:
C:\Program Files\Power Hungry Performance\Pegasus Update Client\Data\1047_2011-01-15_17-13-36_stock_cs.egc

The file -> level1_0.bin <- has been stored as:
C:\Program Files\Power Hungry Performance\Pegasus Update Client\Data\1047_2011-01-15_17-13-36_level1_0.egc

The file -> level2_0.bin <- has been stored as:
C:\Program Files\Power Hungry Performance\Pegasus Update Client\Data\1047_2011-01-15_17-13-36_level2_0.egc

The file -> level3_0.bin <- has been stored as:
C:\Program Files\Power Hungry Performance\Pegasus Update Client\Data\1047_2011-01-15_17-13-36_level3_0.egc

The file -> custom.bin <- has been stored as:
C:\Program Files\Power Hungry Performance\Pegasus Update Client\Data\1047_2011-01-15_17-13-36_custom.egc

This programmer has two custom tunes in Levels 1 and 2 and a canned tune at Level 3. As everyone sees, there are files for each level and a "custom" file.

So, I brilliantly conclude, lbjailer, that the code in your Gryphon is corrupt. (I'm being sarcastic here - it doesn't take a mental giant to see this, does it?)

Here's what I'd like you to try - I can't see how it will hurt anything:

1. I want you to return your Gryphon to the "canned" state. Please connect it to Pegasus and click on [Updates]->[Gryphon Update Manager] and apply both the firmware and calibration updates.
2. If that process seems to go smoothly, click on [Updates]->[Custom File Download] and apply anything you are offered there. This should reinstall your custom tune(s).

You should be using Version 2.02.0828 of Pegasus for this. If your version of Pegasus is old, it should try to update itself once you start it (if you're connected to the internet).

Now that you've gotten through all this, try the [Utilities]->[Read Critical Files] process again. Since you won't have a "stock" tune stored anymore (it gets stored in your first programming session), that file may not be found, but I think the others should be. If they are, you should be good to go.

Let us know what happens. If you get confusing results, Bill will have to get involved and I'll do my best to get his attention.

- Jack

[lbjailer]

Thanks, I will try again. I need to get my HEX code into the Gryphon, so I will try to see if it will load (save) my stock tune, and not make any changes to the ECU, then plug it in to Pegasus.