-
Hello, I am currently studying the functioning of EDS on cFS. I started by exploring the cFS repository and I could find several xml describing each service of cFE. I don't really understand how they are used, for example is there a tool that would allow to generate .h from the xml describing these EDS ? Thanks to this post on the github discussions of cFS : #274 (reply in thread) , I could see that there were other repositories in the NASA Github organization that mentioned EDS. Are these repositories fully integrated into cFS? If so what are their roles and where are they located in cFS ? -Ugo |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 3 replies
-
EDS is a work in progress. In the recent versions of CFE (since 6.6 IIRC), some EDS XML files describing core services are included in the source tree, however they are for reference only - they are not actually used by the build in the official GSFC releases at this time. Separate projects have developed tools to utilize these files into a more complete workflow, for instance:
There are proof-of-concepts around for all of this stuff, but it still needs some agreement around the specific details of how the cFS interfaces should be described, the toolchain implementation(s) to settle on, the build artifacts, etc. In short, its been a slow process (years in the making) but progress is gradually being made, and there seems to be some renewed community interest in getting something in place in a future release. FWIW, a project I previously worked on released the tool and cFS integration under Apache, and can be found at https://github.com/nasa/edslib and https://github.com/jphickey/cfe-eds-framework (the latter just being a combined single repo containing all sub-modules that correlates with the cFE 6.8-rc2 baseline). |
Beta Was this translation helpful? Give feedback.
-
Here's another cFS EDS reference/resource. I have a project called cFS Basecamp described in this short cFS basecamp Overview video that uses an 'App Store' approach so new cFS targets can easily be assembled. The assembly process is made possible because of EDS command and telemetry definitions coupled with app JSON initialization parameter files. I've recently started to publish cFS-based educational projects that rely on the app store. From a broader cFS EDS perspective I think a tool that converts EDS to XTCE would be beneficial so there's a standards-based path to ground systems that support XTCE. |
Beta Was this translation helpful? Give feedback.
EDS is a work in progress. In the recent versions of CFE (since 6.6 IIRC), some EDS XML files describing core services are included in the source tree, however they are for reference only - they are not actually used by the build in the official GSFC releases at this time.
Separate projects have developed tools to utilize these files into a more complete workflow, for instance: