Simple System Manager Arch Thought Process

This page will be a rough draft which lists the info for me to understand the System Manager and help on building the architecture document for the simple SM

What is System Manager?

SM is the most high-level software in ZP3 which decides how to properly coordinate the other managers such that the drone can fly under the control.

List of Features:

  • not necessarily a state machine, a linear loop may work better

  • with methods under a class object for encapsulation purposes

  • it is procedural instead of multithreading

  • it does input/output

  • it doesn’t manage individual managers, instead, it talks to ardupoilt for what it needs

  • generally, decide what to do next

Problems:

  • does it have any freeRTOS features? - it has?

  • Are IO separately managed by SM? what are the IOs - ppm mavlink

  • a linear loop that calls everything we may need but we grab the data we need for the algorithm can really simplify the SM - yes

  • we may need the states to indicate the managers activated (with PM/without PM) - always without PM because PM is replaced by ardupoilt