Issues

• Valve Interface needs a MessageQueue to send msgs to Comms

  atomar94/Flight-Computer#21 · Filter by author atomar94 opened on Feb 27, 2017

• Valve Interface needs to parse incoming commands and handle them accordingly

  atomar94/Flight-Computer#20 · Filter by author atomar94 opened on Feb 27, 2017

• Valve needs to implement open and close api calls

  atomar94/Flight-Computer#19 · Filter by author atomar94 opened on Feb 27, 2017

• Valve Control needs to be able to open and close any vent with simple api calls

  atomar94/Flight-Computer#18 · Filter by author atomar94 opened on Feb 27, 2017

• There needs to be a consumer that writes to the network periodically with the data it just got.

  atomar94/Flight-Computer#17 · Filter by author atomar94 opened on Feb 27, 2017

• The valve class needs to be able to route functionality

  atomar94/Flight-Computer#16 · Filter by author atomar94 opened on Feb 27, 2017

• The network class needs to parse from http reqs to Queued_Msg, and vice versa

  atomar94/Flight-Computer#15 · Filter by author atomar94 opened on Feb 27, 2017

• The Comms/Network stack needs to implement all the dispatch methods

  atomar94/Flight-Computer#14 · Filter by author atomar94 opened on Feb 27, 2017

• update send-msg simulation command to support new message dispatch struct

  atomar94/Flight-Computer#13 · Filter by author atomar94 opened on Feb 27, 2017

• Add failure checks to syscalls

  enhancement
  atomar94/Flight-Computer#6 · Filter by author atomar94 opened on Jan 4, 2017