I have an unusual setup.
VE1 is SD. <100kpa = 100kpa, above this it increases, like a multiply map.
VE2 is AN. This is the main load map.
When I use MLV 4.1.0.1 and load a tune file I can use VE Analyzer, and you can select vetable1 or vetable2.
If I choose vetable2 (AN), it still modifies and moves around the VE map with the blue trace based on datalog points MAP value, not on TPS value.
eg: VE Analyzer on vetable1 - If I'm at 4000rpm @ 100kpa but 40% throttle, blue trace goes to 4000rpm @ 100, which is correct.
eg: VE Analyzer on vetable2 - If I'm at 4000rpm @ 100kpa but 40% throttle, blue trace goes to 4000rpm @ 100 instead of 4000rpm @ 40 . Incorrect.
I think if loading an msq, vetable1 and vetable2 there needs to be a lookup in the main settings to see what algorithm is being used.
Or there is a bug.
Great software, did a ton of laps yesterday and just minor edits after each session. Sweet.
VE analyze - VEtable2 error?
Moderator: LT401Vette
-
- Master MS/Extra'er
- Posts: 632
- Joined: Sun May 02, 2004 2:16 pm
- Location: Auckland, NZ
- Contact:
-
- Super MS/Extra'er
- Posts: 2221
- Joined: Tue May 04, 2004 8:20 pm
- Location: St Louis
- Contact:
Re: VE analyze - VEtable2 error?
I have my ITB motor tuning set up the same way. I have not tried VEAL or VEA in MegaLogViewer, but I would think you would want it to apply trims to the table that you have chosen. This request may generate some tricky programming based on all the tuning possibilities.
At this point, I have resorted to hand tuning an open loop as my motor is fairly violent.
Andy
At this point, I have resorted to hand tuning an open loop as my motor is fairly violent.
Andy
-
- Master MS/Extra'er
- Posts: 632
- Joined: Sun May 02, 2004 2:16 pm
- Location: Auckland, NZ
- Contact:
Re: VE analyze - VEtable2 error?
Hi Andy,
Thanks for quick response.
Yes mine is hand tuned with another person driving or based on datalogs.
At the track yesterday I thought I would try the VE analyzer to see what it would do and noticed this.
Was quick enough to just hand fine tune it based on areas with larger ego corrections. So I should have said that there's no urgency or real need for me to use ve analyzer.
Thanks for quick response.
Yes mine is hand tuned with another person driving or based on datalogs.
At the track yesterday I thought I would try the VE analyzer to see what it would do and noticed this.
Was quick enough to just hand fine tune it based on areas with larger ego corrections. So I should have said that there's no urgency or real need for me to use ve analyzer.
-
- Super MS/Extra'er
- Posts: 12731
- Joined: Sat Jul 16, 2005 8:07 am
- Location: Moorseville, NC
- Contact:
Re: VE analyze - VEtable2 error?
MLV has 1 Y axis load that will be the default for every table, that is set from the main menu.
However, you can set an over-ride for any individual table.
Go to VE Table2, right click on the Y-Axis and select "Set Y-Axis Over-ride"
in there enter "TPS" then it will trace that table to TPS, also for VE Analyze will use TPS for that table..
However, you can set an over-ride for any individual table.
Go to VE Table2, right click on the Y-Axis and select "Set Y-Axis Over-ride"
in there enter "TPS" then it will trace that table to TPS, also for VE Analyze will use TPS for that table..
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
-
- Master MS/Extra'er
- Posts: 632
- Joined: Sun May 02, 2004 2:16 pm
- Location: Auckland, NZ
- Contact: