Power Hungry Performance Forum

Power Hungry Performance Forum (http://forum.gopowerhungry.com/index.php)
-   Gryphon Programmer (Disabled) (http://forum.gopowerhungry.com/forumdisplay.php?f=7)
-   -   So far.... Nothing but Problems (http://forum.gopowerhungry.com/showthread.php?t=587)

twintips_17 Tue, February 24th, 2009 09:33 PM

So far.... Nothing but Problems
 
Got my gryphon in the mail today....:happy-dancing:

Looks sweet in all black... :drool2: Love the mints by the way Corey!!!:drool2:

Anyways I went out and drove it tell I got the temps up to normal and then I stopped and plugged it in to program it. I went through all the steps spot on just like I have done in the past with my edge.

It went fine. Downloaded my stock files and then made a checksum file. But then it gave me an error. It was an F1 error, This vehicles calibration is not yet supported, Check for updates and call tech support if your version is correct.....:disbelief:

Whatever.... So I tried it again thinking it was just being stupid.(electronics like to do this to me)

But it gave me the same error. So before I through a hissy fit i thought that i would go home and check for updates. I thought they were sent with all of them current. So i went to start my truck and it wouldn't start.....:skeptic:

Now im stuck.... I have had this happen before and had to get a pcm reflashed cause the voltage went below what it required and froze. My heart was in the dump today.

Turned the key off and then tried it again and she sprang to life... In a stock form....

So i went home and went to look for updates but my previously loaded Pegasus software didn't want to work..... Tried and tried. Finally I gave up and uninstalled it and then reinstalled it. Got it to work.(back to them wanting to do things to me LOL)

Looked for updates and sure enough there was one.... Yeah maybe now it will work.

So i went to the same spot and tried to program it to level three.... :evillol:

I got past the checksum file error this time.... I’m ready to burn some rubber. Its gets done with all four phases and I go to start it......

It would start but wouldn't run. Well I guess it kind of run. It would rev up to 1200 rpms and then die to 200 before revving it back to 1200 again. I let it do this for some time (20 sec) and then decided it was not right.

I just can’t win for losing at this point....:cursin:

So I try to run a stock tune and at this point in the night I have all but given up when I tried this. It got done programming and it ran great. I drove it a little ways and it felt like it had more power than my edge. That’s what I wanted.

So back to the performance tune... What would make it do that? I was running 91 octane and I didn't mess with the custom options except for tire size.

Any thoughts?

Sorry for the long post.

Jackpine Wed, February 25th, 2009 10:44 AM

I'm amazed at the problems people can have with these things. And, twintips, I haven't a clue what went wrong in your case. Sounds like you were doing everything right, but....

I'd leave everything just as it is until you can get with Bill on this. I suspect he's the only one who can help you.

- Jack

twintips_17 Wed, February 25th, 2009 11:30 AM

Quote:

Originally Posted by JackandJanet (Post 4513)
I'm amazed at the problems people can have with these things. And, twintips, I haven't a clue what went wrong in your case. Sounds like you were doing everything right, but....

I'd leave everything just as it is until you can get with Bill on this. I suspect he's the only one who can help you.

- Jack

What octane is the extreme tune written for?

The edge was written for 91. Is it the same in this case?

I uploaded all the updates like I stated and the gryphon worked on my truck just fine. But I went to put it on my father’s screw.... One year older than mine and the same thing. Gave me the same code...

Now the unit won’t sync with Pegasus....

Could it be I just got a bad unit???

RED4 Wed, February 25th, 2009 11:57 AM

Jack really had the best/only solution to this.

Quote:

Originally Posted by JackandJanet (Post 4513)
I'd leave everything just as it is until you can get with Bill on this. I suspect he's the only one who can help you.

Anything we would suggest would be a stab in the dark and with the problems you seem to be having - I would personally wait for the man who can actually fix this for you.

Power Hungry Wed, February 25th, 2009 12:20 PM

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.

twintips_17 Wed, February 25th, 2009 12:49 PM

Quote:

Originally Posted by Power Hungry (Post 4520)
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 Wed, February 25th, 2009 12:53 PM

Quote:

Originally Posted by twintips_17 (Post 4526)
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 Wed, February 25th, 2009 02:44 PM

Quote:

Originally Posted by JackandJanet (Post 4528)
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....:shrug: 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 Wed, February 25th, 2009 03:37 PM

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 Wed, February 25th, 2009 04:07 PM

Quote:

Originally Posted by JackandJanet (Post 4540)
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:hehe:) 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....:giggle: 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 Wed, February 25th, 2009 04:31 PM

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 Wed, February 25th, 2009 05:36 PM

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.....:skeptic:

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 :hehe:

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?

Jackpine Wed, February 25th, 2009 07:01 PM

Quote:

Originally Posted by twintips_17 (Post 4549)
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.....:skeptic:

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 :hehe:

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?

So, you're running 91 octane gas in an 87 octane tune? Using the manual guidance, you should advance the timing +2 degrees, not 2.5. (The manual, by the way is a little weak on math right here).

If you get a custom towing tune, make sure Bill knows you're using 91 octane gas. He'll build in the timing advance for you and tweak some other things too.

- Jack

twintips_17 Wed, February 25th, 2009 07:13 PM

Quote:

Originally Posted by JackandJanet (Post 4561)
So, you're running 91 octane gas in an 87 octane tune? Using the manual guidance, you should advance the timing +2 degrees, not 2.5. (The manual, by the way is a little weak on math right here).

If you get a custom towing tune, make sure Bill knows you're using 91 octane gas. He'll build in the timing advance for you and tweak some other things too.

- Jack

I did get a custom tow tune at 91. In the past i have been able to puch teh timeing to 2.5 without problems. Either way the point is that the new grypon will only advance it 2.0 in .25 incerments.

So does it advance the same as the manual states? And i only advanced it .5 up and so that would say i was running 88 octane acording to the manual. 91 should more then run on that with no problems?

Im so confused. I had my favorite presets in my ver 4.xx.xx and now they dont go the same into this one. Any custom tune ends up jinxing me even if i jsut mess with tire size:sigh:

That should have no effect on how the engine runs.... Just shift points right?

Jackpine Wed, February 25th, 2009 07:27 PM

Quote:

Originally Posted by twintips_17 (Post 4564)
I did get a custom tow tune at 91. In the past i have been able to puch teh timeing to 2.5 without problems. Either way the point is that the new grypon will only advance it 2.0 in .25 incerments.

So does it advance the same as the manual states? And i only advanced it .5 up and so that would say i was running 88 octane acording to the manual. 91 should more then run on that with no problems?

Im so confused. I had my favorite presets in my ver 4.xx.xx and now they dont go the same into this one. Any custom tune ends up jinxing me even if i jsut mess with tire size:sigh:

That should have no effect on how the engine runs.... Just shift points right?

Time out! You have a custom 91 octane tow tune? The timing's already advanced! If you were bumping it on top of that, you were way over advanced! If, you've advanced it 0.5 now, you've effectively set your truck up for 92 octane gas. It MAY work ok, but you run the risk of detonation under load.

And, if you're using presets from a previous version, I'd say you're asking for trouble.

Bottom line here - If Bill's given you a custom tune, don't try to out think him unless you know more about tuning than he does!

- Jack

twintips_17 Wed, February 25th, 2009 07:30 PM

Quote:

Originally Posted by JackandJanet (Post 4567)
Time out! You have a custom 91 octane tow tune? The timing's already advanced! If you were bumping it on top of that, you were way over advanced! If, you've advanced it 0.5 now, you've effectively set your truck up for 92 octane gas. It MAY work ok, but you run the risk of detonation under load.

And, if you're using presets from a previous version, I'd say you're asking for trouble.

Bottom line here - If Bill's given you a custom tune, don't try to out think him unless you know more about tuning than he does!

- Jack

Slow down sparky:hehe: I ordered one from bill. Im still two months out!!!:smiley_roll1:

I was just stating to your above statement, to tell bill if i order one......

I am working stricktly with "canned" tunes... So i should have been fine. I say again it would have been 88 octane.

As far as using presets from a previous version i am running into trouble.I am learning that and I am having to find new ones. But anything i do results in rough running. Like i said i adjusted the tire size and got a bobbing idle.... Wierd????

Power Hungry Wed, February 25th, 2009 07:37 PM

As far as I know, it should still have a +/- 5º timing adjustment. So does the problem only occur if you change the timing?

If you get a second, try loading the offending custom options and then remove the unit and plug the unit into your USB port. Use Pegasus to read the critical files (under the Utilities Menu). Send me the "Stock" and "Custom" files and I can see if something is getting chewed up in the custom process.

Take care.

twintips_17 Wed, February 25th, 2009 08:19 PM

QUOTE=Power Hungry;4570]As far as I know, it should still have a +/- 5º timing adjustment. So does the problem only occur if you change the timing?

If you get a second, try loading the offending custom options and then remove the unit and plug the unit into your USB port. Use Pegasus to read the critical files (under the Utilities Menu). Send me the "Stock" and "Custom" files and I can see if something is getting chewed up in the custom process.

Take care.[/QUOTE]

It happens to any tune i try and customize. I will try it in about an hour and i will do that if i can get it to sync with pegasus... Still havn't figured that one out.

But the timing adjusts in .25 incerments. I will go try it again.:2thumbs:

twintips_17 Wed, February 25th, 2009 08:47 PM

So i went out and tryed it again. I changed the timing +2.0. Started it up and it ran fine. Im going to go drive it now. I will report back....:woot:

twintips_17 Wed, February 25th, 2009 10:24 PM

I went oout and drove it.... And it seems im back to the way it should be:woot:

Now i am going to work on getting it to sync. One problem fixed for now, untell i adjust tire size. One more problem to go.

Power Hungry Wed, February 25th, 2009 10:30 PM

Making progress! As long as you're moving forward, that's cool.

Keep us up to date.


All times are GMT -4. The time now is 11:10 AM.


All Contents Copyright 2008-2024, Power Hungry Performance