my99 ECUs Ae800, Ae801, Ae802

[viper1982]

With all the information that I will be a good time entertaining.
It was very good doing the searches in the Ecuexplorer's Qery, until the MAP Fueling Table arrived.

I tell you what I did step by step.
1- Converti HEX to DEC = 0x38F: 0x48E = 911: 1166 so far everything ok.
2- Query with Ecuexplorer.
3- I throw a series of 16x16 grid values, ok, but ... the values that I read when converting them to DEC and then doing the mathematical operation that you provided me with AFR = 14.57 * 128 / Value (d) to obtain a readable AFR value is out of range. I think I made a wrong reading of the map or am looking in a non-ECU area.

[viper1982]

Originally Posted by Frenchie

Hi Viper,where abouts in Argentina are you? Was there this time last year,beautiful country, friendly people and good red wine.

Hello ! I am at the southern end of the country. Rio gallegos. Santa Cruz. It is very cold on these sides. I'm glad you met and you got a good impression of this country. As you say the best wines are from the Mendoza area. I was there in January for vacations. visiting wineries.

[Scott.T]

0x38F: 0x48E is the address range in the ECU image for the fuel map.
The Hex data in cells 0x38F through to 0x48E (256 bytes) gives you a 16x16 grid which should be then be converted to decimal then have the conversion calculation applied.

I cant help much with how ecuexplorer displays maps because I just queried the whole image and then drop it into excel and home in on the maps/addresses of interest. My tool predate most of the current applications.
Romraider may be a better tool, just copy paste and edit existing XML

[viper1982]

Originally Posted by Scott.T

0x38F: 0x48E is the address range in the ECU image for the fuel map.
The Hex data in cells 0x38F through to 0x48E (256 bytes) gives you a 16x16 grid which should be then be converted to decimal then have the conversion calculation applied.

I cant help much with how ecuexplorer displays maps because I just queried the whole image and then drop it into excel and home in on the maps/addresses of interest. My tool predate most of the current applications.
Romraider may be a better tool, just copy paste and edit existing XML

Thank you very much I will try what you say, I will see if my knowledge reaches since it is a more complicated subject the correct edition of the .XML if I am successful I count my progress.

Thank you

[viper1982]

Scott! Finally, after several hours of testing, I was able to find the error why I couldn't see the tables with the corresponding values. It was a tiny but significant mistake in this hahaha. a number (1) preceding the search start value. 0x38F was 0x138F.


Now if I could read the Fuel Map and the values made sense.

Fueling MAP:
Hexagesimal = 0x138F: 0x148F
Decimal = 5007: 5263

Now if I continue the Query of everything else.
I wanted to warn you that I had been able to solve it and if someone follows this thread that does not have the same doubts as me.

[viper1982]

Originally Posted by Scott.T

The conversion I'm using has been in circulation/use for 15+ years (not just by me). They are also the same on 1993-1996 ECU of which I have mapped around 400, and all variants UK, WRX, RA, STI. All figures quoted online for these ECU types are based on this conversion.

Your method gives low values. If you applied this to a stock ECU the values would be too low. I'll do the math later.

What gear are you logging in, as it need to be a good 3rd/4th gear pull to get close to target boost. 2nd will under achieve.

Sorry to go back to so old, but what is the standardized value that is finally used to make the tables? or what is commonly adopted by subaru in its values.
14.57 PSI or 14.7 PSI? which is used in a standardized way. It depends on the values that you enter in the conversion so I consult.

[Scott.T]

Originally Posted by viper1982

Scott! Finally, after several hours of testing, I was able to find the error why I couldn't see the tables with the corresponding values. It was a tiny but significant mistake in this hahaha. a number (1) preceding the search start value. 0x38F was 0x138F.


Now if I could read the Fuel Map and the values made sense.

Fueling MAP:
Hexagesimal = 0x138F: 0x148F
Decimal = 5007: 5263

Now if I continue the Query of everything else.
I wanted to warn you that I had been able to solve it and if someone follows this thread that does not have the same doubts as me.

Sorry about missing the '1'. I'll have been back and corrected it.
The data was decoded in an old spreadsheet I hadn't touched for years. I just gave it a quick look and copy/pasted into hear.

[viper1982]

no problem Scott.
I wanted to ask you if you don't mind that I share all the addresses you provided me with the AE8xx ECU in the ROMRAIDER forum to see if someone with experience creating .XML can get to do an Ecu definition or something that can help Romraider to You can do more reading. I don't know if that could contribute something since my knowledge of romraider and modifying .xml are very limited, but maybe it's something useful, right? what you think?

[Scott.T]

I have a licensed Epifan EcuEdit. That might work with Ae80x these days.

[viper1982]

I have that software on the pc. but I did not start to see what I can do with it. I will study it. Can you tell me with what software can I do a complete reading of the ECU or generate a .HEX o BIN of the complete ECU? I do not know if it would be convenient for me to create another new thread for this topic so as not to extend this one so much.

[viper1982]

Ok, here I edited the question since trying the program you were telling me, ECUedit I could see the .BIN / .HEX of both ecu.
Finally my ECU PPP I read it with ECUexplorer "Query mode" Between 00000: 1FFFF It took a long time ... and it generated the .HEX File (I had to assign a termination if it does not record as a flat file, then unreadable for many of the programs) . The ecuedit is a very powerful tool, but you have to study hard and dedicate time to it because for those who don't know it is something complex. But it will keep me entertained for a long time I guess.
I share a couple of photos of map sectors I found using the directions you provided me earlier.
Then I will make the conversions from HEX to DEC and then to the corresponding units. All of this is interesting.

[Scott.T]

If I hadn't said before I meant to say yesterday that ECUExplorer query is how I read out my ECU. As I mentioned above when I read out my VF28 modified tune and saw how little the tuner changed (over 3 visits because after the first visit I was suffering overboost) it drove me down the route of doing it myself

[Scott.T]

How large was your ECU query file that you downloaded from the ECU, and what format does it store it in.

I started creating some Def's in ECUEdit but I need to confirm I am using the correct files.
The files I have found (downloaded from my ECU 15 years ago) seem small, so I think it is just the front end and maps subset.

When I compare them to Ae802.bin files, that I must of acquired at some point, they are much smaller but clearly from the first 1/4 or so of the image.

What doesn't help me, is my downloads were from previously ECUTEK'd Ae802 ECU so the first 20 lines or so of code are very different to the Ae802.bin I have.
I can only assume that this is ECUTEK data/licencing information.

Map addressing appears the same because I have reproduced the Boost Map in ECU Edit using the Ae802.bin and this matches the Boost Map in my spreadsheet which is aligned with the ECUQuery download.

If you can confirm the above question it will help me confirm I am using the correct data. I had almost given up looking for these downloaded files, but found them hiding in a directory I just happened to view with no file extension hence why a .bin or .hex search failed to find them.

Oh! and next time I create a Definition in ECUEdit I must remember to hit the save button !!!!!!!!!!!!!

[viper1982]

Originally Posted by Scott.T

How large was your ECU query file that you downloaded from the ECU, and what format does it store it in.

I started creating some Def's in ECUEdit but I need to confirm I am using the correct files.
The files I have found (downloaded from my ECU 15 years ago) seem small, so I think it is just the front end and maps subset.

When I compare them to Ae802.bin files, that I must of acquired at some point, they are much smaller but clearly from the first 1/4 or so of the image.

What doesn't help me, is my downloads were from previously ECUTEK'd Ae802 ECU so the first 20 lines or so of code are very different to the Ae802.bin I have.
I can only assume that this is ECUTEK data/licencing information.

Map addressing appears the same because I have reproduced the Boost Map in ECU Edit using the Ae802.bin and this matches the Boost Map in my spreadsheet which is aligned with the ECUQuery download.

If you can confirm the above question it will help me confirm I am using the correct data. I had almost given up looking for these downloaded files, but found them hiding in a directory I just happened to view with no file extension hence why a .bin or .hex search failed to find them.

Oh! and next time I create a Definition in ECUEdit I must remember to hit the save button !!!!!!!!!!!!!

Hi Scott, the downloaded file from my AE801 Prodrive ECU is .BIN format It weighs 128 Kb
Just like all the other Roms I downloaded at the time.
I upload it to see if you can give it utility if you need another rom that I put in the image just tell me.

Regarding reading, I initially used the Ecuexplorer range 00000: 1FFFF, but the notebook hung and the reading was not finished, after two attempts and lost time I decided to look for another program, I found one called "ECUmem2" which is an executable file. This allowed me to read the ECU of 00000: 01FFFF without problems and it is the .bin that I uploaded here.

[viper1982]

uhmmmm talking about file size ... check this out .. it's very strange. 1 byte difference? why?

In the first Image, the .ROM on the left I read yesterday with my pc and vagcom cable, with Ecumem2 of my GT99.
The .Rom on the right is the one downloaded long ago from some forum, possibly your reading, your file.

[Scott.T]

128K sounds correct.
I will check what address range I downloaded. I may of given up part way through due to the time taken.
I should be able to progress with ECUEdit definitions. But its logger definitions and map ghosting I want really.

[viper1982]

I was observing that that 1 byte difference when trying to compare both .ROM in the Ecuedit generates an error saying that what I want to compare are of different sizes, so today I changed my ECU in the car, put the AE800 and read with the same method and program that the AE801PPP read. thus achieving a file exactly the same. And so we can compare the ae800 hand in hand with the ae801ppp in the ecuedit.
I upload the file in case it is useful to you.
Unfortunately in my possession I have only those two ECUs. But the AE800 is the same as the AE801 so there is no problem. The only one that would be missing if it were the case is the AE802.

I have no idea why my readings are 1 byte different from the ROMs that are going around the internet.

[Scott.T]

I have all these bin.
Although I may not have the Prodrive one but I do have the map values obtained from an early ecutek beta tester.
I also have STi and P1 bin files and despite what press articles stated they both ran the same tunes.

[viper1982]

if it is not a problem could you send me the BIN of the Ecu of the impreza P1 & STI?

[viper1982]

I found in a forum one that made some map definitions in .XML. Doing a little reverse engineering i just edited the BOOST formula to show it in PSI, it was wrong and it showed a generic value. The rest is intact. They are not all the maps that you revealed but they are some. He helped me at least to see something. You must paste the file in the root directory of the ecuedit.
C: \ Program Files \ ecuEdit \

Just in case make a backup of the original file "ecuEdit.xml" first.

Then when opening the .BIN of the ECU you choose P JECS or I JECS and when opening the BIN you should see some tables.

* The scale of Load does not know in which units it is represented.

[Scott.T]

I'm getting there with the ECUedit definitions.
A bit of a learning curve assigning a bin to a new ECU XML file and using a 2001> WRX definition as the initial 'clone'. There must be an easier way but I'm getting there.

[viper1982]

We are looking for the same thing, I am trying to find ECU definitions that are more or less similar to see if I find the "easy" way to adapt the addresses. But I am still there seeing how it is and how it can be done.

Can you tell me if the scale of "LOAD" is expressed in "MAF voltage" only that it is in another unit where for example 46.00 would actually be 4.6 volt?
I am trying to better understand how the load represents since I have seen that some tables represent them in G / s and others in G / rev, which is really confusing. And it seems more logical and simple to measure it in MAF Voltage.

I see that you have Winols installed, I was investigating and adding the addresses that you gave me of the AE8xx ecu. Very good and complete software. But anyway the ECUedit is being more useful to me to be able to compare the generated LOGS with the tables in real time on the pc.

[Scott.T]

Load is a figure calculated by the ECU code. It isnt a measured value from a sensor for example. It's a combination of things that the ECU uses in the calculation i.e MAP, MAF, Rpm etc. It doesn't really matter what it is as long as all axis that use it show it in the same scale.
I've always just converted it to decimal but it seems to be represented by g/rev.

[viper1982]

Originally Posted by Scott.T

Load is a figure calculated by the ECU code. It doesn't really matter what it is as long as all axis that use it show it in the same scale.
I've always just converted it to decimal but it seems to be represented by g/rev.

Understood thanks

[Scott.T]

Originally Posted by viper1982

Understood thanks

Here you go, for a more detailed answer
https://forums.nasioc.com/forums/sho....php?t=2708033

[Scott.T]

Originally Posted by viper1982

Understood thanks

On the MY2001/02 you can do a little trick with Load to increase the MAF capability.
There is a code/resolution limit of 300g/s for MAF scaling. When you run a bigger turbo you can run into this problem.
The MAF is capable of running more than 300g/s but you just cant scale it.

If you half all the g/s values in the MAF scaling then half all the Load Scale axis for every Map that uses Load (mainly fuel and ignition maps but there may be a few more I cant remember as it was over 10 years ago I did this last) you can trick it into running more than 300g/s.
Because 150g/s in the MAF scale will be equivalent to 300g/s

[viper1982]

Good data that you give about scaling the MAF if necessary. While I don't have a MY01 but it's nice to know.

These days I am looking to be able to make a record like the one you shared above, contrasting the log with the tables of "Base Timming" / "Base Timming + Hi Octane Ign. Advance" & AFR.

I want to do it to try to record the behavior of all the important variables and see how it is projected on these 3 maps. With the current configuration of my motor. I could never see it since I was able to connect to the car recently again since the cable I use had been damaged. I acquired a new one with a better, more stable chip and with this one I am doing everything lately.

To get a good record you can detail which parameters should be included when registering using ECUedit.

I was planning to use:

Engine RPM
Engine Load
Air flow sensor voltage
Ignition Timing
Knock Correction
IAM
Throttle
Manifold Relative Pressure
Primary Wastegate Duty Cycle

Am I missing something important?

I hope any recommendation you can make me. Cheers

[Scott.T]

Originally Posted by viper1982

Good data that you give about scaling the MAF if necessary. While I don't have a MY01 but it's nice to know.

These days I am looking to be able to make a record like the one you shared above, contrasting the log with the tables of "Base Timming" / "Base Timming + Hi Octane Ign. Advance" & AFR.

I want to do it to try to record the behavior of all the important variables and see how it is projected on these 3 maps. With the current configuration of my motor. I could never see it since I was able to connect to the car recently again since the cable I use had been damaged. I acquired a new one with a better, more stable chip and with this one I am doing everything lately.

To get a good record you can detail which parameters should be included when registering using ECUedit.

I was planning to use:

Engine RPM
Engine Load
Air flow sensor voltage
Ignition Timing
Knock Correction
IAM
Throttle
Manifold Relative Pressure
Primary Wastegate Duty Cycle

Am I missing something important?

I hope any recommendation you can make me. Cheers

I'm not sure what parameters are available for logging with ECUEdit because I dont believe there was any support for it when I last used it.
I have just purchased a used Ae800 so I will have a play when it arrives.

[Scott.T]

Have you seen this :
http://www.ecutek.com.au/ecu-tuning/...ecu-comparison

Many years ago (probably about 2002) ECUTEK UK compared the MY99/0 with some interesting facts. This article though seems to go a bit further.

[viper1982]

That Ecutek article was one of those that made me want to read the ECU of my car, and even more after I got the ecu prodrive, with more reason my curiosity increased and it was that I started looking for information on how and what could I connect with. I could not not know what differences were in there between the ae800 and the Prodrive, my curiosity leads me to investigate. It is very interesting what Ecutek says, but it contrasts with reality since I know that in many countries they use the ae800 as an improvement to the ae802, you can read it in many forums.

Too good you got an AE800 ECU, you have fun with the old Jecs again.
Also, later it will be the one you send to edit ECUlabs.

Ecuedit It has very good possibilities of taking readings in these old ECUs, I use it with a VAGCOM KKL cable with the FTDI chip without problems, the connection is good, fast and stable. The cable is from the VAG group (volkswagen / audi / seat)

Then I send you a screenshot of the parameters that ecuedit reads in real time on the ecu jecs ae8xx.

[viper1982]

A while ago I started to test what you say about Logs with Ecuedit, and indeed although it accepts several parameters it does not take all of them, you are right that it does not yet support our Ecus Jecs. The LOAD parameters do not have them, that is, but the addresses must be adapted to the ECU MY01 and beyond. It searches in another sector of the ECU throwing wrong results.
Then the IAM parameter is also in another direction. It does not work.

Conclusion the best way for the Jecs ECU is to take the LOGS with ECUExplorer and then the generated .CSV file is opened with ECUEDIT and already with the .BIN loaded from the ROM of the corresponding ecu it allows to make the comparisons perfectly. You have to work with two programs but the result is very good.

[Scott.T]

See how you get on with these

[Scott.T]

Originally Posted by viper1982

I was observing that that 1 byte difference when trying to compare both .ROM in the Ecuedit generates an error saying that what I want to compare are of different sizes, so today I changed my ECU in the car, put the AE800 and read with the same method and program that the AE801PPP read. thus achieving a file exactly the same. And so we can compare the ae800 hand in hand with the ae801ppp in the ecuedit.
I upload the file in case it is useful to you.
Unfortunately in my possession I have only those two ECUs. But the AE800 is the same as the AE801 so there is no problem. The only one that would be missing if it were the case is the AE802.

I have no idea why my readings are 1 byte different from the ROMs that are going around the internet.

Your files are blank from Address 5000(h) onwards.
This doesn't effect viewing the performance maps but they are incomplete images compared to the ones I have here. Sample Ae800 attached.

They are also 1 byte short of 128Kb.
I needed to add 1 byte to get ECUEdit to recognise them.

[Scott.T]

To save duplicating bin files on the world wide web.

Ae800, Ae801, Ae802, Af040 and Af041 are attached to the OpenECU Forum here : http://forums.openecu.org/viewtopic....=192&start=135

P1 ECU (Ag340) is here : http://forums.openecu.org/viewtopic....=192&start=120

There is also an ECU XML file on that thread, but mine is better.

[viper1982]

Excellent information you have shared. I am already working on the .HML which have more tables than I have found before.
Note that the impreza Prodrive's maps are strangely the same as those of the STI both version 4 and 5. hahah Subaru does strange things sometimes. The same thing happens when I started to compare the maps of the AE800 and the AE801 (I found absolutely no difference) at least in advance maps, combistible or boost. At first glance they are the same. And they are two ECUs that have different labels and everything. The truth is strange. I suppose they must vary slightly in another respect.
Very good info and I am reviewing everything you have sent me.

[Scott.T]

I have a MAF scale to add, just need to work out the conversion

[viper1982]

Originally Posted by Scott.T

I have a MAF scale to add, just need to work out the conversion

I don't know if it works for you but from what I was reading the conversion would be MAF /RPM*60 g/s.

I don't know if it helps for something but I share the EvoScan functions that both subaru and mitsubishi read.

[Scott.T]

Originally Posted by viper1982

I don't know if it works for you but from what I was reading the conversion would be MAF /RPM*60 g/s.

I don't know if it helps for something but I share the EvoScan functions that both subaru and mitsubishi read.

Its the voltage scale vs g/rev for the MY99/00 MAF I'm after.

[Scott.T]

MAF Sensor scale added to XML (attached)

However, the voltage scale is hard coded rather then using values from the BIN.
This Voltage scale is based on that used on the 2001> WRX, so not perfect, but gives a representation. When you rescale a MAF you change the g/s figures, so the voltage Axis is irrelevant really.
I will see if I can spot the voltage scale in the BIN in/around the MAF Scale MAP.

[viper1982]

Excellent work Scott.
I have already added it to all the .XML of the other ECU Jecs of the same type.

[Scott.T]

Minor update.
When I checked my Apexi PFC MAF scale the voltage ran upto 5.12V.
I then checked old data I had on the Ae802 the table was presented with a range of 0 - 512, so I assumed this was equivalent to 0 - 5.12V.
The top few cells are maxed at 300g/s, so I have limited the scale to 4.64V which is the 1st 300g/s.
A Max of 4.64V is very similar to the WRX 2001> which has a max of 4.69V.

Therefore I have adjusted the MAF Voltage scale to match this. Although this is still hard coded.
Many hours of staring at hexadecimal data in the BIN has not identified if the MAF Voltage scale exists in the code.

What websites/forums have you been using for JECS and MY99/00 decoding ?
I assume none have as much data as we have here ?

[viper1982]

Hi Scott. Thus, there is no other forum in which there is as much information as here on this topic and ECU JECS decoding. I have walked through many forums during the last two years, but there is no information and there is no interest in continuing to look for information on these ECUs, since most of them chose to resign or put alternative systems such as Power FC and other systems. I particularly have seen more information on these topics in openecu and romraider, but not as much and valuable as that of this forum where it all started thanks to the addresses you shared. I think that it is very interesting and you want to be kept looking for in addition to the necessary basic technical information that is strictly necessary to achieve the starting point for all this. With no directions to look for as a starting point for everyone, you are blind.
Today by far this thread of conversation is the richest in old jecs ecu.

[viper1982]

Originally Posted by Scott.T

Your files are blank from Address 5000(h) onwards.
This doesn't effect viewing the performance maps but they are incomplete images compared to the ones I have here. Sample Ae800 attached.

They are also 1 byte short of 128Kb.
I needed to add 1 byte to get ECUEdit to recognise them.

I was able to correct my readings from the .BIN ROMS

I took both readings of the two ecu again with another address range and now I read the entire ROM. and it does not leave blank from 5000. I can compare well if I wanted the .bin of the others with mine. Solved.
In my particular case the range used was ROM 100000: 020000

A comment from a Russian helped me, I share it can be useful to someone who wants to read your ecu avoiding the mistake I made.

[Scott.T]

Originally Posted by viper1982

I was able to correct my readings from the .BIN ROMS

I took both readings of the two ecu again with another address range and now I read the entire ROM. and it does not leave blank from 5000. I can compare well if I wanted the .bin of the others with mine. Solved.
In my particular case the range used was ROM 100000: 020000

A comment from a Russian helped me, I share it can be useful to someone who wants to read your ecu avoiding the mistake I made.

Was that with ECUExplorer

[viper1982]

Originally Posted by Scott.T

Was that with ECUExplorer

No, I did it with ECUmem, it is faster and more stable, the Ecuexplorer when I do readings of wide range, I don't know why my PC hangs. This program read me the 128K in about 15 min.

[Scott.T]

Originally Posted by viper1982

No, I did it with ECUmem, it is faster and more stable, the Ecuexplorer when I do readings of wide range, I don't know why my PC hangs. This program read me the 128K in about 15 min.

I'll take a look and add it to my tool box

[viper1982]

When you have time could you explain to me how the progress and fuel tables interact with each other?
I would like to better understand how the association is and how it works with each other depending on the situation.

It confuses me to see that there are HI octane and LO octane tables since I do not understand relationships as one works with the other. If you can evacuate those doubts I thank you.

[viper1982]

Skip that last query as I was searching today and came across a series of Ecutek articles that talk about it and it is not as simple an answer as I expected to receive, it is complex and depends on many factors.

What if I wanted to consult you is for two tables in particular that are in your Ecuedit .XML.
* Lo det fuel compensation
* Hi det fuel compensation

These two tables give results that I do not understand. Can you tell me what it would be?

[Scott.T]

Hi and Lo Det fuel maps seem to be unique to this ECU and are not present as far as I know in the later 2001> ECU.
On the later ECU normally there is a Primary Fuel Map and a Failsafe Fuel Map, plus Base Ignition Timing and Ignition Advance.
Which map gets used is mainly determined by Knock readings and the Ignition Advance multiplier trigger point. For example if the IAT drops to 4 the Advance Map drops the amount of timing as I described in an earlier post. In some cases it may switch fuel maps. This just provides a safety backup of giving extra base fuelling, so does not need to be considered greatly other than alignment of the load scale to ensure the ECU still has control under these Failsafe conditions. Many pro tuners may not even touch this during their 15 minute dyno tune.

Some XML definitions list a Fuel Map A and Fuel Map B which appear to have the same values. It's not understood as to when A or B are used, so the guidance is to make the same changes to both.

With regard to the MY99/00 the hi and lo det fuel compensation maps have been converted believing they represent an AFR correction value, which is most likely dependant on knock feedback.

However, as with alot of the maps and parameters available to adjust there are many than can remain untouched.
Treat them as tools that apply an operating tolerance to the tune.
If when tuning you are setting the key maps to operate within your requirements then these 'tolerance' control maps can be left alone.
This not only applies to the Fuel/Ignition but also the boost control.
On the later ECU (I've not yet found def's for MY99/00) there are also Turbo Dynamic control maps, which again help by applying an operating tolerance and fine tuning.
But as long as you have your Max and Min Wastegate % set to achieve your desired target boot, with very little under or over achievement, then the Turbo Dynamic parameters don't need to be touched.
These fine tuning maps were obviously setup by the original developers, so I figure that as they had much wider knowledge of the ECU operational code, then they are best placed to decide how wide the tolerance needs to be to maintain good and smooth control, of the key operational settings.

[Scott.T]

I have made further changes to the XML based on some information I found I had from 15 years ago.
Its nothing major, but I have rescaled and applied a different calculation to the Hi/Lo Fuel Det maps, which makes them a little more sensible.

I have also added a few more boost compensation maps.
Some are '0' value for the Ae800 because the non-STi models do not have the required sensors. I'm hoping when I apply the changes to the STi/P1 XML some plots will appear.
When I have finished I will post up an example.