This commit is contained in:
parent
c153276454
commit
df90c22fef
@ -1,16 +1,16 @@
|
||||
# Communication with sat-rs based software
|
||||
|
||||
Communication is a huge topic for satellites. These systems are usually not (directly) connected
|
||||
Communication is a huge topic for space systems. They are usually not (directly) connected
|
||||
to the internet and only have 1-2 communication links during nominal operation. However, most
|
||||
satellites have internet access during development cycle. There are various standards provided by
|
||||
CCSDS and ECSS which can be useful to determine how to communicate with the satellite and the
|
||||
primary On-Board Software.
|
||||
of these systems have internet access during development cycle. There are various standards
|
||||
provided by CCSDS and ECSS which can be useful to determine how to communicate with the satellite
|
||||
and the primary On-Board Software.
|
||||
|
||||
# Application layer
|
||||
|
||||
Current communication with satellite systems is usually packet based. For example, the CCSDS space
|
||||
Most communication with space systems is usually packet based. For example, the CCSDS space
|
||||
packet standard only specifies a 6 byte header with at least 1 byte payload. The PUS packet
|
||||
standard is a subset of the space packet standard which adds some fields and a 16 bit CRC, but
|
||||
standard is a subset of the space packet standard, which adds some fields and a 16 bit CRC, but
|
||||
it is still centered around small packets. `sat-rs` provides support for these ECSS and CCSDS
|
||||
standards to also attempts to fill the gap to the internet protocol by providing the following
|
||||
components.
|
||||
|
@ -1,9 +1,9 @@
|
||||
# Framework Design
|
||||
|
||||
Satellites and space systems in general are complex systems with a wide range of requirements for
|
||||
both the hardware and the software.
|
||||
Consequently, the general design of the framework is centered around many light-weight components
|
||||
which try to impose as few restrictions as possible on how to solve certain problems.
|
||||
both the hardware and the software. Consequently, the general design of the framework is centered
|
||||
around many light-weight components which try to impose as few restrictions as possible on how to
|
||||
solve certain problems.
|
||||
|
||||
There are still a lot of common patterns and architectures across these systems where guidance
|
||||
of how to solve a problem and a common structure would still be extremely useful to avoid pitfalls
|
||||
|
@ -5,6 +5,8 @@ This book is the primary information resource for the [sat-rs framework](https:/
|
||||
in addition to the regular API documentation. It contains the following resources:
|
||||
|
||||
1. Architecture informations and consideration which would exceeds the scope of the regular API.
|
||||
2. General information on how to build On-Board Software and how `sat-rs` can help to fulfill
|
||||
the unique requirements of writing software for remote systems.
|
||||
2. A Getting-Started workshop where a small On-Board Software is built from scratch using
|
||||
sat-rs components.
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user