Evo 8 ECU In 2g Works!!

[the_mork]

right now i am not to concerned because i found the periphary bit to turn that check off on the 9055 rom, for some reason i cant get it to work with the 9653 rom. besides if it were the fuse i should be having problems with other things as well.

The periphery bit only handles the rear o2 signal. The 9055 rom must not have a check for rear o2 heater which I believe is your issue.


I also received a PM from a member who doesn't have enough posts to post here so I told him I would post.

Since I can't post in this thread yet, even though I've been running an Evo ECU since before christmas, I thought I would help you guys on this O2 sensor thing. When you get check engine lights for silly things like that, you can just turn them off in the ECU and never worry again. I had one that had to do with fuel temperature and was able to just flip it off. Hopefully this helps you guys out a bit.

I'll post your reply but the problem here is that no one has found the bit that controls the secondary o2 heater circuit malfunction. We can control a CEL for the lack of information from the o2 sensor by disabling it in the address FAA but the heater code is the issue and must be handled through actual hardware manipulation.

I did note that there is now a software patch in testing for handling the rear o2 heater on 9s but so far I haven't seen anything for 8s


If anyone isn't sure what is going on here we are discussing adding this line to the metadata for any evo8/9 rom. If you were to copy it directly from here you would need to remove the space from between the < and the word table because this forum is not set up to handle this sort of line as regular text.

< table name="(periphery 0)" category="Misc" address="faa" type="1D" level="1" scaling="Hex16"/>


Then changing the value of that rom to any of these values.

56D0 -No rear O2 no Immobilizer
5650-no rear O2, No immobilizer, No knock
5658-no rear O2, No knock sensor
56D8-no rear O2
5698, no front or rear 02
5690, no front 02, rear 02, or immobilizer
56D2, No immobilizer

 

[mike96]

You could have also tried putting in an anti-fouler with the correct threads to move the sensor out more. I had to do this to clear the CEL from not having a cat on my car.

originally i had it plugged in and out of the way because i have a wideband in its place so i have nowhere to thread it into.

< table name="(periphery 0)" category="Misc" address="faa" type="1D" level="1" scaling="Hex16"/>

i have mine so that i can check either the individual bits or the value he is talking about "(periphery 0)". i tried that with the 9653 rom already and ran into problems with the car running like it had a bad front o2 sensor, not sure why. but the 9055 runs fine with the rear o2 disabled.

 

[4nturbo]

Well you can add me to the list of guys running an EVO ECU I finely got my car back together and running so i stuck an EVO ecu in the car tonight got it running and took it for a ride so now I'm a happy camper The car is pretty much a stock 95 Talon AWD automatic but thats going to change shortly seeing as I now have a way to tune for upgrades with the EVO ecu

 

[GSXDNA]

Ok guys, I finally got my 780cc injectors. Any ideas on a good starting point for injector latency values?

 

[mike96]

Injector scaling and latecy for different injectors. - evolutionm.net

 

[GSXDNA]

Injector scaling and latecy for different injectors. - evolutionm.net

Thank you. I actually already found that link...I was trying to cross reference against any other info. I guess I'll start off with this and see how it goes.

 

[clockworktoy]

If anyone isn't sure what is going on here we are discussing adding this line to the metadata for any evo8/9 rom. If you were to copy it directly from here you would need to remove the space from between the < and the word table because this forum is not set up to handle this sort of line as regular text.

< table name="(periphery 0)" category="Misc" address="faa" type="1D" level="1" scaling="Hex16"/>


Then changing the value of that rom to any of these values.

Have you tried this? And also would this line be added to the evo7base xml file? I think the hardware fix is easy enough got people who don't mind doing the bit of work.

 

[clockworktoy]

Oh and one more thing, has everyone who has used the 9653 rom had any major issues? Im working with sam on a little writeup and so far the most managable roms i have come encountered is the 9653 and the EDM rom originaly suggested.

 

[mike96]

yes it can be put into the evo7base xml. i have it in mie so i can modify the perifary as either hex or as bits. for those who are using the 9055 roms i have a pretty well setup file for both.

 

[the_mork]

Have you tried this? And also would this line be added to the evo7base xml file? I think the hardware fix is easy enough got people who don't mind doing the bit of work.

Yes and no, I have used it for disabling the immobilizer and I am using it to simulate rear o2 but I still have my rear o2 installed. I enabled the rear o2 delete because I will be installing my wideband there temporarily until I move to a different exhaust someday.

What hardware fix are you talking about? The o2 sensor heater fix? If so then this does not fix that issue. If by chance you are talking about a physical immobilizer bypass then I didn't know that one existed but I'll assume that this is about the o2. In that case I think I noted before that there appears to be something for evo9s but evo8s still just have to use a resistor or wire the o2 sensor up somewhere.

 

[clockworktoy]

Ha i should pay more attention next time. And to The mork i miss used "hardware" But thats what lack of sleep does to me i guess. In any case I just left my o2 sensor plugged in and used the tephra mod for rear o2 and no cel.

 

[the_mork]

I thought I would put together some information that is spread all over this thread into a single post so that hopefully the information will be easier for people who are just starting with the evo ecu to get started. I will assume that you have already downloaded and successfully installed ecuflash.


I have not managed to figure out how to post .xml snippets on this forum without adding a space after the first < so remove this space when you paste things. I will be making a quick post in the Forum questions section to see what it takes to fix this and at that point I will edit my post.


The first thing that you need to do is pick out a ROM. I have had success with the 9653006 and I also used the 94170014 and was able to start my car with it but I have not used it for anything else so I can't verify anything about it but jjgrizz73 reported some problems with inverse load issued.

You can find a perfectly stock 94170014 rom at The Aktive Matrix - Log in but you will need to become a member before you will have access to the download section (free membership).

I am using a Tephra modded 9653006 rom on my car which can be found at TephraMOD V5.10 - evolutionm.net and so far it seems to be working well with no CELs. I'm not sure where to find a 9653006 ROM that is stock but I also don't care because some of the Tephra mods are useful. The 9653006 ROM available at aktivematrix.com does not seem to work.



We can start with instructions for the 94170014 ROM. The only modification that you will need to do to this ROM is to disable the immbolizer. A discussion of disabling the immobilizer can be found here How to disable immobilizer on EDM Evo9? - evolutionm.net the address for the immobilizer in all ROMs is the same so it doesn't matter that this was for an evo9.

The short version is that you need to find the metadata for the 94170014 rom generally this will be found at C:\Program Files\OpenECU\EcuFlash\rommetadata\mitsubishi\evo\94170014 Open it with notepad. If you are using Vista then you will need to open notepad as an administrator then browse to the file.

You will see a lot of script that will look odd to you if you are not familiar with html/xml/programming. You need to scroll to the bottom and look for a line that looks like this.

</rom>

Just before this you will need to add the following

<table name="(periphery 0)" category="Misc" address="faa" type="1D" level="1" scaling="Hex16"/>

Afterward open ecuflash, go to File > Options > User Level and change the value to Developer.

Close ecuflash and reopen it then browse to the rom that you downloaded. After opening it you should find that you have a new option under the Misc category called Periphery0. Double click on that and change the value to 0x56D2. There are a few other options for the values that you can use that do different things for your car. They are as follows:

56D0 -No rear O2 no Immobilizer
5650-no rear O2, No immobilizer, No knock
5658-no rear O2, No knock sensor
56D8-no rear O2
5698, no front or rear 02
5690, no front 02, rear 02, or immobilizer
56D2, No immobilizer

Save your ROM and flash it to your car. Your car should run without a CEL but I cannot guarantee that load will be correct or incorrect because reports of inverted load are unconfirmed and could be isolated.








Tephra Mods:

The Tephra mod ROMs require a very similar process.

Unpack the zipped file somewhere convenient. Open the .xml file in the folder and copy the entire block of text.

Find the .xml for your ROM C:\Program Files\OpenECU\EcuFlash\rommetadata\mitsubishi\evo\9653006 and open it with notepad (remember to open notepad as administrator under Vista). Find the bottom entry which looks like this

</rom>

and paste the block of text just before it. After pasting find the places in the code block (near the top of the text that you pasted in) that has an entry that looks like this endian="CHANGEME" and make them look like this endian="big" if you have Ecuflash 1.3 or higher or endian="little" for Ecuflash 1.29 or lower. Also add the immobilizer code that I showed above just below the Tephra text and change the value in Ecuflash. You will also need Ecuflash to be in developer mode for handling the Tephra mods.

Now we need to adjust the additions that Tephra has provided us. Under the Mods section open the "Tephra mod options" and change the values for every option that you don't want to 0 and every option that you do want to 1. The important thing here is to disable Valet mode (at least for testing purposes) because the default situation has the valet mode set to stop the car from running as an anti-theft measure which is very counterproductive for getting your car to run when you're trying to figure out a number of other things at the same time.


Don't forget to reference the first post in this thread and change the values for MAF scaling and injector scaling so that your car will run right.


Valuable links:
How To Tune an Evo - evolutionm.net
How to disable immobilizer on EDM Evo9? - evolutionm.net
ECUflash tutorial for beginners - evolutionm.net
ECUFlash Basics - tutorial - getting started - evolutionm.net
evolutionm.net - View Single Post - How to MOD your ROM with NLTS or others!
TephraMOD V5.10 - evolutionm.net
How-To: Rescale your MAF (without pics) - evolutionm.net

I thought I would add some more quick links that may help you with the physical installation of the evo8 ecu. If you are having any trouble with switching pins around in your harness please check out this thread.
http://www.dsmtuners.com/forums/art...w-remove-replace-pins-harness-connectors.html

I also believe that I have found a source for pins that fit our wiring harness and I have ordered 10 pins which cost me about $2. If you need more/new pins then check this out. I will be posting back to tell you if the ones that I purchased are correct or not when I get them sometime this week.
TYCO ELECTRONICS / AMP|175265-1|Contact | Newark.com


If anyone sees anything that needs to be fixed or has suggestions on cleaning up this post let me know.

 

[delta448]

^That is one way of doing the periphery table set up, and great for people who know how to code hex values or only want to disable the immobilizer, O2, etc., but some others out there might be like me and want it spelled out bit by bit so as to be sure that there are no mistaken values. I haven't had any programming classes since the late 90's...

Note that this method may allow you to pick and disable certain pesky diagnostic trouble codes (possibly even the cam/crank position sensor DTC -that comes with using a USDM rom image- once it is discovered which bit it is tied to.)

If copied as I have posted in the box below, the bits will all appear individually and some of the known bits will be labeled. Also, please note that some bits affect multiple functions, possibly affecting things adversely if you turn something off accidentally or ignorantly and many of the bits still have unknown effects. Also, from what I've read some bits are not activated by entering a value of 1, but 0 instead. I don't know much about this I'm afraid, but it leads me to believe it might be related to some functions not being enabled by default on certain vehicles.

If you're like me and want all 6 periphery tables listed bit by labeled bit, just replace the line of code that the_mork posted above with the code from this post on evom, which you can copy from this box:

<table name="ECU Periphery00 Hex" category="Periphery" address="f9a" type="1D" level="2" scaling="Hex16"/>
<table name="ECU Periphery0 Hex" category="Periphery" address="faa" type="1D" level="2" scaling="Hex16"/>
<table name="ECU Periphery1 Hex" category="Periphery" address="fba" type="1D" level="2" scaling="Hex16"/>
<table name="ECU Periphery2 Hex" category="Periphery" address="fca" type="1D" level="2" scaling="Hex16"/>
<table name="ECU Periphery3 Hex" category="Periphery" address="fda" type="1D" level="2" scaling="Hex16"/>
<table name="ECU Periphery4 Hex" category="Periphery" address="fea" type="1D" level="2" scaling="Hex16"/>

<scaling name="blobbits" storagetype="bloblist" storagebits="1">
<data name="0" value="00"/>
<data name="1" value="01"/>
</scaling>

<table name="ECU Periphery00 (F9A) Bits" category="Periphery" address="f9a" type="2D" level="2" scaling="blobbits">
<table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16">
<data>bit.15</data>
<data>bit.14</data>
<data>bit.13</data>
<data>bit.12</data>
<data>bit.11</data>
<data>bit.10</data>
<data>bit.09</data>
<data>bit.08</data>
<data>bit.07</data>
<data>bit.06</data>
<data>bit.05</data>
<data>bit.04</data>
<data>bit.03</data>
<data>bit.02</data>
<data>bit.01</data>
<data>bit.00</data>
</table>
</table>

<table name="ECU Periphery0 (FAA) Bits" category="Periphery" address="faa" type="2D" level="2" scaling="blobbits">
<table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16">
<data>bit.15 .</data>
<data>bit.14 .</data>
<data>bit.13 .</data>
<data>bit.12 .</data>
<data>bit.11, 0=Disable EGR Test .</data>
<data>bit.10, 0=Disable "weird unknown" timing pull at cruise .</data>
<data>bit.09, 0=Disable cat-Warmup Ign Retard Tables .</data>
<data>bit.08 .</data>
<data>bit.07, 1=Enable High Oct Ign Map Lookup and many other subroutines .</data>
<data>bit.06, 1=Enable WG solenoid? Enable Speed Limit Test .</data>
<data>bit.05 .</data>
<data>bit.04 .</data>
<data>bit.03, 0=Disable Immobilizer function .</data>
<data>bit.02 .</data>
<data>bit.01, 0=Disable Rear O2 Test and fault report .</data>
<data>bit.00 .</data>
</table>
</table>

<table name="ECU Periphery1 (FBA) Bits" category="Periphery" address="fba" type="2D" level="2" scaling="blobbits">
<table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16">
<data>bit.15 .</data>
<data>bit.14 .</data>
<data>bit.13 .</data>
<data>bit.12 .</data>
<data>bit.11 .</data>
<data>bit.10 .</data>
<data>bit.09 .</data>
<data>bit.08 .</data>
<data>bit.07 .</data>
<data>bit.06 .</data>
<data>bit.05 .</data>
<data>bit.04 .</data>
<data>bit.03 .</data>
<data>bit.02 .</data>
<data>bit.01 .</data>
<data>bit.00, 0=Disable Lean Spool .</data>
</table>
</table>

<table name="ECU Periphery2 (FCA) Bits" category="Periphery" address="fca" type="2D" level="2" scaling="blobbits">
<table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16">
<data>bit.15, P0443 P0446 P0403 P0243 P0090 P2263 .</data>
<data>bit.14, P0450 P0451 P0452 P0453 Evap Pres. Sensor .</data>
<data>bit.13, P0441 Evap Incorrect Purge Flow .</data>
<data>bit.12 .</data>
<data>bit.11, P0031 P0032 P0037 P0038 .</data>
<data>bit.10, P1400 MAP Sensor .</data>
<data>bit.09, P0401 EGR Test .</data>
<data>bit.08, P0506 P0507 Idle Test .</data>
<data>bit.07, P0170 P0171 P0172 .</data>
<data>bit.06, P0134 Front O2 Sensor No Activity .</data>
<data>bit.05, P0000 - or with bit.4 .</data>
<data>bit.04, P0000 - or with bit.5 .</data>
<data>bit.03, P0132 P0136 O2 Sensor Circuit .</data>
<data>bit.02, P0133 P0159 .</data>
<data>bit.01, P0421 not in FSM .</data>
<data>bit.00 .</data>
</table>
</table>

<table name="ECU Periphery3 (FDA) Bits" category="Periphery" address="fda" type="2D" level="2" scaling="blobbits">
<table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16">
<data>bit.15, P0128 Coolant Temp Below Reg. Temp .</data>
<data>bit.14, P1603 Battery Backup .</data>
<data>bit.13 .</data>
<data>bit.12 .</data>
<data>bit.11, P0180 P0183 P0461 P2066 Fuel Sensors .</data>
<data>bit.10 .</data>
<data>bit.09 .</data>
<data>bit.08 .</data>
<data>bit.07, P0551 Power Steer Pressure Sensor .</data>
<data>bit.06, P0500 Vehicle Speed Sensor .</data>
<data>bit.05 .</data>
<data>bit.04 .</data>
<data>bit.03 .</data>
<data>bit.02, P0234 P0243 P2263 Turbo Overboost .</data>
<data>bit.01, P0510 Closed Throttle Switch not in FSM .</data>
<data>bit.00, P1715 P1750 etc .</data>
</table>
</table>

<table name="ECU Periphery4 (FEA) Bits" category="Periphery" address="fea" type="2D" level="2" scaling="blobbits">
<table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16">
<data>bit.15, P0140 1=Enable Rear O2 No Activity test .</data>
<data>bit.14, P0069 MAP vs Baro .</data>
<data>bit.13, P0111 Intake Air Temp Circuit .</data>
<data>bit.12, P0554 Power Steering Pressure Sensor Circuit .</data>
<data>bit.11, P1530 A/C1 Switch .</data>
<data>bit.10 .</data>
<data>bit.09 .</data>
<data>bit.08, P0830 Clutch Pedal Switch A Circuit .</data>
<data>bit.07, P0090 Fuel Pressure Circuit .</data>
<data>bit.06 .</data>
<data>bit.05 .</data>
<data>bit.04 .</data>
<data>bit.03 .</data>
<data>bit.02 .</data>
<data>bit.01 .</data>
<data>bit.00 .</data>
</table>
</table>

 

[the_mork]

Want higher sampling from your evo8 ecu? Then read this thread.

MUT at high baudrates WORKS! 62500 tested. - evolutionm.net

 

[jrohner]

My Evo8 ECU just came, now if only I had my car fixed (broken clutch) so I could give it a try.

 

[jrohner]

I swapped the required wires on the Evo harness I bought, plugged the wires and the ECU in, disabled the immobilizer and it fired right up! If I had my clutch fixed I would be ripping around and putting the tune from my EPROM tune into this Evo ECU. I was out logging and tuning my cousins 04 Evo tonight, we had to waste the last half a tank of gas to make room for E85. The little 680 injectors we put in the Evo tonight have a ways to go yet too. We need to get a restricter in the BCS line so we can get more than the 20-20.5 psi that we're at. I'm definitely goona be working on the ECU boost control when I get to tuning my 2g with the Evo ECU; I'm hoping I can somehow use that to hold the boost a little higher on top end and maybe keep the boost down slightly on the low end to keep the drivetrain together.

 

[the_mork]

It shouldn't be too much of a problem, if you look around over at evolutionm there are some recent developments involving boost control including variable boost control based on gear. I might suggest going to a 3 port GM BCS also, they seem to be able to handle higher boost and quick corrections much better.

 

[the_mork]

Is anyone else having problems with "idle control system malfunction"?

I've had a crappy idle for a long time but my 2g ecu never threw a code. The evo ecu did so I replaced my ISC with one off of an RVR and now my idle is great but I still throw the code every few hours.

I was just wondering if anyone else was having the problem or if anyone knew of a way to disable the check.



Also up until last night I've had the car running on wastegate pressure and I've seen a surprising amount of partial throttle knock. I've never been able to see knock before (CEL on knock) so I was just curious how normal it is, it is usually between 3 and 5 counts and I don't have a log yet because my laptop battery is poor.

 

[Silver2GST]

Hey guys, Great Work here! You have really put together some great information.

I am assuming everyone who has flashed the EVO ECU is using the cable sold by Tactrix ? It is a shame we can't change our normal FTDI based ODBII cables from read only to read/write. From the pictures i have seen it looks like all one needs to do is connect a wire from inside the generic looking ODBII they sell to PIN 79 on the EVO ECU and we could basically cut out the cost of the $100 cable. I know ECUFlash v 1.3 and above only allows you to use there cable, but earlier versions can be used with any FTDI based cable.

Any one care to peak inside the OBDII connector to find out which pin to connect to the ECU flash Pin?

 

[clockworktoy]

Im using ecuflash 1.4 and using the 1.3 openport cable. And to the mork i have the same issue and just turned off the idle system check through periphery bites. Oh and one last thing is anyone logging their wideband through the rear o2 with evoscan?

 

[mike96]

is anyone logging their wideband through the rear o2 with evoscan?

I am, what do you need?

 

[PieEyedPiper]

Is anyone else having problems with "idle control system malfunction"?

I've had a crappy idle for a long time but my 2g ecu never threw a code. The evo ecu did so I replaced my ISC with one off of an RVR and now my idle is great but I still throw the code every few hours.

I was just wondering if anyone else was having the problem or if anyone knew of a way to disable the check.



Also up until last night I've had the car running on wastegate pressure and I've seen a surprising amount of partial throttle knock. I've never been able to see knock before (CEL on knock) so I was just curious how normal it is, it is usually between 3 and 5 counts and I don't have a log yet because my laptop battery is poor.

Do you have 3g lifters? Partial throttle knock makes me think phantom knock.

 

[the_mork]

No, I have original lifters. I logged a few pulls and I'm starting to analyze them now even though I don't have a whole lot of idea what is going on. I definitely have some very real knock with high load (18psi) around 6k rpm at about 7 counts that is repeatable but the partial throttle knock comes in at about 20% load between 3-5k range. What is interesting here and makes me think that it might not be PK is that I have wildly aggressive timing in those ranges so I think I'm going to decrement the whole timing map by 1 degree until I can finish up my spring maintenance, clean up all my boost leaks, install a couple leftover bolt ons and actually begin tuning.

I will look into some 3g lifters though. It is probably something that I should have done a while ago but being a non-longevity maintenance problem they've been put off.

 

[the_mork]

Im using ecuflash 1.4 and using the 1.3 openport cable. And to the mork i have the same issue and just turned off the idle system check through periphery bites. Oh and one last thing is anyone logging their wideband through the rear o2 with evoscan?

I was just curious which periphery bit this was, I looked for it on evolutionm.net but I can't find the xml for it, I'll keep looking but if it is convenient for you I'd appreciate the help.

 

[delta448]

I was just curious which periphery bit this was, I looked for it on evolutionm.net but I can't find the xml for it, I'll keep looking but if it is convenient for you I'd appreciate the help.

FCA bit 8.

<scaling name="blobbits" storagetype="bloblist" storagebits="1">
<data name="0" value="00"/>
<data name="1" value="01"/>
</scaling>

<table name="ECU Periphery00 (F9A) Bits" category="ECUPeriphery" address="f9a" type="2D" level="2" scaling="blobbits">
<table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16">
<data>bit.15</data>
<data>bit.14</data>
<data>bit.13</data>
<data>bit.12</data>
<data>bit.11</data>
<data>bit.10</data>
<data>bit.9</data>
<data>bit.8</data>
<data>bit.7</data>
<data>bit.6</data>
<data>bit.5</data>
<data>bit.4</data>
<data>bit.3</data>
<data>bit.2</data>
<data>bit.1</data>
<data>bit.0</data>
</table>
</table>

<table name="ECU Periphery (FAA) Bits" category="ECUPeriphery" address="faa" type="2D" level="2" scaling="blobbits">
<table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16">
<data>bit.15</data>
<data>bit.14</data>
<data>bit.13</data>
<data>bit.12</data>
<data>Disable EGR / Enabled Ign Adv (set bit=1)</data>
<data>bit.10</data>
<data>Enable Warmup Ign Retard</data>
<data>bit.8</data>
<data>Enable High Oct Ign Map Lookup (and many other subroutines)</data>
<data>"WG solenoid? Enable Speed Limit Test"</data>
<data>bit.5</data>
<data>bit.4</data>
<data>bit.3</data>
<data>bit.2</data>
<data>bit.1</data>
<data>bit.0</data>
</table>
</table>

<table name="ECU Periphery1 (FBA) Bits" category="ECUPeriphery" address="fba" type="2D" level="2" scaling="blobbits">
<table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16">
<data>bit.15</data>
<data>bit.14</data>
<data>bit.13</data>
<data>bit.12</data>
<data>bit.11</data>
<data>bit.10</data>
<data>bit.9</data>
<data>bit.8</data>
<data>Lean Spool</data>
<data>bit.6</data>
<data>bit.5</data>
<data>bit.4</data>
<data>bit.3</data>
<data>bit.2</data>
<data>bit.1</data>
<data>bit.0</data>
</table>
</table>

<table name="ECU Periphery2 (FCA) Bits" category="ECUPeriphery" address="fca" type="2D" level="2" scaling="blobbits">
<table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16">
<data>P0443, P0446, P0403, P0243, P0090, P2263</data>
<data>P0450, P0451, P0452, P0453 Evap</data>
<data>P0441, P0442 Evap</data>
<data>bit.12</data>
<data>P0031, P0032, P0037, P0038</data>
<data>P1400 MAP Sensor</data>
<data>P0401 EGR Test</data>
<data>P0506, P0507 Idle Test</data>
<data>P0170 (P0171, P0172)</data>
<data>P0134 Front O2</data>
<data>P0000 - or with bit.4</data>
<data>P0000 - or with bit.5</data>
<data>P0132, P0136 O2</data>
<data>P0133, P0159</data>
<data>P0421 not in FSM</data>
<data>bit.0</data>
</table>
</table>

<table name="ECU Periphery3 (FDA) Bits" category="ECUPeriphery" address="fda" type="2D" level="2" scaling="blobbits">
<table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16">
<data>P0128 CT Below Reg</data>
<data>P1603 Battery Backup</data>
<data>bit.13</data>
<data>bit.12</data>
<data>P0180 - P0183, P0461, P2066 Fuel Sensors</data>
<data>bit.10</data>
<data>bit.9</data>
<data>bit.8</data>
<data>P0551 PS Pressure</data>
<data>P0500 Speed Sens</data>
<data>bit.5</data>
<data>bit.4</data>
<data>bit.3</data>
<data>P0234, P0243, P2263</data>
<data>P0510 not in FSM</data>
<data>P1715, P1750, etc</data>
</table>
</table>

<table name="ECU Periphery4 (FEA) Bits" category="ECUPeriphery" address="fea" type="2D" level="2" scaling="blobbits">
<table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16">
<data>P0140 Rear O2 No Act</data>
<data>P0069 MAP vs Baro</data>
<data>P0111 IAT Circuit</data>
<data>P0554 PS Press Sens</data>
<data>P1530 A/C1 Switch</data>
<data>bit.10</data>
<data>bit.9</data>
<data>P0830 Clutch Pedal Circuit</data>
<data>P0090 Fuel Pressure Circuit</data>
<data>bit.6</data>
<data>bit.5</data>
<data>bit.4</data>
<data>bit.3</data>
<data>bit.2</data>
<data>bit.1</data>
<data>bit.0</data>
</table>
</table>