Search NASA⌕ Search

SEARCH · Search NASA

Results for “Payload developer”

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 NTRS2020

Electromagnetic Compatibility Considerations for International Space Station Payload Developers

The International Space Station (ISS) is a laboratory for scientific research, innovative technology development, and global education. The ISS provides a number of facilities and platforms for payload developers and investigators to conduct biological, microgravity, and Earth and space observation science, as well as for performing technology development. Due to the unique nature of the ISS vehicle and its electrical power and data systems, achieving electromagnetic compatibility (EMC) with the vehicle requires special considerations by the payload developer. The ISS electromagnetic interference (EMI) requirements and test methods are based on MIL-STD-461, “Electromagnetic Emissions and Susceptibility Requirements for the Control of Electromagnetic Interference”, Revision C, and MIL-STD-462, “Electromagnetic Interference Characteristics, Measurement of,” respectively. The low source impedance of the test setup requires special considerations when designing or selecting EMI power filters and switched mode power supplies. Many filters, suited for later revisions of MIL-STD-461, will result in non-compliant designs. ISS electrical power system power quality requirements, imposed to protect the stability of the system, can also affect EMI filter design. The selection and use of commercial-off-the-shelf (COTS) equipment for ISS applications requires special considerations to meet both EMC and crew safety requirements. Furthermore, the ISS environment can provide unique immunity challenges; if the payload developer ignores these challenges, the result is a possible loss of science or impact to technology demonstration. The ISS provides a unique opportunity for the science and technology development community. However, in order to be successful, the payload developer must incorporate special EMC considerations, many of which will be presented.

McCollum, Matthew↗
NASA NTRS2007

Smart Payload Development for High Data Rate Instrument Systems

This slide presentation reviews the development of smart payloads instruments systems with high data rates. On-board computation has become a bottleneck for advanced science instrument and engineering capabilities. In order to improve the computation capability on board, smart payloads have been proposed. A smart payload is a Localized instrument, that can offload the flight processor of extensive computing cycles, simplify the interfaces, and minimize the dependency of the instrument on the flight system. This has been proposed for the Mars mission, Mars Atmospheric Trace Molecule Spectroscopy (MATMOS). The design of this system is discussed; the features of the Virtex-4, are discussed, and the technical approach is reviewed. The proposed Hybrid Field Programmable Gate Array (FPGA) technology has been shown to deliver breakthrough performance by tightly coupling hardware and software. Smart Payload designs for instruments such as MATMOS can meet science data return requirements with more competitive use of available on-board resources and can provide algorithm acceleration in hardware leading to implementation of better (more advanced) algorithms in on-board systems for improved science data return

Virtex-4↗
NASA NTRS2024

International Space Station Satellite Deployment: Jettison Policy and Best Practices for Satellite Payload Developers

The International Space Station (ISS) deploys dozens of small satellites into Low Earth Orbit (LEO) each year. This presentation and associated paper cover the ISS Jettison Policy requirements and review/approval process, as well as best practices for satellite Payload Developers who have satellites manifested for deployment from ISS. Specifically, topics will include ISS Jettison Policy requirements to limit generation of orbital debris, limit risk of collision with ISS, and limit risk of collision with ISS visiting vehicles. The paper will include details on the ISS Program jettison candidate analysis and approval process, timelines for data submittal to ISS Program, resources for small satellite developers, and design & analysis recommendations for small satellite developers to maximize their likelihood of successful deployment from ISS. New Station deploy capabilities and ways the ISS Program addresses and facilitates innovations in small satellite technology, including propulsion systems, deorbit devices, constellation development, and novel tech demos, will also be explored. The 2024 session topic that best fits this abstract is Orbital Debris, SSA & STM. The ISS Jettison Policy intends to quantify and control the risks of deploying and operating small satellites, not only to ensure the safety of the humans flying in space, but also to preserve the orbital environment for world space activities and enable the significant benefits brought by such utilization. The ISS Program is committed to working with smallsat providers to address their challenges and enable safe, accessible, innovative missions. The Policy has grown with the industry, with each deploy yielding hard-earned lessons learned that improve our process – not only for the next deploy campaign, but with applicability and adaptability for future applications in LEO and beyond.

Jettison Policy↗
NASA NTRS2002

Operational Limitations of the High Rate Frame Multiplexer (HRFM) Onboard the International Space Station(ISS)-and How These Limitations Affect Payload Developers (PDs) and International Partners (IPs)

The data system onboard the United States Operating Segment (USOS) of the ISS is currently used to capture, route, record and downlink high-rate science data from experiments inside the US Lab. Once NASDA's Japanese Experiment Module (JEM) and ESA's Attached Pressurized Module (APM) are launched - in the 2004 to 2005 timeframe - data from these facilities will also be routed to the ground using the USOS data system. A critical component of the USOS data system is the High Rate Frame Multiplexer (HRFM). The HRFM combines multiple data/video inputs and combines them into one data stream. This Ku-band data stream is then routed through the Tracking and Data Relay Satellite (TDRS) system to the ground. The Data Management Coordinator (DMC) - located at the Marshall Space Flight Center's Payload Operations Center (POC) - is responsible for commanding and controlling the HRFM. The HRFM can multiplex a maximum of eight digital data sources and four digital video sources. Thus far, this limitation has not been constraining to operations. However, once the JEM and APM are integrated, the HRFM limitations will become a major constraint to science operations onboard. The purpose of this paper is to characterize the limitations of the HRFM and to explain how these limitations can be successfully managed. With this information, Payload Developers and International Partners will be able to more effectively utilize the data systems onboard the ISS. Ultimately, more science data can be captured and downlinked to Flight Controllers and Scientists on the ground.

Mixson, Charles D.↗
NASA NTRS1990

Payloads development for European land mobile satellites: A technical and economical assessment

The European Space Agency (ESA) has defined two payloads for Mobile Communication; one payload is for pre-operational use, the European Land Mobile System (EMS), and one payload is for promoting the development of technologies for future mobile communication systems, the L-band Land Mobile Payload (LLM). A summary of the two payloads and a description of their capabilities is provided. Additionally, an economic assessment of the potential mobile communication market in Europe is provided.

Perrotta, G.↗
NASA NTRSDate not supplied

Rapid Spacecraft Payload Development: In-Orbit Demonstration of Flight Software Reuse, Scalability, and Dependability

As space mission design trends towards shared, multi-mission platforms and high-performance onboard computing architectures, the number of spacecraft launched into operation is also steadily rising. Through ridesharing, spacecraft miniaturization, and other cost-reduction measures, the barriers to space are lowering, resulting in compounded growth in the amount of flight software being deployed. To meet the needs of both the growing quantity and evolving nature of spacecraft, flight software design must accordingly adapt to support more efficient development, solutions to computational resource-sharing, and software reusability. This paper focuses on a software payload demonstrating several core technologies that improve the state-of-the-art in these identified areas. Launched into low-earth orbit in January 2022, our software payload was conceived, designed, and delivered in a span of merely two months. It was developed on top of the NASA core Flight System (cFS) framework and the Distributed Spacecraft Autonomy (DSA) Comm cFS application, which translates cFS software bus messages across a Data Distribution Service (DDS) network. The flight software, packaged in Linux container images, was deployed as one of 18 flight applications managed through the Unibap SpaceCloud Framework. The applications were run on a Unibap iX5-102 radiation-tolerant payload computer, hosted on the D-Orbit SCV-004 spacecraft as part of an ESA-sponsored in-orbit technology test. Our payload, referred to as the DSA D-Orbit software, demonstrates the reusability of the DSA Comm app in a substantially different context and purpose as its original mission. Comm’s original design goal was to reliably distribute messages between spacecraft swarms of arbitrary size and dynamic network topology. However, we leverage this same functionality to introduce redundancy and opportunistic parallel data processing in the context of a representative onboard image processing workload. This adaptive mission architecture was enabled in part by the SpaceCloud Framework’s use of container virtualization as the payload integration interface. By using a base container image with common high-level language runtimes and libraries, we were able to rapidly design, develop, and validate our image processing application without many of the technological barriers common to flight software development. We present details the goals, approach, results, and lessons learned through this technology demonstration experiment and contextualize those observations against present and future challenges in spacecraft software development.

computer programming↗
NASA NTRS2024

Enhancing the Payload Development Process for Lunar Gateway and Lunar Surface Science & Exploration: Space Biology Beyond Low-Earth-Orbit Instrumentation and Science Series (BLISS) Science Working Group 2023-2024 Annual Report

Space biology BLEO research is inherently driven by the differences between the LEO and BLEO environments, which can be broadly characterized by the five-hazard “RIDGE” paradigm (Radiation, Isolation, Distance, Gravity, Environment, e.g., similar to Figure 2 in (1)). Thus, the envisioned goals over the next decade will include using the cislunar and lunar surface environments to (A) characterize deep-space environments including biological effects of radiation and other stressors, (B) gain experience from isolation of very small groups in very small enclosures, (C) learn to compensate for distance from Earth via in situ resource utilization (ISRU) and bioregenerative life support, (D) gain assurance that all aspects of deep-space exploration can proceed in altered or artificial gravity environments, (E) develop essential adaptation scenarios for the built (e.g., low pressure) and external (e.g., temperature extremes, dust) environments.

Biology↗
NASA NTRS2010

ISS and Shuttle Payload Research Development and Processing

NASA's ISS and Spacecraft Processing Directorate (UB) is charged with the performance of payload development for research originating through NASA, ISS international partners, and the National Laboratory. The Payload Development sector of the Directorate takes biological research approved for on orbit experimentation from its infancy stage and finds a way to integrate and implement that research into a payload on either a Shuttle sortie or Space Station increment. From solicitation and selection, to definition, to verification, to integration and finally to operations and analysis, Payload Development is there every step of the way. My specific work as an intern this summer has consisted of investigating data received by separate flight and ground control Advanced Biological Research Systems (ABRS) units for Advanced Plant Experiments (APEX) and Cambium research. By correlation and analysis of this data and specific logbook information I have been working to explain changes in environmental conditions on both the flight and ground control unit. I have then, compiled all of that information into a form that can be presentable to the Principal Investigator (PI). This compilation allows that PI scientist to support their findings and add merit to their research. It also allows us, as the Payload Developers, to further inspect the ABRS unit and its performance

Calhoun, Kyle A.↗
NASA NTRS1977

Development of shuttle payloads

The development of payloads for the Shuttle is described in terms of two activities - one is oriented towards development of payload hardware, while the other is oriented towards the development of payload/Space Transportation System (STS) planning, scheduling, and integration techniques. This second activity is called STS Utilization Planning (SUP). In addition to describing the major aspects of SUP, a discussion of development activities on three payloads that typify direct Shuttle placement missions is included. These payloads are the First Spacelab Mission, the Atmospheric, Magnetospheric, and Plasmas in Space (AMPS) payload, and the Large Space Telescope (LST).

Murphy, J. T.↗