Warmup and Aggressive MIVEC Maps
Evolved Member
Joined: Dec 2008
Posts: 901
Likes: 0
From: CA
^^ I don't have a wideband yet... but Gunzo said that his 91oct ROM map is really safe and still pig-rich (bunch of people have been running his maps for awhile with zero problems)... so I'm not worried about it going lean as my X is fully stock except for the Perrin dropin. Plus I'll be monitoring it 100% with a dedicated laptop and Evoscan running & checking for any knocks.
Last edited by tipoytm; Aug 5, 2009 at 12:03 PM.
Thread Starter
Evolved Member
iTrader: (9)
Joined: Apr 2005
Posts: 3,222
Likes: 8
From: Rochester, NY
Hiboost, I was comparing your MIVEC maps to Gunzo's 91oct ROM hex file MIVEC maps (found in Evoxforums tuning section) and it looks like yours has more modifications compared to his (can't distinguish which one has more aggressive settings). I based this by examing the factory/stock ROM hex file.
Got a couple of followup questions:
1.) How does your your MIVEC maps compare to Gunzo's modified JDM map on a stock EvoX (w/ K&N dropin)? I'm looking for a smoother power band with max oomph in the 2500-4500 RPM range.
2.) If your maps do have the settings I'm looking for, is it safe to copy-paste your MIVEC maps to Gunzo's ROM and run it on my stock X?
-edit- I don't have a WB, but will have a Evoscan for logging once my tactrix cable arrives.
Thanks in advance!
Got a couple of followup questions:
1.) How does your your MIVEC maps compare to Gunzo's modified JDM map on a stock EvoX (w/ K&N dropin)? I'm looking for a smoother power band with max oomph in the 2500-4500 RPM range.
2.) If your maps do have the settings I'm looking for, is it safe to copy-paste your MIVEC maps to Gunzo's ROM and run it on my stock X?
-edit- I don't have a WB, but will have a Evoscan for logging once my tactrix cable arrives.
Thanks in advance!
You can certrainly copy and paste the maps from one rom file to your current one without any issues and it will most definitely make the low rpm's much more responsive. The mid and top end values are very minimal changes as I'm still working out what is actually a positive change at WOT.
Evolved Member
Joined: Dec 2008
Posts: 901
Likes: 0
From: CA
^^ thanks for the response Hiboost! I'll definitely just run Gunzo's 91oct map for awhile and constantly monitor it using my spare netbook & Evoscan. If everything goes well say after a week or two, I'll copy and paste your MIVEC maps to overwrite gunzo's. He did say that his ROM has more boost, advanced timing, & a little bit leaner compared to stock.
So basically, all I was concerned about is if your MIVEC maps might cause a problem with the modifications Gunzo made with regards to timing, boost and fueling.
- edit - I'm so excited for the Tactrix cable to arrive! WOOT!
So basically, all I was concerned about is if your MIVEC maps might cause a problem with the modifications Gunzo made with regards to timing, boost and fueling.
- edit - I'm so excited for the Tactrix cable to arrive! WOOT!
Last edited by tipoytm; Aug 5, 2009 at 12:14 PM.
Evolved Member
Joined: Dec 2008
Posts: 901
Likes: 0
From: CA
^^ I'm not actually "tuning" my X yet... not going to do that without a wideband. I'm just going to use Gunzo's modified 91oct ROM which has modest improvements over the stock ROM and has been tested with a lot of X owners (check out his thread on Evoxforums). Some even have boltons already, but mine is stock so it should be safer. My only concern is if it was safe to use Hiboost's MIVEC maps on Gunzo's modified ROM.
Last edited by tipoytm; Aug 5, 2009 at 12:39 PM.
Evolved Member
Joined: Apr 2009
Posts: 536
Likes: 0
From: US
I have to agree with goofygrin on this. You NEED a wideband even though you think it's a generic map. Specifically, I did use Gunzo's modified 91 octane map and it was running leaner than I would have liked. I don't want to go off topic here - Gunzo made a GREAT map for self-tuners to start from, but I think you still need a wideband to make sure it's ok to run on your specific car.
HiBoost, thanks for posting all that you've found. I'll try this one day when I have some more time to data log.
HiBoost, thanks for posting all that you've found. I'll try this one day when I have some more time to data log.
^^ I'm not actually "tuning" my X yet... not going to do that without a wideband. I'm just going to use Gunzo's modified 91oct ROM which has modest improvements over the stock ROM and has been tested with a lot of X owners (check out his thread on Evoxforums). Some even have boltons already, but mine is stock so it should be safer. My only concern is if it was safe to use Hiboost's MIVEC maps on Gunzo's modified ROM.
I've put gunzo's maps on a couple peoples' cars and I always tell them "get a wideband" because without it you have no idea what's going on with the car.
Wideband >>>>>>>>> boost gauge in terms of importance.
Evolved Member
Joined: Dec 2008
Posts: 901
Likes: 0
From: CA
I have to agree with goofygrin on this. You NEED a wideband even though you think it's a generic map. Specifically, I did use Gunzo's modified 91 octane map and it was running leaner than I would have liked. I don't want to go off topic here - Gunzo made a GREAT map for self-tuners to start from, but I think you still need a wideband to make sure it's ok to run on your specific car.
HiBoost, thanks for posting all that you've found. I'll try this one day when I have some more time to data log.
HiBoost, thanks for posting all that you've found. I'll try this one day when I have some more time to data log.
Evolved Member
Joined: Dec 2008
Posts: 901
Likes: 0
From: CA
Actually you are tuning your car because you're changing the stock map.
I've put gunzo's maps on a couple peoples' cars and I always tell them "get a wideband" because without it you have no idea what's going on with the car.
Wideband >>>>>>>>> boost gauge in terms of importance.
I've put gunzo's maps on a couple peoples' cars and I always tell them "get a wideband" because without it you have no idea what's going on with the car.
Wideband >>>>>>>>> boost gauge in terms of importance.
I guess I'm not going to change the MIVEC maps on Gunzo's ROM till I get a WB :-) TY for your input
Last edited by tipoytm; Aug 5, 2009 at 02:48 PM.
Evolved Member
Joined: Apr 2009
Posts: 536
Likes: 0
From: US
Thanks for your input... when you say that it is running a little too lean, is that based on an X that has an aftermarket intake (like AEM) or would this also hold true on a stock X w/ just a foam filter? I am not going to modify the fueling/timing/mivec maps at all. I'm just a little confused since Gunzo claimed that his maps are still pig rich.
I'm in the process of converting these files into the Cobb AP, however there are four tables for Cam Timing. So do I need to copy them on the table A only on both the intake/exhaust only? or does it need to be copy on Table A & B on both int/exh??
Here's what the table description looks like on ATR:
Intake Cam Timing Table A WOT
Intake Cam Timing Table B
Exhaust Cam Timing Table A
Exhaust Cam Timing Table B
Thanks in advance!
Here's what the table description looks like on ATR:
Intake Cam Timing Table A WOT
Intake Cam Timing Table B
Exhaust Cam Timing Table A
Exhaust Cam Timing Table B
Thanks in advance!
Last edited by LVSBB6; Aug 7, 2009 at 08:14 AM.
Thread Starter
Evolved Member
iTrader: (9)
Joined: Apr 2005
Posts: 3,222
Likes: 8
From: Rochester, NY
I'm in the process of converting these files into the Cobb AP, however there are four tables for Cam Timing. So do I need to copy them on the table A only on both the intake/exhaust only? or does it need to be copy on Table A & B on both int/exh??
Here's what the table description looks like on ATR:
Intake Cam Timing Table A WOT
Intake Cam Timing Table B
Exhaust Cam Timing Table A
Exhaust Cam Timing Table B
Thanks in advance!
Here's what the table description looks like on ATR:
Intake Cam Timing Table A WOT
Intake Cam Timing Table B
Exhaust Cam Timing Table A
Exhaust Cam Timing Table B
Thanks in advance!
Table B should be = #1 warmup maps in EcuFlash, these are somewhat optional.
You can verify that the Table A maps are the full temp maps by checking if intake advance and exhaust retard have higher numbers and at higher RPM's than the Table B maps. I think they also reverse the X and Y axis on some of those devices so it may take a bit of time transferring the data.
I just finished converting the #2 Full Temp map to my Table As and took the car out for a quick rip, and WOW what a difference! Boost comes on earlier and partial throttle gain is very noticeable! I used the same throttle input on a familiar turn and scared myself, combined with the Blitz TC the car is so much more preppier now. Good job Hiboost! 
Coupe questions for you:
I datalogged a few runs and saw Knock Retard values of 2s in 3000rpm and 1s in around 6000rpm, are these a concern?
You mentioned Table B (warmup maps) is optional, what do you mean by that?
I will be taking my car to the dyno tomorrow, will do some testing on these MIVEC maps compared to the ones that came with the Cobb Stage 2.
Coupe questions for you:
I datalogged a few runs and saw Knock Retard values of 2s in 3000rpm and 1s in around 6000rpm, are these a concern?
You mentioned Table B (warmup maps) is optional, what do you mean by that?
I will be taking my car to the dyno tomorrow, will do some testing on these MIVEC maps compared to the ones that came with the Cobb Stage 2.
Looks like Intake & Exhaust Table A maps = #2 full temp maps in EcuFlash.
Table B should be = #1 warmup maps in EcuFlash, these are somewhat optional.
You can verify that the Table A maps are the full temp maps by checking if intake advance and exhaust retard have higher numbers and at higher RPM's than the Table B maps. I think they also reverse the X and Y axis on some of those devices so it may take a bit of time transferring the data.
Table B should be = #1 warmup maps in EcuFlash, these are somewhat optional.
You can verify that the Table A maps are the full temp maps by checking if intake advance and exhaust retard have higher numbers and at higher RPM's than the Table B maps. I think they also reverse the X and Y axis on some of those devices so it may take a bit of time transferring the data.