Engineering topics
Verma, Vandi
Publications and source records attributed to Verma, Vandi.
Autonomous Science Restart for the Planned Europa Mission with Lightweight Planning and Execution
In this paper we present MEXEC - a lightweight on-board planning and execution system that monitors spacecraft state to robustly respond to current conditions. In addition it projects the remaining plan forward in time to detect conflicts and revise the plan. Most current planetary missions use sequence based commanding from the ground,which limits the ability to respond to on-board state varying from planned for state. This results in planning for worst-case execution time, power utilization, data volume and other resources and leads to under utilization of the spacecraft capability. It also limits the ability to respond to faults. Due to the high radiation environment at Jupiter the probability of flight software resets is high. Therefore, of particular interest to the planned Europa Mission is the capability to restart the science plan after flight software resets. In this paper we present results from running Europa flyby scenarios with flight software resets in the Europa flight software test environment. Preliminary results with the prototype scenario show MEXEC takes less than a tenth of a second to respond to resets. The development was done as part of Europa-focused flight software, but MEXEC was designed to be applicable to landers and rovers as well.
Plan Execution Interchange Language (PLEXIL)
Plan execution is a cornerstone of spacecraft operations, irrespective of whether the plans to be executed are generated on board the spacecraft or on the ground. Plan execution frameworks vary greatly, due to both different capabilities of the execution systems, and relations to associated decision-making frameworks. The latter dependency has made the reuse of execution and planning frameworks more difficult, and has all but precluded information sharing between different execution and decision-making systems. As a step in the direction of addressing some of these issues, a general plan execution language, called the Plan Execution Interchange Language (PLEXIL), is being developed. PLEXIL is capable of expressing concepts used by many high-level automated planners and hence provides an interface to multiple planners. PLEXIL includes a domain description that specifies command types, expansions, constraints, etc., as well as feedback to the higher-level decision-making capabilities. This document describes the grammar and semantics of PLEXIL. It includes a graphical depiction of this grammar and illustrative rover scenarios. It also outlines ongoing work on implementing a universal execution system, based on PLEXIL, using state-of-the-art rover functional interfaces and planners as test cases.
Prototype Software for Future Spaceflight Tested at Mars Desert Research Station
NASA scientists in MDRS Crew 49 (April 23-May 7, 2006) field tested and significantly extended a prototype monitoring and advising system that integrates power system telemetry with a voice commanding interface. A distributed, wireless network of functionally specialized agents interacted with the crew to provide alerts (e.g., impending shut-down of inverter due to low battery voltage), access md interpret historical data, and display troubleshooting procedures. In practical application during two weeks, the system generated speech over loudspeakers and headsets lo alert the crew about the need to investigate power system problems. The prototype system adapts the Brahms/Mobile Agents toolkit to receive data from the OneMeter (Brand Electronics) electric metering system deployed by Crew 47. A computer on the upper deck was connected to loudspeakers, four others were paired with wireless (Bluetooth) headsets that enabled crew members to interact with their personal agents from anywhere in the hab. Voice commands and inquiries included: 1. What is the {battery | generator} {volts | amps | volts and amps}? 2. What is the status of the {generator | inverter | battery | solar panel}? 3. What is the hab{itat} {power usage | volts | voltage | amps | volts and amps}? 4. What was the average hab{itat} {amps | volts | voltage} since <#> {AM | PM)? 5. When did the {generator | batteries} change status? 6. Tell {me I | everyone} when{ ever} the generator goes offline. 7. Tell {me | | everyone} when the hab{itat} {amps | volts | voltage} {exceeds | drops brelow} <#>. 8. {Send | Take | Record} {a} voice note {(for | to} } {at }. This research demonstrates the principles of design in the context of use, investigating requirements through experimental use of prototype systems in an analog setting, and use of MDRS as a research facility for designing and implementing new systems.
Survey of Command Execution Systems for NASA Spacecraft and Robots
NASA spacecraft and robots operate at long distances from Earth Command sequences generated manually, or by automated planners on Earth, must eventually be executed autonomously onboard the spacecraft or robot. Software systems that execute commands onboard are known variously as execution systems, virtual machines, or sequence engines. Every robotic system requires some sort of execution system, but the level of autonomy and type of control they are designed for varies greatly. This paper presents a survey of execution systems with a focus on systems relevant to NASA missions.