Series II ECU Tuning
06-12-2013, 01:41 PM
#751
They bricked a test bench ECU. That is the only reason why I trust the guys over at VT because they let me know about their QTP process and how they have a bunch of tests to make sure that the software can recover from a bad flash (this is similar to what the AP has to help restore a bricked ECU). One of their many tests caused the ECU to brick. Wish I had an update though.
Let me know if they need more ECU's. I have two 09 r3 ecus for sale.
06-12-2013, 04:01 PM
#753
Registered
Join Date: May 2013
Posts: 22
Likes: 0
Received 0 Likes
on
0 Posts
06-12-2013, 08:40 PM
#755
Registered
Join Date: May 2013
Posts: 22
Likes: 0
Received 0 Likes
on
0 Posts
06-12-2013, 10:17 PM
#756
Mazdaedit... not if when... JK. 
im not sure how long i will have the ECU's on hand. I was really excited for the S2 platform and just got a sour taste in my mouth. I am still here and willing to help out anyway i can. Let me know if any of you need a hand.
Also Pimon. I have a full hard copy of the FSM and wiring diagram if you would like to buy it.
im not sure how long i will have the ECU's on hand. I was really excited for the S2 platform and just got a sour taste in my mouth. I am still here and willing to help out anyway i can. Let me know if any of you need a hand.Also Pimon. I have a full hard copy of the FSM and wiring diagram if you would like to buy it.
06-13-2013, 11:13 AM
#758
Haha, well I'm now eagerly waiting for an email from epifan to give me the chance to brick my ECU. Small tip: unplug your laptop from any docking station before getting the hardware id to send to Epifan.
BTW, are there any s2 owners on here using Mazdaedit yet, or am I the first to actually try this on my own car?
BTW, are there any s2 owners on here using Mazdaedit yet, or am I the first to actually try this on my own car?
06-16-2013, 12:17 PM
#759
Registered
Join Date: May 2013
Posts: 22
Likes: 0
Received 0 Likes
on
0 Posts
Haha, well I'm now eagerly waiting for an email from epifan to give me the chance to brick my ECU. Small tip: unplug your laptop from any docking station before getting the hardware id to send to Epifan.
BTW, are there any s2 owners on here using Mazdaedit yet, or am I the first to actually try this on my own car?
BTW, are there any s2 owners on here using Mazdaedit yet, or am I the first to actually try this on my own car?
06-16-2013, 01:18 PM
#760
weeeeeeeeee
iTrader: (12)
I went in and adjusted my S1 omp load table last night and the ROM write died about 60% through.
The rom uploader software hung too.
I ended up shutting MEP completely down, turned off my ignition, and disconnected the OP.
Opened MEP and went directly to the flash utility and loaded the map from there -- I've noticed it is really buggy if you try to flash a map directly from the map editor.
Turned ignition on, plugged the OP back in, and restarted flash.
A couple minutes later I was back in business.
Was NOT fun.
06-16-2013, 01:47 PM
#761
Registered
Join Date: May 2013
Posts: 22
Likes: 0
Received 0 Likes
on
0 Posts
"There is another..."
I went in and adjusted my S1 omp load table last night and the ROM write died about 60% through.
The rom uploader software hung too.
I ended up shutting MEP completely down, turned off my ignition, and disconnected the OP.
Opened MEP and went directly to the flash utility and loaded the map from there -- I've noticed it is really buggy if you try to flash a map directly from the map editor.
Turned ignition on, plugged the OP back in, and restarted flash.
A couple minutes later I was back in business.
Was NOT fun.
I went in and adjusted my S1 omp load table last night and the ROM write died about 60% through.
The rom uploader software hung too.
I ended up shutting MEP completely down, turned off my ignition, and disconnected the OP.
Opened MEP and went directly to the flash utility and loaded the map from there -- I've noticed it is really buggy if you try to flash a map directly from the map editor.
Turned ignition on, plugged the OP back in, and restarted flash.
A couple minutes later I was back in business.
Was NOT fun.
06-16-2013, 02:48 PM
#762
06-16-2013, 03:16 PM
#763
And I've flashed probably 10 different 8s several times plus my own one 40 times .
Good to know you were able to force a flash into it after that happened . Was thinking of doing that with my spare ECU just to see what happened.
06-16-2013, 11:31 PM
#764
Well I finally have it properly registered and have a map I can edit :-) Will see what I can do with it tomorrow. Right now my head is spinning just looking at all the tables. The first thing I was going to try was editing the throttle map. I think I have the right table, it is labelled "throttle duty", the only problem is that there are 12 of them! I guess 3 to cover the different gears ( <no number>, #2, #3), and then 4 of each of those to cover ??? (A, B, C, D)
What are the chances I edit one, and it changes something completely different?
What are the chances I edit one, and it changes something completely different?
06-16-2013, 11:47 PM
#765
Well I finally have it properly registered and have a map I can edit :-) Will see what I can do with it tomorrow. Right now my head is spinning just looking at all the tables. The first thing I was going to try was editing the throttle map. I think I have the right table, it is labelled "throttle duty", the only problem is that there are 12 of them! I guess 3 to cover the different gears ( <no number>, #2, #3), and then 4 of each of those to cover ??? (A, B, C, D)
What are the chances I edit one, and it changes something completely different?
What are the chances I edit one, and it changes something completely different?
Start simple with fan on temps / idle speed etc
06-17-2013, 01:46 PM
#766
no idea why so many maps - suspect one set actually does the business and the other two do nothing . The throttle maps actually take quite a bit of sussing out to get the results you want . Dunno if that is such a good place to start.
Start simple with fan on temps / idle speed etc
Start simple with fan on temps / idle speed etc
Fan temps do look to be fairly simple, but I'm not sure why I would want to change any of them.
There are 7 graphs for idle speed labelled A-G
I recorded a log on the way to work and in ~14 minutes I have 367 samples. That's a sample rate of ~0.4Hz, or less than once every 2 seconds. Not quick enough to monitor things in real time.
Last edited by blu3dragon; 06-17-2013 at 02:18 PM.
06-17-2013, 02:36 PM
#767
I can only speak for the Cobb which has 5 idle tables for the 05 MT series
IIRC
A = Idle clutch out no A/C
B = Idle clutch in no A/C
C = Idle clutch out with A/C on
D= Idle with clutch in A/C on
E = ?
If you were to say want to raise the idle by 50 rpm, in the Cobb I would raise all cells in each table by that amount. ex. Scale the entire table.
IIRC
A = Idle clutch out no A/C
B = Idle clutch in no A/C
C = Idle clutch out with A/C on
D= Idle with clutch in A/C on
E = ?
If you were to say want to raise the idle by 50 rpm, in the Cobb I would raise all cells in each table by that amount. ex. Scale the entire table.
06-17-2013, 02:54 PM
#768
weeeeeeeeee
iTrader: (12)
Isn't E the one that has 500 across all cells? Never figured out what it was for. In MEP, I bumped the "warm" idle up to 950 on all but the one table that had 500 across it. Not sure what that one is for.
Looks like you'll have far better luck just logging directly from a BT OBD2 dongle and something like Torque.
Looks like you'll have far better luck just logging directly from a BT OBD2 dongle and something like Torque.
06-17-2013, 03:18 PM
#769
Thanks, I was thinking I could start with something simple like setting the max throttle opening to 85%, seeing if that had the expected effect and iterating from there... I'm hoping I don't need to use the desired engine torque table to do this?
Fan temps do look to be fairly simple, but I'm not sure why I would want to change any of them.
There are 7 graphs for idle speed labelled A-G
I recorded a log on the way to work and in ~14 minutes I have 367 samples. That's a sample rate of ~0.4Hz, or less than once every 2 seconds. Not quick enough to monitor things in real time.
Fan temps do look to be fairly simple, but I'm not sure why I would want to change any of them.
There are 7 graphs for idle speed labelled A-G
I recorded a log on the way to work and in ~14 minutes I have 367 samples. That's a sample rate of ~0.4Hz, or less than once every 2 seconds. Not quick enough to monitor things in real time.
*Fan temp settings are a common mod. for S1 what are yours set to ?
*Idle - just change the last number on each to say 900 (found to be the smoothest idle speed ) Except for that table that is a flat 500 - don't know what that one is .
*Just checked my sampling rate - it's 11 samples per second . There is an adjustment for that under 'capture options' then 'capture rate ' . 12 options available.
Last edited by Brettus; 06-17-2013 at 03:22 PM.
06-17-2013, 03:42 PM
#770
I can only speak for the Cobb which has 5 idle tables for the 05 MT series
IIRC
A = Idle clutch out no A/C
B = Idle clutch in no A/C
C = Idle clutch out with A/C on
D= Idle with clutch in A/C on
E = ?
If you were to say want to raise the idle by 50 rpm, in the Cobb I would raise all cells in each table by that amount. ex. Scale the entire table.
IIRC
A = Idle clutch out no A/C
B = Idle clutch in no A/C
C = Idle clutch out with A/C on
D= Idle with clutch in A/C on
E = ?
If you were to say want to raise the idle by 50 rpm, in the Cobb I would raise all cells in each table by that amount. ex. Scale the entire table.
Yes, I also have a flat 500 rpm in table E. Not sure what that means. Maybe it is the point at which the ecu decides the engine has stalled?
06-17-2013, 05:25 PM
#771
Haha, well I just tried my first flash, and got a write error 
Tried to upload the stock rom, no go. Tried to start the car, no go....
After some contemplation I managed to find the right combination to make it work:
1. Make sure the ignition is off
2. Unplug the openport from the usb port and make sure mazdaEdit is not running.
3. Plug the openport into the obd port. (no need to unplug, replug if it is already plugged in)
4. Turn ignition on
5. Plug in the openport to the usb port
6. Start mazdaEdit, start the flash utility (F11)
7. Hit the read information about ECU icon (F3)
8. Open the ECU rom image using the file open icon
9. Hit the write icon (F9)
10. Don't move or touch anything while it uploads the data.
With my part-written flash, step 7 was not able to read any information from the ecu, but I was still able to write the data successfully.
I'm sure there are other combinations that work, but there are also some that don't!
Tried to upload the stock rom, no go. Tried to start the car, no go....
After some contemplation I managed to find the right combination to make it work:
1. Make sure the ignition is off
2. Unplug the openport from the usb port and make sure mazdaEdit is not running.
3. Plug the openport into the obd port. (no need to unplug, replug if it is already plugged in)
4. Turn ignition on
5. Plug in the openport to the usb port
6. Start mazdaEdit, start the flash utility (F11)
7. Hit the read information about ECU icon (F3)
8. Open the ECU rom image using the file open icon
9. Hit the write icon (F9)
10. Don't move or touch anything while it uploads the data.
With my part-written flash, step 7 was not able to read any information from the ecu, but I was still able to write the data successfully.
I'm sure there are other combinations that work, but there are also some that don't!
06-17-2013, 05:33 PM
#773
Haha, well I just tried my first flash, and got a write error
Tried to upload the stock rom, no go. Tried to start the car, no go....
After some contemplation I managed to find the right combination to make it work:
1. Make sure the ignition is off
2. Unplug the openport from the usb port and make sure mazdaEdit is not running.
3. Plug the openport into the obd port. (no need to unplug, replug if it is already plugged in)
4. Turn ignition on
5. Plug in the openport to the usb port
6. Start mazdaEdit, start the flash utility (F11)
7. Hit the read information about ECU icon (F3)
8. Open the ECU rom image using the file open icon
9. Hit the write icon (F9)
10. Don't move or touch anything while it uploads the data.
With my part-written flash, step 7 was not able to read any information from the ecu, but I was still able to write the data successfully.
I'm sure there are other combinations that work, but there are also some that don't!
Tried to upload the stock rom, no go. Tried to start the car, no go....
After some contemplation I managed to find the right combination to make it work:
1. Make sure the ignition is off
2. Unplug the openport from the usb port and make sure mazdaEdit is not running.
3. Plug the openport into the obd port. (no need to unplug, replug if it is already plugged in)
4. Turn ignition on
5. Plug in the openport to the usb port
6. Start mazdaEdit, start the flash utility (F11)
7. Hit the read information about ECU icon (F3)
8. Open the ECU rom image using the file open icon
9. Hit the write icon (F9)
10. Don't move or touch anything while it uploads the data.
With my part-written flash, step 7 was not able to read any information from the ecu, but I was still able to write the data successfully.
I'm sure there are other combinations that work, but there are also some that don't!
06-17-2013, 05:33 PM
#774
After all that fun, I have now made successfully made some small changes on my s2 and I also figured out the issue with logging sample rates (selecting certain fields that did not return any values dropped the achievable sample rate significantly)
(selecting certain fields that did not return any values dropped the achievable sample rate significantly)
Last edited by blu3dragon; 06-17-2013 at 05:37 PM.
