Search NASA⌕ Search

SEARCH · Search NASA

Results for “additional protocol”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

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

At least 19 records
All sourcesNASA NTRSDOE OSTI
NASA NTRS2013

Mission Operations Center (MOC) - Precipitation Processing System (PPS) Interface Software System (MPISS)

MPISS is an automatic file transfer system that implements a combination of standard and mission-unique transfer protocols required by the Global Precipitation Measurement Mission (GPM) Precipitation Processing System (PPS) to control the flow of data between the MOC and the PPS. The primary features of MPISS are file transfers (both with and without PPS specific protocols), logging of file transfer and system events to local files and a standard messaging bus, short term storage of data files to facilitate retransmissions, and generation of file transfer accounting reports. The system includes a graphical user interface (GUI) to control the system, allow manual operations, and to display events in real time. The PPS specific protocols are an enhanced version of those that were developed for the Tropical Rainfall Measuring Mission (TRMM). All file transfers between the MOC and the PPS use the SSH File Transfer Protocol (SFTP). For reports and data files generated within the MOC, no additional protocols are used when transferring files to the PPS. For observatory data files, an additional handshaking protocol of data notices and data receipts is used. MPISS generates and sends to the PPS data notices containing data start and stop times along with a checksum for the file for each observatory data file transmitted. MPISS retrieves the PPS generated data receipts that indicate the success or failure of the PPS to ingest the data file and/or notice. MPISS retransmits the appropriate files as indicated in the receipt when required. MPISS also automatically retrieves files from the PPS. The unique feature of this software is the use of both standard and PPS specific protocols in parallel. The advantage of this capability is that it supports users that require the PPS protocol as well as those that do not require it. The system is highly configurable to accommodate the needs of future users.

Ferrara, Jeffrey↗
NASA NTRS2000

Internet Access to Spacecraft

The Operating Missions as Nodes on the Internet (OMNI) project at NASA's Goddard Space flight Center (GSFC), is demonstrating the use of standard Internet protocols for spacecraft communication systems. This year, demonstrations of Internet access to a flying spacecraft have been performed with the UoSAT-12 spacecraft owned and operated by Surrey Satellite Technology Ltd. (SSTL). Previously, demonstrations were performed using a ground satellite simulator and NASA's Tracking and Data Relay Satellite System (TDRSS). These activities are part of NASA's Space Operations Management Office (SOMO) Technology Program, The work is focused on defining the communication architecture for future NASA missions to support both NASA's "faster, better, cheaper" concept and to enable new types of collaborative science. The use of standard Internet communication technology for spacecraft simplifies design, supports initial integration and test across an IP based network, and enables direct communication between scientists and instruments as well as between different spacecraft, The most recent demonstrations consisted of uploading an Internet Protocol (IP) software stack to the UoSAT- 12 spacecraft, simple modifications to the SSTL ground station, and a series of tests to measure performance of various Internet applications. The spacecraft was reconfigured on orbit at very low cost. The total period between concept and the first tests was only 3 months. The tests included basic network connectivity (PING), automated clock synchronization (NTP), and reliable file transfers (FTP). Future tests are planned to include additional protocols such as Mobile IP, e-mail, and virtual private networks (VPN) to enable automated, operational spacecraft communication networks. The work performed and results of the initial phase of tests are summarized in this paper. This work is funded and directed by NASA/GSFC with technical leadership by CSC in arrangement with SSTL, and Vytek Wireless.

Rash, James↗
NASA NTRS2005

A WOUND CARE AND INTRAVENOUS ACCESS SUMMIT FOR ON-ORBIT CARE

Wound care issues and the ability to establish intravenous (IV) access among injured or ill crew members are a source of concern for NASA flight surgeons. Indeed, the microgravity environment and the remote nature of the International Space Station (ISS) pose unique challenges in diagnosing and treating an injured astronaut. Therefore, it is necessary to identify and adapt the best evidence based terrestrial practices regarding wound care, hemostasis, and IV access for use on the ISS. Methods: A panel of consultants was convened to evaluate the adequacy of the current ISS in-flight medical system for diagnosis and treatment of wounds and establishing IV access by a nonclinician crew medical officer. Participants were acknowledged experts in terrestrial wound care and/or operational medicine. Prior to the meeting, each panelist was encouraged to participate in a pre-summit online forum. Results: Eight external experts participated in a face-to-face meeting held at NASA-Johnson Space Center. Recommendations were made to augment the space station pharmacopoeia, as well as current wound care diagnostic, therapeutic, and deorbit criteria protocols. Additionally, suggestions were offered regarding IV access techniques and devices for use in the microgravity environment. Discussion: The results of the expert panel provide an evidence-based approach to the diagnosis and care of wounds in an injured astronaut on aboard the ISS. The results of the panel underscored the need for further research in wound therapy and IV access devices.

Scheuring, R.↗
NASA NTRS2006

Space-based Networking Technology Developments in the Interplanetary Network Directorate Information Technology Program

Described recent development of communications protocols, services, and associated tools targeted to reduce risk, reduce cost and increase efficiency of IND infrastructure and supported mission operations. Space-based networking technologies developed were: a) Provide differentiated quality of service (QoS) that will give precedence to traffic that users have selected as having the greatest importance and/or time-criticality; b) Improve the total value of information to users through the use of QoS prioritization techniques; c) Increase operational flexibility and improve command-response turnaround; d) Enable new class of networked and collaborative science missions; e) Simplify applications interfaces to communications services; and f) Reduce risk and cost from a common object model and automated scheduling and communications protocols. Technologies are described in three general areas: communications scheduling, middleware, and protocols. Additionally developed simulation environment, which provides comprehensive, quantitative understanding of the technologies performance within overall, evolving architecture, as well as ability to refine & optimize specific components.

scheduling↗
NASA NTRS2015

Statistical Analysis of Large Simulated Yield Datasets for Studying Climate Effects

Many studies have been carried out during the last decade to study the effect of climate change on crop yields and other key crop characteristics. In these studies, one or several crop models were used to simulate crop growth and development for different climate scenarios that correspond to different projections of atmospheric CO2 concentration, temperature, and rainfall changes (Semenov et al., 1996; Tubiello and Ewert, 2002; White et al., 2011). The Agricultural Model Intercomparison and Improvement Project (AgMIP; Rosenzweig et al., 2013) builds on these studies with the goal of using an ensemble of multiple crop models in order to assess effects of climate change scenarios for several crops in contrasting environments. These studies generate large datasets, including thousands of simulated crop yield data. They include series of yield values obtained by combining several crop models with different climate scenarios that are defined by several climatic variables (temperature, CO2, rainfall, etc.). Such datasets potentially provide useful information on the possible effects of different climate change scenarios on crop yields. However, it is sometimes difficult to analyze these datasets and to summarize them in a useful way due to their structural complexity; simulated yield data can differ among contrasting climate scenarios, sites, and crop models. Another issue is that it is not straightforward to extrapolate the results obtained for the scenarios to alternative climate change scenarios not initially included in the simulation protocols. Additional dynamic crop model simulations for new climate change scenarios are an option but this approach is costly, especially when a large number of crop models are used to generate the simulated data, as in AgMIP. Statistical models have been used to analyze responses of measured yield data to climate variables in past studies (Lobell et al., 2011), but the use of a statistical model to analyze yields simulated by complex process-based crop models is a rather new idea. We demonstrate herewith that statistical methods can play an important role in analyzing simulated yield data sets obtained from the ensembles of process-based crop models. Formal statistical analysis is helpful to estimate the effects of different climatic variables on yield, and to describe the between-model variability of these effects.

climate↗
NASA NTRSDate not supplied

Firmware Architecture of the ARMADAS Bolting Robot

The Automated Reconfigurable Mission Adaptive Digital Assembly Systems (ARMADAS) project, under development at NASA Ames Research Center, has demonstrated on-ground autonomous robotic assembly of extensive digital structures, and it is now moving forward towards in-space demonstration. The ARMADAS system comprises of the operation software, the operation user interface (opsUI), and a swarm of robots. The robotic system consists of a multitude of collaborative agents specifically designed to transport, place and bolt the building blocks, called voxels (volumetric pixels). This paper focuses on the bolting robot, referred to as Mobile Metamaterial Internal Co-Integrator (MMIC-I). MMIC-I is a battery-powered crawling robot. It navigates the structure through extension, contraction and gripping. Two distinct controller boards operate the robot's two symmetric modules, referred to as module A and B. Board A is the master board: it coordinates motion planning and motion primitives execution, hosts the WiFi client, performs periodic self-assessment and system idle check and triggers faults if anomalies are detected. Board B periodically sends a heartbeat to board A, through a wired communication channel that uses the Serial protocol. Additionally, board A's WiFi client receives heartbeat packet requests or motion/bolting commands from a dedicated server board, and acknowledges reception sending back a response heartbeat packet containing information about the overall robot status, e. g. electrical current and voltage values, target and actual angles, operating mode, fault status. Whenever a motion command is sent, the motion planning section of the firmware determines the current robot configuration, using Inertial Measurement Unit readings and the motors Pulse Width Modulation values. Afterwards, it calculates the list of primitives needed to reach the target state, and controls their execution in the proper order. MMIC-I can receive and execute motion and bolting commands only when it is in operational mode. MMIC-I has three operating modes: standby, operational and safed. Standby mode is automatically entered upon startup. While in standby mode, all motors are powered off, and the only accepted commands are the ones relative to a change of mode and heartbeat packet request. Fault detection causes the robot to automatically enter safed or standby mode. Whenever the detected fault occurs within a motion and requires immediate intervention, e. g. an over-current situation, the robot enters safed mode. Safed mode powers off all motors except for the locomotion module, thus preventing the robot from collapsing. Conversely, when the detected fault doesn't require immediate intervention (low battery warning, for instance), the robot enters standby mode after completing the ongoing motion. This paper provides a detailed discussion of MMIC-I's firmware architecture. It accurately describes the implementation approach for each module: sensor data reading, motor control and actuation, WiFi server-client communication, intra-boards Serial communication, operating modes and autonomous fault detection, motion planning, coordination and execution, etc. Moreover, in support of the software description, this paper includes a thorough characterization of MMIC-I's hardware and avionics.

In-space assembly↗
NASA NTRS2024

Updates to NASA’s Break-in-Prebreathe Rules Due to Type II Decompression Sickness Risk Considerations

INTRODUCTION. Investigation of a central neurological decompression sickness (DCS) case during ground testing at Johnson Space Center identified a break-in-prebreathe (BIP) 13 minutes prior to depressurization as the leading credible cause despite applicable prebreathe payback rules being followed. Applicable NASA rules, for ground and flight, directed 2:1 payback of breaks up to 10 mins in duration, regardless of when a break occurs relative to depress. Full restart of prebreathe is directed following breaks > 10 min. The adequacy of NASA’s BIP rules was evaluated prior to resuming hypobaric ground testing or ISS extravehicular activities. METHODS. The following information sources were reviewed prior to formulating recommendations: i) Type II DCS case report and investigation findings; ii) documented rationale for existing flight rules, iii) consultations with subject matter experts involved in definition of existing flight rules (several of whom had since left NASA), iv) relevant published literature, v) model estimates of tissue on-gassing and off-gassing, and vi) NASA’s operational experience with late breaks in prebreathe. RESULTS. NASA’s nominal prebreathe protocols are validated via extensive ground testing to ensure DCS risk is reduced to within acceptable limits. Conversely, there exists a paucity of data, no validated models, and limited documentation regarding BIP risk for NASA prebreathe protocols. Flight rules implemented for shuttle and later ISS are based primarily on expert opinion and an assumption of symmetric on-gassing and off-gassing, which would make 2:1 payback a conservative mitigation for a BIP. Assumption of exponential gas kinetics makes late breaks higher risk, or require greater payback, than earlier breaks. Two BIPs have occurred using the current ISS prebreathe protocol, each of which was followed by greater than 2:1 payback and at least 59 minutes of 100% O2 pre-depress. No DCS cases have been reported during shuttle or ISS EVA operations. DISCUSSION. Interim changes were implemented to protect against late breaks during ground and flight prebreathes by ensuring negligible difference in conservatively modeled ppN2 pre-depress compared to nominal validated protocols. Additional documentation and literature review as well as chamber test planning are ongoing with the objective of further ground and flight rule updates and validation of a BIP risk model.

Prebreathe↗
NASA NTRS2024

Updates to NASA’s Break-in-Prebreathe Rules Due to Type II Decompression Sickness Risk Considerations

INTRODUCTION. Investigation of a central neurological decompression sickness (DCS) case during ground testing at Johnson Space Center identified a break-in-prebreathe (BIP) 13 minutes prior to depressurization as the leading credible cause despite applicable prebreathe payback rules being followed. Applicable NASA rules, for ground and flight, directed 2:1 payback of breaks up to 10 mins in duration, regardless of when a break occurs relative to depress. Full restart of prebreathe is directed following breaks > 10 min. The adequacy of NASA’s BIP rules was evaluated prior to resuming hypobaric ground testing or ISS extravehicular activities. METHODS. The following information sources were reviewed prior to formulating recommendations: i) Type II DCS case report and investigation findings; ii) documented rationale for existing flight rules, iii) consultations with subject matter experts involved in definition of existing flight rules (several of whom had since left NASA), iv) relevant published literature, v) model estimates of tissue on-gassing and off-gassing, and vi) NASA’s operational experience with late breaks in prebreathe. RESULTS. NASA’s nominal prebreathe protocols are validated via extensive ground testing to ensure DCS risk is reduced to within acceptable limits. Conversely, there exists a paucity of data, no validated models, and limited documentation regarding BIP risk for NASA prebreathe protocols. Flight rules implemented for shuttle and later ISS are based primarily on expert opinion and an assumption of symmetric on-gassing and off-gassing, which would make 2:1 payback a conservative mitigation for a BIP. Assumption of exponential gas kinetics makes late breaks higher risk, or require greater payback, than earlier breaks. Two BIPs have occurred using the current ISS prebreathe protocol, each of which was followed by greater than 2:1 payback and at least 59 minutes of 100% O2 pre-depress. No DCS cases have been reported during shuttle or ISS EVA operations. DISCUSSION. Interim changes were implemented to protect against late breaks during ground and flight prebreathes by ensuring negligible difference in conservatively modeled ppN2 pre-depress compared to nominal validated protocols. Additional documentation and literature review as well as chamber test planning are ongoing with the objective of further ground and flight rule updates and validation of a BIP risk model.

Prebreathe↗
NASA NTRS2000

Operational Implementation of a 2-Hour Prebreathe Protocol for International Space Station

Procedures, equipment, and analytical techniques were developed to implement the ground tested 2-hour protocol in-flight operations. The methods are: 1) The flight protocol incorporates additional safety margin over the ground tested protocol. This includes up to 20 min of additional time on enriched O2 during suit purge and pressure check, increased duration of extravehicular activity (EVA) preparation exercise during O2 prebreathing (up to 90 min vs; the tested 24 min), and reduced rates of depressurization. The ground test observations were combined with model projections of the conservative measures (using statistical models from Duke University and NASA JSQ to bound the risk of Type I and Type II decompression sickness (DCS). 2) An inflight exercise device using the in-flight ergometer and elastic tubes for upper body exercise was developed to replicate the dual cycle exercise in the ground trials. 3) A new in-flight breathing system was developed and man-tested. 4) A process to monitor inflight experience with the protocol, including the use of an in-suit Doppler bubble monitor when available, was developed. The results are: 1) The model projections of the conservative factors of the operational protocol were shown to reduce the risk of DCS to levels consistent with the observations of no DCS to date in the shuttle program. 2) Cross over trials of the dual cycle ergometer used in ground tests and the in-flight exercise system verified that02consumption and the % division of work between upper and lower body was not significantly different at the p= 0.05 level. 3) The in-flight breathing system was demonstrated to support work rates generating 75% O2(max) in 95 percentile subjects. 4) An in-flight monitoring plan with acceptance criteria was put in place for the 2-hour prebreathe protocol. And the conclusions are: The 2-hour protocol has been approved for flight, and all implementation efforts are in place to allow use of the protocol as early as flight ISS 7A, now scheduled in November of 2000.

Waligora, James M.↗
NASA NTRS2009

Survey of Software Problems with Impacts to 'Campout' Protocol Extravehicular Activity (EVA) Prebreathe

During International Space Station campout protocol ExtraVehicular Activity (EVA) preparations, the crew is isolated overnight in the small airlock volume in a reduced pressure, oxygen enriched atmosphere. As such, there are special considerations for the software in terms of air composition, pressure control and emergency responses. For one, the ISS software must monitor and manage two distinct atmospheres. Also, the small airlock volume is especially sensitive to small changes in the environment, and what would be a minor emergency in the larger vehicle volume can have catastrophic results in the isolated airlock. Finally, in cases of emergency, the crew needs to rapidly egress the airlock, which requires an aggressive automatic repressurization to equalize pressure on the hatch. This paper will describe the software which is modified for the airlock campout protocol. In addition, the paper will describe the software problems and hardware problems with software workarounds which have affected campout protocol.

Diderich, Greg↗
NASA NTRS2004

Spectroscopic Determination of the Physical Conditions in Hot Optically Thin Sources

Astrophysical Plasma Emission Database - APED consists of atomic data, primarily theoretical, needed to calculate X-ray through optical emission spectra of hot thermal plasmas. These data are supplemented by experimental values, such as laboratory plasma wave- lengths, and are validated by experiment only rarely. Thus the comparison of predicted spectra to astrophysical spectra serves as invaluable feedback on the quality of the models. Following up on unfavorable comparisons, we have communicated atomic data needs to atomic theorists and experimental plasma physicists so that improvements can be made to the database. The database is now reasonably complete from approx. 1 to 30 A, and from - 90 to 180 A, with significant gaps remaining in the range 30 to 90 A. Astrophysical Plasma Emission Code - APEC uses the APED data as inputs and computes level populations and line emissivities using a rate matrix solver. Tabulated models for a fine grid of temperatures and densities can be applied to observational data. The current public version of APEC output uses an input ionization balance model, assuming CIE; however, we have a working version to calculate the ionization state of the gas. We will begin testing non-equilibrium ionization (NEI) models over the next year - we are now finalizing the atomic database needed to perform the ionization state calculations. At that time, the code will be made public. We have developed optimized error codes, additional testing protocols and substantial documentation, in preparation for this public release. Secondarily, we have begun to investigate the use of APED and APEC for X-ray photoionized plasma, beginning with opacity modeling (e.g. warm absorbers). Application to bright AGN Chandra grating spectra suggests that the accurate wavelengths in APED are of great importance to fitting the data. We are exploring additional subroutines to APEC to extend its usefulness for X-ray photoionized plasma, e.g. to include collisional or photo-excitation of metastable levels for absorption.

Oliversen, Ronald J.↗
NASA NTRS2002

Mobile Router Developed and Tested

The NASA Glenn Research Center, under a NASA Space Act Agreement with Cisco Systems, has been performing joint networking research to apply Internet-based technologies and protocols to space-based communications. As a result of this research, NASA performed stringent performance testing of the mobile router, including the interaction of routing and the transport-level protocol. In addition, Cisco Systems developed the mobile router for both commercial and Government markets. The code has become part of the Cisco Systems Internetworking Operating System (IOS) as of release 12.2 (4) T--which will make this capability available to the community at large. The mobile router is software code that resides in a network router and enables entire networks to roam while maintaining connectivity to the Internet. This router code is pertinent to a myriad of applications for both Government and commercial sectors, including the "wireless battlefield." NASA and the Department of Defense will utilize this technology for near-planetary observation and sensing spacecraft. It is also a key enabling technology for aviation-based information applications. Mobile routing will make it possible for information such as weather, air traffic control, voice, and video to be transmitted to aircraft using Internet-based protocols. This technology shows great promise in reducing congested airways and mitigating aviation disasters due to bad weather. The mobile router can also be incorporated into emergency vehicles (such as ambulances and life-flight aircraft) to provide real-time connectivity back to the hospital and health-care experts, enabling the timely application of emergency care. Commercial applications include entertainment services, Internet protocol (IP) telephone, and Internet connectivity for cruise ships, commercial shipping, tour buses, aircraft, and eventually cars. A mobile router, which is based on mobile IP, allows hosts (mobile nodes) to seamlessly "roam" among various IP subnetworks. This is essential in many wireless networks. A mobile router, unlike a mobile IP node, allows entire networks to roam. Hence, a device connected to the mobile router does not need to be a mobile node because the mobile router provides the roaming capabilities. There are three basic elements in the mobile IP: the home agent, the foreign agent, and the mobile node. The home agent is a router on a mobile node's home network that tunnels datagrams for delivery to the mobile node when it is away from home. The foreign agent is a router on a remote network that provides routing services to a registered mobile node. The mobile node is a host or router that changes its point of attachment from one network or subnetwork to another. In mobile routing, virtual communications are maintained by the home agent, which forwards all packets for the mobile networks to the foreign agent. The foreign agent passes the packets to the mobile router, which then forwards the packets to the devices on its networks. As the mobile router moves, it will register with its home agent on its whereabouts via the foreign agent to assure continuous connectivity.

Ivancic, William D.↗
NASA NTRS2006

CCSDS Time-Critical Onboard Networking Service

The Consultative Committee for Space Data Systems (CCSDS) is developing recommendations for communication services onboard spacecraft. Today many different communication buses are used on spacecraft requiring software with the same basic functionality to be rewritten for each type of bus. This impacts on the application software resulting in custom software for almost every new mission. The Spacecraft Onboard Interface Services (SOIS) working group aims to provide a consistent interface to various onboard buses and sub-networks, enabling a common interface to the application software. The eventual goal is reusable software that can be easily ported to new missions and run on a range of onboard buses without substantial modification. The system engineer will then be able to select a bus based on its performance, power, etc and be confident that a particular choice of bus will not place excessive demands on software development. This paper describes the SOIS Intra-Networking Service which is designed to enable data transfer and multiplexing of a variety of internetworking protocols with a range of quality of service support, over underlying heterogeneous data links. The Intra-network service interface provides users with a common Quality of Service interface when transporting data across a variety of underlying data links. Supported Quality of Service (QoS) elements include: Priority, Resource Reservation and Retry/Redundancy. These three QoS elements combine and map into four TCONS services for onboard data communications: Best Effort, Assured, Reserved, and Guaranteed. Data to be transported is passed to the Intra-network service with a requested QoS. The requested QoS includes the type of service, priority and where appropriate, a channel identifier. The data is de-multiplexed, prioritized, and the required resources for transport are allocated. The data is then passed to the appropriate data link for transfer across the bus. The SOIS supported data links may inherently provide the quality of service support requested by the intra-network layer. In the case where the data link does not have the required level of support, the missing functionality is added by SOIS. As a result of this architecture, re-usable software applications can be designed and used across missions thereby promoting common mission operations. In addition, the protocol multiplexing function enables the blending of multiple onboard networks. This paper starts by giving an overview of the SOIS architecture in section 11, illustrating where the TCONS services fit into the overall architecture. It then describes the quality of service approach adopted, in section III. The prototyping efforts that have been going on are introduced in section JY. Finally, in section V the current status of the CCSDS recommendations is summarized.

Parkes, Steve↗
NASA NTRS1990

Documentation for the token ring network simulation system

A manual is presented which describes the language features of the Token Ring Network Simulation System. The simulation system is a powerful simulation tool for token ring networks which allows the specification of various Medium Access Control (MAC) layer protocols as well as the specification of various features of upper layer ISO protocols. In addition to these features, it also allows the user to specify message and station classes virtually to any degree of detail desired. The choice of a language instead of an interactive system to specify network parameters was dictated by both flexibility and time considerations. The language was developed specifically for the simulation system, and is very simple. It is also user friendly in that language elements which do not apply to the case at hand are ignored rather than treated as errors.

Peden, Jeffery H.↗
NASA NTRS2001

Survey of Header Compression Techniques

This report provides a summary of several different header compression techniques. The different techniques included are: (1) Van Jacobson's header compression (RFC 1144); (2) SCPS (Space Communications Protocol Standards) header compression (SCPS-TP, SCPS-NP); (3) Robust header compression (ROHC); and (4) The header compression techniques in RFC2507 and RFC2508. The methodology for compression and error correction for these schemes are described in the remainder of this document. All of the header compression schemes support compression over simplex links, provided that the end receiver has some means of sending data back to the sender. However, if that return path does not exist, then neither Van Jacobson's nor SCPS can be used, since both rely on TCP (Transmission Control Protocol). In addition, under link conditions of low delay and low error, all of the schemes perform as expected. However, based on the methodology of the schemes, each scheme is likely to behave differently as conditions degrade. Van Jacobson's header compression relies heavily on the TCP retransmission timer and would suffer an increase in loss propagation should the link possess a high delay and/or bit error rate (BER). The SCPS header compression scheme protects against high delay environments by avoiding delta encoding between packets. Thus, loss propagation is avoided. However, SCPS is still affected by an increased BER (bit-error-rate) since the lack of delta encoding results in larger header sizes. Next, the schemes found in RFC2507 and RFC2508 perform well for non-TCP connections in poor conditions. RFC2507 performance with TCP connections is improved by various techniques over Van Jacobson's, but still suffers a performance hit with poor link properties. Also, RFC2507 offers the ability to send TCP data without delta encoding, similar to what SCPS offers. ROHC is similar to the previous two schemes, but adds additional CRCs (cyclic redundancy check) into headers and improves compression schemes which provide better tolerances in conditions with a high BER.

Ishac, Joseph↗
NASA NTRS1988

Early wrong-way response occurs in orthogravitropism of maize roots treated with lithium

Application of lithium ions to tips of roots of Zea mays L. cv. Silver Queen shifts the direction of initial orthogravitropic curvature from downward to upward. The production of this putatively incidental perturbation of orthogravitropic bending kinetics by a pharmacological agent might provide insight into both ortho- and plagiogravitropism. Additionally, the protocol of the experiments bears on recent claims that mucilage external to the root cap plays an essential role in gravitropism. External mucilage was removed before roots were stimulated, yet they reached about 50 degrees gravitropic curvature in an hour.

Non-NASA Center↗
NASA NTRS2007

Zero-Gravity Locomotion Simulators: New Ground-Based Analogs for Microgravity Exercise Simulation

Maintaining health and fitness in crewmembers during space missions is essential for preserving performance for mission-critical tasks. NASA's Exercise Countermeasures Project (ECP) provides space exploration exercise hardware and monitoring requirements that lead to devices that are reliable, meet medical, vehicle, and habitat constraints, and use minimal vehicle and crew resources. ECP will also develop and validate efficient exercise prescriptions that minimize daily time needed for completion of exercise yet maximize performance for mission activities. In meeting these mission goals, NASA Glenn Research Center (Cleveland, OH, USA), in collaboration with the Cleveland Clinic (Cleveland, Ohio, USA), has developed a suite of zero-gravity locomotion simulators and associated technologies to address the need for ground-based test analog capability for simulating in-flight (microgravity) and surface (partial-gravity) exercise to advance the health and safety of astronaut crews and the next generation of space explorers. Various research areas can be explored. These include improving crew comfort during exercise, and understanding joint kinematics and muscle activation pattern differences relative to external loading mechanisms. In addition, exercise protocol and hardware optimization can be investigated, along with characterizing system dynamic response and the physiological demand associated with advanced exercise device concepts and performance of critical mission tasks for Exploration class missions. Three zero-gravity locomotion simulators are currently in use and the research focus for each will be presented. All of the devices are based on a supine subject suspension system, which simulates a reduced gravity environment by completely or partially offloading the weight of the exercising test subject s body. A platform for mounting treadmill is positioned perpendicularly to the test subject. The Cleveland Clinic Zero-g Locomotion Simulator (ZLS) utilizes a pneumatic subject load device to apply a near constant gravity-replacement load to the test subject during exercise, and is currently used in conjunction with the General Clinical Research Center for evaluating exercise protocols using a bedrest analog. The enhanced ZLS (eZLS) at NASA Glenn Research Center features an offloaded treadmill that floats on a thin film of air and interfaces to a force reaction frame via variably-compliant isolators, or vibration isolation system. The isolators can be configured to simulate compliant interfaces to the vehicle, which affects mechanical loading to crewmembers during exercise, and has been used to validate system dynamic models for new countermeasures equipment designs, such as the second International Space Station treadmill slated for use in 2010. In the eZLS, the test subject and exercise device can be pitched at the appropriate angle for partial gravity simulations, such as lunar gravity (1/6th earth gravity). On both the eZLS and the NASA-Johnson Space Center standalone ZLS installed at the University of Texas Medical Branch in Galveston, Texas, USA, the subject's body weight relative to the treadmill is controlled via a linear motor subject load device (LM-SLD). The LM-SLD employs a force-feedback closed-loop control system to provide a relatively constant force to the test subject during locomotion, and is set and verified for subject safety prior to each session. Locomotion data were collected during parabolic flight and on the eZLS. The purpose was to determine the similarities and differences between locomotion in actual and simulated microgravity. Subjects attained greater amounts of hip flexion during walking and running during parabolic flight. During running, subjects had greater hip range of motion. Trunk motion was significantly less on the eZLS than during parabolic flight. Peak impact forces, loading rate, and impulse were greater on the eZLS than during parabolic while walking with a low external load (EL) and rning with a high EL. Activation timing differences existed between locations in all muscles except for the rectus femoris. The tibialis anterior and gluteus maximus were active for longer durations on the eZLS than in parabolic flight during walking. Ground reaction forces were greater with the LM-SLD than with bungees during eZLS locomotion. While the eZLS serves as a ground-based analog, researchers should be aware that subtle, but measurable, differences in kinematics and leg musculature activities exist between the environments. Aside from space applications, zero-gravity locomotion simulators may help medical researchers in the future with development of rehabilitative or therapeutic protocols for injured or ill patients. Zero-gravity locomotion simulators may be used as a ground-based test bed to support future missions for space exploration, and eventually may be used to simulate planetary locomotion in partial gravity environments, including the Moon and Mars. Figure: Zero-gravity Locomotion Simulator at the Cleveland Clinic, Cleveland, Ohio, USA

Perusek, Gail P.↗
NASA NTRSDate not supplied

Validation of Decompression Sickness Risk Mitigation Protocols for Planetary Spaceflight Missions

BACKGROUND: Apollo missions used a 100% O2 cabin atmosphere which effectively eliminated the risk of decompression sickness (DCS) during extravehicular activity (EVA) on the moon. NASA’s future missions to the moon and Mars are expected to use nitrox gas mixtures of up to 34% O2, 66% N2, which will reduce flammability risk compared with Apollo, but will necessitate Oxygen prebreathe prior to EVA to reduce DCS risk to acceptable levels. Prebreathe protocols used on the space shuttle and International Space Station are validated for microgravity EVAs, but the significantly increased risk of DCS during equivalent ambulatory EVAs make these protocols inapplicable to planetary EVA. An “exploration atmosphere” of 56.5 kPa (8.2 psia), 34% O2, 66% N2 has been recommended by NASA as a compromise that balances prebreathe duration, hypoxia, and flammability risk, assuming a 29.6 kPa (4.3 psi) spacesuit. However, this atmosphere may not be used for vehicles that do not support frequent EVA, and with commercial providers and international providers expected to provide landers, pressurized rovers, habitats, and spacesuits, different combinations of vehicle and spacesuit atmospheres are possible and will each require validated prebreathe protocols. OVERVIEW: Key components of a multi-year strategic roadmap include: 1) Establish hypobaric chamber facility capable of supporting 8-person EVA prebreathe validation tests at saturation atmospheres up to 36% O2; 2) validate an EVA physical workload simulation for use during prebreathe validation testing; 3) validate the recommended “exploration atmosphere” prebreathe protocol; 4) validate prebreathe protocols for additional atmospheric combinations that bound the most likely potential operating ranges of future vehicles and spacesuits; and 5) update DCS risk estimation models based on results of prebreathe validation studies. DISCUSSION: Details and data from completion of the first two steps of the strategic roadmap will be presented; the third step is currently underway, with pilot results provided in a companion presentation. Steps four and five will require a multi-year series of chamber tests; collaborations are being pursued.

Andrew F. J. Abercromby↗