Best practice for interfacing between COSMOS and cFS

[stanislaw]

Hi again.

We are setting up COSMOS, cFS and the CCDD tool in parallel to understand how these tools are supposed to work together.

So far, it looks like:

• COSMOS accepts two formats: its own text format or XTCE files.
• CCDD tool has its own internal format in the PostgreSQL database but it can export / import XTCE/EDS/JSON/CSV, but not the COSMOS text files.
• The cFS apps have their TM/TC definitions in the C header files.

Is our understanding right that a typical use case for these 3 tools includes CCDD tool being in the center of graph as a primary source of truth for data from which the XTCE or COSMOS files are generated as well as the cFS' header files? Can we assume that the XTCE import/export is the recommended exchange workflow between COSMOS and cFS (via CCDD)?

Are there alternative workflows? What is the best and practical approach for working with cFS and COSMOS?

If such a best practice exists, we would be happy to explore it, document it and send a patch to the COSMOS documentation.

Thanks.

[ghost]

I don't have any experience using cFS and CCDD but at Ball we have a few database tools which generate COSMOS configurations files, header files, etc. I would assume you are correct that XTCE format is the recommended exchange with cFS. You may have some luck posting an issue over at the cFS project: https://github.com/nasa/cFS

[stanislaw]

I have opened this question on the cFS/discussions: nasa/cFS#326.

[ghost]

We have updated our website with a section about COSMOS 5 and CFS