Hi,
I've been having trouble tuning my Rover V8 with a new MS2V3 3.3.2 msextra code.
Today I opened up a log file from the weekend in MLV and then for the first time realised I could also open up the MSQ and see the VE and Ignition tables in "real" time with the log.
What I saw seemed weird. I had originally had a 16x16 but changed it to 12x12 as there were no real examples of a VE table at 16x16 so copying a known good example was easier at 12x12. Well, in MLV it shows up as 16x16 still. And the values I am seeing in the areas I am having trouble with a wayyyy higher than what I see in Tunerstudio.
Here's the VE from Tunerstudio:
And here's what I see in Megalogviewer:
Is this a bug?
Cheers,
Trav.
Wierd difference between VE table in TunerStudio and MSLogVi
Moderator: LT401Vette
Wierd difference between VE table in TunerStudio and MSLogVi
--
Trav
ms2extra, v3, Rover 4.6l
Trav
ms2extra, v3, Rover 4.6l
Re: Wierd difference between VE table in TunerStudio and MSL
And the MSQ file also...
--
Trav
ms2extra, v3, Rover 4.6l
Trav
ms2extra, v3, Rover 4.6l
Re: Wierd difference between VE table in TunerStudio and MSL
Underneath the AFR table, it should give the MSQ file name that is loaded. Is that the same as the one you're using in MS?
Rover SD1 3.5 EFI
MS2 V3
EDIS
Tech Edge O2
London UK.
MS2 V3
EDIS
Tech Edge O2
London UK.
Re: Wierd difference between VE table in TunerStudio and MSL
Sure is. Double and triple checked as it was an obvious answer.
--
Trav
ms2extra, v3, Rover 4.6l
Trav
ms2extra, v3, Rover 4.6l
Re: Wierd difference between VE table in TunerStudio and MSL
Right - sorry for asking the obvious. Other obvious one would be there are two files of the same name but different locations. Or, of course, a bug somewhere.travm wrote:Sure is. Double and triple checked as it was an obvious answer.
Rover SD1 3.5 EFI
MS2 V3
EDIS
Tech Edge O2
London UK.
MS2 V3
EDIS
Tech Edge O2
London UK.
Re: Wierd difference between VE table in TunerStudio and MSL
I've confirmed that the files were the right ones.
I've also gone and re-set the VE table size back to 16x16 in Tunerstudio and the values that show up in MLV are reflected in the new table. Haven't had a chance to try it in the car to see if the issues with running are resolved but now I've smoothed out the values so they are not jumping from 35 to 76 and back to half again between adjacent cells I'm thinking it might run a little better.
How does one log a bug report??
Cheers,
Trav.
I've also gone and re-set the VE table size back to 16x16 in Tunerstudio and the values that show up in MLV are reflected in the new table. Haven't had a chance to try it in the car to see if the issues with running are resolved but now I've smoothed out the values so they are not jumping from 35 to 76 and back to half again between adjacent cells I'm thinking it might run a little better.
How does one log a bug report??
Cheers,
Trav.
--
Trav
ms2extra, v3, Rover 4.6l
Trav
ms2extra, v3, Rover 4.6l
-
- Super MS/Extra'er
- Posts: 12731
- Joined: Sat Jul 16, 2005 8:07 am
- Location: Moorseville, NC
- Contact:
Re: Wierd difference between VE table in TunerStudio and MSL
How it works under the covers on the firmware, is that both the 12x12 tables and the 16x16 are mapped to the same RAM. So only the one you are using will look right, the others will be scattered like in your picture.
MegaLogViewer doesn't know which table you are using, it displays both veTable1 (the 16x16) and veTable1dozen (12x12), so if you are using the 12x12 tables in TunerStudio, in MLV you need to select the veTable1dozen to get the right table.
However, I also wanted to point out, even if the base table you want to load is 12x12, you don't need to change to 12x12 tables. You can load a 12x12 table into a 16x16 and TS or MLV will scale and interpolate it to the new size.
MegaLogViewer doesn't know which table you are using, it displays both veTable1 (the 16x16) and veTable1dozen (12x12), so if you are using the 12x12 tables in TunerStudio, in MLV you need to select the veTable1dozen to get the right table.
However, I also wanted to point out, even if the base table you want to load is 12x12, you don't need to change to 12x12 tables. You can load a 12x12 table into a 16x16 and TS or MLV will scale and interpolate it to the new size.
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