...
Clarification on what MVP looks like
Should we really be passing stuff thru PM
Pros: prevents multiple sources of input into AM and allows PM to clear current trajectories and immediately swap to pilot control
Cons: What if PM fails, this seems out of PM scope, idk man this seems sus is there a better way
Cons/ notes from Sahil: PM shouldn't be talking to AM, instead SM should just have an if statement where depending on whether the drone is in autonomous mode or RC, it takes the instruction strict from either PM or LOS RC and passes it to AM. That way AM is only communicated to by SM and is only getting data from one source
concerns about combining all the structs into a single message
Post MVP Stuff:
replace message queues with LCM channels (seems like a better way to publish data like sensor data where only the last piece of data should be read, rather than all the data).
Also its pretty easy to implement. Only issue would be lack of support for uint16_t and uint32_t, but if this is post MVP, I have a solution, it will just take time to implement.
Thread System
Nov 27th
...
MVP
...
Communication System
...