Skip to content

CFDP Implementation Rework #80

Description

@hunter-esi

The current CFDP implementation lacks many features specified by https://ccsds.org/Pubs/727x0b5e1.pdf. Now that we have access to yamcs, many of these deficiencies are becoming apparent:

  • The directory listing request (read the contents of the directory) is broken at least upstream.
  • Proxy put requests may be accompanied by additional metadata receive indications that indicate transmission mode, etc. There is an interim solution for the transmission requests, but the code should be modified to comprehend this concept, and support all possible indications.
  • CFDPuserbase only allows a single vfs, meaning that no files can be downloaded from the fread cache.

This is a non exhaustive list, as I am sure there are more unsupported features that I have not discovered.

Metadata

Metadata

Assignees

Labels

tech-debtAn item that tracks technical debt that will need refactoring.upstream-contribA task that tracks work that will need to be pushed upstream to another project.

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions