Skip to main content
Topic: Those Computer Controlled Engines.... (Read 4115 times) previous topic - next topic

Those Computer Controlled Engines....

Reply #15
Holy old thread Batman! :D :hick:

So my trucks random limp-home ness with no CEL is probably the 11 year old cat huh? ...

Those Computer Controlled Engines....

Reply #16
Hahaha, I just sneezed and now I'm seeing spots...:hick:

Anyhow. Carm hit the nail on the head.  OBD-II is basically an emmisions monitoring system.  But it also alows for the tuning of the car.  It's quite indepth when you get to plug it into a program such as Autotap, or EFI Live or HP Tuners.  It's still kind of funny I think that all I had to do is have a buddy plug his computer with HPTuners into my car, and delete codes for emmisions parts.  I no longer have Cats, EGR, or AIR on my car.  Plus I just got a letter in the mail for emissions check and Registration... .

So your problem is most likely somthing that's pretty stupid and easy to fix.  That's related to a bad O2 sensor or your cat's are dying, or something like that.  If you have a laptop I'd suggest ordering AutoTap, it'll read and clear codes, and it's a data logger and instrument panel type thing.

Those Computer Controlled Engines....

Reply #17
AutoTap huh? Where does one find this? It would be useful cause the Grand Prix GT and the GTO are both OBDII as well. I already replaced the front O2 sensor, which made the problem go away for about 4 months. I'm thinking I need to save a few checks and go buy a long-tube header, new cat, cat-bcak, and 2 O2's :D I'll go 17's! :hick:

Those Computer Controlled Engines....

Reply #18
Quote from: koldhearted1;141057
so we do have obd2 on these cars under the dash or where is it? sorry stupid question

96 Explorer....not 84 Cougar.

 

Those Computer Controlled Engines....

Reply #19
It seems here you can find it:  http://www.autotap.com/

Cheapish too. I'll have to pick up one when I go turbo.....on everything.............:rolleyes:

And to clear up one thing....in 94 they knew OBDII was on the horizon.  The EPA mandated that all new engine families (4.6L) were to have OBDII.  Although they had it...it wasn't until 96 that every single vehicle produced had to have a standardized OBDII program.  So the 94-95 Cougs/Birds had a retarded version of OBDII.  Most cars in 94 had a connector, but what you can get out of it isn't very "standard."  Our 95 Mustang 5.0 has one...but I have yet to hook it up to my personal or any of the shop's scanner.  Still to this day, though, not everyone follows this standardization of OBDII.  *COvolkswagenUGH*.......they use 5 digit VW only codes, so when you pull codes from a VW, you get an OBD code that says something like....ok...what caused it?  O2 sensor......???........ok...what is wrong with it?.......which one is it?  The VW code says O2 Sensor (Bank 1, Sensor 1) Voltage too low. 

OBDIII will once and for all take care of this nonsense.  It took until 2005 to find a suitable protocal to standardize diagnostic systems for crying out loud...(CAN - Controller Area Network).  Before 05, there were hundreds of ways ECU's communicated codes to scanners....which is why some scanners can't read some cars, and why most scanners require updates for new cars.  OBDII was far from standardized, but it was MUCH better than OBDI.


Those Computer Controlled Engines....

Reply #21
The only reason it is there is because it HAS to be there....but the OBDII isn't fully functional.  It still is a Ford specific diagnostic programing strategy.  It gives limited information and does its job to the least extent possible.  94-95 Cougars/T-birds are still dyno tested here and not OBDII tested.  I'm pretty sure that the testing machine for OBDII vehicles would reject one because it isn't a 96-newer.  In the emissions class, the teacher instructed us to dyno test anything pre-96, regaurdless of the vehicle having OBDII or not, and Philly is the most strict district in PA, so the state doesn't trust 94-95 OBDII systems to work properly or even read properly on the machine.  Like I said...it's there because the EPA says it has to be there.  But it is NOT OBDII in the manner a 96-newer car is.

Those Computer Controlled Engines....

Reply #22
I dunno about Ford, having all my training on GM, but what I would assume Billyf17 means is that OBD-II was implemented in 94-95 MN12's, but (to use a computer term), in a Beta kind of way. If Microsoft had done it, it would have been MS OBD-II RC1 :D They were close to being fully OBD-II, but not quite.

GM did the same thing for several 94-95 models. They knew OBD-II was on the horizon, so with any vehicles that were significantly changed for 94-95 model year they engineered the cars for OBD-II to prevent having to re-engineer them again in '96. Back in '94 when I was taking GM courses on new models we were told that the new vehicles were OBD-II ready, but not OBD-II compliant because the implementation was not yet fully standardized.  For example, a '95 Pontiac Bonneville had a labotomized OBD-II system - it spit codes out in the P0XXX format but did not monitor for misfire, so the P030X codes were not present.

OBD-II also spelled the end of some of GM's older technologies like TBI and CPI. Those old fuel injection systems simply were not precise enough for OBD-II.

All manufacturers have manufacturer-specific codes, not just VW. With GM a code that starts with P1 or usually means it's GM specific. P0300 would be a standard code for misfire, P1380 would be a manufacturer specific one (in this case, ABS controller failure. ABS is non emissions related so is not required to be standardized).

CougarSE - That 3-digit thing must be Ford only. GM used two digit codes right up until and including 1995. Anybody that's ever had a pre-96 GM and had the check engine light come on would know about code 12 (normal for KOEO - it's a "no ignition pulse" code, which of course is normal with the engine off) and code 32 (EGR system fault)
2015 Mustang GT Premium - 5.0, 6-speed, Guard Green - too much awesome for one car

1988 5.0 Thunderbird :birdsmily: SOLD SEPT 11 2010: TC front clip/hood ♣ Body & paint completed Oct 2007 ♣ 3.55 TC rear end and front brakes ♣ TC interior ♣ CHE rear control arms (adjustable lowers) ♣ 2001 Bullitt springs ♣ Energy suspension poly busings ♣ Kenne Brown subframe connectors ♣ CWE engine mounts ♣ Thundercat sequential turn signals ♣ Explorer overhead console (temp/compass display) ♣ 2.25" off-road dual exhaust ♣ T-5 transmission swap completed Jan 2009 ♣

Those Computer Controlled Engines....

Reply #23
I got you on those 95 GM's. I remember people coming to autozone to have codes pulled on 95 blazers.. things had OBDII ports.. but the scanner wouldn't even power on off the plug... and other GM's had a "beta" like OBDII without the two pins in the "old" plug to jumper it to pull codes.
One 88

Those Computer Controlled Engines....

Reply #24
Quote from: Billyf17;141156
The only reason it is there is because it HAS to be there....but the OBDII isn't fully functional.  It still is a Ford specific diagnostic programing strategy.  It gives limited information and does its job to the least extent possible.  94-95 Cougars/T-birds are still dyno tested here and not OBDII tested.  I'm pretty sure that the testing machine for OBDII vehicles would reject one because it isn't a 96-newer.  In the emissions class, the teacher instructed us to dyno test anything pre-96, regaurdless of the vehicle having OBDII or not, and Philly is the most strict district in PA, so the state doesn't trust 94-95 OBDII systems to work properly or even read properly on the machine.  Like I said...it's there because the EPA says it has to be there.  But it is NOT OBDII in the manner a 96-newer car is.


It is OBD II but it's not "fully compliant". But on that topic, though 1996 was the year that OBD II was required, the systems didn't have to actually be fully compliant until a few years later, right? You sound like you know more about the EPA side. As mentioned above, it does have differences, but it does have several of the OBD II emission monitors and it considered OBD II. An OBD II device is needed to read the 94/95 4.6L. Unfortunately my EEC experience doesn't cover the EEC-V as much. I do know from personal experience that the 1994 4.6L OBD II does not trigger a misfire detection very well.

Those Computer Controlled Engines....

Reply #25
Thunder Chicken-  I know about P1 codes...I'm sorry I didn't specify what I meant with VW.  They have P0 (required), P1, and XXXXX codes.  So you could get a 14506, a 15473, or a 16885, which means didly to anyone without super expensive scanner software.  Unlike P0 codes, VW codes do not have an easy to translate classification system; ex. a P04XX - Evap Leak, P03XX - Misfire.  VW codes come up on a regular scanner as P0 codes, some P1 codes come up as well.  But these codes are very generic, instead of a P0302, a P0300 comes up, which is Misfire Detected....thank you very much...if you were to look up the VW code...it would be like 17205 - Cyl. 2 Misfire Detected.  The code books for VW's are like the size of War and Peace :p.

JeremyT-  OBDII was fully compliant in 96, it had to be...end of story.  But it was refined  in 98 and again in 2001.  Hence the reason a car can pass with 2 readiness monitors not set from 1996 until 2000, but can only have 1 monitor not ready from 2001 on.  And the DLC on 94 4.6's might give codes..but they still use the EEC-IV programing.  Meaning 90% of the time there is an EEC-IV style connector under the dash somewhere.  This is because again, the 4.6 was new in 94 and was required to be "OBDII".  Which meant, in 94 and 95, that the vehicle had an OBDII connector.  But Ford, as did probably everyone else, waited until 96 to fully sync the ECU up with OBDII standards and EPA regulation.

If you didn't know, the EPA sets emissions standards every year for new cars.  They keep tightening up on the standards, the manufactures have to keep up with their controls.  Look at a 96 4.6l and a 2004 4.6l.  Completely different.  Coilpacks to COP, return loop fuel system to returnless.  Ford didn't want to, they had to.  But when the technology allowed, the EPA refined the OBDII system, misfire detection is better, some monitors disappeared because they were obsolete, thermostat monitoring, and the new CAN system.

BTW...the clean air act gets revisited in 3 years....look for OBDIII after that...and look for Gore to lead his charge on the EPA........unless we have a record cold 3 years.....HA.

Those Computer Controlled Engines....

Reply #26
Quote from: Billyf17;141177
Thunder Chicken-  I know about P1 codes...I'm sorry I didn't specify what I meant with VW.  They have P0 (required), P1, and XXXXX codes.  So you could get a 14506, a 15473, or a 16885, which means didly to anyone without super expensive scanner software.  Unlike P0 codes, VW codes do not have an easy to translate classification system; ex. a P04XX - Evap Leak, P03XX - Misfire.  VW codes come up on a regular scanner as P0 codes, some P1 codes come up as well.  But these codes are very generic, instead of a P0302, a P0300 comes up, which is Misfire Detected....thank you very much...if you were to look up the VW code...it would be like 17205 - Cyl. 2 Misfire Detected.  The code books for VW's are like the size of War and Peace :p.

JeremyT-  OBDII was fully compliant in 96, it had to be...end of story.  But it was refined  in 98 and again in 2001.  Hence the reason a car can pass with 2 readiness monitors not set from 1996 until 2000, but can only have 1 monitor not ready from 2001 on.  And the DLC on 94 4.6's might give codes..but they still use the EEC-IV programing.  Meaning 90% of the time there is an EEC-IV style connector under the dash somewhere.  This is because again, the 4.6 was new in 94 and was required to be "OBDII".  Which meant, in 94 and 95, that the vehicle had an OBDII connector.  But Ford, as did probably everyone else, waited until 96 to fully sync the ECU up with OBDII standards and EPA regulation.

If you didn't know, the EPA sets emissions standards every year for new cars.  They keep tightening up on the standards, the manufactures have to keep up with their controls.  Look at a 96 4.6l and a 2004 4.6l.  Completely different.  Coilpacks to COP, return loop fuel system to returnless.  Ford didn't want to, they had to.  But when the technology allowed, the EPA refined the OBDII system, misfire detection is better, some monitors disappeared because they were obsolete, thermostat monitoring, and the new CAN system.

BTW...the clean air act gets revisited in 3 years....look for OBDIII after that...and look for Gore to lead his charge on the EPA........unless we have a record cold 3 years.....HA.


The only thing I could quickly find in regard to my question for vehicles not having to be "fully compliant", but could still be OBD II, in 1996 was this:

Quote

Similar standards were incorporated into the federal Clean Air Act in 1990 which also required all 49-state vehicles to be OBDII equipped by 1996 -- with one loophole. The OBDII systems would not have to be fully compliant until 1999. So some 1996 OBDII systems may lack one of the features normally required to meet the OBDII specs, such as the evaporative emissions purge test.


Maybe the source is wrong. It sounds like the EPA

In regard to Ford's EEC programming in the '94/'95 it still had several monitors required for OBD II that monitored the emissions system. It did have a misfire monitor, catalytic monitor, etc. And it did output OBD II codes and could be read with a generic OBD II reader. That's what I was referring to. I don't disagree with your comments that it differed from 1996, but for the discussion here, I do believe its "OBD II", in short.

I'm not aware of any of the '94/'95 T-Bird/Cougars 4.6Ls having an EEC-IV connector in addition to the OBD II connector under the passenger side dash. I've owned a few and never found or known of such - atleast from my memory.

Those Computer Controlled Engines....

Reply #27
I'm sorry I meant under the hood.  Most of the time, from what I'm told, they put the EEC-IV connector on these vehicles so dealerships could use current diagnostic tools to read the information from the computer.  Mostly because of the limited output of the OBDII connector.  It did read OBDII codes and monitors, but did little in the way of diagnostics.

Those Computer Controlled Engines....

Reply #28
Quote from: Billyf17;141235
I'm sorry I meant under the hood.  Most of the time, from what I'm told, they put the EEC-IV connector on these vehicles so dealerships could use current diagnostic tools to read the information from the computer.  Mostly because of the limited output of the OBDII connector.  It did read OBDII codes and monitors, but did little in the way of diagnostics.

Are you sure about that? Even the manufactures of the EEC-IV compatible scan tools (even cheap ones) specifically state that they will not work on the '94/'95 T-Bird/Cougar 4.6L equipped.

So if the EEC-IV connector really was there and was accessible in addition to the OBD II type connector,  I would think that those scan tools would not have such a reference and would be widely used. The non-OBDII tools are a cheaper than OBD-II compliant tools.

For what it's worth, I never seen an EEC-IV connector under the hood of a '94/'95 4.6L T-Bird/Cougar in addition to the OBD II type connector - for the EEC.

Now, there is an EEC-IV type connector under the hood of those cars, but it's used for the ABS equipped '94/'95 T-Bird/Cougar (and even up until '97) to read the ABS computer and not for the EEC itself.

Those Computer Controlled Engines....

Reply #29
Quote from: JeremyT;141247
Are you sure about that? Even the manufactures of the EEC-IV compatible scan tools (even cheap ones) specifically state that they will not work on the '94/'95 T-Bird/Cougar 4.6L equipped.


I disagree with you. I have a $35 Ford EECIV Code Scanner from CSK (3 years old) that specifically lists every car it will work on, and under Thunderbird/Cougar it goes all the way to 1995. I've never had one nor worked on one, but the book clearly states the scanner will work on those vehicles.