0.97 Released

[LT401Vette]

Hey shauer,
I was just going back to finish the table import and well an interim solution light bulb went on for me....
You can select the table cells in MLV and copy & Paste them into TunerStudio....

They are both doing the copy paste I'm not sure why that didn't click earlier.

[shauer]

Hey shauer,
I was just going back to finish the table import and well an interim solution light bulb went on for me....
You can select the table cells in MLV and copy & Paste them into TunerStudio....

They are both doing the copy paste I'm not sure why that didn't click earlier.

Wow, that is so simple. Thanks!

I never thought of even trying that.

[dave]

Which firmware?

29q i beleive

[q4_fre]

Lately I have been having trouble with usb adapters in megatune. Any difference in code here that it might be likely to work better with this software?
Have used it alot on megatune on std ms2 code. But msextra 2 it seems to be just putting random values everywhere when I burn..

[LT401Vette]

q4_fre, It is completely different code. I would say there is a very good chance your comm will work better. Have you tried any other USB adapters? If there is a problem with the driver for your adapter, TS won't be able to fix that, but i have tested this with about 6 different, mostly very cheap ones off of eBay and I haven't found one that didn't work in windows yet. A couple that gave some troubles in Linux.

dave,
After calibrating with the project open, was there a throttleFactor.inc in the projectCfg dir, or is that the problem, it didn't even make the file?

[xrattiracer]

I dont know if this has been mentioned yet, but as an alternative to the usb adapters you can get pcmcia serial adapters. I had too many problems with the usb adapters with my projects and ended up getting one of these. They work exactly like a hardware serial port (because they are, really) and can be even cheaper than usb ones on ebay. Dont be put off by most of them being shipped from china or taiwan either, they show up in just a couple days.

[q4_fre]

q4_fre, It is completely different code. I would say there is a very good chance your comm will work better. Have you tried any other USB adapters? If there is a problem with the driver for your adapter, TS won't be able to fix that, but i have tested this with about 6 different, mostly very cheap ones off of eBay and I haven't found one that didn't work in windows yet. A couple that gave some troubles in Linux.

Been testing with the usb converter now and it seems to work just fine! Very nice!

But, how do I change the rpm and map bins for the ve and ign table?

[LT401Vette]

But, how do I change the rpm and map bins for the ve and ign table?

Click on them

[dave]

dave,
After calibrating with the project open, was there a throttleFactor.inc in the projectCfg dir, or is that the problem, it didn't even make the file?

you know what, finally tried it today and it worked fine. I guess I should have re-loaded the program.

i was unsuccessful burning the new msq file to MS. The only way I could figure it out was to save and re-load the file and hit yes when it opens, but it instantly produces timeout errors and doesn't do it. I had to u/l the changes using megatune.

also I tend to use the "fetch from ecu" button a lot w/ the fuel table when i forget which file i had in there during a datalog. I missed it.
Using the burn button from the ve table seemed to work but i didn't change anything just then so not 100% sure, i just know that it had a small delay and didn't give me an error.

[LT401Vette]

you know what, finally tried it today and it worked fine. I guess I should have re-loaded the program.

Perhaps it was just in another project you had calibrated before. I should point out for others, it is only MS1 that uses throttleFactor.inc. MSII stores the calibration in the controller.

i was unsuccessful burning the new msq file to MS.

Do you mean just changes you made while connected? If you are connected, they will all be written to the unit as you make them. To load a full msq the only way is to open it and select yes when prompted to write to the controller. That should be the same as MegaTune. If you have an msq loaded before you are online, then go online, the controller data will overwrite the loaded msq. I don't plan to leave this entirely this way long term, I just did it for now to be consistent with MegaTune and the improvements fell to a lower priority that some other functions. The longer term plan is to do a dif when it goes on-line and prompt the user as to weather they want to:
- Send the loaded tune to the controller
- Read the Tuner from the Controller
- View all different settings side by side.

The Fetch Button is easy enough to add, but I think it causes people more confusion about what it does than it is useful, the burn button sort of falls into this category too though.
Really all the fetch Button can do is undo any changes that have been made since the last time you clicked burn. MegaTune performs a Fetch before every dialog opening, so if you make changes and don't click burn, you will get back what you had when you first opened the dialog.
When you close the dialog a Burn is always sent, so you don't really need the Burn Button either. But the Burn button does let you tell the Controller to persist the settings without closing the dialog.

I have wanted a Fetch Button a couple times myself, primarily when I am too far away(a couple floors) from the controller using Bluetooth and the initial connect fails on the read. I need a way to tell it to try again once i move closer. I am thinking there are other ways to handle this though.
But I am completely open to putting a fetch button there if there are some scenarios I am over looking. I just don't want to put it there because we are used to it there.

it instantly produces timeout errors and doesn't do it.

This is important!
What type of timeout errors?
What type of connection are you using?
What OS?
Type of computer?

i just know that it had a small delay and didn't give me an error

I'm assuming you mean the Controller gave a stumble?
I'm thinking I may need better feed back to the user when things are getting written and burned to the Controller. That is a bit different than MegaTune. With MegaTune being a single threaded app, the whole app freezes while it is writing to the Controller, so the user can not do any thing and knows it is working. When it unfreezes, the user knows it is done. TunerStudio handles all comm activity on a separate thread, so you will not feel the comm work in the UI, it will just keep working. Even when you load an msq, it loads almost immediately. then the data is sent in a separate thread.

It should also be noted, that TunerStudio only sends the delta information to the controller. So it will typically load an msq in a small fraction of the time that MegaTune does.
So, say you:
- Save an MSQ in TunerStudio
- Open the MSQ in MegaLogViewer
- Change the value of 6 cells in a ve table
- Save the msq in MLV
- Go back to TunerStudio while connected to the controller
- Open the MSQ and select Yes when prompted to burn to the controller

Only the 6 changed bytes will be sent. TunerStudio does a byte level dif with what is on the controller and only sends bytes that are different from what is already on the controller. So as you can imagine, that is usually done before you lift your finger from the mouse clicker. You might wonder if it even worked

[dave]

i was unsuccessful burning the new msq file to MS.

Do you mean just changes you made while connected? If you are connected, they will all be written to the unit as you make them. To load a full msq the only way is to open it and select yes when prompted to write to the controller. That should be the same as MegaTune. If you have an msq loaded before you are online, then go online, the controller data will overwrite the loaded msq. I don't plan to leave this entirely this way long term, I just did it for now to be consistent with MegaTune and the improvements fell to a lower priority that some other functions. The longer term plan is to do a dif when it goes on-line and prompt the user as to weather they want to:
- Send the loaded tune to the controller
- Read the Tuner from the Controller
- View all different settings side by side.

ok. I seldom do my tuning live, it is always loading files.

fetch/burn stuff

I was totally unaware of this!!!
i had no idea it was automatically uploading to the device, wow I'm glad i didn't have some wierd test file loaded when i turned the car on!
DEFINITELY make this more obvious. and.. optional? maybe it is, will double check. Megatune wasn't great about making read/write changes known either in my opinion.

it instantly produces timeout errors and doesn't do it.

This is important!
What type of timeout errors?
What type of connection are you using?
What OS?
Type of computer?

I'll do it again tonight and copy/paste the error dialouge. Sorry for the lack of details, I wasn't sure if this was already known or not.

[LT401Vette]

I was totally unaware of this!!!
i had no idea it was automatically uploading to the device, wow I'm glad i didn't have some wierd test file loaded when i turned the car on!
DEFINITELY make this more obvious. and.. optional? maybe it is, will double check. Megatune wasn't great about making read/write changes known either in my opinion.

If you have a weird file loaded and you connect to your car by turning it on, the car's tune will be loaded and over ride the loaded msq. The msq wouldn't get written to the car, it's exactly the same as MegaTune.

While you are connected with any of the Tuning Software's (Megatune, MegaTunix and TunerStudio) any changes you make are actually changes sent to the controller. You can not open an msq and edit it without updating the controller unless you are not connected or select work off line.

[dave]

I was totally unaware of this!!!
i had no idea it was automatically uploading to the device, wow I'm glad i didn't have some wierd test file loaded when i turned the car on!
DEFINITELY make this more obvious. and.. optional? maybe it is, will double check. Megatune wasn't great about making read/write changes known either in my opinion.

If you have a weird file loaded and you connect to your car by turning it on, the car's tune will be loaded and over ride the loaded msq. The msq wouldn't get written to the car, it's exactly the same as MegaTune.

While you are connected with any of the Tuning Software's (Megatune, MegaTunix and TunerStudio) any changes you make are actually changes sent to the controller. You can not open an msq and edit it without updating the controller unless you are not connected or select work off line.

ah ok i had it backwards
Maybe it was a noob thing that i didn't know this even after all the tuning i've done, but a visual feel-good indicator that your change hit the car would be neat. same with the read-in, I didn't assume that at all, and wouldn't notice if 4 numbers on the VE table weren't what i thought.

[LT401Vette]

a visual feel-good indicator that your change hit the car would be neat. same with the read-in, I didn't assume that at all, and wouldn't notice if 4 numbers on the VE table weren't what i thought.

Agreed. I would like to prompt the user with the options I listed above when they connect. I should have that in pretty short order. Feed back from someone new is often the best, it is new to everyone at some point and if you look at it long enough, even the complex seems simple. That won't help the next guy though

I have no idea how long I was using MegaTune before i fully understood when it was reading and writing to the controller.

I like the idea of some indicator that things are being written too. Overall the simplest way to look at is:
While TunerStudio is connected to a controller, it always maintains state between the controller memory and local memory. There is a Memory Synchronization component in the application with that as it's only job, move bytes an back and forth to insure it is the same in both locations. The Controller always wins if the memory is different.

[dave]

I would like to prompt the user with the options I listed above when they connect. I should have that in pretty short order.

sounds cool, just don't bastardize the nag-free startup.

[myk777]

Have been away from this for a while but just loaded up the latest alpha last night and tried it out on my setup. Seems to connect fine and guages all have reasonable values. I do however have one question regarding the TPS calibration: When I open the calibration screen it has already pre-populated the TPS adc values (say like 224 closed and 996 wide open), these match the ones I used when I calibrated it in megatune which makes sense since I believe the MS-II chip stores this on-chip and doesn't use an .inc file for the throttle cal, so TS is just retrieving this data from the chip and displaying it. However if I ask it to "get" the current values from the chip it will return a value of 0 for closed throttle and a value of 1024 for open throttle, it appears that these are already using the calibration and not the "true" adc values, this also differs from the megatune results and gives an error when you try and close the calibration screen in TS. I thought I understood this, but I can't figure this one out?

MS-II, standard code v2.886

Mike

[Eagle7]

Phil, I miss the MT indication of the filename of the msq that is loaded. Or have I overlooked it somewhere? Also would appreciate an indication that the file is no longer up to date (something modified).

Wonderful application. Great work. Thank you.

[LT401Vette]

myk777, that is interesting.... When you click get current, it is just putting the value from tpsADC I wouldn't expect the tpsADC outputChannel to return calibrated tainted numbers.

But I just went and looked in the ini for 2.886, this is what I found:

Code: Select all

   tpsADC           = { tps*10.23 }, "ADC" ; Fake for calibrator and file indexing.

It looks like tpsADC is just based on percent * 10.23??? I'll have to look into what MegaTune is doing here. It may be using the the currently stored min and max to reverse calculate the REAL value.

Eagls7,
You aren't overlooking anything.... It isn't there. Good point. I'll put something in.

Thanks!

[myk777]

myk777, that is interesting.... When you click get current, it is just putting the value from tpsADC I wouldn't expect the tpsADC outputChannel to return calibrated tainted numbers.

But I just went and looked in the ini for 2.886, this is what I found:

Code: Select all

   tpsADC           = { tps*10.23 }, "ADC" ; Fake for calibrator and file indexing.

It looks like tpsADC is just based on percent * 10.23??? I'll have to look into what MegaTune is doing here. It may be using the the currently stored min and max to reverse calculate the REAL value.

Thanks!

Just went out and checked the realtime display page in TS and sure enough the TPS adc values range from 0 to 1024 so this is definitely not a true representation of the actual adc values. The percentages are all correct however. I also checked in megatune and they don't have a guage or any other display that shows the TPS adc realtime, its all in percentage, however the "get" adc values in megatune due report correct adc equivalent voltages, TS does not. I can see the above equation 0% = 0 adc and 100% = 1023 adc, just a fake to give total adc range? not sure why though. Thanks for the help here.

Mike

[LT401Vette]

I see in the MSIi Extra ini they commented out the fake tpsADC and added one in the OutputChannels....
So I can see how you can easily reverse calculate for MSII, but that may not be consistent with MS2 Extra

tpsADC = scalar, U16, 86, "ADC", 1, 0 ; REAL for calibrator and file indexing.

I wouldn't want that sort of logic in the application code anyway, it should be part of the fake tpsADC formula.

I'll have to check both firmwares out live tonight.