Search NASA⌕ Search

SEARCH · Search NASA

Results for “spacecraft commanding”

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 505 records · Page 28
All sourcesNASA NTRSDOE OSTI
NASA NTRS1984

Performance testing of the Galileo attitude control system

Performance testing plans, procedures, and initial results for the Galileo Attitude and Articulation Control Subsystem are described. The objectives of performance testing include test bed comparisons, examining the interactions between spacecraft dynamics and controllers, and verifying the ability to tune control algorithms in flight to meet specific performance requirements. Two primary test beds are described. One, the Integration Test Laboratory, drives actual flight hardware components and support equipment with a real time computer simulation of spacecraft dynamics. The other, the Functional Simulator, is a nonreal time computer simulation with high fidelity spacecraft dynamics, including flexible appendages, fuel slosh, and simulated hardware components. Initial Functional Simulator results are presented which illustrate spacecraft response to open loop spin-up and turn commands. A closed loop sun acquisition turn is also demonstrated. Future tests for verifying performance of attitude determination, spacecraft control, and scan platform pointing functions are outlined.

Bell, C. E.↗
NASA NTRS2005

Support for User Interfaces for Distributed Systems

An extensible Java(TradeMark) software framework supports the construction and operation of graphical user interfaces (GUIs) for distributed computing systems typified by ground control systems that send commands to, and receive telemetric data from, spacecraft. Heretofore, such GUIs have been custom built for each new system at considerable expense. In contrast, the present framework affords generic capabilities that can be shared by different distributed systems. Dynamic class loading, reflection, and other run-time capabilities of the Java language and JavaBeans component architecture enable the creation of a GUI for each new distributed computing system with a minimum of custom effort. By use of this framework, GUI components in control panels and menus can send commands to a particular distributed system with a minimum of system-specific code. The framework receives, decodes, processes, and displays telemetry data; custom telemetry data handling can be added for a particular system. The framework supports saving and later restoration of users configurations of control panels and telemetry displays with a minimum of effort in writing system-specific code. GUIs constructed within this framework can be deployed in any operating system with a Java run-time environment, without recompilation or code changes.

Eychaner, Glenn↗
NASA NTRS1992

Planetary mission operations

A high-level overview is presented of the process through which the uplink segment of NASA's prospective planetary missions will be instituted; the overview is supplemented by suggestions as to how costs can be reduced. Uplink costs constitute two-thirds of the total cost of operations. Attention is given to 'sequence loading', which is a time-lagged set of commands and supporting information that is prepared on the ground and uplinked to the spacecraft's onboard computer. The sequence is the primary guide used by the spacecraft to accomplish its mission; sequences are supplemented by real-time commands that are executed upon reception from the ground.

Mclaughlin, W. I.↗
NASA NTRS2016

Human Flight to Lunar and Beyond - Re-Learning Operations Paradigms

For the first time since the Apollo era, NASA is planning on sending astronauts on flights beyond LEO. The Human Space Flight (HSF) program started with a successful initial flight in Earth orbit, in December 2014. The program will continue with two Exploration Missions (EM): EM-1 will be unmanned and EM-2, carrying astronauts, will follow. NASA established a multi-center team to address the communications, and related tacking/navigation needs. This paper will focus on the lessons learned by the team designing the architecture and operations for the missions. Many of these Beyond Earth Orbit lessons had to be re-learned, as the HSF program has operated for many years in Earth orbit. Unlike the Apollo missions that were largely tracked by a dedicated ground network, the HSF planned missions will be tracked (at distances beyond GEO) by the DSN, a network that mostly serves robotic missions. There have been surprising challenges to the DSN as unique modern human spaceflight needs stretch the experience base beyond that of tracking robotic missions in deep space. Close interaction between the DSN and the HSF community to understand the unique needs (e.g. 2-way voice) resulted in a Concept of Operations (ConOps) that leverages both the deep space robotic and the Human LEO experiences. Several examples will be used to highlight the unique challenges the team faced in establishing the communications and tracking capabilities for HSF missions beyond Earth Orbit, including: Navigation. At LEO, HSF missions can rely on GPS devices for orbit determination. For Lunar-and-beyond HSF missions, techniques such as precision 2-way and 3-way Doppler and ranging, Delta-Difference-of-range, and eventually possibly on-board navigation will be used. At the same time, HSF presents a challenge to navigators, beyond those presented by robotic missions - navigating a dynamic/"noisy" spacecraft. Impact of latency - the delay associated with Round-Trip-Light-Time (RTLT). Imagine trying to have a 2-way discussion (audio or video) with an astronaut, with a 2-3 sec or more delay inserted (for lunar distances) or 20 minutes delay (for Mars distances). Balanced communications link. For robotic missions, there has been a heavy emphasis on higher downlink data rates, e.g. bringing back science data. Higher uplink data rates were of secondary importance, as uplink was used only to send commands (and occasionally small files) to the spacecraft. The ratio of downlink-to-uplink data rates was often 10:1 or more. For HSF, a continuous forward link is established and rates for uplink and downlink are more similar.

Kenny, Edward (Ted)↗
NASA NTRS2002

Systems Architecture for Fully Autonomous Space Missions

The NASA Goddard Space Flight Center is working to develop a revolutionary new system architecture concept in support of fully autonomous missions. As part of GSFC's contribution to the New Millenium Program (NMP) Space Technology 7 Autonomy and on-Board Processing (ST7-A) Concept Definition Study, the system incorporates the latest commercial Internet and software development ideas and extends them into NASA ground and space segment architectures. The unique challenges facing the exploration of remote and inaccessible locales and the need to incorporate corresponding autonomy technologies within reasonable cost necessitate the re-thinking of traditional mission architectures. A measure of the resiliency of this architecture in its application to a broad range of future autonomy missions will depend on its effectiveness in leveraging from commercial tools developed for the personal computer and Internet markets. Specialized test stations and supporting software come to past as spacecraft take advantage of the extensive tools and research investments of billion-dollar commercial ventures. The projected improvements of the Internet and supporting infrastructure go hand-in-hand with market pressures that provide continuity in research. By taking advantage of consumer-oriented methods and processes, space-flight missions will continue to leverage on investments tailored to provide better services at reduced cost. The application of ground and space segment architectures each based on Local Area Networks (LAN), the use of personal computer-based operating systems, and the execution of activities and operations through a Wide Area Network (Internet) enable a revolution in spacecraft mission formulation, implementation, and flight operations. Hardware and software design, development, integration, test, and flight operations are all tied-in closely to a common thread that enables the smooth transitioning between program phases. The application of commercial software development techniques lays the foundation for delivery of product-oriented flight software modules and models. Software can then be readily applied to support the on-board autonomy required for mission self-management. An on-board intelligent system, based on advanced scripting languages, facilitates the mission autonomy required to offload ground system resources, and enables the spacecraft to manage itself safely through an efficient and effective process of reactive planning, science data acquisition, synthesis, and transmission to the ground. Autonomous ground systems in turn coordinate and support schedule contact times with the spacecraft. Specific autonomy software modules on-board include mission and science planners, instrument and subsystem control, and fault tolerance response software, all residing within a distributed computing environment supported through the flight LAN. Autonomy also requires the minimization of human intervention between users on the ground and the spacecraft, and hence calls for the elimination of the traditional operations control center as a funnel for data manipulation. Basic goal-oriented commands are sent directly from the user to the spacecraft through a distributed internet-based payload operations "center". The ensuing architecture calls for the use of spacecraft as point extensions on the Internet. This paper will detail the system architecture implementation chosen to enable cost-effective autonomous missions with applicability to a broad range of conditions. It will define the structure needed for implementation of such missions, including software and hardware infrastructures. The overall architecture is then laid out as a common thread in the mission life cycle from formulation through implementation and flight operations.

Esper, Jamie↗
NASA NTRS2020

Communications with Curiosity during solar conjunction

This study examines the methodology for operating and communicating with NASA's Curiosity Rover (MSL) during the 2019 solar conjunction. For MSL, solar conjunction occurs when the viewing angle between the Sun and Mars from Earth's perspective falls below 3 degrees, which occurs roughly every two Earth years and lasts for about two weeks. This presents a challenge for engineers operating a vehicle on Mars because the degraded signal to noise ratio disrupts data flow between Earth and the spacecraft. As a result, operators designate a command moratorium in which no commands are sent to the rover and instead design long-term plans that are uplinked weeks in advance (rather than the nominal case of daily uplinks). Coordinating communications with the rover leading up to and following conjunction requires negotiations with several orbiters, another lander, and the Deep Space Network (DSN) each with their own set of constraints. It is the Strategic Comm Planning T coordination, which acts as a baseline for the conjunction Comm team faced additional complications such as the arrival of two new spacecraft at Mars - Roscosmos ExoMars Trace Gas Orbiter (TGO).

Laubach, Sharon↗
NASA NTRS2015

Attitude Design for the LADEE Mission

The Lunar Atmosphere and Dust Environment Explorer (LADEE) satellite successfully completed its 148-day science investigation in a low-altitude, near-equatorial lunar orbit on April 18, 2014. The LADEE spacecraft was built, managed and operated by NASA's Ames Research Center (ARC). The Mission Operations Center (MOC) was located at Ames and was responsible for activity planning, command sequencing, trajectory and attitude design, orbit determination, and spacecraft operations. The Science Operations Center (SOC) was located at Goddard Space Flight Center and was responsible for science planning, data archiving and distribution. This paper details attitude design and operations support for the LADEE mission. LADEE's attitude design was shaped by a wide range of instrument pointing requirements that necessitated regular excursions from the baseline one revolution per orbit "Ram" attitude. Such attitude excursions were constrained by a number of flight rules levied to protect instruments from the Sun, avoid geometries that would result in simultaneous occlusion of LADEE's two star tracker heads, and maintain the spacecraft within its thermal and power operating limits. To satisfy LADEE's many attitude requirements and constraints, a set of rules and conventions was adopted to manage the complexity of this design challenge and facilitate the automation of ground software that generated pointing commands spanning multiple days of operations at a time. The resulting LADEE Flight Dynamics System (FDS) that was developed used Visual Basic scripts that generated instructions to AGI's Satellite Tool Kit (STK) in order to derive quaternion commands at regular intervals that satisfied LADEE's pointing requirements. These scripts relied heavily on the powerful "align and constrain" capability of STK's attitude module to construct LADEE's attitude profiles and the slews to get there. A description of the scripts and the attitude modeling they embodied is provided. One particular challenge analysts faced was in the design of LADEE maneuver attitudes. A flight rule requiring pre-maneuver verification of in-flight maneuver conditions by ground operators prior to burn execution resulted in the need to accommodate long periods in the maneuver attitude. This in turn complicated efforts to satisfy star tracker interference and communication constraints in lunar orbit. In response to this challenge, a graphical method was developed and used to survey candidate rotation angles about the thrust vector. This survey method is described and an example of its use on a particular LADEE maneuver is discussed. Finally, the software and methodology used to satisfy LADEE's attitude requirements are also discussed in the context of LADEE's overall activity planning effort. In particular, the way in which strategic schedules of instrument and engineering activities were translated into actual attitude profiles at the tactical level, then converted into precise quaternion commands to achieve those pointing goals is explained. In order to reduce the risk of time-consuming re-planning efforts, this process included the generation of long-term projections of constraint violation predictions for individual attitude profiles that could be used to establish keep-out time-frames for particular attitude profiles. The challenges experienced and overall efficacy of both the overall LADEE ground system and the attitude components of the Flight Dynamics System in meeting LADEE's varied pointing requirements are discussed.

LADEE↗
NASA NTRS1975

Digital computer control of a 30-cm mercury ion thruster

The major objective was to define the exact role of an onboard spacecraft computer in the control of ion thrusters. An initial computer control system with accurate high speed capability was designed, programmed, and tested with the computer as the sole control element for an operating ion thruster. The command functions and a code format for a spacecraft digital control system were established. A second computer control system was constructed to operate with these functions and format. A throttle program sequence was established and tested. A two thruster array was tested with these computer control systems and the results reported.

Low, C. A., Jr.↗
NASA NTRS1975

Digital computer control of a 30 cm mercury ion thruster

The major objective of this program was to define the exact role of an on-board spacecraft computer in the control of ion thrusters. An initial computer control system with accurate high speed capability was designed, programmed, and tested with the computer as the sole control element for an operating ion thruster. The command functions and a code format for a spacecraft digital control system were established. A second computer control system was constructed to operate with these functions and format. A throttle program sequence was established and tested. A two thruster array was tested with these computer control systems and the results reported.

Low, C. A., Jr.↗
NASA NTRS2021

NOAA-17 Break-up Engineering Investigation Board Final Report

The NOAA-17 break-up was found to be a single, localized debris event producing about100 trackable pieces; there is likely no catastrophic damage to the whole spacecraft. NOAA-17 debris is very much in family with NOAA-16 debris, and DMSP F11 and F13 are very much in family with each other and share similarities with NOAA-16 and 17; it is likely all four (“The Big Four”) share the same debris source. DMSP F13 break-up occurred simultaneous with a known battery overcharge and therefore battery rupture is most likely intermediate cause of the Big Four break-ups; this is a low confidence assessment since other debris sources cannot be definitively ruled out. No root cause was found as the NOAA-17 batteries were all confirmed to have been disconnected from the charge path as intended. Possible conditions for reconnection are all unlikely including short circuits and commanding from a “bad actor.” All related spacecraft pose a risk of similar break-ups for decades to come and are a threat to the critical 800-850 km polar orbit regime; even appropriately decommissioned spacecraft appear to be at risk. Recommendations include an update to the decommissioning procedure and consideration of further investigations and active debris removal, consistent with national policy.

Maggie Atkinson↗
NASA NTRS1978

Electronic switching spherical array antenna

This work was conducted to demonstrate the performance levels attainable with an ESSA (Electronic Switching Spherical Array) antenna by designing and testing an engineering model. The antenna was designed to satisfy general spacecraft environmental requirements and built to provide electronically commandable beam pointing capability throughout a hemisphere. Constant gain and beam shape throughout large volumetric coverage regions are the principle characteristics. The model is intended to be a prototype of a standard communications and data handling antenna for user scientific spacecraft with the Tracking and Data Relay Satellite System (TDRSS). Some additional testing was conducted to determine the feasibility of an integrated TDRSS and GPS (Global Positioning System) antenna system.

Stockton, R.↗
NASA NTRS2017

Efficient Data Generation and Publication as a Test Tool

A tool to facilitate the generation and publication of test data was created to test the individual components of a command and control system designed to launch spacecraft. Specifically, this tool was built to ensure messages are properly passed between system components. The tool can also be used to test whether the appropriate groups have access (read/write privileges) to the correct messages. The messages passed between system components take the form of unique identifiers with associated values. These identifiers are alphanumeric strings that identify the type of message and the additional parameters that are contained within the message. The values that are passed with the message depend on the identifier. The data generation tool allows for the efficient creation and publication of these messages. A configuration file can be used to set the parameters of the tool and also specify which messages to pass.

command↗
NASA NTRS1994

Apollo 11 Recovery

The Apollo 11 spacecraft is lifted from the ocean after its water landing (not shown) onto the deck of the USS Hornet. The crewmembers, Commander Neil A. Armstrong, Lunar Module Pilot Edwin E. Aldrin, Jr., and Command Module Pilot Michael Collins, are seen going from the spacecraft to the quarantine chambers. They talk to family members over the phone after their arrival at the Ellington Air Force Base. Footage shows the celebration of Armstrong's birthday and the release of the crew from quarantine.

Source record↗
NASA NTRS1974

Spacecraft control section for the improved Small Astronomy Satellite (SAS)

The upgraded spacecraft control section for the Small Astronomy Satellite is able to point its thrust axis to any direction in space; it can also spin or slow its outer body rotation to zero for star-locked pointing of side viewing experiments. A programmable telemetry system and delayed command system enhance the inherent capability of a spacecraft designed to be used for a variety of experiments, each of which can be built independently and attached just prior to final acceptance testing and launch. The design of this new spacecraft, whose first launch is scheduled for 1975, is provided in sufficient detail to permit the reader to ascertain its suitability for specific experiments. A summary of the spacecraft characteristics, project reliability requirements, and environmental test conditions are included in the appendices.

Townsend, M. R.↗
NASA NTRS1994

Time maintenance system for the BMDO MSX spacecraft

The Johns Hopkins University Applied Physics Laboratory (APL) is responsible for designing and implementing a clock maintenance system for the Ballistic Missile Defense Organizations (BMDO) Midcourse Space Experiment (MSX) spacecraft. The MSX spacecraft has an on-board clock that will be used to control execution of time-dependent commands and to time tag all science and housekeeping data received from the spacecraft. MSX mission objectives have dictated that this spacecraft time, UTC(MSX), maintain a required accuracy with respect to UTC(USNO) of +/- 10 ms with a +/- 1 ms desired accuracy. APL's atomic time standards and the downlinked spacecraft time were used to develop a time maintenance system that will estimate the current MSX clock time offset during an APL pass and make estimates of the clock's drift and aging using the offset estimates from many passes. Using this information, the clock's accuracy will be maintained by uplinking periodic clock correction commands. The resulting time maintenance system is a combination of offset measurement, command/telemetry, and mission planning hardware and computing assets. All assets provide necessary inputs for deciding when corrections to the MSX spacecraft clock must be made to maintain its required accuracy without inhibiting other mission objectives. The MSX time maintenance system is described as a whole and the clock offset measurement subsystem, a unique combination of precision time maintenance and measurement hardware controlled by a Macintosh computer, is detailed. Simulations show that the system estimates the MSX clock offset to less than+/- 33 microseconds.

Hermes, Martin J.↗
NASA NTRS1996

An Architecture to Promote the Commercialization of Space Mission Command and Control

This paper describes a command and control architecture that encompasses space mission operations centers, ground terminals, and spacecraft. This architecture is intended to promote the growth of a lucrative space mission operations command and control market through a set of open standards used by both gevernment and profit-making space mission operators.

cost efficient operations standardisation money ca↗
NASA NTRS1970

Current events

Apollo spacecraft program evolution, discussing Apollo 13 accident, command and service module modifications, oxygen tank design, mission objectives, etc

Mcdivitt, J. A.↗