Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix #410, correct CCSDS Blue Book version #411

Merged
merged 1 commit into from
Oct 5, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions docs/dox_src/cfs_cf.dox
Original file line number Diff line number Diff line change
Expand Up @@ -210,7 +210,7 @@
engine is capable of transmitting and receiving a configurable number of
transactions simultaneously. The engine builds outgoing Protocol Data Units
(PDUs) and interprets the incoming PDUs. It handles all details regarding the
CFDP standard protocol which is defined in the CCSDS 727.0-B-4 Blue Book. The
CFDP standard protocol which is defined in the CCSDS 727.0-B-5 Blue Book. The
engine processes the file transactions when it is 'cycled'. The number of
engine cycles per wake up is a configuration parameter defined in the table.
At most one PDU will be sent on a single engine cycle.
Expand Down Expand Up @@ -1405,7 +1405,7 @@ CF_UnionArgs_Payload_t;
CF is currently limited by the Software Bus performance. Future work may
include implementing a point-to-point interface for high speed transfers.

The CFDP standard CCSDS 727.0-B-4 allows a variety of data-type sizes for
The CFDP standard CCSDS 727.0-B-5 allows a variety of data-type sizes for
Source and Destination Entity ID's, Transaction ID and PDU Header length.
Currently, this application does not support the following:
1. an Entity ID length other than the size defined in cf_platform_cfg.h
Expand All @@ -1432,11 +1432,11 @@ CF_UnionArgs_Payload_t;
Not Respected'.

This version of CF does not support keep alive procedures that are detailed in
section 4.1.6.5 of CFDP CCSDS 727.0-B-4 Blue Book.
section 4.1.6.5 of CFDP CCSDS 727.0-B-5 Blue Book.

Invalid file structures are not supported by this version of the CF
application. Invalid file structures are described in 4.1.6.1.1.8 of CFDP
CCSDS 727.0-B-4 Blue Book and apply only when record boundaries are respected
CCSDS 727.0-B-5 Blue Book and apply only when record boundaries are respected
(see segmentation control above).

Only transmission modes unacknowledged (class 1) and acknowledged (class 2) are
Expand Down