christopherrabotin / cdh

A demo of a command and data handling subsystem (software only) for Zephyr RTOS using Protobufs

cdh

A demo of a command and data handling subsystem (software only) for Zephyr RTOS using Protobufs

cdh's Issues

Subsystem and TM/TC configuration

The idea here is to be able to generate a whole C&DH subsystem from a configuration file and then use the TMs and TCs directly in the C++ code over Zephyr. Additionally, it would be good is the main of the OS could cycle through the subsystems to have each execute the commands and populate the TM stream. There's a lot of flexibility here, and it seems like code generation is the easiest approach. Hence, it may be easier to write a Python tool for this. It's important that the dev still has control over which TMs and TCs are being sent.

Telecommand for general C++

• Signed via an HMAC (or something similar for embedded systems)
• TC frame: timestamp of sending (used for signature validation plus secret key), number of TCs sent, ... more?
• TC: ID which can be masked per subsystem, optional parameter, flag for parameter, CRC, time of execution

Just have a few hardcoded demo TCs in the tests for now.

Telemetry frame for general C++

• a TM point can have different formats (and an ID especially)
• a TM point should have a checksum (cf. https://groups.google.com/forum/#!topic/protobuf/E2lpJWCtnqY -- use getBytes() ?)
• a TM frame has several TM points, a timestamp and a checksum (eventually later it should have a signature too)

Makefile for TM/TC over Zephyr

Will require Zephyr C++ sample