Closed blueed9696 closed 2 months ago
I think it is a liability thing. Every flight system is different and you would need to configure the app for it and make sure it is a fit for your need.
It has been our experience that RF communications is very unique from one mission to the next. Whether it is due to the transceiver hardware, multiple antennas, encryption, data rates, or how the hardware is attached to the spacecraft bus. Some efforts have been made recently to at least separate the protocol processing (e.g. - CCSDS standards) from the hardware interface but that is not always as simple as it sounds either because special operational circumstances seem to always pop up.
On Wed, Jul 24, 2024 at 12:19 PM Jaehyun Park @.***> wrote:
I'm trying to build a RF communication app and trying to reference other app codes. However, I could find the apps in this code are non flight applications.
What makes them to become a non flight purpose? Is it because it doesn't have RF system?
— Reply to this email directly, view it on GitHub https://github.com/nasa/cFS/issues/785, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKJGI2E7OJNFGU4GPGIVKETZN7HZBAVCNFSM6AAAAABLM2NFOWVHI2DSMVQWIX3LMV43ASLTON2WKOZSGQZDOOJZHA4DMNY . You are receiving this because you are subscribed to this thread.Message ID: @.***>
Closing issue. Please continue in discussions.
I'm trying to build a RF communication app and trying to reference other app codes. However, I could find the apps in cFS repository are non flight applications.
What makes them to become a non flight purpose? Is it because it doesn't have RF system?