SEARCH · Engineering Papers

Results for “Next Generation Uplink”

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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

28 records · Page 2

All sources NASA NTRS DOE OSTI

NASA NTRS2010

Interference Analysis for an Aeronautical Mobile Airport Communications System

The next generation of aeronautical communications for airport surface applications has been identified through a NASA research program and an international collaborative future communications study. The result, endorsed by both the United States and European regulatory agencies is called AeroMACS (Aeronautical Mobile Airport Communications System) and is based upon the IEEE 802.16e mobile wireless standard. Coordinated efforts to develop appropriate aviation standards for the AeroMACS system are now underway within RTCA (United States) and Eurocae (Europe). AeroMACS will be implemented in a recently allocated frequency band, 5091- 5150 MHz. As this band is also occupied by fixed satellite service uplinks, AeroMACS must be designed to avoid interference with this incumbent service. The aspects of AeroMACS operation that present potential interference to the fixed satellite service are under analysis in order to enable the definition of standards that assure that such interference will be avoided. The NASA Glenn Research Center has been involved in this analysis, and the first results of modeling and simulation efforts directed at this analysis are the subject of this paper.12

Wilson, Jeffrey D.↗

NASA NTRS2011

Interference Analysis for an Aeronautical Mobile Airport Communications System

The next generation of aeronautical communications for airport surface applications has been identified through a NASA research program and an international collaborative future communications study. The result, endorsed by both the United States and European regulatory agencies is called AeroMACS (Aeronautical Mobile Airport Communications System) and is based upon the IEEE 802.16e mobile wireless standard. Coordinated efforts to develop appropriate aviation standards for the AeroMACS system are now underway within RTCA (United States) and Eurocae (Europe). AeroMACS will be implemented in a recently allocated frequency band, 5091-5150 MHz. As this band is also occupied by fixed satellite service uplinks, AeroMACS must be designed to avoid interference with this incumbent service. The aspects of AeroMACS operation that present potential interference to the fixed satellite service are under analysis in order to enable the definition of standards that assure that such interference will be avoided. The NASA Glenn Research Center has been involved in this analysis, and the first results of modeling and simulation efforts directed at this analysis are the subject of this presentation.

Wilson, Jeffrey D.↗

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 NTRS2011

An Examination of Selected Datacom Options for the Near-Term Implementation of Trajectory Based Operations

A primary feature of the Next Generation Air Transportation System (NextGen) is trajectory based operations (TBO). Under TBO, aircraft flight plans are known to computer systems on the ground that aid in scheduling and separation. The Future Air Navigation System (FANS) was developed to support TBO, but relatively few aircraft in the US are FANSequipped. Thus, any near-term implementation must provide TBO procedures for non-FANS aircraft. Previous research has explored controller clearances, but any implementation must also provide procedures for aircraft requests. The work presented here aims to surface issues surrounding TBO communication procedures for non-FANS aircraft and for aircraft requesting deviations around weather. Three types of communication were explored: Voice, FANS, and ACARS,(Aircraft Communications Addressing and Reporting System). ACARS and FANS are datacom systems that differ in that FANS allows uplinked flight plans to be loaded into the Flight Management System (FMS), while ACARS delivers flight plans as text that must be entered manually via the Control Display Unit (CDU). Sixteen pilots (eight two-person flight decks) and four controllers participated in 32 20-minute scenarios that required the flight decks to navigate through convective weather as they approached their top of descents (TODs). Findings: The rate of non-conformance was higher than anticipated, with aircraft off path more than 20% of the time. Controllers did not differentiate between the ACARS and FANS datacom, and were mixed in their preference for Voice vs. datacom (ACARS and FANS). Pilots uniformly preferred Voice to datacom, particularly ACARS. Much of their dislike appears to result from the slow response times in the datacom conditions. As a result, participants frequently resorted to voice communication. These results imply that, before implementing TBO in environments where pilots make weather deviation requests, further research is needed to develop communication procedures that integrate voice and datacom.

trajectory based operations↗

NASA NTRS2014

Use of Semi-Autonomous Tools for ISS Commanding and Monitoring

As the International Space Station (ISS) has moved into a utilization phase, operations have shifted to become more ground-based with fewer mission control personnel monitoring and commanding multiple ISS systems. This shift to fewer people monitoring more systems has prompted use of semi-autonomous console tools in the ISS Mission Control Center (MCC) to help flight controllers command and monitor the ISS. These console tools perform routine operational procedures while keeping the human operator "in the loop" to monitor and intervene when off-nominal events arise. Two such tools, the Pre-positioned Load (PPL) Loader and Automatic Operators Recorder Manager (AutoORM), are used by the ISS Communications RF Onboard Networks Utilization Specialist (CRONUS) flight control position. CRONUS is responsible for simultaneously commanding and monitoring the ISS Command & Data Handling (C&DH) and Communications and Tracking (C&T) systems. PPL Loader is used to uplink small pieces of frequently changed software data tables, called PPLs, to ISS computers to support different ISS operations. In order to uplink a PPL, a data load command must be built that contains multiple user-input fields. Next, a multiple step commanding and verification procedure must be performed to enable an onboard computer for software uplink, uplink the PPL, verify the PPL has incorporated correctly, and disable the computer for software uplink. PPL Loader provides different levels of automation in both building and uplinking these commands. In its manual mode, PPL Loader automatically builds the PPL data load commands but allows the flight controller to verify and save the commands for future uplink. In its auto mode, PPL Loader automatically builds the PPL data load commands for flight controller verification, but automatically performs the PPL uplink procedure by sending commands and performing verification checks while notifying CRONUS of procedure step completion. If an off-nominal condition occurs during procedure execution, PPL Loader notifies CRONUS through popup messages, allowing CRONUS to examine the situation and choose an option of how PPL loader should proceed with the procedure. The use of PPL Loader to perform frequent, routine PPL uplinks offloads CRONUS to better monitor two ISS systems. It also reduces procedure performance time and decreases risk of command errors. AutoORM identifies ISS communication outage periods and builds commands to lock, playback, and unlock ISS Operations Recorder files. Operation Recorder files are circular buffer files of continually recorded ISS telemetry data. Sections of these files can be locked from further writing, be played back to capture telemetry data that occurred during an ISS loss of signal (LOS) period, and then be unlocked for future recording use. Downlinked Operation Recorder files are used by mission support teams for data analysis, especially if failures occur during LOS. The commands to lock, playback, and unlock Operations Recorder files are encompassed in three different operational procedures and contain multiple user-input fields. AutoORM provides different levels of automation for building and uplinking the commands to lock, playback, and unlock Operations Recorder files. In its automatic mode, AutoORM automatically detects ISS LOS periods, then generates and uplinks the commands to lock, playback, and unlock Operations Recorder files when MCC regains signal with ISS. AutoORM also features semi-autonomous and manual modes which integrate CRONUS more into the command verification and uplink process. AutoORMs ability to automatically detect ISS LOS periods and build the necessary commands to preserve, playback, and release recorded telemetry data greatly offloads CRONUS to perform more high-level cognitive tasks, such as mission planning and anomaly troubleshooting. Additionally, since Operations Recorder commands contain numerical time input fields which are tedious for a human to manually build, AutoORM's ability to automatically build commands reduces operational command errors. PPL Loader and AutoORM demonstrate principles of semi-autonomous operational tools that will benefit future space mission operations. Both tools employ different levels of automation to perform simple and routine procedures, thereby offloading human operators to perform higher-level cognitive tasks. Because both tools provide procedure execution status and highlight off-nominal indications, the flight controller is able to intervene during procedure execution if needed. Semi-autonomous tools and systems that can perform routine procedures, yet keep human operators informed of execution, will be essential in future long-duration missions where the onboard crew will be solely responsible for spacecraft monitoring and control.

Brzezinski, Amy S.↗

NASA NTRS2014

3D Printing In Zero-G ISS Technology Demonstration

The National Aeronautics and Space Administration (NASA) has a long term strategy to fabricate components and equipment on‐demand for manned missions to the Moon, Mars, and beyond. To support this strategy, NASA and Made in Space, Inc. are developing the 3D Printing In Zero‐G payload as a Technology Demonstration for the International Space Station (ISS). The 3D Printing In Zero‐G experiment ('3D Print') will be the first machine to perform 3D printing in space. The greater the distance from Earth and the longer the mission duration, the more difficult resupply becomes; this requires a change from the current spares, maintenance, repair, and hardware design model that has been used on the International Space Station (ISS) up until now. Given the extension of the ISS Program, which will inevitably result in replacement parts being required, the ISS is an ideal platform to begin changing the current model for resupply and repair to one that is more suitable for all exploration missions. 3D Printing, more formally known as Additive Manufacturing, is the method of building parts/objects/tools layer‐by‐layer. The 3D Print experiment will use extrusion‐based additive manufacturing, which involves building an object out of plastic deposited by a wire‐feed via an extruder head. Parts can be printed from data files loaded on the device at launch, as well as additional files uplinked to the device while on‐orbit. The plastic extrusion additive manufacturing process is a low‐energy, low‐mass solution to many common needs on board the ISS. The 3D Print payload will serve as the ideal first step to proving that process in space. It is unreasonable to expect NASA to launch large blocks of material from which parts or tools can be traditionally machined, and even more unreasonable to fly up multiple drill bits that would be required to machine parts from aerospace‐grade materials such as titanium 6‐4 alloy and Inconel. The technology to produce parts on demand, in space, offers unique design options that are not possible through traditional manufacturing methods while offering cost-effective, high‐precision, low‐unit on‐demand manufacturing. Thus, Additive Manufacturing capabilities are the foundation of an advanced manufacturing in space roadmap. The 3D Printing In Zero‐G experiment will demonstrate the capability of utilizing Additive Manufacturing technology in space. This will serve as the enabling first step to realizing an additive manufacturing, print‐on‐demand "machine shop" for long‐duration missions and sustaining human exploration of other planets, where there is extremely limited ability and availability of Earth‐based logistics support. Simply put, Additive Manufacturing in space is a critical enabling technology for NASA. It will provide the capability to produce hardware on‐demand, directly lowering cost and decreasing risk by having the exact part or tool needed in the time it takes to print. This capability will also provide the much‐needed solution to the cost, volume, and up‐mass constraints that prohibit launching everything needed for long‐duration or long‐distance missions from Earth, including spare parts and replacement systems. A successful mission for the 3D Printing In Zero‐G payload is the first step to demonstrate the capability of printing on orbit. The data gathered and lessons learned from this demonstration will be applied to the next generation of additive manufacturing technology on orbit. It is expected that Additive Manufacturing technology will quickly become a critical part of any mission's infrastructure.

Werkheiser, Niki↗

NASA NTRS1999

Autonomous Command Operations of the WIRE Spacecraft

This paper presents operational innovations which will be introduced on NASA's Wide Field Infrared Explorer (WIRE) mission. These innovations include an end-to-end design architecture for an autonomous commanding capability for the uplink of command loads during unattended station contacts. The WIRE mission is the fifth and final mission of NASA's Goddard Space Flight Center Small Explorer (SMEX) series to be launched in March of 1999. Its primary mission is the targeting of deep space fields using an ultra-cooled infrared telescope. Due to its mission design WIRE command loads are large (approximately 40 Kbytes per 24 hours) and must be performed daily. To reduce the cost of mission operations support that would be required in order to uplink command loads, the WIRE Flight Operations Team has implemented all autonomous command loading capability. This capability allows completely unattended operations over a typical two-day weekend period. The key factors driving design and implementation of this capability were: 1) integration with already existing ground system autonomous capabilities and systems, 2) the desire to evolve autonomous operations capabilities based upon previous SMEX operations experience - specifically the TRACE mission, 3) integration with ground station operations - both autonomous and man-tended, 4) low cost and quick implementation, and 5) end-to-end system robustness. A trade-off study was performed to examine these factors in light of the low-cost, higher-risk SMEX mission philosophy. The study concluded that a STOL (Spacecraft Test and Operations Language) based script, highly integrated with other scripts used to perform autonomous operations, was best suited given the budget and goals of the mission. Each of these factors is discussed in addition to use of the TRACE mission as a testbed for autonomous commanding prior to implementation on WIRE. The capabilities implemented on the WIRE mission are an example of a low-cost, robust, and efficient method for autonomous command loading when implemented with other autonomous features of the ground system. They call be used as a design and implementation template by other missions interested in evolving toward autonomous and lower cost operations. Additionally, the WIRE spacecraft will be used as an operational testbed upon completion of its nominal mission later in 1999. One idea being studied is advanced on-board modeling. Advanced on-board modeling techniques will be used to more efficiently display the spacecraft state. This health and safety information could be used by engineers on the ground or could be used by tile spacecraft for its own assessments. Additionally, this same state information could also be input into the event-driven scheduling system, as the scheduling system will need to assess the spacecraft state before undertaking a new activity. Advanced modeling techniques are being evaluated for a number of NASA missions including The Next Generation Space Telescope (NGST), which is scheduled to launch in 2007.

Walyus, Keith↗

NASA NTRS2015

X-Band CubeSat Communication System Demonstration

Today's CubeSats mostly operate their communications at UHF- and S-band frequencies. UHF band is presently crowded, thus downlink communications are at lower data rates due to bandwidth limitations and are unreliable due to interference. This research presents an end-to-end robust, innovative, compact, efficient and low cost S-band uplink and X-band downlink CubeSat communication system demonstration between a balloon and a Near Earth Network (NEN) ground system. Since communication systems serve as umbilical cords for space missions, demonstration of this X-band communication system is critical for successfully supporting current and future CubeSat communication needs. This research has three main objectives. The first objective is to design, simulate, and test a CubeSat S- and X-band communication system. Satellite Tool Kit (STK) dynamic link budget calculations and HFSS Simulations and modeling results have been used to trade the merit of various designs for small satellite applications. S- and X-band antennas have been tested in the compact antenna test range at Goddard Space Flight Center (GSFC) to gather radiation pattern data. The second objective is simulate and test a CubeSat compatible X-band communication system at 12.5Mbps including S-band antennas, X-band antennas, Laboratory for Atmospheric and Space Physics (LASP) /GSFC transmitter and an S-band receiver from TRL-5 to TRL-8 by the end of this effort. Different X-band communication system components (antennas, diplexers, etc.) from GSFC, other NASA centers, universities, and private companies have been investigated and traded, and a complete component list for the communication system baseline has been developed by performing analytical and numerical analysis. This objective also includes running simulations and performing trades between different X-band antenna systems to optimize communication system performance. The final objective is to perform an end-to-end X-band CubeSat communication system demonstration between a balloon and/or a sounding rocket and a Near Earth Network (NEN) ground system. This paper presents CubeSat communication systems simulation results, analysis of X-band and S-band antennas and RF front-end components, transceiver design, analysis and optimization of space-to-ground communication performance, subsystem development, as well as the test results for an end-to-end X-band CubeSat communication system demonstration. The outcome of this work will be used to pave the way for next generation NEN-compatible X-band CubeSat communication systems to support higher data rates with more advanced modulation and forward error correction (FEC) coding schemes, and to support and attract new science missions at lower cost. It also includes an abbreviated concept of operations for CubeSat users to utilize the NEN, starting from first contact with NASA's communication network and continuing through on-orbit operations.

NEN↗

NASA NTRS2000

Nozomi Cis-Lunar Phase Orbit Determination

Japan's Institute of Space and Astronautical Science (ISAS) launched Nozomi, its first mission to the planet Mars using the newly developed M-V launch vehicle on July 3, 1998. Scientific objectives of the mission are to study the structure and dynamics of the Martian upper atmosphere and its interaction with the solar wind. Nozomi is a cooperative mission between ISAS and the National Aeronautics and Space Administration (NASA). The NASA contribution includes navigation and tracking services provided by the Jet Propulsion Laboratory (JPL). The spacecraft also serves as an engineering demonstration of basic technology for planetary exploration. One of the new technologies was a unique trajectory, developed by ISAS, which used solar gravitational perturbations at the weak stability boundary as an aid to achieve an Earth-Mars transfer orbit. This trajectory saves approximately 120 m/s of Delta V compared to direct hyperbolic insertion and is considered an enabling technology for the mission. Nozomi was the first spacecraft to employ this trajectory and provided on-orbit validation of the technique. The trajectory was achieved by initially placing the spacecraft in a highly elliptical cis-lunar phasing orbit. Six maneuvers were performed during this period to correct injection errors and target an outbound lunar swingby in September 1998. The gravity assist from the lunar swingby raised apogee to the vicinity of the weak stability boundary. After three more targeting maneuvers, Nozomi performed an inbound lunar swingby followed immediately by a powered Earth swingby in late December 1998. A 420 m/s Trans Mars Insertion (TMI) burn at the final Earth periapsis was intended to place the spacecraft on a heliocentric trajectory leading to Mars orbit insertion in October 1999. Orbit determination for Nozomi is performed in parallel by both ISAS and the Multi-Mission Navigation (MMNAV) group at JPL. This was an advantage for the mission because each group would generate solutions based on data collected from their respective tracking networks. Spacecraft events, such as sequence uplinks and maneuvers, were generally scheduled during passes at the Usuda tracking station in Japan. As a result, maneuver design and reconstruction was derived from MMNAV solutions based on JPL tracking data obtained immediately prior to or following maneuvers. Data was also exchanged between ISAS and MMNAV so orbit determination could be performed on joint data sets in support of critical targeting late in the cis-lunar phase. In this paper, information regarding the MMNAV orbit determination effort for the first six months of the mission is presented. The spacecraft trajectory is characterized first, followed by a discussion of the orbit determination estimation procedure and models. Results from selected orbit solutions are presented and compared against reconstructed trajectories. One area of emphasis in this paper is orbit determination in the vicinity of the weak stability boundary. Precise navigation was necessary to target the second lunar swingby and the powered Earth swingby. Delivery accuracy of 150 m was required for these critical encounters, but a number of factors contributed to the general degradation of orbit determination accuracy. This included the fact that the spacecraft was at apogee, at a range of 1.7 million km and moving at less than I km/sec perpendicular to the line of sight. Nozomi was also close to zero degrees declination where there are known limitations on orbit determination performance. Finally, S-band tracking data was acquired through the Nozomi backup low gain antenna. This antenna is offset from the axis of this spin stabilized spacecraft and superimposed large signatures in the Doppler and range data. These difficulties were overcome by combining long data arcs, spanning several maneuvers, with a high fidelity solar pressure model. The model included a physically accurate representation of the spacecraft structure and a high time resolution orientation model. Observation modeling included the removal of the spin induced Doppler bias, spin signature and per pass correction of range calibration errors applied for data leading up to critical events. As a result, all orbit determination goals were met. A second area of emphasis in this paper is the JPL tracking and orbit determination effort in support of the TMI maneuver. TMI occurred out of contact with ground stations and the JPL Goldstone tracking complex had the first pass following the bum. As a result, MMNAV had the responsibility to make a rapid assessment of the maneuver performance. MMNAV made the determination that a 100 m/s under bum had occurred and promptly informed ISAS via voice lines. ISAS immediately began preparations for a correction maneuver (TMIc), which had to be performed during the next Usuda pass. The near real time assessment by MMNAV provided accurate antenna frequency and pointing updates for the spacecraft acquisition at Usuda and the close coordination between the two agencies enabled the design and successful execution of the TMc maneuver. Propellant consumption during the correction burn dictated that the mission be redesigned. ISAS developed a new plan which adds 3 full solar orbits, two Earth swingbys and one lunar swingby with arrival at Mars in January 2004. The final Mars orbit will still enable the mission to achieve all of its science objectives.

Ryne, Mark↗