New tune.....new truck!!!
 

Well, after being caught up in the PHP e-mail debacle of 2009, one that I'm sure will go down in automotive history, I finally received my custom tune.

You see, after being very patient, :whistle1: and waiting about 3 months I finally contacted Corey to check up on my tune. Low and behold it was on the server and ready for me to down load. :woot: The real kicker is that it had been there sense MAY!!!!! :yikes2: Apparently Corey's e-mail had never made it to me. :doh:

The moral to the story is to be patient, be polite, and check in every so often to see how your tunes are going. :howdy: The reality is I actually received very fast service, as my tune was ready in 2 weeks, :cheesy smile: the other reality is that electronic communication is far from perfect. :cursin:

Anyway, it was like having a new truck when I originally installed my Gryphon and set it to level 2, now I have re-lived the experience of having a new truck again after installing my new custom 87 octane tune. Bill, either you're that good, or Ford is that bad. :hehe: Sorry Bill, I couldn't resist. Bill obviously knows what he's doing, and does it very well. I have much better performance, and a sold 1.5 MPG increase. Thank you Bill and Corey for all the hard work and effort you put into PHP, and allowing me to be a part of the Power Hungry Performance team. :thumbs up yellow:

Glad you got everything and enjoying the truck...

Im usually not a fan of a cap on a truck.....but your truck looks very nice. :beers:

Thanks JWB. I use my truck to transport dogs, so the cap works really well for that. There are times I wish it wasn't on there, but all in all it works out well. That's why I leveled the truck by lowering the rear, it makes dealing with the dogs easier.

Thanks for being patient!
It makes our job easier!
Glad that everything worked out!
Great look'n ride!

Lars:2thumbs:

Not a problem Lars. I have a business much like Bill and Corey's and understand what they go through on a daily basis. We live in a fast paced world where so many people expect quick answers, and "instant gratification". I think the internet has both helped and hurt what we all expect out of other people. My advise to those who have a hard time with patience is to detail your truck, and spend some time reading the ford workshop manuals for your particular vehicle. You'll look sharper, be smarter, and before you know it you'll be rumbling down the street in a custom tuned, good looking truck, with a smile on your face. :cheesy smile: Thank god these things have windshields or we would all be picking bugs out of our teeth.

PS, both you and Jack do a fantastic job of fielding questions and providing answers to the masses. The people on this list are lucky to have both of you here.

Down N Dirty,

Good looking truck. Like you, I'm partial to the Mark-LT wheels. I've got a set sitting in the garage that I got for dirt cheap and plan to have them powder-coated black.

Question: What size tires did you end up installing and how do you like them? You picture looks like they are about 275's ?

Any issues with the drop shackles? Love my truck, but they are very tall at the rear. I can see why the fold-out step is an option on the 2009's.


Thanks.

Nice choice on wheels. I bet they will look real nice when you get them painted, be sure and put up a picture when you get them done. I love these wheels, their almost a KR, but have the grooves cut in the spokes.

Actually the tires on there now are Michelin 255/70-18. The same height as a 275/65, but a little narrower. I'm getting ready to put some new tires on and will be going to 275/65, or 285/65, just not sure which ones yet......price will definitely play a part in my choice.

I did not use a drop shackle to lower the rear, I simply removed the stock 4X4 block between the axle and springs, and replaced the u-bolts with stock 2X4 u-bolts. It's a very clean and easy way of dropping the rear of a 4X4.

Yes, almost exactly a KR wheel, but much easier and cheaper to find. Seems like everybody who got a Mark-LT or Navigator ditched the stock wheels and went to blingy 23-inchers, leaving lots of these wheels on the second-hand market.

My thought was to powder coat the wheels in gloss black and leave the Lincoln center caps the original color.


Yeah, I priced out the Michelin 275's to fit. They are not cheap. Haven't bought them yet. Still noodling... I just know the stock 17" Hankooks really need to go.


In spite of the tow hooks on the front of mine, it's a 2wd, so no blocks to take out.

How exactly are you checking for the tunes? So far everytime I pulg my gryphon into my computer for anything besides changing splash screens, it ends up not working and I have to completely reset it.

Your right man, people dump these wheels like they were stock steel wheels.....and I love them. Sounds like you do too, so their lose is our gain.

I look forward to seeing pics when you get them on.

Hey longshot, I sent Corey a PM, and had a response within a day. There's lots a threads here about hooking up your Gryphon, so you might want to check some of those out. Maybe Jack or Lars will chime in and point you in the right direction.......that's why they get paid the big bucks. :hehe: I would just end up confusing you. I know how it works, just not good at explaining it.

haha, know the feeling, should have been there when I was TRYING to explain rim sizing to someone. I know what Im saying even if it doesnt sound like it.:hehe:

I've checked how other people are checking and so far everytime I've done it something messes up to corrupt the memory on the programmer...I must have the charm of a sledge hammer to computers.:hehe:

Hang in there longshot......someone will chime in here soon and rescue you.

well Im not really worried about it right now, ordered my gryphon towards the end of july so there is still some wait time. I'm just wondering if there are any other ways to check since the way I did it messed it up twice.

You won't have to disconnect your Gryphon to check. Just make sure you have registered your Gryphon using Help->Registration.

Then, you can check to see if your tunes are ready by just clicking on Updates->Current Update Status.

Once you see there are updates ready for you, set your truck back to stock, plug your Gryphon into the PC with Pegasus running and then hit Updates->Targeted Functions. Follow the directions. DO NOT leave your PC unattended until the tunes are loaded, and don't let anyone else get their grubby paws on your PC! :)

When the tunes have finished loading, simply disconnect your Gryphon from the PC, turn your truck's ignition to ON (don't start the engine) and plug the Gryphon back in. Then, program your new custom tune into the PCM!

- Jack

mK, that'll work. Im guessing that when it says "no PCM information was located" in english it means "chill dude, they're still cookin":hehe:

Where are you seeing this? In Updates->Current Update Status, I see: "Serial Number 1047 was not located on the server." (Which tells me there's nothing new for my unit (S/N 1047)).

- Jack

here's a word for word quote of everthing that comes up:
"
No attached device was located.
Using registered device Serial Number 1997.

No PCM information was located.
This update was applied on 07/27/2009.

Current working invoice number is: 0000.
Update information was last updated on: 00/00/0000
"

what do you make of it?

It's certainly NOT what I see.

Help me here. Have you gone into Help->Registration and entered ALL the details, including the HEX (Calibration) code? (I know, why the heck can't we agree on names for things?) :shrug:

Here's what I put in the four boxes for "Device Information", it may help you figure out what to put in - I think maybe some of the required info is not clear:

1. Serial Number: 1047 (This is also my "Invoice Number").
2. Model Number: GPFG150-0408 (I got this from the "Diagnostics->Tech Support->Version Info" screen on the Gryphon, while plugged in to my truck).
3. Device Type: 6 (This is shown as "Hardware" in the "Version Info" screen.)
4. Calibration: RXCM5E4 (My HEX code, which is seen when you hit <Enter> on the "Version Info" screen.

The only thing I can think of is that your "Registration" info is incomplete. Can you check that for me?

Thanks,

- Jack

yep, entered everything, even let it pull some of the info off of the programmer to make sure it was correct. Now there is one box that is blank, its the one on the bottom right that says calibration, but even when it pulled info from the programmer I dont think that it was filled in. Your might also look different because your tunes have already come in. :shrug:

That's the one I suspected was blank! Go ahead and manually type it in. This is your HEX code. Do that and click on <Save> in the Registration window.

Once you do that, try the "Update Status" menu item again.

- Jack

Did that but still saying the same thing letter for letter.:confused:
my hex is okdg3a3. Tried both zero and the letter O for the first one and capitalized and lower case, same thing either way. Do you think that Im getting this because my tune hasn't come in?

did some more digging into things that might also be wrong. Found something else that is making me curious. I currently have pagasus v.2.01.0575, and when I check for pagasus updates it says there is one: v2.01.0594. So I click updates>apply updates. It then downloads the update (successfully) so I click OK. Then that window closes and a new smaller window comes up that says "finalizing update"(this one appears to be with pegasus programming and not Windows). That stays up for a second and then a new window comes up that is tited "Complete" but says there are no files to be processed. Just after reading this a window, a new box comes up that says "component 'MSCOMM32.OCX' or one of its dependencies not correctly registered: a file is missing or invalid". Then when that closes I notice that pegasus is also closed.

Is this a situation similar to Will Smith in "Irobot" where everthing electronic is messing up or is my MS Windows OS acting like it's preview game 'minesweeper'? :face-lol:

*is there a connection between this mysterious 'MSCOMM32.OCX' and Microsoft windows?

I have something simular going on...

My client will pull everything except the hex code and it won't let me type it in manually. My client version is v2.01.0594. Everything else works fine. I just don't want to be left off the custom tune list because of a mistake on my part...

I put the truck to stock, pull it out of the truck, connect it up, everything connects but it won't let me enter my hex. (My hex is in my user cp and I also emailed it to Corey.)

Added: After looking at it again I see my hex code in the update manager window so I know the program has it. It just doesn't enter it in my registration info.

This is why I love/hate computers. (And I taught computer programming and microprocessor design in the University for 20 years). :sigh:

Circuit and Longshot, I'm going to defer this to Bill, because it's a problem with his software and I don't have access to the internals of it. It might help him to know your operating system. Is it XP, Vista, or 64-bit Vista? (What the heck is going to happen when Windows 7 hits the streets?) :crazy:

I vaguely recall something about the missing ".OCX" file, but I can't find it now. Bill will probably know immediately what to do.

Version ".0594" is the correct one at this moment.

Sorry I can't be more help. :shrug:

- Jack

Im not too worried about it because I THINK I'll still be able to download my custom tune when it comes in. But its good to be sure. What are the differences between the new and previous programs?

As for OS's, I've got the 32bit windows Vista. I know this missing file's name looks familiar, just cant place it.:confused:

Me and computers either dont like each other at all or work together awesome. I just think windows is like the game minesweeper. Your happy and smiling until you make one click that is not so good then *boom*, you gotta start everthing all over. lol

There is patch on the PHP website's support page that addresses the MSCOMM32.OCX problem. You'll need to download and run the installer to fix the issue.

There is also going to be an update available tomorrow for Pegasus. Version 2.01.0605 will be the latest release and fixes the problem where the registration form doesn't correctly retrieve the calibration code from the device. There are a couple of other minor tweaks as well, but nothing significant.

I'll be rebuilding the installer to hopefully resolve the problem with the MSCOMM32.OCX issue and also include the new 64 bit compatible USB drivers.

Keep an eye out on the website for the full installer.

Thanks.

Ok well I'll wait for the newer update because even the mscomm32 installer from the website isnt getting its job done.

Thanks. I will have an eye out for it. At least I don't have any of the other problems.

I am trying to burn as much of my 87 octane out of my tank (first time ever I regretted having the large tank lol) so I can fill up with 94 on the weekend and try level 3. :happy-dancing:

Good luck longshot :thumbs up yellow: