spark 4 degrees less than table

[GintsK]

found that - its set to zero now, but still no change.

It seems to pull more timing during warmup, when the motor is cold. Like 16 degrees, then tapers off. But i can't find any coolant temp related ign settings?

ign retard at acceleration = 14 deg

But there is! 3D table for retard from IAT vs TPS% (or MAP)
VT or MT?

[gunni]

IAT is not Coolant

His IAT is not having effect ,

[GintsK]

Sorry! My fault.

Also new firmwares have possibility to configure retard value at warmup.

[multiplex]

Any idea what variables these might be? It could be warmup related - although i am now officially out of warmup mode by moving down my upper temp bin

my favorite variable so far is blablabla[0] - blablabla[7]   

Sorry! My fault.

Also new firmwares have possibility to configure retard value at warmup.

[gunni]

None of the gauges seem to show that cold coolant is having effect.

Also the coolant adjustment is not an adjustable variable. Which it should of course be.

[GintsK]

Ignition settings -> Other - Ign adjust cold (0deg C)
It is adjustable

[multiplex]

i have that set to zero, but the ign retard clamp isn't

What does ignition_retard_clamp do?  should it be zero?

well anyways here are a few more logs and configs. I've added spark_curve_diff so you can see the change that is in effect

One set of logs is driving around, the other is warmup from cold

www.voytilla.com/vems/warmup.csv
www.voytilla.com/vems/warmup.vemslog
www.voytilla.com/vems/boost_pulls.csv
www.voytilla.com/vems/boost_pulls.vemslog
www.voytilla.com/vems/101309b.vemscfg

[z0tya]

from changelog:
since 1.1.56:* config.ignretard_clamp adjusts maximum ATDC retard
from global.h:
uint8_t ignretard_clamp;     // ignition retard claming.0=clamp at 63.75 (no clamping); 200=clamp at 64-(200/4) ATDC;

and one more interesting from changelog:
since 1.1.52: * cold retard renamed to cold adjust, set 128 to zero adjust

[multiplex]

ok problem is solved! 

it seems to be MAT retard related, even though that didn't show up in the logs, and i was not in any region of the retard table that should have effected anything

regardless, here is what i found

config13 was set to Hex 16 = 10110 in binary

I changed it to 11110 binary to disable MAT retard

thanks everyone for the help

i did learn about a few new cool features in the process. I kinda like the cold ign adv settings.

#define ODDFIRE               0 // 0:normal, 1:odd-fire
#define O2_WB_SENSOR          1 // 0:narrowband, 1:diy-wb
#define CONTROL_STRATEGY      2 // 0:use the MAP or tps map blend for fuel calcs 1:do not use any multipliers
#define BARO_CORRECTION       3 // 0:off, 1:on
#define MAT_RETARD            4 // 0:on, 1:off
#define IGNLAMBDA_TPSKPA   5 // 0: ign, lambda looked up by kpa; 1: ign, lambda looked up by tpskpa, see hybrid_rpm_...
#define CLT_CURVE_17_POINT      6   // 1:use config curve, 0: use flash curve
#define MAT_CURVE_17_POINT      7   // 1:use config curve, 0: use flash curve

[z0tya]

I have seen very interesting thing on warmup log
There are spikes in spark and invert of this in spark diff (i dont know what is it) til 18 C clt.

And after clt goes up the spikes will infrequent.
After 33C CLT the spike inverted and densed til 65C

This is a secret warm up feature?
And in your spark table show about 14 deg, when the spark angle guage show 2 til 85C clt


I dont really understand

So if you switch off mat retart at config, this things disapper?

[MWfire]

idle spark control?

[z0tya]

good idea, but disabled in his config

[gunni]

ok problem is solved! 

it seems to be MAT retard related, even though that didn't show up in the logs, and i was not in any region of the retard table that should have effected anything

regardless, here is what i found

config13 was set to Hex 16 = 10110 in binary

I changed it to 11110 binary to disable MAT retard

thanks everyone for the help

i did learn about a few new cool features in the process. I kinda like the cold ign adv settings.

#define ODDFIRE               0 // 0:normal, 1:odd-fire
#define O2_WB_SENSOR          1 // 0:narrowband, 1:diy-wb
#define CONTROL_STRATEGY      2 // 0:use the MAP or tps map blend for fuel calcs 1:do not use any multipliers
#define BARO_CORRECTION       3 // 0:off, 1:on
#define MAT_RETARD            4 // 0:on, 1:off
#define IGNLAMBDA_TPSKPA   5 // 0: ign, lambda looked up by kpa; 1: ign, lambda looked up by tpskpa, see hybrid_rpm_...
#define CLT_CURVE_17_POINT      6   // 1:use config curve, 0: use flash curve
#define MAT_CURVE_17_POINT      7   // 1:use config curve, 0: use flash curve

It may be that since your config had MAT retard enabled that when you have that, it does both the old retard as well as your MAT retard table. So one you could see not having effect, while the other one was actually happening in the background.

Obviously this old retard should be removed and the retard table always active, and anybody can just put in zeros if they don´t want it to have an effect.

EDIT.

I just ran a test on my ecu I have here.
Where I disabled MAT retard, the table did not work and no changes where.
When the retard was active the table works, but if I took out the numbers no ignition change was there.
Maybe it´s specific to your firmware?

[z0tya]

anyway do you have gauge groups in the new 2009/10/02 0.10.0 Vemstune?

[multiplex]

yeah what is weird is my first entry in my MAT retard table was for 40 degrees C.  I never even came close to that region 

I have yet to figure out gauge groups and even basic gauge setups in vemstune - i need some help there.