1) When using VEAnalyze, you have to set different Lambda signal delays for different parts of the table to get meaningful results. I'm aware TS has a little table built in for that for VEAL.
Would it be possible to implement this feature into MLV, in addition or instead of the slider?
This also could be helpful when browsing through logs. I currently use a custom field I called AFRError, which is ([Field.AFR]-[AFR Target 1]). This of course doesn't incorporate the delays, and is unreliable in transients.
2) If the above is not an option, would it be possible to add a "reset" button to VEA?
For example, when I do an analysis with delay 1, and then with delay 0, the calculated VETable gets changed differently compared to analyzing with delay 0. It seems the VETable calculated in the prior analysis is used as the base for the next analysis. I wonder if this is on purpose, as I can't really think of a reason doing it this way right now besides forcing cells to change easier - but theres already the cell change box for that?
Anyway, when doing several analyses using different delays in succession, I therefore have to close VEA and reopen it, including re-setting the correct Afr-table etc. A simple reset button to discard the changes in the VETable suggested by the prior analysis would solve this.
Lambda signal delay / reset VEA
Moderator: LT401Vette
-
- Experienced MS/Extra'er
- Posts: 374
- Joined: Thu May 26, 2016 1:25 pm
- Location: Germany
Lambda signal delay / reset VEA
My project: Link
-
- Super MS/Extra'er
- Posts: 12733
- Joined: Sat Jul 16, 2005 8:07 am
- Location: Moorseville, NC
- Contact:
Re: Lambda signal delay / reset VEA
I can't believe that has not been back ported yet... I just never seem to get caught up.
How I have always managed that is I primarily use 2 delays, one above 80 kPa and one below.
In VEA:
- I set a filter to filter everything below 80 kPa
- run VEA with lambda delay at one, accept the table
- Open VEA again, set the filter to filter everything above 80 kPa
- Run VEA with lambda delay set to a higher value.
Hopefully soon MLV will get some time...
How I have always managed that is I primarily use 2 delays, one above 80 kPa and one below.
In VEA:
- I set a filter to filter everything below 80 kPa
- run VEA with lambda delay at one, accept the table
- Open VEA again, set the filter to filter everything above 80 kPa
- Run VEA with lambda delay set to a higher value.
Hopefully soon MLV will get 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