SEARCH · Search NASA
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.
The objectives, functions, and organization of the Deep Space Network are summarized; deep space station, ground communication, and network operations control capabilities are described. The network is designed for two-way communications with unmanned spacecraft traveling approximately 16,000 km (10,000 miles) from earth to the farthest planets and to the edge of our solar system.
The objectives, functions, and organization of the Deep Space Network are summarized. Deep space station, ground communication, and network operations control capabilities are described.
The objectives, functions, and organization of the Deep Space Network are summarized; deep space station, ground communication, and network operations control capabilities are described.
The network is designed for two-way communications with unmanned spacecraft traveling approximately 16,000 km (10,000 miles) from earth to the farthest planets and to the edge of our solar system. The objectives, functions, and organization of the Deep Space Network are summarized. Deep space station, ground communication, and network operations control capabilities are described.
The objectives, functions, and organization of the Deep Space Network are summarized; deep space station, ground communication, and network operations control capabilities are described.
The objectives, functions, and organization of the Deep Space Network are summarized. Deep space station, ground communication, and network operations control capabilities are described.
The objectives, functions, and organization of the Deep Space Network are summarized; deep space station, ground communication, and network operations control capabilities are described.
The objectives, and organization of the Deep Space Network are summarized. Deep space station, ground communication, and network operations control capabilities are described.
The objectives, functions, and organization of the Deep Space Network are summarized. Deep Space Station, ground communication, and network operations control capabilities are described.
The objectives, functions, and organization of the Deep Space Network are summarized. Deep space station, ground communication, and network operations control capabilities are described.
The objectives, functions, and organization of the Deep Space Network are summarized; deep space station, ground communication, and network operations control capabilities are described.
The retrospective presentation provides technical disciplinary focus in the following technical areas: (1) integrated avionics; (2) guidance, navigation, and control; (3) aerodynamics; (4) structures; (5) life support, environmental control, and crew station; (6) ground operations; (7) propulsion and power; (8) communications and tracking; (9) mechanics and mechanical systems; and (10) thermal and contamination environments and protection systems.
The concepts and capabilities that supported ground-tended Space Station Freedom (SSF) utilization and operations are described. On-board computer control support capabilities are required, and potential approaches for computer sequencing are discussed. An integrated process which links the planning processes with the implementation and execution of the operations is required to perform continuous, long-term utilization of SSF. Payload designs that make accommodations for ground-tended operation can be supported by the operations infrastructure. The payload operations integration center and Space Station Control Center are to support continuous operations of payloads that are designed to be operated from the ground. An overall process of ground-tended payload operations which links the weekly planning and continuous ground-tended execution functions is defined.
NASDA has recently developed a new tracking and control system as a basis for future satellite mission operation. It is named type-I Space Operations and Data Systems (type-I SODS). The software of this system is separated into three parts: operation and control system, network system, and support and information system. The operation control system treats telemetry and command operations. The network system controls the communication line and ground station equipments to connect the satellite and the operation control system. The support and information system provides to other systems necessary information. JERS-1 which was launched in February of this year is the first satellite operated by type-l SODS. We explain the architecture and operation methods of this system using JERS-1 mission operations.
This presentation details the experimental design of an investigation of small unmanned aircraft system (sUAS) operations involving multiple vehicle management by a remote operator. The study is part of an ongoing effort to explore multiple vehicle control by multiple operators, i.e., the control of N vehicles by m operators (m:N operations). For this effort, NASA and collaborators have developed prototypes of a concept of operations (ConOps), roles and responsibilities (R&R) for operators and supervisors, and a ground control station (GCS), including software displays and interfaces. Participants in this study acted as the pilot-in-command of twelve aircraft flying pre-approved routes in a simulation of a food delivery operation utilizing sUAS in the San Diego, CA area. Each participant experienced four experimental trials. Twice within the course of each trial, participants were responsible for responding to a sudden, unanticipated, and high-priority contingency: an airspace restriction for sUAS operations known as a UAS Volume Reservation (UVR). Upon issuance of a UVR, pilots were expected to reroute affected vehicles around the airspace. The level of automation (LoA) and workload of the flight rerouting task were varied. The LoA was manipulated by providing reroute suggestions ("auto" condition) for aircraft or by requiring pilots to manually reroute ("manual" condition) affected vehicles. Workload was varied as a function of the number of vehicles affected by the UVR contingencies: 2 vehicles ("low workload" condition) versus 4 vehicles ("high workload" condition). Additionally, some vehicles required pilots to adjust for terrain conflicts while avoiding the UVR region. Due to the COVID-19 pandemic, in-person data collection for this study was not possible. Researchers adapted to this circumstance through the development of remote data collection protocol. Participants were able to view adapted GCS displays using the Microsoft Teams teleconferencing platform and responded to events by using a verbal protocol developed for the experiment. Using this protocol, participants provided instructions for actions to a researcher, referred to as the surrogate, to carry out on their behalf. This presentation describes the experiment design, including special details for remote data collection via a subject-surrogate configuration, and concludes with planned data analysis and results to be presented at a later date.
A seven channel physiological telemetry system was designed, constructed, and tested for a space environment to transfer physiological and voice information to and from an astronaut. Three ECG leads were monitored simultaneously, and two-way voice communication was achieved. The portable unit operated properly under ground based station (GBS) control. The major design problem was associated with the constraints of a wide bandwidth FM transmitter with crystal control combined with the tri-state logic format used. However, by using an ''indirect FM'' scheme and incorporating additional waveshaping circuits at the GBS, proper operation of the system was obtained. In the present form, the telemetry system has capability for seven channels of low level (2.5 mv peak maximum) physiological signals with bandwidths between 0.03 Hz and 100 Hz. Additional signal conditioning and modification of the instrumentation amplifier gains are required for other signals.
Ground systems operations at the National Aeronautics and Space Administration's (NASA) Payload Operations and Integration Function (POIF) is increasing, via the High Operations Tempo (HOT) initiative, its ability to support more science activities with a fourth crew member on the International Space Station (ISS). The Flight Control Team's need to support this increased crew presence mandated the need for a series of software tools to better handle the increasing pace of payload science operations. The overall need was clear from the outset, but the full scope and user experience for each tool, were not as well understood, so establishing a fixed set of initial requirements was not feasible. An Agile Software Development (ASD) paradigm takes advantage of uncertainty, and plans for it, so it was deemed the most appropriate approach to create room for exploring novel concepts, and to mount a rapid and flexible response to inevitiably changing requirements. It facilitated the need for unprecedented collaboration between the Product Team (i.e. users from the Flight Control Team) and the Development Team (i.e. POIC systems engineers, developers, testers). This is a process shift in the development, test, and release of software from one that is prescriptive to one that is adaptive, which is necessary for these tools to have longevity. The application of ASD to the product development lifecycle permitted the timely incorporation of customer feedback, and, allowed for continuous quality improvements. This resulted in a suite of tools that are efficient, user-friendly, and enable POIF ground systems to support the increasing pace of payload science operations. ASD is not as much a set of prescriptive processes as it is a shift in mindset; one that moves from planning against change, to planning for change, thereby iteratively growing software towards user-defined value.
Ground systems operations at the National Aeronautics and Space Administration's (NASA) Payload Operations and Integration Center (POIC) at Marshall Space Flight Center (MSFC) recently increased via a High Operations Tempo (HOT) initiative, in order to support more science activities with a fourth crew member on the International Space Station (ISS). The Flight Control Team's (FCT) need to support this increasing pace of payload science operations was the impetus for creating a series of new tools. While their need was clear, the full scope and user experience for each tool was not as well-understood, thus establishing a fixed set of initial requirements was not feasible. A hybridized Agile Software Development (ASD) paradigm was created to take advantage of this uncertainty, plan for it, permit the exploration of novel concepts, and also facilitate a rapid and flexible response to inevitably changing requirements. The POIC's hybridized ASD approach places preeminent focus on providing customer value through the delivery of high quality, customer-focused solutions in short timeframes. This has been successfully achieved through creating unprecedented modes of cooperation and collaboration between operations and software development teams, frequent user evaluations of the software with well-defined feedback mechanisms, increased human factors involvement, and a dedication to successful outcomes by the whole of the POIC. Since space science operations and software development are not typically so closely linked, this paper discusses an approach that offers an optimal way to provide an increased return on investment and a faster time-to-completion than traditional software development paradigms, while aiming at delivering high quality products and customer-driven value.