Search NASA⌕ Search

SEARCH · Search NASA

Results for “adaptive structures response to external stimulation remote or automatic command”

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 73 records · Page 4
All sourcesNASA NTRSDOE OSTI
NASA NTRS2011

MSLICE Sequencing

MSLICE Sequencing is a graphical tool for writing sequences and integrating them into RML files, as well as for producing SCMF files for uplink. When operated in a testbed environment, it also supports uplinking these SCMF files to the testbed via Chill. This software features a free-form textural sequence editor featuring syntax coloring, automatic content assistance (including command and argument completion proposals), complete with types, value ranges, unites, and descriptions from the command dictionary that appear as they are typed. The sequence editor also has a "field mode" that allows tabbing between arguments and displays type/range/units/description for each argument as it is edited. Color-coded error and warning annotations on problematic tokens are included, as well as indications of problems that are not visible in the current scroll range. "Quick Fix" suggestions are made for resolving problems, and all the features afforded by modern source editors are also included such as copy/cut/paste, undo/redo, and a sophisticated find-and-replace system optionally using regular expressions. The software offers a full XML editor for RML files, which features syntax coloring, content assistance and problem annotations as above. There is a form-based, "detail view" that allows structured editing of command arguments and sequence parameters when preferred. The "project view" shows the user s "workspace" as a tree of "resources" (projects, folders, and files) that can subsequently be opened in editors by double-clicking. Files can be added, deleted, dragged-dropped/copied-pasted between folders or projects, and these operations are undoable and redoable. A "problems view" contains a tabular list of all problems in the current workspace. Double-clicking on any row in the table opens an editor for the appropriate sequence, scrolling to the specific line with the problem, and highlighting the problematic characters. From there, one can invoke "quick fix" as described above to resolve the issue. Once resolved, saving the file causes the problem to be removed from the problem view.

Crockett, Thomas M.↗
NASA NTRS2008

ATHLETE's Feet: Mu1ti-Resolution Planning for a Hexapod Robot

ATHLETE is a large six-legged tele-operated robot. Each foot is a wheel; travel can be achieved by walking, rolling, or some combination of the two. Operators control ATHLETE by selecting parameterized commands from a command dictionary. While rolling can be done efficiently with a single command, any motion involving steps is cumbersome - walking a few meters through difficult terrain can take hours. Our goal is to improve operator efficiency by automatically generating sequences of motion commands. There is increasing uncertainty regarding ATHLETE s actual configuration over time and decreasing quality of terrain data farther away from the current position. This, combined with the complexity that results from 36 degrees of kinematic freedom, led to an architecture that interleaves planning and execution at multiple levels, ranging from traditional configuration space motion planning algorithms for immediate moves to higher level task and path planning algorithms for overall travel. The modularity of the architecture also simplifies the development process and allows the operator to interact with and control the system at varying levels of autonomy depending on terrain and need.

Smith, Tristan B.↗
NASA NTRS2012

Rapid Diagnostics of Onboard Sequences

Keeping track of sequences onboard a spacecraft is challenging. When reviewing Event Verification Records (EVRs) of sequence executions on the Mars Exploration Rover (MER), operators often found themselves wondering which version of a named sequence the EVR corresponded to. The lack of this information drastically impacts the operators diagnostic capabilities as well as their situational awareness with respect to the commands the spacecraft has executed, since the EVRs do not provide argument values or explanatory comments. Having this information immediately available can be instrumental in diagnosing critical events and can significantly enhance the overall safety of the spacecraft. This software provides auditing capability that can eliminate that uncertainty while diagnosing critical conditions. Furthermore, the Restful interface provides a simple way for sequencing tools to automatically retrieve binary compiled sequence SCMFs (Space Command Message Files) on demand. It also enables developers to change the underlying database, while maintaining the same interface to the existing applications. The logging capabilities are also beneficial to operators when they are trying to recall how they solved a similar problem many days ago: this software enables automatic recovery of SCMF and RML (Robot Markup Language) sequence files directly from the command EVRs, eliminating the need for people to find and validate the corresponding sequences. To address the lack of auditing capability for sequences onboard a spacecraft during earlier missions, extensive logging support was added on the Mars Science Laboratory (MSL) sequencing server. This server is responsible for generating all MSL binary SCMFs from RML input sequences. The sequencing server logs every SCMF it generates into a MySQL database, as well as the high-level RML file and dictionary name inputs used to create the SCMF. The SCMF is then indexed by a hash value that is automatically included in all command EVRs by the onboard flight software. Second, both the binary SCMF result and the RML input file can be retrieved simply by specifying the hash to a Restful web interface. This interface enables command line tools as well as large sophisticated programs to download the SCMF and RMLs on-demand from the database, enabling a vast array of tools to be built on top of it. One such command line tool can retrieve and display RML files, or annotate a list of EVRs by interleaving them with the original sequence commands. This software has been integrated with the MSL sequencing pipeline where it will serve sequences useful in diagnostics, debugging, and situational awareness throughout the mission.

Starbird, Thomas W.↗
NASA NTRS1973

Studies to design and develop improved remote manipulator systems

Remote manipulator control considered is based on several levels of automatic supervision which derives manipulator commands from an analysis of sensor states and task requirements. Principle sensors are manipulator joint position, tactile, and currents. The tactile sensor states can be displayed visually in perspective or replicated in the operator's control handle of perceived by the automatic supervisor. Studies are reported on control organization, operator performance and system performance measures. Unusual hardware and software details are described.

Hill, J. W.↗
NASA NTRS1986

Nonlinear interfaces for acceleration-commanded control of spacecraft and manipulators

Nominal command generation in real time for the control of manipulators or of maneuvering spacecraft is hampered by the nonlinearity of the equations of motion. Likewise the real time tracking of a computed nominal trajectory in the presence of disturbances requires the computation of time-varying Jacobians of the motion. An alternative approach is the formulation of acceleration-commanded control laws in appropriately chosen generalized advantageous to design dedicated circuit interfaces to perform the required transformation. It is also possible to guarantee that actuator and sensor saturation limits are not exceeded, by means of feedback-biased circuits that implement automatic overload limitation of acceleration commands. Recent developments following this 'hardware computation' point of view will be discussed.

Dwyer, T. A. W., III↗
NASA NTRS2011

Flight Dynamics Aspects of a Large Civil Tiltrotor Simulation Using Translational Rate Command

An in-depth analysis of a Large Civil Tiltrotor simulation with a Translational Rate Command control law that uses automatic nacelle deflections for longitudinal velocity control and lateral cyclic for lateral velocity control is presented. Results from piloted real-time simulation experiments and offline time and frequency domain analyses are used to investigate the fundamental flight dynamic and control mechanisms of the control law. The baseline Translational Rate Command conferred handling qualities improvements over an attitude command attitude hold control law but in some scenarios there was a tendency to enter PIO. Nacelle actuator rate limiting strongly influenced the PIO tendency and reducing the rate limits degraded the handling qualities further. Counterintuitively, increasing rate limits also led to a worsening of the handling qualities ratings. This led to the identification of a nacelle rate to rotor longitudinal flapping coupling effect that induced undesired pitching motions proportional to the allowable amount of nacelle rate. A modification that applied a counteracting amount of longitudinal cyclic proportional to the nacelle rate significantly improved the handling qualities. The lateral axis of the Translational Rate Command conferred Level 1 handling qualities in a Lateral Reposition maneuver. Analysis of the influence of the modeling fidelity on the lateral flapping angles is presented. It is showed that the linear modeling approximation is likely to have under-predicted the side-force and therefore under-predicted the lateral flapping at velocities above 15 ft/s. However, at lower velocities, and therefore more weakly influenced by the side force modeling, the accelerations that the control law commands also significantly influenced the peak levels of lateral flapping achieved.

Lawrence, Ben↗
NASA NTRS1972

Design and development of a brushless, direct drive solar array reorientation system

This report covers the design and development of the laboratory model, and is essentially a compilation of reports covering the system and its various parts. To enhance completeness, the final report of Phase 1 covering circuit development of the controller is also included. A controller was developed for a brushless, direct-drive, single axis solar array reorientation system for earth-pointed, passively-stabilized spacecraft. A control systems was designed and breadboard circuits were built and tested for performance. The controller is designed to take over automatic control of the array on command after the spacecraft is stabilized in orbit. The controller will orient the solar array to the sun vector and automatically track to maintain proper orientation. So long as the orbit is circular, orientation toward the sun is maintained even though the spacecraft goes into the shadow of the earth. Particular attention was given in the design to limit reaction between the array and the spacecraft.

Jessee, R. D.↗
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 NTRS2013

Evaluation of Flight Deck-Based Interval Management Crew Procedure Feasibility

Air traffic demand is predicted to increase over the next 20 years, creating a need for new technologies and procedures to support this growth in a safe and efficient manner. The National Aeronautics and Space Administration's (NASA) Air Traffic Management Technology Demonstration - 1 (ATD-1) will operationally demonstrate the feasibility of efficient arrival operations combining ground-based and airborne NASA technologies. The integration of these technologies will increase throughput, reduce delay, conserve fuel, and minimize environmental impacts. The ground-based tools include Traffic Management Advisor with Terminal Metering for precise time-based scheduling and Controller Managed Spacing decision support tools for better managing aircraft delay with speed control. The core airborne technology in ATD-1 is Flight deck-based Interval Management (FIM). FIM tools provide pilots with speed commands calculated using information from Automatic Dependent Surveillance - Broadcast. The precise merging and spacing enabled by FIM avionics and flight crew procedures will reduce excess spacing buffers and result in higher terminal throughput. This paper describes a human-in-the-loop experiment designed to assess the acceptability and feasibility of the ATD-1 procedures used in a voice communications environment. This experiment utilized the ATD-1 integrated system of ground-based and airborne technologies. Pilot participants flew a high-fidelity fixed base simulator equipped with an airborne spacing algorithm and a FIM crew interface. Experiment scenarios involved multiple air traffic flows into the Dallas-Fort Worth Terminal Radar Control airspace. Results indicate that the proposed procedures were feasible for use by flight crews in a voice communications environment. The delivery accuracy at the achieve-by point was within +/- five seconds and the delivery precision was less than five seconds. Furthermore, FIM speed commands occurred at a rate of less than one per minute, and pilots found the frequency of the speed commands to be acceptable at all times throughout the experiment scenarios.

Wilson, Sara R.↗
NASA NTRS1980

Precision controllability of the YF-17 airplane

A flying qualities evaluation conducted on the YF-17 airplane permitted assessment of its precision controllability in the transonic flight regime over the allowable angle of attack range. The precision controllability (tailchase tracking) study was conducted in constant-g and windup turn tracking maneuvers with the command augmentation system (CAS) on, automatic maneuver flaps, and the caged pipper gunsight depressed 70 mils. This study showed that the YF-17 airplane tracks essentially as well at 7 g's to 8 g's as earlier fighters did at 4 g's to 5 g's before they encountered wing rock. The pilots considered the YF-17 airplane one of the best tracking airplanes they had flown. Wing rock at the higher angles of attack degraded tracking precision, and lack of control harmony made precision controllability more difficult. The revised automatic maneuver flap schedule incorporated in the airplane at the time of the tests did not appear to be optimum. The largest tracking errors and greatest pilot workload occurred at high normal load factors at low angles of attack. The pilots reported that the high-g maneuvers caused some tunnel vision and that they found it difficult to think clearly after repeated maneuvers.

Sisk, T. R.↗
NASA NTRS1989

Closed-Loop Motor-Speed Control

Electronic motor-speed control circuit designed to operate in electrically noisy environment. Includes optoelectronic pick-up device, placed inside motor housing to provide speed feedback signal. Automatically maintains speed motor at commanded value. Measures speed of motor in terms of frequency of pulses of infrared light chopped by fan blades of motor. Difference between measured and commanded speeds serves as control signal for external amplifier driving motor. Major advantage of circuit is low cost.

Smith, Matthew A.↗
NASA NTRS1987

Automatically reconfigurable control for rapid retargeting of flexible pointing systems

A reconfigurable nonlinear control system design methodology is proposed to automatically correct computed slew torque commands of space-based pointing systems for the effects of slew-induced structural deformations. The possibility of forcing an elastic structure, such as that of a space-based instrument frame, to deform in a preselected way in response to rapid slews is demonstrated. To accomplish this, a supervisory controller must select a pair of algorithms, one for structural counterexcitation and the other for slew torque correction. It is shown how the reachability and subsequent tracking of the appropriate 'slow manifold', where the control algorithms are valid, can be ensured by a fast tracking loop, with time-varying gain dependent only on the commanded angular acceleration.

Dwyer, Thomas A. W., III↗
NASA NTRS2000

Agent Building Software

AgentBuilder is a software component developed under an SBIR contract between Reticular Systems, Inc., and Goddard Space Flight Center. AgentBuilder allows software developers without experience in intelligent agent technologies to easily build software applications using intelligent agents. Agents are components of software that will perform tasks automatically, with no intervention or command from a user. AgentBuilder reduces the time and cost of developing agent systems and provides a simple mechanism for implementing high-performance agent systems.

Source record↗
NASA NTRS2001

A tool for autonomous ground-based rover planning

This paper discusses a proof-of-concept prototype for ground-based automatic generation of validated rover command sequences from high-level science and engineering activities.

automated planning scheduling rover operations art↗
NASA NTRS2010

An Introduction to Sked

In this note I give an overview of the VLBI scheduling software sked. I describe some of the algorithms used in automatic scheduling and some sked commands which have been introduced at users requests. I also give a cookbook for generating some schedules.

Gipson, John↗
NASA NTRS2005

Rover Sequencing and Visualization Program

The Rover Sequencing and Visualization Program (RSVP) is the software tool for use in the Mars Exploration Rover (MER) mission for planning rover operations and generating command sequences for accomplishing those operations. RSVP combines three-dimensional (3D) visualization for immersive exploration of the operations area, stereoscopic image display for high-resolution examination of the downlinked imagery, and a sophisticated command-sequence editing tool for analysis and completion of the sequences. RSVP is linked with actual flight-code modules for operations rehearsal to provide feedback on the expected behavior of the rover prior to committing to a particular sequence. Playback tools allow for review of both rehearsed rover behavior and downlinked results of actual rover operations. These can be displayed simultaneously for comparison of rehearsed and actual activities for verification. The primary inputs to RSVP are downlink data products from the Operations Storage Server (OSS) and activity plans generated by the science team. The activity plans are high-level goals for the next day s activities. The downlink data products include imagery, terrain models, and telemetered engineering data on rover activities and state. The Rover Sequence Editor (RoSE) component of RSVP performs activity expansion to command sequences, command creation and editing with setting of command parameters, and viewing and management of rover resources. The HyperDrive component of RSVP performs 2D and 3D visualization of the rover s environment, graphical and animated review of rover-predicted and telemetered state, and creation and editing of command sequences related to mobility and Instrument Deployment Device (IDD) operations. Additionally, RoSE and HyperDrive together evaluate command sequences for potential violations of flight and safety rules. The products of RSVP include command sequences for uplink that are stored in the Distributed Object Manager (DOM) and predicted rover state histories stored in the OSS for comparison and validation of downlinked telemetry. The majority of components comprising RSVP utilize the MER command and activity dictionaries to automatically customize the system for MER activities. Thus, RSVP, being highly data driven, may be tailored to other missions with minimal effort. In addition, RSVP uses a distributed, message-passing architecture to allow multitasking, and collaborative visualization and sequence development by scattered team members.

Cooper, Brian↗
NASA NTRS2005

Update on Rover Sequencing and Visualization Program

The Rover Sequencing and Visualization Program (RSVP) has been updated. RSVP was reported in Rover Sequencing and Visualization Program (NPO-30845), NASA Tech Briefs, Vol. 29, No. 4 (April 2005), page 38. To recapitulate: The Rover Sequencing and Visualization Program (RSVP) is the software tool to be used in the Mars Exploration Rover (MER) mission for planning rover operations and generating command sequences for accomplishing those operations. RSVP combines three-dimensional (3D) visualization for immersive exploration of the operations area, stereoscopic image display for high-resolution examination of the downlinked imagery, and a sophisticated command-sequence editing tool for analysis and completion of the sequences. RSVP is linked with actual flight code modules for operations rehearsal to provide feedback on the expected behavior of the rover prior to committing to a particular sequence. Playback tools allow for review of both rehearsed rover behavior and downlinked results of actual rover operations. These can be displayed simultaneously for comparison of rehearsed and actual activities for verification. The primary inputs to RSVP are downlink data products from the Operations Storage Server (OSS) and activity plans generated by the science team. The activity plans are high-level goals for the next day s activities. The downlink data products include imagery, terrain models, and telemetered engineering data on rover activities and state. The Rover Sequence Editor (RoSE) component of RSVP performs activity expansion to command sequences, command creation and editing with setting of command parameters, and viewing and management of rover resources. The HyperDrive component of RSVP performs 2D and 3D visualization of the rover s environment, graphical and animated review of rover predicted and telemetered state, and creation and editing of command sequences related to mobility and Instrument Deployment Device (robotic arm) operations. Additionally, RoSE and HyperDrive together evaluate command sequences for potential violations of flight and safety rules. The products of RSVP include command sequences for uplink that are stored in the Distributed Object Manager (DOM) and predicted rover state histories stored in the OSS for comparison and validation of downlinked telemetry. The majority of components comprising RSVP utilize the MER command and activity dictionaries to automatically customize the system for MER activities.

Cooper, Brian↗
NASA NTRS2012

Mini AERCam for In-Space Inspection

The NASA Johnson Space Center Engineering Directorate has developed the Miniature Autonomous Extravehicular Robotic Camera (Mini AERCam) as a free-flying, robotic inspection vehicle intended for future external inspection and remote viewing of human spacecraft. The Mini AERCam technology demonstration unit has been successfully integrated into the approximate form and function of a nanosatellite flight system by leveraging the success of AERCam Sprint flight system and related free-flyer technology development. The Mini AERCam free flyer can be operated via remote piloting from a control station supporting teleoperation and supervised autonomous commanding, with functions such as automatic stationkeeping, point-to-point maneuvering, and automatic docking. Free-flyer testing has been conducted on an air-bearing table and in a six degree-of-freedom closed-loop orbital simulation, and enhancements have been made to provide additional capabilities for future space-based inspection. This presentation will provide a technical overview of the Mini AERCam development, including strategies for spacecraft integration.

Fredrickson, Steven E.↗