Results for “automated orbital rendezvous” — Page 3

NASA NTRS2008

Automated and Adaptive Mission Planning for Orbital Express

The Orbital Express space mission was a Defense Advanced Research Projects Agency (DARPA) lead demonstration of on-orbit satellite servicing scenarios, autonomous rendezvous, fluid transfers of hydrazine propellant, and robotic arm transfers of Orbital Replacement Unit (ORU) components. Boeing's Autonomous Space Transport Robotic Operations (ASTRO) vehicle provided the servicing to the Ball Aerospace's Next Generation Serviceable Satellite (NextSat) client. For communication opportunities, operations used the high-bandwidth ground-based Air Force Satellite Control Network (AFSCN) along with the relatively low-bandwidth GEO-Synchronous space-borne Tracking and Data Relay Satellite System (TDRSS) network. Mission operations were conducted out of the RDT&E Support Complex (RSC) at the Kirtland Air Force Base in New Mexico. All mission objectives were met successfully: The first of several autonomous rendezvous was demonstrated on May 5, 2007; autonomous free-flyer capture was demonstrated on June 22, 2007; the fluid and ORU transfers throughout the mission were successful. Planning operations for the mission were conducted by a team of personnel including Flight Directors, who were responsible for verifying the steps and contacts within the procedures, the Rendezvous Planners who would compute the locations and visibilities of the spacecraft, the Scenario Resource Planners (SRPs), who were concerned with assignment of communications windows, monitoring of resources, and sending commands to the ASTRO spacecraft, and the Mission planners who would interface with the real-time operations environment, process planning products and coordinate activities with the SRP. The SRP position was staffed by JPL personnel who used the Automated Scheduling and Planning ENvironment (ASPEN) to model and enforce mission and satellite constraints. The lifecycle of a plan began three weeks outside its execution on-board. During the planning timeframe, many aspects could change the plan, causing the need for re-planning. These variable factors, ranging from shifting contact times to ground-station closures and required maintenance times, are discussed along with the flexibility of the ASPEN tool to accommodate changes to procedures and the daily or long-range plan, which contributed to the success of the mission. This paper will present an introduction to ASPEN, a more in-depth discussion on its use on the Orbital Express mission, and other relative work. A description of ground operations after the SRP deliveries were made is included, and we briefly discuss lessons learned from the planning perspective and future work.

scheduling↗

NASA NTRS1991

Approach range and velocity determination using laser sensors and retroreflector targets

Rockwell International is conducting an ongoing program to develop Laser Docking Sensors (LDS) that provide high performance and high intrinsic value while meeting all mission objectives. These LDS systems are now being required to aid future spacecraft docking, station keeping, and berthing/capture systems. Improved automated tracking, rendezvous, soft docking, and capture will be required in the construction and support of SSF and future orbiting platforms. The development of a practical LDS requires an easy-to-operate, low-cost, compact system. A wide range of options for laser range detection equipment, ranging from commercial technology to specialized military systems, was evaluated. This evaluation focused on both direct applicability of existing systems and usability of specific technologies contained in these systems. From these efforts it was determined that a new approach provided the greatest promise of fulfilling all mission requirements at the lowest life-cycle cost.

Race, L.↗

NASA NTRS2007

Analysis of Thermal Control Coatings on MISSE for Aerospace Applications

Many different passive thermal control materials were flown as part of the Materials on International Space Station Experiment. Engineers and scientists at the Marshall Space Flight Center have analyzed a number of these materials, including: Zinc oxide/potassium silicate coating, Zinc oxide/potassium silicate/silicone coating, Zinc orthotitanate/potassium silicate coating, Electrically conductive thermal control coatings and Various coatings for part marking, automated rendezvous and capture, and astronaut visual aids These and other material samples were exposed to the low Earth orbital environment of atormc oxygen, ultraviolet radiation, thermal cycling, and hard vacuum, though atomic oxygen exposure was very limited for some samples. Solar absorptance, infrared emittance, and mass measurements indicate the durability of these materials to withstand the space environment. The effect of contamination from an active space station on the performance of white thermal control coatings is discussed.

Finckenor, Miria↗

NASA NTRS1996

Flight Test Results from Real-Time Relative Global Positioning System Flight Experiment on STS-69

A real-time global positioning system (GPS) Kalman filter has been developed to support automated rendezvous with the International Space Station (ISS). The filter is integrated with existing Shuttle rendezvous software running on a 486 laptop computer under Windows. In this work, we present real-time and postflight results achieved with the filter on STS-69. The experiment used GPS data from an Osborne/Jet propulsion Laboratory TurboRouge receiver carried on the Wake Shield Facility (WSF) free flyer and a Rockwell Collins 3M receiver carried on the Orbiter. Real time filter results, processed onboard the Shuttle and replayed in near-time on the ground, are based on single vehicle mode operation and on 5 to 20 minute snapshots of telemetry provided by WSF for dual-vehicle mode operation. The Orbiter and WSF state vectors calculated using our filter compare favorably with precise reference orbits determined by the University of Texas Center for Space Research. The lessons learned from this experiment will be used in conjunction with future experiments to mitigate the technology risk posed by automated rendezvous and docking to the ISS.

Park, Young W.↗

NASA NTRS2011

Guidance, Navigation, and Control Program

The Rendezvous and Proximity Operations Program (RPOP) is real-time guidance, navigation, and control (GN&C) domain piloting-aid software that provides 3D Orbiter graphics and runs on the Space Shuttle's Criticality-3 Payload and General Support Computer (PGSC) in the crew cockpit. This software provides the crew with Situational Awareness during the rendezvous and proximity operations phases of flight. RPOP can be configured from flight to flight, accounting for mission-specific flight scenarios and target vehicles, via initialization load (I-load) data files. The software provides real-time, automated, closed-loop guidance recommendations and the capability to integrate the crew s manual backup techniques. The software can bring all relative navigation sensor data, including the Orbiter's GPC (general purpose computer) data, into one central application to provide comprehensive situational awareness of the rendezvous and proximity operations trajectory. RPOP also can separately maintain trajectory estimates (past, current, and predicted) based on certain data types and co-plot them, in order to show how the various navigation solutions compare. RPOP s best estimate of the relative trajectory is determined by a relative Kalman filter processing data provided by the sensor suite s most accurate sensor, the trajectory control sensor (TCS). Integrated with the Kalman filter is an algorithm that identifies the reflector that the TCS is tracking. Because RPOP runs on PC laptop computers, the development and certification lifecycles are more agile, flexible, and cheaper than those that govern the Orbiter FSW (flight software) that runs in the GPC. New releases of RPOP can be turned around on a 3- to 6-month template, from new Change Request (CR) to certification, depending on the complexity of the changes.

Hinkel, Heather↗

NASA NTRS1991

On-orbit demonstration of automated closure and capture using ESA-developed proximity operations technologies and an existing, serviceable NASA Explorer Platform spacecraft

The European Space Agency (ESA) has been working to develop an autonomous rendezvous and docking capability since 1984 to enable Hermes to automatically dock with Columbus. As a result, ESA with Matra, MBB, and other space companies have developed technologies that are also directly supportive of the current NASA initiative for Automated Rendezvous and Capture. Fairchild and Matra would like to discuss the results of the applicable ESA/Matra rendezvous and capture developments, and suggest how these capabilities could be used, together with an existing NASA Explorer Platform satellite, to minimize new development and accomplish a cost effective automatic closure and capture demonstration program. Several RV sensors have been developed at breadboard level for the Hermes/Columbus program by Matra, MBB, and SAAB. Detailed algorithms for automatic rendezvous, closure, and capture have been developed by ESA and CNES for application with Hermes to Columbus rendezvous and docking, and they currently are being verified with closed-loop software simulation. The algorithms have multiple closed-loop control modes and phases starting at long range using GPS navigation. Differential navigation is used for coast/continuous thrust homing, holdpoint acquisition, V-bar hopping, and station point acquisition. The proximity operation sensor is used for final closure and capture. A subset of these algorithms, comprising the proximity operations algorithms, could easily be extracted and tailored to a limited objective closure and capture flight demonstration.

Hohwiesner, Bill↗

NASA NTRS1991

On-orbit demonstrations of automated closure and capture using ESA-developed proximity operations technologies and an existing serviceable NASA Explorer platform spacecraft

Since 1984 the European Space Agency (ESA) has been working to develop an autonomous rendezvous and docking capability to enable Hermes to dock automatically with Columbus. As a result, ESA (with Matra, MBB, and other space companies) have developed technologies that are directly supportive of the current NASA initiative for Automated Rendezvous and Capture. Fairchild and Matra would like to discuss the results of the applicable ESA/Matra rendezvous and capture developments and suggest how these capabilities could be used together with an existing NASA Explorer Platform satellite to minimize new development and accomplish a cost-effective automatic closure and capture demonstration program.

Hohweisner, Bill↗

NASA NTRS1991

CTV rendezvous techniques

The cargo transfer vehicle (CTV) requires the capability to perform automated rendezvous with Space Station Freedom (SSF) using onboard sensors and algorithms. The current approach to CTV rendezvous applies techniques developed during the orbital maneuvering vehicle (OMV) program which have been mechanized for automatic, onboard execution. The initial catch up sequence can be described as a passive rendezvous without explicit time of arrival control. The ultimate requirement for this rendezvous technique is to place the CTV on the SSF V-bar axis at some specified downrange distance. The launch vehicle will use yaw steering during orbit injection to achieve the proper phantom plane for nodal biasing. This presentation describes the primary components of the CTV rendezvous scheme.

Jennings, Jerry L.↗

NASA NTRS1995

Long range targeting for space based rendezvous

The work performed under this grant supported the Dexterous Flight Experiment one STS-62 The project required developing hardware and software for automating a TRAC sensor on orbit. The hardware developed by for the flight has been documented through standard NASA channels since it has to pass safety, environmental, and other issues. The software has not been documented previously, therefore, this report provides a software manual for the TRAC code developed for the grant.

Everett, Louis J.↗

NASA NTRS1997

Managing Satellites

Integral Systems, Inc.'s EPOCH 2000 forms the core of NASA's Near Earth Asteroid Rendezvous (NEAR) mission's command and control center. EPOCH 2000, which allows ground operators to monitor and control satellites over a wide area network, owes part of its heritage from work completed to support Goddard Space Flight Center. The software automates telemetry processing, commanding, anomaly detection, and archiving collected data. The NEAR spacecraft, launched in February 1996, will rendezvous in early 1999 and orbit the Asteroid Eros for a year. Integral Systems also provided Low Earth Orbit Autonomous Ground Terminals (LEO-Ts) to NASA. The LEO-T is designed to make it easier and less expensive for principal investigators to obtain telemetry, tracking and control services for their science missions. The company products have supported well over 70 satellite missions aimed at scientific research, meteorology, or communications applications.

Source record↗

NASA NTRS1991

Manned versus unmanned rendezvous and capture

Rendezvous and capture (docking) operations may be performed either automatically or under manual control. In cases where humans are far from the mission site, or high-bandwidth communications lines are not in place, automation is the only option. Such might be the case with unmanned missions to the moon or Mars that involve orbital docking or cargo transfer. In crewed situations where sensors, computation capabilities, and other necessary instrumentation are unavailable, manual control is the only alternative. Power, mass, cost, or other restrictions may limit the availability of the machinery required for an automated rendezvous and capture. The only occasions for which there is a choice about whether to use automated or manual control are those where the vehicle(s) have both the crew and instrumentation necessary to perform the mission either way. The following discussion will focus on the final approach or capture (docking) maneuver. The maneuvers required for long-range rendezvous operations are calculated by computers. It is almost irrelevant whether it is an astronaut, watching a count-down timer who pushes the button firing the thruster or whether the computer keeps track of the time and fires with the astronaut monitoring. The actual manual workload associated with a mission that may take as long as hours or days to perform is small. The workload per unit time increases tremendously during the final approach (docking) phase and this is where the issue of manual versus automatic is more important.

Brody, Adam R.↗

NASA NTRSDate not supplied

Automated Software for Manned Spacecraft - Bridging the Gap from Sci Fi to Reality

With a voice command or a few taps on the console, the spacecraft pivots on a dime at high velocity and gently docks to an orbiting space platform. This is the image most people have of the complex software computations and integrated hardware performance necessary for a spacecraft to successfully perform an automated launch, rendezvous, and docking. Today’s reality is that while computer operations are advancing rapidly, science fiction over-simplifies and over-sells current capabilities. This paper discusses the integration of spacecraft computer automation into the operation of one of the United States’ new Commercial Crew vehicles - the Boeing CST-100 Starliner. Lessons learned by the Boeing Mission Operations team, a private-public partnership with NASA, from conceptual design through real-time operation of the first test flight will be discussed. Focus will center on how operations has learned to use the automated software to their advantage while also knowing how to adjust the automation in response to spacecraft or mission anomalies. One goal of advanced spacecraft automation is the ability to reduce both the crew workload and the ground control footprint while at the same time increasing spacecraft and mission flexibility. Historically, crewed spacecraft required a large number of operators on the ground to use a plethora of tools to compute nominal and contingency mission trajectories. Moving those sophisticated software tools to being onboard the vehicle can reduce the need for such complex ground support. Given that today’s spacecraft software is not yet as capable or as flexible in all circumstances as the computers depicted in movies, there is usually a trade-off between software automation cost and the flexibility of that software resulting in a trade-off between what is performed on the spacecraft and what is left to onboard crew or ground control. For missions that go beyond the Moon, software that autonomously controls nearly every aspect of a crewed mission will become a necessity given the long time delays between the spacecraft and Earth’s ground control teams. The lessons learned by Boeing and its Mission Operations team, through the design and implementation of Starliner’s hardware and software automation, will be able to inform future public and private spacecraft design. As the technologies and capabilities evolve, incorporating lessons learned in successful low Earth orbit commercial crew vehicle missions, spacecraft designs will continue to improve and be able to better enable safe execution of human missions to the Moon and beyond.

Robert C Dempsey↗

NASA NTRSDate not supplied

Automated Software for Manned Spacecraft - Bridging the Gap from Sci Fi to Reality

With a voice command or a few taps on the console, the spacecraft pivots on a dime at high velocity and gently docks to an orbiting space platform. This is the image most people have of the complex software computations and integrated hardware performance necessary for a spacecraft to successfully perform an automated launch, rendezvous, and docking. Today’s reality is that while computer operations are advancing rapidly, science fiction over-simplifies and over-sells current capabilities. This paper discusses the integration of spacecraft computer automation into the operation of one of the United States’ new Commercial Crew vehicles - the Boeing CST-100 Starliner. Lessons learned by the Boeing Mission Operations team, a private-public partnership with NASA, from conceptual design through real-time operation of the first test flight will be discussed. Focus will center on how operations has learned to use the automated software to their advantage while also knowing how to adjust the automation in response to spacecraft or mission anomalies. One goal of advanced spacecraft automation is the ability to reduce both the crew workload and the ground control footprint while at the same time increasing spacecraft and mission flexibility. Historically, crewed spacecraft required a large number of operators on the ground to use a plethora of tools to compute nominal and contingency mission trajectories. Moving those sophisticated software tools to being onboard the vehicle can reduce the need for such complex ground support. Given that today’s spacecraft software is not yet as capable or as flexible in all circumstances as the computers depicted in movies, there is usually a trade-off between software automation cost and the flexibility of that software resulting in a trade-off between what is performed on the spacecraft and what is left to onboard crew or ground control. For missions that go beyond the Moon, software that autonomously controls nearly every aspect of a crewed mission will become a necessity given the long time delays between the spacecraft and Earth’s ground control teams. The lessons learned by Boeing and its Mission Operations team, through the design and implementation of Starliner’s hardware and software automation, will be able to inform future public and private spacecraft design. As the technologies and capabilities evolve, incorporating lessons learned in successful low Earth orbit commercial crew vehicle missions, spacecraft designs will continue to improve and be able to better enable safe execution of human missions to the Moon and beyond.

Robert C. Dempsey↗

NASA NTRSDate not supplied

Automated Software for Crewed Spacecraft - Bridging the Gap from Sci Fi to Reality

With a voice command or a few taps on the console, the spacecraft pivots on a dime at high velocity and gently docks to an orbiting space platform. This is the image most people have of the complex software computations and integrated hardware performance necessary for a spacecraft to successfully perform an automated launch, rendezvous, and docking. Today’s reality is that while computer operations are advancing rapidly, science fiction over-simplifies and over-sells current capabilities. This paper discusses the integration of spacecraft computer automation into the operation of one of the United States’ new Commercial Crew vehicles - the Boeing CST-100 Starliner. Lessons learned by the Boeing Mission Operations team, a private-public partnership with NASA, from conceptual design through real-time operation of the first test flight will be discussed. Focus will center on how operations has learned to use the automated software to their advantage while also knowing how to adjust the automation in response to spacecraft or mission anomalies. One goal of advanced spacecraft automation is the ability to reduce both the crew workload and the ground control footprint while at the same time increasing spacecraft and mission flexibility. Historically, crewed spacecraft required a large number of operators on the ground to use a plethora of tools to compute nominal and contingency mission trajectories. Moving those sophisticated software tools to being onboard the vehicle can reduce the need for such complex ground support. Given that today’s spacecraft software is not yet as capable or as flexible in all circumstances as the computers depicted in movies, there is usually a trade-off between software automation cost and the flexibility of that software resulting in a trade-off between what is performed on the spacecraft and what is left to onboard crew or ground control. For missions that go beyond the Moon, software that autonomously controls nearly every aspect of a crewed mission will become a necessity given the long time delays between the spacecraft and Earth’s ground control teams. The lessons learned by Boeing and its Mission Operations team, through the design and implementation of Starliner’s hardware and software automation, will be able to inform future public and private spacecraft design. As the technologies and capabilities evolve, incorporating lessons learned in successful low Earth orbit commercial crew vehicle missions, spacecraft designs will continue to improve and be able to better enable safe execution of human missions to the Moon and beyond.

Robert C Dempsey↗

NASA NTRSDate not supplied

Automated Software for Crewed Spacecraft - Bridging the Gap from Sci Fi to Reality

With a voice command or a few taps on the console, the spacecraft pivots on a dime at high velocity and gently docks to an orbiting space platform. This is the image most people have of the complex software computations and integrated hardware performance necessary for a spacecraft to successfully perform an automated launch, rendezvous, and docking. Today’s reality is that while computer operations are advancing rapidly, science fiction over-simplifies and over-sells current capabilities. This paper discusses the integration of spacecraft computer automation into the operation of one of the United States’ new Commercial Crew vehicles - the Boeing CST-100 Starliner. Lessons learned by the Boeing Mission Operations team, a unique private-public partnership with NASA, from conceptual design through real-time operation of the first test flight will be discussed along with evolution of the system in preparation for the second uncrewed test flight. Focus will center on how operations has learned to use the automated software to their advantage while also knowing how to adjust the automation in response to spacecraft or mission anomalies.

Robert C. Dempsey↗

NASA NTRS2006

MSFC Analysis of Thermal Control Materials on MISSE

Many different passive thermal control materials were flown as part of the Materials on International Space Station Experiment, including coatings, anodizes, and multi-layer insulation materials. Engineers and scientists at the Marshall Space Flight Center have analyzed a number of these materials, including: Zinc oxide/potassium silicate coating, Zinc orthotitanate/potassium silicate coating, Sulfuric acid anodized aluminum, Various coatings for part marking, automated rendezvous and capture, and astronaut visual aids, FEP Teflon with silver/Inconel backing, and Beta cloth with and without aluminization. These and other material samples were exposed to the low Earth orbital environment of atomic oxygen, ultraviolet radiation, thermal cycling, and hard vacuum, though atomic oxygen exposure was very limited for some samples. Solar absorptance, infrared emittance, and mass measurements indicate the durability of these materials to withstand the space environment. The effect of contamination from an active space station on the performance of white thermal control coatings is discussed.

Finckenor, Miria↗

NASA NTRS1988

Automated low-thrust guidance for the orbital maneuvering vehicle

This paper describes the highly autonomous OMV Guidance Navigation and Control system. Emphasis is placed on a key feature of the design, the low thrust guidance algorithm. The two guidance modes, orbit change guidance and rendezvous guidance, are discussed in detail. It is shown how OMV will automatically transfer from its initial orbit to an arbitrary target orbit and reach a specified rendezvous position relative to the target vehicle.

Rose, Richard E.↗

NASA NTRS1990

Communications and tracking technology discipline

Viewgraphs on communications and tracking technology discipline for Space Station Freedom are presented. The objective is to develop devices, components, and analytical methods to enhance and enable technology to meet space station evolutionary requirements for multiple access (proximity) communications, space-to-ground communications, and tracking as it pertains to rendezvous and docking as well as potential orbital debris warning systems. Topics covered include: optical communications and tracking; monolithic microwave integrated circuit systems; traveling wave tube technology; advanced modulation and coding; and advanced automation.

Romanofsky, Robert↗