TunerStudioMS 0.95

[LT401Vette]

There is a little overview of TunerStudioMS at this site now:
http://www.efianalytics.com/TunerStudio/

I did get a new release out last night, 0.95.
There were quite a few fixes and improvements in it.
Note: Auto Update does not restart the app. It may start another copy, but to finish the update you will need to shut down all instances of TunerStudioMS and then start a new one. That will finish the update. With this being the first auto update, I didn't notice this problem until it was out the door. I'll have it fixed when you upgrade from what ever the next version is.

- Port scanning is now done in parallel, so if you have a port that hangs the port scan, you can type it in directly when you go to the menu:
Communications -> Settings

- The Dash should be switching from °C to °F and vice verse. The min, max and critical values will be based on the gauge defined in the ini file. You can change temp settings or any setting from the Project properties menu, the new values will take effect immediately upon clicking the Ok button.
The Project Properties can be access when a project is loaded, on the menu at:
File -> Project -> Properties

I'm sorry the documentation and communication has been so scare to this point. That is really for 2 reasons:
1) Time has been focused on getting the code done first, especially considering things are changing continuously.
2) I intentionally have kept communications somewhat low to shake the kinks out with a smaller group. It is getting closer, so the growth in usage is great to see.

There is still some more clean up to do, but things are coming along nicely. I just need to get back to the last couple missing Standard Dialogs. Once this base version is stable, then the focus will be on the real cool stuff to come.

[myk777]

I d-loaded it last night and gave it a quick try on the MS2 2.886 and it does connect now. I didn't have much time to play with it but it did seem like the calibrate TPS didn't work right or maybe I didn't understand it properly. The values it got from the processor were always 0 or 1 at closed and 1024 at open, I thought these would be somewhere kinda mid range i.e ~125 for low and ~900 for high? It did however report values like this when I first opened the dialog.

Mike

[LT401Vette]

Is that in a car or on a bench?
If in a car I'm with you, 0-1024 would be weird as it is full range. On a bench, that would be normal to get full range 0V-5V.

[myk777]

It was on the car (ATV actually)

Mike

[Per Eriksson]

Looks really sharp but it seems the celsius bug is still there?

I've tried shifting back and forth but it still shows in farenheit.

[LT401Vette]

Looks really sharp but it seems the celsius bug is still there?

I've tried shifting back and forth but it still shows in farenheit.

On the main dash?
I'm missing something, this works for me
What gauges specifically? All of them?

[Per Eriksson]

I tried the 2 different dash styles, both show iat and clt in farenheit.

Can I send you something to aid in finding the bug?

[LT401Vette]

If you go to Project Properties, does the setting show it is still in C?

File -> Project -> Properties

If you change it to C or F, does it change it on the dash?

Are you looking at the min's and maxes or is it the values that aren't getting converted?

[Per Eriksson]

It is the actual value that doesn't change.
In project settings it show the correct Cor F depending on what I set before.

On the dash it says C but numerical value is in F.

[myk777]

A few more things from testing tonight, looks great btw.

1) Still having same issue with TPS cal as stated above, doesn't seem to fetch proper ADC value from MS when the "get" button is pushed, however when you first open the dialog it is already populated with the correct values (not sure if this is what is in the chip already or the .ini?)

2) In guage designer the decimal place property doesn't seem to do anything.

3) When in a table and you modify cells by multiselecting (dragging box around cells) then make a change to the cells contents, the undo button doesn't work as I think it should, it only undoes one of the cells at a time not all of the cells that were changed.

4) Played a bit with the injector test mode and it wouldn't refire the injectors when "repeat test" was selected, in fact I'm not sure exactly how this dialog is supposed to work, it seems a little strange in Megatune also, in megatune I usually click repeat test, then continually hit the burn button and it refires the injectors, didn't act the same in TS.

Sure looks good though, keep up the great work.

Mike

[LT401Vette]

A few more things from testing tonight, looks great btw.

1) Still having same issue with TPS cal as stated above, doesn't seem to fetch proper ADC value from MS when the "get" button is pushed, however when you first open the dialog it is already populated with the correct values (not sure if this is what is in the chip already or the .ini?)

Is the blue progress bar underneath moving with the throttle?

2) In guage designer the decimal place property doesn't seem to do anything.

It limits the number of decimal places displayed on the numeric readout part. It will not change the static numbers around the outside.

3) When in a table and you modify cells by multiselecting (dragging box around cells) then make a change to the cells contents, the undo button doesn't work as I think it should, it only undoes one of the cells at a time not all of the cells that were changed.

Yeah, I know about this one. It is just because of the way my table widget sends changes, one sell at a time. It is at a lower level that memory model changes are tracked, so it sees each cell change as a single action to be undone. I need to alter the table widget to send chunks.

4) Played a bit with the injector test mode and it wouldn't refire the injectors when "repeat test" was selected, in fact I'm not sure exactly how this dialog is supposed to work, it seems a little strange in Megatune also, in megatune I usually click repeat test, then continually hit the burn button and it refires the injectors, didn't act the same in TS.

I haven't looked at this dialog, it is built from the ini. If you normally make it repeat using the burn button... I can see where that would be a problem. TS doesn't send the burn command if no data has changed.
Sure looks good though, keep up the great work.

Mike[/quote]

[LT401Vette]

It is the actual value that doesn't change.
In project settings it show the correct Cor F depending on what I set before.

On the dash it says C but numerical value is in F.

I see the problem now.... I was at work and not connected to an MS. The labels and limits are changing fine, but the actual value is not... I'll look into this.

[LT401Vette]

Scrap pile that theory. The values are changing for me too.

What firmware are you using? Which ini?

[Per Eriksson]

029q

Do you mean the ini that is in the project map?

[LT401Vette]

Both Coolant temp and Air temp?

What dash are you using?
What if you right click and load a different dash from under File?

[Per Eriksson]

Both are wrong, I think i've tried every possible combination with different dashes and switching back and fort between F and C.

I can send you my files and msq if it helps.

[LT401Vette]

Hmm. Can you zip up your whole project directory and send it to me? Maybe it is some combination of settings or something. But I should be able to reproduce it if I am running on the same project.

[Per Eriksson]

Here it comes

jevlar.rar

[LT401Vette]

Thanks for the help. I reproduced it and found the problem. Do an auto update for version 0.951 and it should work now!

[Morten VJ]

it looks like it Works.
But i placed my inc. files in the inc. diretory, and the temperature was Wrong.
I did trace the tps.inc to bee in the projektCFG.
And placed the inc. files there.
Hope it will work, tomorrow will tell.
B it's a confusing setup of directories.

Morten