Engineering PapersSearch

SEARCH · Engineering Papers

Results for “network telemetry”

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 37 records · Page 2

Thomas Leps Internship Abstract

An optical navigation system is being flown as the backup system to the primary Deep Space Network telemetry for navigation and guidance purposes on Orion. This is required to ensure Orion can recover from a loss of communication, which would simultaneously cause a loss of DSN telemetry. Images taken of the Moon and Earth are used to give range and position information to the navigation computer for trajectory calculations and maneuver execution. To get telemetry data from these images, the size and location of the moon need to be calculated with high accuracy and precision. The reentry envelope for the Orion EM-1 mission requires the centroid and radius of the moon images to be determined within 1/3 of a pixel 3 sigma. In order to ensure this accuracy and precision can be attained, I was tasked with building precise dot grid images for camera calibration as well as building a hardware in the loop test stand for flight software and hardware proofing. To calibrate the Op-Nav camera a dot grid is imaged with the camera, the error between the image dot location and the actual dot location can be used to build a distortion map of the camera and lens system so that images can be fixed to display truth locations. To build the dot grid images I used the Electro Optics Lab optical bench Bright Object Simulator System, and gimbal. The gimbal was slewed to a series of elevations and azimuths. An image of the collimated single point light source was then taken at each position. After a series of 99 images were taken at different locations the single light spots were extracted from each image and added to a composite image containing all 99 points. During the development of these grids it was noticed that an intermittent error in the artificial "star" locations occurred. Prior to the summer this error was attributed to the gimbal having glitches in it's pointing direction and was going to be replaced, however after further examining the issue I determined it to be a software issue. I have since narrowed the likely source of the error down to a Software Development Kit released by the camera supplier PixeLink. I have since developed a workaround in order to build star grids for calibration until the software bug can be isolated and fixed. I was also tasked with building a Hardware in the Loop test stand in order to test the full Op-Nav system. A 4k screen displays simulated Lunar and Terrestrial images from a possible Orion trajectory. These images are then projected through a collimator and then captured with an Op-Nav camera controlled by an Intel NUC computer running flight software. The flight software then analyzes the images to determine attitude and position, this data is then reconstructed into a trajectory and matched to the simulated trajectory in order to determine the accuracy of the attitude and position estimates. In order for the system to work it needs to be precisely and accurately aligned. I developed an alignment procedure that allows the screen, collimator and camera to be squared, centered and collinear with each other within a micron spatially and 5 arcseconds in rotation. I also designed a rigid mount for the screen that was machined on site in Building 10 by another intern. While I was working in the EOL we received a $500k Orion startracker for alignment procedure testing. Due to my prior experience in electronics development, as an ancillary duty, I was tasked with building the cables required to operate and power the startracker. If any errors are made building these cables the startracker would be destroyed, I was honored that the director of the lab entrusted such a critical component with me. This internship has cemented my view on public space exploration. I always preferred public sector to privatization because, as a scientist, the most interesting aspects of space for me are not necessarily the most profitable. I was concerned that the public sector was faltering however, and that in order to improve human space exploration I would be forced into private sector. I now know that, at least at JSC, human spaceflight is still progressing, and exciting work is still being done. I am now actively seeking employment at JSC after I complete my Ph.D and have met with my branch chiefs and mentor to discuss transitioning to a grad Co-op position.

Leps, Thomas

Python & Qt, Powerful Tools for Technical Computing

The objective of this presentation is to give a brief overview of Python computer language and Qt for Python which provides an interface to Python for building graphical applications. The Qt language provides a method for rapid programming of Graphical User Interfaces (GUIs) that are highly scalable, robust and platform independent. Both Python and Qt provide a powerful set of tools for Dynamic Analysis which are based on Open-Source software. Many problems and calculations in Structural Dynamics such as Power Spectral Density, Shock Response Spectrum and Vibration Response Spectrum can be easily calculated using these tools. The advantage of using Open-Source software is the ability to create custom graphical user interfaces similar to Matlab without the expense of software licensing and the ability to customize the software to an organization's specific needs. Also, another advantage is the ability to know which algorithms are being used by the GUI, know the numerical limitations and scale to large size data sets. I will end the presentation by demonstrating a Structural Dynamics GUI I created that was designed primarily to interactively analyze Post Flight high speed data provided by the ground station telemetry networks.

Grillo, Vincent

Telemetry, tracking, and command consolidation in the Deep Space Network

Currently, in NASA's Deep Space Network (DSN), telemetry, tracking, and command (TT&C) functions are distributed between multiple subsystem computers. Control design of these subsystems did not consider the interaction necessary between the functions, which create opportunities for loss of data. Also, the current controller design can force the use of equipment that is not needed for the task at hand, to the detriment of others. As part of the Network Simplification Project (NSP), the TTC implementation has been re-examined, New telemetry and commanding equipment is being built, and the control of the TT&C functions is being consolidated into two controllers, Uplink and Downlink. The new equipment uses commercial components, as opposed to the custom built equipment it is replacing, which improves reliability and simplifies maintenance.

tracking

Table-driven configuration and formatting of telemetry data in the Deep Space Network

With a restructured software architecture for telemetry system control and data processing, the NASA/Deep Space Network (DSN) has substantially improved its ability to accommodate a wide variety of spacecraft in an era of 'better, faster, cheaper'. In the new architecture, the permanent software implements all capabilities needed by any system user, and text tables specify how these capabilities are to be used for each spacecraft. Most changes can now be made rapidly, outside of the traditional software development cycle. The system can be updated to support a new spacecraft through table changes rather than software changes, reducing the implementation, test, and delivery cycle for such a change from three months to three weeks. The mechanical separation of the text table files from the program software, with tables only loaded into memory when that mission is being supported, dramatically reduces the level of regression testing required. The format of each table is a different compromise between ease of human interpretation, efficiency of computer interpretation, and flexibility.

Manning, Evan

The Venus Balloon Project telemetry processing

The peculiarities of the Venus Balloon telemetry system required the development of a new methodology for the telemetry processing, since the capabilities of the Deep Space Network (DSN) telemetry system do not include burst processing of short frames with two different bit rates and first bit acquisition. A software package was produced for the non-real time detection, demodulation, and decoding of the telemetry streams obtained from an open loop recording utilizing the DSN spectrum processing subsystem-radio science (DSP-RS). A general description of the resulting software package (DMO-5539-SP) and its adaptability to the real mission's variations is contained.

Urech, J. M.

Voyager telecommunications - The broadcast from Jupiter

The means by which the data collected by the Voyager 1 mission to Jupiter were returned to earth are presented. Radio links between the earth and the spacecraft are used for the transmission of both imaging and nonimaging telemetry from the spacecraft and commands from the earth and for radiometric observations of the spacecraft and its environment. Features which have lead to vast improvements in the capability of the Voyager telecommunications system over that of previous space probes include the use of X-band rather than S-band telemetry, a dual power X-band traveling wave tube amplifier, a 3.7 m spacecraft antenna and a single channel telemetry system with concatenated coding. Communications equipment at the three ground complexes of the Deep Space Network for telemetry reception includes 64 m steerable antennas, cryogenic maser preamplifiers and a phase-lock loop receiver. Voyager 1 has met or exceeded all of its telecommunications requirements, providing a 98% data return and a total of 2 x 10 to the 11th data bits during the Jupiter encounter.

Edelson, R. E.

Variability in Ocean Color Associated with Phytoplankton and Terrigenous Matter: Time Series Measurements and Algorithm Development at the FRONT Site on the New England Continental Shelf

Fronts in the coastal ocean describe areas of strong horizontal gradients in both physical and biological properties associated with tidal mixing and freshwater estuarine output (e.g. Simpson, 1981 and O Donnell, 1993). Related gradients in optically important constituents mean that fronts can be observed from space as changes in ocean color as well as sea surface temperature (e.g., Dupouy et al., 1986). This research program is designed to determine which processes and optically important constituents must be considered to explain ocean color variations associated with coastal fronts on the New England continental shelf, in particular the National Ocean Partnership Program (NOPP) Front Resolving Observational Network with Telemetry (FRONT) site. This site is located at the mouth of Long Island sound and was selected after the analysis of 12 years of AVHRR data showed the region to be an area of strong frontal activity (Ullman and Cornillon, 1999). FRONT consists of a network of modem nodes that link bottom mounted Acoustic Doppler Current Profilers (ADCPs) and profiling arrays. At the center of the network is the Autonomous Vertically Profiling Plankton Observatory (AVPPO) (Thwaites et al. 1998). The AVPPO consists of buoyant sampling vehicle and a trawl-resistant bottom-mounted enclosure, which holds a winch, the vehicle (when not sampling), batteries, and controller. Three sampling systems are present on the vehicle, a video plankton recorder, a CTD with accessory sensors, and a suite of bio-optical sensors including Satlantic OCI-200 and OCR-200 spectral radiometers and a WetLabs ac-9 dual path absorption and attenuation meter. At preprogrammed times the vehicle is released, floats to the surface, and is then winched back into the enclosure with power and data connection maintained through the winch cable. Communication to shore is possible through a bottom cable and nearby surface telemetry buoy, equipped with a mobile modem, giving the capability for near-real time data transmission and interactive sampling control.

Morrison, John R.

Striped Mullet Migration Patterns in the Indian River Lagoon: A Network Analysis Approach to Spatial Fisheries Management

Striped mullet (Mugil cephalus) are numerically abundant forage fish, highly valuable as prey and commercially valuable to humans. From September to December, mullet in the Indian River Lagoon (IRL), Florida undergo an annual migration from inshore foraging habitats to oceanic spawning sites. However, their migratory pathways, in particular their intra-estuarine movement pathways, remain unknown. To address this knowledge gap, we utilized passive acoustic telemetry to assess the movement patterns of M. cephalus within the IRL. Thirty-two fish were tagged, generating usable tracks from 18 individuals. The mean (±s.d.) time that fish were detected in the array was ~38 ± 90 days, with the longest at 444 days. We also document the first evidence of skipped spawning in M. cephalus inhabiting waters of the southeastern United States. These data suggest impoundments around the Merritt Island National Wildlife Refuge appear to serve as important refugia for striped mullet while the Banana and Indian Rivers act as corridors during their inshore migratory movements. Through spatial fisheries management, high value habitat and connective elements utilized by mullet and other vital forage fish may be identified, to benefit both natural and human dynamics in estuarine systems.

Acoustic telemetry

Memory Network For Distributed Data Processors

Universal Memory Network (UMN) is modular, digital data-communication system enabling computers with differing bus architectures to share 32-bit-wide data between locations up to 3 km apart with less than one millisecond of latency. Makes it possible to design sophisticated real-time and near-real-time data-processing systems without data-transfer "bottlenecks". This enterprise network permits transmission of volume of data equivalent to an encyclopedia each second. Facilities benefiting from Universal Memory Network include telemetry stations, simulation facilities, power-plants, and large laboratories or any facility sharing very large volumes of data. Main hub of UMN is reflection center including smaller hubs called Shared Memory Interfaces.

Bolen, David

Telemetry in bundles: delay-tolerant networking for delay-challenged applications

This paper presents an overview of DTN concepts, including bundles and the Bundling overlay protocol. One possible scenario for the application of DTN to a telemetry return problem is described, and there is a brief discussion of the current state of DTN technology development.

delay-tolerant networking bundling interplanetary

Embedded parallel processing based ground control systems for small satellite telemetry

The use of networked terminals which utilize embedded processing techniques results in totally integrated, flexible, high speed, reliable, and scalable systems suitable for telemetry and data processing applications such as mission operations centers (MOC). Synergies of these terminals, coupled with the capability of terminal to receive incoming data, allow the viewing of any defined display by any terminal from the start of data acquisition. There is no single point of failure (other than with network input) such as exists with configurations where all input data goes through a single front end processor and then to a serial string of workstations. Missions dedicated to NASA's ozone measurements program utilize the methodologies which are discussed, and result in a multimission configuration of low cost, scalable hardware and software which can be run by one flight operations team with low risk.

Forman, Michael L.

The performance of VLA as a telemetry receiver for Voyager planetary encounters

The Very Large Array (VLA) was proposed for use as a supplement to the Deep Space Network (DSN) for telemetry reception at Voyager 2 Uranus and Neptune encounters. The main problem with the use of VLA for telemetry is that it is not capable of producing a continuous stream of data. Gaps of one millisecond follow every 51 milliseconds of data. The effect of these millisecond gaps on coded telemetry is investigated. An upgapped system of the same aperture as the VLA would be capable of handling data rates of 38.4 kbps at Uranus encounter and 19.2 kbps at Neptune encounter. It is shown that VLA with (7, 1/2) convolutional coding (the baseline coding scheme for Voyager) will support a data rate of 10.8 kbps but not 19.2 kbps at both Uranus and Neptune. It is also shown that by implementing Voyager's concatenated Reed-Solomon/convolutional coding capability, data rates of 38.4 kbps and 19.2 kbps would be achievable at Uranus and Neptune respectively. Concatenation also offers a factor of 2 improvement in overall throughput.

Deutsch, L. J.

Telemetry Simulation Assembly Implementation in the DSN

The telemetry simulation was implemented as part of the MARK IV network implementation project. The telemetry simulation assembly (TSA) is replacing the Simulation Conversion Assembly (SCA) throughout the DSN. The development of the TSA is discussed, and the design is described to the block diagram level.

Alberda, M. E.