FlexTrak Transceiver Downlink Model

[xszymonzur]

Model of the process of preparing and transmitting data (telemetry and mode change reports) through FlexTrack. Please see this comment for more implementation-based reflections.

In the Physical Architecture a "mock" function "Transmit data" has been created in place of "Send telemetry datapoints" and "Send mode change report". Both the "Send telemetry datapoints" and "Send mode change report" retained their functional exchanges (as they are a remainder from Logical Architecture and I wanted them to still be correctly reflected in Dataflow Views), but are not allocated to any Behaviour Components.

[ES] Commanded Mode Change Physical Scenario (as many other diagrams and FCs) had to be changed in accordance with the new model.

[RQT] OBC Subsystem Requirements has not been updated.

Please see commit messages for a full list of diagrams changed/added.

[chgio]

I forgot to mention the Interface Diagrams, but about the current one, feel free to delete it or just use it for sandboxing.

For the future, the gist of the plan I have in mind is:

• we start with making and allocating ports in the Architectures
• then we use the Interfaces to specify the data exchanged through those ports

Also, this is limited to the interfaces between Behaviour PCs (aka software components), as I cannot think of a meaning for interfaces between Node PCs representing computing hardware -- noting that those seem to be entirely separate from physical links, which are conversely very useful.

[chgio]

closing for abandonment of the FlexTrak in favour of an in-house-developed comms module based on the STM32WL55JC Nucleo Devkit. thank you very much @xszymonzur for all your great work, keeping it for docs.