Self changing cell values

[OrangeAlpine]

First of all, let me say I do not view this as a problem, more of a mystery.

While setting up the AFR table and Auto Tuning, I noticed one table value was totally wrong and a value I would never enter (15.1). I had decided to fatten up that cell to 14.7 from 15.0 which I thought I had entered, which is why the table was open. Did so, but when I came back to the cell a few minutes later, it was now 15.2! It seems that when a table is closed, the computer likes to change the value of the cell that is highlighted. I am combating that by highlighting an unused cell.

BTW, this has all come about because Auto Tune was completely unable to tune (still is, we'll do it manually) the 1600 rpm column. The engine was running in the 16's and I checked the AFR table to be sure I had not suffered a Senior Moment while setting up the table. Anyone ever experienced this issue?

Just one of the many computer problems I've been experiencing. I'm beginning to think the system is possessed. This is a Dell using XP. The Dell was being difficult (sees things that are not there) so I purchased an Asus 8.1 with Bing. My son decided to load Ubuntu into it, which locked up 8.1. As a result, we were never able to get 8.1 to run satisfactorily, so we got a new hard drive and loaded Mint Rebecca. Everything works but Tuner Studio! I think we are closing in on that issue (thanks Pile Driver), but that is with heavy emphasis on "we" not "I". My son is the brains of that operation and is currently not available to play with Dad's problems.

Bill

[LT401Vette]

I noticed one table value was totally wrong and a value I would never enter (15.1).

What that 15.1 in the VE Analyze VE Table tooltip, or the value in the AFR table itself?

I had decided to fatten up that cell to 14.7 from 15.0 which I thought I had entered, which is why the table was open. Did so, but when I came back to the cell a few minutes later, it was now 15.2!

The cell values wouldn't change while closed, but every time you open the table, it is freshly read from the MegaSquirt to be sure it is up to date. So did the change never make it back to the controller? That should only be possible without warnings if you have an older firmware. But as it was now higher than the original 15.1, well don't know.
What kind of MS do you have?
What firmware?

[OrangeAlpine]

The 15.1 was in the AFR table. Needless to say, I don't know what made it to where.

MS3X

1.3.2 Firmware

Tuner Studio MS v2.505

Bill

[LT401Vette]

Please update your TunerStudio, that release is a couple years old now.

[OrangeAlpine]

Really? I recently reinstalled XP in this computer which supposedly wiped out my Registered copy of Tuner Studio. I downloaded the free version of Tuner Studio a week or so ago and as it would not Auto Tune,my son reactivated my Registration Saturday.

Color me very confused.
Edit, it appears I accidently loaded the old version off of a jump drive.
Bill

[LT401Vette]

Hmmm, where did it get downloaded from?

Stick with these sites for current stable versions:

http://www.tunerstudio.com/index.php/downloads
http://www.efianalytics.com/TunerStudio/download/

[OrangeAlpine]

It was downloaded from the Tuner Studio site.

This wild. I found an MSQ for 2.16, so it had been installed. Just got off the phone with my son, he said he just registered whatever I was using. Looks like the laptop is playing some high tech mind games with a vulnerable old fart.

Bill

[jsmcortina]

It was downloaded from the Tuner Studio site.

Yes, but over a year ago.

I found an MSQ for 2.16, so it had been installed.

2.16 what? Not sure I understand.

James

[OrangeAlpine]

Tuner Studio v2.16 as opposed to Tuner Studio v2.05, which I had mislabeled 2.5. Dyslexia is one of my inherent problems.

Bill

[jsmcortina]

The TunerStudio version isn't related to the tune/MSQ.

James

[2swe]

Anyone ever experienced this issue?

Bill

yes I did.. I've noticed Spark table is slowly changing and I'm 90% sure AFR target table is changing too..
I think it has something to do with opening and saving once in TS other time in MLV.

I use MS1 HR11, TunerStudio and MLV is updated regularly.

MS1 works with whole numbers in VE and Spark tables, if I create msq in MLV it looks like this:

Code: Select all

<constant cols="12" digits="0" name="advTable1" rows="12" units="deg">
         20 12 20 26 32 37 40 43 45 45 45 45 
         20 14 20 25 31 34 38 42 45 45 45 45 
         17 16 20 25 29 32 34 37 40 40 40 40 
         13 16 19 23 27 29 31 33 34 34 34 34 
         14 15 18 23 26 28 29 30 31 32 32 32 
         13 13 17 22 24 26 27 28 28 29 29 29 
         13 13 17 21 23 25 26 26 27 27 27 27 
         12 12 16 20 23 25 25 25 26 26 26 26 
         12 12 16 20 22 24 25 25 25 26 26 26 
         12 12 16 19 22 24 24 24 24 25 25 25 
         12 12 15 18 20 21 22 22 22 23 24 24 
         12 12 15 18 20 21 22 22 22 23 24 24 
      </constant>

then I open this msq in TS to do other changes, and when I save it, it looks different :

Code: Select all

<constant cols="12" digits="0" name="advTable1" rows="12" units="deg">
         18.8672 11.1232 18.8672 24.8512 30.8352 37.1712 38.9312 43.1552 43.8592 43.8592 43.8592 43.8592 
         18.8672 12.8832 18.8672 24.1472 30.1312 34.0032 37.1712 42.0992 43.8592 43.8592 43.8592 43.8592 
         17.1072 16.0512 18.8672 24.1472 29.0752 30.8352 34.0032 37.1712 38.9312 38.9312 38.9312 38.9312 
         11.8272 16.0512 18.1632 23.0912 25.9072 29.0752 30.1312 31.8912 34.0032 34.0032 34.0032 34.0032 
         12.8832 13.9392 18.1632 23.0912 24.8512 28.0192 29.0752 30.1312 30.1312 30.8352 30.8352 30.8352 
         11.8272 11.8272 17.1072 22.0352 24.1472 24.8512 25.9072 28.0192 28.0192 29.0752 29.0752 29.0752 
         11.8272 11.8272 17.1072 19.9232 23.0912 24.1472 24.8512 24.8512 25.9072 25.9072 25.9072 25.9072 
         11.1232 11.1232 16.0512 18.8672 23.0912 24.1472 24.1472 24.1472 24.8512 24.8512 24.8512 24.8512 
         11.1232 11.1232 16.0512 18.8672 22.0352 24.1472 24.1472 24.1472 24.1472 24.8512 24.8512 24.8512 
         11.1232 11.1232 16.0512 18.1632 22.0352 24.1472 24.1472 24.1472 24.1472 24.1472 24.1472 24.1472 
         11.1232 11.1232 13.9392 18.1632 18.8672 19.9232 22.0352 22.0352 22.0352 23.0912 24.1472 24.1472 
         11.1232 11.1232 13.9392 18.1632 18.8672 19.9232 22.0352 22.0352 22.0352 23.0912 24.1472 24.1472 
      </constant>

when I open it in MLV again some numbers are changed..

[2swe]

So, I created an experimental msq with spark table containing numbers from 10 to 21, saved it in MLV as 1.msq

then I opened it in TS, and saved as 2.msq

then I opened 2.msq in MLV and saved as 3.msq

opened 3 .msq in TS, and voila, spark table is changed..

[LT401Vette]

Anyone ever experienced this issue?

Bill

yes I did.. I've noticed Spark table is slowly changing and I'm 90% sure AFR target table is changing too..
I think it has something to do with opening and saving once in TS other time in MLV.

I use MS1 HR11, TunerStudio and MLV is updated regularly.

MS1 works with whole numbers in VE and Spark tables, if I create msq in MLV it looks like this:

Code: Select all

<constant cols="12" digits="0" name="advTable1" rows="12" units="deg">
         20 12 20 26 32 37 40 43 45 45 45 45 
         20 14 20 25 31 34 38 42 45 45 45 45 
         17 16 20 25 29 32 34 37 40 40 40 40 
         13 16 19 23 27 29 31 33 34 34 34 34 
         14 15 18 23 26 28 29 30 31 32 32 32 
         13 13 17 22 24 26 27 28 28 29 29 29 
         13 13 17 21 23 25 26 26 27 27 27 27 
         12 12 16 20 23 25 25 25 26 26 26 26 
         12 12 16 20 22 24 25 25 25 26 26 26 
         12 12 16 19 22 24 24 24 24 25 25 25 
         12 12 15 18 20 21 22 22 22 23 24 24 
         12 12 15 18 20 21 22 22 22 23 24 24 
      </constant>

then I open this msq in TS to do other changes, and when I save it, it looks different :

Code: Select all

<constant cols="12" digits="0" name="advTable1" rows="12" units="deg">
         18.8672 11.1232 18.8672 24.8512 30.8352 37.1712 38.9312 43.1552 43.8592 43.8592 43.8592 43.8592 
         18.8672 12.8832 18.8672 24.1472 30.1312 34.0032 37.1712 42.0992 43.8592 43.8592 43.8592 43.8592 
         17.1072 16.0512 18.8672 24.1472 29.0752 30.8352 34.0032 37.1712 38.9312 38.9312 38.9312 38.9312 
         11.8272 16.0512 18.1632 23.0912 25.9072 29.0752 30.1312 31.8912 34.0032 34.0032 34.0032 34.0032 
         12.8832 13.9392 18.1632 23.0912 24.8512 28.0192 29.0752 30.1312 30.1312 30.8352 30.8352 30.8352 
         11.8272 11.8272 17.1072 22.0352 24.1472 24.8512 25.9072 28.0192 28.0192 29.0752 29.0752 29.0752 
         11.8272 11.8272 17.1072 19.9232 23.0912 24.1472 24.8512 24.8512 25.9072 25.9072 25.9072 25.9072 
         11.1232 11.1232 16.0512 18.8672 23.0912 24.1472 24.1472 24.1472 24.8512 24.8512 24.8512 24.8512 
         11.1232 11.1232 16.0512 18.8672 22.0352 24.1472 24.1472 24.1472 24.1472 24.8512 24.8512 24.8512 
         11.1232 11.1232 16.0512 18.1632 22.0352 24.1472 24.1472 24.1472 24.1472 24.1472 24.1472 24.1472 
         11.1232 11.1232 13.9392 18.1632 18.8672 19.9232 22.0352 22.0352 22.0352 23.0912 24.1472 24.1472 
         11.1232 11.1232 13.9392 18.1632 18.8672 19.9232 22.0352 22.0352 22.0352 23.0912 24.1472 24.1472 
      </constant>

when I open it in MLV again some numbers are changed..

MS1 has some rather odd scaling (0.352) for the advance table to get from the RAW binary values on the MS to the user values.
TunerStudio saves the msq with enough precision to exactly match the real value, even though MS1 has the spark table configured to only display it a a whole number.

advTable1 = array, U08, 0,[12x12], "deg", 0.352, -28.4, -10.0, 80.0, 0

So you can load/save forever and the values are the same...

Now there does seem to be an issue with MLV for MS1. It loaded and displays the values rounded to the proper whole number, but when saved it is truncating instead of rounding...
I'm glad you spotted this, but am quite surprised it was never noticed before!
This would only happen on MS1, So I don't think it applies to the OP, but relevant none the less.