Yes. You good men spent a lot of time on something really simple. I am sorry I didn't make the connection earlier. Nonetheless, I am grateful. Why? Well, the obvious is that I can now pull coeds. More importantly, do you realize how much you have taught me? Knowledge that many of you have trained for, spent years in the making, you shared with me freely! I have learned a tremendous amount!!

Although we are connected through pages on the internet, when I think of folks that are good with autos, I think of ctubutus, subford, Gary, labaron, Franklin, and vjsimone. All have contributed over a long period of time - several years for that matter. I appreciate all of it and consider you friends, if only by the web.

I have those codes to examine and understand how to correct. And there's the fuel pump and IAC wiring issues that may be tied to one of the codes. There aren't that many codes, so that's a good thing. I'll get it figured out.

If you want to continue to help amidst the frustration with my slowness, please feel free.

Steve

 

Congrat's!! Good job hanging in there. It can be really frustrating, but you got there in the end.

Having said that, I need to caution you as I'm not sure what you mean by "I can now pull coeds." The coeds I knew weren't easily impressed just because an old truck runs.

 

In either case, it's not JUST the truck. It's the DRIVER!

 

Oh, maybe that was my problem.

 

Heh, if I choose to continue, HA!!!

OK, subford alluded to something pretty important - there are THREE sets of codes:

KOEO
CM
KOER

KOEO & CM codes are delivered in a single process but are separated from each other with something like 10 seconds, a single flash, 10 more seconds (the transition from KOEO to CM). <-- when doing the blinkenlight method, make sure you understand what a code reader is telling you

 

Yes. I have a Ford tester, but also have an Actron CP9690.

The Actron does a full range of tests. On my newer vehicles it will also allow me to drive the vehicle and give me performance data A-Z. It's pretty slick. Now I need to learn what all of it is about so I can understand the data. lol

At any rate, possible while using Ford tester I didn't give it enough time because I thought it was finished at 10. It didn't seem to progress past that, but I only waited about 20 seconds.

What are the CM codes?






[QUOTE=ctubutis;16430262]Heh, if I choose to continue, HA!!!

OK, subford alluded to something pretty important - there are THREE sets of codes:

KOEO
CM
KOER

KOEO & CM codes are delivered in a single process but are separated from each other with something like 10 seconds, a single flash, 10 more seconds (the transition from KOEO to CM).

 

Continuous Memory Codes or CM codes

Continuous Memory Codes are issued as a result of information stored during continuous Self-Test, while the vehicle was in normal operation. These codes are displayed only during Key On Engine Off testing and after the separator pulse. Intermittent faults that have not occured in the last 80 warm-up cycles (40 cycles on some applications) are erased from Continuous Memory and will not produce a Continuous Memory Code.

NOTE:
The separator pulse and Continuous Memory Codes follow Key On Engine Off Self-Test codes ONLY.

 

You must have hung around with the rich coeds ... All the poor ones I grew up with were competition in the Automotive Diagnostic challenges!

-Enjoy
fh : )_~

 

Got it. Thanks!!

With my Actron, I did KOEO fast and slow tests with engine off, as well as KOER tests with engine on. The KOEO Tests gave me an 11, while the KOER tests codes were 41, 34, and 12.

I found a vacuum leak and fixed that. I then did a re-test of CM codes using my Ford code reader. Now I show a 31, and that's it. I'm too tired to connect my Actron to see if it will still show the other codes under a KOER test, but will do that tomorrow.

Again, thanks for your efforts!

 

Pulling codes from this OBD-I stuff is something of a big deal compared to today's technology, there are certain pre-requisites that must first be met (engine up to operating temperature) and you hve to go through these gyrations with the brake pedal and steering wheel (depending on installed equipment & year in evolution) to do it correctly, it's not like you just plug in some device and it points you to exactly where to go looking.

Order of appearance of codes can kinda be important, too.

But how you go about fixing them is different; you begin with the lowest-number error and work your way up numerically (in general).

 

That's good information.

The ACTRON gives specific directions such as the one's you describe in each step. That's helpful to novices like me.

However, the fixing of codes in order, lowest to highest code number makes sense. I will do that. Thanks!!

 

Best description I came across on this topic came from Ralph (81-F-150-Explorer) several years ago, it's called "Fix the cavity."

You have a cavity in your tooth, that gets a Code 10.

You have a toothache, that gets a Code 23.

You have a headache, Code 37.

Fix the cavity and all that stuff goes away with it.

It doesn't always 100% operate that way but, in general, that's what they were trying to implement.

Also in general... fix all KOEO issues first thing, then pay attention to the running & CM codes.

 

The KOEO self-test is an electrical ball park range test of most of the sensors. That is why the engine needs to war to get the temp sensors inside the ball park range the EEC Computer is looking for. KOEO codes are not saved in any way.
That is why you must get a 11 in your case for KOEO code before you can do the KOER self-test.

The CM codes will tell you why the CEL (MIL new name) came on while you were driving. Note the CEL (MIL) will only come on for emission related problems so you can get codes in CM that did not turn on the CEL if the problems were not emission related.

The KOER self-test is more of an actuator test and will not check most sensors.

 

This story gets better and better every day….. Good job following that wire back….. We will make a Tech out of you by next year.

KOEO – Code 11 means you truck passed the KOEO Self-Test, this is required before moving on the KOER troubleshooting.

KOEO – Code 13; Follow this procedure to clear this code; (your idle is set to high)
5.0L V8: 1985 Truck and Van; To adjust idle speed: (Official Procedure)

1. Disconnect the battery for 3 minutes to erase the current idle control program from ECA memory. Turn the throttle stop screw in (clockwise) 1 turn.

2. Reconnect the battery, start the engine, and run it at 1800 rpm for 30 seconds.

3. Place the transmission in drive (AT) and let idle speed stabilize.

4. Back out the throttle stop screw, until idle speed is 600 ±20 (AT). Then back out the screw another 1/2 turn.

5. Stop the engine and disconnect the battery for at least 3 minutes.

6. To check curb idle speed, start the engine and run it at 1800 rpm for 30 seconds. Place the transmission in drive (AT) or neutral (MT) and let idle speed stabilize. Refer to the VECI decal for curb idle specifications.

So, I have done this 12 times, this is not easy, easier with 2 people.

Print these instructions out, 2 sets if you have 2 people. Easier to use a Diagnostic Tachometer, $30, unless you have one.

Easier to count the turns with a long straight slot screwdriver. You will need the stopwatch function on your phone to time the 30 seconds. It is challenging to keep your foot on the peddle steady @ 1800 rpm. Do not start the clock until you are steady @ 1800 rpm. (Practice this first before you follow the procedure).

If you only have one person, you will have to set your parking break, and block your wheels. I recommend you use reverse instead of drive (step 3), so you don’t get run over, works just as well.

Please ask questions. I have cleared code 13 using this procedure.

Ref; http://beta.askatech.com/AskATechLiv...Track/F050.pdf

 

I can tell you've got a lot of experience with the the 90s-gen stuff, Bill(?).

The first year of a CEL (MIL new name HA) connected to a computer is 1988, he doesn't have such a dash light to light up, so deciding to pull codes was on an as-needed basis as it started to run bad (or not start).