Would it be possible to plot a second vertical line on the MLV plot for where the AFR data which corresponds to "now" appears?
Alternatively, could one make the AFR data plot onto the screen back in time according to where the lambda delay thinks it has come from?
This would make reading AFRTarget versus AFR easier and would help one set a better lambda delay figure into TS.
kind regards
Marek
feature suggestion - lambda delay
Moderator: LT401Vette
Re: feature suggestion - lambda delay
I saw "lambda delay" and got excited... I am not sure this is what your after, but I would love to see the lambda delay targets integrated into the VE analysis tuning section. I really prefer to do actual tuning, offline so I can watch the changes.
Forget the porn, my bathroom is full of car manuals...
1977 Rabbit (retired)
1991 Cabriolet (retired)
1977 Rabbit (retired)
1991 Cabriolet (retired)
Re: feature suggestion - lambda delay
Yes that's exactly what I am saying:-
In TS, during VEAL, it uses AFR data based on the lambda delay, but offline in MLV, the same process uses records between 0 and 10 records earlier - it means that the same "tuning" offline and in real time are using different AFR data which can't be a good thing.
kind regards
Marek
In TS, during VEAL, it uses AFR data based on the lambda delay, but offline in MLV, the same process uses records between 0 and 10 records earlier - it means that the same "tuning" offline and in real time are using different AFR data which can't be a good thing.
kind regards
Marek