Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • M1 sys Manager is completely different M2, so we should call someone new to take over the task

  • Should define the M2 sys manager

  • Right now the sys manager passes the controller data to the AM, AM process, and output to motors

  • No interthread currently, there was an interthread doc, which didn’t determine the specific implementation – TODO: find the doc probably this one 2023-06-26: Inter-Thread Communication Discussion https://www.freertos.org/Inter-Task-Communication.html

  • SM should only init the freertos threads, and kick them to start, doing interthread comm, making decision

  • Should SM read RC input, should SM do this or TM do this?- SM for now

...

  • Need to figure out data going in and out – too confused to make progress

  • Doc:Path Management Architecture which documented the data TM is expected to receive

  • Data in is defined in the doc, M6 M7 data in are the same structure

  • M6 data out, should be 3-axis angular stuff, need to define the data structure, should be largely the one required for AM, need to minic the RC output

Driver

Data In/Out

am
m2 in

  • rc
    m2 out

  • rc

  • actuator pos
    m3 in

  • rc
    m3 out

  • rc

  • desired set points

  • current pos

  • axis pid values

pm
m6 in

  • see confluence
    m6 out

  • pitch, yaw, roll

  • mimic rc
    m7 in

  • see confluence
    m7 out

  • pitch, yaw, roll

  • mimic rc

tm

sm

  • start other managers in threads
    m2 in

  • rc
    m2 out

  • rc