Timing map don't match log? "Flash"

[rstchris]

So I have noticed a few times now so a made sure the air temp and baro are not pulling a few degrees. My log shows as much as 7* less than my timing map and there is 0 knock. What is stealing my timing? I can't tell exactly where I should be on the map cause my load function don't log properly but it should be pretty freakin high.

 

[donniekak]

I have programmed my ecu to only run one timing map. Best solution i ever found. I also run e85.

 

[Ceddy]

When are you seeing lower timing?

If your Octane Level isn't 100%, the Low Octane maps will be interpolated in.

There is a Timing Knock Down On Light Accel function that can be disabled, if wanted.

The Warm Retard map will pull timing if coolant is cold.

At idle timing is controlled to maintain idle speed, +-10 map value is normal.

 

[rstchris]

I haven't looked at anything but wot. these are pulls done with 195*ect, 85* iat and 0 knock. All the conditions seem right. It makes it hard to tune cause I am commanding 24* up top and seeing 19* and at 3500rpm wot i'm commanding 15-16ish and seeing 9-10* I run E85 so there is no such thing as knock for me @ 11.7afr.

 

[Ceddy]

Log Octane Level, if its not 100% the Low Octane map will start to be used. (The ecu interpolates between the High and Low Octane Timing maps depending on Octane Level.)

You can edit the Octane Update Points, to change how much knock changes Octane, or even effectively disable it by setting "Knock Counts Above, Decreases Octane" to a high number. But it is a good safety feature to have.

 

[rstchris]

Octane is pegged at 100. It should be running only on the high octane map if the conditions are right but it's not. I remember logging v1.4 and seeing it switch when I would get knock it would pull 1-2* then feed it right back but since v1.8 I have not been doing much as my car has had alot of downtime but I remember seeing this before on v1.8 I might try using 1.4 and see what happens cause back then I wasn't seeing this issue.

 

[jeffo]

Have you checked for boost leaks? It could be that the MAS is seeing much more airflow than indicated on your boost gauge, so you are on higher, more retarded timing maps.

 

[rstchris]

It woudn't matter if I did have boost leaks cause I am using the small maps and flowing lots of air putting me in the far right area anyway. I should be flowing in between the last 2 load bins on the stock size maps. Thing is, if I flow more, timing won't decrease as there is not more map with lower timing values past where i'm at and if I am flowing less than i suspect then my timing should be even higher.

 

[rstchris]

This is my low octane map and I am logging even lower than that. My octane rating is pegged at 100. My high oct map is pointless. This is 1.4V, I switched back and still have this issue but now my MIL seems to be wacky. Sometimes I get the test when I turn the key on but goes off and stays on while koer with NO trouble codes. I reset the batt and redid the flash with no fix.

 

[Ceddy]

You should post your rom if you want someone to troubleshoot, can't see all settings from pic.

If Octane = 100, High Octane map will be used.

You are coming down off a Load spike, at 4000 rpms you are in a 10* cell, which matches your logged value. But don't know what your High Octane map looks like.

Newer versions have Fractional Timing Advance, which logs timing to two decimal places.

 

[rstchris]

Oh, sorry. That line is not the notation. The box denotes peak load on the right side of the log, I should have clarified. The bin with 12* is where I should have been but I figured out i'm running on low oct. map 2 as I took the top left corner and made it all 2* and logged with one changed map at a time. I have my settings on map set 1 though. Do you think this could lead back to my clutch swich?

 

[jeffo]

Bit=0 means MAP1
Bit=1 means MAP2
Is that how you have it set?

 

[rstchris]

Yes, I have it set to run on mapset 2 with high oct. lookup. It used to work, I tested out the octane lookup and it don't work anymore either. I will turn off the NLTS and gnd that wire to see if it goes back to normal. As it is now I have tried turning map switching on/off, high oct. on/off and no change.

 

[Ceddy]

If you are running NLTS with a 5 speed.

You should have Map Switching on and locked to set 1 (0 in CeddyMod Bits)



The stock Map Switching is used by Automatic transmissions, as well as switching the main fuel and timing maps, it switches a lot of other things that are not fully understood.

Having it locked to map set 1 will keep it in 5-Speed mode even when the clutch is depressed.

Your timing issues may be linked to using set 2.

In newer versions I have Map Switching labeled as a Debug Only feature, until it is more fully understood what all is effected by it.

 

[rstchris]

I am using a 5spd and have map swiching off. I am still using v1.8 Using map set 2 is not my intention, i'm trying to get it back to 1 but changing settings have no affect so i'm going to try turning off nlts and gnd that wire to see what happens cause that s how it was stock.

 

[rstchris]

Ok, I put my low oct #1 to 2* on the whole idle and just off idle area and kept the low oct #2 normal. I logged idle while pumping the clutch and I am switching between them. It's nice that map switchingis working very well but I have switching turned on and selected mapset #1 yet still switching on me. I tried turning map switching off and no change. The only way to run on #1 maps is to have the P/N pin grounded then turn off NLTS.

 

[Ceddy]

I'll check out the Map Switching code. You can set both map sets equal as a temporary solution.

 

[rstchris]

Thats what I pretty much did but unfortulately when I get stuck on mapset 2 my high oct. lookup doesn't work. For now i'll just disable NLTS and gnd that wire so I can run on my prefered maps.