nicolassabra

hey

This is is my timing map and my logs.

As u can see the ecu is pulling timing all over the rpm and there is no knock

ANY suggestions.

THANKS

Raptord

iTrader: (10)

What does your timing vs IAT table look like?

nicolassabra

[QUOTE=Raptord;11077510]What does your timing vs IAT table look like?
do you mean this one?

Raptord

iTrader: (10)

I'm talking about the timing trim vs IAT table in ecuflash

PureDrivePerformance

What's your Load 1byte factor on your rom and evoscan?

nicolassabra

i hope ur talking about these tables , and excuse me but i am still learning .

nicolassabra

my rom load factor is 1.4
my evoscan factor is 1.2

Raptord

iTrader: (10)

Your ignition trim table could be pulling one or 2 degrees depending on IAT.

They have to be the same. Set the evoscan one to 1.4.

PureDrivePerformance

This is the problem. Evoscan is calculating/logging a lower load than your ECU is reading during your pull. When you look at the log the timing at a particular RPM and Load don't match the timing on your map.

Like Raptord said you need to have them both the same. I'd put 1.4 in Evoscan. Do that and I'm sure it will line up.

nicolassabra

Thanks for ur reply i really appreciated ,but am confused now because yesterday i read a thread posted by tephra on how to calculate load factor and the formula is:you divide your max load value in ecuflash by 255 and that's what i did .
350/255=1.4.
But today i found a small table in Miscellaneous Tephra Mods under the name of 2byte to 1byte Load Factor showing that the load factor in ecuflash is set to 1.2
So should i rely on this table?

PureDrivePerformance

I'm not sure I'm following. That is the table to change based on your calculations you mentioned above. You said that your rom was set to 1.4 for the 1byte load factor. Are saying that it changed back to 1.2?

1.2 setting is stock and all the roms come that way until you modify it to whatever load factor you want. You just have to make sure it's the same in EvoScan.

nicolassabra

Its the same in both evoscan and ecuflash .I think my problem is not here, its in the ignition trim vs air temperature table , tomorrow ill zero up the units from 93 to 122
Fahrenheit and take a run to see if anything will change.

Raptord

iTrader: (10)

What did you mean by this then?

nicolassabra

Am talking about the 1byte factor , its the same in my rom and evoscan . so the problem isn't here , its in the ignition trim vs IAT table as u said in your first post.

merlin.oz

Keep in mind that TephraMod 1-byte load will read higher than the load that is used in the spark map, which is baro compensated load plus modifiers like air temp subtraction.

If your 1-byte factor is 1.2 your measured load will top out at 306, this is why you would change it to read higher, but the 1-byte value in EvoScan has to match whats in your rom.