Closed jbsmith-abq closed 3 years ago
We do support XTCE but not the complete set. I see a comment in the code which says variable sized strings are not supported so I'm not sure as I'm not very familiar with the standard. The best thing would be to try it out. COSMOS comes with a XTCE parser which automatically parses XTCE configuration files with a .xtce extension. It also has a tool called "xtce_converter" in the /bin directory which can convert XTCE files to COSMOS and COSMOS to XTCE.
I agree with Jason that the current answer is no. Would love a pull request to add this ;)
I would like to resurrect this idea, at least for strings. Before I do any implementation, what sort of behavior should this have? My initial idea is to set the size of a string to 0 if either TerminationChar or LeadingSize are specified. However this would only be primitive/partial support for these features. (https://public.ccsds.org/Pubs/660x1g1.pdf sections 4.3.2.2.5.5.4 and 4.3.2.2.5.5.5)
Potentially even creating another telemetry item for the LeadingSize element though at a glance it may be complicated to add an arbitrary parameter the set.
I'm not familiar with the XTCE standard but COSMOS would use a 0 length string.
Does Cosmos support XTCE Telemetry with variable-length fields?