Help to identify Maps in Euro WRX MY03

[crispyduck]

I've been trying for a while now to identify my maps from MY03 Impreza 2.0 WRX (EURO) [AH750-5141]. I'm at the stage where I could do with some expert help in identifying some maps especially the wastegate map.

Attached is the ecuEdit XML file of what I have so far. It includes a number of "Test Maps" where I think there may be something. I think "Test Map 7" and "Test Map 8" might be what I need. Anyone kow if this is correct?

Also if anyone knows what the other "Test Maps" are I would greatly appriciate the assistance. Please let me know if you need any more information.

Minor edit: Note, attached XML config assumes a 192K image size. I've uploaded a 160K and 192K image in the above referenced thread.

-Steve.

[Freon]

I could load the file, but couldn't open the hex viewer in Ecuedit. Can you post a 192k version of your ROM?

[crispyduck]

I could load the file, but couldn't open the hex viewer in Ecuedit. Can you post a 192k version of your ROM?

Freon, thanks for trying to take a look. I've uploaded a 192K version of my ROM in the link I referenced above.
If you need anything else just ask.
-Steve.

[Freon]

Ah, guess I could've done that myself, then. Oh well, I'll see what I can find.

[calvinc]

here are the most important offsets for your rom type;
Revision: A4TE001G - MY03 Subaru Impreza 2.0 WRX (EURO) [AH750-5141]

calvin.

[Freon]

After looking at the above, it looks like you already have them. Test map 7 and 8.

Map1 (initial) 8x8
R: #2A613 2 byte value*50
C: #2A623 1 byte
D:#2A62E 2 byte

Map2 (max) 8x8
R: #2A6AE 2 byte value*50
C: #2A6BE 1 byte
D: #2A6CB 2 byte

I'm not sure if any further value translations are required.

[Freon]

Gee, this is fun.

MAF 47x1
R: #28028 2 byte (val/48 ??)
D: #2808B 2 byte, unsure of translation, assume val/8192 is close for "per cylinder g/s"

Rev limit (fixed)
2907E val * 50 2 byte (comes out to 7100)

I also think you reversed your high and low det map.

I had mixed results just translating the addresses that calvin posted by just adding 8000h. Rev limiter was dead on at least.

[crispyduck]

Calvin, Freon,
Thanks very much for all your help here guys. I'm off to update my ecuEdit xml configuration so I can finally see all this information. Some kind person on here has remapped my ECU and I'm off to confirm what's changed before reflashing and testing.
-Steve.

[crispyduck]

Ok guys,

I've now added some of the above information from Calvin and Freon. Calvin, I found that some of the early offsets were one byte out. Freon, your right my Low and High Det maps were the wrong way round (thanks!). I've also corrected some row and col values and locations especially for load.

Attached is my updated ecuEdit XML config file. Below is a list of items from Calvin that I'm being a dummy at getting visualised (the items without a star '*'). The main problem is knowing the power, byte order and mask, row and col size, and the formulas. Does anyone already have an example XML file with all this information in for their ECU? I'm more than happy applying this to my ECU, it just helps to have an example to work from.

Revision: A4TE001G (UK WRX 03 - AH750 5141)

== THESE OFFSETS ARE FOR ROM FILES WITHOUT THE 8K RAM BLOCK (192K image size adjustment (plus 0x8000) after the slash '/') ==

---- 3D MAPS ----
*0x2262D/2a62e (140845) : Initial Wastegate Duty A
*0x226C8/2a6c8 (141000) : Maximum Wastegate Duty A
*0x2253F/2a540 (140607) : Desired Boost (A-Auto)
*0x225A4/2a5a5 (140708) : Desired Boost (B-Manual)
0x22DC0/2adc0 (142784) : EGT Limit
*0x20CB6/28cb7 (134326) : Low Detonation Fuel Map
*0x20DF9/28dfa (134649) : High Detonation Fuel Map
*0x212A2/292a3 (135842) : Ignition Base Map
*0x217E9/297ea (137193) : Ignition Correction Map
---- 2D MAPS ----
0x210AE/290ae (135342) : Boost Limit
0x20089/28089 (131209) : MAF Sensor Scaling
0x22C5B/2ac5b (142427) : CEL Threshold - Boost Solenoid
---- DATA MAPS ----
*0x2107E/2907e (135294) : Rev Limit
0x20C72/28c72 (134258) : Fuel Map Knock Switch Threshold
0x21902/29902 (137474) : Knock Learning Range - Engine Load
0x21912/29912 (137490) : Knock Learning Range - Engine Speed
0x2059F/2859f (132511) : Injector Size Scaling
0x22AF0/2aaf0 (142064) : CEL Threshold - MAF Sensor
*0x228D9/2a8d9 (141529) : Select Monitor ID
0x2109F/2909f (135327) : Speed Limiter
0x218BA/298ba (137402) : Initial Advance Multiplier
0x218BB/298bb (137403) : Coarse Ignition Learning Range - Engine Speed
0x218C3/298c3 (137411) : Coarse Ignition Learning Range - Engine Load
0x21928/29928 (137512) : Fine Ignition Learning Range - Engine Speed
0x21930/29930 (137520) : Fine Ignition Learning Range - Engine Load
0x218F5/298f5 (137461) : Knock Detection Range - Engine Speed
0x218FD/298fd (137469) : Knock Detection Range - Minimum Engine Load
0x20C0B/28c0b (134155) : Closed Loop - Throttle % (Manual)
0x20C0C/28c0c (134156) : Closed Loop - Maximum Vehicle Speed
0x20C0E/28c0e (134158) : Closed Loop - Maximum EGT

I'm doing this to help me compare the differences between my original ECU maps and this modified one I have. I'm nearly done and hopefully tomorrow will post again with the location of a few map changes that I have not seen documented anywhere yet!

Cheers for any help here,
-Steve.

[calvinc]

Calvin, I found that some of the early offsets were one byte out.

on the contrary my dear watson...you guys obviously dont have the map format.

3D maps:
<y-axis values><y-axis length - 1><x-axis values><x-axis length - 1><type><z-axis values>

2D maps:
<y-axis values><y-axis length - 1><type><z-axis values>

type definitions (3D):
0x04 = y16 x8 z8
0x14 = y16 x8 z16
0x05 = y16 x16 z8
0x15 = y16 x16 z16

type definitions (2D):
0x00 = y8 z8
0x01 = y16 z8
0x10 = y8 z16
0x11 = y16 z16

the type definitions represent the bit read length. an x,y,z of 8 means read as the character (8bit). an x,y,z of 16 means read as short (16bits)

so the only offset you should need is the 1 to the <type>, the rest is all available within the map itself.

calvin.

[Freon]

Is the XML format EcuEdit produces off agreed standard? I'm just using EcuEdit GUI (latest version) and save the XML.

[crispyduck]

Is the XML format EcuEdit produces off agreed standard? I'm just using EcuEdit GUI (latest version) and save the XML.

Me too....

[epifan]

3D maps:
<y-axis values><y-axis length - 1><x-axis values><x-axis length - 1><type><z-axis values>

2D maps:
<y-axis values><y-axis length - 1><type><z-axis values>

This is actually only for some ECUs, like A4TE001G, for others we are can't apply this formulas. Just look at Low Det Fuel map for A4TE001G (red and yellow cells is unused, green-blue is used bytes)

and Low Det Fuel map of not applicable A4TF500F (US WRX 02)

[crispyduck]

on the contrary my dear watson...you guys obviously dont have the map format.

That's fantastic information. Thank you for sharing this Sherlock , it makes much more sense now.

[crispyduck]

Continuing to analyse the differences between my standard Euro MY03 WRX and a P** version. Below are the difference that I can not explain. In the illustrations the left side is my original ECU and the right side is the P** version. All information is in hex and relates to my above 192K image.

I know this is a lot to ask because it's getting very detailed now and perhaps now there are no quick answers but ... anyone care to have a go at explaining what these, as yet, unidentified changes relate to?

If I feel confident at explaining these remaining changes I'll reflash my car with it and give it a try. I can hear some of you say 'just flash it!' however I'm being overly cautious here ...













-Steve.