SEARCH · Engineering Papers

Results for “command process”

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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 1,171 records · Page 65

All sources NASA NTRS DOE OSTI

DOE OSTI2018

MaDaTS: Managing Data on Tiered Storage for Scientific Workflows

Scientific workflows are processing large amounts of data through complex simulation and analysis tasks. Meanwhile, the need to minimize I/O costs on next generation systems and the evolution of new technologies (NVRAMs, SSDs etc.) is resulting in deeper storage hierarchies on High Performance Computing (HPC) systems. A multi-tiered storage hierarchy introduces complexities in workflow and data management. There is need for simple and flexible data abstractions that can allow users to seamlessly manage workflow data and tasks on HPC systems with multiple storage tiers. MaDaTS (Managing Data on Tiered Storage for Scientific Workflows) provides an API and a command-line tool that allows users to manage their workflows and data on tiered storage (Ghoshal & Ramakrishnan (2017)).

97 MATHEMATICS AND COMPUTING↗

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 NTRS2007

Flight Dynamics Performances of the MetOp A Satellite during the First Months of Operations

The 19th of October 2006 at 16:28 UTC the first MetOp satellite (MetOp A) was successfully launched from the Baykonur cosmodrome by a Soyuz/Fregat launcher. After only three days of LEOP operations, performed by ESOC, the satellite was handed over to EUMETSAT, who is since then taking care of all satellite operations. MetOp A is the first European operational satellite for meteorology flying in a Low Earth Orbit (LEO), all previous satellites operated by EUMETSAT, belonging to the METEOSAT family, being located in the Geo-stationary orbit. To ensure safe operations for a LEO satellite accurate and continuous commanding from ground of the on-board AOCS is required. That makes the operational transition at the end of the LEOP quite challenging, as the continuity of the Flight Dynamics operations is to be maintained. That means that the main functions of the Flight Dynamics have to be fully validated on-flight during the LEOP, before taking over the operational responsibility on the spacecraft, and continuously monitored during the entire mission. Due to the nature of a meteorological operational mission, very stringent requirements in terms of overall service availability (99 % of the collected data), timeliness of processing of the observation data (3 hours after sensing) and accuracy of the geo-location of the meteorological products (1 km) are to be fulfilled. That translates in tight requirements imposed to the Flight Dynamics facility (FDF) in terms of accuracy, timeliness and availability of the generated orbit and clock solutions; a detailed monitoring of the quality of these products is thus mandatory. Besides, being the accuracy of the image geo-location strongly related with the pointing performance of the platform and with the on-board timing stability, monitoring from ground of the behaviour of the on-board sensors and clock is needed. This paper presents an overview of the Flight Dynamics operations performed during the different phases of the MetOp A mission up to routine. The activities performed to validate all the Flight Dynamics functions, characterize the behaviour of the satellite and monitor the performances of the Flight Dynamics facility will be highlighted. The MetOp Flight Dynamics Operations team is led by Anders Meier Soerensen and composed by Pier Luigi Righetti, Francisco Sancho, Antimo Damiano and David Lazaro. The team is supported by Hilda Meixner, responsible for all Flight Dynamics validation activities.

Righetti, Pier Luigi↗

NASA NTRS1992

Assured crew return vehicle post landing configuration design and test

The 1991-1992 senior Mechanical and Aerospace Engineering Design class continued work on the post landing configurations for the Assured Crew Return Vehicle (ACRV) and the Emergency Egress Couch (EEC). The ACRV will be permanently docked to Space Station Freedom fulfilling NASA's commitment of Assured Crew Return Capability in the event of an accident or illness aboard Space Station Freedom. The EEC provides medical support and a transportation surface for an incapacitated crew member. The objective of the projects was to give the ACRV Project Office data to feed into their feasibility studies. Four design teams were given the task of developing models with dynamically and geometrically scaled characteristics. Groups one and two combined efforts to design a one-fifth scale model for the Apollo Command Module derivative, an on-board flotation system, and a lift attachment point system. This model was designed to test the feasibility of a rigid flotation and stabilization system and to determine the dynamics associated with lifting the vehicle during retrieval. However, due to priorities, it was not built. Group three designed a one-fifth scale model of the Johnson Space Center (JSC) benchmark configuration, the Station Crew Return Alternative Module (SCRAM) with a lift attachment point system. This model helped to determine the flotation and lifting characteristics of the SCRAM configuration. Group four designed a full scale EEC with changeable geometric and geometric and dynamic characteristics. This model provided data on the geometric characteristics of the EEC and on the placement of the CG and moment of inertia. It also gave the helicopter rescue personnel direct input to the feasibility study. Section 1 describes in detail the design of a one-fifth scale model of the Apollo Command Module Derivative (ACMD) ACRV. The objective of the ACMD Configuration Model Team was to use geometric and dynamic constraints to design a one-fifth scale working model of the Apollo Command Module Derivative (ACMD) configuration with a Lift Attachment Point (LAP) System. This model was required to incorporate a rigidly mounted flotation system and the egress system designed the previous academic year. The LAP system was to be used to determine the dynamic effects of locating the lifting points at different locations on the vehicle. The team was then to build and test the model; however, due to priorities, this did not occur. To better simulate the ACMD after a water landing, the nose cone section was removed and the deck area exposed. The areas researched during the design process were construction, center of gravity and moment of inertia, and lift attachment points.

Source record↗

NASA NTRS1999

Landsat-7 Simulation and Testing Environments

A spacecraft Attitude Control and Determination Subsystem (ACDS) is heavily dependent upon simulation throughout its entire development, implementation and ground test cycle. Engineering simulation tools are typically developed to design and analyze control systems to validate the design and software simulation tools are required to qualify the flight software. However, the need for simulation does not end here. Operating the ACDS of a spacecraft on the ground requires the simulation of spacecraft dynamics, disturbance modeling and celestial body motion. Sensor data must also be simulated and substituted for actual sensor data on the ground so that the spacecraft will respond by sending commands to the actuators as they will on orbit. And finally, the simulators is the primary training tool and test-bed for the Flight Operations Team. In this paper various ACDS simulation, developed for or used by the Landsat 7 project will be described. The paper will include a description of each tool, its unique attributes, and its role in the overall development and testing of the ACDS. Finally, a section is included which discusses how the coordinated use of these simulation tools can maximize the probability of uncovering software, hardware and operations errors during the ground test process.

Holmes, E.↗

NASA NTRS1993

Mission Operations and Command Assurance: Automating an Operations TQM Task

Mission Operations and Command Assurance (MO&CA) is a Total Quality Management (TQM) task on JPL projects to instill quality into mission operations. The mission operations environment is inherently risky because each decision made is potentially mission critical. The flight operations environment generally requires operators to make rapid critical decisions and solve problems based on limited information, while closely following standard procedures. MO&CA's primary goal is to help improve the operational reliability and reduce risk of projects during flight. To achieve this goal, automation of the MO&CA task is required. MO&CA specifically embodies the TQM principle of continuous process improvement (CPI) in which processes are continually examined and analyzed for opportunities for improvement. The second way in which MO&CA implements CPI on JPL projects is on new projects or upgrades to existing projects.

mission↗

NASA NTRS1994

Evolving software reengineering technology for the emerging innovative-competitive era

This paper reports on a multi-tool commercial/military environment combining software Domain Analysis techniques with Reusable Software and Reengineering of Legacy Software. It is based on the development of a military version for the Department of Defense (DOD). The integrated tools in the military version are: Software Specification Assistant (SSA) and Software Reengineering Environment (SRE), developed by Computer Command and Control Company (CCCC) for Naval Surface Warfare Center (NSWC) and Joint Logistics Commanders (JLC), and the Advanced Research Project Agency (ARPA) STARS Software Engineering Environment (SEE) developed by Boeing for NAVAIR PMA 205. The paper describes transitioning these integrated tools to commercial use. There is a critical need for the transition for the following reasons: First, to date, 70 percent of programmers' time is applied to software maintenance. The work of these users has not been facilitated by existing tools. The addition of Software Reengineering will also facilitate software maintenance and upgrading. In fact, the integrated tools will support the entire software life cycle. Second, the integrated tools are essential to Business Process Reengineering, which seeks radical process innovations to achieve breakthrough results. Done well, process reengineering delivers extraordinary gains in process speed, productivity and profitability. Most importantly, it discovers new opportunities for products and services in collaboration with other organizations. Legacy computer software must be changed rapidly to support innovative business processes. The integrated tools will provide commercial organizations important competitive advantages. This, in turn, will increase employment by creating new business opportunities. Third, the integrated system will produce much higher quality software than use of the tools separately. The reason for this is that producing or upgrading software requires keen understanding of extremely complex applications which is facilitated by the integrated tools. The radical savings in the time and cost associated with software, due to use of CASE tools that support combined Reuse of Software and Reengineering of Legacy Code, will add an important impetus to improving the automation of enterprises. This will be reflected in continuing operations, as well as in innovating new business processes. The proposed multi-tool software development is based on state of the art technology, which will be further advanced through the use of open systems for adding new tools and experience in their use.

Hwang, Phillip Q.↗

NASA NTRS2003

STS-107 Flight Day 6 Highlights

This video shows the activities of the STS-107 crew on flight day 6 of the Columbia orbiter's final mission. The crew members include: Rick Husband, Commander; William McCool, Pilot; Kalpana Chawla, David Brown, Michael Anderson, Laurel Clark; Mission Specialists; Ilan Ramon, Payload Specialist. The primary activities of flight day 6 are spaceborne experiments, and a conversation between Israeli Prime Minister Ariel Sharon, accompanied by the Israeli Minister of Education, and Israeli astronaut Ilan Ramon. Both the Israelis and their interpreter are audible on the tape. The video also features a bioreactor used to grow cancer cells in microgravity, and footage taken by the Mediterranean Israeli Dust Experiment (MEIDEX) of sprites, lightning in the lower ionosphere. Mission Specialist Anderson is shown working on the Laminar Soot Processes (LSP-2) experiment. Pilot McCool answers two questions from the public, and a view of Panama is shown.

Source record↗

NASA NTRS2010

Analyzing Distributed Functions in an Integrated Hazard Analysis

Large scale integration of today's aerospace systems is achievable through the use of distributed systems. Validating the safety of distributed systems is significantly more difficult as compared to centralized systems because of the complexity of the interactions between simultaneously active components. Integrated hazard analysis (IHA), a process used to identify unacceptable risks and to provide a means of controlling them, can be applied to either centralized or distributed systems. IHA, though, must be tailored to fit the particular system being analyzed. Distributed systems, for instance, must be analyzed for hazards in terms of the functions that rely on them. This paper will describe systems-oriented IHA techniques (as opposed to traditional failure-event or reliability techniques) that should be employed for distributed systems in aerospace environments. Special considerations will be addressed when dealing with specific distributed systems such as active thermal control, electrical power, command and data handling, and software systems (including the interaction with fault management systems). Because of the significance of second-order effects in large scale distributed systems, the paper will also describe how to analyze secondary functions to secondary functions through the use of channelization.

Morris, A. Terry↗

NASA NTRS2007

Tracking and Data Relay Satellite (TDRS) Orbit Estimation Using an Extended Kalman Filter

Alternatives to the Tracking and Data Relay Satellite (TDRS) orbit estimation procedure were studied to develop a technique that both produces more reliable results and is more amenable to automation than the prior procedure. The Earth Observing System (EOS) Terra mission has TDRS ephemeris prediction 3(sigma) requirements of 75 meters in position and 5.5 millimeters per second in velocity over a 1.5-day prediction span. Meeting these requirements sometimes required reruns of the prior orbit determination (OD) process, with manual editing of tracking data to get an acceptable solution. After a study of the available alternatives, the Flight Dynamics Facility (FDF) began using the Real-Time Orbit Determination (RTOD(Registered TradeMark)) Kalman filter program for operational support of TDRSs in February 2007. This extended Kalman filter (EKF) is used for daily support, including within hours after most thrusting, to estimate the spacecraft position, velocity, and solar radiation coefficient of reflectivity (C(sub R)). The tracking data used are from the Bilateration Ranging Transponder System (BRTS), selected TDRS System (TDRSS) User satellite tracking data, and Telemetry, Tracking, and Command (TT&C) data. Degraded filter results right after maneuvers and some momentum unloads provided incentive for a hybrid OD technique. The results of combining EKF strengths with the Goddard Trajectory Determination System (GTDS) Differential Correction (DC) program batch-least-squares solutions, as recommended in a 2005 paper on the chain-bias technique, are also presented.

Ward, Douglas T.↗

NASA NTRS2008

Enabling and Enhancing Space Mission Success and Reduction of Risk through the Application of an Integrated Data Architecture

The engineering phases of design, development, test, and evaluation (DDT and E) and subsequent planning, preparation, and operation (Ops) of space vehicles in a complex and distributed environment requires massive and continuous flows of information across the enterprise and across temporal stages of the vehicle lifecycle. The resulting capabilities at each subsequent stage depend in part on the capture, preparation, storage, and subsequent provision of information from prior stages. The United States National Aeronautics and Space Administration (NASA) is currently designing a fleet of new vehicles that will replace the Space Shuttle and expand space operations and exploration capabilities. This includes the 2 stage human rated lift vehicle Ares 1 and its associated crew vehicle the Orion, and a service module; the heavy lift cargo vehicle, Ares 5, and an associated cargo stage known as the Earth Departure Stage; and a Lunar Lander vehicle that contains a descent stage, and ascent stage, and a habitation module. A variety of concurrent assorted ground operations infrastructure including software and facilities are also being developed, assorted technology and assembly designs and development for equipment such as EVA suits, life support systems, command and control technologies are also in the pipeline. The development is occurring in a distributed manner, with project deliverables being contributed by a large and diverse assortment of vendors and most space faring nations. Critical information about all of the components, software, and procedures must be shared during the DDT and E phases and then made readily available to the mission operations staff for access during the planning, preparation, and operations phases, and also need to be readily available for system to system interactions. The Constellation Data Systems Project (CxDS) is identifying the needs, and designing and deploying systems and processes to support these needs. This paper details the steps and processes that NASA is applying within the Constellation Program to manage this data and information, and to insure that the correct information is available, correctly annotated, and can be provisioned digitally to enhance response times, and support engineering analysis and anomaly resolution.

Brummett, Robert C.↗

NASA NTRS2006

Real-Time Diagnosis of Faults Using a Bank of Kalman Filters

A new robust method of automated real-time diagnosis of faults in an aircraft engine or a similar complex system involves the use of a bank of Kalman filters. In order to be highly reliable, a diagnostic system must be designed to account for the numerous failure conditions that an aircraft engine may encounter in operation. The method achieves this objective though the utilization of multiple Kalman filters, each of which is uniquely designed based on a specific failure hypothesis. A fault-detection-and-isolation (FDI) system, developed based on this method, is able to isolate faults in sensors and actuators while detecting component faults (abrupt degradation in engine component performance). By affording a capability for real-time identification of minor faults before they grow into major ones, the method promises to enhance safety and reduce operating costs. The robustness of this method is further enhanced by incorporating information regarding the aging condition of an engine. In general, real-time fault diagnostic methods use the nominal performance of a "healthy" new engine as a reference condition in the diagnostic process. Such an approach does not account for gradual changes in performance associated with aging of an otherwise healthy engine. By incorporating information on gradual, aging-related changes, the new method makes it possible to retain at least some of the sensitivity and accuracy needed to detect incipient faults while preventing false alarms that could result from erroneous interpretation of symptoms of aging as symptoms of failures. The figure schematically depicts an FDI system according to the new method. The FDI system is integrated with an engine, from which it accepts two sets of input signals: sensor readings and actuator commands. Two main parts of the FDI system are a bank of Kalman filters and a subsystem that implements FDI decision rules. Each Kalman filter is designed to detect a specific sensor or actuator fault. When a sensor or actuator fault occurs, large estimation errors are generated by all filters except the one using the correct hypothesis. By monitoring the residual output of each filter, the specific fault that has occurred can be detected and isolated on the basis of the decision rules. A set of parameters that indicate the performance of the engine components is estimated by the "correct" Kalman filter for use in detecting component faults. To reduce the loss of diagnostic accuracy and sensitivity in the face of aging, the FDI system accepts information from a steady-state-condition-monitoring system. This information is used to update the Kalman filters and a data bank of trim values representative of the current aging condition.

Kobayashi, Takahisa↗

NASA NTRS2014

The CCSDS Next Generation Space Data Link Protocol (NGSLP)

The CCSDS space link protocols i.e., Telemetry (TM), Telecommand (TC), Advanced Orbiting Systems (AOS) were developed in the early growth period of the space program. They were designed to meet the needs of the early missions, be compatible with the available technology and focused on the specific link environments. Digital technology was in its infancy and spacecraft power and mass issues enforced severe constraints on flight implementations. Therefore the Telecommand protocol was designed around a simple Bose, Hocquenghem, Chaudhuri (BCH) code that provided little coding gain and limited error detection but was relatively simple to decode on board. The infusion of the concatenated Convolutional and Reed-Solomon codes5 for telemetry was a major milestone and transformed telemetry applications by providing them the ability to more efficiently utilize the telemetry link and its ability to deliver user data. The ability to significantly lower the error rates on the telemetry links enabled the use of packet telemetry and data compression. The infusion of the high performance codes for telemetry was enabled by the advent of digital processing, but it was limited to earth based systems supporting telemetry. The latest CCSDS space link protocol, Proximity-1 was developed in early 2000 to meet the needs of short-range, bi-directional, fixed or mobile radio links characterized by short time delays, moderate but not weak signals, and short independent sessions. Proximity-1 has been successfully deployed on both NASA and ESA missions at Mars and is planned to be utilized by all Mars missions in development. A new age has arisen, one that now provides the means to perform advanced digital processing in spacecraft systems enabling the use of improved transponders, digital correlators, and high performance forward error correcting codes for all communications links. Flight transponders utilizing digital technology have emerged and can efficiently provide the means to make the next leap in performance for space link communications. Field Programmable Gate Arrays (FPGAs) provide the capability to incorporate high performance forward error correcting codes implemented within software transponders providing improved performance in data transfer, ranging, link security, and time correlation. Given these synergistic technological breakthroughs, the time has come to take advantage of them in applying them to both on going (e.g., command, telemetry) and emerging (e.g., space link security, optical communication) space link applications. However one of the constraining factors within the Data Link Layer in realizing these performance gains is the lack of a generic transfer frame format and common supporting services amongst the existing CCSDS link layer protocols. Currently each of the four CCSDS link layer protocols (TM, TC, AOS, and Proximity-1) have unique formats and services which prohibits their reuse across the totality of all space link applications of CCSDS member space agencies. For example, Mars missions. These missions implement their proximity data link layer using the Proximity-1 frame format and the services it supports but is still required to support the direct from Earth (TC) protocols and the Direct To Earth (AOS/TM) protocols. The prime purpose of this paper, is to describe a new general purpose CCSDS Data Link layer protocol, the NGSLP that will provide the required services along with a common transfer frame format for all the CCSDS space links (ground to/from space and space to space links) targeted for emerging missions after a CCSDS agency-wide coordinated date. This paper will also describe related options that can be included for the Coding and Synchronization sub-layer of the Data Link layer to extend the capacities of the link and additionally provide an independence of the transfer frame sub-layer from the coding sublayer. This feature will provide missions the option of running either the currently performed synchronous coding and transfer frame data link or an asynchronous coding/frame data link, in which the transfer frame length is independent of the block size of the code. The benefits from the elimination of this constraint (frame synchronized to the code block) will simplify the interface between the transponder and the data handling equipment and reduce implementation costs and complexities. The benefits include: inclusion of encoders/decoders into transmitters and receivers without regard to data link protocols, providing the ability to insert latency sensitive messages into the link to support launch, landing/docking, telerobotics. and Variable Coded Modulation (VCM). In addition the ability to transfer different sized frames can provide a backup for delivering stored anomaly engineering data simultaneously with real time data, or relaying of frames from various sources onto a trunk line for delivery to Earth.

Kazz, Greg J.↗

NASA NTRSDate not supplied

Emulation of Core Flight System Applications for Flight Software Development and Validation

The Mars Sample Return (MSR) campaign is an unprecedented attempt in the return of Martian samples back to Earth. The ascent from the surface will be performed by the Mars Ascent Vehicle (MAV), a critical element in the mission that National Aeronautics and Space Administration (NASA) Marshall Space Flight Center (MSFC) is developing. To this end, innovations in flight software development, verification, and validation are occurring. The MAV flight computer will run Core Flight System (cFS), an open-source software environment developed by NASA Goddard Space Flight Center (GSFC). NASA Marshall’s MAV Mission and Fault Management (M&FM) Team has implemented an emulation of two applications of this architecture: Limit Checker and Stored Command. Using an emulation of the functionalities of these applications allows for rapid prototyping of table-based algorithms. Further, M&FM is leveraging an in-house, low-fidelity but high-throughput State Analysis Model (SAM), an integrated MATLAB Stateflow Plant and Software model. This model is run in parallel with the cFS emulation for full flyout testing of the M&FM algorithms, verification of intent of these algorithms, and for future auto-generation of application-ingestible M&FM tables. The tables can then be delivered to the MAV Flight Software (FSW) team in a seamless process, reducing the cost of traditional FSW development and the risk of starting M&FM FSW development at later points in the NASA program life cycle.

Cody Wheeler↗

NASA NTRSDate not supplied

Emulation of Core Flight System Applications for Flight Software Development and Validation

Cody Wheeler↗

NASA NTRSDate not supplied

Distributed Spacecraft Autonomy - Development of Swarm Autonomy Capability and Scalability for Spacecraft

The Distributed Spacecraft Autonomy project is developing a suite of software tools that enable an operator to command and receive data from a swarm as a single entity, enable a swarm to autonomously coordinate its actions via distributed decision making and reactive closed-loop control, and model swarm behavior in the presence of anomalies or failures. Our use case is the mapping of the electron density of the ionosphere using radio tomography by coordinating the selection of appropriate GPS channels, and by recording Total Electron Count (TEC) measurements. DSA will be demonstrated onboard the NASA Ames Starling mission – a swarm of four small, LEO spacecraft, scheduled to launch in 2021. We will also perform a ground demonstration with simulated and hardware-in-the-loop elements, to validate the tools for controlling swarms of up to 100 assets. The capability to communicate autonomously between the swarm satellites is demonstrated via a sophisticated simulation architecture. Historical Plasmasphere TEC data obtained via dual-band Novatel GPS Receivers are utilized as a representative input dataset for the swarm. The representative TEC data and GPS satellite observability information is fed to the autonomous software package in place of a true real-time ground data collection process. The swarm satellites actively share status updates amongst one another and utilize multi-agent decision making to optimally identify regions of interest in the TEC distribution. The software, aware of the bandwidth limitations of the swarm satellites, prioritizes explorative measurements, which define the range of observability for the satellites, as well as exploitative measurements, which focus on maximizing the observance potential of regions with prolonged, elevated TEC density. The science of this study can ultimately be used to determine the dynamics and coupling of Earth’s magnetosphere, ionosphere, and atmosphere and their response to solar and terrestrial inputs. The findings can be applied to the imaging of critical, transient phenomena in the magnetosphere in later missions. Meanwhile, the swarm autonomy capabilities have far reaching potential in future satellite missions. As an experimental demonstration of the autonomous capabilities of the network, a message is first printed within a core Flight Executive (cFE) application. Two cFE applications that communicate with one another within the same core Flight System (cFS) are shown. Communication between mission applications on the internal cFE bus is extended to utilize Data Distribution Service (DDS) for vehicle-to-vehicle networking. The DDS middleware provides reliable delivery, routing, and topic subscription features over User Datagram Protocol (UDP). Leveraging Linux containerization, a networked set of satellite instances are generated by script to simulate swarm behavior. Swarm commanding and synchronization through the network is demonstrated under various topologies and data-loss conditions. Finally, autonomous swarm scalability from 2 satellites to 100 satellites is shown.

Distributed Autonomy↗

NASA NTRS1972

Fourier plane filters

An electrically addressed liquid crystal Fourier plane filter capable of real time optical image processing is described. The filter consists of two parts: a wedge filter having forty 9 deg segments and a ring filter having twenty concentric rings in a one inch diameter active area. Transmission of the filter in the off (transparent) state exceeds fifty percent. By using polarizing optics, contrast as high as 10,000:1 can be achieved at voltages compatible with FET switching technology. A phenomenological model for the dynamic scattering is presented for this special case. The filter is designed to be operated from a computer and is addressed by a seven bit binary word which includes an on or off command and selects any one of the twenty rings or twenty wedge pairs. The overall system uses addressable latches so that once an element is in a specified state, it will remain there until a change of state command is received. The drive for the liquid crystal filter is ? 30 V peak at 30 Hz to 70 Hz. These parameters give a rise time for the scattering of 20 msec and a decay time of 80 to 100 msec.

Oliver, D. S.↗

NASA NTRS1989

The flight telerobotic servicer Tinman concept: System design drivers and task analysis

A study was conducted to develop a preliminary definition of the Flight Telerobotic Servicer (FTS) that could be used to understand the operational concepts and scenarios for the FTS. Called the Tinman, this design concept was also used to begin the process of establishing resources and interfaces for the FTS on Space Station Freedom, the National Space Transportation System shuttle orbiter, and the Orbital Maneuvering vehicle. Starting with an analysis of the requirements and task capabilities as stated in the Phase B study requirements document, the study identified eight major design drivers for the FTS. Each of these design drivers and their impacts on the Tinman design concept are described. Next, the planning that is currently underway for providing resources for the FTS on Space Station Freedom is discussed, including up to 2000 W of peak power, up to four color video channels, and command and data rates up to 500 kbps between the telerobot and the control station. Finally, an example is presented to show how the Tinman design concept was used to analyze task scenarios and explore the operational capabilities of the FTS. A structured methodology using a standard terminology consistent with the NASA/National Bureau of Standards Standard Reference Model for Telerobot Control System Architecture (NASREM) was developed for this analysis.

Andary, J. F.↗