Let's see your fully tuned timing maps
#2702
Evolving Member
iTrader: (4)
Join Date: Oct 2008
Location: Massachusetts
Posts: 139
Likes: 0
Received 0 Likes
on
0 Posts
I am using 1.4 load factor.
Made sure to align my rom in evoscan using my last log, still showing in the 310 load cells.
Did another couple of pulls with no luck. Tried adding some more timing in the 310/320 load cells, and still peaking at 9 degree's. I'm quite confused at this point.
Made sure to align my rom in evoscan using my last log, still showing in the 310 load cells.
Did another couple of pulls with no luck. Tried adding some more timing in the 310/320 load cells, and still peaking at 9 degree's. I'm quite confused at this point.
Last edited by EvilDSM97; Jun 19, 2017 at 03:38 PM.
#2704
Evolving Member
iTrader: (4)
Join Date: Oct 2008
Location: Massachusetts
Posts: 139
Likes: 0
Received 0 Likes
on
0 Posts
Not using 2 byte RPM, however. I rev to 7300 typically, limit is set at 7500.
Last edited by EvilDSM97; Jun 19, 2017 at 08:03 PM.
#2705
Evolved Member
iTrader: (2)
What if you set the map to 8 degrees, will the log show 8 degrees for that load. I'm curious if the ecu is pulling timing regardless of what you have on the map. Also is your low octane ignition map set to the same values as the high octane map? Is this an evo 8 or 9?
#2708
Evolved Member
If your not getting any knock, then in ECU flash check to make sure the load table is set to reference the Omni 4 bar sensor. I know the tephra 9653 rom labeled Omni 4 bar is configured wrong. You actually have to go in and change the load scale from kalvico 3.5 bar to Omni 4 bar. Can't remember if it was the load table that was wrong or the sd table. Also check your psi table for boost control. There are several places in ECU flash that reference the Omni 4 bar sensor scaling. If your using the ECU for boost control be careful if you change these over to Omni 4 bar as they will change your boost level.
That's assuming your running the Omni 4 bar sensor. I know it's mixed up on that 9653 sd rom that's labeled for the 4 bar.
That's assuming your running the Omni 4 bar sensor. I know it's mixed up on that 9653 sd rom that's labeled for the 4 bar.
Last edited by 2winscroll; Jun 20, 2017 at 08:02 AM.
#2709
Evolving Member
iTrader: (4)
Join Date: Oct 2008
Location: Massachusetts
Posts: 139
Likes: 0
Received 0 Likes
on
0 Posts
I actually think my low octane ignition map is set to 9 degrees in those areas, I have to verify that when I get home when I have my laptop in front of me but I'm fairly certain. Is it possible for the ecu resort to the low map although there is no knock detected in the logs?
#2710
Evolving Member
iTrader: (4)
Join Date: Oct 2008
Location: Massachusetts
Posts: 139
Likes: 0
Received 0 Likes
on
0 Posts
If your not getting any knock, then in ECU flash check to make sure the load table is set to reference the Omni 4 bar sensor. I know the tephra 9653 rom labeled Omni 4 bar is configured wrong. You actually have to go in and change the load scale from kalvico 3.5 bar to Omni 4 bar. Can't remember if it was the load table that was wrong or the sd table. Also check your psi table for boost control. There are several places in ECU flash that reference the Omni 4 bar sensor scaling. If your using the ECU for boost control be careful if you change these over to Omni 4 bar as they will change your boost level.
That's assuming your running the Omni 4 bar sensor. I know it's mixed up on that 9653 sd rom that's labeled for the 4 bar.
That's assuming your running the Omni 4 bar sensor. I know it's mixed up on that 9653 sd rom that's labeled for the 4 bar.
#2711
Evolved Member
I can't remember which rom was wrong it may have been 9417. I was on that rom but I switched to 9653. I had the same problem and that was the issue. You did verify your evoscan definition is correct I assume.
#2714
Evolving Member
iTrader: (4)
Join Date: Oct 2008
Location: Massachusetts
Posts: 139
Likes: 0
Received 0 Likes
on
0 Posts
I'm finally home from work in front of my laptop. Figured I'd screenshot some of my settings. (Also added a shot of low octane timing map for good measure)
Let me know if anything jumps out at anyone that may be wrong. By the way I really do appreciate everyone taking the time to try to help me out with this thus far!
Let me know if anything jumps out at anyone that may be wrong. By the way I really do appreciate everyone taking the time to try to help me out with this thus far!
#2715
Evolved Member
In evoscan post 2702, I see you are using Omni kpa load, ECU load will be different since it is modified by map sensor VE table. For instance when your map sensor reads 350 load, your ECU load will be 370 ECU load. I can't see anything else wrong tho
In the drop down for the load axis you need to choose load 1 byte. That should put you in the 330 column
In the drop down for the load axis you need to choose load 1 byte. That should put you in the 330 column
Last edited by 2winscroll; Jun 20, 2017 at 06:46 PM.