Ok, I will take a stab at this and see if I can come up with a list for tasks and for the notifications.
73 Chris
On Wed, Apr 19, 2023 at 2:55 PM Burns Fisher (AMSAT) via pacsat-dev < [email protected]> wrote:
No, they are not the same. The WD has an enum value for each task that is monitored by the watchdog (essentially all of them). The destination task list only has the tasks that we send messages to via the message facility. This typically allows one task or an interrupt to start up another task. But not all tasks need it. 73,
Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software*
On Wed, Apr 19, 2023 at 2:25 PM Chris Thompson via pacsat-dev < [email protected]> wrote:
Also note there is a second enum for InterTask notifications, which currently has this:
typedef enum { ToNone=-1, ToDownlinkControl=0, ToCommand, ToRxTask, ToTxTask, ToTelemetry, // New message destinations go above here ToCAN, ToCoordinate, NumberOfDestinations } DestinationTask;
Should this contain the same list as the WD Reports?
73 Chris
On Wed, Apr 19, 2023 at 2:19 PM Chris Thompson via pacsat-dev < [email protected]> 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, TelemetryWD, ControlWD, RadioWD, CommandWD, IdleWD, // Note used in RT ExperimentWD, CoordinateWD, /* 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?
73 Chris
-- Chris E. Thompson [email protected] [email protected]
pacsat-dev mailing list -- [email protected] View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected] To unsubscribe send an email to [email protected] Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
-- Chris E. Thompson [email protected] [email protected]
pacsat-dev mailing list -- [email protected] View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected] To unsubscribe send an email to [email protected] Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
pacsat-dev mailing list -- [email protected] View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected] To unsubscribe send an email to [email protected] Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org