When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
Weather update: that 24-constant map was not the OMP setting while cold starting... but I found something else that might come in handy someday:
Found out that ignition timing values are represented as 8 bit unsigned integers as follows:
0 = -50 deg
...
99 in decimal means -0,5deg
100 in decimal means 0 deg
101 in decimal means 0,5 deg
...
255 = 77,5 deg
RPM axis(X/columns) and load axis(Y/rows) usually sit as 32bit float values.
Further discoveries... one day gotta tear up that .hex code and find out what the more interesting looking tables do:
Note to whoever may try this with ME in the future... CTRL+H points you to the .hex area where that table is stored.
Once you define your own map besides those predefined, you will see its area with a shade of blue. But if you try to define over an area that is already defined then the cells won't turn blue! That is a sign you're looking at charted areas already - and thus no point pursuing that anymore.
Last edited by ciprianrx8; Nov 6, 2022 at 03:33 PM.
Now if anyone wants to have a look at what I've dug up, here you go: my calibration and XML definitions.
To add them, open up the .xml file, and select whichever map you want. Copy that part, for example:
</map>
<map name="Unknown Load vs RPM #5" type="3" help="Unknown load vs rpm map|" class="Test">
<rows count="18" offset="#75EC0" storagetype="float" func_2val="[x]*100" func_val2="[x]/100" format="%.0f" metric="%" caption="Engine Load"/>
<cols count="19" offset="#75F08" storagetype="float" format="%.0f" metric="RPM" caption="Engine Speed"/>
<data offset="#75F54" storagetype="int16" format="%.0f" caption="???"/>
</map>
Then open the .hex; in the map window go to edit -> add map from XML. On the new window that pops up, paste the above text(or anything else from the .xml file).
You should get something like this:
I've added what I assumed to know to each of those... and still, at this stage I'd say no more than 30% of the ECU is mapped! Of those, we barely know 10% for sure which map does what.
I've had to bother Epifan a bit and he was actually helpful with this latest endeavour of mine. I'll let the pictures speak; what has to be said is that some extra hardware is needed - but there is NO extra connection between the car and the laptop to be made(the tactrix dongle is all that's needed).
Major problem discovered... it seems that the personal version of ME doesn't let you do this. I can't spend any more time on this matter, but it seems that only using the "generic OBD2 can" will ME actually ask custom PIDs. The "MPSCAN" logger seems to be hardcoded to only do a specific range of PIDs, and even if you feed it more, it will show them up but never actually send the requests on CAN to grab those. This is purely a sw limitation of ME, and it even outputs in the console "invalid CMD xxxx" when forcing the MPSCAN logger to do those extra PIDs... real shame .
Perhaps one day someone can churn more time on getting it work, or come up with another logger. ME has been buggy, at best; but I've served my purpose with it.
LOL! You really expect that to yield anything.... He dropped me some hints but far from offering a "how-to". I've had to do some hardcore trial and error...
Some dangerous behaviour I've noticed recently that *might* be related to MazdaEdit.
There are 3 ECUs that I know of atm. ECU 1 runs software partnumber A, ECUs 2 and 3 run software partnumber B.
All ECUs have been reflashed by same original Tactrix cable.
ECU 1 has been reflashed about 100 times or so, then it started popping up a random P0601 DTC. It would pop up under WOT/high load/medium or high rpm.
No fix was found, despite all efforts of flashing other tunes/factory tunes/PCM reset via Forscan etc) and a replacement ECU was sourced.
ECU 2 has been the replacement for ECU 1, and it has been reflashed about 30-40 times so far. No issues so far and plenty of driving was done.
ECU 3 has been reflashed ONCE and during the first drive(literally minutes) after reflash DTC P0601 popped up. Reflashed to another tune, code cleared but the car wasn't driven much since the first occurence.
When DTC P0601 shows up, the gas pedal goes dead, the car idles at 2000rpm(under ECU 1/software partnumber 1) or 1500 RPM (ECU3 with software partnumber B), will not accelerate but will not die either. You could even drive along in 6th gear at 2000RPM with no other limitation whatsoever. Masking the DTC does nothing - lol - great use-case here. After replacing ECU 1 with ECU 2 the car drove perfectly so I'd say for sure there is nothing wrong with the rest of the car.
At this point I believe that once P0601 pops up once there is no running away from it. Replacing ECUs is also a pain if the replacement doesn't have the same SW partnumber on it.
It could be that checksums are not perfectly computed for every single value you can enter in ME or the slightest glitch or electrical poor connection can trigger this. I'm not talking about yanking on cables or jumping around with the laptop, I sit still as dead during writing of tunes.
I could test on ECU 1 to see what happens if CAN wires are cut during reflashing; after all that ECU is now a paperweight.
I also believe that a complete ECU wipe with Mazda IDS(service tool) might clear this issue for good - but I don't know where to grab one.
Any ideas? Is the flash memory that sh***y and can die off anytime ?
I don't see this answered. Eprom is not meant to be rewritten many times. Eprom memory is meant to be programed once, and perhaps re-flashed few times (OEM sw updates). The more it is written to the "shallower" the voltage flip is and less likely that it writes in to the memory and that it sticks.
Dunno what went wrong with it in the end. Eeprom memory is affected by age and temperature too. x5 sooner at 80C vs 25C. But we are still talking about thousands and thousands of reflashes. Doubt I've flashed a thousand times across 30 ecus so far.
My turbo ECU has 521 flashes on it without issue. Before that another ecu had 300ish on it . Also done thousands of reflashes on other ecus without issue.
hi guys, i am late for the party.
i just bought the Mazdaedit and already requested the Flat Shift and Launch control map patch.
however its not working on my rx8. has any one got it to work? what may be i have done wrong that it wont work?
cheers
hi guys, i am late for the party.
i just bought the Mazdaedit and already requested the Flat Shift and Launch control map patch.
however its not working on my rx8. has any one got it to work? what may be i have done wrong that it wont work?
cheers
I haven't tried the Mazdaedit patch but have tried FS and LC in different software. The LC works fine but FS was a waste of time , my shifting without it is better.
My 8 has been down for years as my rebuild wasn't worth a crap and had horrible starts after 10000 miles. I attribute it to the solid corner seals too.
But when I get my next rebuild is anyone of you doing remote tunes for people who already have a Mazda edit ?
Quick question about MazdaEdit : I have a Full bridgeport and my engine builder did flash the ECU with is tune (i don't know the soft he used), so when i sent my dump file to EpifanSoftware, he couldn't send me the .HEX file.
Is there a way to retrieve the data used on my ECU (with the CAN Logger or else) to do like a reverse-engineering ?
thanks
Quick question about MazdaEdit : I have a Full bridgeport and my engine builder did flash the ECU with is tune (i don't know the soft he used), so when i sent my dump file to EpifanSoftware, he couldn't send me the .HEX file.
Is there a way to retrieve the data used on my ECU (with the CAN Logger or else) to do like a reverse-engineering ?
thanks
If it was mazdaedit he used you would be able to flash over top of it if you found a suitable file. Anything else .... Could be a trip to the wrecker for you .... make sure you get the same ecu no.
Unless ...you take it back and get him to flash the stock tune back in. I have done that successfully with Versatuner
Mazda can do an As Built flash which will restore the ECU but you will loose your existing tune.
The different softwares use different "keys" to protect their tunes so if you want the existing stuff so you can reflash it with ME you are out of luck. I mean its possible but not a simple process.
Ah yes , I had forgotten that Mazda can do this .... actually had to do it back in the day with Hymee software. Was a major PIA though as no-one knew wtf they were doing.
Thanks for your answers !
I was afraid i'll have to start a tune from scratch as i'm sure i'll never get the tune from my old builder, but it's even worse, i will not be able to flash with ME over their previous tune ? it will mess the all ECU ?
i have to bring the 8 to Mazda (for the fuel pump, airbag stuff etc.) i'll ask if they can do an As built Flash, may be it's my easiest solution
Grab a tactrix 2.0, search RX8man on github, get his tool and read the tune that's in your ecu. As built stuff HAS NOTHING TO DO WITH HOW YOUR ENGINE RUNS. Actually you can't do anything with as-built file, just turn cruise control on and off.
And let me state that ME changes the ECU access key from MazdA to EpSMZ, so that locks out 99% of people from reading/writing to an ecu that was previously reflashed with ME.
Ah yes , I had forgotten that Mazda can do this .... actually had to do it back in the day with Hymee software. Was a major PIA though as no-one knew wtf they were doing.
I just realised, i got reflashed like 10 years ago with Hymee pro tuner software, and then i don't know what soft they did use when they did my bridgeport, and now i want to add MazdaEdit in the mix...
Can we flash from different soft over the ECU or if we change software we must first get back to a stock tune ?
If it was mazdaedit he used you would be able to flash over top of it if you found a suitable file. Anything else .... Could be a trip to the wrecker for you .... make sure you get the same ecu no.
Unless ...you take it back and get him to flash the stock tune back in. I have done that successfully with Versatuner
Confirm that you could overwrite Versatuner over Mazdaedit.
My car originally had a "mini map" from a reputable tuner, which was running unpredictably in some conditions, and the guy refused to make changes based on his personal opinion.
I used Versatuner to successfully back up the Mazedit file, dump new changes, and also able to make a comparison between my tune and "mini map"
.
as it was still built when there was no deficit in Electro materials.. but wouldnt bet such will be with todays ECU's ....
Could be a trip to the wrecker for you .... make sure you get the same ecu no.
