Upgrade notes

[jsmcortina]

I have made a start on some notes to help upgraders from previous versions.

http://www.ms3efi.com/doc/upgrade.html

and I would appreciate input from our testers on the many things I have likely omitted.

James

[Tjabo]

That looks like a real good start James, I'll try to give it some more attention over the weekend.

Also I now notice I need to give the rev limiting some attention, as I didn't notice the difference!

Thad

[jsmcortina]

Also I now notice I need to give the rev limiting some attention, as I didn't notice the difference!

It hasn't changed just yet, I in the process of doing that.

James

[Tjabo]

Ah! Okay, one less thing for me to be embarrassed by. It's okay, I have many others!

[LT401Vette]

It would be nice to have links to the needed common hardware changes when upgrading. For example the change of ign driver pin when upgrading an MS1 wasted spark setup.

[jsmcortina]

Good point. I've added a note about that, but haven't put the link and page yet..
Would it be possible for TS to automatically re-scale the spark table from 2.1.x ?

James

[LT401Vette]

Would it be possible for TS to automatically re-scale the spark table from 2.1.x ?

It is possible, everything is possible , but it is not completely straight forward as it might seem with TS already doing that for vex imports.

I'll look at that today.

[LT401Vette]

Ok James... I slipped that one into tonight's release. It should scale any tables up or down and give a warning.

[LT401Vette]

The MS1 Hardware change notes are good... I didn't realize I needed to change my NOS pins and hardware... I think I finally decided to just use a different main board for the MS3..

You should be able to remove the note on having to export/import spark tables as a VEX. TS rescaling from the msq seems to be working well. TS does not identify the spark tables directly, it just rescales any 1D or 2D arrays. I can't think of any place this would be bad, but it is probably good to keep in mind.


Right now there are about 50 warnings loading a MS2Extra msq. Perhaps these should be separated out to somehow make bad ones jump out better?

A user should be connected to the unit or have already connected when they load an upgrade msq. If they loaded it offline without having ever connected to a real controller, then connect to a controller, any constants that were not defined in the msq would not have a value of 0. If you then connected to a controller, the difference report would come up. If you select use TunerStudio settings, it will write the 0's overwriting the default values.