Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “SERVICE MODULE”

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.

1,287 records · Page 72

NDT System for Metal Components in Concrete Structures (Final Report)

Steel reinforcements embedded within concrete can corrode and crack, leading to weakening of the structures, and existing NDT (non-destructive testing) techniques do not provide the full picture. Condition assessment is critical in evaluating these structures in order to ensure safe, long-term operation of the nuclear power plants. Improved NDT techniques are needed as the nation’s generating stations age and require action based on increasingly critical inspection data. The power industry uses eddy current test (ECT) during in-service inspections to detect and monitor defects such as cracks and corrosion in metals, particularly metal pipes. However, the detection of defects in the reinforcing steel embedded in concrete is far more challenging for numerous reasons. Primary among them is the concrete layer’s thickness, which prevents the ability to have a close proximity between sensor and metallic sample. One solution to this problem is to create a higher sensitivity technique which can inspect at depth, with good spatial resolution and excellent directional sensitivity, to isolate the metal buried deep in the concrete and characterize defects in the metal. The goal of the phase II research program was to study and develop a new reinforced concrete NDT technology based on anisotropic magnetoresistive (AMR) sensors designed specifically for ECT of steel reinforcements in concrete. The first technical objective was to demonstrate the capability of inspecting steel reinforcement structures, including metal rebar and tensioning cable at or below 6” of depth embedded in concrete. Another objective was to be able to confidently identify multiple layers of reinforcements at varying depths. In addition, the technique needed to be able to provide condition assessment of the metal, providing data on the structure and positioning of the steel members, material loss, and detection of the presence of breaks. An important part of the research and development was aimed at achieving superior performance compared to existing technology. The ability to detect corrosion breaks in unbonded multi-wire and multi-strand tendons was another important objective. The final objective that led to a successful program was to build a complete prototype portable scanning system capable of demonstrating the probe performance in the field. All of these objectives were met, which provided data for the system development work going forward. RMD worked with the engineering firm Simpson Gumpertz & Heger to develop a detailed problem definition for concrete structures and the necessary sensor specifications. In addition, we developed finite element simulation models for the eddy current based NDT system through the analysis of the electromagnetic (EM) properties of sample materials and the orientation of the transmitter, sensor array (receivers), metal, and intervening materials like concrete and air. Based on the modeling and specifications, we designed and fabricated prototype sensor modules. We then acquired and fabricated test samples to characterize and optimize the sensors. Finally, we built a complete prototype for testing on actual concrete structures. This new NDT technology has high promise for greatly improving capabilities in the inspection of steel reinforcements within concrete structures, such as rebar, liners, anchors, and prestressing cables. This method could be valuable in the maintenance of nuclear power plants, and many other structures critical to our nation’s infrastructure.

42 ENGINEERING↗

The Evolution of Lidar Networks: A US Perspective

Atmospheric aerosols and clouds play an important role in climate by directly scattering and absorbing sunlight. Aerosol-cloud interactions modify the particle properties causing indirect effects, alter aerosol deposition and rainfall, and contribute substantially to the uncertainties in predicting climate effects. Aerosols also affect air quality and both constituents modulate boundary layer dynamics to a certain extent, in turn impacting aerosol transport and aerosol-cloud interactions. The spatiotemporal distribution of aerosol and cloud layers is thus important, and lidar remains the primary instrument for determining the vertical distribution of aerosols and thin clouds. Lidar still provides important information for opaque cloud layers by determining base heights. Combined lidar and radar data provide a comprehensive coverage of aerosol and cloud vertical distributions, and thus locations where and when they interact. Lidar data provide a means of constraining column aerosol loading observations (e.g. AOD) to vertical extents. In addition, lidar has proven effective at determining a proxy for boundary layer height by examining aerosol gradients and/or cloud base heights in lidar profiles. Polarized lidars provide additional information on particle shape, allowing estimates of cloud phase and separation of dust or smoke from sulfate and sea salt aerosols. Given the importance of lidar observations and a critical maturation in technology and retrieval techniques, several organizations began to build operational lidar networks around 2000. The European Aerosol Research Lidar Network (EARLINET) was started as a research focused network of advanced lidars across Europe. The Asian Dust Lidar Network (ADNET) was also developed as a regional network providing lidar profiles of dust and pollution across Eastern Asia. In the US, the NASA Micro Pulse Lidar Network (MPLNET) was created to provide global lidar profiling at key sites in the NASA Aerosol Robotic Network (AERONET). The Network for the Detection of Atmospheric Composition Change (NDACC) pre-dates these networks and many sites have lidar, but it is not strictly a lidar network and at the time focused less on the lower troposphere. Finally, there were already existing ceilometer networks operated by various meteorological agencies, but in particular here in the US the profile data has not been available. The ceilometer networks were used to provide only clouds base heights and estimates of PBL height. Thus, the distinguishing feature between lidar and ceilometer networks was historically the ability to actually provide profile information (in addition to differences in wavelength, and advanced retrievals such as the raman technique). As time progressed, each lidar network matured and developed more operational capabilities and data sets, coupled with viable data centers providing DAAC services and access to near-real-time (NRT) data. In 2008 under WMO guidance, the Global Atmospheric Watch (GAW) Aerosol Lidar Observation Network (GALION) was formed as a global network made up of the existing lidar networks. The goal was to share information, best practices, and develop frameworks and techniques for quality data. GALION grew to include several other regional lidar networks and this has led to a vast increase in quality lidar sites worldwide.

Welton, Ellsworth J.↗

Streamlining Stakeholder Data Accessibility Utilizing Web-Based GIS Capabilities - 18672

Environmental data is often complex, and it can be difficult to provide proper context to fully understand and comprehensively analyze the data. One tool identified to better present complicated data is the use of web-based Geographic Information Systems (GIS). Web-based GIS provides much-needed visual context to the complex data collected at Los Alamos National Laboratory (LANL). By overlaying environmental data atop relevant geographical features, such as topography, surface or subsurface geology, hydrogeological features, buildings, roads, and technical areas, LANL's diverse group of stakeholders are better able to understand environmental data collected at the LANL site within the framework of the surrounding geography. Since 2012, Los Alamos has utilized a web-based GIS module in the Intellus New Mexico data-sharing web site. This web site provides unfettered public access to LANL and New Mexico Environment Department (NMED) - Department of Energy (DOE) Oversight Bureau environmental data. Through the past five years of real world experience, LANL identified areas where questions and confusion arose, particularly for those not directly associated with the site's environmental cleanup mission. In order to query the millions of records in Intellus in a meaningful way, users had to have substantial knowledge of the data organization and nomenclature ahead of time. While this was not a challenge for LANL and NMED environmental scientists, it proved to be a substantial barrier for members of the general public to utilize Intellus. In 2017, LANL initiated an Intellus redesign with the goal of deconstructing the type of questions people asked and identifying the types of user personas accessing the site to engineer a simpler path to desired data sets. Greatly simplified click paths ('Quick Paths') were created that walk the user through the basics with a minimum of jargon and a strong reliance on mapping results for easy visualization. The improved mapping was enabled by an upgraded online GIS functionality that allowed LANL to easily integrate their own base-maps to provide users the most up to date views of their data. The integrated Intellus GIS was enhanced to assimilate with LANL's dynamic base maps and site information in relation to data collection activities, to avoid outdated presentations. A simplified user interface (UI) was added and easier data querying was designed. A more robust visual presentation was created that allowed better viewing of spatial data. All data queries in the new simplified 'Quick Path' give the users the option to map the results and save their results to their optional accounts. This brings the power of GIS visualization to all users without the need for GIS knowledge or extensive training. By integrating with Esri{sup R} technologies, base-map layers in ArcGIS Online{sup R} can be updated by LANL or other data providers at any time and reflected immediately in the Intellus mapping application called GIS+ 1. Users can even load additional map layers to GIS+ that contain their own spatial data or information shared from over a million users on ArcGIS Online{sup R}, such as ecological information from the Fish and Wildlife Service, or geology layers from the USGS. The results from the improved quick path search in Intellus can be viewed in GIS+ and analyzed using Esri's{sup R} Smart Mapping technology, which makes it easy to classify results with its visual representation of the results in an interactive histogram, where sliders can be dragged to look at various intervals for each color range for that query. With enhanced GIS+, Los Alamos National Laboratory is able to observe improve Stakeholder engagement and positive Stakeholder interactions within its public environmental database, Intellus New Mexico. (authors)

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

Launch Pad in a Box

NASA Kennedy Space Center (KSC) is developing a new deployable launch system capability to support a small class of launch vehicles for NASA and commercial space companies to test and launch their vehicles. The deployable launch pad concept was first demonstrated on a smaller scale at KSC in 2012 in support of NASA Johnson Space Center's Morpheus Lander Project. The main objective of the Morpheus Project was to test a prototype planetary lander as a vertical takeoff and landing test-bed for advanced spacecraft technologies using a hazard field that KSC had constructed at the Shuttle Landing Facility (SLF). A steel pad for launch or landing was constructed using a modular design that allowed it to be reconfigurable and expandable. A steel flame trench was designed as an optional module that could be easily inserted in place of any modular steel plate component. The concept of a transportable modular launch and landing pad may also be applicable to planetary surfaces where the effects of rocket exhaust plume on surface regolith is problematic for hardware on the surface that may either be damaged by direct impact of high speed dust particles, or impaired by the accumulation of dust (e.g., solar array panels and thermal radiators). During the Morpheus free flight campaign in 2013-14, KSC performed two studies related to rocket plume effects. One study compared four different thermal ablatives that were applied to the interior of a steel flame trench that KSC had designed and built. The second study monitored the erosion of a concrete landing pad following each landing of the Morpheus vehicle on the same pad located in the hazard field. All surfaces of a portable flame trench that could be directly exposed to hot gas during launch of the Morpheus vehicle were coated with four types of ablatives. All ablative products had been tested by NASA KSC and/or the manufacturer. The ablative thicknesses were measured periodically following the twelve Morpheus free flight tests. The thermal energy from the Morpheus rocket exhaust plume was only found to be sufficient to cause appreciable ablation of one of the four ablatives that were tested. The rocket exhaust plume did cause spalling of concrete during each descent and landing on a landing pad in the hazard field. The Extended Abstract ASE Earth and Space Conference April, 2016 - Orlando, FL concrete surface was laser scanned following each Morpheus landing, and the total volume of spalled concrete that eroded between the first and final landings of the Morpheus Project's test campaign was estimated. This paper will also describe a new deployable launch system (DLS) capability that is being developed at KSC and was publicly announced in May 2015 (KSC Partnerships, 2015). The DLS is a set of multi-user Ground Support Equipment that will be used to test and launch small class launch vehicles. The system is comprised of four main elements: the Launch Stand, the Flame Deflector, the Pad Apron and the KAMAG transporter. The system elements are designed to be deployed at launch or test sites within the KSC/CCAFS boundaries. The DLS is intended to be used together with the Fluid and Electrical System of the Universal Propellant Servicing Systems and Mobile Power Data and Communications Unit.

Ablatives Testing↗

Launch Pad in a Box

NASA Kennedy Space Center (KSC) is developing a new deployable launch system capability to support a small class of launch vehicles for NASA and commercial space companies to test and launch their vehicles. The deployable launch pad concept was first demonstrated on a smaller scale at KSC in 2012 in support of NASA Johnson Space Center's Morpheus Lander Project. The main objective of the Morpheus Project was to test a prototype planetary lander as a vertical takeoff and landing test-bed for advanced spacecraft technologies using a hazard field that KSC had constructed at the Shuttle Landing Facility (SLF). A steel pad for launch or landing was constructed using a modular design that allowed it to be reconfigurable and expandable. A steel flame trench was designed as an optional module that could be easily inserted in place of any modular steel plate component. The concept of a transportable modular launch and landing pad may also be applicable to planetary surfaces where the effects of rocket exhaust plume on surface regolith is problematic for hardware on the surface that may either be damaged by direct impact of high speed dust particles, or impaired by the accumulation of dust (e.g., solar array panels and thermal radiators). During the Morpheus free flight campaign in 2013-14, KSC performed two studies related to rocket plume effects. One study compared four different thermal ablatives that were applied to the interior of a steel flame trench that KSC had designed and built. The second study monitored the erosion of a concrete landing pad following each landing of the Morpheus vehicle on the same pad located in the hazard field. All surfaces of a portable flame trench that could be directly exposed to hot gas during launch of the Morpheus vehicle were coated with four types of ablatives. All ablative products had been tested by NASA KSC and/or the manufacturer. The ablative thicknesses were measured periodically following the twelve Morpheus free flight tests. The thermal energy from the Morpheus rocket exhaust plume was only found to be sufficient to cause appreciable ablation of one of the four ablatives that were tested. The rocket exhaust plume did cause spalling of concrete during each descent and landing on a landing pad in the hazard field. The Extended Abstract ASE Earth and Space Conference April, 2016 - Orlando, FL concrete surface was laser scanned following each Morpheus landing, and the total volume of spalled concrete that eroded between the first and final landings of the Morpheus Project's test campaign was estimated. This paper will also describe a new deployable launch system (DLS) capability that is being developed at KSC and was publicly announced in May 2015 (KSC Partnerships, 2015). The DLS is a set of multi-user Ground Support Equipment that will be used to test and launch small class launch vehicles. The system is comprised of four main elements: the Launch Stand, the Flame Deflector, the Pad Apron and the KAMAG transporter. The system elements are designed to be deployed at launch or test sites within the KSC/CCAFS boundaries. The DLS is intended to be used together with the Fluid and Electrical System of the Universal Propellant Servicing Systems and Mobile Power Data and Communications Unit

Mobile Launch Pad Development↗

NASA Software Engineering Benchmarking Study

To identify best practices for the improvement of software engineering on projects, NASA's Offices of Chief Engineer (OCE) and Safety and Mission Assurance (OSMA) formed a team led by Heather Rarick and Sally Godfrey to conduct this benchmarking study. The primary goals of the study are to identify best practices that: Improve the management and technical development of software intensive systems; Have a track record of successful deployment by aerospace industries, universities [including research and development (R&D) laboratories], and defense services, as well as NASA's own component Centers; and Identify candidate solutions for NASA's software issues. Beginning in the late fall of 2010, focus topics were chosen and interview questions were developed, based on the NASA top software challenges. Between February 2011 and November 2011, the Benchmark Team interviewed a total of 18 organizations, consisting of five NASA Centers, five industry organizations, four defense services organizations, and four university or university R and D laboratory organizations. A software assurance representative also participated in each of the interviews to focus on assurance and software safety best practices. Interviewees provided a wealth of information on each topic area that included: software policy, software acquisition, software assurance, testing, training, maintaining rigor in small projects, metrics, and use of the Capability Maturity Model Integration (CMMI) framework, as well as a number of special topics that came up in the discussions. NASA's software engineering practices compared favorably with the external organizations in most benchmark areas, but in every topic, there were ways in which NASA could improve its practices. Compared to defense services organizations and some of the industry organizations, one of NASA's notable weaknesses involved communication with contractors regarding its policies and requirements for acquired software. One of NASA's strengths was its software assurance practices, which seemed to rate well in comparison to the other organizational groups and also seemed to include a larger scope of activities. An unexpected benefit of the software benchmarking study was the identification of many opportunities for collaboration in areas including metrics, training, sharing of CMMI experiences and resources such as instructors and CMMI Lead Appraisers, and even sharing of assets such as documented processes. A further unexpected benefit of the study was the feedback on NASA practices that was received from some of the organizations interviewed. From that feedback, other potential areas where NASA could improve were highlighted, such as accuracy of software cost estimation and budgetary practices. The detailed report contains discussion of the practices noted in each of the topic areas, as well as a summary of observations and recommendations from each of the topic areas. The resulting 24 recommendations from the topic areas were then consolidated to eliminate duplication and culled into a set of 14 suggested actionable recommendations. This final set of actionable recommendations, listed below, are items that can be implemented to improve NASA's software engineering practices and to help address many of the items that were listed in the NASA top software engineering issues. 1. Develop and implement standard contract language for software procurements. 2. Advance accurate and trusted software cost estimates for both procured and in-house software and improve the capture of actual cost data to facilitate further improvements. 3. Establish a consistent set of objectives and expectations, specifically types of metrics at the Agency level, so key trends and models can be identified and used to continuously improve software processes and each software development effort. 4. Maintain the CMMI Maturity Level requirement for critical NASA projects and use CMMI to measure organizations developing software for NASA. 5.onsolidate, collect and, if needed, develop common processes principles and other assets across the Agency in order to provide more consistency in software development and acquisition practices and to reduce the overall cost of maintaining or increasing current NASA CMMI maturity levels. 6. Provide additional support for small projects that includes: (a) guidance for appropriate tailoring of requirements for small projects, (b) availability of suitable tools, including support tool set-up and training, and (c) training for small project personnel, assurance personnel and technical authorities on the acceptable options for tailoring requirements and performing assurance on small projects. 7. Develop software training classes for the more experienced software engineers using on-line training, videos, or small separate modules of training that can be accommodated as needed throughout a project. 8. Create guidelines to structure non-classroom training opportunities such as mentoring, peer reviews, lessons learned sessions, and on-the-job training. 9. Develop a set of predictive software defect data and a process for assessing software testing metric data against it. 10. Assess Agency-wide licenses for commonly used software tools. 11. Fill the knowledge gap in common software engineering practices for new hires and co-ops.12. Work through the Science, Technology, Engineering and Mathematics (STEM) program with universities in strengthening education in the use of common software engineering practices and standards. 13. Follow up this benchmark study with a deeper look into what both internal and external organizations perceive as the scope of software assurance, the value they expect to obtain from it, and the shortcomings they experience in the current practice. 14. Continue interactions with external software engineering environment through collaborations, knowledge sharing, and benchmarking.

Rarick, Heather L.↗

Trajectory Engineering with Modular Patched Conics for Entry Systems and TPS (TEMPEST)

Brief Presenter Biography (35 word limit): Bohdan Wesely is an Aerospace Engineer in the Entry Systems and Technology Division at Ames. He has worked on a variety of projects for NASA including integrated TPS (thermal protection system) flight hardware deliveries and testing services for commercial partners. Introduction: TEMPEST is a new trajectory analysis framework that is designed to fill the gap between dedicated flight mechanics tools and aerothermal and TPS sizing tools. The project started as an SJSU master’s thesis and has since evolved into a general conceptual design tool capable of studying a wide variety of entry problems. Development is ongoing in the Entry Systems and Technology Division at NASA ARC. Why TEMPEST: Space missions involving entry into a planetary atmosphere involve a series of unique requirements across multiple disciplines. Whether it is traditional entry descent and landing (EDL), or aerocapture, the vehicle must navigate to its target landing location or orbit state, and the TPS must protect the payload during entry. The design process typically involves iterative handoffs between various flight mechanics, flow solver, and material response level tools. During the early conceptual phase, a wide variety of feasible trajectories are simulated in a Monte Carlo scenario which broadly satisfy the mission or landing requirements. Next, computational fluid dynamics (CFD), direct simulation Monte Carlo (DSMC), and other flow solver analyses are performed at various key trajectory points to generate an aero-database, heating and TPS design requirements also emerge at this stage. At this point, with updated aerodynamics from the various flow solvers, trajectories can be re-run, this in turn can change the required freestream conditions for the CFD tools, and as a project progresses, these analyses converge, and uncertainty is reduced. However, there is always a “hand-off” occurring between two inherently coupled phenomena. Analysis Description: One of the goals with TEMPEST is to use a variety of first principles estimation methods coupled with an atmosphere model to predict vehicle aerothermodynamics across the entire flight regime while propagating a 3 or 6 degree of freedom (DoF) trajectory. Aerodynamics methods include modified Newtonian, Maxwell and Cercignani- Lampis-Lord (CLL) for continuum, transitional, and free molecular flow regimes. Aerothermodynamics include boundary layer and reference enthalpy methods, and Mutation++ for non-equilibrium chemistry modeling. TEMPEST is also capable of stitching multiple trajectory segments together to study mission scenarios like multi-pass aerocapture and aero-gravity assists. Most of the program is implemented in MATLAB using modern system objects, it relies on several C++ shared libraries for supporting tools like Gmsh, the Global Reference Atmospheric Model (GRAM), and Mutation++. The various first principles aerothermal estimation methods are discretized across either a structured axisymmetric panel mesh or an unstructured tri-mesh generated from an open-source tool such as Gmsh, this allows solutions on the same mesh to be compared across tools such as CB-Aero. CFD Coupling. A physics-aware, gaussian process CFD anchoring scheme is proposed to adjust the various first principles methods as a CFD database is populated. One goal for this anchoring module is to inform the project where CFD should be run. Full knowledge of the entire trajectory, atmosphere, and aerothermodynamics allows for easier identification of high sensitivity areas and uncertainty quantification. While the first principles effects are well known and proven accurate in existing tools such as CB- Aero and Cart3D, a physics aware CFD anchoring scheme increases tool credibility across a project lifecycle. Material Response Modeling. Correct TPS sizing is critical for optimizing mass for science payloads and ensuring mission success. The process typically involves a thermal analysis along the trajectory with surface heating environments as a boundary condition. Several design constraints are maximum bondline temperature and maximum recession with various margining techniques. The material response tool FIAT, developed out of NASA Ames, is currently being integrated into the TEMPEST environment. TPS recession, shape change, mass loss, and mass property alteration are all factors that can perturb an entry trajectory. For missions like Mars 2020, recession was minimal and was safely handled separately as a post process. For missions such as Jupiter Galileo with a high TPS mass fraction or asteroid entries, recession plays a major role. The proposed fully coupled scheme is to use an epoch-based approach where the trajectory integration is halted after a recession threshold, the energy balance and FIAT are solved at each panel, the mesh, aerodynamics, and mass properties are updated, and the trajectory continues. Several computational tradeoffs have been made during the development of TEMPEST to limit the cost of a single trajectory and preserve its utility as a conceptual, rapid iteration tool. Conclusion: Development of TEMPEST is ongoing and the project is still in its infancy. This talk aims to showcase its unique capabilities to support future NASA entry systems missions.

Bohdan O Wesely↗

Seeing the forest for all the trees: Mycorrhizal‐associated nutrient economies are modulated by stem density and the synchrony between overstorey and understorey communities

1. Identifying relationships between plant communities and soil characteristics is a critical step in understanding the consequences of species gains and losses in ecosystems. The mycorrhizal associated nutrient economy (MANE) hypothesis predicts that the degree to which tree species and their mycorrhizal associates affect soil properties is driven by the relative dominance of different mycorrhizal types (often measured by relative basal area). While this approach emphasizes the importance of canopy trees, it does not account for how other factors (e.g. the density and composition of understorey trees) may alter tree–soil relationships. 2. We analysed tree–soil data from an eastern deciduous forest in southern Indiana, USA that contains >29,000 georeferenced stems, including 21 species that associate with arbuscular mycorrhizal (AM) fungi and 14 that associate with ectomycorrhizal (ECM) fungi. We sampled soils (upper 5 cm) from across the plot and modelled soil characteristics to tree communities. Given differences in soil characteristics among AM-dominated and ECM-dominated neighbourhoods, we hypothesized that relationships between tree-mycorrhizal dominance and soils would be affected by both the density of stems in the plot (owing to ‘Zinke’ individual plant effects) and composition of the understorey trees (owing to ‘trait divergence effects’) 3. In support of our Zinke hypothesis, we found that the relationships between tree-mycorrhizal dominance and soil variables (soil pH, nitrification rates and carbon to nitrogen ratio) were strengthened as stand density increased. In support of the trait divergence hypothesis, we found that as the mismatch between overstorey and understorey composition increased (e.g. AM-dominated understories beneath ECM-dominated overstories and vice versa), the relationship between tree dominance and soil variables weakened. We were able to use these insights to create mycorrhizal metrics to predict soil variables that were sensitive to the structural composition of neighbourhoods. 4. Synthesis. Our results indicate that relationships between plants and soils in forests are not only shaped by dominant overstorey trees but also the density and composition of understorey trees. Thus, efforts to predict the ecosystem consequences of species gains and losses may benefit from considering these elements of forest structure and not only the basal area of the dominant trees.

MANE framework↗

Solar Dynamics Observatory Guidance, Navigation, and Control System Overview

The Solar Dynamics Observatory (SDO) was designed and built at the Goddard Space Flight Center, launched from Cape Canaveral on February 11, 2010, and reached its final geosynchronous science orbit on March 16, 2010. The purpose of SDO is to observe the Sun and continuously relay data to a dedicated ground station. SDO remains Sun-pointing throughout most of its mission for the instruments to take measurements of the Sun. The SDO attitude control system (ACS) is a single-fault tolerant design. Its fully redundant attitude sensor complement includes sixteen coarse Sun sensors (CSSs), a digital Sun sensor (DSS), three two-axis inertial reference units (IRUs), and two star trackers (STs). The ACS also makes use of the four guide telescopes included as a part of one of the science instruments. Attitude actuation is performed using four reaction wheels assemblies (RWAs) and eight thrusters, with a single main engine used to provide velocity-change thrust for orbit raising. The attitude control software has five nominal control modes, three wheel-based modes and two thruster-based modes. A wheel-based Safehold running in the attitude control electronics box improves the robustness of the system as a whole. All six modes are designed on the same basic proportional-integral-derivative attitude error structure, with more robust modes setting their integral gains to zero. This paper details the final overall design of the SDO guidance, navigation, and control (GN&C) system and how it was used in practice during SDO launch, commissioning, and nominal operations. This overview will include the ACS control modes, attitude determination and sensor calibration, the high gain antenna (HGA) calibration, and jitter mitigation operation. The Solar Dynamics Observatory mission is part of the NASA Living With a Star program, which seeks to understand the changing Sun and its effects on the Solar System, life, and society. To this end, the SDO spacecraft carries three Sun-observing instruments: Helioseismic and Magnetic Imager (HMI), led by Stanford University; Atmospheric Imaging Assembly (AIA), led by Lockheed Martin Space and Astrophysics Laboratory; and Extreme Ultraviolet Variability Experiment (EVE), led by the University of Colorado. The basic mission is to observe the Sun for a very high percentage of the 5-year mission (10-year goal) with long stretches of uninterrupted observations and with constant, high-data-rate transmission to a dedicated ground station to be located in White Sands, New Mexico. These goals guided the design of the spacecraft bus that will carry and service the three-instrument payload. Overarching design goals for the bus are geosynchronous orbit, near-constant Sun observations with the ability to fly through eclipses, and constant HGA contact with the dedicated ground station. A three-axis stabilized ACS is needed both to point at the Sun accurately and to keep the roll about the Sun vector correctly positioned with respect to the solar north pole. This roll control is especially important for the magnetic field imaging of HM I. The mission requirements have several general impacts on the ACS design. Both the AIA and HMI instruments are very sensitive to the blurring caused by jitter. Each has an image stabilization system (ISS) with some ability to filter out high frequency motion, but below the bandwidth of the ISS the control system must compensate for disturbances within the ACS bandwidth or avoid exciting jitter at higher frequencies. Within the ACS bandwidth, the control requirement imposed by AIA is to place the center of the solar disk no more than 2 arc sec, 3 , from a body-defined target based on one of the GTs that accompany the instrument. This body-defined target, called the science reference boresight (SRB), was determined from the postlaunch orientation of the GTs by averaging the bounding telescope boresights for pitch to get a pitch SRB coordinate, and by averaging the bounding boresights for yaw toet the yaw SRB coordinate. The location of this SRB in the 0.5-deg field-of-view for each GT then becomes the central target for each telescope; one GT is selected for use as the ACS controlling guide telescope (CGT) at any given time. Fine Sun-pointing is effected based on this SRB for all three instruments when the Sun is within the linear range of the CGT. In addition to limiting jitter, HMI science requires averaging several observations, making the instrument sensitive to low frequency motion that induces differential motion between each observation. This requires the spacecraft attitude to be stable about the roll axis to approximately 10 arcsec over a ten-minute period. Instrument calibrations require that the spacecraft point the SRB up to 2.5 degrees in pitch and yaw away from the center of the Sun, placing the Sun outside the field-of-view of the guide telescopes. In such instances, when the GTs cannot provide the definitive target for the ACS, on-board attitude determination combined with ephemeris prediction of the Sun direction must provide the definitive target. EVE is capable of observing the Sun with less dependence on attitude control. However, the ground data processing needs for calibrations result in the most strict attitude knowledge requirements for the mission: [35,70,70] arcsec, 3 , of knowledge with respect to the center of the solar disk. In addition to driving the ACS sensor selection, the knowledge requirements, which have their effect primarily during Inertial mode calibrations, drive the accuracy requirements for the solar ephemeris. The need to achieve and maintain geosynchronous orbit (GEO) drove the need for high-efficiency propulsive systems and appropriate attitude control. The main engine provided high specific impulse for the maneuvers to attain GEO, while the smaller ACS thrusters managed the disturbance torques of the larger engine and provided the capability for much smaller adjustment burns on orbit. SDO s large solar profile means that solar radiation pressure is a large torque disturbance, and the momentum buildup from this disturbance and the GEO altitude drives the ACS to use thrusters to manage vehicle momentum. The demanding data capture budget for the mission, however, requires SDO to avoid frequent thruster maneuvers, while concerns about on-orbit jitter restrict the maximum desired wheel speeds desired from the RWAs. The plan for on-orbit wheel speed and momentum management will be discussed as well as what is now being done in operation after the jitter environment was characterized. The SDO ACS hardware complement is single-fault tolerant. Two main processors carry virtually identical copies of the command and data handling and ACS software, and two identical attitude control electronics (ACE) boxes carry Coldfire processors with contingency ACS software and other hardware interface cards; the ACE structure allows reaction wheels to be commanded by the Sun-pointing Safehold independent of the Mil Std 1553 data bus. The sixteen Adcole CSSs are grouped into primary and backup sets of eight sensors, each set providing the ability to calculate a sun vector. Each set of eight eyes provides full 4 -steradian coverage. The Adcole DSS comprises an optics head and a separate electronics box providing a 1553 data interface. The electronics box is mounted inside the Faraday cage created by the spacecraft bus module. The DSS head with its 32- deg square FOV is mounted on the instrument module with its boresight along the spacecraft X axis, nearly aligned with the Sun during observations. Adcole has designed the DSS calibration parameters so that the accuracy is 0.24 arcminutes within 10 deg of the boresight, and diminishes to 3 arcminutes as the Sun moves towards the edges of its FOV . This DSS calibration scheme provides higher accuracy attitude determination over the range of the instrument calibration maneuvers.

Morgenstern, Wendy M.↗