Drivers

State Operations

FSM

Field Explanations:

Here you can find a short summary of some fields that may be confusing.

If a field not listed here is confusing, please contact @Khalil Damouni, @Aspen Erlandsson or @Richard and the description will be updated.

Drivers:

You MUST open the task entry to access the inner sub-table to specify functions.

Desired Effect/Outcome - This is a high level description of what you want the function to do. Here you can specify what you want the function’s parameters (any external information that the function will need from the caller to complete its operation), effect (i.e. enable battery charging), and returns (any data the function caller wants to get out of the function). Fill accordingly to specific needs.

State Operations:

Isolated/Global - Whether or not the state operation needs to interface with other MCU’s to communicate data in the process of completing its task.

Arguments + Return - This is not a specific description of data types or exact variables passed, but a high level summary of what data should be coming in and going out.

To access the non-c pseudocode you MUST open the task. You can change the programming language accordingly.

FSM:

To link the state operations associated with an FSM task, you MUST open the task and reference the required state operations in the table under additional details.

Conditions for early exit - For example if the function is follow through (sending data to earth), are there any stages of the function during which it could be interrupted by a higher priority task? (In that example perhaps once it has downlinked a single image it could be exited before downlinking any others).