Search NASA⌕ Search

Engineering topics

Hirsh, Robert L.

Publications and source records attributed to Hirsh, Robert L..

8 records
All sourcesNASA NTRSDOE OSTI
NASA NTRS2018

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.↗
NASA NTRS2016

Landing Hazard Avoidance Display

Landing hazard avoidance displays can provide rapidly understood visual indications of where it is safe to land a vehicle and where it is unsafe to land a vehicle. Color coded maps can indicate zones in two dimensions relative to the vehicles position where it is safe to land. The map can be simply green (safe) and red (unsafe) areas with an indication of scale or can be a color coding of another map such as a surface map. The color coding can be determined in real time based on topological measurements and safety criteria to thereby adapt to dynamic, unknown, or partially known environments.

Abernathy, Michael Franklin↗
NASA NTRS2015

Interfacing and Verifying ALHAT Safe Precision Landing Systems with the Morpheus Vehicle

The NASA Autonomous precision Landing and Hazard Avoidance Technology (ALHAT) project developed a suite of prototype sensors to enable autonomous and safe precision landing of robotic or crewed vehicles under any terrain lighting conditions. Development of the ALHAT sensor suite was a cross-NASA effort, culminating in integration and testing on-board a variety of terrestrial vehicles toward infusion into future spaceflight applications. Terrestrial tests were conducted on specialized test gantries, moving trucks, helicopter flights, and a flight test onboard the NASA Morpheus free-flying, rocket-propulsive flight-test vehicle. To accomplish these tests, a tedious integration process was developed and followed, which included both command and telemetry interfacing, as well as sensor alignment and calibration verification to ensure valid test data to analyze ALHAT and Guidance, Navigation and Control (GNC) performance. This was especially true for the flight test campaign of ALHAT onboard Morpheus. For interfacing of ALHAT sensors to the Morpheus flight system, an adaptable command and telemetry architecture was developed to allow for the evolution of per-sensor Interface Control Design/Documents (ICDs). Additionally, individual-sensor and on-vehicle verification testing was developed to ensure functional operation of the ALHAT sensors onboard the vehicle, as well as precision-measurement validity for each ALHAT sensor when integrated within the Morpheus GNC system. This paper provides some insight into the interface development and the integrated-systems verification that were a part of the build-up toward success of the ALHAT and Morpheus flight test campaigns in 2014. These campaigns provided valuable performance data that is refining the path toward spaceflight infusion of the ALHAT sensor suite.

Carson, John M., III↗
NASA NTRS2011

Crew Office Evaluation of a Precision Lunar Landing System

A representative Human System Interface for a precision lunar landing system, ALHAT, has been developed as a platform for prototype visualization and interaction concepts. This facilitates analysis of crew interaction with advanced sensors and AGNC systems. Human-in-the-loop evaluations with representatives from the Crew Office (i.e. astronauts) and Mission Operations Directorate (MOD) were performed to refine the crew role and information requirements during the final phases of landing. The results include a number of lessons learned from Shuttle that are applicable to the design of a human supervisory landing system and cockpit. Overall, the results provide a first order analysis of the tasks the crew will perform during lunar landing, an architecture for the Human System Interface based on these tasks, as well as details on the information needs to land safely.

Major, Laura M.↗
NASA NTRS2011

Developing a Prototype ALHAT Human System Interface for Landing

The goal of the Autonomous Landing and Hazard Avoidance Technology (ALHAT) project is to safely execute a precision landing anytime/anywhere on the moon. This means the system must operate in any lighting conditions, operate in the presence of any thruster generated regolith clouds, and operate without the help of redeployed navigational aids or prepared landing site at the landing site. In order to reach this ambitious goal, computer aided technologies such as ALHAT will be needed in order to permit these landings to be done safely. Although there will be advanced autonomous capabilities onboard future landers, humans will still be involved (either onboard as astronauts or remotely from mission control) in any mission to the moon or other planetary body. Because many time critical decisions must be made quickly and effectively during the landing sequence, the Descent and Landing displays need to be designed to be as effective as possible at presenting the pertinent information to the operator, and allow the operators decisions to be implemented as quickly as possible. The ALHAT project has established the Human System Interface (HSI) team to lead in the development of these displays and to study the best way to provide operators enhanced situational awareness during landing activities. These displays are prototypes that were developed based on multiple design and feedback sessions with the astronaut office at NASA/ Johnson Space Center. By working with the astronauts in a series of plan/build/evaluate cycles, the HSI team has obtained astronaut feedback from the very beginning of the design process. In addition to developing prototype displays, the HSI team has also worked to provide realistic lunar terrain (and shading) to simulate a "out the window" view that can be adjusted to various lighting conditions (based on a desired date/time) to allow the same terrain to be viewed under varying lighting terrain. This capability will be critical to determining the effect of terrain/lighting on the human pilot, and how they use windows and displays during landing activities. The Apollo missions were limited to about 28 possible launch days a year due to lighting and orbital constraints. In order to take advantage of more landing opportunities and venture to more challenging landing locations, future landers will need to utilize sensors besides human eyes for scanning the surface. The ALHAT HSI system must effectively convey ALHAT produced information to the operator, so that landings can occur during less "optimal" conditions (lighting, surface terrain, slopes, etc) than was possible during Apollo missions. By proving this capability, ALHAT will simultaneously provide more flexible access to the moon, and greater safety margins for future landers. This paper will specifically focus on the development of prototype displays (the Trajectory Profile Display (TPD), Landing Point Designation (LPD), and Crew Camera View (CCV) ), implementation of realistic planetary terrain, human modeling, and future HSI plans.

Hirsh, Robert L.↗
NASA NTRS2007

Automating CapCom Using Mobile Agents and Robotic Assistants

Mobile Agents (MA) is an advanced Extra-Vehicular Activity (EVA) communications and computing system to increase astronaut self-reliance and safety, reducing dependence on continuous monitoring and advising from mission control on Earth. MA is voice controlled and provides information verbally to the astronauts through programs called "personal agents." The system partly automates the role of CapCom in Apollo-including monitoring and managing navigation, scheduling, equipment deployment, telemetry, health tracking, and scientific data collection. Data are stored automatically in a shared database in the habitat/vehicle and mirrored to a site accessible by a remote science team. The program has been developed iteratively in authentic work contexts, including six years of ethnographic observation of field geology. Analog field experiments in Utah enabled empirically discovering requirements and testing alternative technologies and protocols. We report on the 2004 system configuration, experiments, and results, in which an EVA robotic assistant (ERA) followed geologists approximately 150 m through a winding, narrow canyon. On voice command, the ERA took photographs and panoramas and was directed to serve as a relay on the wireless network.

Clancey, William J.↗
NASA NTRS2005

Automating CapCom Using Mobile Agents and Robotic Assistants

We have developed and tested an advanced EVA communications and computing system to increase astronaut self-reliance and safety, reducing dependence on continuous monitoring and advising from mission control on Earth. This system, called Mobile Agents (MA), is voice controlled and provides information verbally to the astronauts through programs called personal agents. The system partly automates the role of CapCom in Apollo-including monitoring and managing EVA navigation, scheduling, equipment deployment, telemetry, health tracking, and scientific data collection. EVA data are stored automatically in a shared database in the habitat/vehicle and mirrored to a site accessible by a remote science team. The program has been developed iteratively in the context of use, including six years of ethnographic observation of field geology. Our approach is to develop automation that supports the human work practices, allowing people to do what they do well, and to work in ways they are most familiar. Field experiments in Utah have enabled empirically discovering requirements and testing alternative technologies and protocols. This paper reports on the 2004 system configuration, experiments, and results, in which an EVA robotic assistant (ERA) followed geologists approximately 150 m through a winding, narrow canyon. On voice command, the ERA took photographs and panoramas and was directed to move and wait in various locations to serve as a relay on the wireless network. The MA system is applicable to many space work situations that involve creating and navigating from maps (including configuring equipment for local topology), interacting with piloted and unpiloted rovers, adapting to environmental conditions, and remote team collaboration involving people and robots.

Clancey, William J.↗