Submitted a ticket on 10/23/2010 Ticket number 89.

Recieved a responce on 10/30/2010

I have yet to see a responce since.

:shrug::cursin::censored1::yikes2:

Gryphon *Blank*
 

I took truck to dealer today, removed gryphon and returned to stock. I tried to update after Pegasus update file was installed. My Gryphon is blank now. No HEX code. There is no way I am going to try and program the truck now. I need to find a way to restore the Gryphon. I plug it in and the software says it can't locate the Gryphon, but I can see it is doing something when I plug it in. I have rebooted my PC and the Gryphon and still no luck. I updated my trouble ticket #94. I copied and paste my results of reading critical files and all of them say they are blank.
I plugged it in the truck and it displayed the HEX, but I too afraid to try a program.

When you say "it is doing something", what do you mean?

Normally, if a Gryphon is plugged into a PC and Pegasus is not running, or if Pegasus can't connect to the Gryphon, the Gryphon's screen will be red.

When Pegasus connects to the Gryphon, the screen turns green - no writing appears on the Gryphon's screen. What does yours do?

Is it possible you have a faulty USB cable or USB controller? Does another device connect properly through them?

And, is it possible your device driver is corrupt in your PC? See: http://forum.gopowerhungry.com/faqs-...tallation.html If this looks at all possible, follow the directions there to reinstall your drivers.

It really doesn't sound like there's anything wrong with your Gryphon if it recognizes and connects to your truck. I suspect a problem in your PC.

- Jack

Hi Jack, Thanks for your reply. I uninstalled and reinstalled like you suggested. I followed the instructions as your link instructed. My screen does turn green, it shows my serial #. I'm connected on Com 8. My HEX is missing from the registration. (calibration). So since it changes to green that means it is recognized but wont update. Is there a way to force the HEX code? (I'm running XP on a Laptop).

Thanks for telling me all this. It really says your Gryphon is fine, but that for some reason, Pegasus is not seeing your hex.

And, I'm sure you've tried clicking on the [Retrieve] button in the [Help]->[Registration] screen of Pegasus? (Because as far as I know, that's the only way to input the "hex/calibration" code.)

I just clicked on the [Clear] button in Pegasus with my old Gryphon connected, and that blanked out all the windows except for the "device type", then I clicked [Retrieve] and it loaded my Serial number, Model Number, and Calibration.

I'm using the most recent version of Pegasus now, which is V2.02.0828.

Regardless, if you can't get it to show the calibration code in Pegasus, there's no harm in trying to update the device.

I think you are trying to reinstall custom files? If so, I'd first restore the Gryphon to its "canned" state. While connected to Pegasus, click on [Updates]->[Gryphon Update Manager]. Apply BOTH the firmware and the calibration updates. That should take you back to "canned". Then, click on [Updates]->[Custom File Download]. This should restore/upload the custom tune files you are trying to get.

If this does not work, there is probably a S/N error in your custom files on PHP's server and they will have to get involved. As far as I know, your custom files are matched only to your unit's S/N for download.

Let me know if you are successful with any of this. But, I honestly think your unit is safe to use on your truck.

- Jack

Thanks. I did try to load canned tunes and thats where it says it cant find the Gryphon. I did the retireve tool and everything but the HEX shows up. My serial # is there. I sent in a trouble ticket (#94) back in October and also purchased a new tune and thought maybe the new tune was there. Thats when the Pegasus installed "it's" update, and then the Gryphon lost my HEX and began not finding the Gryphon on the USB, although it shows it being there on the registration. The screen goes green, and when I do the custom tune download it shows the files being downloaded and when it gets to the end, it says it can't see the gryphon.
What would happen if I installed Pegasus on my desktop (Windows 7) and try it there?

I am too, still waiting on an answer. Ticket #95. Posted 10/29.

OK, I'll try to get Bill's attention on this for both of you.

- Jack

Same here, I'm ticket #90. I'd really appreciate a status update (of any type). It looks like this is a common issue with a certain flash (possibly the first code V (flexfuel) engines?). Hopefully Bill can figure this out so that all the canned tunes work. I'm still using level1 - tow only; and would really like to use level2, thats one of the reasons why I choose this unit.

thank-you
Matt

Matt - please complete as much information as you can in your User Profile. Specifically, your engine's hex (calibration) code, your truck's Model Year, your phone number, Gryphon Serial Number, etc. Anything that might help Bill easily address your situation.

- Jack

Just to keep this thread going, please all continue to make updates regarding resolution of this issue. Seems that it is a common issue among quite a few of us. I've experienced the issue 2 or 3 times in the past 3 weeks, and again, I've already received an update. I will monitor progress with everyone before do anything else on my end.

Hi Jack, thanks for the reply. I will update my profile here as requested. Just my 02 cents though, I deal with a 25,000 user environment in my line of work, and the one thing that we preach is only ONE area for each dataset/value. Once you start manually putting in the same information in different areas, the data is considered useless as it may not be accurate. If one thing changes, you (the user) have to go back to multiple areas to update it. And the service person (PHP in this case) doesn't know which data is accurate or which source they should use. So we preach that data should not be manually replicated anywhere, ever. And everyone knows the ONE area where data should be updated. In this example, Bill/PHP would know that he can ALWAYS count on the information in the ticket, as the info he finds elsewhere may not be accurate. For a smaller company or user base this is not as big of a problem, but as you grow, it will become completely unmanagable.

Just my 02 cents... regardless of that, I would be happy to update my profile here as well if that is helpfull to PHP, and will do so shortly.

thanks
Matt

EDIT: profile updated jan4/2011 11:30CST

Thanks for updating that. The profile is usually the first place us moderators look because many people fill that in when they first join. I would consider that to be more accurate because while filling out a service ticket the user would probably be more stressed and more prone to errors. The profile is also a good refrence when things dont seem to add up. One example would be is a 5.6L engine with the hex code of OKDG1A6. Obviously there was a single number error somewhere in the engine size but that is for sure a 4.6L because of the first part of the HEX code. Sometimes, like you said, things get typed in wrong but it helps to have something to look back on.

How often do the 'canned tunes' typically get updated? Have they been the same for years, or are they constantly being tweaked? How do I know if I have the latest canned tunes? I assume I compare the version/software # on my Gryphon, but what is the current version available?

thanks
Matt

They get very minor tweaks ever so often. Probably wouldn't hurt to plug the programmer into the computer and check for updates.

So we can just do a full update through the Update Manager....then go back to Targeted Functions to restore custom tunes....correct?

Pefect, just was I was looking for.

Also, anything if I need to know if I change my PC I use to update? I had installed Pegasus on my laptop and when I created my trouble ticket, I noticed it stores the 'computer name' in the ticket. I will be using my new PC from now on, so i will have to install Pegasus on that. Will I need to update the computer name on my open ticket?

thanks
Matt

For the monochrome gyphons, yes.

For the CS and CTS gryphons, not without being instructed by Bill.

That'll work. Just make sure that you update pegasus when you install it onto the new computer. I think the link on the website is an older version.
And yes, update the computer name and any other relevant information on the open ticket.

Fail Safe mode
 

Well today I had a new problem. I was leaving work and my truck went into the Fail safe mode. I stopped on the side of the road, turned it off and started back up and everything has been fine since.

Not sure if this can be linked with the rough running problems that I have been having.

Mike

Were you able to check for codes?

I ran the Pegasus update. returned message Gryphon updated successfully.
Firmware Version: v3.10.1063 .Calibration Version: v2.04.1012 .

Went to plug it into my truck, and as soon as the gryphon is plugged in it says 'external memory needs to be reflashed - call tech support '.

argh. ticket #136.

Is there no way to reflash with the current software? I guess the pegasus client detects that the flash is 'current' and there is no option to reapply. Should be easy enough if there was that option.

edit: doesn't look like it. I guess if I had custom tunes (I don't) I could reinitiate that download and it would fix itself. But as it is, it looks like PHP will have to throw the canned tunes in the 'custom' bin so it can be reflashed.

same kinda issue as this, except mine didn't have a comm timeout. it all seemed to work fine. I can still see my serial #. http://forum.gopowerhungry.com/close...t-timeout.html

Wow...what is that exactly? What happens when a truck goes into fail safe mode?

I did not check codes when it happened because I totally forgot that the Gryphon could do that... LOL!! But I just checked now and no codes show up.


BigSur
Engine fail safe popped up on the information screen. I was only pulling out of the parking lot at work so I immediately stopped and turned the truck off. I am not exactly sure what happens in fail safe mode. It just doesn't sound like a good thing. Everything seems fine now. Nothing out of the ordinary happened when the message popped up.

Update to my post #123, I installed pegasus on a different PC, and was able to reflash the unit with the same firmware/calibration this same. hopefully when I plug it into my truck the 'memory' error is no longer there.

but then we are still back to the hesitation/missing issue :(

"Failsafe" is actually designed to get you home if your truck engine overheats. (It's also known as "limp home mode"). Basically, the PCM shuts down spark and fuel to half of the cylinders so that the engine can run cooler.

As I said, it's supposed to be triggered by overheating, but it seems that the PCM can apply this strategy any old time - possibly caused by a false sensor signal. If you're really paying attention, you'll see the temperature gauge peg on full hot as it goes into failsafe mode. The PCM is actually moving the temp gauge there, since it is not actually telling you what the coolant temperature is (there's no sensors for that value - it's inferred by the PCM from the Cylinder Head Temperature).

The fact that an engine shutdown and restart often clears this condition is almost a sure sign (to me) that some sensor is malfunctioning.

- Jack

Got the fail safe error again today. I immediately checked for codes and this this is what I got. And again I turned her off and started back up and all was good. Same I was leaving work and as soon as I pulled out of the parking lot bang, fail safe.

P061B Internal Control Module Torque Calculation Performance

Anyone have any idea what this is?

After reading a bit in the forum, I see that this code may be related to the tune. Everything that I have seen says canned tunes, but I am running a custom 87 perf tune. Please help!

Does your truck throw any codes when this happens? How about fuel quality? Is it possible you have bad fuel, water in it, bad fuel filter? If it were me, I would add some water remover, premium fuel, new filter, and octane booster. Why? Cuz this could very well fix your problem and even if it doesn't it still will be good for your truck. A very cost effective fix or atleast a beneficial way to rule out a problem. Hope this helps.......

More on the issue; it seems to happen most at around 25-30mph, rpm around 1500-1600.

I also have noticed that at idle (it is also missing at idle), that the spark advance is not steady, it is constantly moving around from 11 to 18 degrees. This is cold, warmed up, been running for an hour, it doesn't matter. Definitely not good for a stable idle.

Matt

Ticket #94
 

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

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.

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

thanks

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

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.

I don't think you will get the hex code into the Gryphon until you do your first programming session.

If I'm right, what you might try is:

Restore the canned tunes and then program your truck to the Level 1 transmission tune (no customizations). This will also store your stock tune into the Gryphon.

Return your truck to stock and THEN connect the Gryphon back to Pegasus to proceed.

- Jack

What he said. :D

Unable to locate the file specifed by the target instructions. Process failed.

Update failed. Please contact your vendor for assistance.

Here is what Pegasus said.

i'm going to try it on my desktop running windows 7 and see if that works

I must be having issues with my Laptop. I installed on myt desktop and everything seemed to have worked. I am now going to plug it in my truck. I am still waiting for my new custom tune and a response to my trouble ticket #94.
Thanks for your time Jack.

Laptops can easily be a problem. They have limited power output at the USB ports (come are better than others). Some laptops simply cannot communicate properly with the Gryphon. I have a laptop that won't backup on an external hard drive, even if I use a "two USB plug" connector with it. However, if the drive has an external power supply, it will work.

- Jack

Any updates to this guys? Has anyone applied updates that seemed to have resolved the issue? I'm in the same boat I have been. It still happens, but it's very seldom....so seldom that I'm okay with it.

I wish someone would at least confirm this issue and that it is being worked on. I'm happy with the canned tunes but paid for custom tunes. The custom tune seems to be the cause this issue.

I agree b/c it didn't happen on my canned tow tune either....only the 87 custom performance tune. It WOULD be nice to get an update, but it is what it is. I like my custom tune too much to switch off of it, so I'll just deal with it for now.

I can only use canned tune #1. #2 is what gives me hesitation issues.

Mods, can you please alert Bill? I have been waiting since end of October and have only had one response saying it would be looked at soon. I essentially have a really expensive gauge reader, I could have just kept my Scangauge if I wanted that.

If it was a custom tune issue I could see, but this is a canned tune.

Matt

Matt - the problem you are describing sounds a lot like a dirty throttle body or dirty MAF sensor or both. Has anyone suggested this possibility to you and/or have you checked those two items? Without going back through 15 pages of posts, I can't tell, and I'm reluctant to do that - which brings me to this:

The thread has become essentially useless because it is so long and is composed of posts that often describe different problems. At the moment, I can't easily tell who has an outstanding issue and who doesn't. I'm sure Bill would have no better success. We Mods have fallen down on our duties here and I've decided there's really only one solution - to close the thread.

Please, if you are having an issue with anything, create a thread in this forum: http://forum.gopowerhungry.com/general-support/ Do NOT "piggyback" on someone else's thread here, even if your problem is identical! Create your OWN thread for YOUR problem! If you want to suggest a solution or ask a question to clarify the problem that the thread OP is talking about, those would be "legal" posts in someone else's thread, but nothing else.

And, probably the BEST way now to get Bill's attention on a problem is to submit a "trouble ticket": Support Login Please use that method too.

I hope no one feels "stepped on" here. I'm NOT putting anyone down, but I AM trying to get you who need it, useful help.

Thanks for understanding.

- Jack