sounds like you're covered but send me an email or pm otherwise

Subscribed for the s2 results...

Ok, so REtali8 swung by this afternoon and we were able to read his ecu. I really will need to sit down and try to define the tables, but in his case, most of the 800 or so tables are id'ed, and some even have the (what appears to be) the correct axies.

I will tell you guys straight up, I'm not a rotary expert, however I do a great deal of experience and time tuning piston engine Mazdas(and well most Otto Cycle engines).So tell me what tables you deem most important( well other than fuel and maf cal) and I will look to see what I can find, as time permits

well looks like i am ordering the tactrix right now lol

Granted, S1 owner here, I now own a tactrix... but no mazdaedit :(

just ordered mine. will order ME as soon as the openecu gets here :D

I ordered my tactrix on a Saturday evening and it was in my possession by the following Tuesday. I seriously hope epifan isn't really waiting for Brettus to open up the personal edition.

Hey guys, just checking in. As Dynotronics stated was able to make it down there. We were able to read the ECU and also did some data logging as well. All in all we spent almost two hours together. I look forward to not only MazdaEdit, but also seeing Dynotronics more.

Awesome. Glad to hear, I wish I could have been there.

sweeeeet

(back to lurking)

To test tthe software he should have made a change and tested it on the car - was that done ?

Some of you may want to speak with Harlan. he is making progress in his ion sensing setup and using the IGN1A coils.
If he can get a true ion sensing system then that could be a milestone?

Nope, simply because I have no idea what tables are what on this particular calibration. As I am sure you have seen in your work with the software, different calibrations can have huge variations on the offsets of the tables. So I wanted to look for the OL/CL thresholds first( as they are by far easiest to locate) and go from there.

It was really just a case of seeing if the sw was willing to handshake and read the ecu, which it did with no issues. Since it understands and communicates with this protocol, writing is the easy part, it's the what to write that gets interesting.

I'm more than happy to share with you our findings, and experience, as I may need your input on the rotary

defining the specific maps is the hard part, once you have them laid out in a workable format then the tuning part is pretty well known for anyone with prior RX8 tuning experience

I will be defining most of the maps as best I can very soon. We pretty much had it all sorted a while back but I lost the info as explained earlier .
I believe it is important to actually change something on the map and load it into the ECU to verify that it does work .
The first time I tried that I ended up putting the car into limp mode and it needed a fix from epifan to get me going again.

Finding and defining the tables is the easy part, we have software that handles that's task on the denso and Mitsubishi ecus. However figuring the logic and the use of each table is a bit tougher.

We have a bit of advantage here, since the logic on the throttle tables, and comanded torque tables looks very similar to the mx5.

I have a race next weekend, so I will be a bit limited till after that to dig thru the rom. I'll keep you updated

I suppose those of us familiar with the preceding RX8 software maps can pick those out more easily

Yes, but I'm gonna bet, based on what I know of the older Cobb sw, that there are way more than you realize.

Brettus, no it wasn't. Also I agree we need to write to ECU to claim success. But, as I stated previously this was not the intent this trip.

Dynotronics will be sending me the ECU read we did. Once we look thru it and decide what to update, then we were going to attempt a write. I look forward to the journey.

Just change the idle, easiest test.

thewird

I've seen them all on the S1, and yes, we don't know what many of them are. That's not necessarily a bad thing. If you can get the S2 to the same level as the S1 Cobb AP many S2 owners would be *extremely* happy

From overhearing some conversations at the DFWMazda group meets regarding the AP, I would agree.

Yes, changing the idle would be an easy test. Provided it is labeled. I know one thing we noticed was (Dynotronics keep me honest here) was the software did not detect a knock sensor. I was comfortable with the plan of doing a read, looking at data, then write.

Any updates? I'm almost tempted to get the Pro version just to find and play with tables the AP doesn't have. But my wife would kill me, then I would be dead.

Is there some sort of guide for people like myself, not familiar with this software?

I've done some logging with it, but how do I download my ecu on to my comp to review?

I come from a world of ford falcon j3 ecu reflashing, different setup.

Per email with Epifan yesterday, personal version of MazdaEdit should be ready for S2 RX-8 sometime this week.