What is BS EN 16603-70-41 - Telemetry and telecommand packet about ?
BS EN 16603-70-41 addresses the utilization of telecommand packet and telemetry packets for the purpose of remote monitoring and control of space craft subsystems and payloads.
BS EN 16603-70-41 defines a set of services that satisfy all the fundamental operational requirements for spacecraft monitoring and control during spacecraft integration, testing and flight operations, refer to ECSS-E-ST-70-11. It also specifies the structure and contents of the telecommand packets used to transport the requests and the telemetry packets used to transport the reports.
BS EN 16603-70-41 can be used by any mission, no matter what its domain of application, orbit or ground station coverage characteristics. However, it is not the intention that the PUS should be applied in its entirety to a given mission.
The services defined in BS EN 16603-70-41 cover a wide spectrum of operational scenarios and, for a given mission, only a subset of these services is likely to be appropriate.
Who is BS EN 16603-70-41 - Telemetry and telecommand packet for ?
BS EN 16603-70-41 on telemetry and telecommand packet is applicable to:
- Aerospace and defense industries
- Government authorities related to the space system
- Design engineers
- Manufacturers of telemetry and telecommand equipment
- Manufacturers of remote monitoring devices
Why should you use BS EN 16603-70-41 - Telemetry and telecommand packet ?
Telemetry facilitates the transmission of space-acquired data from source to user in a standardised highly automated manner.
BS EN 16603-70-41 mainly addresses the requirements that apply to the spacecraft and its components.
BS EN 16603-70-41 provides guidelines on telemetry and telecommand packet that are used for transporting the request and reports with greater efficiency.
What’s changed since the last update ?
BS EN 16603-70-41:2017 supersedes EN 14776:2004. BS EN 16603-70-41:2017 includes some technical changes with respect to EN 14776:2004. These include:
- The introduction of the PUS foundation model that has been used to produce the “standard service types” and shall be used to produce the “mission-specific service types”, i.e. Adding new service types, subservice types, message types, etc and adding capabilities to the ”standard service types”;
- Shall be used to produce the “mission services”, i.e. Creating the required services by “realizing the service types”, and inheriting all mandatory sub-services and minimum capabilities and selecting, for each service, the additional capabilities, the optional sub-services, etc and creating the service-specific definitions
