Instead of revise the "cracking the ecu (http://www.rx8club.com/showthread.php?t=81801)" thread, I want to start a new one with all information update and put in one thread so that we may share what we have and keep this thread more clean.

Currently there are a few solutions for reflashing the ECU. However from reading the forum and research, the following are the break down:

One is the AccessPORT, if you go with this route, buy from MazdaManiac with tuning support. This one is good for professional tuning as it protect the tuners' properties/maps.

The second one is Hyme's sCANalyser Pro Tuner. This is the best solution for those that want to tune it yourself or get a group of people to chip in to buy the hardware and shared to cost and would allow you to tuned multiple cars; best cheapest solution you can buy.

Third, well go with my solution loL! DIY using mazda flashing software and the J2534 device. This will allow you to invest more with other cars model as well keep update to the most recent flash put out by mazda. This is also why I would recommend Hyme's solution as I'm sure one day who know, J2534 API may offer for the sCANalyser unit.

The other I think it's EFIDude? Since I have no info, I will not discuss this. From the open ecu end, they are working on the J2534 as well, but I don't know if it will be another option for us RX8; I'll leave it to you to find out and decide the rest and will not debate on who is better than who :p

Now come the fun part. Lucky for those users at open ecu they have a handful of supports and map created by users and all the good stuffs, etc. and that makes me jealous in many ways. So what I am proposing is since we have the solution for us to flash the PCM, we should create some user knowledge sharing to shared our finding and creation openly; and of course leave the copyright materials to those who owned as secret, such as professional map created and tune by vendors, etc.

I will use this thread to keep everyone up date and share more information as I found suitable and I would like to thanks a few other in this forum as they have help me sourcing the material I need to place my PCM on bench and you know who you are.

I would like to start out with the most basic information as these are the information would be most useful for everyone and working from there. Currently this is the tentative list of information that I would like to discuss and shared:

1. How to change the FAN control coolant temperature
2. How to disable CEL DTC codes
3. Identifying different map: Meter Oil Pump, Ignition, Fuel, etc.
4. How to search and verify for map from scratch with the help an disassembler.
5. How to scale each map to support FI
And the more advance for the code at heart:
6. How to create multiple maps and switching between them
7. How to create other features not available, like turning the dummy oil gauge to something useful, launch control, etc

For me, I don't think 6-7 will be achievable by myself but just want to throw some idea around and hope one day we might have enough info to piece them together.

For today, I would like to share the following:

Since I'm working on my car with flashID n3z2et (2003-2004 Cal MT), all reference location and values are coming from this flash version. I have completed disassemble the flash as I was working on and off in the past 6 months and will be using my spared PCM as a guinea pig. If you want to contribute with other flash version, please add to the thread and If I have time, I might be able to pull the same info from different version as once the code is located from one version, searching for the same information should be quite easy from the next version as our PCM speak bigendian language once you understand them :)

I have a few forum member that offer me accessing to new flash file, I will pm you in due time when I'm ready to work on those new files :)


How to turn on fan at lower coolant temperature?
There are three fan control modes:

Low speed two fans
Hi speed single fan
Hi Speed two fans


In the flash, there are three location for ECT value and only two modes are use.
Low speed two fan turn on at 97°C, turn off at 94°C
Hi speed two fans turn on 101°C, turn off at 98°C.

ECT value in 32bit float data type for fan control:

Fan Control #1
0x76700 Turn on if temperature reached (97°C)
0x76704 Turn off after temperature dropped (3°C)
Fan Control #2
0x76708 Turn on if temperature reached (97°C)
0x7670C Turn off after temperature dropped (3°C)
Fan Control #3
0x76710 Turn on if temperature reached (101°C)
0x76714 Turn off after temperature dropped (3°C)


How do I disable the Check Engine Light for each DTC Codes?
There are 4 tables, 1 DTC code lookup table, 3 monitoring sub-routines monitoring status table, some are checked and stored if errors and some just check and warning.
DTC Codes lookup: 0x7C8E4 - 140 x 16bits int DTC codes (only 124 standard ones are defined: P0030-P2504, U0073-U0167)
DTC Monitor 1 on/off 1 bit: 0x7C9FC - 140 x 8bits byte, stored value monitoring?
DTC MOnitor 2 on/off 1 bit: 0x7CA88 - 140 x 8bits byte, pending value monitoring?
DTC MOnitor 3 on/off 3 bits: 0x7CB14 - 140 x 8bits byte, bit 1 on/off, bit 2 system shutdown, bit 3 limp mode

So let say if you want to disable P0420 code, you would set all value to zero in the three monitor table at position 43rd: 0x7C9FC+42, 0x7CA88+42, 0x7CB14+42, in an array, the table index start at 0, so the 43rd position has index of 42.

For anti-thelf disabling, I think placing all zero on 74th position for P1260 should do something, but I doubt it's that simple; I need yet to verify.

Next order of business are rom check sum: 0x7fb80, 3 x 32bits int


For more advance stuffs:

Scaling tables:
ECT Sensor scaling: 0x6F430, 32 x 32bits float
MAF Sensor scaling: 0x6F65C, 48 x 32bits float
IAT Sensor scaling: 0x6FAB0, 16 x 32bits float

I also have some information about Metter Oil pump and the fuel/ignition map. Still need to working on the injectors pulse and will share that next time after I complete piecing together my Turbo project.

And the following attached screenshot are for a sneak peak at what I'm working on. In due time, you all will have access to these information, so keep this thread clean and well behave. If you scratch my back, I'll scratch your? ;)

FlashEdit.zip contains application FlashEdit.exe (required .net 2.0 Framework to run) and definition file SW-N3Z2ET000.xml

The binary romz file is too big to upload, pm me if you need one.

Reserved for future use
So I need to wait 30s for each post? :)

Reserved for future use #2

Reserved for future use #3
You may post your reply below :)

I'm not sure you have the fan functions correct .
My understanding was
1 2 fans low speed 97C
2 max temp allowable with motor off . 97C IE turns fans on if temp goes over this with engine off . Not sure on this though .....
3 2 fans high speed 101C

I'm not sure you have the fan functions correct .
My understanding was
1 2 fans low speed 97C
2 max temp allowable with motor off . 97C IE turns fans on if temp goes over this with engine off . Not sure on this though .....
3 2 fans high speed 101C

if that is correct, then I need to re check the assembly codes for the 3 values location. Reason I believed there is a 3 modes fan setup is because of the two temp are same, one of the branch statement in the assembly code checking the two location would of trigger a different flag if the temp are different but with current same temp #, it never have a chance to execute. Also if you check the wiring diagram on how the fans are hooked up, you will see what I mean. Btw, don't confuse the control # with mode #, they are independent description and notice I choose the word carefully not to use FAN1 or FAN2, etc. You need the combination of the 3 controls/flags to create 3 different modes. Now if you enter all location with same number, you would create a single mode on/off hi speed fan.

Low speed = two fans running hooked up in series (high resistant? whatever the electrical term is).
Hi speed = two fan running hooked up in parallel (low resistant?).
If you trigger the switches correctly, you can have one of the fan run by itself at high speed (passenger side I believe).

So total 3 combined modes. If you happened to edit the two entries for 97, you want to edit at both location to preserve the factory two setting modes, otherwise, you will create the third mode which is a one fan hi-speed mode. Question is why Mazda chose to use 2 modes instead of 3? And why they use low/hi speed two fans instead of single speed 1 or 2 fan?

When the motor is off the coolant and other temp (IAT & ambient temp) will play the role of triggering the fan on/off (I still need to verify what is the threshold value are); if the engine happen to be on HI speed 2 fan, it will stay on until other event trigger (key off will not trigger the fan off if the temp is above certain number that is not define in that table mentioned and it is a constant set in the rom at other places and there are other trigger that cause the fan to swith on/off after key off); because the coolant is not circulating when engine is off, cooling the radiator will not cool down the water in the engine that much. This is also why sometime when the fan is on after you turn off the key, and you turn back on/off again, the fan would stop if the engine bay wasn't that hot.

in due time I will prove or disprove this claim with my PCM on bench, unless someone already done this can confirm.

would be good to know for sure . The way i read the wireing diagram the 3 possible modes are :

2 fans on slow
1 fan on slow 1 on fast
2 fans on fast

anyway , good work i will follow your thread with interest ....

seikx8

connectors are good? :)

good job.

beers :beer:

If anyone wants to see the AccessTuner instructions, which defines a bunch of maps in the PCM and what they do, I'll put them here: http://www.geocities.com/arghx/Rx-8_AccessTuner.pdf

There is an explanation of cooling fan function and its associated tables on pages 24-25.

Also, I have the SAE J2534 standards "Recommended Practice for Pass-Thru Vehicle Programming" (2002) and the 2006 update, "Optional Pass-Thru Features" in PDF form. PM me about it.

seikx8

connectors are good? :)

good job.

beers :beer:

Thank to you and other, I got all the connectors and some extra plugs with no pins, after talking to one of my college friend recently, which I forgot he is working as an engineer told me I should of call him and could source those connectors and pins easily :banghead: So lesson learned is to keep in touch with your buddy, however that cannot compared to the kindness from most of these forum members :)

I'm still working on the wiring to simulate the ignition key acc/on/off, etc.. otherwise everything look good.

If anyone wants to see the AccessTuner instructions, which defines a bunch of maps in the PCM and what they do, I'll put them here: http://www.geocities.com/arghx/Rx-8_AccessTuner.pdf

There is an explanation of cooling fan function and its associated tables on pages 24-25.

Also, I have the SAE J2534 standards "Recommended Practice for Pass-Thru Vehicle Programming" (2002) and the 2006 update, "Optional Pass-Thru Features" in PDF form. PM me about it.

That document does give a lot of info. Look like I don't need to do much of the homework and can just piece the info from the ROM location to the description. Thanks for the cheat sheet and that's a lot of knowledge to digest :)

For the fan control, it still doesn't explain what fan1 a & fan1 b does to the actual fan switches, pretty vague description. About the fan2 vss, I missed the vehicle speed part.

Thank to you and other, I got all the connectors and some extra plugs with no pins, after talking to one of my college friend recently, which I forgot he is working as an engineer told me I should of call him and could source those connectors and pins easily :banghead: So lesson learned is to keep in touch with your buddy, however that cannot compared to the kindness from most of these forum members :)

I'm still working on the wiring to simulate the ignition key acc/on/off, etc.. otherwise everything look good.

uh, no.

thanks for keeping of with the project. i just gave you stuff that was going to rot in my garage! :lol:

beers :beer:

would be good to know for sure . The way i read the wireing diagram the 3 possible modes are :

2 fans on slow
1 fan on slow 1 on fast
2 fans on fast

anyway , good work i will follow your thread with interest ....

You got the "1 fan on slow 1 on fast" wrong :) you can't have a low speed fan without changing its resistant (connecting it to a resistor)
I was bored, so I created this diagram showing 3 different circuits by grounding the 2 pcm pins in 3 different combination to drive the 3 relays.

http://www.rx8club.com/attachment.php?attachmentid=133997&stc=1&d=1235190156

uh, no.

thanks for keeping of with the project. i just gave you stuff that was going to rot in my garage! :lol:

beers :beer:

It's like a hobby that have no end :)
I don't think they'll rot, more of paper weight? :lol:
:beerchug:

Our map locations will vary depending on flashes, like my MAF is 0x6e694, and IAT is 0x6e4a0. I have a few other ones verified. Something that is puzzing my right now is, whether or not there are 1-2, 3-4, & 5-6, or 1-4, 5-6 & Hysteresis. Originally I worked on this and conclude the latter of those, but have read about others claiming the former. The dtc thing is great info, I hope I can find that in my rom, and work with it, that has been something I have been interested in, but havent looked into yet, thanks for the direction. The oil metering table I originally confused it with a fueling limp mode and didn't touch it but I am pretty sure I have it identified properly at 0x77c78 20X20. I have some other tables like the baro comps, injector size, o2 sensor, primary idle speed, rev limiter and others. I have been working with both CA model and non Cali flashes. Let's figure this thing out.

It's different from year to year.

04 has 1-2 3-4 5-6 and Hysteresis
05 has 2 maps plus Hysteresis
06-08and up has 2 maps and Hysteresis but is different from 05 in other respects.
09 is different but I don't know how.

I'm not sure of the differences this is information Jeff (MM) passed on to me in our talks.

So there are 4 different software versions of the PCM for the RX8.

Slight hijack, but can you pull the stock ignition map out of there for comparision with my own?

You got the "1 fan on slow 1 on fast" wrong :) you can't have a low speed fan without changing its resistant (connecting it to a resistor)
I was bored, so I created this diagram showing 3 different circuits by grounding the 2 pcm pins in 3 different combination to drive the 3 relays.

]

Good work .

Slight hijack, but can you pull the stock ignition map out of there for comparision with my own?

Here you go... http://www.rx8club.com/showpost.php?p=2600151&postcount=31


Hows that 3 rotor renesis coming along? :eyetwitch

Well, the good news is I have bought two spare donor engines for the grand total of £2 (~$3), bad new is they're both pretty knackered, but hey, gettting stripped down anyway...

I've been looking into the S-DAIS, and it looks like the SSV valve actually opens at 3000 RPM, not the original 3750 as advertised, can anyone confirm this or dispute?

I was looking at your map at 6DB14, and I have a similar map at 6bc3C. Awhile ago when I started tuning on this thing,I unplugged my o2 to get out of closed loop which made me a bit lean at idle, and I increased the table values and it brought my idle afr's back down... Strange, right? Unfortunately, at that moment, I wasn't monitoring the timing. Looking at it again, with the two matching tables, it would make sense to be a leading and trailing timing table, but it doesn't match my actual advance at idle either.

Okay, so if I get this right the DTC bits are
00 No check
01 Check
03 Check Shutdown
05 Check Limp

It's different from year to year.

04 has 1-2 3-4 5-6 and Hysteresis
05 has 2 maps plus Hysteresis
06-08and up has 2 maps and Hysteresis but is different from 05 in other respects.
09 is different but I don't know how.

I'm not sure of the differences this is information Jeff (MM) passed on to me in our talks.

So there are 4 different software versions of the PCM for the RX8.


My 04 doesn't have 4 tables, just 3. 1-4 5+6 + Hyst. Plus how about some talk on the strategies Mazda uses for map switching, like TP fueling compared to Load. Or the Oil metering... Is it strictly by RPM that makes the transition? Something else I was looking for, was the VSS fan operation... Is it 40 & 32? During an autox event I was be leaving the course around 205-210 F. I'd like to keep the fan on longer so High rpm heat, with lower vehicle speeds, it can still cool more. Any thoughts?

More fan stuff from Mazda

what do the hysteresis maps look like?

what do the hysteresis maps look like?

The stock ones look the same.

It's been dead for a bit...
I speculate that I have found the Throttle position map in the cal 03 mt rom, I haven't actually tested it yet, but it's 21x18 16 bit it starts @ 73A00, 3 different ones in that area, not sure why yet. I have 3 in my rom that are identical to yours. A little testing would verify it's TP.
I went back and rechecked my idle timing table against n3z2et @ 6DB14 and it alters my fueling, not my timing( but they do look like a matching leading and trailing table)... and I can't find a matching table like 6E048, which I was thinking might be the idle timing.
Other than that, any thought on the SDAIS system? I have some addresses, but can only really verify the 6th port and the VDI.
Another table of interest to me was a Tip-in fuel enrichment... I don't have anything on this yet.

you can tune on your own with accessport using racetuner. i really don't see how efidude or scanalyzer would be better than that for the do it yourselfer. and coob always gives you mazdas latest flash with purchase of AP. you can see the whole map.

i'm not sure if i'm following this thread right, but if you guys want to know what the stock map is supposed to look like, i can show you.

you can tune on your own with accessport using racetuner. i really don't see how efidude or scanalyzer would be better than that for the do it yourselfer. and coob always gives you mazdas latest flash with purchase of AP. you can see the whole map.

i'm not sure if i'm following this thread right, but if you guys want to know what the stock map is supposed to look like, i can show you.
We had this discussion on Cobb Forums. Because there is more to the world than just USDM.

Cheers

Andrew

Hey guys!

First of all, I'd like to comment on all the hard work some of you have put forth into this project - especially seik! I read through the "cracking the ecu" thread, and some of it really reminded me of the work going on in the EvoX/ralliart community (down to the processor - which is of a similar family).

While it looks like now a major portion of the maps are extracted, I was wondering if I might be of any service.. I'm pretty much useless i software reverse engineering, but if it hasn't been done, and someone could take some detailed pics of the traces on the ECU circuit board, I could at least potentially help determine which sensors/devices attach to which ports on the processor. Is that unnecessary by this stage?

Man, I just wish I have more time to spend on this project. Just want to drop by with no update still. However my turbo fabrication is about 90% complete and I work 10+ hrs a day now, so you can guess why I haven't frequent this board for a while.

I've been looking into the S-DAIS, and it looks like the SSV valve actually opens at 3000 RPM, not the original 3750 as advertised, can anyone confirm this or dispute?

I think I've seen this before when I traced the code and I was wondering the same. Maybe Mazda change these value to match the engine power curve with new fuel/timing values. And if i recalled correctly, there is a low-high and high-low opening scheme preventing the valve from flip-flop; or is it something else that I was working on :dunno:.

Could be 3000 - but the effect of it is felt a few hundred rpm later - hence the discrepency

Hey, is there still interest here? I've been in contact with Colby at OpenECU as well as a few others that are looking to add RX-8 support. I've also been doing my own work with this and have a few ROM's from different years including a RB tuned ROM image.

Good to see you back

yes

how are you getting your ROMs?

Well, I was playing around with the lower level protocols for a while but then decided to pick up a Harrison R&D unit since I wanted to focus more on the ROM itself then the process of reading and writing (since that seems to be handled pretty well at this point). The ROM's I have are pulled from people I know around here. I got the latest U flash straight from the Mazda MMP utility though and the RB flash was sent to me.

I will admit I've been busy with work and doing an engine swap (lost a coolant seal on rotor 2 at 153,792miles) so my work with the ROMs isn't as far as I'd like and it hasn't helped that I've more then once got caught up looking at the raw assembly code as I try to understand the actual Hitachi Vehicle OS. But with all that in mind I've been able to put a working flash on my car to clear DTCs and adjust my fan temps. Was nice since I hadn't looked at my work with the ROMs for almost 2months while I practically lived in the garage with the 8 (figured I'd get a lot done while she was apart).

I do know that Colby (the mind behind ECUflash) is working on adding the RX-8 to his list of supported vehicles. I helped him get a head start by giving him all my notes on the PCM's hardware spec for the S1's as well as the code base that Mazda uses for it's ROMs.

ECUflash + the ability to turn off CEL's and force readiness would be pretty important. It would help with inspections for those people who are running speed density based systems that keep the factory PCM on life support. It's a lot cheaper to use a ECUflash and a Tactric cable than to buy a whole AP just for something like that.

Exactly my thought. I haven't figured out how to force readiness but I have it so it doesn't care if certain systems are present or not.

After being burned on the Harrison CanScan I'm reluctant to try him again

In general my experience with every supplier on this subject has been less than positive in various degrees

ya I was worried about being burned with the Harrison but my experience wasn't that bad dealing with them and the product works fine so far. Does what I want at least. I know I could have spent a lil more and gotten an AP but some sick and twisted part of me finds enjoyment out of reverse engineering things. I agree with Team on one thing tho, the product may read and flash but that's really all you get from Harrison, and most others are tight lipped or just don't care to help out with understanding the ROMs.

You most definitely can get the feeling that all the places either feel like your not worth talking to or that you should be seeking their professional services to accomplish the task. Then you have the manufacturers who want all the inner workings to only be accessible by there private techs at dealerships and other corporate facilities leaving the small shops in the dust. The old idea of working on the car at home as a father/son project or just because you enjoy working on cars in general is dying with the new age of automobiles. Some say it's for emissions or safety or this or that but I think it's been shown here (I believe I've seen MM back this up many times) that you can tune and have fun with a car and even build monsters that pass smog and retain safety. Just sucks now cuz you basically need a degree in software engineering just to figure out what's going on in the damn thing. But I digress.

Anyway, if there is interest in the little bit I had done already and what I'm still working on (slowly due to a bunch of training I'm currently in for work but still working on), I'd be more then willing to put up all my data on my website and if others are interested in putting in some time I'll even setup a content management system off my servers so that files and related info can be easily exchanged and all.

Disclaimer: I'm not a master tuner, I've gained an understanding of tuning from prior experience plus lots of reading and I'm better with carbs then with EFI. But I am a software and systems engineer and working with the raw ROM's is right up my alley and I may try to find an algorithm that would allow for a semi-automated discovery of datasets in the ROM's but for now I'm still trying to figure out similarities that exist between revisions of the ROMs and the larger maps are cake when compared to finding things lik fan temps or idle speed and so on.

Well I'd think figuring out the major known maps would be easy with a Cobb unit if you have the ROM capability too. Make changes to a particular map with the Cobb, load it, then check the ROM to see what changed where. :dunno:

That would make things a breeze and I could use that to make a tool that could scan the hex code and attempt to find and label maps based on known values and so on. Issue is I don't know anyone up here with a Cobb for an RX-8. I mean just knowing a few layouts of Cobb supported ROMs could make it quite a bit easier to take an unknown ROM and map it out since you can look for axises and common values in a table since not every value changes. That's how I've been doing it so far but all by hand. I have noticed that it seems certain calibrations have different map sets tho. So that gets a little confusing when you have a calibration with an extra fueling map for a pre-defined set of gears that doesn't exist in another ROM.

Well now, with the knowledge that Cobb is pulling out perhaps this side project got a little more important.

Sent you a PM

I haven't done much more with this project since last I emailed you. I think I just added DTC descriptions. I had considered working on more defs but I am limited to the roms that I have. With one pretty well mapped out, others should be progressively easier, but I too don't have an AP, which would have made things a lightyear faster. Hadn't you been looking into powersteering control? Anyway what sort of progress can you share?

Well I've located most the fuel and timing maps in the U calibration from Mazda but I'm still working on everything else. I tried a couple automated utilities with little to no luck so I've been doing it all by hand using compare functions in a Hex editor as well as the demo version of WinOLS. Slow process since I don't have huge amounts of time to dedicate to it and like I said earlier, through May and June I was tied up swapping out my engine and chasing down a few gremlins in the car (bah I knew I shouldn't have fed them after mid-night) and prior to that I was trying to figure out why she was running crappy lol (I was in denial about my disappearing coolant right up to the moment she spewed it all out on the ground while I was 2hrs from home).

^ Are you using IDA Pro for disassembly?

I wish, no I'm using some free windows and linux utilities including a dis-assembler I found that works with SH-2 binaries.

I wish, no I'm using some free windows and linux utilities including a dis-assembler I found that works with SH-2 binaries.

Have you never heard of BitTorrent?

LOL yea, just didn't find any good torrents on the couple sites I looked at. Then I became distracted as I dug my heals in with the utilities I already had.

Looking forward to seeing some real progress soon ;)

LOL yea, just didn't find any good torrents on the couple sites I looked at. Then I became distracted as I dug my heals in with the utilities I already had.

It's there. I have it. I've looked through some older WRX 16 bit ECU roms with it. I just don't know enough to really figure out what I'm looking at, and don't have a deep enough background in real programming to pick it up easily.

Geesh, my head is spinning after reading all this. Great info though. Now I have to go do some more reading to answer a few questions I have, haha.

I'll tear around the torrents and see what I can dig up.

I have a couple good ideas to make quick work of this, including a de-compile of a certain tuning application written in Win32 using Borland C++ and Visual Studio. I also found I had a few maps mis-labelled in a joint XML def that Vansickey started and I was working to finish that was based off a v1 Mazda ROM tuned by RB.

Depending on the information I find inside the apps associated with a loaned piece of equipment from a friendly forum member the information I could pull together could open up many doors for both flashers and tuners.

As I get some good data to show I'll create a page on my personal blog to openly share it with the community. Link to come...

NOTE: For those who worry about the future and stuff that disappears in the months after a thread goes dormant, I'll reassure you with the knowledge I've operated my site for more then 8 years and don't plan to stop now.

Well I'll take it back, Harrison R&D seems to have pulled their act together with the Apex-OBDScan and RX8 Flasher system. The ability to read the existing PCM program is a nice feature too.

does the system use IAT's during open loop?
OD

If anyone wants to see the AccessTuner instructions, which defines a bunch of maps in the PCM and what they do, I'll put them here: http://www.geocities.com/arghx/Rx-8_AccessTuner.pdf

There is an explanation of cooling fan function and its associated tables on pages 24-25.

Also, I have the SAE J2534 standards "Recommended Practice for Pass-Thru Vehicle Programming" (2002) and the 2006 update, "Optional Pass-Thru Features" in PDF form. PM me about it.

Hey buddy do you still have this pdf? The link does not work. Thanks. :)

Ah, nice to be home after about 2 weeks of travel. Anyway, I'll be digging into making definition files over the coming weeks. I also found the AccessTuner PDFs to be helpful in naming the maps that I have found in both "version1" and "version2" ROMs for the RX-8.

Yeah I have been reading the help files in Access Tuner and they are pretty helpful at identifying different things.