Torque seems low and late
Sep 12, 2010, 10:01 AM
#47
Evolving Member
Thread Starter
iTrader: (14)
Join Date: Dec 2009
Location: New York
Posts: 362
Likes: 0
Received 0 Likes
on
0 Posts
Also make sure your BOV isn't leaking at peak boost too. I generally stick around 11.5AFR with water/meth injection but everyone has different preferences with it. This is how you capture a snapshot of your timing chart:
http://www.youtube.com/watch?v=8wRKj...eature=related
With your air intake temps being so high there, your ECU is retarding the ignition timing which is why you see a different value than you have in the timing map.
First, log your Air Temps during a pull while doing your tuning session so we can see which section your air temps fall into on the table below.
Next, we need to edit the table to accommodate the air temp range you are currently tuning with. Lets say your air temps are 100*F on average, this would land you closest to the 93*F cell in the table which currently reads -1* of timing retard.
What we are going to do is 'SHIFT' the timing curve in this map so its still useful without having to zero all of the values out to make it useless.
Now, edit the values in the table so the cells with the zero is 93* and have it add timing slowly as the temps get cooler and lower timing as the air temps get warmer. Now this feature is still fully functional and adjusted for the Air Temp range that you are tuning with! Now, sometimes if I am tuning on a really hot day, I will actually have it ADD 1* of timing in the 68* cell since the engine is less knock prone under these conditions. The next time you run into an issue with an extreme temperature change, try adjusting these settings before retuning the entire timing map!
http://www.youtube.com/watch?v=8wRKj...eature=related
With your air intake temps being so high there, your ECU is retarding the ignition timing which is why you see a different value than you have in the timing map.
First, log your Air Temps during a pull while doing your tuning session so we can see which section your air temps fall into on the table below.
Next, we need to edit the table to accommodate the air temp range you are currently tuning with. Lets say your air temps are 100*F on average, this would land you closest to the 93*F cell in the table which currently reads -1* of timing retard.
What we are going to do is 'SHIFT' the timing curve in this map so its still useful without having to zero all of the values out to make it useless.
Now, edit the values in the table so the cells with the zero is 93* and have it add timing slowly as the temps get cooler and lower timing as the air temps get warmer. Now this feature is still fully functional and adjusted for the Air Temp range that you are tuning with! Now, sometimes if I am tuning on a really hot day, I will actually have it ADD 1* of timing in the 68* cell since the engine is less knock prone under these conditions. The next time you run into an issue with an extreme temperature change, try adjusting these settings before retuning the entire timing map!
Im not seeing that table in my ROM. My ROM ID is 98640014 .I have a JDM Evo7 and I know your market for Evos started from the 03 Evo 8 so I know my ROM might not been "developed" like the new ROMs. Attached is a night time log (1st) and a daytime log (2nd) and a Timing map
Sep 12, 2010, 11:09 AM
#48
Evolved Member
iTrader: (51)
Join Date: Feb 2010
Location: San Antonio
Posts: 1,640
Likes: 0
Received 0 Likes
on
0 Posts
Your logging too many things, and log 2byte load or 1byte not loadcalc(in accurate)...
During spool you go from 9* to 4* then to 3*... Smooth that out and get rid of that knock that is pulling timing...
Do another log with just the neccesities logged...
During spool you go from 9* to 4* then to 3*... Smooth that out and get rid of that knock that is pulling timing...
Do another log with just the neccesities logged...
Sep 12, 2010, 11:10 AM
#49
Evolved Member
iTrader: (51)
Join Date: Feb 2010
Location: San Antonio
Posts: 1,640
Likes: 0
Received 0 Likes
on
0 Posts
Your logging too many things, and log 2byte load or 1byte not loadcalc(in accurate)...
During spool you go from 9* to 4* then to 3*... Smooth that out and get rid of that knock that is pulling timing...
Do another log with just the neccesities logged...
During spool you go from 9* to 4* then to 3*... Smooth that out and get rid of that knock that is pulling timing...
Do another log with just the neccesities logged...
Sep 12, 2010, 11:24 AM
#50
Evolving Member
Thread Starter
iTrader: (14)
Join Date: Dec 2009
Location: New York
Posts: 362
Likes: 0
Received 0 Likes
on
0 Posts
Bare with me sir. I am very new to this software and still very ignoranant to many things
. Im am not seeing 2byte load in my evoscan software just Load1Byte and Load MUT 2byte Mod.
Sep 12, 2010, 04:50 PM
#53
Evolved Member
iTrader: (51)
Join Date: Feb 2010
Location: San Antonio
Posts: 1,640
Likes: 0
Received 0 Likes
on
0 Posts
Lol, yes sensai... Sent you a PM yoda!!!
Evopower- Mut2byte is what you want... Just don't use LoadCalc, its really inaccurate.
I would tell you to send me your rom, but I don't have my laptop with me... I might get it sent to me, idk yet
Evopower- Mut2byte is what you want... Just don't use LoadCalc, its really inaccurate.
I would tell you to send me your rom, but I don't have my laptop with me... I might get it sent to me, idk yet
.
Sep 12, 2010, 08:15 PM
#55
I posted this in another thread for someone who was also having problems setting up 2 byte load. I just did a quick copy-paste because I need to go to bed, so if anything isn't clear, send me a pm and I'll help you out.
You need to setup your mut addresses to be able to log 2byte load. You'll need to find what addresses you need to enter into the MUT00 and MUT01 tables depending on what ROM version you have in this thread :
https://www.evolutionm.net/forums/ec...te-thread.html
Then enter the corresponding values into your own map, and flash it to your car. For example, my rom version is 88590015. My MUT00 value is 6B42 (entered as 0x6B42 in Ecuflash) and my MUT01 value is 6B43 (again, entered as 0x6B43 in Ecuflash).
After that make sure that in Evoscan your 2byteload is looking at requestid 00 and requestid 01, which correspond to MUT00 and MUT01.
https://www.evolutionm.net/forums/ec...te-thread.html
Then enter the corresponding values into your own map, and flash it to your car. For example, my rom version is 88590015. My MUT00 value is 6B42 (entered as 0x6B42 in Ecuflash) and my MUT01 value is 6B43 (again, entered as 0x6B43 in Ecuflash).
After that make sure that in Evoscan your 2byteload is looking at requestid 00 and requestid 01, which correspond to MUT00 and MUT01.
Sep 12, 2010, 09:30 PM
#57
Evolving Member
Thread Starter
iTrader: (14)
Join Date: Dec 2009
Location: New York
Posts: 362
Likes: 0
Received 0 Likes
on
0 Posts
Found IT on PAGE 2 of the thread 
MUT00 =885C
MUT01 =885D
So I placed the info in the ROM Mut tables and flashed it to the car. Car now reads 2Byteload
.
MUT00 =885C
MUT01 =885D
So I placed the info in the ROM Mut tables and flashed it to the car. Car now reads 2Byteload
.
Last edited by EvoPower81; Sep 12, 2010 at 09:35 PM.
Sep 13, 2010, 04:15 AM
#58
Evolving Member
Thread Starter
iTrader: (14)
Join Date: Dec 2009
Location: New York
Posts: 362
Likes: 0
Received 0 Likes
on
0 Posts
Here is my latest datalog. I have the timing bumped to 7* and richen the afrs to 11.5 range which JOT reccommend . Torque went up some more. getting some knock counts between 5200-7000. Might need to pull 1 or 2* in that area since the AFRs dont look lean. What do you think?
. Torque went up some more. getting some knock counts between 5200-7000. Might need to pull 1 or 2* in that area since the AFRs dont look lean. What do you think?
I figured mine should b similar ?