MTCFORUM
02-13-2002, 09:50 PM
OK, with all the chip discussion let me add the real reasons why this paticular 1997 program is bad.
As I have explained before there are two parts the EEC software, the operating system and the calibration. You can different EEC catch codes on the same OS and the chips will interchange. Dennis will verify this.
Well, in 1997 that year Mark was very unique form a software standpoint, a milestone actually.
There were several new features that were added to the software, I'll name some of them now.
The rev limiter and speed limters were no longer hit a certain entry criteria and shut off injectors. They were changed to "soft" limiters that pulled timing, added fuel, shut off only the needed injectors to maintain speed.
The EEC calculated the temperature of the catalysts and if the EEC calculated too high of a temp, it would start adding fuel to cool it off.
It was the first Ford car with all speed traction control. This reduced engine torque and/or manipulated the transmission shifting to lower torque to the wheels.
It was the first car with a tach that was given it's signal by the EEC rather than a hardware from the ignition module.
It was the first Ford car with coil on plug ignition system.
It was the first car with a digital MLPS (now called TRS) rather than a resister wiper.
The majority of the info on the dash was now boradcast accrossed data lines rather than hard wires. There is actually a trans overtemp warning in the message center if the motor gets too hot.
There are other things as well, but there are just some highlights. Now, why is this all important?
Like any large change to an OS, there were errors. Some of these errors made it into the first batch of production '97s, like the BLX3 code. For example, you know that if you put your foot to WOT during crank, the EEC shut off the injectors as a way to clean a flooded engine out. Well, try this on a BLX3, the car will start, that's bad. So, with the errors that made the start of production, there are some weird things that happen when you put a chip on and "re-direct" the software to somewhere else.
jerry
As I have explained before there are two parts the EEC software, the operating system and the calibration. You can different EEC catch codes on the same OS and the chips will interchange. Dennis will verify this.
Well, in 1997 that year Mark was very unique form a software standpoint, a milestone actually.
There were several new features that were added to the software, I'll name some of them now.
The rev limiter and speed limters were no longer hit a certain entry criteria and shut off injectors. They were changed to "soft" limiters that pulled timing, added fuel, shut off only the needed injectors to maintain speed.
The EEC calculated the temperature of the catalysts and if the EEC calculated too high of a temp, it would start adding fuel to cool it off.
It was the first Ford car with all speed traction control. This reduced engine torque and/or manipulated the transmission shifting to lower torque to the wheels.
It was the first car with a tach that was given it's signal by the EEC rather than a hardware from the ignition module.
It was the first Ford car with coil on plug ignition system.
It was the first car with a digital MLPS (now called TRS) rather than a resister wiper.
The majority of the info on the dash was now boradcast accrossed data lines rather than hard wires. There is actually a trans overtemp warning in the message center if the motor gets too hot.
There are other things as well, but there are just some highlights. Now, why is this all important?
Like any large change to an OS, there were errors. Some of these errors made it into the first batch of production '97s, like the BLX3 code. For example, you know that if you put your foot to WOT during crank, the EEC shut off the injectors as a way to clean a flooded engine out. Well, try this on a BLX3, the car will start, that's bad. So, with the errors that made the start of production, there are some weird things that happen when you put a chip on and "re-direct" the software to somewhere else.
jerry