Version 0.988.1 Released

[kritip]

Try saving as PNG, it should be a lot clearer, but not excessive file size.

[Peter Florance]

Try saving as PNG, it should be a lot clearer, but not excessive file size.

Can I do that from TunerStudio or is it still a printscreen capture?

Thanks!

[kritip]

still a screen capture. Just a matter of saving it in a different format.

[LT401Vette]

Peter, Can do. The blue looks really dark on your screen... JPG's loose clarity on save, they don't work well for screen shots. I usually use png files, they support 32 bit color and use a lossless compression.

Kaas, It sounds like there may be a write permission issue. What OS are you on? Are any of you settings getting saved from session to session? i.e, window position, navigation style, look & feel....

[Kaas]

Phil.
Yes I can save all of the things I have changed. I am using XP prof. I uninstalled the old TS and reinstalled, now I can use my new project and if I change the project to another one, then the changed one stays. So it works great now. I dont know what was wrong before.

BUT, I have found another thing.

Look in the AFR 8X8 table: This first picture is from when the msq is saved in MT. And it looks fine!



Look in the AFR again: This time I have saved the same msq in TS. So my analyzer gets f*** up but changest thing is when I open it in TS again, then the AFR in TS is correct and still wrong in MLW. If I save the same msq again in MT, then the AFR gets back to normal in MLW. STRANGE........

[LT401Vette]

Kaas, that's NOT good... What firmware are you on? Can you post an msq saved from TS?

[Kaas]

Yes its hr10_f and I am using MS1 2.2 MSnS

http://ljbk.dk/saab/ms/msq/alpha-badafr.msq

[Southcross]

I'm having some troubles with the Acceleration Wizard... i can't edit the acceleration points via the keyboard. I can only use my mouse to drag the points?

[Kaas]

I allso have that problem just with coolant-related air density!

[LT401Vette]

Make sure the Curve graph has focus. Either click on it or press tab until it has the dotted line around it.

[Southcross]

Make sure the Curve graph has focus. Either click on it or press tab until it has the dotted line around it.

my problem is Up & Down arrow, and Shift+Left/Right isn't changing the values of the data points in the Acceleration Wizard... but it seems to work on other things (I tested it on Priming Pulsewidth and it worked)


Also, how about being able to set a limit on the Datalog size? some how I turned it on while benchtesting my MS, forgot and had my MS on over night... my laptop totally freaked out when the log size exceeded 800MB. I'd say have a "total size" limit, and also could it create indexed files as it reaches certain file sizes.... so as an example, If I were to limit to 100MB, have it also be able to limit each log to 10MB and make log01.txt log02.txt logXX.txt...log10.txt. 10mb files are easier to run through your MegaLog than a 100MB file

[LT401Vette]

A max log size is easy enough, I'll put it on the list.

The Curve graph hot keys seem to be working fine for me.... The one difference between the Accel Wizard and the other Curve graphs is there are many components to have focus. On the other Curve Graphs the Curve graph is all alone so it will always have focus.
In the accel Wizard you need to make sure the one you want to change has focus. It will have a dashed line surrounding it when it has focus.

[Kaas]

Did you find the AFR problem?

[Southcross]

The Curve graph hot keys seem to be working fine for me....

oddest thing.... its fixed now

I copied my values from someone else.... his MAP values in the MT configuration were descending (values top to bottom) instead of ascending (values bottom to top) like the TPS values. I reversed all the values, now the hot keys work just fine... I don't know why someone would want to enter the Bin values backwards, but that was the source of my problems.

[UnaClocker]

This is not MS3 but MS2/Extra version 3.0.3 alpha which is the new sequential code. The signature is "MS2Extra Rel 3.0.3a".

Jean

I did mention we shouldn't call this version 3.. ;)

[LT401Vette]

Kaas,
The tpsBins problem... The problem is actually in MegaLogViewer, or you could say the HiRes code broke MLV rules

Here is what is happening... Because MLV doesn't read the ini file, it uses it's own set of rules to match X and Y bins to the tables. For MS1 firmwares, there is only one table per page, or that is the MLV rule anyway. So MLV matches what ever tpsBin and rpmBin it finds on the same page as the table Bins.....

But, I see that isn't true for here... "AFR Targets for VE Table 1" and "AFR Targets for VE Table 3" are both on page 7 in the ini
You have "AFR Targets for VE Table 3" with blank or all 0's for the tpsBins.

MLV will need a tweak to the logic.


Here is the work around though.... You just have to load your "AFR Targets for VE Table 1" into "AFR Targets for VE Table 3" in TunerStudio. Then MLV will have the right Bins...

Don't work about the miss-match for saving from MLV, MLV doesn't change any of the x or y values when it save an msq

[Kaas]

Table3 seems to be "grey" all the time, I cant set the afr targets for table3. I went to the lamdba afr setting and set table3 to on, but still cant get in to the afr table3!

I will just wait on till you find out what to do with the code!

[LT401Vette]

You'll need to turn on Dual table for Table 3 to be enabled.

The problem with the code is, well MLV code is in a bit of a state of flux... It is in a transitional state for MLV 3. So to make any changes to 2.954 I would have to branch and make double changes, I've been trying to avoid that .