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.
The jumper between STI (single wire) and SIGRTN/Ground. Fordfuelinjection.com says to short STI to ground, but it is easiest to jumper it to the signal return pin in the 6 pin connector with something like a paperclip.
One thing to note is that you need to do this twice--once for KOEO codes and once for CM codes. Even though the CM codes flash out after the KOEO codes, they don't get cleared if you pull the jumper while the KOEO codes are being flashed. You have to start the code-flashing process again, and pull the jumper while the CM codes are flashing.
The CM codes are the only ones that can get cleared. Any codes that flash before the separator pulse are things that the computer sees wrong at the time of the test.
The jumper between STI (single wire) and SIGRTN/Ground. Fordfuelinjection.com says to short STI to ground, but it is easiest to jumper it to the signal return pin in the 6 pin connector with something like a paperclip.
The CM codes are the only ones that can get cleared. Any codes that flash before the separator pulse are things that the computer sees wrong at the time of the test.
Then why do I have to clear KOEO (Key On, Engine OFF) codes after I fix something?
I believe you're thinking of KOER (Key On, Engine Running) codes--which are read with the engine running, and are cleared as soon as the engine is shut off.
I believe you're thinking of KOER (Key On, Engine Running) codes
No, I'm not. I know the difference between KOEO and KOER tests. When a KOEO test is run, there's a group of codes output, then a separator pulse, then a second group of codes. The first group are problems that the computer flags at that instant, the second group are codes that have been stored in memory. A KOER test only displays hard faults, or problems at the time of the test (you're right, they can't be cleared). The codes during a KOER test are the same as the codes in a KOEO test before the separator pulse, neither of which can be erased. The memory (CM) codes are the only ones that can be cleared.
If you pull the paperclip while the KOEO codes are flashing out, they will be cleared. (Try it...unplug something to set a code with the engine running, then check the codes). If you do not run the engine again before checking the KOEO codes again, all you'll get is a 111 code before the separator pulse, but the CM codes will still be there.
I know because my '93 has a tranny issue that only sets codes when I drive it. I can endlessly duplicate what I said above. That was when I discovered that I had to clear the CM codes separately (pull the "paperclip" AFTER the separator pulse).
Okay, let me put it this way. TPS is junk and throwing codes (and truck is running like crap--BTDT). Replace TPS. Without starting truck, all the original codes will be there (when my TPS went a few years ago, it threw about 4 KOEO codes). They can then be cleared as I described--pulling the jumper during KOEO before the separator. The CM codes will still be there, which will need to be cleared separately.
Maybe the '87-'91 trucks are a bit different (they do have 2-digit codes), I didn't play with reading codes much on my '90 (stopped driving it before I found FTE and learned how to read codes).
Maybe so, but I haven't seen anything online to indicate any difference in procedure between 2 and 3 digit codes, and the CM codes are the only ones actually stored in the computers memory. I'll give it a try when I get my truck back together, and maybe try my dad's truck when I'm back home this coming weekend (2 vs. 3 digit).
To edit what I said in my last post, instead of being impossible to clear, hard faults should only be able to be cleared by fixing the cause of the problem. They are not stored in memory, so in theory, they should not be able to be cleared by pulling the jumper. I'm hoping to test that theory soon.
But those codes are stored in some kind of memory--the test is done before the codes are ever flashed out (which happens 3 times--the quick flashes for a code reader, then they're repeated twice).