Hi all,
I do a lot of tuning from recorded MS3 logs, which are sampled at quite a high speed.
I'm finding that VEAL in MLV is basically useless because of the 0 to 9 delay adjustment doesn't have the range or accuracy (over a log) required.
For example, at low loads, i have a lambda response delay of ~15 samples so the max of 9 is far too low. Even if i could set a value of 15, its then far too high for high load periods.
So can you please implement a load vs rpm delay table, and make it time based rather than sample based (just like it is in TS).
Thanks
Request: Fix VEAL lambda delay!
Moderator: LT401Vette
Request: Fix VEAL lambda delay!
Toyota Celica GT4/Alltrac with 5S-GTE stroker (2.2L I4 turbo, high CR) on E85 w/FlexFuel.
MS3 + MS3X + KnockBoard + RTC + BT + DIY CAN-IO-Board + DIY CAN Digital Dash.
MS3 + MS3X + KnockBoard + RTC + BT + DIY CAN-IO-Board + DIY CAN Digital Dash.
-
- Super MS/Extra'er
- Posts: 2221
- Joined: Tue May 04, 2004 8:20 pm
- Location: St Louis
- Contact:
Re: Request: Fix VEAL lambda delay!
Could you please a big data log.
Andy
Andy
Re: Request: Fix VEAL lambda delay!
There is nothing to stop you from opening up the log in a spreadsheet, derving the lambda delay from a lookup table and editing in the data you want where you want it.
Once you get adept at this sort of thing, you'll realise that VEAL etc is simply performing lookups, cross multiplying precentages based on the the four corners of the cells that surround your data point, and then multiplying up a value to return to you. These functions just do it so much faster than you can manually.
What is more, you can get a registered copy of TS do calculations for you, by importing one table , resizing it and storing it for another purpose. Effectively, you get a new interpolated table by the backdoor.
kind regards
Marek
Once you get adept at this sort of thing, you'll realise that VEAL etc is simply performing lookups, cross multiplying precentages based on the the four corners of the cells that surround your data point, and then multiplying up a value to return to you. These functions just do it so much faster than you can manually.
What is more, you can get a registered copy of TS do calculations for you, by importing one table , resizing it and storing it for another purpose. Effectively, you get a new interpolated table by the backdoor.
kind regards
Marek
-
- Super MS/Extra'er
- Posts: 12731
- Joined: Sat Jul 16, 2005 8:07 am
- Location: Moorseville, NC
- Contact:
Re: Request: Fix VEAL lambda delay!
I will get to it... I am spread very thin, but MLV is over due for some time.
Phil Tobin
EFI Analytics, helping to simplify EFI
Next Generation tuning software.
Supporting all MegaSquirt versions and firmwares.
http://www.TunerStudio.com
http://www.efiAnalytics.com/MegaLogViewer/
Support the firmware running your engine:
http://www.msextra.com/doc/donations.html
EFI Analytics, helping to simplify EFI
Next Generation tuning software.
Supporting all MegaSquirt versions and firmwares.
http://www.TunerStudio.com
http://www.efiAnalytics.com/MegaLogViewer/
Support the firmware running your engine:
http://www.msextra.com/doc/donations.html
Re: Request: Fix VEAL lambda delay!
Thanks PhilLT401Vette wrote:I will get to it... I am spread very thin, but MLV is over due for some time.
Toyota Celica GT4/Alltrac with 5S-GTE stroker (2.2L I4 turbo, high CR) on E85 w/FlexFuel.
MS3 + MS3X + KnockBoard + RTC + BT + DIY CAN-IO-Board + DIY CAN Digital Dash.
MS3 + MS3X + KnockBoard + RTC + BT + DIY CAN-IO-Board + DIY CAN Digital Dash.
-
- Experienced MS/Extra'er
- Posts: 374
- Joined: Thu May 26, 2016 1:25 pm
- Location: Germany
Re: Request: Fix VEAL lambda delay!
I started using 200Hz logs, and as this hasn't changed yet am also running into trouble. I have a delay of about 250ms at lower revs, and therefore would have to set a delay of ~50 samples.
Maybe change the slider to an input box for entering an integer, as a provisional fix in the meantime?
Maybe it would also be more robust to enter the time delay instead of a sample delay, as data rate can vary especially when using bluetooth.
Maybe change the slider to an input box for entering an integer, as a provisional fix in the meantime?
Maybe it would also be more robust to enter the time delay instead of a sample delay, as data rate can vary especially when using bluetooth.
My project: Link