Elfering

Ive been having an issue with Tuner Studio after the program shuts down, laptop restarts etc. where the great tune that I have been driving/auto tuning and saving every time will have to go through fairly significant fuel table changes after the restart.

For example, this morning I drove into work letting VEAL do its thing on my fuel table and just like the last few drives, very few small changes were made to the table values (cell resistance set to easy). I go into work, and at some point during the day, the laptop decides to restart itself. When I get ready to go home, I boot up the laptop, open TS, choose my project and am effectively operating on what TS calls "Current Tune". If I kick on Auto tune from here and start driving, major changes start happening across the VE table which suggests to me that the "Current Tune" that is loaded is some older rough tune that it's defaulting to.

No big deal, I'll just open the tune I drove in on and saved this morning.... Load the tune, start auto tune, major fuel table changes again. Load second newest tune, same thing.

To me, this means that either:

A.) Tuner Studio is not saving my tunes (or at least my VE tables correctly)

B.) TS is not opening and referencing my tunes/saves correctly.

Does anyone have any insight to this? I hate losing a weeks worth of tuning because of a restart. Unfortunately I haven't been able to really get it to generate a difference report pop up until it's too late.

acedeuce802

iTrader: (1)

Take a screenshot of your VE map before you close it, then compare to the VE map when it's doing weird things. Maybe something like your MAT correction is way off and is causing a big change in AFR without the VE map actually changing.

Are you hitting "Apply" and "Save on ECU" when you're done autotuning?

Elfering

I hit "stop auto tune", "apply", then file save or save as. Each time I'm ready to turn the car off.

shuiend

iTrader: (24)

You need to be constantly hitting apply and save tune boxes in TS while you are running autotune.

Elfering

I do use use apply very often, almost never the save on ECU button though. If I lose 2 mins worth of tuning because the car dies etc. (never really happens) I'm not too worried. Not being able to save a tune I was just in and confidently load it 30 seconds later after closing TS is what bothers me.

Elfering

Just an update. I finally got around to uninstalling Tuner Studio/Re-installing, creating a new project and am still having the same issue. I can make changes to settings like boost control/spark settings and they will save correctly and can be reloaded but my fuel VE table changes will not or be loaded from previous saved tunes after Tuner Studio is shut down and re-opened. Any input is appreciated!

deezums

iTrader: (3)

You've verified this, with screenshots or exporting the tables or anything other than autotune? You aren't editing the fuel table in megalog viewer? You save the file, so all the red and blue numbers on the VE table turn black? If you have it set to write to the ECU and you unplug the laptop or otherwise modify the tune, you'll get a tune mismatch the next time you connect. You aren't seeing those?

I think your tuning practice is just bad, there's no reason to be running autotune so much. You're probably just retuning for different air temperatures every time you go out, and if you are using the stock MAT table I could see it shifting pretty radically from the morning to the afternoon.

Elfering

I have compared screen shots of my fuel VE table from a confirmed tune making almost no changes with cell resistance set to easy to my VE table after shutting down and reloading TS. Aside from just looking at the differences cell to cell between my screen shot and current tune, the chart full of red and blue cell changes almost immediately makes this pretty noticeable, I'm getting cell value changes of as high as ~40 in some areas immediately after.

I get difference reports for other instances like if I kill the car with auto tune still running before hitting apply, but not between the controller and TS after the restart. It seems to acknowledge my tune as "Current Tune" but then make radical changes as soon as I hit the auto tune feature. Yes, I save as, all the numbers turn black, cell change graph goes all white. I'll save 5 more instances of a good tune just so I can try and mess around with things without over writing my best tune, reboot the laptop or close/restart TS correctly and TS will want to run wild with changes compared to 1 minute ago when it didnt want to change anything.

I don't think its that I use auto tune too often. I try to get it to a place where very little cell change happens, then leave it alone. I can do that without the laptop restarting pretty easily within about a week. But when I plug it in to give it some adjustments once a month just to make sure its still happy because of changes in temperature or after moving to a new state like I just did, I absolutely shouldn't have to start from square one. Also. I can do this in the heat of the afternoon and have the same results as a morning to afternoon change.

I haven't pulled the O2 sensor for calibration in a long while, that's one of the next things on my list. Maybe TS is understanding the readings from the O2 differently after a restart than it did the first time it was opened a week before or some crap. I'm not above resorting to "because voodoo" in my understanding of this at this point.

WestfieldMX5

I'd try to uninstall and completelt delete the install map. Sometimes stuff stays behind.