Chico 61,
Look, no offense intended here. You are certainly entitled to your opinion. You have every right to express it as you wish.
I must respectfully diasgree. It probably doesn't really matter except in principle. 95awd2008 is apparently
going to use his T-Bird for parts. However, I must reply to comment on inaccuracies I find in this thread.
A-Z & people who rely on it aren't a good reference for anything to me.
The confusion & myths swirling around Automotive Cyber-technology are a result of people unqualified to work with,
or on automotive digital control systems & driveability problems they may represent. It's a science, not Voo Doo Magic.
BUT E.E.C. 5 Codes ?
. . . . AUTOZONE ?
. . . . . 32 years?
. . . . What are you talking about?
All FoMoCo Electronic Engine Control systems are an EEC system. EEC is the abreviation of
Electronic Engine Control
EEC systems which do create codes (and not all do) are operating system specific.
EEC IV systems would be CFI & SEFI systems which use speed density logic & codes in older FoMoCo systems.
Many early systems had STAR capability. This onboard ability for systems to self diagnose & Readout it's results.
It thus abbreviates as
STAR = Self Test Automatic Readout.
This began in mid 80's. STAR systems are operating system specific DTC notations. Self Diagnostics atill exist today
in the OBD II PCMs of late model cars.
SEFI is sort of a cross between CFI & TPI speed density, operating systems as FoMoCo developed EECs.
MAFS is where FoMoCo went into OBD I logic and that was around 1993.
That is model and application specific but it makes analyzation very complex so "Uncle" stepped in.
By U.S. Govt. Mandate in 1996 OBD I became OBD II with a uniform code system & "pending code files", as well as
those older fault and/or DTC code presentation such as previous systems also offered from EEC IV onward.
But why am I explaining this ?
Point is a '94 Thunderbird with a 4.6L modular V8 rolled out of Ford's plant equipped with OBD I operating system.
When you get code 15 in OBD I system, it makes no difference if everything mechanical is in perfect order, or not.
Engine will not run correctly & most likely not at all if ROM is scrambled in PCM, which is what a DTC 15 says.
Disconnecting this & that then cranking an engine over to start it further confounds/exacerbates a working PCM.
At the same time it makes no difference to corrupted PCM because if PCM is not working it's not reading or writing DTCs.
Call & response efforts it can not make can not be read or analyzed. Once PCM/ Operating System is corrupted.
Also KAM will not work anymore. KAM or keep alive memory is last resort for diagnostics in flawed systems.
So the more one screws around trying to figure out why there's a problem the worse a problem which existed
or exists becomes as well as the more damage is often inflicted during the shade tree experimentations.
So what I say and what I mean is:
You will not get engines requiring sophisticated operating systems such as OBD I or II to fire up & run well,
if they even run at all with a failed system still wired in, but inoperative for whatever reason there could be.
FBp 