Search NASA⌕ Search

SEARCH · Search NASA

Results for “Command and Tracking”

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 793 records · Page 44
All sourcesNASA NTRSDOE OSTI
NASA NTRS2020

Pterodactyl: Control Architectures Development for Integrated Control Design of a Mechanically Deployed Entry Vehicle

The need to return high mass payloads is driving the development of a new class of vehicles, Deployable Entry Vehicles (DEV) for which feasible and optimized control architectures have not been developed. The Pterodactyl project, seeks to advance the current state-of-the-art for entry vehicles by developing a design, test, and build capability for DEVs that can be applied to various entry vehicle configurations. This paper details the efforts on the NASA-funded Pterodactyl project to investigate multiple control techniques for the Lifting Nano-ADEPT (LNA) DEV. We design and implement multiple control architectures on the LNA and evaluate their performance in achieving varying guidance commands during entry.First we present an overview of DEVs and the Lifting Nano-ADEPT (LNA), along with the physical LNA configuration that influences the different control designs. Existing state-of-the-art for entry vehicle control is primarily propulsive as reaction control systems (RCS) are widely employed. In this work, we analyze the feasibility of using both propulsive control systems such as RCS to generate moments, and non-propulsive control systems such as aerodynamic control surfaces and internal moving mass actuations to shift the LNA center of gravity and generate moments. For these diverse control systems, we design different multi-input multi-output (MIMO) state-feedback integral controllers based on linear quadratic regulator (LQR) optimal control methods. The control variables calculated by the controllers vary, depending on the control system being utilized and the outputs to track for the controller are either the (i) bank angle or the (ii) angle of attack and sideslip angle as determined by the desired guidance trajectory. The LQR control design technique allows the relative allocation of the control variables through the choice of the weighting matrices in the cost index. Thus, it is easy to (i) specify which and how much of a control variable to use, and (ii) utilize one control design for different control architectures by simply modifying the choice of the weighting matrices.By providing a comparative analysis of multiple control systems, configurations, and performance, this paper and the Pterodactyl project as a whole will help entry vehicle system designers and control systems engineers determine suitable control architectures for integration with DEVs and other entry vehicle types.

Okolo, Wendy A.↗
NASA NTRSDate not supplied

Advances in Autonomous Communications and Operations: Tes-N Series

Advances in nanosat subsystems over the past decade have taken the CubeSat standard from a communication-limited educational tool to a powerful platform enabling space research. The potential for autonomous operations may greatly increase the capability of downlinking even larger data sets. This is enabled through miniaturization of software-defined radio/cognitive communication solutions and a rapidly growing number of ground stations and satellite network crosslinks. The TechEdSat-n orbital flight series is currently demonstrating experiments using cognitive communication concepts including User Initiated Service (UIS) and High-rate Delay Tolerant Networks (HDTN), which show a significant step toward improved capability. At the core of this is the use of the Iridium L-band Short Burst Data (SBD) modems, pioneered by TES-n for space applications. SBD enables unique rapid command, control, and scheduling to initiate the UIS and HDTN protocols. This occurs by performing GPS-assisted on-orbit ephemeris determination, enabling negotiation with high bandwidth ground assets to repeatedly downlink over a specific commercial or government-owned ground station. The technique is RF band-agnostic and may be extended to higher bandwidth stations and SDRs. This may also include free-space optical communication, through both laser and omnidirectional LEDs, which can provide an attractive protocol for downlinking very large datasets over far fewer ground stations. In addition, this may be extended to lunar applications for such future concepts as LunaNet, whereby scheduling and cognitive technologies can assist in greatly improving Earth downlink capabilities with ground stations which will see greater competition for usage. Lastly, the NASA Communication Service Program (CSP), intended to eventually replace the NASA Tracking and Data Relay Satellite System (TDRSS) will also demonstrate the feasibility of commercially-provided satellite communication capabilities. All of these combined advances, including large advances in on-board computation on small platforms, will result in more remarkable data processing capability – yielding even more as of yet unknown discoveries.

Autonomy↗
NASA NTRS2008

The NASA Orbiting Carbon Observatory (OCO) Mission: Objectives, Approach, and Status

The Orbiting Carbon Observatory (OCO) is a NASA Earth System Science Pathfinder (ESSP) mission that is currently under development at the Jet Propulsion Laboratory (JPL). OCO will make global, space-based measurements of atmospheric carbon dioxide (CO2) with the precision, resolution, and coverage needed to characterize regional-scale sources and sinks of this important greenhouse gas. The observatory consists of a dedicated spacecraft bus that carries a single instrument. The bus employs single-string version of Orbital Sciences Corporation (OSC) LEOStar-2 architecture. This 3-axis stabilized bus includes a propulsion system for orbit insertion and maintenance, provides power, points the instrument, receives and processes commands from the ground, and records, stores, and downlinks science and engineering data. The OCO instrument incorporates 3 oboresighted, high resolution grating spectrometers that will make coincident measurements of reflected sunlight in near-infrared CO2 and molecular oxygen (O2) bands. The instrument was designed and manufactured by Hamilton Sundstrand (Pomona, CA), and then integrated, flight qualified, and calibrated by JPL. It is scheduled for delivery to OSC (Dulles, VA) for integration with the spacecraft bus in the spring of 2008. OCO will be launched from the Vandenberg Air Force Base on a dedicated OSC Taurus XL launch vehicle in December 2008. It will fly in formation with the Earth Observing System Afternoon Constellation, a group of satellites that files in a 98.8 minute, 705 km altitude, sun-synchronous orbit. This orbit provides coverage of the sunlit hemisphere with a 16-day ground track repeat cycle. OCO will fly approx.4 minutes ahead of the EOS Aqua platform, with an ascending nodal crossing time of approx.1:26 PM. The OCO science data will be transmitted to the NASA Ground Network Stations in Alaska and Virginia, and then transferred to the OCO Ground Data System at JPL. There, the CO2 and O2 spectra will be analyzed by the OCO Science Team to provide spatially resolved estimates of the column-averaged CO2 dry air mole fraction, XCO2. These measurements are expected to improve our understanding of the nature and processes that regulate atmospheric CO2 enabling more reliable forecasts of CO2 buildup and its impact on climate change.

global measurements↗
NASA NTRS2018

Utilizing Testing Frameworks for Launch Control Systems Continuous Integration

Command and control software is an integral part of the launch procedure. The most important part of this type of software is its ability to communicate well with the user and relay information in a correctly formatted way such that the user can understand the data. There is a tool that aides the communication between the different parts of the system, and effectively, the user. This instrument is capable of taking several complex values and ensuring that they are correctly sorted into their distinctive message values and distributed properly among the different facets of the system. This tool will easily translate and publish the data inside of messages in the system to something that is readable and understandable. The tool also allows for transmission of the recorded data to the user, effectively ensuring the communication between different components of the system. As well as keeping track of messages and ensuring that the information contained within each of them reaches the correct location, this tool has the ability to keep track of its own statistics and determine how many messages passed in were erroneous and how many were successfully transmitted. It is able to check and see what the total message failure count is when an invalid message is given, as well as the number of different messages and their respective types passed into the tool. This tool is of great value to the new Space Launch System (SLS). As such, the tool must be thoroughly tested with test cases that, although improbable, are possible, where the tool may not function properly. Testing an interface this complex is necessary to ensure mission safety and create unlikely scenarios where the tool would work as intended, and stretch its limits to test that even under the most uncommon conditions it would still continue to function. This software will be an important part of the control system for the newest spacecraft which will fly deeper into space than humans have ever travelled. It will fly beyond the moon, into deep space to Mars and perhaps set the groundwork for a manned mission even further to create more opportunities for interplanetary and even interstellar travel by humans. This mission relies heavily on software and hardware to ensure the safety of the humans that will be on board and therefore must be checked, exhausting each and every different situation, such that there is not a doubt surrounding the well-being of the humans aboard the rocket. That is why testing is such an important part of the mission. It provides evidence that the systems aboard the rocket and on the launch pad are safe.

Unit Testing↗
DOE OSTI2019

Decentralized Signal Processing and Distributed Control of Collaborative Autonomous Networks (17-ERD-101 LDRD Final Report)

Intelligent autonomous sensor networks, often comprised of large numbers of sensors, must be capable of jointly exploiting data collected at each agent in the network, and using that data to optimize their future actions towards multiple mission objectives. Centralized signal processing and optimization solutions process all data and determine all future actions at a single agent, and the resulting information and commands are disseminated back to the network. The communications bandwidth this requires and the single point of failure the central agent represents often make these solutions untenable for national security applications. In this project, several fundamental algorithms for solving both the decentralized signal processing and network optimization were developed, as well as simulation software to validate the results of these algorithms at scale. Specifically, novel algorithms for Bayesian decentralized estimation and decentralized detection and optimization based on the alternating direction method of multipliers (ADMM) were developed for autonomous sensor networks and published in the literature. The first large scale simulation of autonomous sensor networks (1000 agents) was conducted on this project, validating the performance of the developed algorithms. These algorithms and simulation tools are critical components of any decentralized autonomous network and have current and future national security applications, including distributed sensor networks for detection, estimation, and tracking problems, and large decentralized cyber-physical infrastructure such as the power grid.

42 ENGINEERING↗
NASA NTRS1972

S-band transponder experiment

The experiment which derives data from three lunar-orbiting objects, the command-service module (CSM), the lunar module (LM), and the subsatellite in the S-band is described. Each provides detailed information on the near-side lunar gravitational field. The primary emphasis is on the low-altitude (20 km) CSM data. The LM data cover a very short time span and are somewhat redundant with the CSM data. The resolution of the high-altitude (100 km) CSM data is not as great as that of the low altitude data. The low-altitude CSM and LM data coverage and the complementary coverage obtained during the Apollo 14 mission are presented. The experiment uses the same technique of gravity determination employed on the Lunar Orbiter, in the data of which the large anomalies called mascons were first observed. The data consist of variations in the spacecraft speed as measured by the Earth-based radio tracking system.

Sjogren, W. L.↗
NASA NTRS2002

Profile-Following Entry Guidance Using Linear Quadratic Regulator Theory

This paper describes one of the entry guidance concepts that is currently being tested as part of Marshall Space Flight Center's Advance Guidance and Control Project. The algorithm is of the reference profile tracking type. The reference profile consists of the reference states, range-to-go, altitude, and flight path angle, and reference controls, bank angle and angle of attack, versus energy. A linear control law using state feedback is used with energy-scheduled gains. The gains are obtained offline using Matlab's steady state linear quadratic regulator function. Lateral trajectory control is effected by performing periodic bank sign reversals based on a heading error corridor. A description and results of the AG&C test cases on which it has been tested are given. Although it is not anticipated that the algorithm will be quite as robust as algorithms with onboard trajectory re-generation capability, the results nevertheless show it to be very robust with respect to varying initial conditions and works satisfactorily even for entries from widely different orbits than that of the reference profile. Moreover, the commanded bank and angle of attack histories are very smooth, making it easier for the attitude control system to implement the guidance commands. Finally, results indicate that the guidance gains are more or less trajectory-independent which is a potentially useful property.

Dukeman, Greg A.↗
NASA NTRS2013

IT Security Support for Spaceport Command and Control System

During the fall 2013 semester, I worked at the Kennedy Space Center as an IT Security Intern in support of the Spaceport Command and Control System under the guidance of the IT Security Lead Engineer. Some of my responsibilities included assisting with security plan documentation collection, system hardware and software inventory, and malicious code and malware scanning. Throughout the semester, I had the opportunity to work on a wide range of security related projects. However, there are three projects in particular that stand out. The first project I completed was updating a large interactive spreadsheet that details the SANS Institutes Top 20 Critical Security Controls. My task was to add in all of the new commercial of the shelf (COTS) software listed on the SANS website that can be used to meet their Top 20 controls. In total, there are 153 unique security tools listed by SANS that meet one or more of their 20 controls. My second project was the creation of a database that will allow my mentor to keep track of the work done by the contractors that report to him in a more efficient manner by recording events as they occur throughout the quarter. Lastly, I expanded upon a security assessment of the Linux machines being used on center that I began last semester. To do this, I used a vulnerability and configuration tool that scans hosts remotely through the network and presents the user with an abundance of information detailing each machines configuration. The experience I gained from working on each of these projects has been invaluable, and I look forward to returning in the spring semester to continue working with the IT Security team.

computer security↗
NASA NTRS2010

Preliminary Design of the Guidance, Navigation, and Control System of the Altair Lunar Lander

Guidance, Navigation, and Control (GN&C) is the measurement and control of spacecraft position, velocity, and attitude in support of mission objectives. This paper provides an overview of a preliminary design of the GN&C system of the Lunar Lander Altair. Key functions performed by the GN&C system in various mission phases will first be described. A set of placeholder GN&C sensors that is needed to support these functions is next described. To meet Crew safety requirements, there must be high degrees of redundancy in the selected sensor configuration. Two sets of thrusters, one on the Ascent Module (AM) and the other on the Descent Module (DM), will be used by the GN&C system. The DM thrusters will be used, among other purposes, to perform course correction burns during the Trans-lunar Coast. The AM thrusters will be used, among other purposes, to perform precise angular and translational controls of the ascent module in order to dock the ascent module with Orion. Navigation is the process of measurement and control of the spacecraft's "state" (both the position and velocity vectors of the spacecraft). Tracking data from the Earth-Based Ground System (tracking antennas) as well as data from onboard optical sensors will be used to estimate the vehicle state. A driving navigation requirement is to land Altair on the Moon with a landing accuracy that is better than 1 km (radial 95%). Preliminary performance of the Altair GN&C design, relative to this and other navigation requirements, will be given. Guidance is the onboard process that uses the estimated state vector, crew inputs, and pre-computed reference trajectories to guide both the rotational and the translational motions of the spacecraft during powered flight phases. Design objectives of reference trajectories for various mission phases vary. For example, the reference trajectory for the descent "approach" phase (the last 3-4 minutes before touchdown) will sacrifice fuel utilization efficiency in order to provide landing site visibility for both the crew and the terrain hazard detection sensor system. One output of Guidance is the steering angle commands sent to the 2 degree-of-freedom (dof) gimbal actuation system of the descent engine. The engine gimbal actuation system is controlled by a Thrust Vector Control algorithm that is designed taking into account the large quantities of sloshing liquids in tanks mounted on Altair. In this early design phase of Altair, the GN&C system is described only briefly in this paper and the emphasis is on the GN&C architecture (that is still evolving). Multiple companion papers will provide details that are related to navigation, optical navigation, guidance, fuel sloshing, rendezvous and docking, machine-pilot interactions, and others. The similarities and differences of GN&C designs for Lunar and Mars landers are briefly compared.

Lee, Allan Y.↗
NASA NTRS2008

The Development of the Ares I-X Flight Test

The National Aeronautics and Space Administration (NASA) Constellation Program (CxP) has identified a series of tests to provide insight into the design and development of the Ares I Crew Launch Vehicle (CLV) and the Orion Crew Exploration Vehicle (CEV). Ares I-X was created as the first suborbital development flight test to help meet CxP objectives. The Ares I-X flight vehicle is an early operational model of Ares, with specific emphasis on Ares I and ground operation characteristics necessary to meet Ares I-X flight test objectives. Ares I-X will encompass the design and construction of an entire system that includes the Flight Test Vehicle (FTV) and associated operations. The FTV will be a test model based on the Ares I design. Select design features will be incorporated in the FTV design to emulate the operation of the CLV in order to meet the flight test objectives. The operations infrastructure and processes will be customized for Ares I-X, while still providing data to inform the developers of the launch processing system for Ares/Orion. The FTV is comprised of multiple elements and components that will be developed at different locations. The components will be delivered to the launch/assembly site, Kennedy Space Center (KSC), for assembly of the elements and components into an integrated, flight-ready, launch vehicle. The FTV will fly a prescribed trajectory in order to obtain the necessary data to meet the objectives. Ares I-X will not be commanded or controlled from the ground during flight, but the FTV will be equipped with telemetry systems, a data recording capability and a flight termination system (FTS). The in-flight part of the test includes a trajectory to simulate maximum dynamic pressure during flight and perform a stage separation representative of the CLV. The in-flight test also includes separation of the Upper Stage Simulator (USS) from the First Stage and recovery of the First Stage. The data retrieved from the flight test will be analyzed and used in the design and development of the Ares I vehicle. This paper will discuss the challenges in developing a new launch vehicle in a very short timeframe. The duration from formal Authority to Proceed to launch is 32 months with launch scheduled for April, 2009. The discussion will include changes to organizational structure, system engineering approaches, and early lessons learned for a fast tracked and highly visible project.

Ess, Robert H.↗
NASA NTRS2015

AMO EXPRESS: A Command and Control Experiment for Crew Autonomy Onboard the International Space Station

NASA is investigating a range of future human spaceflight missions, including both Mars-distance and Near Earth Object (NEO) targets. Of significant importance for these missions is the balance between crew autonomy and vehicle automation. As distance from Earth results in increasing communication delays, future crews need both the capability and authority to independently make decisions. However, small crews cannot take on all functions performed by ground today, and so vehicles must be more automated to reduce the crew workload for such missions. NASA's Advanced Exploration Systems Program funded Autonomous Mission Operations (AMO) project conducted an autonomous command and control experiment on-board the International Space Station that demonstrated single action intelligent procedures for crew command and control. The target problem was to enable crew initialization of a facility class rack with power and thermal interfaces, and involving core and payload command and telemetry processing, without support from ground controllers. This autonomous operations capability is enabling in scenarios such as initialization of a medical facility to respond to a crew medical emergency, and representative of other spacecraft autonomy challenges. The experiment was conducted using the Expedite the Processing of Experiments for Space Station (EXPRESS) rack 7, which was located in the Port 2 location within the U.S Laboratory onboard the International Space Station (ISS). Activation and deactivation of this facility is time consuming and operationally intensive, requiring coordination of three flight control positions, 47 nominal steps, 57 commands, 276 telemetry checks, and coordination of multiple ISS systems (both core and payload). Utilization of Draper Laboratory's Timeliner software, deployed on-board the ISS within the Command and Control (C&C) computers and the Payload computers, allowed development of the automated procedures specific to ISS without having to certify and employ novel software for procedure development and execution. The procedures contained the ground procedure logic and actions as possible to include fault detection and recovery capabilities. The autonomous operations concept includes a reduction of the amount of data a crew operator is required to verify during activation or de-activation, as well as integration of procedure execution status and relevant data in a single integrated display. During execution, the auto-procedures (via Timerliner) provide a step-by-step messaging paradigm and a high-level status upon termination. This messaging and high-level status is the only data generated for operator display. To enhance situational awareness of the operator, the Web-based Procedure Display (WebPD) provides a novel approach to the issues of procedure display and execution tracking. WebPD is a web based application that serves as the user interface for electronic procedure execution. It incorporates several aspects of the HTML5 standard. Procedures are written in a dialect of XML called Procedure Representation Language (PRL). WebPD tracks execution status in the procedure or procedures being displayed. WebPD aggregates and simplifies the auto-sequence execution status information, and formatted to be easily followed and understood by an operator who is not dedicated to actively monitoring the task. WebPD also provides an integrated data and control interface to pause or halt the execution in order to provide a check point of operation and to examine progress before starting the next sequence of activities. For this demonstration, the procedure was initiated and monitored from the ground. As the Timeliner sequences executed, their high-level execution status was written to PLMDM memory. This memory is read and downlinked via Ku-Band at a 1 Hz rate. The data containing the high-level execution status is de-commutated on the ground, and rebroadcast for WebPD consumption. A future demonstration will be performed onboard, with ISS astronauts initiating the operations instead of ground controllers. The AMO EXPRESS experiment demonstrated activation and de-activation of EXPRESS rack 7, providing the capability of future single button activations and deactivations of facility class racks. The experiment achieved numerous technical and operations 'firsts' for the ISS

Stetson, Howard K.↗
NASA NTRS1993

EOS ground data systems: A description and interface overview

The Earth Observing System (EOS) is planned as a space-based measurement system, earth-science research program, and data and information system (EOSDIS). It will consist of several high data rate spacecraft with multiple earth sensing instruments which provide investigators with a thorough, longterm view of the earth's environment. Up to seven spacecraft may be supported at once, either in operational, checkout, or testing phases; and the average data rate from the EOS satellites in orbit at any one time is expected to be from 18 to 60 Mbps. Providing the data processing and flight operations support for EOS will be the EOSDIS Core System (ECS). The ECS will command and control the spacecraft; process and store the EOS data; provide access to the data for years; and support researchers. The data processing aspects of the ECS consist of a collection of Distributed Active Archive Centers (DAAC's) which perform the product generation, data archive and distribution, and information management services. Flight operations aspects will be provided by the EOS Operations Center, by instrument control centers, and by widely distributed instrument support terminals. The communications and system management aspects will be provided by the EOSDIS Science Network and the System Management Center. In addition to the EOS satellite data, other data sets from earlier earth science missions are also to be added to designated DAAC's. Other ground data systems which will provide support to EOS for acquiring, transporting, processing, and distributing the transformed spacecraft data are currently being defined or are being upgraded for the EOS era. These systems include the Space Network consisting of the Tracking and Data Relay Satellite System (TDRSS), the TDRSS Ground Terminals, and the Network Control Center as well as the night Dynamics Facility, the EOS Data and Operations System, and EOS Communications. This paper briefly describes data handling by the ECS, the support data systems, their interfaces, and their roles.

Smith, Gene↗
NASA NTRS2013

Dynamics and Control of a Disordered System in Space

In this paper, we present some ideas regarding the modeling, dynamics and control aspects of granular spacecraft. Granular spacecraft are complex multibody systems composed of a spatially disordered distribution of a large number of elements, for instance a cloud of N grains in orbit, with N greater than 10(exp 3). These grains can be large (Cubesat-size) or small (mm-size), and can be active, i.e., a fully equipped vehicle capable sensing their own position and attitude, and enabled with propulsion means, or entirely passive. The ultimate objective would be to study the behavior of the single grains and of large ensembles of grains in orbit and to identify ways to guide and control the shape of a cloud composed of these grains so that it can perform a useful function in space, for instance, as an element of an optical imaging system for astrophysical applications. This concept, in which the aperture does not need to be continuous and monolithic, would increase the aperture size several times compared to large NASA observatories such as ATLAST, allowing for a true Terrestrial Planet Imager that would be able to resolve exo-planet details and do meaningful spectroscopy on distant world. In the paper, we address the modeling and autonomous operation of a distributed assembly (the cloud) of large numbers of highly miniaturized space-borne elements (the grains). A multi-scale, multi-physics model is proposed of the dynamics of the cloud in orbit, as well as a control law for cloud shape maintenance, and preliminary simulation studies yield an estimate of the computational effort, indicating a scale factor of approximately N(exp 1.4) as a function of the number of grains. A granular spacecraft can be defined as a collection of a large number of space-borne elements (in the 1000s) designed and controlled such that a desirable collective behavior emerges, either from the interactions among neighboring grains, and/or between the grains and the environment. In this paper, each grain is considered to be a highly miniaturized spacecraft which has limited size and mass, hence it has limited actuation, limited propulsive capability, limited power, limited sensing, limited communication, limited computational resources, limited range of motion, limited lifetime, and may be expendable. The modeling and dynamics of clouds of vehicles is more challenging than with conventional vehicles because we are faced with a probabilistic vehicle composed of a large number of physically disconnected vehicles. First, different scales of motion occur simultaneously in a cloud: translations and rotations of the cloud as a whole (macro-dynamics), relative rotation and translation of one cloud member with respect to another (meso-dynamics), and individual cloud member dynamics (micro-dynamics). Second, the control design needs to be tolerant of the system complexity, of the system architecture (centralized vs. decentralized large scale system control) as well as robust to un-modeled dynamics and noise sources. Figure 1, top left, shows the kinematic parameters of a 1000 element cloud in orbit. The motion of the system is described with respect to a local vertical-local horizontal (LV-LH) orbiting reference frame (x,y,z)=F(sub ORF) of origin O(sub ORF) which rotates with mean motion omega and orbital semi-major axis R(sub 0). The orbital geometry at the initial time is defined in terms of its six orbital elements, and the orbital dynamics equation for point O(sub ORF) is propagated forward in time under the influence of the gravitational field of the primary and other external perturbations, described below. The origin of this frame coincides with the initial position of the center of mass of the system, and the coordinate axes are z along the local vertical, x toward the flight direction, and y in the orbit normal direction. The assumptions we used to model the dynamics are as follows: 1) The inertial frame is fixed at Earth's center. 2) The orbiting Frame ORF follows Keplerian orbit. 3) the cloud system dynamics is referred to ORF. 4) the attitude of each grain uses the principal body frame as body fixed frame. 5) the atmosphere is assumed to be rigidly rotating with the Earth. Regarding the grains forming the cloud: 1) each grain is modeled as a rigid body; 2) a simple attitude estimator provides attitude estimates, 3) a simple guidance logic commands the position and attitude of each grain, 4) a simple local feedback controller based on PD control of local states is used to stabilize the attitude of the vehicle. Regarding the cloud: 1) the cloud as a whole is modeled as an equivalent rigid body in orbit, and 2) an associated graph establishes agent connectivity and enables coupling between modes of motion at the micro and macro scales; 3) a simple guidance and estimation logic is modeled to estimate and command the attitude of this equivalent rigid body; 4) a cloud shape maintenance controller is based on the dynamics of a stable virtual truss in the orbiting frame. Regarding the environmental perturbations acting on the cloud: 1) a non-spherical gravity field including JO (Earth's spherical field) zonal component, J2 (Earth's oblateness) and J3 zonal components is implemented; 2) atmospheric drag is modeled with an exponential model; 3) solar pressure is modeled assuming the Sun is inertially fixed; and 4) the Earth's magnetic field is model using an equivalent dipole model. The equations of motion are written in a referential system with respect to the origin of the orbiting frame and the state is propagated forward in time using an incremental predictor-corrector scheme. A representative cloud with varying number of grains is simulated to identify the limitations in computation time as the number of grains grows. We derive a control law to track a desired surface in the ORF (equivalently to maintain a reference cloud shape) by defining an error from a desired surface shape, and designing a control law that is exponentially stable and reduces the tracking error to zero. Figure 1 (top right) shows a comparison of various requirements for simulation of single spacecraft vs. granular spacecraft, indicating the high degree of complexity that needs to be taken into consideration. The ORF components of control force required by one of the grains is, for this particular case, in the micro-Newton range. However, no attempt has been made yet to reconfigure (or re-orient) the cloud configuration internally, for which forces in the milli-Newton level are expected, depending on the time required to do the reconfiguration. Figure 1, bottom, shows the computation time as a function of the number of grains, indicating an order N(exp 1.43) scaling on a 8 Gb, 1067 MHz RAM MacOSX computer with a 3.06 GHz Intel Core 2 Duo processor. With this metric, the same simulation for a system of N=1000 grains would take 5.4 hours, and 146 hours (i.e., 6 days) for a system with N=10,000 grains. Therefore, efficient ways to simulate this complex system, where not only the time scales of natural system dynamics, but also the sampling times of the Guidance, Navigation, and Control are included, remain to be explored. Additional details on the cloud modeling, dynamics, and control will be described in the paper.

simulation↗
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 NTRS2016

Spaceport Command and Control System Support Software Development

The Spaceport Command and Control System (SCCS) is a project developed and used by NASA at Kennedy Space Center in order to control and monitor the Space Launch System (SLS) at the time of its launch. One integral subteam under SCCS is the one assigned to the development of a data set building application to be used both on the launch pad and in the Launch Control Center (LCC) at the time of launch. This web application was developed in Ruby on Rails, a web framework using the Ruby object-oriented programming language, by a 15 - employee team (approx.). Because this application is such a huge undertaking with many facets and iterations, there were a few areas in which work could be more easily organized and expedited. As an intern working with this team, I was charged with the task of writing web applications that fulfilled this need, creating a virtual and highly customizable whiteboard in order to allow engineers to keep track of build iterations and their status. Additionally, I developed a knowledge capture web application wherein any engineer or contractor within SCCS could ask a question, answer an existing question, or leave a comment on any question or answer, similar to Stack Overflow.

Knowledge Transfer↗
NASA NTRS1991

Model reference adaptive control of robots

This project presents the results of controlling two types of robots using new Command Generator Tracker (CGT) based Direct Model Reference Adaptive Control (MRAC) algorithms. Two mathematical models were used to represent a single-link, flexible joint arm and a Unimation PUMA 560 arm; and these were then controlled in simulation using different MRAC algorithms. Special attention was given to the performance of the algorithms in the presence of sudden changes in the robot load. Previously used CGT based MRAC algorithms had several problems. The original algorithm that was developed guaranteed asymptotic stability only for almost strictly positive real (ASPR) plants. This condition is very restrictive, since most systems do not satisfy this assumption. Further developments to the algorithm led to an expansion of the number of plants that could be controlled, however, a steady state error was introduced in the response. These problems led to the introduction of some modifications to the algorithms so that they would be able to control a wider class of plants and at the same time would asymptotically track the reference model. This project presents the development of two algorithms that achieve the desired results and simulates the control of the two robots mentioned before. The results of the simulations are satisfactory and show that the problems stated above have been corrected in the new algorithms. In addition, the responses obtained show that the adaptively controlled processes are resistant to sudden changes in the load.

Steinvorth, Rodrigo↗
NASA NTRS1984

A flight-test and simulation evaluation of the longitudinal final approach and landing performance of an automatic system for a light wing loading STOL aircraft equipped with wing spoilers

As part of a comprehensive flight-test investigation of short takeoff and landing (STOL) operating systems for the terminal systems for the terminal area, an automatic landing system has been developed and evaluated for a light wing-loading turboprop-powered aircraft. An advanced digital avionics system performed display, navigation, guidance, and control functions for the test aircraft. Control signals were generated in order to command powered actuators for all conventional controls and for a set of symmetrically driven wing spoilers. This report describes effects of the spoiler control on longitudinal autoland (automatic landing) performance. Flight-test results, with and without spoiler control, are presented and compared with available (basically, conventional takeoff and landing) performance criteria. These comparisons are augmented by results from a comprehensive simulation of the controlled aircraft that included representations of the microwave landing system navigation errors that were encountered in flight as well as expected variations in atmospheric turbulence and wind shear. Flight-test results show that the addition of spoiler control improves the touchdown performance of the automatic landing system. Spoilers improve longitudinal touchdown and landing pitch-attitude performance, particularly in tailwind conditions. Furthermore, simulation results indicate that performance would probably be satisfactory for a wider range of atmospheric disturbances than those encountered in flight. Flight results also indicate that the addition of spoiler control during the final approach does not result in any measurable change in glidepath track performance, and results in a very small deterioration in airspeed tracking. This difference contrasts with simulations results, which indicate some improvement in glidepath tracking and no appreciable change in airspeed tracking. The modeling problem in the simulation that contributed to this discrepancy with flight was not resolved.

Brown, S. C.↗
NASA NTRS2004

Transitioning to Intel-based Linux Servers in the Payload Operations Integration Center

The MSFC Payload Operations Integration Center (POIC) is the focal point for International Space Station (ISS) payload operations. The POIC contains the facilities, hardware, software and communication interface necessary to support payload operations. ISS ground system support for processing and display of real-time spacecraft and telemetry and command data has been operational for several years. The hardware components were reaching end of life and vendor costs were increasing while ISS budgets were becoming severely constrained. Therefore it has been necessary to migrate the Unix portions of our ground systems to commodity priced Intel-based Linux servers. hardware architecture including networks, data storage, and highly available resources. This paper will concentrate on the Linux migration implementation for the software portion of our ground system. The migration began with 3.5 million lines of code running on Unix platforms with separate servers for telemetry, command, Payload information management systems, web, system control, remote server interface and databases. The Intel-based system is scheduled to be available for initial operational use by August 2004 The overall migration to Intel-based Linux servers in the control center involves changes to the This paper will address the Linux migration study approach including the proof of concept, criticality of customer buy-in and importance of beginning with POSlX compliant code. It will focus on the development approach explaining the software lifecycle. Other aspects of development will be covered including phased implementation, interim milestones and metrics measurements and reporting mechanisms. This paper will also address the testing approach covering all levels of testing including development, development integration, IV&V, user beta testing and acceptance testing. Test results including performance numbers compared with Unix servers will be included. need for a smooth transition while maintaining real-time support. An important aspect of the paper will involve challenges and lessons learned. product compatibility, implications of phasing decisions and tracking of dependencies, particularly non- software dependencies. The paper will also discuss scheduling challenges providing real-time flight support during the migration and the requirement to incorporate in the migration changes being made simultaneously for flight support. This paper will also address the deployment approach including user involvement in testing and the , This includes COTS product compatibility, implications of phasing decisions and tracking of dependencies, particularly non- software dependencies. The paper will also discuss scheduling challenges providing real-time flight support during the migration and the requirement to incorporate in the migration changes being made simultaneously for flight support.

Guillebeau, P. L.↗