[Sls-slp] Relevance of Annex C in CCSDS 700.0-G-3 (AOS GB)

[Andrea Modenini]

Hi Greg,
Apologies late reply.

I quickly checked Annex C. Indeed the Annex C goes across the TM and AOS books.
I believe we can extract the CVCDU RS part (with test vectors) and move it in our TM GB, since really specific to RS testing.

For the VCDU FHEC, and CRC instead I'd say better that they stay in the AOS GB, since these are specified in the AOS BB, and we can support you in updating the content with all the existing codes.

@Andrews, Kenneth S (US 332B)<mailto:kenneth.s.andrews at jpl.nasa.gov> can you provide your view?

Andrea
Ph.D. Andrea Modenini
TT&C Communications Systems Engineer
TT&C and PDT Systems & Techniques Section (TEC-EST)
RF Systems Division
European Space Agency, ESTEC
Keplerlaan 1, PO Box 299
NL-2200 AG Noordwijk, The Netherlands
andrea.modenini at esa.int<mailto:andrea.modenini at esa.int> | www.esa.int<http://www.esa.int/>
T +31 6 484 56 527

From: Kazz, Greg (US 312B) <greg.j.kazz at jpl.nasa.gov>
Sent: Wednesday, May 8, 2024 12:34 AM
To: Andrea Modenini <Andrea.Modenini at esa.int>; Andrews, Kenneth S (US 332B) <kenneth.s.andrews at jpl.nasa.gov>; Matt Cosby <matt.cosby at goonhilly.org>
Cc: Kazz, Greg (US 312B) via SLS-SLP <sls-slp at mailman.ccsds.org>; C&S WG <sls-cc at mailman.ccsds.org>
Subject: Relevance of Annex C in CCSDS 700.0-G-3 (AOS GB)

Hi Andrea & Ken,

Looking over the current AOS GB (1993), there is an Annex C entitled: "Procedures for Verifying CCSDS Encoder Implementations" consisting of:

  1.  CVCDU R-S outer code, the VCDU Header Error Control code, and the Cyclic Redundancy Code (CRC) polynomial used to generate the VCDU Error Control field.
  2.  A Reed-Solomon outer code is used to generate check symbols that are appended to a VCDU to form a CVCDU....followed by test vectors that one could use to verify these codes in their implementations.

Question - Similar to the tack the SLP WG is taking in reviewing the TC GB (CCSDS 200-G-6), vintage 1987, would it make more sense to extract Annex C from the AOS GB and place that information into the TM Sync & CC Green Book ?

So far, it appears to me that most if not the remainder of the AOS GB is out of date and not very useful to maintain as a green book anymore.

Best regards,
Greg
This message is intended only for the recipient(s) named above. It may contain proprietary information and/or protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo at esa.int).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/sls-slp/attachments/20240513/ced827b8/attachment.htm>