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 289 records · Page 16
All sourcesNASA NTRSDOE OSTI
NASA NTRS2013

Multi-User Space Link Extension (SLE) System

The Multi-User Space (MUS) Link Extension system, a software and data system, provides Space Link Extension (SLE) users with three space data transfer services in timely, complete, and offline modes as applicable according to standards defined by the Consultative Committee for Space Data Systems (CCSDS). MUS radically reduces the schedule, cost, and risk of implementing a new SLE user system, minimizes operating costs with a lights-out approach to SLE, and is designed to require no sustaining engineering expense during its lifetime unless changes in the CCSDS SLE standards, combined with new provider implementations, force changes. No software modification to MUS needs to be made to support a new mission. Any systems engineer with Linux experience can begin testing SLE user service instances with MUS starting from a personal computer (PC) within five days. For flight operators, MUS provides a familiar-looking Web page for entering SLE configuration data received from SLE. Operators can also use the Web page to back up a space mission's entire set of up to approximately 500 SLE service instances in less than five seconds, or to restore or transfer from another system the same amount of data from a MUS backup file in about the same amount of time. Missions operate each MUS SLE service instance independently by sending it MUS directives, which are legible, plain ASCII strings. MUS directives are usually (but not necessarily) sent through a TCP-IP (Transmission Control Protocol Internet Protocol) socket from a MOC (Mission Operations Center) or POCC (Payload Operations Control Center) system, under scripted control, during "lights-out" spacecraft operation. MUS permits the flight operations team to configure independently each of its data interfaces; not only commands and telemetry, but also MUS status messages to the MOC. Interfaces can use single- or multiple-client TCP/IP server sockets, TCP/IP client sockets, temporary disk files, the system log, or standard in, standard out, or standard error as applicable. By defining MUS templates in ASCII, the flight operations team can include any MUS system variable in telemetry or command headers or footers, and/or in status messages. Data fields can be arranged within messages in different sequences, according to the mission s needs. The only constraints imposed are on the format of MUS directive strings, and some bare minimum logical requirements that must be met in order for MUS to read the mission control center's spacecraft command inputs. The MUS system imposes no limits or constraints on the numbers and combinations of missions and SLE service instances that it will support simultaneously. At any time, flight operators may add, change, delete, bind, connect, or disconnect.

Perkins, Toby↗
NASA NTRS2018

Robust, Radiation Tolerant Command and Data Handling and Power System Electronics for SmallSats

In today's budgetary environment, there is significant interest within the National Aeronautics and Space Administration (NASA) to enable small robotic science missions that can be executed faster and cheaper than previous larger missions. To help achieve this, focus has shifted from using exclusively radiation-tolerant or radiation-hardened parts to using more commercial-off-the-shelf (COTS) components for NASA small satellite missions that can last at least one year in orbit. However, there are some portions of a spacecraft's avionics, such as the Command and Data Handling (C&DH) subsystem and the Power System Electronics (PSE) that need to have a higher level of reliability that goes beyond what is attainable with currently available COTS parts. While there are a number of COTS components that can withstand a total ionizing dose (TID) of tens or hundreds of kilorads, there is still a great deal of concern about tolerance to and mitigation of single-event effects (SEE).

6U satellite↗
NASA NTRS1988

A feedback linearization approach to spacecraft control using momentum exchange devices

Recent developments in the area of nonlinear control theory have shown how coordiante changes in the state and input spaces can be used with nonlinear feedback to transform certain nonlinear ordinary differential equations into equivalent linear equations. These feedback linearization techniques are applied to resolve two problems arising in the control of spacecraft equipped with control moment gyroscopes (CMGs). The first application involves the computation of rate commands for the gimbals that rotate the individual gyroscopes to produce commanded torques on the spacecraft. The second application is to the long-term management of stored momentum in the system of control moment gyroscopes using environmental torques acting on the vehicle. An approach to distributing control effort among a group of redundant actuators is described that uses feedback linearization techniques to parameterize sets of controls which influence a specified subsystem in a desired way. The approach is adapted for use in spacecraft control with double-gimballed gyroscopes to produce an algorithm that avoids problematic gimbal configurations by approximating sets of gimbal rates that drive CMG rotors into desirable configurations. The momentum management problem is stated as a trajectory optimization problem with a nonlinear dynamical constraint. Feedback linearization and collocation are used to transform this problem into an unconstrainted nonlinear program. The approach to trajectory optimization is fast and robust. A number of examples are presented showing applications to the proposed NASA space station.

Dzielski, John Edward↗
NASA NTRS2009

Apollo Spacecraft and Saturn V Launch Vehicle Pyrotechnics/Explosive Devices

The Apollo Mission employs more than 210 pyrotechnic devices per mission.These devices are either automatic of commanded from the Apollo spacecraft systems. All devices require high reliability and safety and most are classified as either crew safety critical or mission critical. Pyrotechnic devices have a wide variety of applications including: launch escape tower separation, separation rocket ignition, parachute deployment and release and electrical circuit opening and closing. This viewgraph presentation identifies critical performance, design requirements and safety measures used to ensure quality, reliability and performance of Apollo pyrotechnic/explosive devices. The major components and functions of a typical Apollo pyrotechnic/explosive device are listed and described (initiators, cartridge assemblies, detonators, core charges). The presentation also identifies the major locations and uses for the devices on: the Command and Service Module, Lunar Module and all stages of the launch vehicle.

Interbartolo, Michael↗
NASA NTRSDate not supplied

Creating an Interface to view Multi-Spacecraft Swarm Telemetry

Distributed Spacecraft Systems are a type of multi-spacecraft mission architecture that can not only provide improved resolution, coverage, and availability of existing missions, but also enable missions that would be previously infeasible using traditional approaches. Distributed Spacecraft Autonomy (DSA) is a project developed by the National Aeronautics and Space Administration that enables distributed spacecraft systems. In previous science swarm missions, the spacecraft involved have not been able to communicate with each other without utilizing a ground station. Now that the spacecraft can perform inter-satellite communication, the spacecraft can be treated as a collective. Swarm autonomy is critical for a growing number of satellites which means novel ways of displaying swarm data needs to be implemented. Such systems introduce unique challenges to traditional approaches for command and control of these spacecraft, due to the large number of spacecraft and the complexity of the interactions between them. The ground data system for DSA addresses these challenges through the creation of a custom user interface that allows a single operator to orchestrate a multi-spacecraft swarm in a scalable way. This plenary describes the details of the autonomy demonstration being performed, the requirements of those using the interface to analyze the spacecraft telemetry to assess demonstration success, and the approach taken by the ground systems team to create an interface that satisfies these requirements. This approach involves the creation of several distinct components that correspond to the level of detail presented to the user. These components are based on conventional user roles in human-robot interaction, including supervisor, operator, and mechanic, extended to accommodate the additional overhead of coordinating actions between agents. One main feature of the interface is the listenability matrix component which will represent inter-satellite communications in a heat mapped matrix. The above work described will enable users to command and interact with the spacecraft as a collective.

human-swarm interaction↗
NASA NTRS2008

LISA Pathfinder

USA Pathfinder is a space mission dedicated to demonstrating technology for the Laser Interferometer Space Antenna (LISA). LISA is a joint ESA/NASA mission to detect low-frequency gravitational waves on the 0.0001 to 0.1 Hz frequency band. LISA is expected to observe 100's of merging massive black hole binaries out z-15, tens of thousands of close compact binary systems in the Milky Way, merging intermediate-mass black hole binaries, tens of stellar-mass black holes falling into supermassive black holes in galactic centers, and possibly other exotic sources. Several critical LISA technologies have not been demonstrated at the requisite level of performance. In spaceflight, and some fight hardware cannot be tested in a 1-g environment. Hence, the LISA Pathfinder mission is being implemented to demonstrate these critical LISA technologies in a relevant flight environment. LISA Pathfinder mimics one arm of the LISA constellation by shrinking the 5-million-kilometer armlength down to a few tens of centimeters. The experimental concept is to measure the relative separation between two test masses nominally following their own geodesics, and thereby determine the relative residual acceleration between them near 1 mHz, about a decade above the lowest frequency required by LISA. To implement such a concept, disturbances on the test masses must be kept very small by many design features, but chiefly by "drag-free" flight. A drag-free spacecraft follows a free-falling test mass which it encloses, but has no mechanical connection to. The spacecraft senses it's orientation and separation with respect to the proof mass, and its propulsion system is commanded to keep the spacecraft centered about the test mass. Thus, the spacecraft shields the test mass from most external influences, and minimizes the effect of force gradients arising from the spacecraft, and acting on the test mass. LISA Pathfinder will compare the geodesic of one test mass against that of the other. Only a metrology system based on interferometry can achieve the displacement sensitivity. Interferometers monitor the separation of both test masses with a sensitivity comparable to that required by LISA, and using the same technologies. LISA Pathfinder is scheduled to be launched in the first half of 1020 to a Lissajous orbit around the first Sun-Earth Lagrange point, L1. In addition to a complete European technology package (the LISA Technology Package, or LTP), LISA Pathfinder will also carry thrusters and software, known as ST-7, a part of NASA's New Millennium Program.

Stebbins, Robin↗
NASA NTRS2008

Automated and Adaptive Mission Planning for Orbital Express

The Orbital Express space mission was a Defense Advanced Research Projects Agency (DARPA) lead demonstration of on-orbit satellite servicing scenarios, autonomous rendezvous, fluid transfers of hydrazine propellant, and robotic arm transfers of Orbital Replacement Unit (ORU) components. Boeing's Autonomous Space Transport Robotic Operations (ASTRO) vehicle provided the servicing to the Ball Aerospace's Next Generation Serviceable Satellite (NextSat) client. For communication opportunities, operations used the high-bandwidth ground-based Air Force Satellite Control Network (AFSCN) along with the relatively low-bandwidth GEO-Synchronous space-borne Tracking and Data Relay Satellite System (TDRSS) network. Mission operations were conducted out of the RDT&E Support Complex (RSC) at the Kirtland Air Force Base in New Mexico. All mission objectives were met successfully: The first of several autonomous rendezvous was demonstrated on May 5, 2007; autonomous free-flyer capture was demonstrated on June 22, 2007; the fluid and ORU transfers throughout the mission were successful. Planning operations for the mission were conducted by a team of personnel including Flight Directors, who were responsible for verifying the steps and contacts within the procedures, the Rendezvous Planners who would compute the locations and visibilities of the spacecraft, the Scenario Resource Planners (SRPs), who were concerned with assignment of communications windows, monitoring of resources, and sending commands to the ASTRO spacecraft, and the Mission planners who would interface with the real-time operations environment, process planning products and coordinate activities with the SRP. The SRP position was staffed by JPL personnel who used the Automated Scheduling and Planning ENvironment (ASPEN) to model and enforce mission and satellite constraints. The lifecycle of a plan began three weeks outside its execution on-board. During the planning timeframe, many aspects could change the plan, causing the need for re-planning. These variable factors, ranging from shifting contact times to ground-station closures and required maintenance times, are discussed along with the flexibility of the ASPEN tool to accommodate changes to procedures and the daily or long-range plan, which contributed to the success of the mission. This paper will present an introduction to ASPEN, a more in-depth discussion on its use on the Orbital Express mission, and other relative work. A description of ground operations after the SRP deliveries were made is included, and we briefly discuss lessons learned from the planning perspective and future work.

scheduling↗
NASA NTRS1998

Smart Executives for Autonomous Spacecraft

In this article we explore the design of an executive for an autonomous spacecraft. The executive is responsible for translating high-level commands, whether they come from the ground or from an on-board planner, into the low-level commands understood directly by the spacecraft hardware.

control system autonomous spacecraft planning func↗
NASA NTRS2010

Wireless Intra-Spacecraft Communication: The Benefits and the Challenges

In this paper we present a systematic study of how intra-spacecraft wireless communication can be adopted to various subsystems of the spacecraft including C&DH (Command & Data Handling), Telecom, Power, Propulsion, and Payloads, and the interconnects between them. We discuss the advantages of intra-spacecraft wireless communication and the disadvantages and challenges and a proposal to address them.

Avionics↗
NASA NTRS1994

Autonomous mission planning and scheduling: Innovative, integrated, responsive

Autonomous mission scheduling, a new concept for NASA ground data systems, is a decentralized and distributed approach to scientific spacecraft planning, scheduling, and command management. Systems and services are provided that enable investigators to operate their own instruments. In autonomous mission scheduling, separate nodes exist for each instrument and one or more operations nodes exist for the spacecraft. Each node is responsible for its own operations which include planning, scheduling, and commanding; and for resolving conflicts with other nodes. One or more database servers accessible to all nodes enable each to share mission and science planning, scheduling, and commanding information. The architecture for autonomous mission scheduling is based upon a realistic mix of state-of-the-art and emerging technology and services, e.g., high performance individual workstations, high speed communications, client-server computing, and relational databases. The concept is particularly suited to the smaller, less complex missions of the future.

Sary, Charisse↗
NASA NTRS2009

Probabilistic Risk Assessment for Decision Making During Spacecraft Operations

Decisions made during the operational phase of a space mission often have significant and immediate consequences. Without the explicit consideration of the risks involved and their representation in a solid model, it is very likely that these risks are not considered systematically in trade studies. Wrong decisions during the operational phase of a space mission can lead to immediate system failure whereas correct decisions can help recover the system even from faulty conditions. A problem of special interest is the determination of the system fault protection strategies upon the occurrence of faults within the system. Decisions regarding the fault protection strategy also heavily rely on a correct understanding of the state of the system and an integrated risk model that represents the various possible scenarios and their respective likelihoods. Probabilistic Risk Assessment (PRA) modeling is applicable to the full lifecycle of a space mission project, from concept development to preliminary design, detailed design, development and operations. The benefits and utilities of the model, however, depend on the phase of the mission for which it is used. This is because of the difference in the key strategic decisions that support each mission phase. The focus of this paper is on describing the particular methods used for PRA modeling during the operational phase of a spacecraft by gleaning insight from recently conducted case studies on two operational Mars orbiters. During operations, the key decisions relate to the commands sent to the spacecraft for any kind of diagnostics, anomaly resolution, trajectory changes, or planning. Often, faults and failures occur in the parts of the spacecraft but are contained or mitigated before they can cause serious damage. The failure behavior of the system during operations provides valuable data for updating and adjusting the related PRA models that are built primarily based on historical failure data. The PRA models, in turn, provide insight into the effect of various faults or failures on the risk and failure drivers of the system and the likelihood of possible end case scenarios, thereby facilitating the decision making process during operations. This paper describes the process of adjusting PRA models based on observed spacecraft data, on one hand, and utilizing the models for insight into the future system behavior on the other hand. While PRA models are typically used as a decision aid during the design phase of a space mission, we advocate adjusting them based on the observed behavior of the spacecraft and utilizing them for decision support during the operations phase.

dynamic fault trees↗
NASA NTRS2012

MPST Software: MoonKommand

This software automatically processes Sally Ride Science (SRS) delivered MoonKAM camera control files (ccf) into uplink products for the GRAIL-A and GRAIL-B spacecraft as part of an education and public outreach (EPO) extension to the Grail Mission. Once properly validated and deemed safe for execution onboard the spacecraft, MoonKommand generates the command products via the Automated Sequence Processor (ASP) and generates uplink (.scmf) files for radiation to the Grail-A and/or Grail-B spacecraft. Any errors detected along the way are reported back to SRS via email. With Moon Kommand, SRS can control their EPO instrument as part of a fully automated process. Inputs are received from SRS as either image capture files (.ccficd) for new image requests, or downlink/delete files (.ccfdl) for requesting image downlink from the instrument and on-board memory management. The Moon - Kommand outputs are command and file-load (.scmf) files that will be uplinked by the Deep Space Network (DSN). Without MoonKommand software, uplink product generation for the MoonKAM instrument would be a manual process. The software is specific to the Moon - KAM instrument on the GRAIL mission. At the time of this writing, the GRAIL mission was making final preparations to begin the science phase, which was scheduled to continue until June 2012.

Kwok, John H.↗
NASA NTRS1974

Pioneer Odyssey: Encounter with a Giant

Ancient peoples, perhaps thousands of years ago, undoubtedly conceived the idea of "reaching out" to Jupiter, the largest and most brilliant of the "wandering stars." But for mankind to stretch across the half billion miles to the giant planet of the Solar System many advances in technical and organizational fields of human endeavor had to be made. Outreach to Jupiter did not become a serious possibility until the Pioneer F and G Project was formed by NASA early in 1968. And then man began to design an extension of his senses that would probe the environs of the giant of the Solar System, a truly pioneer odyssey into the virtually unknown regions beyond the orbit of Mars. In the ensuing year. a dedicated and cooperative effort of several thousand people in Govern­ment, university, and private industrial organiza­tions converted the idea into a reality. Less than twelve generations after Galileo first saw the banded disc of Jupiter and the flickering dots of its large satellites in the newly invented telescope, mankind sent a machine to make observations within that Jovian system. The two Pioneer spacecraft for the mission to Jupiter each weighed only about 570 pounds, yet carried eleven highly sophisticated instruments capable of operating unattended for many year in space. The spacecraft consumes less electrical power than a standard 100 watt lamp yet is able to accept instructions from Earth to control numerous operating modes of its scientific payload, process observations from these scientific instruments and format the observations into information usable on Earth. Even more remarkable. the space­craft transmits a radio signal of only 8 watts power - equal to a nightlight - yet the information carried by the radio signal is received back on Earth from a distance of several billion miles. The Pioneer mission could not have been a success without the special engineering, scientific and management organization created for its accomplishment. This organization was rather unique in that it first had to meet a launch date target relatively quickly and then had to function for an extremely long mission operational time, far longer than any previous mission to planets. The first task was thus to organize so that the mission could be planned and the spacecraft designed and fabricated to be ready for launch within a few weeks of a 30-month target for completion. The program also produced an organization that planned mission operations to such detail that more than 16,000 commands were transmitted flawlessly to the distant spacecraft during Jupiter encounter. And each command reached the spacecraft within one second of the planned time despite the more than 90 minutes required for the radio message to travel from Earth to the space­craft and for the spacecraft to return a confirma­tion to controllers back on Earth. The organization for Pioneer also determined the required flight path from Earth to Jupiter with such precision, and controlled the launch vehicle with such accuracy, that 21 months after launch the spacecraft was able to fly behind Jupiter's satellite lo, thereby providing the first measurement that indicated the possibility of a tenuous atmosphere about this large satellite. Finally, the Pioneer organization processed and analyzed each year sufficient information from the spacecraft to fill a book having about 3 million pages and reduced this avalanche of data from space into summaries of manageable size. And all this organization depended on people, consisted of people: the people who really made this whole mission possible. Pioneer has always depended on the dedication of many individuals from many organizations throughout the world to achieve its scientific objectives, and, as evidenced by the success of the Pioneer series, this dependence is completely justified. Relatively few individuals have an opportunity during their lives to participate in such a challenging, historic, pioneering effort; and still fewer are able to enjoy the rewards of such an activity. We who have worked on Pioneer 10 and its sister spacecraft, Pioneer 11, consider ourselves fortunate to be in both classes. For the opportunity we thank the people of the United States of America, who have supported our country's space effort and its spreading of human awareness of a vast and intriguing universe in which our own unique planet Earth is only one of myriads of worlds. This volume describing the mission to Jupiter and its results is one of the many rewards for our effort which we share with you, the reader.

Fimmel, Richard O.↗
NASA NTRS1979

Trends in the automation of planetary spacecraft

The automation of planetary spacecraft at the Jet Propulsion Laboratory (JPL) is discussed. Factors affecting the development of spacecraft automation, such as predictable and repetitive functions and narrow time-window, are analyzed. The volume of command data transmitted to the spacecraft is considered, together with an examination of 'autonomy' (executing functions without outside control) in relation to the ground command activity needed during the mission. The role of the spacecraft's growing computational power in increasing vehicle autonomy is noted.

Bird, T. H.↗
NASA NTRS2007

Automated Sequence Generation Process and Software

"Automated sequence generation" (autogen) signifies both a process and software used to automatically generate sequences of commands to operate various spacecraft. The autogen software comprises the autogen script plus the Activity Plan Generator (APGEN) program. APGEN can be used for planning missions and command sequences.

Gladden, Roy↗