Question about beta ini and .986

[preston]

I just downloaded .986.x (whatever was newest 3 days ago on the 19th).

I also downloaded the MsExtra2.10g (beta) to the MS.

Does TS have a specific ini ? I used "other" in project properties to load the ini provided for MT with the MsExtra code and MT runs fine with it.

But if I burn a tune to the MS with TS I get "could not read back page 3 (or page 1) restoring previously read bytes" and then I get corrupted warmup tables and after a few seconds the gauges go nuts. TS is displaying the ecu def as MsExtra2.1.0g even as the file is actually named megasquirt-II.ini. I tried doing different things in different ways but general result was miscommunication between TS and MS. I'm not sure, but I think I successfully loaded and connected with MT using the .msq saved by TS so that was compatible.

I read somehwere else that TS can use the same ini as MT so I'm not sure what the problem is, unless you need to build a special ini for each release even the betas ?

[LT401Vette]

The ini's are the same. Once it copies over it will show up in the drop down with the signature name, not the filename.

Is it any specific setting you are changing that is triggering this reaction? Or are you loading an msq?

What are you using for a serial connection? Real serial, or USB?

What OS are you running on?

[preston]

Windows XP with a usb to serial adapter (the radio shack one)
I had no problems running previous TS (sorry, dont' remember the rev, but 1-2 months old) and MsExtra2.0.1.
You know, I should probably roll that back - I know I have succesfully used an older version of TS with an older version of B&G2.886 and possibly with extra2.0.1, but I can't be sure what exactly. Anyway point is I have succesfully used TS before.

This time I would get a problem writing a tune. I could load TS, connect, and it seemed to have no problem reading MS, although I usually only double check the fuel, ign, and cranking pulse tables. I did not run the engine on TS for obvious reasons. When I would burn a tune I would get the error previously mentioned, and then the gauges woudl freak and at least the warmup table would be corrupted. I'm fairly sure I could hit "burn" on the tuning tables without any obvious problems but....not sure.

I'm going to the dyno tomorrow, will have to use MT, but maybe I can try again tomorrow afternoon. Although I'm not so sure about what to do as I was just doing straightforward stuff. I would have only been changing fuel, ign, or warmup tables before trying to burn a tune to the MS.
Really all I can think of is trying the even newer extra beta or falling back to 2.0.1 to see if the problem is with that beta code, but I'm reluctant to move backwards at least since I worry about the compatibility of the .msq files I'll be creating on the dyno tomorrow (I have to assume msq's are not guaranteed backwards compatible ?)

[LT401Vette]

I wouldn't roll back firmwares, I doubt that is the problem. I did make quite a few changes to the comm layer in this release.

See if this does consistently happen or if you can see what might be triggering it. Perhaps things like:
shutting off and restarting the engine,
Cranking before the progress bar gets to 100%
Comm breaks.

I'll see if I can come up with some way of reproducing it on this end.