Search NASA⌕ Search

SEARCH · Search NASA

Results for “Telecommand”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 19 records
All sourcesNASA NTRSDOE OSTI
NASA NTRS1993

The EURECA telecommanding chain: Experience with packet telecommand and telemetry systems

The European Retrieval Carrier (EURECA) was launched on its first flight on the 31st July 1992 by the Space Shuttle Atlantis. EURECA is characterized by several new on-board features, most notable Packet Telemetry and a partial implementation of Packet Telecommanding using an early version of the Command Operation Procedure (COP-1) protocol. EURECA has also very low contact time with its Ground Station, with a consequent high number of out-of-visibility onboard operations. This paper concentrates on the implementation and operational experience with the COP-1 Protocol and the effect the short ground contact time has on the design of the Commanding System. Another interesting feature is that the COP-1 is implemented at the control center rather than at the ground station. The COP-1 protocol also successfully supported the mission during the launch where commands were sent via NASCOM and the Shuttle.

Mueller, C.↗
NASA NTRS1983

Packet telemetry and packet telecommand - The new generation of spacecraft data handling techniques

Because of rising costs and reduced reliability of spacecraft and ground network hardware and software customization, standardization Packet Telemetry and Packet Telecommand concepts are emerging as viable alternatives. Autonomous packets of data, within each concept, which are created within ground and space application processes through the use of formatting techniques, are switched end-to-end through the space data network to their destination application processes through the use of standard transfer protocols. This process may result in facilitating a high degree of automation and interoperability because of completely mission-independent-designed intermediate data networks. The adoption of an international guideline for future space telemetry formatting of the Packet Telemetry concept, and the advancement of the NASA-ESA Working Group's Packet Telecommand concept to a level of maturity parallel to the of Packet Telemetry are the goals of the Consultative Committee for Space Data Systems. Both the Packet Telemetry and Packet Telecommand concepts are reviewed.

Hooke, A. J.↗
NASA NTRS1998

An Object-Oriented Interface to the CCSDS Ground Telecommand Services

The Telecommand Data Routing and Channel Services defined by the Consultative Committee for Space Data Systems (CCSDS) are flexible enough to support a myriad of commanding models. Because the standard is so broad, the traditional approach has been to implement only the portion of the standard needed by the particular spacecraft being tested/operated. Tasked with providing Telecommand Services for an entire class of spacecraft, where each spacecraft may choose any valid CCSDS commanding model, NASA Code 584 designed a common architecture capable of handling the full CCSDS protocol. The solution uses another CCSDS standard - the Standard Formatted Data Unit (SFDU) as the interface to the Telecommand Services. SFDUs provide a consistent way of labelling data objects, as well as allowing data objects to encapsulate other data objects. The resulting interface is: - Flexible: The full Data Routing and Channel Services are available via a single interface. The client (i.e. the command source) may enter commands at any layer within the protocol stack, specify any of the data aggregation or segmentation methods, and dynamically set any configuration parameter defined in the standard. - Object-oriented: Each object specifies both the data and the actions to be performed with the data. An object may contain other objects. - Expandable: New capabilities are added by defining new objects. Objects pass thru the protocol layers until they reach the applicable layer. The resulting design is: - Modular: The logic for each protocol layer is contained in a separate Application Program Interface (API). The objects used for the external interface are also used for communication between layers. - Distributable: The design can be split along any layer boundary for distribution across multiple machines. The objects ensure data consistency across platforms. This paper describes the SFDU-based interface and the resulting protocol implementation. The implementation is currently used by NASA (National Aeronautics and Space Administration) for integration & test of the microwave Anisotropy Probe (MAP) and Earth observer-I (EO-l) spacecraft. It will be used for post-launch operations of these spacecraft as well as the Imager for Magnetopause to Aurora Global Exploration (IMAGE) spacecraft.

Ray, Timothy Joseph↗
NASA NTRS1991

Consultative Committee for Space Data Systems recommendation for space data system standards: Telecommand. Part 2.1: Command operation procedures

This recommendation contains the detailed specification of the logic required to carry out the Command Operations Procedures of the Transfer Layer. The Recommendation for Telecommand--Part 2, Data Routing Service contains the standard data structures and data communication procedures used by the intermediate telecommand system layers (the Transfer and Segmentation Layers). In particular, it contains a brief description of the Command Operations Procedures (COP) within the Transfer Layer. This recommendation contains the detailed definition of the COP's in the form of state tables, along with definitions of the terms used. It is assumed that the reader of this document is familiar with the data structures and terminology of part 2. In case of conflict between the description of the COP's in part 2 and in this recommendation, the definition in this recommendation will take precedence. In particular, this document supersedes section 4.3.3.1 through 4.3.3.4 of part 2.

Source record↗
NASA NTRS1994

Experience with the EURECA Packet Telemetry and Packet Telecommand system

The European Retrieval Carrier (EURECA) was launched on its first flight on the 31st of July 1992 and retrieved on the 29th of June 1993. EURECA is characterized by several new on-board features, most notably Packet telemetry, and a partial implementation of packet telecommanding, the first ESA packetised spacecraft. Today more than one year after the retrieval the data from the EURECA mission has to a large extent been analysed and we can present some of the interesting results. This paper concentrates on the implementation and operational experience with the EURECA Packet Telemetry and Packet Telecommanding. We already discovered during the design of the ground system that the use of packet telemetry has major impact on the overall design and that processing of packet telemetry may have significant effect on the computer loading and sizing. During the mission a number of problems were identified with the on-board implementation resulting in very strange anomalous behaviors. Many of these problems directly violated basic assumptions for the design of the ground segment adding to the strange behavior. The paper shows that the design of a telemetry packet system should be flexible enough to allow a rapid configuration of the telemetry processing in order to adapt it to the new situation in case of an on-board failure. The experience gained with the EURECA mission control should be used to improve ground systems for future missions.

Sorensen, Erik Mose↗
NASA NTRS1994

The ESA standard for telemetry and telecommand packet utilisation: PUS

ESA has developed standards for packet telemetry and telecommand, which are derived from the recommendations of the Inter-Agency Consultative Committee for Space Data Systems (CCSDS). These standards are now mandatory for future ESA programs as well as for many programs currently under development. However, while these packet standards address the end-to-end transfer of telemetry and telecommand data between applications on the ground and Application Processes on-board, they leave open the internal structure or content of the packets. This paper presents the ESA Packet Utilization Standard (PUS) which addresses this very subject and, as such, serves to extend and complement the ESA packet standards. The goal of the PUS is to be applicable to future ESA missions in all application areas (Telecommunications, Science, Earth Resources, microgravity, etc.). The production of the PUS falls under the responsibility of the ESA Committee for Operations and EGSE Standards (COES).

Kaufeler, Jean-Francois↗
NASA NTRS2012

Replacing the CCSDS Telecommand Protocol with the Next Generation Uplink (NGU)

The current CCSDS Telecommand (TC) Recommendations 1-3 have essentially been in use since the early 1960s. The purpose of this paper is to propose a successor protocol to TC. The current CCSDS recommendations can only accommodate telecommand rates up to approximately 1 mbit/s. However today's spacecraft are storehouses for software including software for Field Programmable Gate Arrays (FPGA) which are rapidly replacing unique hardware systems. Changes to flight software occasionally require uplinks to deliver very large volumes of data. In the opposite direction, high rate downlink missions that use acknowledged CCSDS File Delivery Protocol (CFDP)4 will increase the uplink data rate requirements. It is calculated that a 5 mbits/s downlink could saturate a 4 kbits/s uplink with CFDP downlink responses: negative acknowledgements (NAKs), FINISHs, End-of-File (EOF), Acknowledgements (ACKs). Moreover, it is anticipated that uplink rates of 10 to 20 mbits/s will be required to support manned missions. The current TC recommendations cannot meet these new demands. Specifically, they are very tightly coupled to the Bose-Chaudhuri-Hocquenghem (BCH) code in Ref. 2. This protocol requires that an uncorrectable BCH codeword delimit the TC frame and terminate the randomization process. This method greatly limits telecom performance since only the BCH code can support the protocol. More modern techniques such as the CCSDS Low Density Parity Check (LDPC)5 codes can provide a minimum performance gain of up to 6 times higher command data rates as long as sufficient power is available in the data. This paper will describe the proposed protocol format, trade-offs, and advantages offered, along with a discussion of how reliable communications takes place at higher nominal rates.

Consultative Committee for Space Data Systems (CCS↗
NASA NTRS1985

Packet Telemetry and Packet Telecommand

Two communication protocols for telemetry and telecommand reduce amount of required hardware and software and facilitate bidirectional information exchange.

Hooke, A. J.↗
NASA NTRS1983

Standard methods for telemetry and telecommand channel coding

Recommendations being developed by the NASA-ESA Working Group (NEWG) for Space Data Systems Standardization and the Consultative Committee for Space Data Systems (CCSDS) to standardize spacecraft telemetry and command coding are characterized. The telemetry convolutional codes used by JPL, ESA, and GSFC are found to be similar but incompatible, and it is recommended that a secondary capability for the other two schemes be developed at each facility, with the GSFC scheme as the ultimate standard, a periodic convolutional interleaving procedure for use with the NASA Tracking and Data Relay Satellite, and an optional concatenation of the convolutional code with a Reed-Solomon code to achieve up to 6.8 dB of gain. The telecommand-coding approach adopted by CCSDS is based on the schemes in use at JPL and GSFC.

Macmedan, M. L.↗
NASA NTRS1985

Standard Codes for Telemetry and Telecommand

Different systems communicate and development costs reduced. Report discusses efforts to standardize telemetry and telecommand codes of various space programs. Used to detect and correct bit errors in communication channels with low signal-to-noise ratios, codes proliferated in recent years. Each coding/decoding system developed to solve specific problem, but some systems are similar and exhibit similar performance.

Macmedan, M. L.↗
NASA NTRS1987

Intermodulation interference avoidance for enhanced performance of ESA Deep Space Telecommand Systems

The performance degradation of the European Space Agency (ESA) Deep Space Telecommand receiving subsystem due to the presence of cross-modulation and ranging interference for simultaneous ranging and command operations on the Earth-to-space link is investigated. The most important result is that under imperfect carrier reference the command subcarrier and the ranging tone frequencies can be selected to suppress the cross-modulation interference and interference from the ranging channel for the specified command bit rate and ranging code component. Recommendations as to use of specific command subcarrier frequency, command bit rate, and ranging tone frequency are made for consideration in future standards systems.

Nguyen, Tien M.↗
NASA NTRS1994

Ground equipment for the support of packet telemetry and telecommand

This paper describes ground equipment for packet telemetry and telecommand which has been recently developed by industry for the European Space Agency. The architectural concept for this type of equipment is outlined and the actual implementation is presented. Focus is put on issues related to cross support and telescience as far as they affect the design of the interfaces to the users of the services provided by the equipment and to the management entities in charge of equipment control and monitoring.

Hell, Wolfgang↗
NASA NTRS2012

Replacing the CCSDS Telecommand Protocol with Next Generation Uplink

Better performing Forward Error Correction on the forward link along with adequate power in the data open an uplink operations trade space that enable missions to: Command to greater distances in deep space (increased uplink margin) Increase the size of the payload data (latency may be a factor) Provides space for the security header/trailer of the CCSDS Space Data Link Security Protocol Note: These higher rates could be used for relief of emergency communication margins/rates and not limited to improving top-end rate performance. A higher performance uplink could also reduce the requirements on flight emergency antenna size and/or the performance required from ground stations. Use of a selective repeat ARQ protocol may increase the uplink design requirements but the resultant development is deemed acceptable, due the factor of 4 to 8 potential increase in uplink data rate.

Low Density Parity Check (LDPC)↗
NASA NTRS1993

Uncorrectable sequences and telecommand

The purpose of a tail sequence for command link transmission units is to fail to decode, so that the command decoder will begin searching for the start of the next unit. A tail sequence used by several missions and recommended for this purpose by the Consultative Committee on Space Data Standards is analyzed. A single channel error can cause the sequence to decode. An alternative sequence requiring at least two channel errors before it can possibly decode is presented. (No sequence requiring more than two channel errors before it can possibly decode exists for this code.)

Ekroot, Laura↗
NASA NTRS1995

The Next Generation of Space Telemetry and Telecommand Standards

New standards for space/ground communications protocols are suggested for the following areas: a) file transfer based on the Internet, b) transport based on the Internet TCP/UDP, c) security derived from the ISO NLSP, a new space network, and a new space data link.

spacecraft communications telemetry standards tele↗
NASA NTRS1995

The Next Generation of Space Telemetry and Telecommand Standards

Standardizing the exchange of data through communications channels that connect spacecraft with their ground systems reduces costs. Efficient coding and packetization promote the automated, error-free transfer of data.

Galileo Near Infrared Mapping Spectrometer NIMS Ju↗
NASA NTRS1994

Packet utilisation definitions for the ESA XMM mission

XMM, ESA's X-Ray Multi-Mirror satellite, due for launch at the end of 1999 will be the first ESA scientific spacecraft to implement the ESA packet telecommand and telemetry standards and will be the first ESOC-controlled science mission to take advantage of the new flight control system infrastructure development (based on object-oriented design and distributed-system architecture) due for deployment in 1995. The implementation of the packet standards is well defined at packet transport level. However, the standard relevant to the application level (the ESA Packet Utilization Standard) covers a wide range of on-board 'services' applicable in varying degrees to the needs of XMM. In defining which parts of the ESA PUS to implement, the XMM project first considered the mission objectives and the derived operations concept and went on to identify a minimum set of packet definitions compatible with these aspects. This paper sets the scene as above and then describes the services needed for XMM and the telecommand and telemetry packet types necessary to support each service.

Nye, H. R.↗