Seeing 2-3 degrees difference in timing mp vs log.
Oct 14, 2012, 06:12 PM
#33
I logged my timing map and it is lower than what's on the map. I don't get it. I'm getting 1's and 0's where I have 5's. No knock. I've zeroed out air temp comp tables. I also matched my lo-octane map to my hi-octane map so there isn't any interpolating between the two.
Oct 14, 2012, 07:43 PM
#37
Your issue is weird, as I have had this happen before (timing differences), but have always figure it out, as its always the temp timing trim or wrong load logged.
Oct 14, 2012, 08:03 PM
#38
I already know you did. I was talking to ace, as he has a different ROM and that may very well be his issue (logging wrong load). Its worth a try.
Your issue is weird, as I have had this happen before (timing differences), but have always figure it out, as its always the temp timing trim or wrong load logged.
Your issue is weird, as I have had this happen before (timing differences), but have always figure it out, as its always the temp timing trim or wrong load logged.
Oct 14, 2012, 09:42 PM
#40
I've discovered 2 things
1. My 1 byte load gauge max and chart max is 270 and I'm hitting 280 and 290 now that I pushed my boost up to 27 from 25 psi. So I'll change that to like 300.
2. My Alt Ignition Map is seems a lot closer than my Regular Ignition map. Here's a pic of my tracer and Alt ignition map. I'll try matching my alt map to my regular ignition map and see if that affects it.
1. My 1 byte load gauge max and chart max is 270 and I'm hitting 280 and 290 now that I pushed my boost up to 27 from 25 psi. So I'll change that to like 300.
2. My Alt Ignition Map is seems a lot closer than my Regular Ignition map. Here's a pic of my tracer and Alt ignition map. I'll try matching my alt map to my regular ignition map and see if that affects it.
Oct 14, 2012, 11:43 PM
#41
2byte load
MUT 00 = 895C
MUT 01 = 895D
2byte load + baro compensated = 8960 and 8961
2byte load + baro and IAT compensated = 8962 and 8963
Also, my evoscan is also set to the same chart & gauge max and it doesnt affect anything.
And there ways to check if you were on your alt map.
Oct 16, 2012, 09:01 AM
#43
Here are the address. You have to enter them 2byte load style and log 2byte load to log them.
2byte load
MUT 00 = 895C
MUT 01 = 895D
2byte load + baro compensated = 8960 and 8961
2byte load + baro and IAT compensated = 8962 and 8963
Also, my evoscan is also set to the same chart & gauge max and it doesnt affect anything.
And there ways to check if you were on your alt map.
2byte load
MUT 00 = 895C
MUT 01 = 895D
2byte load + baro compensated = 8960 and 8961
2byte load + baro and IAT compensated = 8962 and 8963
Also, my evoscan is also set to the same chart & gauge max and it doesnt affect anything.
And there ways to check if you were on your alt map.
I discovered that I was 4-5 cells low on the load reading. I almost flashed my rom with putting my desired timing in cells 4-5 cells higher than what my 1byte load was reading. I decided not to.
I logged 2byte load and my 1byte load was off like you (and I) suspected. I'm up in the 330's and 340's and my 1byte load was reading 280's at peak load. I realized I had 1.4 load factor on my rom and 1.2x* on my evoscan Eval. I changed my 1byte load in evoscan to read 1.4. I got the idea from reading your responses on https://www.evolutionm.net/forums/ec...ng-values.html
In that thread you say not to worry about the high load. This goes against what a lot of people say. It seems like a boost leak, which is very possible since I just did a HG job and installed a ix turbo. I also used new boost lines, but it had a slightly larger ID than the ones I replaced. I think it was 4mm and now it's 5mm ID. Anyhow, this did make a small boost leak at the BOV, but I double zip tied it, but I haven't done a boost leak test after the weather got colder here.
Oct 16, 2012, 11:22 AM
#44
Thanks Jay!
I discovered that I was 4-5 cells low on the load reading. I almost flashed my rom with putting my desired timing in cells 4-5 cells higher than what my 1byte load was reading. I decided not to.
I logged 2byte load and my 1byte load was off like you (and I) suspected. I'm up in the 330's and 340's and my 1byte load was reading 280's at peak load. I realized I had 1.4 load factor on my rom and 1.2x* on my evoscan Eval. I changed my 1byte load in evoscan to read 1.4. I got the idea from reading your responses on https://www.evolutionm.net/forums/ec...ng-values.html
In that thread you say not to worry about the high load. This goes against what a lot of people say. It seems like a boost leak, which is very possible since I just did a HG job and installed a ix turbo. I also used new boost lines, but it had a slightly larger ID than the ones I replaced. I think it was 4mm and now it's 5mm ID. Anyhow, this did make a small boost leak at the BOV, but I double zip tied it, but I haven't done a boost leak test after the weather got colder here.
I discovered that I was 4-5 cells low on the load reading. I almost flashed my rom with putting my desired timing in cells 4-5 cells higher than what my 1byte load was reading. I decided not to.
I logged 2byte load and my 1byte load was off like you (and I) suspected. I'm up in the 330's and 340's and my 1byte load was reading 280's at peak load. I realized I had 1.4 load factor on my rom and 1.2x* on my evoscan Eval. I changed my 1byte load in evoscan to read 1.4. I got the idea from reading your responses on https://www.evolutionm.net/forums/ec...ng-values.html
In that thread you say not to worry about the high load. This goes against what a lot of people say. It seems like a boost leak, which is very possible since I just did a HG job and installed a ix turbo. I also used new boost lines, but it had a slightly larger ID than the ones I replaced. I think it was 4mm and now it's 5mm ID. Anyhow, this did make a small boost leak at the BOV, but I double zip tied it, but I haven't done a boost leak test after the weather got colder here.
A boost leak could be making your load higher. But you gotta understand, that things like intake filter and tube mess with the MAF readings and make load higher/lower. Also temps have an affect too. Example, in cold weather, 22psi will make 260 load, but in hot weather you need 25psi to make that same 260 load (on the same car).
But regardless, its always a good idea to do a boost leak test and make sure you are leak free.
Last edited by Boosted Tuning; Oct 16, 2012 at 11:35 AM.
