When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
Went to pass another person on the highway today and my truck started to "miss" like a gasser. I was going up a hill and it seemed like I wasn't hitting on all eight. When I got to school I used my predator to check the codes and pulled up one reguarding the Turbo, EBP and something about my transmission. I then called the dealership to schedule an appointment tomorrow morning and restored my factory settings. After I was done, I went to check the codes again (on stock program) so I could run them past you guys but the codes were gone! Is anybody having issues with their predator throwing codes but no codes while it's unplugged? How can I tell the dealership what happened without telling them it happened while I was hooked up to a programmer? I only run it on the 65 HP mode (don't have any other mods) and restore it to stock if I tow/haul ANYTHING! Do not want to push truck until I get exhaust.
I have not heard of the Predator causing codes that did not appear while running the factory original program. What do you mean "it happened while I was hooked up to a programmer."?
With the latest versions of the Predator, I always get the:
P0603 Powertrain Control Module Keep Alive Memory (KAM) Error
and
P1000 OBD Systems Readiness Test Not Complete
when I load the 65HP program.
When I restore the factory original, I get no codes. One of these days, I am going to unplug the EGR start the engine, shut it down with the factory tune loaded and then load the 65, start and run, then restore factory tune and see it the codes are there.
SBV,
It is my VERY layman's understanding that the KAM memory error you get happens every time you change the programming (via the predator or anything else) and will go away with time...the same as the P1000 system readiness... that one, from my understanding, is just saying that the vehicle has not had enough key cycles to make it happy that the system is checking everything out all right.
The first time I loaded the Predator I got this code, since then I never had any other codes. I have flashed many times with no codes since my original install. The one thing I have always done since my first install is load a new tune after the truck is at operating temps.
SBV,
It is my VERY layman's understanding that the KAM memory error you get happens every time you change the programming (via the predator or anything else) and will go away with time...the same as the P1000 system readiness... that one, from my understanding, is just saying that the vehicle has not had enough key cycles to make it happy that the system is checking everything out all right.
If you load the Predator and get the KAM error, go to diagnostics and clear the error. It will go away.
SBV45,
I meant how do I tell the dealership my "missing" problem happened while I was hooked up to the predator. Like I said, all of the codes were thrown while I was on the 65 HP mode. After I restored my factory settings the codes were gone. I have never gotten the P0693 code. I was afraid that the codes were erased with the 65 HP mode so I tried to recreate the "miss" this morning on the way to the dealership and couldn't. I called the dealership and all the service writer could tell me was that the tech was waiting on parts, I called after the tech went home and she would not tell me what the problem was or what parts he is waiting for, so I will let you guys in on the full story as soon as I get my truck back.
I have not heard of the Predator being the cause of a problem that would throw a code. Usually there is something wrong that shows up after the Predator program is loaded. It is essential that you reload the factory original tune before going to the dealer.
I did go back to the stock program, I am not going to eat the cost of a new 6.0! I am guessing this had something to do with my smoking problem and the predator just magnified the problem. I am just stumped how the codes do not re-appear after I reload the stock program. oh well, love the truck, so as long as they keep fixing it(for free), I can't complain.
Nope. I just told them what happened, as far as they know, my truck is as stock as it was when it rolled off the assembly line. I did not tell them about the predator or my ability to read the codes that it caused, I am leaving it up to them to find out what isn't working. I assume since they are currently waiting for parts they found out what was wrong on their own. I am going to give the dealership a call in about an hour to find out what they think the problem is. I will keep eveybody updated.
Just got back from the dealership and they could not find anything wrong with my truck. After two days worth of diagnostics and test drives with the shop foreman, they could not duplicate the problems I originally had. As I said before, the codes I retrieved with the 65 HP mode were nowhere to be found. I will upload the program again tomorrow to see if I can get those codes to come up again so I can contact Diablo with better information. Obviously I am not a technician but my common sense tells me the problem is with the predator and not with Ford. I am still really impressed with the programmer, I just hope my the problem is bad software. I bought the programmer less than two months ago so I am guessing it is up to date. Who knows, hopefully Diablo will.
Your software on your Predator can be uploaded off the Diablo site. It is easy to do and there is a fairly recent new release. I would do that. I would call them as well. Where did you buy the Predator? If you bought it from MotorHaven you can call them. They are good.
Rezvani's Latest Post-Apocalyptic Monster Is a Ford F-150 Raptor Underneath
Slideshow: Called the Fortress, the 850-horsepower pickup combines Raptor underpinnings with military-inspired features, survival equipment, and a starting price of $285,000.