Background Tasks and CFDP Engine in Cosmos 5

[kmgraves]

I am attempting to perform a file transfer between Cosmos5 and an embedded target using CFDP and nasa cFS.

For reference, I am working off the implementation done by OpenSatKit (originally created by Visiona) for Cosmos4

https://github.com/OpenSatKit/OpenSatKit/tree/master/cosmos/lib/cfdp https://github.com/edipovisiona/cfdp-engine

Following the setup in the Readme by Visiona there appears to be a large number of differences in the file organization and how things work between Cosmos 4 and 5.

Has integrating this engine to Cosmos5 been done elsewhere, or has something similar been done?

With all the files for the engine in my plugin's directory, I attempted to initialize the engine by adding it as a background task in the cmd_tlm_server.txt , but that seems to do nothing. So I'm wondering if there is a new way to initialize background tasks in Cosmos 5?

[jmthomas]

I don't think this has yet been ported to COSMOS 5. Note that COSMOS 5 has a plugin migration function cosmos-control.bat cosmos migrate PLUGIN -a which you can run in the COSMOS 4 configuration directory to help migrate to COSMOS 5. You can also create a plugin from scratch with cosmos-control.bat cosmos generate plugin NAME.

Also check our our Demo for ideas.

Note that background tasks have basically become microservices in COSMOS 5. We have a few examples in the Demo.