Minimal INI file?
Posted: Fri Apr 14, 2017 6:20 pm
I have been becoming interested in electronics hardware lately and (just for fun) have built a few things like the $15 Megasquirt dashboard that would benefit from a more friendly interface to the firmware. It seems to me that many of the things TunerStudio does are broadly in the right vein and, given that I really don't like writing GUIs, I was wondering whether I might be able to configure TunerStudio to do the work.
I have been experimenting with trimming down an existing MS2 .ini file to see what it can do without, but it's pretty huge and I suspect it would be easier to start with a minimal .ini and build up from there. Is there such a creature? Also, is there any documentation of how the .ini file is processed (e.g. how TS decides whether to use CRCs, how it decides what to interrogate from the MS at startup)?
If it's a silly idea, please say so. It all might be too hard if the tie-in with MS hardware is tight -- I don't want to port Motorola's serial monitor to other hardware -- but I thought it'd be worth checking anyway.
And, BTW, my TS/MS2 connection has been fine for several days now. Seems I just needed to post a question to solve my problem. Easy fix all round!
Have fun,
Rob.
I have been experimenting with trimming down an existing MS2 .ini file to see what it can do without, but it's pretty huge and I suspect it would be easier to start with a minimal .ini and build up from there. Is there such a creature? Also, is there any documentation of how the .ini file is processed (e.g. how TS decides whether to use CRCs, how it decides what to interrogate from the MS at startup)?
If it's a silly idea, please say so. It all might be too hard if the tie-in with MS hardware is tight -- I don't want to port Motorola's serial monitor to other hardware -- but I thought it'd be worth checking anyway.
And, BTW, my TS/MS2 connection has been fine for several days now. Seems I just needed to post a question to solve my problem. Easy fix all round!
Have fun,
Rob.