VE Table Import?

shauer · Post by **shauer** » Sun Jun 15, 2008 3:56 pm

I have been using the latest alpha on my MSII-extra setup using Windows 2000 and it works great.

I was looking for a way to import a VE table that I modified in MegaLogViewer and I could not locate a way to do it. Is this feature supported yet?

Thanks

LT401Vette · Post by **LT401Vette** » Sun Jun 15, 2008 8:53 pm

That is near the top of the todo list. But currently it does not import a vex, only export.

For mow you need to load the whole msq. But I should point out that when you load an MSQ into TunerStudio and tell it to burn it to the controller, it only sends the changed bytes, not the entire msq. So there is little advantage to using vex to transport between the 2 programs.

shauer · Post by **shauer** » Mon Jun 16, 2008 4:20 am

Thanks for the information on the msq save in TunerStudio. I have been only importing VE tables from Megalogviewer for the past couple months as a work around to a bug that existed.

I am under the impression that the 16x16 table save bug in Megalogviewer is still there? My config uses two 16x16 tables and the last time I tried saving an entire msq it made a mess of the tables due to a memory overlap issue between the 12x12 and 16x16 tables in the later versions of MS2-extra. Was this bug fixed and I just missed a thread somewhere?

Keep up the great work on TunerStudio. I'm already playing with dash layouts...

LT401Vette · Post by **LT401Vette** » Mon Jun 16, 2008 6:09 am

I think you got me. I did put in a fix for the 16x16 tables, but only for veTable1. If you are using dual table, the second table will still have issues....

I'll get this resolved on both ends.

RangingRover · Post by **RangingRover** » Sat May 02, 2009 10:41 pm

Just a quick bump on this one - I'm using MLV 2.954 (as far as I know the latest version?), and just started using blended tables. After many hours of testing, updating and changing settings I worked out that MLV when editing veTable2 doesn't change the values in both areas it needs to, only in veTable2, and the mismatch was what was causing my msqs to load screwy... So just a quick reminder. No big drama, as shauer says you can just import vetable2 once the msq has been loaded (although in some of my testing vetable1 would go screwy also after changing table2), just painful when you're chasing it.

LT401Vette · Post by **LT401Vette** » Sun May 03, 2009 1:13 pm

I don't remember if I ever made the second table work right or not. Judging by what you say, I didn't.....

It is pretty tricky, because what happens is; Those tables share the same memory on the controller, MLV only edits the values in the msq. The 16x16 and 12x12 tables have their own set of values in the msq.
So, if MLV edits the 16x16 tables, but leaves the 12x12 tables alone, what happens when you open it in TS or MT is:
The 16x16 table may load first and update the memory in the controller, then it will load the 12x12 tables on veTable1 and veTable2 and over write the memory with those values....

What I would recommend doing for now with the dual tables is to
a) Copy and paste the values if you are using TunerStudio
or
b) export the table to a VEX, then import in TunerStudio or MegaTune.

MLV has been slow on changes for 2 reasons... TunerStudio work, but also that I have quite a few shared components that have been on branched code from TunerStudio. The MLV 3.0 code has been moving everything to the new packages, but has been sort of in flux... But I just fired it up a couple days ago, with only a few issues to resolve. Soon I hope to have TunerStudio released and really focus on MLV for a while. Not that TunerStudio is out of ideas, but I think MLV is falling behind

RangingRover · Post by **RangingRover** » Mon May 04, 2009 2:34 am

LT401Vette wrote: It is pretty tricky, because what happens is; Those tables share the same memory on the controller, MLV only edits the values in the msq. The 16x16 and 12x12 tables have their own set of values in the msq.
So, if MLV edits the 16x16 tables, but leaves the 12x12 tables alone, what happens when you open it in TS or MT is:
The 16x16 table may load first and update the memory in the controller, then it will load the 12x12 tables on veTable1 and veTable2 and over write the memory with those values....

What I would recommend doing for now with the dual tables is to
a) Copy and paste the values if you are using TunerStudio
or
b) export the table to a VEX, then import in TunerStudio or MegaTune.

MLV has been slow on changes for 2 reasons... TunerStudio work, but also that I have quite a few shared components that have been on branched code from TunerStudio. The MLV 3.0 code has been moving everything to the new packages, but has been sort of in flux... But I just fired it up a couple days ago, with only a few issues to resolve. Soon I hope to have TunerStudio released and really focus on MLV for a while. Not that TunerStudio is out of ideas, but I think MLV is falling behind

vetable3 in 12x12 form is also used to store values for the 2 16x16 tables... I worked out that the first value in vetable3dozen corresponds to the first value in the third line of veTable2 (16x16). I think vetable2dozen must be used to store the end of vetable1 and the start of vetable2..... But it doesn't matter. As you say, exporting the table works fine, and isn't a big hassle if you are aware of it.

Not trying to hassle or be a pain, just a gentle reminder in case it had slipped by the wayside, I know you are flat out juggling the two programs, and I'm very interested to see what MLV3 looks like....

LT401Vette · Post by **LT401Vette** » Mon May 04, 2009 9:56 am

vetable3 in 12x12 form is also used to store values for the 2 16x16 tables... I worked out that the first value in vetable3dozen corresponds to the first value in the third line of veTable2 (16x16). I think vetable2dozen must be used to store the end of vetable1 and the start of vetable2..... But it doesn't matter. As you say, exporting the table works fine, and isn't a big hassle if you are aware of it.

Exactly

So to fix veTable1 I go through all of veTable1dozen and part of veTable2dozen and update the values to match. And if both the dozen tables and the 16x16 tables are dirty I don't really know which values to use, but I give the 16x16 priority.
For veTable2 it starts in the middle of veTable2dozen and goes into 3, if the update goes the other way, veTable2dozen starting in veTable1 and goes into veTable2. It gets messy quickly. So I just fixed it for the 95% that are using single table. This was when I thought I might be making MLV ini aware, then it would have better visibility into the ini like TS, but I have decided that probably has more downsides than up. So I better just fix it

On another note, I saw you have had crashing problems with TunerStudio, is this on a recent version? The current release should be 100% stable, so if you have problem I do appreciate more information.

RangingRover · Post by **RangingRover** » Tue May 05, 2009 5:37 am

LT401Vette wrote: On another note, I saw you have had crashing problems with TunerStudio, is this on a recent version? The current release should be 100% stable, so if you have problem I do appreciate more information.

That was with 0.988.5, which I think is the most recent? However I have updated Java since then, and haven't yet tried TS again since then, so that may make a difference. If not, I'll try that RXTX driver you linked to in the other thread. Either way, I'll report back in the other thread when I know more....

LT401Vette · Post by **LT401Vette** » Tue May 05, 2009 6:41 am

Unless you are running a Mac you shouldn't need to mess with the RXTX, it is in there when you install it.

Please let me know if it doesn't anything weird, I prefer to know so I can try to fix it for everyone.

Megasquirt Support Forum (MSEXTRA)

VE Table Import?

VE Table Import?

Re: VE Table Import?

Re: VE Table Import?

Re: VE Table Import?

Re: VE Table Import?

Re: VE Table Import?

Re: VE Table Import?

Re: VE Table Import?

Re: VE Table Import?

Re: VE Table Import?