Engineering topics

Connell, E. B.

Publications and source records attributed to Connell, E. B..

4 records

NASA NTRS1985

Standards for space data systems

NASA has chaired the Consultative Committee for Space Data Systems (CCSDS) for the past four years. During that time, a top-level, end-to-end reference model for space data sytems has been developed that identifies the functions anad services which must be provided by space data systems, and defines the interfaces between major functional elements. A group of definitions for standard protocols has been derived by analyzing these interfaces, and a set of detailed guidelines for space data system standards is in the final stages of negotiation among member CCSDS agencies. Two guidelines that address packet telemetry and channel coding have been approved and are being incorporated into the internal standards of member agencies. Others (packet telecommand, time code, standards data format unit) are in review within CCSDS technical panels and will soon be submitted for approval. These guidelines provide a mechanism for significant cost savings in the implementation of space data systems by allowing reuse of hardware and software for different payloads and for missions, and by enabling the substitution of new technology/higher performance elements at key points in the data system without causing major perturbations in the remainder of the system.

Connell, E. B.↗

NASA NTRS1984

Future interactive data systems

The information and control requirements of the investigator-users of future free-flying, platform-based, or Space Station-based scientific experiments are assessed, and the implications of these requirements for the design of the information systems are discussed. The principal requirements include near-real-time interaction with the payload, distributed or remote payload command and control, rapid access to quick-look data, flexibility of payload command sequences, on-demand uplink-downlink availability, system transparency, and modular design to facilitate replacement of system components. Current developments in systems architecture such as increased use of onboard microprocessors to select and preprocess data and transmit autonomous streams directly to the user, standardization of interfaces, and the NASA Tracking and Data Relay Satellite System are characterized, and block diagrams of present and future systems are provided.

Bracken, P. A.↗

NASA NTRS1983

Data system architecture considerations for a space station

The functions that a space station could serve are outlined and details of the data systems requirements are discussed. The data system design will be guided by an overall space systems plan, and will feature distributed, layered architecture, user friendliness, hierarchical control, technology transparency, standard interfaces, and automated engineering tools. The station would begin with a limited core capability and evolve to serve functions defined thereafter. The automation of the engineering tools will be necessary to permit an optimized, minimized crew to control all functions of the space station, while at the same time freeing the crew from being actively involved in maintaining the nominal life support functions of the equipment. One major criterion is that the software must be error free, while another is adaptibility to changing space station configurations and demands.

Connell, E. B.↗

NASA NTRS1983

The new standard spacecraft timecode

Time is an important parameter for space-acquired measurements, in virtue of the basing of instrument analysis on a sampled sensor time series. In addition, time provides the most efficient linkage between instrument data and externally generated ancillary parameters. Attention is presently given to the rationale and form of the standard timecode structure developed by NASA, with emphasis on the important class of binary unsegmented codes. The structure provides a mechanism for the self-documentation of timecodes, so that data users can interpret time measurement in an unambiguous manner. The binary unsegmented codes are modular and easily machine-readable; they also feature expendable resolution and ambiguity periods.

Connell, E. B.↗