Software design patterns - Serialization/return from passive components

64 views

Skip to first unread message

Jan Dentler

unread,

Jun 25, 2021, 12:15:24 PM6/25/21

to F´ Community Group

Hi,

I have some questions regarding Fprime communication design patterns with passive components.

The target for most space systems is to operate with mostly passive components to mitigate scheduling risks.Therefore you typically use a sequential execution pattern with normal function calls e.g. send necessary execution information and get the results back e.g. via reference. As example with a passive master component (MC) and passive slave components.

MC SC1 SC2

│ ----exec(infotosend, &returnresults)---> │ │

│ ---------------exec(infotosend, &returnresults)-------------> │

In Fprime that's an issue, as communication is serialized to be compatible with a TMTC design pattern.

Here my questions

1. Is there any reference component that shows how a port with nontrivial return values is defined in xml and connected?

2. Did anyone solve this issue by implementing a return value serialization?

3. What are your design patterns for such a simple request response interaction with passive components while keeping modularity? E.g.

MC SC1 SC2

│ -------------------exec- ------------> │ │

│ <--- setResultsInMemory--- │ │

- │

│ ------------------exec-----------------------------------> │

│ <--- setResultsInMemory----------------------- │

Thank you in advance for your inspiration!

Best regards,

Jan

Thibault FARGES

unread,

Jun 25, 2021, 2:19:29 PM6/25/21

to F´ Community Group

Hi,

Could you please ask your question again on the new GitHub conversations link here: https://github.com/nasa/fprime/discussions ?

Recently we switched to these GitHub Discussions in order to consolidate the questions on this site and make the Google Group obsolete/disliked.

Note for the group admins. Should we redirect to GitHub Discussions in the group description?