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 793 records · Page 44

The Microgravity Science Glovebox (MSG), a Resource for Gravity-Dependent Phenomena Research on the International Space Station (ISS)

The Microgravity Science Glovebox (MSG) is a double rack facility aboard the International Space Station (ISS) designed for gravity-dependent phenomena investigation handling. The MSG has been operating in the ISS US Laboratory Module since July 2002. The MSG facility provides an enclosed working area for investigation manipulation and observation in the ISS. The MSG s unique design provides two levels of containment to protect the ISS crew from hazardous operations. Research investigations operating inside the MSG are provided a large 255 liter work volume, 1000 watts of dc power via a versatile supply interface (120,28, +/-12, and 5 Vdc), 1000 watts of cooling capability, video and data recording and real time downlink, ground commanding capabilities, access to ISS Vacuum Exhaust and Vacuum Resource Systems, and gaseous nitrogen supply. With these capabilities, the MSG is an ideal platform for research required to advance the technology readiness levels (TRL) needed for the Crew Exploration Vehicle and the Exploration Initiative. Areas of research that will benefit from investigations in the MSG include thermal management, fluid physics, spacecraft fire safety, materials science, combustion and reacting control systems, in situ fabrication and repair, and advanced life support technologies. This paper will provide a detailed explanation of the MSG facility, a synopsis of the research that has already been accomplished in the MSG, an overview of investigations planning to operate in the MSG, and possible augmentations that can be added to the MSG facility to further enhance the resources provided to investigations.

Spivey, Reggie A.↗

An Overview of the Microgravity Science Glovebox (MSG) Facility, and the Gravity-Dependent Phenomena Research Performed in the MSG on the International Space Station (ISS)

The Microgravity Science Glovebox (MSG) is a double rack facility aboard the International Space Station (ISS) designed for gravity-dependent phenomena investigation handling. The MSG has been operating in the ISS US Laboratory Module since July 2002. The MSG facility provides an enclosed working area for investigation manipulation and observation, The MSG's unique design provides two levels of containment to protect the ISS crew from hazardous operations. Research investigations operating inside the MSG are provided a large 255 liter work volume, 1000 watts of dc power via a versatile supply interface (120, 28, +/-12, and 5 Vdc), 1000 watts of cooling capability, video and data recording and real time downlink, ground commanding capabilities, access to ISS Vacuum Exhaust and Vacuum Resource Systems, and gaseous nitrogen supply. With these capabilities, the MSG is an ideal platform for research required to advance the technology readiness levels (TRL) needed for the Crew Exploration Vehicle and the Exploration Initiative. Areas of research that will benefit from investigations in the MSG include thermal management, fluid physics, spacecraft fire safety, materials science, combustion, reaction control systems, in situ fabrication and repair, and advanced life support technologies. This paper will provide a detailed explanation of the MSG facility, a synopsis of the research that has already been accomplished in the MSG and an overview of investigations planning to operate in the MSG. In addition, this paper will address possible changes to the MSG utilization process that will be brought about by the transition to ISS as a National Laboratory.

Spivey, Reggie A.↗

A Simulation Based Investigation of High Latency Space Systems Operations

This study was the first in a series of planned tests to use physics-based subsystem simulations to investigate the interactions between a spacecraft's crew and a ground-based mission control center for vehicle subsystem operations across long communication delays. The simulation models the life support system of a deep space habitat. It contains models of an environmental control and life support system, an electrical power system, an active thermal control systems, and crew metabolic functions. The simulation has three interfaces: 1) a real-time crew interface that can be use to monitor and control the subsystems; 2) a mission control center interface with data transport delays up to 15 minute each way; and 3) a real-time simulation test conductor interface used to insert subsystem malfunctions and observe the interactions between the crew, ground, and simulated vehicle. The study was conducted at the 21st NASA Extreme Environment Mission Operations (NEEMO) mission. The NEEMO crew and ground support team performed a number of relevant deep space mission scenarios that included both nominal activities and activities with system malfunctions. While this initial test sequence was focused on test infrastructure and procedures development, the data collected in the study already indicate that long communication delays have notable impacts on the operation of deep space systems. For future human missions beyond cis-lunar, NASA will need to design systems and support tools to meet these challenges. These will be used to train the crew to handle critical malfunctions on their own, to predict malfunctions and assist with vehicle operations. Subsequent more detailed and involved studies will be conducted to continue advancing NASA's understanding of space systems operations across long communications delays.

Li, Zu Qun↗

A Simulation Based Investigation of High Latency Space Systems Operations

This study was the first in a series of planned tests to use physics-based subsystem simulations to investigate the interactions between a spacecraft's crew and a ground-based mission control center for vehicle subsystem operations across long communication delays. The simulation models the life support system of a deep space habitat. It contains models of an environmental control and life support system, an electrical power system, an active thermal control system, and crew metabolic functions. The simulation has three interfaces: 1) a real-time crew interface that can be use to monitor and control the subsystems; 2) a mission control center interface with data transport delays up to 15 minute each way; and 3) a real-time simulation test conductor interface used to insert subsystem malfunctions and observe the interactions between the crew, ground, and simulated vehicle. The study was conducted at the 21st NASA Extreme Environment Mission Operations (NEEMO) mission. The NEEMO crew and ground support team performed a number of relevant deep space mission scenarios that included both nominal activities and activities with system malfunctions. While this initial test sequence was focused on test infrastructure and procedures development, the data collected in the study already indicate that long communication delays have notable impacts on the operation of deep space systems. For future human missions beyond cis-lunar, NASA will need to design systems and support tools to meet these challenges. These will be used to train the crew to handle critical malfunctions on their own, to predict malfunctions, and to assist with vehicle operations. Subsequent more detailed and involved studies will be conducted to continue advancing NASA's understanding of space systems operations across long communications delays.

Li, Zu Qun↗

Reconfigurable modular computer networks for spacecraft on-board processing

The core electronics subsystems on unmanned spacecraft, which have been sent over the last 20 years to investigate the moon, Mars, Venus, and Mercury, have progressed through an evolution from simple fixed controllers and analog computers in the 1960's to general-purpose digital computers in current designs. This evolution is now moving in the direction of distributed computer networks. Current Voyager spacecraft already use three on-board computers. One is used to store commands and provide overall spacecraft management. Another is used for instrument control and telemetry collection, and the third computer is used for attitude control and scientific instrument pointing. An examination of the control logic in the instruments shows that, for many, it is cost-effective to replace the sequencing logic with a microcomputer. The Unified Data System architecture considered consists of a set of standard microcomputers connected by several redundant buses. A typical self-checking computer module will contain 23 RAMs, two microprocessors, one memory interface, three bus interfaces, and one core building block.

Rennels, D. A.↗

Galileo - The Serial-Production AIT Challenge

The Galileo Project is one of the most demanding projects of ESA, being Europe's autarkic navigation system and a constellation composed of 30 satellites. This presentation points out the different phases of the project up to the full operational capability and the corresponding launch options with respect to launch vehicles as well as launch configurations. One of the biggest challenges is to set up a small serial 'production line' for the overall integration and test campaign of satellites. This production line demands an optimization of all relevant tasks, taking into account also backup and recovery actions. A comprehensive AIT concept is required, reflecting a tightly merged facility layout and work flow design. In addition a common data management system is needed to handle all spacecraft related documentation and to have a direct input-out flow for all activities, phases and positions at the same time. Process optimization is a well known field of engineering in all small high tech production lines, nevertheless serial production of satellites are still not the daily task in space business and therefore new concepts have to be put in place. Therefore, and in order to meet the satellites overall system optimization, a thorough interface between unit/subsystem manufacturing and satellite AIT must be realized to ensure a smooth flow and to avoid any process interruption, which would directly lead to a schedule impact.

Ragnit, Ulrike↗

Control Program for an Optical-Calibration Robot

A computer program provides semiautomatic control of a moveable robot used to perform optical calibration of video-camera-based optoelectronic sensor systems that will be used to guide automated rendezvous maneuvers of spacecraft. The function of the robot is to move a target and hold it at specified positions. With the help of limit switches, the software first centers or finds the target. Then the target is moved to a starting position. Thereafter, with the help of an intuitive graphical user interface, an operator types in coordinates of specified positions, and the software responds by commanding the robot to move the target to the positions. The software has capabilities for correcting errors and for recording data from the guidance-sensor system being calibrated. The software can also command that the target be moved in a predetermined sequence of motions between specified positions and can be run in an advanced control mode in which, among other things, the target can be moved beyond the limits set by the limit switches.

Johnston, Albert↗

Mission and Navigation Design for the 2009 Mars Science Laboratory Mission

NASA s Mars Science Laboratory mission will launch the next mobile science laboratory to Mars in the fall of 2009 with arrival at Mars occurring in the summer of 2010. A heat shield, parachute, and rocket-powered descent stage, including a sky crane, will be used to land the rover safely on the surface of Mars. The direction of the atmospheric entry vehicle lift vector will be controlled by a hypersonic entry guidance algorithm to compensate for entry trajectory errors and counteract atmospheric and aerodynamic dispersions. The key challenges for mission design are (1) develop a launch/arrival strategy that provides communications coverage during the Entry, Descent, and Landing phase either from an X-band direct-to-Earth link or from a Ultra High Frequency link to the Mars Reconnaissance Orbiter for landing latitudes between 30 deg North and 30 deg South, while satisfying mission constraints on Earth departure energy and Mars atmospheric entry speed, and (2) generate Earth-departure targets for the Atlas V-541 launch vehicle for the specified launch/arrival strategy. The launch/arrival strategy employs a 30-day baseline launch period and a 27-day extended launch period with varying arrival dates at Mars. The key challenges for navigation design are (1) deliver the spacecraft to the atmospheric entry interface point (Mars radius of 3522.2 km) with an inertial entry flight path angle error of +/- 0.20 deg (3 sigma), (2) provide knowledge of the entry state vector accurate to +/- 2.8 km (3 sigma) in position and +/- 2.0 m/s (3 sigma) in velocity for initializing the entry guidance algorithm, and (3) ensure a 99% probability of successful delivery at Mars with respect to available cruise stage propellant. Orbit determination is accomplished via ground processing of multiple complimentary radiometric data types: Doppler, range, and Delta-Differential One-way Ranging (a Very Long Baseline Interferometry measurement). The navigation strategy makes use of up to five interplanetary trajectory correction maneuvers to achieve entry targeting requirements. The requirements for cruise propellant usage and atmospheric entry targeting and knowledge are met with ample margins.

Mission design↗

Using the cFS Command and Data Dictionary (CCDD) to Automate Software Development on Habulous

Final paper is attached. The NASA developed Core Flight System (cFS) is a reusable software architecture that has been used on multiple spaceflight missions. By using this framework, missions are able to reuse code from other missions, as well as leverage deployment onto similar computer architectures (i.e. not "reinvent the wheel" on each new mission). The success in the cFS concept can be seen in the large number of projects using cFS at FSW-2018. The Habulous project is an Earth-based testbed, used for hardware and software that may one day be used on a future space habitat unit, with many participating groups from various NASA centers and aerospace organizations around the country. The distributed nature of the various teams mean that defining (and following) an interface definition is critical on the project. Additionally, since various groups use various types of computer hardware (32/64-bit, big/little endian, Linux/VxWorks/Windows) many additional complications exist in interfacing all the various components into a final integrated system. cFS is used on the majority the flight software (FSW) in running in Habulous. But some subsystems have elected to not use cFS, and use a software bridge (called SBN_lib) to interact with the other cFS nodes in Habulous. In order to most efficiently develop the FSW, a central database is used to define and store each message sent by cFS. A Command and Data Dictionary (CDD) is something nearly universal on spacecraft, but as a team we worked to develop the CDD before the SW development was complete, and not treat it like "as built" documentation. To manage the CDD, the cFS Command and Data Dictionary (CCDD) tool was chosen (available from NASA as open source software). The CCDD tool has successfully been used to automate/autocode a large amount of software used on Habulous, as we are hoping to use it to define even more items in the future (time-triggered Ethernet (TTE) network maps, CPU scheduling). Additionally, Habulous has been exploring the use of cFS on wildly heterogeneous CPUs, and how to coordinate all those various machines using/extending the software bus – network (SBN) application in cFS, as well as TTE to coordinate message passing between various synchronized machines. The major topics to be covered in the presentation are: (1) Updating to the CCSDS_v2 extended headers (and using CPU# as subsystem ID). (2) Managing all the message identification numbers for each cFS message sent/received on any of the various CPUs. (3) Using the CCDD information to automatically generate the C-header files that define the structure for all software bus (SB) commands/telemetry messages. (4) Using the CCDD to automatically generate XML Telemetry and Command Exchange (XTCE) files, which streams display production/integration/testing in a web based display architecture (5) Extending/customizing SBN to pass messages among computers on multiple networks. (6) Using "Protobetter" inside SBN to manage different endian-ness/architectures. (7) Using SBN_lib to allow non-cFS node to communicate with cFS nodes. (8) Developing TTE network and schedule tables for all the various CPUs to use.

Hirsh, Robert L.↗

Secure Web-based Ground System User Interfaces over the Open Internet

A prototype has been developed which makes use of commercially available products in conjunction with the Java programming language to provide a secure user interface for command and control over the open Internet. This paper reports successful demonstration of: (1) Security over the Internet, including encryption and certification; (2) Integration of Java applets with a COTS command and control product; (3) Remote spacecraft commanding using the Internet. The Java-based Spacecraft Web Interface to Telemetry and Command Handling (Jswitch) ground system prototype provides these capabilities. This activity demonstrates the use and integration of current technologies to enable a spacecraft engineer or flight operator to monitor and control a spacecraft from a user interface communicating over the open Internet using standard World Wide Web (WWW) protocols and commercial off-the-shelf (COTS) products. The core command and control functions are provided by the COTS Epoch 2000 product. The standard WWW tools and browsers are used in conjunction with the Java programming technology. Security is provided with the current encryption and certification technology. This system prototype is a step in the direction of giving scientist and flight operators Web-based access to instrument, payload, and spacecraft data.

Langston, James H.↗

The Microgravity Science Glovebox (MSG), a Resource for Gravity-Dependent Phenomena Research on the International Space Station (ISS)

The Microgravity Science Glovebox (MSG) is a double rack facility aboard the International Space Station (ISS) designed for gravity-dependent phenomena investigation handling. The MSG has been operating in the ISS US Laboratory Module since July 2002. The MSG facility provides an enclosed working area for investigation manipulation and observation in the ISS. The MSG's unique design provides two levels of containment to protect the ISS crew from hazardous operations. Research investigations operating inside the MSG are provided a large 255 liter work volume, 1000 watts of dc power via a versatile supply interface (120,28, plus or minus 12, and 5 Vdc), 1000 watts of cooling capability, video and data recording and real time downlink, ground commanding capabilities, access to ISS Vacuum Exhaust' and Vacuum Resource 'Systems, and gaseous nitrogen supply. With these capabilities, the MSG is an ideal platform for research required to advance the technology readiness levels (TRL) needed for the Crew Exploration Vehicle and the Exploration Initiative. Areas of research that will benefit from investigations in the MSG include thermal management, fluid physics, spacecraft fire safety, materials science, combustion and reacting control systems, in situ fabrication and repair, and advanced life support technologies. This paper will provide a detailed explanation of the MSG facility, a synopsis of the research that has already been accomplished in the MSG, an overview of investigations planning to operate in the MSG, and possible augmentations that can be added to-the MSG facility to further enhance the resources provided to investigations.

Spivey, Reggie A.↗

Low Impact Docking System (LIDS)

Since 1996, NASA has been developing a docking system that will simplify operations and reduce risks associated with mating spacecraft. This effort has focused on developing and testing an original, reconfigurable, active, closed-loop, force-feedback controlled docking system using modern technologies. The primary objective of this effort has been to design a docking interface that is tunable to the unique performance requirements for all types of mating operations (i.e. docking and berthing, autonomous and piloted rendezvous, and in-space assembly of vehicles, modules and structures). The docking system must also support the transfer of crew, cargo, power, fluid, and data. As a result of the past 10 years of docking system advancement, the Low Impact Docking System or LIDS was developed. The current LIDS design incorporates the lessons learned and development experiences from both previous and existing docking systems. LIDS feasibility was established through multiple iterations of prototype hardware development and testing. Benefits of LIDS include safe, low impact mating operations, more effective and flexible mission implementation with an anytime/anywhere mating capability, system level redundancy, and a more affordable and sustainable mission architecture with reduced mission and life cycle costs. In 1996 the LIDS project, then known as the Advanced Docking Berthing System (ADBS) project, launched a four year developmental period. At the end of the four years, the team had built a prototype of the soft-capture hardware and verified the control system that will be used to control the soft-capture system. In 2001, the LIDS team was tasked to work with the X- 38 Crew Return Vehicle (CRV) project and build its first Engineering Development Unit (EDU).

LaBauve, Tobie E.↗

A packet switched communications system for GRO

This paper describes the packet switched Instrumenters Communication System (ICS) that was developed for the Command Management Facility at GSFC to support the Gamma Ray Observatory (GRO) spacecraft. The GRO ICS serves as a vital science data acquisition link to the GRO scientists to initiate commands for their spacecraft instruments. The system is ready to send and receive messages at any time, 24 hours a day and seven days a week. The system is based on X.25 and the International Standard Organization's (ISO) 7-layer Open Systems Interconnection (OSI) protocol model and has client and server components. The components of the GRO ICS are discussed along with how the Communications Subsystem for Interconnection (CSFI) and Network Control Program Packet Switching Interface (NPSI) software are used in the system.

Husain, Shabu↗

Development and Testing of Automatically Generated ACS Flight Software for the MAP Spacecraft

By integrating the attitude determination and control system (ACS) analysis and design, flight software development, and flight software testing processes, it is possible to improve the overall spacecraft development cycle, as well as allow for more thorough software testing. One of the ways to achieve this integration is to use code-generation tools to automatically generate components of the ACS flight software directly from a high-fidelity (HiFi) simulation. In the development of the Microwave Anisotropy Probe (MAP) spacecraft, currently underway at the NASA Goddard Space Flight Center, approximately 1/3 of the ACS flight software was automatically generated. In this paper, we will examine each phase of the ACS subsystem and flight software design life cycle: analysis, design, and testing. In the analysis phase, we scoped how much software we would automatically generate and created the initial interface. The design phase included parallel development of the HiFi simulation and the hand-coded flight software components. Everything came together in the test phase, in which the flight software was tested, using results from the HiFi simulation as one of the bases of comparison for testing. Because parts of the spacecraft HiFi simulation were converted into flight software, more care needed to be put into its development and configuration control to support both the HiFi simulation and flight software. The components of the HiFi simulation from which code was generated needed to be designed based on the fact that they would become flight software. This process involved such considerations as protecting against mathematical exceptions, using acceptable module and parameter naming conventions, and using an input/output interface compatible with the rest of the flight software. Maintaining good configuration control was an issue for the HiFi simulation and the flight software, and a way to track the two systems was devised. Finally, an integrated test approach was devised to support flight software testing at both the unit- and build-test levels using the HiFi simulation to generate data for performance verification. Another benefit of the simulation and code-generation application used on the MAP project is that it supported bringing flight software and test data into the HiFi simulation environment. It was possible to integrate parts of the hand-coded flight software into the HiFi simulation, and also possible to import flight software test data for comparison and performance verification. This capability was used to incorporate the flight software Kalman filter into the HiFi simulation. This enabled us to greatly increase the amount of testing that could be done on the filter, because we could exert a greater degree of control over the software-only simulation than over the flight software test environment. Also, since the simulation could be used to run the Kalman filter faster than real time, our testing efficiency was greatly increased. We will conclude our discussion with a summary of the lessons learned thus far using automatically- generated code for the MAP project, and the spacecraft status as we work towards our scheduled launch in the year 2000.

ODonnell, James R., Jr.↗

Space-borne computing for the year 2000 and beyond

The influence and utilization of computers in space science investigations greatly enhances the ability to address difficult and complicated questions about the Universe. Space Science is wholly dependent on computers because the data acquired from instruments on the spacecraft are not only complicated in form but also voluminous. Athough a great deal of attention has been paid to develop efficient and powerful computing systems on-ground, research in the area of spaceborne computing is far from satisfactory. On-board processing of data will be important in future planetary missions where telemetry rates constrain the total amount of data which can be returned and decisions may have to be made in real time. Little thought has been given to a dynamic man-machine interface with regard to scientific real-time interactive control of flight experiments. Careful thinking is therefore essential to define appropriate spaceborne computing requirements for the future. It is imperative that powerful multiprocessing systems for on-board processing be experimentally impleneted and evaluated in selected application missions. The presentation addresses key issues and attempts to define the requirements for such processing with some of NASA's future missions in perspective. The resulting architectural and performance issues and possible developments are also addressed.

Iyer, Ravi K.↗

An Independent Orbit Determination Simulation for the OSIRIS-REx Asteroid Sample Return Mission

After arriving at the near-Earth asteroid (101955) Bennu in late 2018, the OSIRIS-REx spacecraft will execute a series of observation campaigns and orbit phases to accurately characterize Bennu and ultimately collect a sample of pristine regolith from its surface. While in the vicinity of Bennu, the OSIRIS-REx navigation team will rely on a combination of ground-based radiometric tracking data and optical navigation (OpNav) images to generate and deliver precision orbit determination products. Long before arrival at Bennu, the navigation team is performing multiple orbit determination simulations and thread tests to verify navigation performance and ensure interfaces between multiple software suites function properly. In this paper, we will summarize the results of an independent orbit determination simulation of the Orbit B phase of the mission performed to test the interface between the OpNav image processing and orbit determination software packages.

Orbit↗

Rest architecture for link analysis tools portal

A web portal is under development to improve overall services provided by NASA networks that support near-­‐Earth missions. These networks are managed by Space Communication and Navigation (SCaN) Program of NASA and include the following: Deep Space Network (DSN), Space Network (SN), and Near-­‐Earth Network (NEN). DSN is a network of antennas located in three longitudinally separated sites and supports interplanetary spacecraft missions, radio science, and radar astronomy observations. SN consists of a number of geostationary Tracking and Data Relay Satellites (TDRS) and associated ground stations. NEN consists of both NASA-­‐owned ground stations and those owned by international, commercial, and academic partners. This study investigates different web access techniques for mission users to use link analysis tools that aid in operating NASA networks. We developed a web portal prototype following principles of Representational state transfer (REST) architecture to leverage scalability, independent deployment of tools, and generic interfaces. In REST architectures, requests and responses between clients and servers are built around transferring representations of resources that can be addressed in memory. We demonstrate the feasibility of using REST architecture to facilitate web-­‐service transactions via web-­‐portal.

Lee, Carlyn-­‐Ann↗

Concept of Operations for OSIRIS-REx Optical Navigation Image Planning

Optical navigation (OpNav) is a critical subsystem of the OSIRIS-REx asteroid sample return mission, which operated in the vicinity of near-Earth asteroid (101955) Bennu from August 2018 through April 2021. A substantial amount of mission resources across multiple subsystems and institutions is required to ensure that the OpNav data are successfully acquired. The KinetX OpNav team, part of the Flight Dynamics System (FDS), is responsible for performing required analysis to develop the OpNav operations plans; requesting, reviewing and verifying the plans; and ultimately using the image data for critical navigation operations. The FDS team, responsible for the mission navigation, is operated by KinetX Aerospace with management and operations support from NASA’s Goddard Space Flight Center. The Science Processing and Operations Center (SPOC), located at the University of Arizona’s Lunar and Planetary Laboratory, is responsible for generating the planning products for all science and most OpNav data. These plans are integrated into the spacecraft sequences, tested, and commanded by the Mission Support Area (MSA) at Lockheed Martin Space. To ensure mission-critical navigation image data are successfully acquired, the plan is developed through a waterfall of planning cycles over the course of 3 months prior to onboard plan execution. During the initial strategic planning for a mission phase, detailed analysis is performed by the OpNav team to conceptualize the concept of operations (ConOps) for image data collection. This phase OpNav Narrative is included along with other strategic planning documents for the key ground segment stakeholders to review and provide feedback. The detailed OpNav plans get defined in the tactical planning cycle, which spans 8 to 3 weeks before the week-long integrated sequence is executed on-board the spacecraft. During the tactical cycle, the initial OpNav Request is submitted along with the science requests, kicking off development of the science and OpNav plans. Once the initial plan is drafted, interfaces are exercised so that the plan can be reviewed and iterated, if necessary. A rigorous schedule is followed by the planning teams during the implementation cycle, spanning the last 18 days before uplink, to ensure all the necessary integration, testing, and reviewing can occur on time. The development of the OpNav planning ConOps, including responsibilities, interfaces, timelines, and procedures, took extensive collaboration across mission elements and institutions. The process was robust throughout the 137 weeks of continuous Optical Navigation Operations at Bennu, which concluded on April 9th, 2021.

Coralie D. Adam↗