See my thoughts below:
73,
Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software*
On Wed, Apr 19, 2023 at 2:19 PM Chris Thompson via pacsat-dev < pacsat-dev@amsat.org> wrote:
This is probably a question just for Burns but I will copy to the list so it is logged for posterity.
We need to update the task names. From the architecture design I have the following: RxTask TxTask Ax25Task UplinkTask PbTask CommandTask ConsoleTask TelemCollectionTask
In the code today we define the names here, I think: typedef enum { CurrentTaskWD=0, CANSupportWD,
Not required. We are not using CAN in pacsat
TelemetryWD,
Note: This task COLLECTS the telemetry every n seconds (4 in Fox and Golf I think)
ControlWD,
This may not be needed. In Fox and Golf it is the task that formats and downlinks (via Radio task) the telemetry. If the telemetry task just writes the telemetry into a file, then no one needs to format it differently. OTOH, if there are different modes etc like Golf and Fox, we might need something.
RadioWD,
Is this going to be the same as Rx and Tx? Maybe not needed.
CommandWD,
This may still be needed. On Fox/Golf it is send command data to decode by the Radio task. Probably something like that still required?
IdleWD, // Note used in RT
I bet this is supposed to be "NOT" rather than "NOTE". But I'd have to check. FreeRTOS DOES have an idle task. In Fox, the idle task just whacks away at the watchdog so if there is no idle time, we reboot. On RT, we may use it to check memory, but I don't know why it does not need to pay attention to the WD.
ExperimentWD,
I'm not sure we need this. Pacsat IS a payload.
CoordinateWD,
Not required. This is only for Golf where there are multiple processors. Unless we need something similar to coordinate the host and the pacsat payload.
/* Add any new tasks to watch in here. Maximum number of tasks is 9.*/ /* The nine limit is the number of bits available in the downlink */ LastWD, InterruptThd = LastWD, ConsoleTsk }WdReporters_t;
I have listed 8 tasks. We probably want the Experiment to be the 9th. But what about idle, coordinate, Interrupt, CAN? How do we fit it into 9? Or should we just assume 4 bits and have 16?
Worth a double check. THis comment (written by me no doubt) seems overly simplistic. But note that this is a bitmask, not a number. The bitmask shows which tasks have and have not kicked the watchdog. So to have 16, we need 16 bits.
73 Chris
-- Chris E. Thompson chrisethompson@gmail.com g0kla@arrl.net
pacsat-dev mailing list -- pacsat-dev@amsat.org View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org To unsubscribe send an email to pacsat-dev-leave@amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org