Search NASA⌕ Search

SEARCH · Search NASA

Results for “Receive and distribute ground commands”

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.

Nodes

Nodes is a technology demonstration mission that is scheduled for launch to the International SpaceStation no earlier than Nov.19, 2015. The two Nodes satellites will be deployed from the Station in early 2016 todemonstrate new network capabilities critical to the operation of swarms of spacecraft. They will demonstrate the ability ofmulti spacecraft swarms to receive and distribute ground commands, exchange information periodically, andautonomously configure the network by determining which spacecraft should communicate with the ground each day ofthe mission.

Nodes↗

Performance evaluation of Platform Data ManagementSystem under various degrees of protocol implementation

The Platform Data Management System (DMS) collects Housekeeping (H/K), Payload (P/L) Engineering, and Payload Science data from various subsystems and payloads on the platform for transmission to the ground through the downlink via TDRSS. The DMS also distributes command data received from the ground to various subsystems and payloads. In addition, DMS distributes timing and safemode data. The function of collection and distribution of various types of data is performed by the Command and Data Handling (C&DH) subsystem of DMS. The C&DH subsystem uses for this purpose a number of data buses namely, Housekeeping, Payload Engineering, Payload Science, and Time and Safemode buses. Out of these buses, the H/K, P/L Engineering, and P/L Science buses are planned to be implemented by using MIL-STD 1553 bus. Most of the period covered was spent in developing a queue theoretic model of the 1553 Bus as used in the DMS. The aim is to use this model to test the performance and suitability of the 1553 Bus to the DMS under a number of alternative design scenarios.

Arozullah, Mohammed↗

Ground Support for the Space-Based Range Flight Demonstration 2

The primary objective of the NASA Space-Based Range Demonstration and Certification program was to develop and demonstrate space-based range capabilities. The Flight Demonstration 2 flights at NASA Dryden Flight Research Center were conducted to support Range Safety (commanding and position reporting) and high-rate (5 Mbps) Range User (video and data) requirements. Required ground support infrastructure included a flight termination system computer, the ground-data distribution network to send range safety commands and receive range safety and range user telemetry data and video, and the ground processing systems at the Dryden Mission Control Center to process range safety and range user telemetry data and video.

Burkes, Darryl A.↗

Support for User Interfaces for Distributed Systems

An extensible Java(TradeMark) software framework supports the construction and operation of graphical user interfaces (GUIs) for distributed computing systems typified by ground control systems that send commands to, and receive telemetric data from, spacecraft. Heretofore, such GUIs have been custom built for each new system at considerable expense. In contrast, the present framework affords generic capabilities that can be shared by different distributed systems. Dynamic class loading, reflection, and other run-time capabilities of the Java language and JavaBeans component architecture enable the creation of a GUI for each new distributed computing system with a minimum of custom effort. By use of this framework, GUI components in control panels and menus can send commands to a particular distributed system with a minimum of system-specific code. The framework receives, decodes, processes, and displays telemetry data; custom telemetry data handling can be added for a particular system. The framework supports saving and later restoration of users configurations of control panels and telemetry displays with a minimum of effort in writing system-specific code. GUIs constructed within this framework can be deployed in any operating system with a Java run-time environment, without recompilation or code changes.

Eychaner, Glenn↗

Command and Control System Automated Testing

The Kennedy Space Center (KSC) has developed its own Command and Control System for the launch of the Space Launch System (SLS) and Orion capsule. The Command and Control System (CCS) is used by console engineers for the launch and system checkout of aerospace vehicles. The CCS allows console engineers to read data from the flight hardware on the launch pad and from the ground control systems and allows console engineers to issue commands, like opening a valve, to the flight hardware and ground control systems. The CCS needs to interact with thousands of devices and hardware controllers for the spacecraft and ground systems, receive data from these devices, distribute the data to console engineers in real-time, and allow console engineers to issue commands to manipulate hardware on the launch pad. The system needs to be robust, fault tolerant, responsive, and fast. In order to keep up with the pace of development of the CCS, a Test Automation System (TAS) is needed to validate the integrity of the system as a whole along with its individual components. Automated tests allow for faster development time, since tests can be ran through a Continuous Integration system and allow developers to check their code faster. Currently, the different modules, classes, and functions that make up the CCS are tested at the unit level, and the system level, with all the modules working together. My project was to implement a system for the data protocol layer of the Command Control System to be tested as a complete functional unit, with all of its classes and functions working together, but independent of the other modules of the CCS.

Automated TestingTest Automation↗

Programmable Ultra-Lightweight System Adaptable Radio

The programmable ultra-lightweight system adaptable radio (PULSAR) is a NASA Marshall Space Flight Center transceiver designed for the CubeSat market, but has the potential for other markets. The PULSAR project aims to reduce size, weight, and power while increasing telemetry data rate. The current version of the PULSAR has a mass of 2.2 kg and a footprint of 10.8 cm2. The height depends on the specific configuration. The PULSAR S-Band Communications Subsystem is an S- and X-band transponder system comprised of a receiver/detector (receiver) element, a transmitter element(s), and related power distribution, command, control, and telemetry element for operation and information interfaces. It is capable of receiving commands, encoding and transmitting telemetry, as well as providing tracking data in a manner compatible with Earthbased ground stations, near Earth network, and deep space network station resources. The software-defined radio's (SDR's) data format characteristics can be defined and reconfigured during spaceflight or prior to launch. The PULSAR team continues to evolve the SDR to improve the performance and form factor to meet the requirements that the CubeSat market space requires. One of the unique features is that the actual radio design can change (somewhat), but not require any hardware modifications due to the use of field programmable gate arrays.

Werkheiser, Arthur↗

Dynamic Assurance of Autonomous Systems through Ground Control Software

Assurance cases are being increasingly acknowledged as a way to build trust in complex systems with autonomous capabilities [1]. An assurance case is a comprehensive, defensible, and valid justification that a system will function as intended for the specific mission and operating environment. Such justifications for systems with autonomous capabilities are often based on various probabilistic quantifications [2]. Due to the dynamic nature of the environmental conditions in which these systems operate, as well as the changing nature of the autonomous systems themselves, these probabilistic quantifications cannot be simply estimated once during design time. Rather, they need to be continually evaluated during systems operations to ensure that the assurance case justifications are valid. We refer to the assurance case that combines both the static and dynamic elements as a Dynamic Assurance Case (DAC). Such complex systems with autonomous capabilities are often deployed with a Ground Control Software (GCS) component to enable remote operation. Whether the system is composed of a single unit or a fleet of units, deployed distributed or in remote environments, GCS acts as a window into the behavior of the deployed system. It receives telemetry from the system, issues commands to the system and provides various functionalities to visualize the system performance. We propose a dynamic assurance framework where the GCS acts as a relay between the autonomous system and its DAC. GCS can be used to measure both unit-specific as well as system-wide probabilistic quantifications using the incoming telemetry. We embed these quantifications throughout the DAC as variables that can be updated by external sources. We use the GCS to periodically update these variables, which allows us to continually evaluate the formally defined assurance case justifications. We demonstrate our dynamic assurance framework in the NASA Ames project Troupe1 that aims at developing a fleet of rovers capable of au- tonomously mapping their environment. The rovers work cooperatively, each collecting data for different parts of the environment. Each rover runs an identical core Flight System (cFS) [4] application. Troupe1 uses OpenC3 Cosmos [5] as the ground system, and AdvoCATE [3] to capture the system DAC. We show how we can measure both rover-specific and system-wide quantifications in Cosmos using its Ruby scripting editor and pass them into the DAC modelled in AdvoCATE. Then, we show how these incoming variables can be embedded in different parts of the DAC and how effects of their updates can be observed

Irfan Sljivo↗

Distributed Spacecraft Autonomy - Development of Swarm Autonomy Capability and Scalability for Spacecraft

The Distributed Spacecraft Autonomy project is developing a suite of software tools that enable an operator to command and receive data from a swarm as a single entity, enable a swarm to autonomously coordinate its actions via distributed decision making and reactive closed-loop control, and model swarm behavior in the presence of anomalies or failures. Our use case is the mapping of the electron density of the ionosphere using radio tomography by coordinating the selection of appropriate GPS channels, and by recording Total Electron Count (TEC) measurements. DSA will be demonstrated onboard the NASA Ames Starling mission – a swarm of four small, LEO spacecraft, scheduled to launch in 2021. We will also perform a ground demonstration with simulated and hardware-in-the-loop elements, to validate the tools for controlling swarms of up to 100 assets. The capability to communicate autonomously between the swarm satellites is demonstrated via a sophisticated simulation architecture. Historical Plasmasphere TEC data obtained via dual-band Novatel GPS Receivers are utilized as a representative input dataset for the swarm. The representative TEC data and GPS satellite observability information is fed to the autonomous software package in place of a true real-time ground data collection process. The swarm satellites actively share status updates amongst one another and utilize multi-agent decision making to optimally identify regions of interest in the TEC distribution. The software, aware of the bandwidth limitations of the swarm satellites, prioritizes explorative measurements, which define the range of observability for the satellites, as well as exploitative measurements, which focus on maximizing the observance potential of regions with prolonged, elevated TEC density. The science of this study can ultimately be used to determine the dynamics and coupling of Earth’s magnetosphere, ionosphere, and atmosphere and their response to solar and terrestrial inputs. The findings can be applied to the imaging of critical, transient phenomena in the magnetosphere in later missions. Meanwhile, the swarm autonomy capabilities have far reaching potential in future satellite missions. As an experimental demonstration of the autonomous capabilities of the network, a message is first printed within a core Flight Executive (cFE) application. Two cFE applications that communicate with one another within the same core Flight System (cFS) are shown. Communication between mission applications on the internal cFE bus is extended to utilize Data Distribution Service (DDS) for vehicle-to-vehicle networking. The DDS middleware provides reliable delivery, routing, and topic subscription features over User Datagram Protocol (UDP). Leveraging Linux containerization, a networked set of satellite instances are generated by script to simulate swarm behavior. Swarm commanding and synchronization through the network is demonstrated under various topologies and data-loss conditions. Finally, autonomous swarm scalability from 2 satellites to 100 satellites is shown.

Distributed Autonomy↗

Distributed Spacecraft Autonomy (DSA): Development of Swarm Autonomy Capability and Scalability for Spacecraft

The Distributed Spacecraft Autonomy project is developing a suite of software tools that enable an operator to command and receive data from a swarm as a single entity, enable a swarm to autonomously coordinate its actions via distributed decision making and reactive closed-loop control, and model swarm behavior in the presence of anomalies or failures. Our use case is the mapping of the electron density of the ionosphere using radio tomography by coordinating the selection of appropriate GPS channels, and by recording Total Electron Count (TEC)measurements. DSA will be demonstrated on board the NASA Ames Starling mission a swarm of four small, LEO spacecraft, scheduled to launch in 2021. We will also perform a ground demonstration with simulated and hardware-in-the-loop elements, to validate the tools for controlling swarms of up to 100 assets.The capability to communicate autonomously between the swarm satellites is demonstrated via a sophisticated simulation architecture. Historical Plasma sphere TEC data obtained via dual-band Novatel GPS Receivers are utilized as a representative input data set for the swarm. The representative TEC data and GPS satellite observability information is fed to the autonomous software package in place of a true real-time ground data collection process. The swarm satellites actively share status updates amongst one another and utilize multi-agent decision making to optimally identify regions of interest in the TEC distribution. The software,aware of the bandwidth limitations of the swarm satellites, prioritizes explorative measurements,which define the range of observability for the satellites, as well as exploitative measurements,which focus on maximizing the observance potential of regions with prolonged, elevated TEC density. The science of this study can ultimately be used to determine the dynamics and coupling of Earth's magnetosphere, ionosphere, and atmosphere and their response to solar and terrestrial inputs. The findings can be applied to the imaging of critical, transient phenomena in the magnetosphere in later missions. Meanwhile, the swarm autonomy capabilities have far reaching potential in future satellite missions.As an experimental demonstration of the autonomous capabilities of the network, a message is first printed within a core Flight Executive (cFE) application. Two cFE applications that communicate with one another within the same core Flight System (cFS) are shown.Communication between mission applications on the internal cFE bus is extended to utilize Data Distribution Service (DDS) for vehicle-to-vehicle networking. The DDS middle ware provides reliable delivery, routing, and topic subscription features over User Data gram Protocol (UDP).Leveraging Linux containerization, a networked set of satellite instances are generated by script to simulate swarm behavior. Swarm commanding and synchronization through the network is demonstrated under various topologies and data-loss conditions. Finally, autonomous swarms calability from 2 satellites to 100 satellites is shown.

Fugate, Jason↗

Earth Science Technology Office (ESTO) New Observing Strategies (NOS) and NOS-Testbed (NOS-T)

With the advancement of space hardware technologies such as smaller spacecraft, component and instrument miniaturization and high performance space processors, and with the advancement of software technologies in artificial intelligence, big data analysis and autonomous decision making, Earth Science is looking at novel ways to observe phenomena that previously could not have been studied or would have been too expensive to study with traditional missions. In particular, the New Observing Strategies (NOS) component of the NASA Earth Science Technology Office (ESTO) Advanced Information Systems Technology (AIST) Program aims at leveraging these novel technologies as well as low cost and easy access to space to acquire multi-temporal or simultaneous multi-angular, multi-locations, multi-resolution and multi-spectral observations that will provide better multi-source measurements and will build a more dynamic and comprehensive picture of Earth Science phenomena that need to be studied and analyzed. For applications such as water resources management, air quality monitoring, biodiversity studies or disaster management, NOS will integrate the use of small instruments, small spacecraft, constellations of spacecraft and networks of sensors to design new missions that will provide the necessary measurements to improve future forecast and science modeling systems.Measurement acquisition will therefore be approached as a system of systems rather than on a mission basis, and a system of this complexity should not be expected to work without full integration and experimental characterization. Although most of the individual technologies enabling to link and coordinate multi-source observations are more or less mature, a few technologies need to be developed and all of them need to be integrated and tested as a system. In order for this validation to occur, the AIST Program is developing the NOS Testbed that includes 3 main goals:1.Validate novel NOS technologies, independently and as a system2.Demonstrate novel distributed operations concepts3.Socialize new Distributed Spacecraft Mission (DSM) and SensorWeb (SW) technologies and concepts to the science community by significantly retiring the risk of integrating these new technologies.The NOS Testbed will consist of multiple sensing nodes, simulated or actual, representing space, air and/or ground measurements, that are interconnected by a communications fabric (infrastructure that permits nodes to transmit and receive data between one another and interact with each other). Each node will be supported by hardware capabilities required to perform nodes monitoring and command & control, as well as intelligent "onboard" computing. The nodes will work together in a collaborative manner to demonstrate optimal science capabilities. The testbed will enable to validate technologies such as inter-node communication models, techniques and protocols; inter-node coordination; real-time data fusion and understanding; planning; sensor re-targeting; etc. Additionally, the testbed will have the capability to interact with various mission design tools, OSSEs and one or several forecast models. More details about the NOS Testbed will be presented at the confererence.

Earth Science missions; Advanced information Syste↗

Advancing Autonomy in Distributed Space Systems: Insights From on-Orbit Testing with the Starling 1.0 Mission

Autonomous decision-making is crucial for enhancing mission effectiveness in Distributed Space Systems (DSS), particularly in multi-spacecraft operations where communication constraints and mission complexity pose challenges. The Distributed Spacecraft Autonomy (DSA) team at NASA’s Ames Research Center is advancing autonomy in DSS through five key technical areas: distributed resource and task management, reactive operations, system modeling and simulation, human-swarm interaction, and ad hoc network communications. The DSA experiment onboard the Starling 1.0 Mission showcases collaborative resource allocation for multi-point science data collection with four small spacecraft. Autonomy in decision-making is highlighted as a crucial factor for multi-spacecraft missions, enabling spacecraft to operate independently, reducing reliance on ground control. This capability is particularly significant for future deep-space missions, where communication delays and limited data transmission capacity make traditional command and control approaches impractical. This demonstration focuses on a GPS Channel Selection Experiment, leveraging emergent capabilities like "shared sampling" and "simultaneous sampling" to optimize channel selection across the spacecraft swarm. The experiment aims to capture ionospheric phenomena such as the Equatorial Ionization Anomaly and Polar Patches. The DSA system's autonomous reconfiguration ability is showcased, emphasizing its adaptability to natural phenomena without significant integration efforts. The GPS Channel Selection Experiment utilizes a dual-band GPS receiver to estimate plasma density in the ionosphere. Explorative and exploitative channel selections are employed based on the nature of observed phenomena. The performance of DSA algorithms is evaluated in terms of optimal channel allocations and responsiveness to changes in observed features. The DSA Flight Software utilizes the Core Flight System (cFS) framework, ensuring compatibility with the Starling 1.0 flight mission software. DSA showcases results from RTI’s Connext DDS Micro communication middleware, enabling message routing over the Ad-Hoc Network of Starling 1.0. This paper provides a comprehensive overview of the DSA experiment's initial results, emphasizing the advancements in autonomy for Distributed Space Systems and the successful collaboration with the Starling 1.0 mission.

Caleb Ashmore Adams↗

Telescience Resource Kit Software Capabilities and Future Enhancements

The Telescience Resource Kit (TReK) is a suite of PC-based software applications that can be used to monitor and control a payload on board the International Space Station (ISS). This software provides a way for payload users to operate their payloads from their home sites. It can be used by an individual or a team of people. TReK provides both local ground support system services and an interface to utilize remote services provided by the Payload Operations Integration Center (POIC). by the POIC and to perform local data functions such as processing the data, storing it in local files, and forwarding it to other computer systems. TReK can also be used to build, send, and track payload commands. In addition to these features, work is in progress to add a new command management capability. This capability will provide a way to manage a multi- platform command environment that can include geographically distributed computers. This is intended to help those teams that need to manage a shared on-board resource such as a facility class payload. The environment can be configured such that one individual can manage all the command activities associated with that payload. This paper will provide a summary of existing TReK capabilities and a description of the new command management capability. For example, 7'ReK can be used to receive payload data distributed

Schneider, Michelle↗

Far UV camera/spectrograph

In March 1610, Galileo Galilei reported the first use of a telescope to view mountains and maria on the Moon. On April 21, 1972, the Apollo 16 commander pointed a somewhat more complex optical instrument at the Earth from the Moon and obtained several remarkable photographs showing atmospheric rather than surface features. The optical part of the far UV camera (aperture, 7.5 cm) was not much larger than Galileo's telescope. Like his, this instrument was also pointed at other celestial objects that Galileo viewed, including the Milky Way and Jupiter, and the Large Magellanic Cloud (LMC), which is not visible from Italy. More important, the far UV camera/spectrograph recorded light in the invisible band of wavelengths between 50 and 160 nm, approximately one-third the wavelength that can penetrate the atmosphere of the Earth to ground-based telescopes. As described in more detail in this section, these UV observations from the Moon allow study of the entire atmosphere of the Earth and the geocorona. The photographs show hydrogen and other gases in the solar wind and interplanetary media, and they provide new data on stars, nebulae, and galaxies much farther away. When used as a spectrograph, the instrument distributes the light it receives according to wavelength, and the resulting spectrum shows bright lines or gaps known to be characteristic of various gases, such as hydrogen (H), helium (He), oxygen (O), nitrogen (N), and neon (Ne). If a gas cloud is hot, the atoms are excited and the spectrum shows bright emission lines; if it is cool, the atoms absorb light, leaving gaps or absorption lines. The far UV camera is blind to ordinary visible light; for that reason, the photographs show very few of the stars mapped by ground-based telescopes. Only the very-high-temperature (blue) stars of spectral classes O, B, and possibly A (temperatures from 50000 ° down to 10000°K) are expected to be recorded. Image blackness or density on the negatives also depends on the brightness of the star, which astronomers measure in an inverted logarithmic scale of magnitudes. A star of 6 magnitudes (mag.) can barely be seen with the unaided eye. An 11-mag. star is 100 times fainter, and a 12-mag. star is 2.5 times fainter yet. The faintest star recorded by the far UV camera is at least 11 mag., which is called the limiting magnitude.

George R. Carruthers↗

2012 Ground Testing Highlights

As part of the Fundamental Aeronautics Program and a collaborative effort with Boeing, and Lockheed Martin this past year a series of sonic boom test were completed in the NASA Ames Unitary Plan Wind Tunnel (UPWT). One of the goals was to develop new test techniques and hardware for measuring sonic boom signatures in the transonic and supersonic regimes. Data for various model designs and configurations were collected and will be used to validate CFD predictions of sonic boom signatures. Reactivation of the NASA Ames Mitsubishi compressor system was completed this past year. The compressor is intended to replace and augment the existing UPWT Clark Compressor as the primary Make Up Air (MUA) source. The MUA system provides air and vacuum pumping capability to the Ames UPWT. It will improve productivity and reliability of the UPWT as a vital testing and research facility for the U.S. aerospace industry and NASA. Funding for this task was provided from the American Recovery Investment Act (ARRA). Installation and validation of a Noncontact Stress Monitoring System (NSMS) for the 3-stage compressor was completed at the 11-foot Transonic Wind Tunnel. The system, originally developed at AEDC, consists of 36 pairs of LED light sources with optic beam send and receive probes along a 1-per rev signal. The new system allows for continuous monitoring and recording of compressor blade bending and torsion stress during normal test operations. A very unusual test was completed in the 11 FT TWT to acquire aerodynamic and flow field data for the Crew Exploration Vehicle (CEV) Parachute Assembly System (CPAS) to validate CFD methods and tools. Surface pressure distribution measurements and velocity measurements in the wake of the command module back to the drogues parachute location were acquired. Testing methods included Particle Image Velocimetry (PIV), Pressure Sensitive Paint (PSP), Schlieren Infrared Imaging (IR) and boundary layer survey and skin friction.

Buchholz, Steven J.↗

NASA Operational Simulator for Small Satellites: Tools for Software Based Validation and Verification of Small Satellites

The NASA Operational Simulator for Small Satellites (NOS3) is a suite of tools to aid in areas such as software development, integration test (IT), mission operations training, verification and validation (VV), and software systems check-out. NOS3 provides a software development environment, a multi-target build system, an operator interface-ground station, dynamics and environment simulations, and software-based hardware models. NOS3 enables the development of flight software (FSW) early in the project life cycle, when access to hardware is typically not available. For small satellites there are extensive lead times on many of the commercial-off-the-shelf (COTS) components as well as limited funding for engineering test units (ETU). Considering the difficulty of providing a hardware test-bed to each developer tester, hardware models are modeled based upon characteristic data or manufacturers data sheets for each individual component. The fidelity of each hardware models is such that FSW executes unaware that physical hardware is not present. This allows binaries to be compiled for both the simulation environment, and the flight computer, without changing the FSW source code. For hardware models that provide data dependent on the environment, such as a GPS receiver or magnetometer, an open-source tool from NASA GSFC (42 Spacecraft Simulation) is used to provide the necessary data. The underlying infrastructure used to transfer messages between FSW and the hardware models can also be used to monitor, intercept, and inject messages, which has proven to be beneficial for VV of larger missions such as James Webb Space Telescope (JWST). As hardware is procured, drivers can be added to the environment to enable hardware-in-the-loop (HWIL) testing. When strict time synchronization is not vital, any number of combinations of hardware components and software-based models can be tested. The open-source operator interface used in NOS3 is COSMOS from Ball Aerospace. For testing, plug-ins are implemented in COSMOS to control the NOS3 simulations, while the command and telemetry tools available in COSMOS are used to communicate with FSW. NOS3 is actively being used for FSW development and component testing of the Simulation-to-Flight 1 (STF-1) CubeSat. As NOS3 matures, hardware models have been added for common CubeSat components such as Novatel GPS receivers, ClydeSpace electrical power systems and batteries, ISISpace antenna systems, etc. In the future, NASA IVV plans to distribute NOS3 to other CubeSat developers and release the suite to the open-source community.

Verification↗

AG Channel Measurement and Modeling Results for Over-Sea Conditions

This report describes results from flight tests conducted in an over-sea environment, for the purpose of characterizing the air-to-ground (AG) channel, for future unmanned aircraft system (UAS) communication system analysis and design. These results are for the first of a set of several flight tests conducted in different ground site (GS) environments. An ultimate aim of all these tests is the development of models for the AG channel that can be used in communication system evaluation. In this report we provide measured results for propagation path loss, root-mean square delay spread (RMS-DS), and the correlation coefficient of the primary received signal components on the four antennas (two antennas for C-band, two for L-band). For path loss, the curved-earth two-ray model provides a reasonable fit to the measured data, altered by several dB at the shortest link distances by aircraft antenna pattern effects. This two-ray model also accounts for the majority of measured RMS-DS results of a few tens of nanoseconds, except for the occasional intermittent reflections from surface objects. These intermittent reflections yield RMS-DS values up to several hundred nanoseconds. For portions of the flight path that were over a harbor area highly populated with boats, the channel was found to be more "continuously dispersive," with RMS-DS reaching approximately 250 ns. A separate model will be developed for this over-harbor setting. The correlation coefficient results are still undergoing analysis; preliminary observations are that correlation between signals on the same-band antennas is generally large (>0.6) for the C-band straight flight paths, whereas for the L-band signals and for the oval-shaped flight paths the correlation is generally small (below 0.4). Inter-band correlations are typically very small, and are well modeled as zero-mean Gaussian in distribution, with a standard deviation less than 0.2. Hence the over-sea channel effects in the two bands can be considered uncorrelated, which will allow for good diversity gains in dual-band systems. We describe initial modeling approaches for the over-sea channel; complete models for this and the over-harbor setting will appear in a subsequent report.

Aircraft Communications↗