Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “standard interfaces”

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 73 records · Page 4
All sourcesNASA NTRSDOE OSTI
NASA NTRS2015

Standardized Modular Power Interfaces for Future Space Explorations Missions

Earlier studies show that future human explorations missions are composed of multi-vehicle assemblies with interconnected electric power systems. Some vehicles are often intended to serve as flexible multi-purpose or multi-mission platforms. This drives the need for power architectures that can be reconfigured to support this level of flexibility. Power system developmental costs can be reduced, program wide, by utilizing a common set of modular building blocks. Further, there are mission operational and logistics cost benefits of using a common set of modular spares. These benefits are the goals of the Advanced Exploration Systems (AES) Modular Power System (AMPS) project. A common set of modular blocks requires a substantial level of standardization in terms of the Electrical, Data System, and Mechanical interfaces. The AMPS project is developing a set of proposed interface standards that will provide useful guidance for modular hardware developers but not needlessly constrain technology options, or limit future growth in capability. In 2015 the AMPS project focused on standardizing the interfaces between the elements of spacecraft power distribution and energy storage. The development of the modular power standard starts with establishing mission assumptions and ground rules to define design application space. The standards are defined in terms of AMPS objectives including Commonality, Reliability-Availability, Flexibility-Configurability and Supportability-Reusability. The proposed standards are aimed at assembly and sub-assembly level building blocks. AMPS plans to adopt existing standards for spacecraft command and data, software, network interfaces, and electrical power interfaces where applicable. Other standards including structural encapsulation, heat transfer, and fluid transfer, are governed by launch and spacecraft environments and bound by practical limitations of weight and volume. Developing these mechanical interface standards is more difficult but an essential part of defining physical building blocks of modular power. This presentation describes the AMPS projects progress towards standardized modular power interfaces.

Spacecraft Power↗
NASA NTRS2005

A Proven Ground System Architecture for Promoting Collaboration and Common Solutions at NASA

NASA Goddard Space Flight Center's "GMSEC" ground system architecture was presented at GSAW2003 as a concept being studied. GMSEC would utilize a publish/subscribe middleware framework and standardized interfaces to allow custom and COTS ground system components to plug-and-play. This capability, in turn, would reduce integration costs, allow for technology infusion over time, and encourage the development and sharing of common components across missions and organizations. At GSAW2004, GMSEC was presented at a breakout session as a system working well in the NASA lab and being applied as an integral piece of reengineering efforts for several GSFC missions. Today, GMSEC is supporting five satellites at GSFC and has been selected by several future missions. Over 30 plug-and-play components are now available to missions using the GMSEC approach. Other organizations, including Marshall Space Flight Center, Johns Hopkins University's Applied Physic Lab, and the Institute for Scientific Research are each developing GMSEC-compatible components. Based on the success of GMSEC and efforts at other NASA Centers, the message bus approach is now being evaluated as a NASA Agency-wide approach for many future missions involving multiple NASA Centers as we move towards the goals of NASA s new Exploration Initiative. The presentation will explain the basic technical concepts of using a publish/subscribe framework for mission operations support (and its applicability to flight systems as well). Lessons learned on NASA's GMSEC program will allow the audience to better understand the significant benefits of this architecture approach over the traditional "one-off" solution approach. The point of the presentation is to show the long-term benefits of using a ground system architecture which incorporates many of the successful GMSEC concepts - message bus, mix of COTS and custom software, standard interfaces, plug-and-play, etc. The implications for the development process will also be discussed.

Smith, Danford↗
NASA NTRS1973

Data bus system development program

Two data bus systems were designed fabricated, Data Bus System I and Data Bus System II. The technical features of the delivered hardware include the following: (1) 5 MHz selfclocking data bus; (2) bidirectional communications utilizing Manchester Code at data rates in excess of 20,000 words per second; (3) utilization of MSI COS/MOS technology (4) probability of accepting an erroneous data bit less than 1 in 10 to the 25th power (5) low power consumption (50 to 1 reduction in quiescent current over P/MOS) (6) compatibility with projected high density packaging. Three distinct types of data bus remote terminals were developed: the subsystem interface unit, the combination of an electronic interface unit and a standard interface unit-serial, and an SIU/Preprocessor.

Harrison, J. S. J.↗
NASA NTRS1991

ELV payload environment; Proceedings of the NASA-Industry Conference on Launch Environments of ELV Payloads, Elkridge, MD, June 4-6, 1990

Various papers on the ELV payload environment are presented. Individual topics addressed include: EnviroNET: the Space Environment Information Service, ELV Payload Environments Study, perspective of GSFC Orbital Launch Services Office, Cosmic Background Explorer, the Standard Booster Interface, MLV Standard Interface Study, future payload requirements, General Dynamics Atlas family, Delta II Launch Vehicle environments, Titan vibroacoustics, Titan IV, the Scout Launch Vehicle, Pegasus.

Lauriente, Michael↗
NASA NTRS2004

Open-systems Architecture of a Standardized Command Interface Chip-set for Switching and Control of a Spacecraft Power Bus

This viewgraph presentation reviews the architecture of the The CIA-AlA chip-set is a set of mixed-signal ASICs that provide a flexible high level interface between the spacecraft's command and data handling (C&DH) electronics and lower level functions in other spacecraft subsystems. Due to the open-systems architecture of the chip-set including an embedded micro-controller a variety of applications are possible. The chip-set was developed for the missions to the outer planets. The chips were developed to provide a single solution for both the switching and regulation of a spacecraft power bus. The Open-Systems Architecture allows for other powerful applications.

power switch slice (PSS)↗
NASA NTRS2022

International Docking System Standard (IDSS) Interface Definition Document (IDD) Revision F

This IDSS IDD details the physical geometric mating interface and design loads requirements. The physical geometric interface requirements must be strictly followed to ensure physical spacecraft mating compatibility. This includes both defined components and areas that are void of components. The IDD also identifies common design parameters as identified in Section 3.0, e.g., docking initial conditions and vehicle mass properties. This information represents a recommended set of design values enveloping a broad set of design reference missions and conditions, which if accommodated in the docking system design, increases the probability of successful docking between different spacecraft.

Stanley R Donahoe↗
NASA NTRS1995

Interface Provides Standard-Bus Communication

Microprocessor-controlled interface (IEEE-488/LVABI) incorporates service-request and direct-memory-access features. Is circuit card enabling digital communication between system called "laser auto-covariance buffer interface" (LVABI) and compatible personal computer via general-purpose interface bus (GPIB) conforming to Institute for Electrical and Electronics Engineers (IEEE) Standard 488. Interface serves as second interface enabling first interface to exploit advantages of GPIB, via utility software written specifically for GPIB. Advantages include compatibility with multitasking and support of communication among multiple computers. Basic concept also applied in designing interfaces for circuits other than LVABI for unidirectional or bidirectional handling of parallel data up to 16 bits wide.

Culliton, William G.↗
NASA NTRS1990

Process and information integration via hypermedia

Success stories for advanced automation prototypes abound in the literature but the deployments of practical large systems are few in number. There are several factors that militate against the maturation of such prototypes into products. Here, the integration of advanced automation software into large systems is discussed. Advanced automation systems tend to be specific applications that need to be integrated and aggregated into larger systems. Systems integration can be achieved by providing expert user-developers with verified tools to efficiently create small systems that interface to large systems through standard interfaces. The use of hypermedia as such a tool in the context of the ground control centers that support Shuttle and space station operations is explored. Hypermedia can be an integrating platform for data, conventional software, and advanced automation software, enabling data integration through the display of diverse types of information and through the creation of associative links between chunks of information. Further, hypermedia enables process integration through graphical invoking of system functions. Through analysis and examples, researchers illustrate how diverse information and processing paradigms can be integrated into a single software platform.

Hammen, David G.↗
NASA NTRS2008

An EXPRESS Rack Overview and Support for Microgravity Research on the International Space Station (ISS)

The EXpedite the PRocessing of Experiments to Space Station or EXPRESS Rack System has provided accommodations and facilitated operations for microgravity-based research payloads for over 6 years on the International Space Station (ISS). The EXPRESS Rack accepts Space Shuttle middeck type lockers and International Subrack Interface Standard (ISIS) drawers, providing a modular-type interface on the ISS. The EXPRESS Rack provides 28Vdc power, Ethernet and RS-422 data interfaces, thermal conditioning, vacuum exhaust, and Nitrogen supply for payload use. The EXPRESS Rack system also includes payload checkout capability with a flight rack or flight rack emulator prior to launch, providing a high degree of confidence in successful operations once an-orbit. In addition, EXPRESS trainer racks are provided to support crew training of both rack systems and subrack operations. Standard hardware and software interfaces provided by the EXPRESS Rack simplify the integration processes for ISS payload development. The EXPRESS Rack is designed to accommodate multidiscipline research, allowing for the independent operation of each subrack payload within a single rack. On-orbit operations began for the EXPRESS Rack Project on April 24, 2001, with one rack operating continuously to support high-priority payloads. The other on-orbit EXPRESS Racks operate based on payload need and resource availability. Over 50 multi-discipline payloads have now been supported on-orbit by the EXPRESS Rack Program. Sustaining engineering, logistics, and maintenance functions are in place to maintain hardware, operations and provide software upgrades. Additional EXPRESS Racks are planned for launch prior to ISS completion in support of long-term operations and the planned transition of the U.S. Segment to a National Laboratory.

Pelfrey, Joseph J.↗
NASA NTRS2005

A NASA Strategy for Leveraging Emerging Launch Vehicles for Routine, Small Payload Missions

Orbital flight opportunities for small payloads have always been few and far between, and then on February 1, 2002, the situation got worse. In the wake of the loss of the Columbia during STS- 107, changing NASA missions and priorities led to the termination of the Shuttle Small Payloads Projects, including Get-Away Special, Hitcbker, and Space Experiment Module. In spite of the limited opportunities, long queue, and restrictions associated with flying experiments on a man-rated transportation system; the carriers provided a sustained, high quality experiment services for education, science, and technology payloads, and was one of the few games in town. Attempts to establish routine opportunities aboard existing ELVs have been unsuccessful, as the cost-per-pound on small ELVs and conflicts with primary spacecraft on larger vehicles have proven prohibitive. Ths has led to a backlog of existing NASA-sponsored payloads and no prospects or plans for fbture opportunities within the NASA community. The prospects for breaking out of this paradigm appear promising as a result of NASA s partnership with DARPA in pursuit of low-cost, responsive small ELVs under the Falcon Program. Through this partnership several new small ELVs, providing 1000 lbs. to LEO will be demonstrated in less than two years that promise costs that are reasonable enough that NASA, DoD, and other sponsors can once again invest in small payload opportunities. Within NASA, planning has already begun. NASA will be populating one or more of the Falcon demonstration flights with small payloads that are already under development. To accommodate these experiments, Goddard s Wallops Flight Facility has been tasked to develop a multi-payload ejector (MPE) to accommodate the needs of these payloads. The MPE capabilities and design is described in detail in a separately submitted abstract. Beyond use of the demonstration flights however, Goddard has already begun developing strategies to leverage these new ELVs as elements of a larger system designed to provide routine, low-cost end-to-end services for small science, Exploration, and education payloads. The plan leverages the management approaches of the successful Sounding Rocket Program and Shuttle Small Payloads Projects. The strategy consists of using a systems implementation approach of elements, including 1) Falcon ELVs, 2) advanced launch site technologies and processes, 3) suite of experiment carriers accommodating different mission requirements, 4) streamlined integration and test operations, 5 ) experiment brokering and management, and 6) standardized, distributed payload operations. The envisioned suite of carriers includes the MPE, a standard interface experiment carrier, and potentially a reentry fieeflyer experiment carrier. Key to the success of this strategy is standard experiment interfaces within the carriers to limit mission- unique tasks, establishmg and managing a program of scheduled reoccurring flights rather than discrete missions, and streamlined, centralized implementation of the elements. These individual elements are each under development and Goddard will demonstrate the overall system strategy low-cost small payload missions on the initial Falcon demonstration launches from Wallops. goal is to show that this model should be converted to a sustained NASA program supporting science, technology, and education, with annual flight opportunities. The paper will define in detail the various elements of the overall program, as well as provide status, philosophy, and strategy for the program that will hopefully once-and-for-all provide low-cost, routine access to space for the small payloads community.

Underwood, Bruce E.↗
NASA NTRS2012

Remotely Accessible Testbed for Software Defined Radio Development

Previous development testbeds have assumed that the developer was physically present in front of the hardware being used. No provision for remote operation of basic functions (power on/off or reset) was made, because the developer/operator was sitting in front of the hardware, and could just push the button manually. In this innovation, a completely remotely accessible testbed has been created, with all diagnostic equipment and tools set up for remote access, and using standardized interfaces so that failed equipment can be quickly replaced. In this testbed, over 95% of the operating hours were used for testing without the developer being physically present. The testbed includes a pair of personal computers, one running Linux and one running Windows. A variety of peripherals is connected via Ethernet and USB (universal serial bus) interfaces. A private internal Ethernet is used to connect to test instruments and other devices, so that the sole connection to the outside world is via the two PCs. An important design consideration was that all of the instruments and interfaces used stable, long-lived industry standards, such as Ethernet, USB, and GPIB (general purpose interface bus). There are no plug-in cards for the two PCs, so there are no problems with finding replacement computers with matching interfaces, device drivers, and installation. The only thing unique to the two PCs is the locally developed software, which is not specific to computer or operating system version. If a device (including one of the computers) were to fail or become unavailable (e.g., a test instrument needed to be recalibrated), replacing it is a straightforward process with a standard, off-the-shelf device.

Lux, James P.↗
NASA NTRS1991

Guideline requirements for serviceable spacecraft grasping/berthing/docking interfaces based on simulations and flight experience

The described efforts support a NASA Space Assembly and Servicing Working Group activity to draft guideline interface standards. The general requirements are to provide a simple, reliable, and durable system. Interface requirements developed include lateral position offset, axial and lateral velocities, and angular misalignment. A survey of concepts and simulation studies of spacecraft docking, existing docking/end effector performance criteria, and space proven, qualified docking data was conducted and evaluated, in order to provide recommended mechanical interface guidelines and interface tolerances for manual and autonomous capture operations. The criterion for the selection of the guidelines was maximum capability to handle malfunctions. Originally the guidelines for a zero velocity docking were considered to be covered within the grasping/berthing definition. It is acknowledged that perhaps a separate category needs to be established for this operation. The draft standard was delivered to the AIAA for review, revision, and issuance as the first U.S. national standard guideline on interfaces. The intent is to develop the guidelines into an International Standards Organization standard.

Thompson, Allen B.↗
NASA NTRS1980

Shuttle/payload communications and data systems interface analysis: Executive summary

Potential interface compatibility problems associated with interfacing OFT payload elements with orbiter communications and data handling elements that would result from payload or orbit failure to meet interface requirements contained in the orbiter/cargo standard interface specification are identified. The potential interface compatibility problems can be associated with either attached payloads in the payload bay or detached payloads communicating with the orbiter via an RF link. Evaluation of the attached payload orbiter interfaces was made by investigating interface problem areas experienced between the IUS and the orbiter since similar problems could be expected for other payloads.

Source record↗
NASA NTRSDate not supplied

Enabling Universal Access to Power on the Lunar Surface

The National Aeronautics and Space Administration (NASA) Artemis Missions will return human astronauts to the lunar surface, demonstrate technologies that establish a sustained presence on the lunar surface and enable human missions to Mars, and help create a lunar commercial economy. Creating a sustained permanent presence on the lunar surface will require access to continuous and highly reliable power to support mission needs. During Artemis, lunar surface operations will evolve and grow over time (years), requiring an increase in the amount of power needed (100s of kW) and distance that the power must be transmitted (up to 10 km during early Artemis missions). A lunar commercial economy is likely to exceed this power demand to the MW level and distance in the 100s of km. This increased distance and demand for highly reliable power drives the need to create an electric power grid by connecting localized lunar power systems (e.g., habitats, in-situ resource utilization plants, etc.), each containing one or more loads and/or sources. Developing a lunar surface power grid will allow lunar surface operations to resemble electrical utility operations on Earth; it allows power to be generated where it is convenient and allows power to be consumed where it is convenient and required. A lunar surface electric power grid will facilitate the growth of a lunar commercial economy because it provides a means to connect new loads to an existing electrical power system. A common standardized interface to the grid and a set of standardized voltages is required to take full advantage of the benefits of an electric power grid, similar to the terrestrial power grid. NASA Glenn Research Center is leading an effort to create universal access to power through the development of the Universal Modular Interface Converter (UMIC). The UMIC is designed to have a common interface that connects sources and loads compliant with the International Space Power System Interoperability Standard (ISPSIS) to a higher voltage AC transmission system or power grid. This presentation will further discuss the evolution of power during the Artemis missions, challenges associated with creating a sustained presence on the lunar surface, progress made on the UMIC, and future opportunities for technology development and standards.

space power systems↗
NASA NTRS1976

Payload transportation system study

A standard size set of shuttle payload transportation equipment was defined that will substantially reduce the cost of payload transportation and accommodate a wide range of payloads with minimum impact on payload design. The system was designed to accommodate payload shipments between the level 4 payload integration sites and the launch site during the calendar years 1979-1982. In addition to defining transportation multi-use mission support equipment (T-MMSE) the mode of travel, prime movers, and ancillary equipment required in the transportation process were also considered. Consistent with the STS goals of low cost and the use of standardized interfaces, the transportation system was designed to commercial grade standards and uses the payload flight mounting interfaces for transportation. The technical, cost, and programmatic data required to permit selection of a baseline system of MMSE for intersite movement of shuttle payloads were developed.

Source record↗