Search NASA⌕ Search

SEARCH · Search NASA

Results for “spacecraft data interfaces”

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 577 records · Page 32

Flight Software Dictionary Development for the Mars2020 Rover

The Mars2020 project, developed and operated by the Jet Propulsion Laboratory (JPL), successfully landed the Perseverance rover and its flying companion Ingenuity on the surface of Mars on February 18th 2021. Perseverance combines heritage and cutting-edge flight software and hardware to accomplish crucial mission requirements related to Martian surface sampling. The design, development, and operation of NASA’s large strategic science missions require the ability to communicate spacecraft capabilities to hundreds of engineers across multiple disciplines. The interaction between flight and ground software development, Verification and Validation (V&V), Assembly, Test, and Launch Operations (ATLO), and management each demand quick understanding of unique slices of information for each discipline. This information includes the current capabilities of the flight system as well as future capabilities and their status as they are developed and tested. Despite the fundamental and critical nature of this information, the flight software dictionaries used to track it are a stumbling block for many projects. These dictionaries provide the cornerstone for the interpretation of data sent from the spacecraft, allowing for quick comprehension by engineers on the ground. During both spacecraft development and operations, flight software dictionary management includes significant challenges due to the large number of interfacing systems and the subtle yet distinct needs of each.The engineering of flight software dictionaries for Mars2020 had numerous challenges, most-notably: parallel dictionary development to support simultaneous separate flight software build campaigns for each mission phase (cruise and surface), managing requests for operations-enabling information without perturbing the heritage interface with the rover, and the introduction of new tools by the dictionary stakeholders that forced the dictionary team to innovate and redesign the heritage tool chain. These challenges generated guiding principles for the dictionary development effort: emphasize coding best practices and unit testing in the dictionary code development tool chain, use institutionally provided COTS (commercial-off-the-shelf) tools whenever possible, and maintain the heritage flight-ground interface all while advancing operations-enabling information via a loosely coupled interface.Throughout development and operations, the Mars2020 dictionary toolchain included IBM DOORS Next Generation, GitHub, Microsoft Excel, Docker, Jenkins, and a significant custom-built Python codebase. Significant interfaces included JPL’s command and control software, heritage flight software team tools and processes, and the many cloud-based ground tools developed for the mission.This paper will discuss the requirements for the Mars2020 dictionary development, the development team’s response to those requirements, lessons learned throughout the process, steps taken towards automated deliveries and continuous integration of stakeholder inputs, potential toolchain improvements for Mars2020, and key takeaways that could be applied to future missions.

Pyrzak, Guy↗

Dissipative Processes in the Magnetopause Boundary Layer and Flux Transfer Events Using the Interball Spacecraft

Work on two quite distinct projects was accomplished: a study of flux transfer events and a study of the magnetosheath-polar cusp interface. The study with Oleg Vaisberg of the Space Research Institute in Moscow used only Interball data. We analyzed the magnetometer data and to assist the observations of Flux Transfer Events (FTEs) to aid in the interpretation of the data. One of the issues was to distinguish between simple traversals of the magnetopause and encounters with FTES. Once that distinction became clear then we could examine the changes in the plasma associated with the FTE. The second study was undertaken to study the turbulent interaction of the magnetosheath flow past the polar cusp. In this study Polar Data was used inside the magnetosphere as Interball crossed through the cusp into the magnetosheath. Our most interesting but least turbulent example was on May 29, 1996 when the interplanetary magnetic field (IMF) was northward. During these conditions the magnetosheath interface with the cusp becomes streamlined due to reconnection above the polar cusp. This reconnection provides a smooth surface across which the velocity shear occurs, thus minimizing turbulence in the interaction. The magnetopause current lies closer to the Earth than the flow boundary. This current layer reverses the field direction from nortward to southward in the neighborhood of the distant cusp and is somewhat noisty but not as much as this region becomes when the IMF is southward.

Russell, C. T.↗

BioSentinel: Leading the Way for Deep Space CubeSat Missions

Flagship science missions are not alone in Deep Space thanks to BioSentinel, a 6U spacecraft launched on Artemis-1. BioSentinel is one of the longest operating CubeSats beyond cislunar space. The subsystems and COTS components of the BioSentinel bus are a template for future deep space missions, and the lessons learned from over a year of operations will enable improved performance for the next missions. BioSentinel achieved its unprecedented performance for an SLS secondary payload due to preparation, planning, and a robust design. Pre-launch antenna and interface testing with both DSN and ESA confirmed command and data pathways and allowed for operational flexibility in the critical early hours post-deployment. Mission Operations simulations prior to launch identified potential risks and primed operators to respond in flight, preparing the team to react quickly to successfully detumble the spacecraft and enter a power-positive state. The spacecraft would not have survived without the inclusion of the trailblazing 3D-printed composite cold gas propulsion system. The non-standard tank geometry enabled efficient use of the limited space available in the CubeSat, as well as the capability to detumble the spacecraft and manage momentum, while providing sufficient margin to execute potential delta-V maneuvers. The Iris radio has operated for over 18 months with no significant issues. Initial Iris performance estimates have been accurate throughout the mission. BioSentinel continues to collect data on thermal conditions and to validate our performance models with real-world knowledge. We have received exemplary support from our DSN partners. Following the conclusion of the primary science mission, the Linear Energy Transfer (LET) Spectrometer continued to collect solar and galactic radiation data from its location in heliocentric orbit. The free space dataset offered by the BioSentinel LET is a valuable source of data for model validation and future mission planning. As the spacecraft travels farther from Earth it is poised to provide longitudinally distributed measurements of solar particle events during solar maximum. The lessons learned from BioSentinel suggest key areas to enhance performance. The ability to upload modified flight software can increase the stability of memory management. Additional heaters in the propulsion system design have already proven successful on the Starling mission. Streamlining mission operations can reduce costs, increase data return, and better utilize DSN time. Enhancements such as these will facilitate reliable, long-duration deep space exploration using the proven BioSentinel 6U CubeSat bus.

BioSentinel↗

Development of Graphical User Interface for ARRBOD (Acute Radiation Risk and BRYNTRN Organ Dose Projection)

The space radiation environment, particularly solar particle events (SPEs), poses the risk of acute radiation sickness (ARS) to humans; and organ doses from SPE exposure may reach critical levels during extra vehicular activities (EVAs) or within lightly shielded spacecraft. NASA has developed an organ dose projection model using the BRYNTRN with SUMDOSE computer codes, and a probabilistic model of Acute Radiation Risk (ARR). The codes BRYNTRN and SUMDOSE, written in FORTRAN, are a Baryon transport code and an output data processing code, respectively. The ARR code is written in C. The risk projection models of organ doses and ARR take the output from BRYNTRN as an input to their calculations. BRYNTRN code operation requires extensive input preparation. With a graphical user interface (GUI) to handle input and output for BRYNTRN, the response models can be connected easily and correctly to BRYNTRN in friendly way. A GUI for the Acute Radiation Risk and BRYNTRN Organ Dose (ARRBOD) projection code provides seamless integration of input and output manipulations, which are required for operations of the ARRBOD modules: BRYNTRN, SUMDOSE, and the ARR probabilistic response model. The ARRBOD GUI is intended for mission planners, radiation shield designers, space operations in the mission operations directorate (MOD), and space biophysics researchers. The ARRBOD GUI will serve as a proof-of-concept example for future integration of other human space applications risk projection models. The current version of the ARRBOD GUI is a new self-contained product and will have follow-on versions, as options are added: 1) human geometries of MAX/FAX in addition to CAM/CAF; 2) shielding distributions for spacecraft, Mars surface and atmosphere; 3) various space environmental and biophysical models; and 4) other response models to be connected to the BRYNTRN. The major components of the overall system, the subsystem interconnections, and external interfaces are described in this report; and the ARRBOD GUI product is explained step by step in order to serve as a tutorial.

Kim, Myung-Hee↗

PROPERTIES OF CHROMOSPHERIC EVAPORATION AND PLASMA DYNAMICS OF A SOLAR FLARE FROM IRIS OBSERVATIONS

The dynamics of hot chromospheric plasma of solar flares is a key to understanding the mechanisms of flare energy release and particle acceleration. A moderate M1.0 class flare of 2014 June 12, (SOL2014-06-12T21:12) was simultaneously observed by NASA's Interface Region Imaging Spectrograph (IRIS) and other spacecraft, and also by the New Solar Telescope at the BBSO. This paper presents the first part of our investigation focused on analysis of the IRIS data. Our analysis of the IRIS data in different spectral lines reveals a strong redshifted jet-like flow with a speed of ∼100 km s{sup −1} of the chromospheric material before the flare. Strong nonthermal emission of the C ii k 1334.5 Å line, formed in the chromosphere–corona transition region, is observed at the beginning of the impulsive phase in several small (with a size of ∼1″) points. It is also found that the C ii k line is redshifted across the flaring region before, during, and after the impulsive phase. A peak of integrated emission of the hot (1.1 · 10{sup 7} K) plasma in the Fe xxi 1354.1 Å line is detected approximately five minutes after the integrated emission peak of the lower temperature C ii k. A strong blueshift of the Fe xxi line across the flaring region corresponds to evaporation flows of the hot chromospheric plasma with a speed of 50 km s{sup −1}. Additional analysis of the RHESSI data supports the idea that the upper chromospheric dynamics observed by IRIS has features of “gentle” evaporation driven by heating of the solar chromosphere by accelerated electrons and by a heat flux from the flare energy release site.

79 ASTRONOMY AND ASTROPHYSICS↗

Earth Observatory Satellite system definition study. Report no. 7: EOS system definition report

The design concept and operational aspects of the Earth Observatory Satellite (EOS) are presented. A table of the planned EOS missions is included to show the purpose of the mission, the instruments involved, and the launch date. The subjects considered in the analysis of the EOS development are: (1) system requirements, (2) design/cost trade methodology, (3) observatory design alternatives, (4) the data management system, (5) the design evaluation and preferred approach, (6) program cost compilation, (7) follow-on mission accommodation, and (8) space shuttle interfaces and utilization. Illustrations and block diagrams of the spacecraft configurations are provided.

Source record↗

Transitioning Autonomous Systems Technology Research to a Flight Software Environment

NASA has developed methods and algorithms for autonomous spacecraft operations,including automated planning and scheduling, fault diagnostics and impact determination,procedure management and display. Making the transition from technology research tooperational flight software requires overcoming significant technical, programmatic andcultural challenges. Technology research is aimed at developing methods that performspecific functions correctly, but the resulting software may not be designed for flightprocessors with limited CPU, memory and network resources, and may not be easilyintegrated into spacecraft flight software. Our objective in the Autonomous Systems andOperations Project is to make significant strides toward the transformation from technologyto operational use. Our focus was twofold: maturing research grade autonomy software intoa flight software environment using broadly accepted languages and tools; and integratingautonomy applications with each other and with representative systems and their data andcommand interfaces. For a target flight software environment, we chose Core FlightSoftware, developed by Goddard Space Flight Center as a common operating systemindependent framework. Our hardware integration environment was provided by theIntegrated Power and Avionics Systems (iPAS) Lab at Johnson Space Center, in whichvarious subsystem development has been conducted to address engineering challenges forthe vehicles and systems required for long-duration missions into the solar system. The iPASand its network of connected facilities provides realistic subsystem hardware or simulationsof spacecraft power, life support, guidance, navigation and control, and command and datahandling subsystems. Interfaces between autonomy applications and the subsystems beingassessed and controlled were developed, assessed and refined. The hardware and softwareenvironment using CFS and the iPAS facility has proven to be a highly flexible and realisticenvironment in which to rapidly integrate applications in an iterative, low cost setting. Usingthe integration environment we have developed, we will turn our focus to performance andsizing analysis to determine the computational requirements for full-scale deployment ofautonomy technology. Scalability of reasoners and the spacecraft models upon which theyoperate, and robustness across the full range of spacecraft conditions and environments willbe explored and improved. We are making significant contributions to the future programsthat will build the spacecraft that will take humans beyond the Earth-Moon system, in whichprogram Systems Engineers will be able to accurately and confidently design in accurate,robust and mature autonomous operations systems.

Flight Software↗

Re-Engineering the Tropical Rainfall Measuring Mission (TRMM) Satellite Utilizing Goddard Space Flight Center (GSFC) Mission Services Center (GMSEC) Middleware Based Technology to Enable Lights Out Operations and Autonomous Re-Dump of Lost Telemetry Data

The Tropical Rainfall Measuring Mission (TRMM) spacecraft was launched in November of 1996 in order to obtain unique three dimensional radar cross sectional observations of cloud structures with particular interest in hurricanes. The TRMM mission life was recently extended with current estimates that operations will continue through the 2012-2013 timeframe. Faced with this extended mission profile, the project has embarked on a technology refresh and re-engineering effort. TRMM has recently implemented a re-engineering effort to expand a middleware based messaging architecture to enable fully redundant lights-out of flight operations activities. The middleware approach is based on the Goddard Mission Services Evolution Center (GMSEC) architecture, tools and associated open-source Applications Programming Interface (API). Middleware based messaging systems are useful in spacecraft operations and automation systems because private node based knowledge (such as that within a telemetry and command system) can be broadcast on the middleware messaging bus and hence enable collaborative decisions to be made by multiple subsystems. In this fashion, private data is made public and distributed within the local area network and multiple nodes can remain synchronized with other nodes. This concept is useful in a fully redundant architecture whereby one node is monitoring the processing of the 'prime' node so that in the event of a failure the backup node can assume operations of the prime, without loss of state knowledge. This paper will review and present the experiences, architecture, approach and lessons learned of the TRMM re-engineering effort centered on the GMSEC middleware architecture and tool suite. Relevant information will be presented that relates to the dual redundant parallel nature of the Telemetry and Command (T and C) and Front-End systems and how these systems can interact over a middleware bus to achieve autonomous operations including autonomous commanding to recover missing science data during the same spacecraft contact.

Marius, Julio L.↗

OSIRIS-REx Earth Return Orbit Determination Analysis and Performance

Origins, Spectral Interpretation, Resource Identification, and Security–Regolith Explorer (OSIRIS-REx) was a NASA New Frontiers–class asteroid sample return mission to (101955) Bennu. OSIRIS-REx performed a series of Trajectory Cor-rection Maneuver (TCM)s to target an Entry Interface (EI) point for Earth Return and entry, descent, and landing (EDL). On September 24, 2023, the Sample Re-turn Capsule (SRC) separated from the spacecraft, entered the atmosphere, and ultimately landed at the Utah Test and Training Range for recovery. This paper gives an overview of the updated orbit determination (OD) covariance analysis that went into the Earth return and reentry analysis after asteroid departure. Tracking data assumptions and multiple filter cases are analyzed to show performance. Operational OD results from TCM-9 and subsequent targeting maneuvers up to entry interface are provided. We show parameter error analysis contributions from the OD setup and their breakdown in the B-Plane error ellipses. Finally, we discuss the terminal OD solutions into EI and reconstruction results using onboard image data.

Jason M. Leonard↗

A solar type II radio burst from coronal mass ejection-coronal ray interaction: Simultaneous radio and extreme ultraviolet imaging

Simultaneous radio and extreme ultraviolet (EUV)/white-light imaging data are examined for a solar type II radio burst occurring on 2010 March 18 to deduce its source location. Using a bow-shock model, we reconstruct the three-dimensional EUV wave front (presumably the type-II-emitting shock) based on the imaging data of the two Solar TErrestrial RElations Observatory spacecraft. It is then combined with the Nançay radio imaging data to infer the three-dimensional position of the type II source. It is found that the type II source coincides with the interface between the coronal mass ejection (CME) EUV wave front and a nearby coronal ray structure, providing evidence that the type II emission is physically related to the CME-ray interaction. This result, consistent with those of previous studies, is based on simultaneous radio and EUV imaging data for the first time.

79 ASTRONOMY AND ASTROPHYSICS↗

Rotary Joints With Electrical Connections

Power and data transmitted on many channels. Two different rotary joints equipped with electrical connections between rotating and stationary parts. One joint transmits axial thrust and serves as interface between spinning and nonspinning parts of Galileo spacecraft. Other is scanning (limitedrotation) joint that aims scientific instruments from nonspinning part. Selected features of both useful to designers of robots, advanced production equipment, and remotely controlled instruments.

Osborn, F. W.↗

Environmentally-induced discharge transient coupling to spacecraft

The Hughes SCREENS (Space Craft Response to Environments of Space) technique was applied to generic spin and 3-axis stabilized spacecraft models. It involved the NASCAP modeling for surface charging and lumped element modeling for transients coupling into a spacecraft. A differential voltage between antenna and spun shelf of approx. 400 V and current of 12 A resulted from discharge at antenna for the spinner and approx. 3 kv and 0.3 A from a discharge at solar panels for the 3-axis stabilized Spacecraft. A typical interface circuit response was analyzed to show that the transients would couple into the Spacecraft System through ground points, which are most vulnerable. A compilation and review was performed on 15 years of available data from electron and ion current collection phenomena. Empirical models were developed to match data and compared with flight data of Pix-1 and Pix-2 mission. It was found that large space power systems would float negative and discharge if operated at or above 300 V. Several recommendations are given to improve the models and to apply them to large space systems.

Viswanathan, R.↗

Mapping Between Distinct Reed-Solomon Codes

One-to-one mapping between two Reed-Solomon (RS) codes devised to enable decoder designed for one of codes to operate on other one also. Codes in question must have same N and K parameters (defined below) but otherwise be two distinct RS codes. Mapping intended to enable same ground-based decoder to decode telemetry signals from two spacecraft in two different RS codes of (N,K) = (255,223). Also useful in purely terrestrial data communications and in optical and magnetic recording and playback of digitized audio and video signals. Implemented in interface circuitry and/or software to enable communication between coding systems of different manufacturers using different RS codes within same (N,K) family.

Perlman, Marvin↗

Definition of spacecraft standard interfaces by the NASA Space Assembly and Servicing Working Group (SASWG)

The purpose of the NASA Space Assembly and Servicing Working Group (SASWG) is to study enabling technologies for on-orbit spacecraft maintenance and servicing. One key technology required for effective space logistics activity is the development of standard spacecraft interfaces, including the 'Basic Set' defined by NASA, the U.S. Space Command, and industry panelists to be the following: (1) navigation aids; (2) grasping, berthing, and docking; and (3) utility connections for power, data, and fluids. Draft standards have been prepared and referred to professional standards organizations, including the AIAA, EIA, and SAE space standards committee. The objective of the SASWG is to support these committees with the technical expertise required to prepare standards, guidelines, and recommended practices which will be accepted by the ANSI and international standards organizations, including the ISO, IEC, and PASC.

Radtke, Robert↗

Autonomous Satellite Command and Control through the World Wide Web: Phase 3

NASA's New Millenium Program (NMP) has identified a variety of revolutionary technologies that will support orders of magnitude improvements in the capabilities of spacecraft missions. This program's Autonomy team has focused on science and engineering automation technologies. In doing so, it has established a clear development roadmap specifying the experiments and demonstrations required to mature these technologies. The primary developmental thrusts of this roadmap are in the areas of remote agents, PI/operator interface, planning/scheduling fault management, and smart execution architectures. Phases 1 and 2 of the ASSET Project (previously known as the WebSat project) have focused on establishing World Wide Web-based commanding and telemetry services as an advanced means of interfacing a spacecraft system with the PI and operators. Current automated capabilities include Web-based command submission, limited contact scheduling, command list generation and transfer to the ground station, spacecraft support for demonstrations experiments, data transfer from the ground station back to the ASSET system, data archiving, and Web-based telemetry distribution. Phase 2 was finished in December 1996. During January-December 1997 work was commenced on Phase 3 of the ASSET Project. Phase 3 is the subject of this report. This phase permitted SSDL and its project partners to expand the ASSET system in a variety of ways. These added capabilities included the advancement of ground station capabilities, the adaptation of spacecraft on-board software, and the expansion of capabilities of the ASSET management algorithms. Specific goals of Phase 3 were: (1) Extend Web-based goal-level commanding for both the payload PI and the spacecraft engineer; (2) Support prioritized handling of multiple PIs as well as associated payload experimenters; (3) Expand the number and types of experiments supported by the ASSET system and its associated spacecraft; (4) Implement more advanced resource management, modeling and fault management capabilities that integrate the space and ground segments of the space system hardware; (5) Implement a beacon monitoring test; (6) Implement an experimental blackboard controller for space system management; (7) Further define typical ground station developments required for Internet-based remote control and for full system automation of the PI-to-spacecraft link. Each of those goals is examined in the next section. Significant sections of this report were also published as a conference paper.

Cantwell, Brian↗

Performance interface document for users of Tracking and Data Relay Satellite System (TDRSS) electromechanically steered antenna systems (EMSAS)

Satellites that use the NASA Tracking and Data Relay Satellite System (TDRSS) require antennas that are crucial for performing and achieving reliable TDRSS link performance at the desired data rate. Technical guidelines are presented to assist the prospective TDRSS medium-and high-data rate user in selecting and procuring a viable, steerable high-gain antenna system. Topics addressed include the antenna gain/transmitter power/data rate relationship; Earth power flux-density limitations; electromechanical requirements dictated by the small beam widths, desired angular coverage, and minimal torque disturbance to the spacecraft; weight and moment considerations; mechanical, electrical and thermal interfaces; design lifetime failure modes; and handling and storage. Proven designs are cited and space-qualified assemblies and components are identified.

Hockensmith, R.↗

IUS/TUG orbital operations and mission support study. Volume 3: Space tug operations

A study was conducted to develop space tug operational concepts and baseline operations plan, and to provide cost estimates for space tug operations. Background data and study results are presented along with a transition phase analysis (the transition from interim upper state to tug operations). A summary is given of the tug operational and interface requirements with emphasis on the on-orbit checkout requirements, external interface operational requirements, safety requirements, and system operational interface requirements. Other topics discussed include reference missions baselined for the tug and details for the mission functional flows and timelines derived for the tug mission, tug subsystems, tug on-orbit operations prior to the tug first burn, spacecraft deployment and retrieval by the tug, operations centers, mission planning, potential problem areas, and cost data.

Source record↗

CCSDS Time-Critical Onboard Networking Service

The Consultative Committee for Space Data Systems (CCSDS) is developing recommendations for communication services onboard spacecraft. Today many different communication buses are used on spacecraft requiring software with the same basic functionality to be rewritten for each type of bus. This impacts on the application software resulting in custom software for almost every new mission. The Spacecraft Onboard Interface Services (SOIS) working group aims to provide a consistent interface to various onboard buses and sub-networks, enabling a common interface to the application software. The eventual goal is reusable software that can be easily ported to new missions and run on a range of onboard buses without substantial modification. The system engineer will then be able to select a bus based on its performance, power, etc and be confident that a particular choice of bus will not place excessive demands on software development. This paper describes the SOIS Intra-Networking Service which is designed to enable data transfer and multiplexing of a variety of internetworking protocols with a range of quality of service support, over underlying heterogeneous data links. The Intra-network service interface provides users with a common Quality of Service interface when transporting data across a variety of underlying data links. Supported Quality of Service (QoS) elements include: Priority, Resource Reservation and Retry/Redundancy. These three QoS elements combine and map into four TCONS services for onboard data communications: Best Effort, Assured, Reserved, and Guaranteed. Data to be transported is passed to the Intra-network service with a requested QoS. The requested QoS includes the type of service, priority and where appropriate, a channel identifier. The data is de-multiplexed, prioritized, and the required resources for transport are allocated. The data is then passed to the appropriate data link for transfer across the bus. The SOIS supported data links may inherently provide the quality of service support requested by the intra-network layer. In the case where the data link does not have the required level of support, the missing functionality is added by SOIS. As a result of this architecture, re-usable software applications can be designed and used across missions thereby promoting common mission operations. In addition, the protocol multiplexing function enables the blending of multiple onboard networks. This paper starts by giving an overview of the SOIS architecture in section 11, illustrating where the TCONS services fit into the overall architecture. It then describes the quality of service approach adopted, in section III. The prototyping efforts that have been going on are introduced in section JY. Finally, in section V the current status of the CCSDS recommendations is summarized.

Parkes, Steve↗