Modify/redesign the thruster scripting engine to build the base for future 'Mission-Scripts".
I propose to design a generic "Scripting Engine" which can be used to control the higher (mission) levels of the CLIMB OBC Software in future.
All C-Level modules will provide the 'Command-API' (currently also used by the debug UART) to be triggered. Additional we will need some sort of 'Register/WaitFor - API Events" command and some primitive control structures (IF-THEN/LOOP/..) to be available.
Scripts should be provided either from Flash (hard coded basic and emergency scripts), or from MRAM Storage.
I think we should aim for possibility to run N (~10) scripts in parallel. The engine module should provide the commands to activate/run and deactivate/stop any available scripts and also to upload new scripts (from ground station) to MRAM storage.
Details for that are T.B.D. and documented as they evolve.
Modify/redesign the thruster scripting engine to build the base for future 'Mission-Scripts".
I propose to design a generic "Scripting Engine" which can be used to control the higher (mission) levels of the CLIMB OBC Software in future.
All C-Level modules will provide the 'Command-API' (currently also used by the debug UART) to be triggered. Additional we will need some sort of 'Register/WaitFor - API Events" command and some primitive control structures (IF-THEN/LOOP/..) to be available.
Scripts should be provided either from Flash (hard coded basic and emergency scripts), or from MRAM Storage.
I think we should aim for possibility to run N (~10) scripts in parallel. The engine module should provide the commands to activate/run and deactivate/stop any available scripts and also to upload new scripts (from ground station) to MRAM storage.
Details for that are T.B.D. and documented as they evolve.