Search NASA⌕ Search

Engineering topics

Jeb Orr

Publications and source records attributed to Jeb Orr.

8 records
All sourcesNASA NTRSDOE OSTI
NASA NTRSDate not supplied

Multiple-Effector Control Allocation: Theory and Practice

Redundant controls are ubiquitous in many aerospace domains, including aircraft, spacecraft, and launch vehicles. Multiple control effectors having different capabilities (e.g., reaction controls, aerosurfaces, and vectored engines) must be optimally allocated to achieve high-performance and robust vehicle control, while considering different constraints, cost, or performance metrics associated with various control mixing schemes. These can include force or deflection limits, rate limits, propellant usage or drag penalties, cross-axis coupling, uncertainties, or even servoelastic interactions. This presentation introduces the fundamentals of control allocation theory, based on linear algebra and convex sets, using a handful of examples taken from the air and space vehicle domains. It is shown that even simple methods can provide verifiable and quantifiable performance benefits over ad-hoc approaches, and can support enhanced functions like fault tolerance and control reconfiguration.

Bill Benson↗
NASA NTRSDate not supplied

Gimbal Bearing Friction in the SLS Core Stage Thrust Vector Control System

The Space Launch System (SLS) Core Stage Thrust Vector Control (TVC) system is comprised of eight mechanical feedback Shuttle heritage Type III TVC actuators that vector the four Shuttle heritage RS-25 engines about a Shuttle heritage gimbal block/bearing. The MSFC Controls community has long regarded gimbal friction to be a negligible effect on the overall control of gimbaled RS-25 engines. This is corroborated by Space Shuttle test and flight data that does not appear to show degraded effects, nor limit cycling at the end of the shuttle flight. For this reason, friction was not expected to be a driving factor of performance and control of the reused RS-25 engines aboard the SLS. However, after test data showed a large shift in frequency behavior and a highly damped step-response in the time series, there was further investigation into what could have caused this behavior. Heritage friction models used in previous gimbal and ball bearings were evaluated such as Coulomb, Dahl and LuGre, but the single degree of freedom friction models alone were not enough to explain the behavior and shifts seen in the test data. This paper presents the additional findings and modeling efforts regarding friction on the RS-25 engines. Using the Two Actuator Operational Simulation (TAOS), the difference from modeling separate friction degrees of freedom to coupled degrees of freedom was investigated to deduce the effects of one axis’s movement on the other. Next, due to the vibration environment, a modified LuGre model has been proposed that adds an additional term to decrease the friction coefficient at low engine velocity amplitudes. Lastly, the addition of the stiffness in each half of the gimbal bearing has increased modeling fidelity by also adding the effect on the gimbal bearing bending in compliance to both the friction torque on the surface of the gimbal bearing and the actuator force that is forcing the engine in a specified direction. Through these effects, the time and frequency domain behavior seen in test can be characterized accurately.

Friction↗
NASA NTRSDate not supplied

Core Stage TVC Systems Engineering Challenges in Reusing Heritage Hardware

The Space Launch System (SLS) Core Stage (CS) Thrust Vector Control (TVC) system is comprised of 8 mechanical feedback Shuttle heritage Type III TVC actuators and four RS-25 engines, each attached to a Shuttle heritage gimbal block/bearing. Two actuators are used to move each engine in two planes perpendicular to one another (i.e., pitch and yaw). The TVC system design leverages hardware from the Space Shuttle program as well as new hardware designed specifically for the Core Stage. The Space Shuttle heritage hardware directly reused on SLS includes the Orbiter TVC hydraulic servo-actuators (with two slight design modifications), the Orbiter hydraulic circulation pumps, the Orbiter gimbal block/bearing, and the Solid Rocket Booster hydraulic pumps. The Core Auxiliary Power Unit (CAPU) is derived from the Orbiter Auxiliary Power Unit (APU). The Orbiter and Solid Rocket Booster APU turbines are powered by hot gas produced by catalyzed hydrazine decomposition. On the SLS Core Stage, the CAPU turbine is spun using cold gas tapped-off from the RS-25 to CS liquid hydrogen autogenous pressurization line. While direct reuse or slight modification of existing hardware may seem to be a triple-win for a program in cost, schedule, and technical risk mitigation, those benefits can only be realized when its degree of application in a new system is carefully and thoughtfully managed. The heritage hardware reuse should be prescribed within the heritage design capability and reuse environments must lie within the envelope of heritage qualification testing. Despite the significant test and flight experience of the Shuttle heritage hardware components, successful integration with the newly designed CS TVC components and incorporation into the stage design proved to be a challenge which required re-qualification of the heritage hardware as well as thorough integrated testing to support flight certification. Examples of the challenges that were overcome include: re-qualifying heritage hardware to survive new shock and vibration environments, certifying performance of extensively modified heritage hardware, regenerating design insight due to lack of available heritage vendor data, showing compliance to modern structural design standards, translation of heritage requirements for analog avionics to modern digital avionics, and interfacing heritage mechanical hardware with newly designed avionics. This paper is the second installment in a seven-paper series surveying the design, engineering, test validation, and flight performance of the Core Stage Thrust Vector Control system. This paper will discuss several engineering challenges encountered during the development process for SLS CS TVC and how they were successfully overcome to reach flight readiness.

Thrust Vector Control↗
NASA NTRSDate not supplied

Space Launch System: Core Stage Thrust Vector Control Systems Engineering Challenges in Reusing Heritage Hardware

The Space Launch System (SLS) Core Stage (CS) Thrust Vector Control (TVC) system is comprised of 8 mechanical feedback Shuttle heritage Type III TVC actuators and four RS-25 engines, each attached to a Shuttle heritage gimbal block/bearing. Two actuators are used to move each engine in two planes perpendicular to one another (i.e., pitch and yaw). The TVC system design leverages hardware from the Space Shuttle program as well as new hardware designed specifically for the Core Stage. The Space Shuttle heritage hardware directly reused on SLS includes the Orbiter TVC hydraulic servo-actuators (with two slight design modifications), the Orbiter hydraulic circulation pumps, the Orbiter gimbal block/bearing, and the Solid Rocket Booster hydraulic pumps. The Core Auxiliary Power Unit (CAPU) is derived from the Orbiter Auxiliary Power Unit (APU). The Orbiter and Solid Rocket Booster APU turbines are powered by hot gas produced by catalyzed hydrazine decomposition. On the SLS Core Stage, the CAPU turbine is spun using cold gas tapped-off from the RS-25 to CS liquid hydrogen autogenous pressurization line. While direct reuse or slight modification of existing hardware may seem to be a triple-win for a program in cost, schedule, and technical risk mitigation, those benefits can only be realized when its degree of application in a new system is carefully and thoughtfully managed. The heritage hardware reuse should be prescribed within the heritage design capability and reuse environments must lie within the envelope of heritage qualification testing. Despite the significant test and flight experience of the Shuttle heritage hardware components, successful integration with the newly designed CS TVC components and incorporation into the stage design proved to be a challenge which required re-qualification of the heritage hardware as well as thorough integrated testing to support flight certification. Examples of the challenges that were overcome include: re-qualifying heritage hardware to survive new shock and vibration environments, certifying performance of extensively modified heritage hardware, regenerating design insight due to lack of available heritage vendor data, showing compliance to modern structural design standards, translation of heritage requirements for analog avionics to modern digital avionics, and interfacing heritage mechanical hardware with newly designed avionics. This paper is the second installment in a seven-paper series surveying the design, engineering, test validation, and flight performance of the Core Stage Thrust Vector Control system. This paper will discuss several engineering challenges encountered during the development process for SLS CS TVC and how they were successfully overcome to reach flight readiness.

Thrust Vector Control↗
NASA NTRSDate not supplied

Low-G Slosh Workshop Results From 2023: State of the Art, Gaps and Forward Work

The NASA Engineering and Safety Center (NESC) sponsored a workshop to dis-cuss low-g slosh. Over a dozen different NASA centers and industry partners participated in this workshop. The main topics were to identify the state of the art regarding test data, Computational Fluid Dynamics (CFD) analysis resources, and GN&C models that are available for this problem. The primary intent was to determine deficiencies in the collective knowledge base and to identify priorities that should be established for proactive work in the areas of model development, validation, and model integration. Recommendations from workshop participants include establishing an online slosh modeling resource, conducting ground/flight testing, developing surrogate models, and establishing co-simulation techniques. This paper summarizes the workshop findings and recommendations for the larger community.

Lattice-Boltzmann↗