thirdgen

iTrader: (26)

So it all started last night...I started my car up in the garage and it idled really lean. So I started a datalog, and drove it from my to my fiance's parents house. I shut the car off and then megalog viewed my datalog. I VE analyzed it and the numbers were a drastic change. Then I noticed my AFR Target Table was all different than what I had entered. So I reloaded my saved .vex file so my correct targets would be there, and I ve analyzed it again. Then I noticed that my Spark table was totally different! WTF? Anyway, I corrected everything, and reloaded it to the MS and now my car won't start, it'll just crank and crank. So I re-burned the firmware, reloaded everything, and same ****. So now my car is sitting in the driveway, unable to start. WHAT IS THE DEAL?

thirdgen

iTrader: (26)

So I just walked out to the car and I uploaded an old really shitty tuned, pretty basic, .msq. I turned the key to crank it, and the car fired right off! So at least I can drive it. Still though, HOW THE HELL DO MY TABLES CHANGE? I mean, whatever happened, happened in a way that it wouldn't even let my car kick over. Anybody else ever have issues like this?

ScottFW

iTrader: (4)

Sometimes the .msq just gets corrupted. FWIW, I usually just use the .vex table when I'm tuning VEs because it's faster to burn to the MS than a whole new .msq, but the remote possibility of file corruption is why I do also save the entire .msq.

It's only happened to me once. The car cranked but died after about 30 sec. Fortunately I was still in my driveway and not yet into the morning rush hour traffic. Somehow the warmup enrichment numbers had been corrupted such that they became warmup enleanment. In the field where it's usually at 120%, it was set to 4%. Obviously that's a file corruption thing since it normally won't let you enter anything less than 100 in those fields. Other fields can get corrupted too, including tables, or something in the engine constants so the car won't even start. Usually it can be fixed by simply reloading the most recent .msq. I haven't had any issues that required reflashing the firmware, but others have.

Joe Perez

iTrader: (8)

I'll give a +1 here.

My usual procedure when analyzing a log is to save an MSQ file out of the MS, and load both the MSQ and the log into MLV. After I'm done crunching, I export just the VEX out of MLV, and then import it directly into the appropriate screen of MT once I'm back in the car.

I almost never load a whole MSQ into MT unless I've just re-flashed the firmware or done some equally destructive process.

Using this procedure, I don't think I've ever had anything go corrupt within the MS itself.