I'm not seeing the "Another Program Altered the file" message. Let me know if you see it and what steps you were taking to get it. I haven't changed anything there for a while.

And I got a CRC error when trying to burn my auto tuned VE table after a restart.

Restarting VE Analyze? Like a start stop... That should only happen if the controller was power cycled or reset. After the CRC failure TS would refresh the local store with what is on the controller.

I should change that message, CRC failure isn't very informative to most users . And it almost sounds bad, well it could be but most times it is letting you know that for some reason there was a difference between what was local and what actually exists in the Controllers RAM, historically you just didn't know.So next we need to eliminate as many scenarios as possible that could create the out of sync condition. Currently the only one I know of is a reset or fast powercycle, but you know i could put in a monitor for that that re-interrogates when that happens.

Aside from a couple odd error messages from TS, I had no new problems with the new serial code on my 3 or so hours of driving the car yesterday. I still get the occasional pause in the data feed to my TS dashboard, and the a chime from the computer telling me that TS thinks there was a reset. I have several datalogs of that, I generally started a new datalog right after it happend each time so it'd be easier to go back and look at. This is an issue I've had with this computer in this car for a long time. It's either the computer, or the particular MS that I've only ever used in this car. The new serial routines don't have an impact on it.The funny messages I got in TS.. I was autotuning on my way to work, stopped for gas and stopped the autotune, but forgot to burn it before shutting the car off. When I shut the car off, I got a warning message about a configuration error and TS needing to go offline to save my MS or something.When I started back up, I got a difference report about the autotuned VE table differences. I told it to use the TS table and then I got the CRC error. It was either this error, or the last one that told me it was dumping some data to the comms log for me to pass to Phil. So there should be more details about that in there. Maybe some details about my comms dropouts too. I did turn the data rate up to Max, I had been keeping it at 15. My dropouts remained at about the same usual rate.. One chime every 15 minutes or so, sometimes I'd get two chimes near each other, it's definitely random. And usually while I'm just cruising along, no rhyme or reason to the complaints.

Yeah shoot me that TunerStudioLogFile when you get a chance. The diff report sounds fine, but I'm not sure what would have caused the crc error. It dumps the full page from both TunerStudio and the Controller to a log so I can see exactly what byte was different.

In theory, that's how TS should be handling comm problems, it backs off a notch each time it encounters and error and resumes. I remember the unfun I used to have with my gauges going bonkers when TS went out of sync. I'd just assume that the new serial protocol should help alleviate this. It'd sure be nice if it didn't ever have to throttle back, because the new comms take care of the original problem.

HI all. i' m arriving from alpha 11 , now i have installed tuner studio 1.078 .i have connection problem, goes of life often.I have usb serial cable.Have i to go to alpha 12 to solve it ?

Not necessarily. There is no reason alpha 11 should be going off line unless there is some reason in your connection. Is it going offline primarily while the engine is running? You may simply have a poorly shielded serial cable.

Alpha 12 with the new serial protocol does not fix bad serial connections, it does help insure they are detected and data is not used if corrupted.