Search results

Valve Interface needs a MessageQueue to send msgs to Comms

Status: Open.

#21 In atomar94/Flight-Computer;

· atomar94 opened on Feb 27, 2017

Valve Interface needs to parse incoming commands and handle them accordingly

Status: Open.

#20 In atomar94/Flight-Computer;

· atomar94 opened on Feb 27, 2017

Valve needs to implement open and close api calls

Status: Open.

#19 In atomar94/Flight-Computer;

· atomar94 opened on Feb 27, 2017

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

Status: Open.

#18 In atomar94/Flight-Computer;

· atomar94 opened on Feb 27, 2017

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

Status: Open.

#17 In atomar94/Flight-Computer;

· atomar94 opened on Feb 27, 2017

The valve class needs to be able to route functionality

Status: Open.

#16 In atomar94/Flight-Computer;

· atomar94 opened on Feb 27, 2017

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

Status: Open.

#15 In atomar94/Flight-Computer;

· atomar94 opened on Feb 27, 2017

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

Status: Open.

#14 In atomar94/Flight-Computer;

· atomar94 opened on Feb 27, 2017

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

Status: Open.

#13 In atomar94/Flight-Computer;

· atomar94 opened on Feb 27, 2017

Add failure checks to syscalls

enhancement

Status: Open.

#6 In atomar94/Flight-Computer;

· atomar94 opened on Jan 4, 2017