Power Hungry Performance Forum

Power Hungry Performance Forum (http://forum.gopowerhungry.com/forum/index.php)
-   1997 to 2003 F-150 (http://forum.gopowerhungry.com/forum/forumdisplay.php?f=12)
-   -   Emission testing.. (http://forum.gopowerhungry.com/forum/showthread.php?t=6772)

AZFX4 Tue, July 5th, 2011 02:55 PM

Emission testing..
 
Not another!

So I have to take emission testing in AZ.. what a PITA.

From everything I read with the tuner, I just have to unplug it from the OBD port and take the test with it tuned. I did not download another tune or set it to stock. It's been on the same tune for atleast 3 months and over 1500miles worth of driving..

But when I unplugged it and went in to get it tested it showed my OBD port wasn't ready. Did it some how trigger the P1000 code when I unplugged it from the OBD port? Or whats your thoughts?

Sucks sitting in the baking heat and then to "fail".. The guy inside basically told me my truck has been serviced and I need to drive around to let the computer learn again.. which I understand, but is there a reason it triggered that code by just unplugging it from the OBD port? I thought it only did that when re-tuned or set to stock and going in.

88Racing Tue, July 5th, 2011 03:10 PM

If you left it on the custom tune there shouldn't have been any issues not unless their cord is junk.....check your cigarette lighter fuse incase that's been fried.....that's the only other thing I can think of......

AZFX4 Tue, July 5th, 2011 11:08 PM

Well I did about 125mile round trip today... so that should get rid of it, if for some reason unplugging it reset it? But the question is, could it have triggered the P1000 code? They didn't tell me what code was set, just that my OBD wasn't "READY"... cause if for some reason I go back in after all this driving and it's still not, "READY" I don't know wtf?

Now if for some reason my fuse is fine or fried, but I pull it out and put it back in, will I have to drive around still to make sure it's gone?

AZFX4 Tue, July 5th, 2011 11:31 PM

I just checked that fuse, it looks good. Replaced it with a new 1 anyways.. so now the question is, am I going to have to drive another 100miles to make that code go away or did this not affect it?

I was going to go tomorrow and see if it will pass but if I fail, then I got to go through a bunch of crap to get it registered being it would have "failed" twice, even though it's just OBD not being read..

Ahh.

Longshot270 Wed, July 6th, 2011 12:00 AM

Is there another place to get it done? The custom tune should not be triggering any readiness codes.

AZFX4 Wed, July 6th, 2011 01:34 AM

No, it's OBD port testing.

So, should this clear within 100miles or so? Or do you think I may have a different problem? I'm hesitant to try to plug Gryphon back in and see if it works.. but if I do that, it will probably trigger it again and I'll have to wait longer and it's due by 15th.. but once I fail twice, I have to call some emission bs place and talk to them, so I have no clue what will be involved with that if I fail again.

AZFX4 Wed, July 6th, 2011 01:36 AM

Is there something else I can try?

Set it back to stock, drive for 200miles and would that work? I'm reading leaving it tuned and just unplugging from OBD port will pass, but now that I failed once.. scared it will happen the 2nd time even driving it for 125miles!

A buddy suggested having like Autozone or someone try to read codes from OBD port to see if their scanner will read it. I would assume if they can, the guys at emission testing should also.. I should have no codes, but just seeing if their scanner will read it?

Longshot270 Wed, July 6th, 2011 07:04 AM

Have you tried pulling codes?

88Racing Wed, July 6th, 2011 08:39 AM

Is the gryphon seeing any codes? Cause autozone will see the same ones...

AZFX4 Wed, July 6th, 2011 01:10 PM

I have not plugged it back in because I figure if I do, I'll trigger the same code and have to drive another 100+ miles.. but if I have Autozone pull them I think I'll be safe? I'm going to try before work.

AZFX4 Sat, July 9th, 2011 05:43 AM

Autozone pulled no codes.

I tried emissions 2nd time, OBD still not ready. My buddy found a site on what to do for the drive cycle and it was from Ford Motor Company so I did that. Went back, but being I "failed" twice I got locked out of the system. I have to go through ADEQ, Enviromental Quality bs.. so I went to them, they checked after I did what was said for drive cycle and I'm still not ready.

My question is right now... is there anyway that being that I'm still tuned, it's not letting my computer relearn this? It's showing my EVAP monitor and EGR monitor isn't ready. The guy was cool and told me how EVAP is hard to get to read, but will come on first before EGR... he explained how to try to get it to come on was have gas at 1/2 tank and keep it there and drive city/highway... but it can't be under 1/2, but not to much over 1/2.... he told me a lady drove for 5 weeks and STILL wasn't ready. He even had his Expedition on the dyno and a scan tool measuring everything and had it perfect and it still didn't want to register it. I asked if I should just disconnect battery and redo it and he said no since I'm so close. I just need 1 more monitor to be ready for him to unlock it, then I can go down and try emissions. Not guaranteed to pass but it's my only way to see.

So can this get tagged and have Bill read this? I just need to know if it's possible the Gryphon being tuned still may be causing my computer to not be ready? I've got 6 days til it's due and either I keep driving for next few days and HOPE it clears, or reset it and put it back at stock. But then it's possible it takes even longer to get everything reading, ready.

88Racing Sat, July 9th, 2011 07:15 AM

I still think that the shop has a faulty cord....

Longshot270 Sat, July 9th, 2011 07:31 AM

I left a note for Bill...

AZFX4 Sat, July 9th, 2011 03:55 PM

Heck if I know.. it's such a PITA!

Just want it to be done and over with.

Jackpine Sat, July 9th, 2011 06:45 PM

AZFX4 - I've been watching this thread, but haven't really had anything to say, so I stayed out of it.

However, until you talk to Bill, I would strongly advise that you DO NOT return to the Level 0 Stock tune. That is guaranteed to set your P1000 code and that in itself will cause you to fail.

I'm somewhat puzzled by the symptoms you have though. I'm reasonably certain nothing in Bill's tunes effects the Evap System. So, I wonder if there's possibly a sensor failure in that circuit? The EGR though is a whole different matter. I WOULD expect Bill's tunes to interact with EGR. I suppose though, there can be a sensor failure in the EGR circuit too. I have no electrical information on your model year truck, so I'm just guessing.

Now, it's possible if you reset to Level 0 and then reloaded your tune, the problems would go away. (But please don't do that unless Bill says to do so.)

One thing that would be safe is to check for codes. Have you done that? And, if you find any, try to clear them.

Beyond this bit of pretty fuzzy advice, I've nothing brilliant to offer. Yours is the FIRST truck I've heard of failing an emissions check while being tuned. :shrug:

And, 88, I doubt the "cord at the shop is bad". Here in Arizona, inspection stations are licensed facilities with several entrance bays. And, they are not affiliated with any "repair" facilities. Unless he used the same bay, he'd be getting a different monitor. And, I doubt a bay would go belly up on just his truck but think everyone else's is fine. I DO think there's a problem, but have no clue how to fix it.

- Jack

AZFX4 Sat, July 9th, 2011 06:53 PM

Being the FIRST is in most cases, the best thing. But in this case it sucks.

My truck also is basically the only truck I have read about the PCM being locked when changing tunes, which was 1 reason I was scared to return to stock incase it decided to lock itself once again!

Autozone checked for codes, I had no codes. And plugging the unit back into OBD port I figured would not be smart, but what do I know.

It sucks, I guess keep driving it.... that's all I'm told I can do. UNLESS something is wrong internally with the wiring or computer. And if the sensor is somehow bad, how would I change it? Guy at ADEQ explained to me there isn't anything to be changed or fixed, it can only be driven off.... so I'm stumped. I would HATE for me to plug the Gryphon back in and reset the computer again and have to go through the P1000 and try to clear it all again. But maybe plugging it in will help? I have 5 days, then I have to get an extension which is 30days, so I would be willing to try anything then.

Jackpine Sat, July 9th, 2011 06:56 PM

I "feel your pain", as someone once said, and wish I could help. I added a couple of thoughts to my previous post while you were posting your last.

Wish I could be more help.

- Jack

AZFX4 Sat, July 9th, 2011 09:17 PM

Thanks..we shall see what happens.

88Racing Mon, July 11th, 2011 03:23 PM

Quote:

Originally Posted by JackandJanet (Post 49384)
AZFX4 - I've been watching this thread, but haven't really had anything to say, so I stayed out of it.

However, until you talk to Bill, I would strongly advise that you DO NOT return to the Level 0 Stock tune. That is guaranteed to set your P1000 code and that in itself will cause you to fail.

I'm somewhat puzzled by the symptoms you have though. I'm reasonably certain nothing in Bill's tunes effects the Evap System. So, I wonder if there's possibly a sensor failure in that circuit? The EGR though is a whole different matter. I WOULD expect Bill's tunes to interact with EGR. I suppose though, there can be a sensor failure in the EGR circuit too. I have no electrical information on your model year truck, so I'm just guessing.

Now, it's possible if you reset to Level 0 and then reloaded your tune, the problems would go away. (But please don't do that unless Bill says to do so.)

One thing that would be safe is to check for codes. Have you done that? And, if you find any, try to clear them.

Beyond this bit of pretty fuzzy advice, I've nothing brilliant to offer. Yours is the FIRST truck I've heard of failing an emissions check while being tuned. :shrug:

And, 88, I doubt the "cord at the shop is bad". Here in Arizona, inspection stations are licensed facilities with several entrance bays. And, they are not affiliated with any "repair" facilities. Unless he used the same bay, he'd be getting a different monitor. And, I doubt a bay would go belly up on just his truck but think everyone else's is fine. I DO think there's a problem, but have no clue how to fix it.

- Jack

It is a possibilty.....I used a scan tool once it was fine on all makes and models except VW''s produced in 04-06.....especially jettas....one of the contacts was not raised enough in the scan tool to make contact with the slightly depressed one in the jetta's port.....but if the OP was set up in two different bays with two different monitors then my theory is out the door......:cursin:

Take care

AZFX4 Tue, July 12th, 2011 06:26 PM

I feel like something is really wrong. 508+ miles and it still said NOT READY...... Either the custom tunes for some reason has it blocked from monitoring it? Or something with my PCM... I don't know? I mean the Gryphon acts as my PCM in a way, so could it be blocking it?

I'm making a drive to Flagstaff Thursday. I think it's around 200+ miles round trip.. I was thinking of setting it back to stock, disconnecting battery and driving there and back and try and see what happens. But I'm scared my trucks PCM will lock itself AGAIN. And since Bill hasn't been chiming in and giving his opinion, if my truck did lock itself I may be screwed..............

Jackpine Tue, July 12th, 2011 07:34 PM

AZFX4 - I've left a note to both Bill and Cody. I've tried to make them aware of your unique problem. I'll check again tomorrow to see if you've made contact.

- Jack

AZFX4 Tue, July 12th, 2011 08:02 PM

I've talked to a few guys, all who have programmers, and have passed emissions with their truck tuned. Neither have a Gryphon but custom tunes nonless. They all advised me to return to stock and disconnect battery and start over. They suggest something isn't right after 500+ miles it's the same. So I'm all for trying it..

It almost locked up AGAIN. It glitched at the end of everything and was stuck on turn truck off and back on. Luckily when I unplugged it, it showed a fail and let me retry and successfully returned to stock. Could it be my Gryphon has a problem also? Since the last 2 out of 3 times changing levels it has locked itself?

And JackandJanet, thanks. Any idea what my choices will be if I don't pass? I know I can get a 30 day perment and be safe and keep trying to pass.. but if I don't What do I do?

Jackpine Tue, July 12th, 2011 08:52 PM

Quote:

Originally Posted by AZFX4 (Post 49462)
I've talked to a few guys, all who have programmers, and have passed emissions with their truck tuned. Neither have a Gryphon but custom tunes nonless. They all advised me to return to stock and disconnect battery and start over. They suggest something isn't right after 500+ miles it's the same. So I'm all for trying it..

It almost locked up AGAIN. It glitched at the end of everything and was stuck on turn truck off and back on. Luckily when I unplugged it, it showed a fail and let me retry and successfully returned to stock. Could it be my Gryphon has a problem also? Since the last 2 out of 3 times changing levels it has locked itself?

And JackandJanet, thanks. Any idea what my choices will be if I don't pass? I know I can get a 30 day perment and be safe and keep trying to pass.. but if I don't What do I do?

There ARE shops that will fix your truck so it will "pass" and then you bring it back so they can "make it run right" (put it back the way it was). I would not go to them. They set up camp right beside the emissions stations.

A reputable dealer could fix the problem. You would want it tuned to stock before taking it there though and neither of these approaches is not likely to be cheap.

I honestly think there IS a sensor problem in your truck, and that kind of thing is best fixed at a reputable shop (most dealerships really are, in spite of the bad press they get). But, I am very reluctant to tell you to go back to the stock tune until Bill has had a chance to look at this.

If he doesn't get with you soon (in a day) let me know, either in this thread or in a PM. I have another way to get his attention and will use it if needed. I see, Ryan, that your User Profile is up to date, so they should be able to use that information to double check your tunes for problems. But, could you add a telephone number to your details there? Bill does not hesitate to call when there are issues.
- Jack

cleatus12r Tue, July 12th, 2011 09:33 PM

What kills me is that the truck failed for a P1000 with a custom calibration loaded into the PCM.....

The P1000 switch is turned off in all three custom tunes. The PCM shouldn't care.

I'll link Bill to this thread tomorrow.

AZFX4 Tue, July 12th, 2011 11:02 PM

J&J, I suppose it could be a sensor problem, the guy had told me there is nothing I can do besides drive til it goes off. But who knows... It's set back on stock, I will make the drive to Flagstaff Thursday and try to get to ADEQ Friday right before work and see if I pass being on stock tune. If not, well I'll chime back in.. I'll add a phone number.

AZFX4 Tue, July 12th, 2011 11:04 PM

cleatus12r, that's kinda interesting that P1000 code is turned off.

So maybe my problem isn't really a P1000 code? I never scanned for it, I was just told simply being that my OBD port isn't ready, that's the drive cycle and you drive til the OBD port is ready. Which drive cycle is P1000. Autozone's scanner doesn't read P1000.

Heck if I know..

88Racing Wed, July 13th, 2011 01:17 AM

Quote:

Originally Posted by AZFX4 (Post 49467)
cleatus12r, that's kinda interesting that P1000 code is turned off.

So maybe my problem isn't really a P1000 code? I never scanned for it, I was just told simply being that my OBD port isn't ready, that's the drive cycle and you drive til the OBD port is ready. Which drive cycle is P1000. Autozone's scanner doesn't read P1000.

Heck if I know..

If you were to put your truck back to stock programming .....you'd get the p1000 code and have to drive your truck till it goes away....disconne ting the battery while in stock programming will cause this also...

AZFX4 Wed, July 13th, 2011 06:08 AM

I did stock programming and disconnecting of battery just lastnight because after 500+ miles it still didn't go away, I had to try something. I know this throws the P1000 all over again, but maybe being on stock it will pass, something with custom tunes was blocking it from reading the sensors, if that's possible. I'm just willing to try anything since I NEED to pass.

Power Hungry Wed, July 13th, 2011 09:15 AM

P1000 is a "DTC" which indicates that the PCM has not finished drive cycle testing of the Evaporative, EGR, O2, and other systems. When those systems clear the self tests, then the P1000 goes away by itself. Just removing the programmer from the OBDII port DOES NOT have anything to do with the P1000 or the self tests, so we can rule out that as a problem.

I checked your calibrations and there is nothing in the tuning that would affect the EVAP or the EGR test monitors. I seriously doubt that the cause of the test failure is related to the tuning, and that you may actually have a problem with the vehicle's EVAP system (often a bad gas cap or a broken vent hose from the fuel tank) and/or the EGR system. Your calibration is one of the most popular 97-03 calibrations we do tuning for and I've never seen this issue before.

What it comes down to is this...

(1) Check the EVAP system for cracks or leaks... anything that will prevent the fuel tank from drawing a slight vacuum while running. If the EVAP system can't maintain a vacuum in the fuel tank, this will definitely prevent the OBD monitors from completing and you will fail every time.

(2) Return the truck back to stock and then follow the recommended drive cycle procedure. If the vehicle is still failing, then you definitely have a problem with the systems indicated.

As to the issue of why the programmer is hanging, I don't have an immediate answer. That could be a hardware related issue, heat issue, or voltage issue, or something else not identified. For the time being, do not reprogram the vehicle unless you're at home so we can perform a recovery if necessary.

I hope this is helpful.

Jackpine Wed, July 13th, 2011 09:27 AM

AZFX4 - Now that you're talking to Bill and Cody, I'll stay out of it. I like Bill's explanation. But, can you tell us - do they actually test anything on your model year truck besides plugging into the OBD port? For instance, do they take your gas cap off and attach it to a vacuum port to see if it's alright? Do they put a sniffer into the tailpipe?

As I recall, on my 2005 truck, I use the OBD port only line and the ONLY thing they do is read the data at the port. I seem to remember that line is for 2001 and up trucks (but I may have the year wrong).

Knowing this information may help Bill.

Oh, one more thing. I don't think you will be able to read the P1000 code if it's set using the monochrome Gryphon. At least I never did. I DO see it (when it's set) with the CTS programmer though and I assume the CS would show it too.

- Jack

Power Hungry Wed, July 13th, 2011 11:28 AM

All the programmers (Gryphon, Evolution, CS, and CTS) have the capability to read the P1000. The question is whether or not the P1000 DTC has been disabled in the calibration. In most cases, the P1000 was shut off to avoid the annoyance of the DTC and also prevent unnecessary tech calls about what the P1000 DTC was. However, this does not affect the system self tests for the OBDII monitors. Those will continue to function as normal, so if the monitors continue to come back as "Not Ready" then there is a problem with one or more emissions related systems.

I will say that performing a drive cycle to reset the monitors can be extremely difficult. There are very specific guidelines that need to be adhered to and sometimes it can take days of driving to get the monitors to clear. With specific fuel levels, temperatures, drive speeds and drive cycles that need to be met, it can be quite a pain. I do think that after 500 miles of driving, if the system hasn't cleared itself then there really is a problem with the vehicle. Unfortunately, OBDII monitors aren't something that can be forced, faked, or bypassed.

Take care.

Jackpine Wed, July 13th, 2011 12:25 PM

Quote:

Originally Posted by Power Hungry (Post 49481)
All the programmers (Gryphon, Evolution, CS, and CTS) have the capability to read the P1000. The question is whether or not the P1000 DTC has been disabled in the calibration. In most cases, the P1000 was shut off to avoid the annoyance of the DTC and also prevent unnecessary tech calls about what the P1000 DTC was. However, this does not affect the system self tests for the OBDII monitors. Those will continue to function as normal, so if the monitors continue to come back as "Not Ready" then there is a problem with one or more emissions related systems.

I will say that performing a drive cycle to reset the monitors can be extremely difficult. There are very specific guidelines that need to be adhered to and sometimes it can take days of driving to get the monitors to clear. With specific fuel levels, temperatures, drive speeds and drive cycles that need to be met, it can be quite a pain. I do think that after 500 miles of driving, if the system hasn't cleared itself then there really is a problem with the vehicle. Unfortunately, OBDII monitors aren't something that can be forced, faked, or bypassed.

Take care.

Bill, my comment about the P1000 code was based on my NEVER seeing it when returning the truck to stock while I was still using my old Gryphon. And yes, I looked for it. :shrug: But, it showed up at stock when I started using the CTS. And, as you say, it certainly did not clear quickly when the truck was at stock either.

- Jack

AZFX4 Thu, July 14th, 2011 12:12 AM

Bill, that helps alot... I'll see what happens tomorrow as I'm taking a long drive, if that fails I will follow their guidelines on drive cycle on stock tune and see if I can possibly get rid of it.

J&J, They plug into my OBD port and they take my gas cap off, but it failed before they did anything to my gas cap. I can't recall if they put a tube over it when I first bought it or not? So I can't be sure.

cleatus12r Thu, July 14th, 2011 07:21 AM

Oh, and the EPA mandate for OBD 2 vehicles and the EVAP system requires the fuel level to be between 85% and 15%...so you have a wider fuel level window than what the emission shop told you.

Just a little information.

AZFX4 Thu, July 14th, 2011 02:27 PM

If getting rid fo the drive cycle code is so strict, I need to try to find a road that I can actually do everything correctly. Not to many places I can do certain speeds for long periods of times like it says. Or 0-60s, back to 40s, OD off, ect ect.

Power Hungry Thu, July 14th, 2011 02:31 PM

That's the problem. I've had to fight for days to on some vehicles to get the OBD test monitors to complete. Others will seem to do it just driving to the grocery store. It's really weird.

AZFX4 Thu, July 14th, 2011 06:50 PM

Your right it's wack.

Lastnight I bought a sub and amp, well we hooked it up, and unplugged the battery. Todays last day til registration expired. I read the paper on passing drive cycle, and did everything but all the 0-60, coast to 40, ect ect... went to ADEQ, hooked me up and it said I was ready! So about 2 hours of driving and around 100 miles it was ready. Went to emissions, PASSED! COMPLETE.

Now the next problem..................... downloading custom tunes.

Got home, plugged it in, download tune 2 - 87 Perf tune. Went through the 1-4 step, then writing checksum files.. ect ect.. did the 1-4 again about alerts and records.. got to turn key off, turn key on, did that and it froze at that. Unplugged, plugged back in, said session failed and restore stock settings. Did so, redownloaded tune 2 and it went through everything and completed, now it's on tune 2. Turned truck off. Did a few things.. came back and turned truck on to go for a drive and Gryphons screen went black. This has happened many times, it's usually the fuse... I replaced the fuse, nothing... put another 1 in just to see. Nothing... with the fuse out, for some weird reason the Gryphons screen came on, but it wasn't good. It showed my 4 parameter boxes, and bottom 2 was very out of pixel, and it showed like -173.0 in both boxes, it was weird. Or -17.30 whatever that means then screen went blank. Tried another fuse.. NOTHING. Now it's black. It came BACK on without a fuse and went off.

I want to say somethings wrong with the device itself? Cause all my fuses are brand new. And it usually just turns back on. I'll retry it in a while. Let it settle... but now what could be the problem? Would you consider trading this old style for a CS and I pay the difference? Is the software in the new CS's better?

AZFX4 Thu, July 14th, 2011 06:58 PM

Went back out, unplugged it, plugged it back in, screen came on. Read my HEX file and started...

Now the sceen now works.. Weird.

Power Hungry Thu, July 14th, 2011 09:00 PM

I'd have to say it's a connection issue with either the plug on the back of the device or with where it connects to the OBDII port. Unfortunately, I don't have any way to reuse the device or we'd find some way give you credit against a CS or CTS. I know Edge was offering some sort of upgrade credit, but not sure if they still have that. When I get back to the office, I can check with Edge and see if they're still offering anything.

Glad everything else got straightened out with the emissions testing.

Take care.

AZFX4 Fri, July 15th, 2011 01:33 AM

Alright thanks.

AZTriton Tue, April 10th, 2012 04:11 PM

Resurrecting this thread on OBD & Emissions
 
Maybe it's something with PHP tuned F-150 FX4's in Chandler, AZ but I'm having a hell of a time getting the drive cycle on my truck to be complete so I can get my emissions test done (and the state says this is the ONLY test for 1996 & newer vehicles...)
The first time I took my truck for testing, I don't think the PCM had been reset since I upgraded my EVO to a Gryphon (at least 6 months) but my system was 'NOT READY'. I reset to stock... maybe not the best decision but since my system had not been reset in a long time, sounded logical (was on the performance custom tune). I drove it at stock for 200 miles (almost all highway which is annoying since my 35" tires cause the speedo to read way low all the time) and went back and it was still not ready. I've been driving it on and off (it's not my daily driver) and even bought a scan tool. No DTC's, nothing abnormal... still not ready: EVAP, Catalyst & EGR still "incomplete". Went out and did a drive cycle for these monitors this past weekend and still "incomplete". I guess I'll have to spend money and have the dealer look at it... can't even get the EGR monitor to execute which is a pretty simple exercise of accelerating 0 to 45 at 1/2 to 3/4 throttle 3 times. Pretty annoying!

Longshot270 Tue, April 10th, 2012 06:04 PM

If you still have any canned tunes, they'll fix the drive cycle issue. If that doesn't work then I'd say there is something funny going on with the systems in question.


All times are GMT -5. The time now is 01:36 PM.


All Contents Copyright 2008-2020, Power Hungry Performance