1.1.43 alpha2 test result

[MWfire]

Loock lambda.It's 0.9x, but on lcd is 1.9x.It's a bit scary to see lambda 1.8 on wot:).
http://uk.youtube.com/watch?v=_N4FbCQTmE0

[GintsK]

This is a bug! 1.95 is 0.95.
I notice something similar!

[Sambas]

I can't reproduce this lcd 1.xx lambda problem. Tested many setups, including MWfire's msq. Could it be some mystery interference problem? How long is your lcd cable? Is it shielded and shield connected to case from Ecu end of connector?

Slow lcd is explained by new task handling. Lcd is low priority task which is over ruled by higher priority tasks ( engine management ).

[MWfire]

I can't reproduce this lcd 1.xx lambda problem. Tested many setups, including MWfire's msq. Could it be some mystery interference problem? How long is your lcd cable? Is it shielded and shield connected to case from Ecu end of connector?

Slow lcd is explained by new task handling. Lcd is low priority task which is over ruled by higher priority tasks ( engine management ).

Cable is 2m utp(unshilded). I don't thing it's interference problem, becouse on LPG(low ohm injectors) i drive whit pwm and i don't have this problem(firmware 1.0.73). This film is made on petrol(high ohm injectors).

[gunni]

Does the boost switch work in this firmware?

When Boost alternate settings enabled..
IÃ,´ve got this on a bench and making air temp colder makes boost target higher....
I canÃ,´t find anything that suggest a connection between the two?

This is closed loop setup
Analog input works to lower maximum allowed DutyCycle as expected.
TPS voltage also changes duty cycle by using the Boost vs. TPS scaling as expected.

Open loop boost, open loop DC adjustment channel enabled
If the DC is 10% in the map, maximum possible is 20% duty cycle and minimum is 0%
If map is 20% , max is 40% duty and minimum 9% duty
if map is 30% then max is 60% duty and min 14%.
and so on, everything above 50% in the map allows for 100% max via the switch,

if DC adjustment channel disabled, then DC is same as the DC map.

If Alternate settings disabled.
DC changes to chase the boost target.
but air temp also contributes to the boost target.
But lowers the boost target, that is if target is MAP-target.
If "boost target" then DC is always 0%
Why is MAT making such a mess of things?
If MAT goes above 30C then boost target is lower then 100kpa

[MWfire]

Does the boost switch work in this firmware?

When Boost alternate settings enabled..
IÃ,´ve got this on a bench and making air temp colder makes boost target higher....
I canÃ,´t find anything that suggest a connection between the two?

This is closed loop setup
Analog input works to lower maximum allowed DutyCycle as expected.
TPS voltage also changes duty cycle by using the Boost vs. TPS scaling as expected.

Open loop boost, open loop DC adjustment channel enabled
If the DC is 10% in the map, maximum possible is 20% duty cycle and minimum is 0%
If map is 20% , max is 40% duty and minimum 9% duty
if map is 30% then max is 60% duty and min 14%.
and so on, everything above 50% in the map allows for 100% max via the switch,

if DC adjustment channel disabled, then DC is same as the DC map.

If Alternate settings disabled.
DC changes to chase the boost target.
but air temp also contributes to the boost target.
But lowers the boost target, that is if target is MAP-target.
If "boost target" then DC is always 0%
Why is MAT making such a mess of things?
If MAT goes above 30C then boost target is lower then 100kpa

Maybe this?
uint8_t boost_matdec; // boost decrease -4kPa/C above this MAT [ F-40 ]

[gunni]

Thanks but why isnÃ,´t that in the Megatune software then?

ItÃ,´s a pretty clever control mechanism, I spot EGT boost retard as well.

[Sambas]

Those are placed in shiftcut page as they don't fit on main boostcontrol page. I'll put them to boost alternate page.

[gunni]

IÃ,´m upgrading to 1.1.44 anyway
so no need to upgrade 1.1.43 as .44 is logical upgrade from other fwÃ,´s

[PeepPaadam]

IÃ,´m upgrading to 1.1.44 anyway
so no need to upgrade 1.1.43 as .44 is logical upgrade from other fwÃ,´s

But Experimental features have disappeared on 1.1.44? I'd like to test some of them (like wheel speed input) but didn't find them on 1.1.44.

[MWfire]

IÃ,´m upgrading to 1.1.44 anyway
so no need to upgrade 1.1.43 as .44 is logical upgrade from other fwÃ,´s

But Experimental features have disappeared on 1.1.44? I'd like to test some of them (like wheel speed input) but didn't find them on 1.1.44.

You need difrent vems.hex. This is my_make for 12x12 with speed sensor enabled.
http://www.vems.hu/files/DamirMuha/1.1.46/my_make.txt

[Sprocket]

How stable is this firmware?