Update 0.982.4

[em_knaps]

Indeed, the laptop i use for tuning is only 800mhz,

The 3ghz machine is my desktop PC i use for checking the operation of my MS whilst hooked up to the stim

Is there an application that could detect processor power and preset TS to suit?
Perhaps on install?

Thanks again Phil,
Great work.

Daniel.

[LT401Vette]

I actually do that to a degree. The dashboards are not limited, but anti-alias will default to off if you are on a slow machine.

[smolly]

There seems to be a small problem in the AFR table.
For example, a value of 16.0 is shown as 15.9 in the 2D view. The 3D view is allright, there the 16.0 is shown. I've checked it against Megatune

I'm guessing it is a rounding difference. Can you shoot me an msq where you are seeing this happen?

[LT401Vette]

smolly,
I looked into this and it was as I suspected, the table is truncating instead of rounding the least significant digit. When you are seeing a 16.2:1 AFR after transforming it to the actual byte level in the MegaSquirt it is actually something like 16.1809... With the table only displaying 1 significant digit, it should be rounded to 16.2, but it was getting truncated to 16.1 instead.

So it is fixed now for the next release.

Thanks for spotting this.

[wes kiser]

This is the first update I have tried in close to 6 months, and I just want to say great job. I have been having a rash of random MS projects lately, so I wanted to try it again. I have a couple of questions/suggestions

1) How do you import VE tables?
2) Are the .msq files directly compatible with Megatune (my VE and Ignition tables do not appear to come in the same)
3) Make the x and y scales of the AE wizzard user definable. All of my installs are large throttle, small displacement engines with large injectors. My maximum AE values are never greater than 4ms, and my %/s numbers are never larger than 50%/s. This makes for a very bunched up, nearly unreadable AE table.

[LT401Vette]

1) How do you import VE tables?

VEX import still not there, it is almost done but somehow keeps falling off the list. You can copy & paste the table values from another table in TS or MLV for now though.

2) Are the .msq files directly compatible with Megatune (my VE and Ignition tables do not appear to come in the same)

They are directly compatible, both ways. If you are seeing some minor differences in the 2 D tables, it is do to a problem with the displayed value being truncated instead of rounded. This is fixed for the next update that should be out tonight. If you look at the values in the 3D view, they should always match MegaTune in the current version.

3) Make the x and y scales of the AE wizzard user definable.

I have been tossing around a good way to do this as I know it can vary quite a bit on different installs.

[Black99rt]

Nice work on the software and the update. I've completely given up on MT, as it never reliably starts with my usb adapter no matter what "fixes" I try. TS works flawlessly every time.

I saw you mentioned a version of VE analyze coming soon. Will it be using system ram so that the laptop can perform it on a running engine using the MSII extra code? I was under the impression MT's VE analyze doesn't work because limited ecu ram availability with the extra code's features.

[LT401Vette]

Thanks,

The way I am doing the VE Analyze it doesn't require any significant ram. It isn't like MLV where the entire log is loaded into memory, it works with the data as it comes maintains live statistical data and drops the older raw data once it is worked in. It is similar to MLV's VE analysis, but I am incorporating several improvements that I haven't gotten into MLV yet.
There are still several advantages to off line processing like MLV, primarily that you don't need to put as many precautionary measures in place. If there is a problem with the input data like a dead O2 signal, you aren't making changes to the tune on a running engine, there is a opportunity to see something is wrong. If you are working on a running engine, some additional monitoring is quite important to detect more input data problems. So that is a focus of VE Analyze live.

[Black99rt]

Better logic for rich misfires would be great. Or at least, not using a huge AFR lean spike to adjust the VE table, and perhaps flagging it as a cell that needs user attention.