Search NASA⌕ Search

SEARCH · Search NASA

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 235 records · Page 13
All sourcesNASA NTRSDOE OSTI
NASA NTRS1994

SCL: An off-the-shelf system for spacecraft control

In this age of shrinking military, civil, and commercial space budgets, an off-the-shelf solution is needed to provide a multimission approach to spacecraft control. A standard operational interface which can be applied to multiple spacecraft allows a common approach to ground and space operations. A trend for many space programs has been to reduce operational staff by applying autonomy to the spacecraft and to the ground stations. The Spacecraft Command Language (SCL) system developed by Interface and Control Systems, Inc. (ICS) provides an off-the-shelf solution for spacecraft operations. The SCL system is designed to provide a hyper-scripting interface which remains standard from program to program. The spacecraft and ground station hardware specifics are isolated to provide the maximum amount of portability from system to system. Uplink and downlink interfaces are also isolated to allow the system to perform independent of the communications protocols chosen. The SCL system can be used for both the ground stations and the spacecraft, or as a value added package for existing ground station environments. The SCL system provides an expanded stored commanding capability as well as a rule-based expert system on-board. The expert system allows reactive control on-board the spacecraft for functions such as electrical power systems (EPS), thermal control, etc. which have traditionally been performed on the ground. The SCL rule and scripting capability share a common syntax allowing control of scripts from rules and rules from scripts. Rather than telemeter over sampled data to the ground, the SCL system maintains a database on-board which is available for interrogation by the scripts and rules. The SCL knowledge base is constructed on the ground and uploaded to the spacecraft. The SCL system follows an open-systems approach allowing other tasks to communicate with SCL on the ground and in space. The SCL system was used on the Clementine program (launched January 25, 1994) and is required to have bidirectional communications with the guidance, navigation, and control (GNC) algorithms which were written as another task. Sequencing of the spacecraft maneuvers are handled by SCL, but the low-level thruster pulse commands are handled by the GNC software. Attitude information is reported back as telemetry, allowing the SCL expert system to inference on the changing data. The Clementine SCL flight software was largely reused from another Naval Center for Space Technology (NCST) satellite program. This paper details the SCL architecture and how an off-the-shelf solution makes sense for multimission spacecraft programs. The Clementine mission will be used as a case study in the application of the SCL to a 'fast track' program. The benefits of such a system in a 'better, cheaper, faster' climate will be discussed.

Buckley, Brian↗
NASA NTRS1996

Modular Software for Spacecraft Navigation Using the Global Positioning System (GPS)

The Goddard Space Flight Center Flight Dynamics and Mission Operations Divisions have jointly investigated the feasibility of engineering modular Global Positioning SYSTEM (GPS) navigation software to support both real time flight and ground postprocessing configurations. The goals of this effort are to define standard GPS data interfaces and to engineer standard, reusable navigation software components that can be used to build a broad range of GPS navigation support applications. The paper discusses the GPS modular software (GMOD) system and operations concepts, major requirements, candidate software architecture, feasibility assessment and recommended software interface standards. In additon, ongoing efforts to broaden the scope of the initial study and to develop modular software to support autonomous navigation using GPS are addressed,

Truong, S. H.↗
NASA NTRS1985

Space Station crew interface specifications and standards

NASA's Space Station Human Productivity and Man/System Integration Standards programs are described. The data collection methodologies and analyses utilized in the productivity study are examined. The study reveals that attention to habitability is required in order to maximize human productivity for on-orbit operations. The nine program tasks used to develop standards for man/system integration are discussed.

Geer, C. W.↗
NASA NTRS1991

KBS Demonstration

The Knowledge Based System (KBS) demonstration included five different items: the executive program, three of the industrial codes, and graphical display capability using current MYI MS-DOS programs. The graphics capability included two and three dimensional plots viewed from different angles. This capability will be ported to OS/2 and made an integral part of the KBS executive program. The three codes demonstrated included Spiral Groove Gas Seals (SPIRAL), Gas Cylindrical Seals (GCYL), and Incompressible Seals (ICYL). The SPIRAL and GCYL interface has the standard PM interface, while the ICYL interface was designed using ToolBook.

Aggarwal, Bharat↗
NASA NTRS2003

Standard user data services for spacecraft applications

The Consultative Committee for Space Data Systems is an international organization of national space agencies that is branching out to provide new standards to enhanced reuse of spacecraft equiptment and software. These Spacecraft Onboard Interface (SOIF) standards will be based on the well-known Internet protocols. this paper will review the SOIF standards by looking at the services that are being proposed for SOIF.

space interfaces avionics interfaces standard inte↗
DOE OSTI2024

Multiphysics modeling of accelerators through code integration

This work aims to improve the ability of particle accelerator researchers to develop high-performance accelerator cavity designs by creating an overall multiphysics framework that integrates and couples existing application codes. This framework will allow accelerator researchers to build multiphysics models that will optimize cavity design, improve understanding of whole-device performance, and reduce the development and fabrication costs of accelerator research. We utilize the open-source VizSchema data standard as an intermediate data structure interface layer to standardize interfaces between individual application codes. VizScema is extensively documented online, and plugins for VizSchema are available for popular visualization packages, including VisIt and ParaView. Currently, the work focuses on coupling the EM field solver COMSOL and the electron gun code MICHELLE to allow COMSOL field-solve results to be seamlessly used by MICHELLE for particle-solve. Later work will extend this integration to include other fields, particles, and thermodynamics simulation codes.

43 PARTICLE ACCELERATORS↗
NASA NTRS2019

Flexible Modem Interface (FMI) in Space - Extending Standardized Commercial Satellite Communications Services to Space Users

Recent innovations are producing a multitude of advanced commercial satellite communications (COMSATCOM) systems that could deliver massive amounts of SATCOM capacity at a fraction of current cost while also offering reliability and availability that is critical to achieving mission success for orbiting assets. Recognizing the alignment of commercial capabilities with the National Aeronautics and Space Administration's (NASA) diverse mission requirements, the agency is proactively engaging industry to formulate strategies leading towards a NASA communications architecture that includes advanced commercial capabilities. To fully leverage the expanded space resources, NASA must also address the integration of commercial waveforms into its space terminals. In pursuit of similar goals, the United States Department of Defense (DoD) is leading the standardization of the flexible modem interface (FMI) to address service integration for their tactical terminals in pursuit of a DoD Wideband SATCOM Enterprise.This paper describes how NASA is adapting this FMI standard to work with the Space Telecommunications Radio System (STRS) software-defined radio (SDR) framework to address the challenging size, weight, and power resource requirements for terminals in space. A full adaptation would include waveform compatibility with modular baseband processing, frequency compatibility with a wideband front end, and radiated beam control with an electronically steerable antenna to enable multi-provider commercial service capability in a feasible package for space terminals. Security is also a key aspect to be addressed for this integration since data will flow through commercial networks, commercial service providers have their own security mechanisms, and space terminals must be able to securely load proprietary software and firmware needed to access the commercial networks on demand. Success of this effort means commercial partners will be able to allow network-compliant implementations to be hosted on STRS-compliant SDRs in space for reliable and capable network access.

COMSATCOM↗
NASA NTRS2006

SpaceWire Plug and Play

The ability to rapidly deploy inexpensive satellites to meet tactical goals has become an important goal for military space systems. In fact, Operationally Responsive Space (ORS) has been in the spotlight at the highest levels. The Office of the Secretary of Defense (OSD) has identified that the critical next step is developing the bus standards and modular interfaces. Historically, satellite components have been constructed based on bus standards and standardized interfaces. However, this has not been done to a degree, which would allow the rapid deployment of a satellite. Advancements in plug-and-play (PnP) technologies for terrestrial applications can serve as a baseline model for a PnP approach for satellite applications. Since SpaceWire (SpW) has become a de facto standard for satellite high-speed (greater than 200Mbp) on-board communications, it has become important for SpW to adapt to this Plug and Play (PnP) environment. Because SpW is simply a bulk transport protocol and lacks built-in PnP features, several changes are required to facilitate PnP with SpW. The first is for Host(s) to figure out what the network looks like, i.e., how pieces of the network, routers and nodes, are connected together; network mapping, and to receive notice of changes to the network. The second is for the components connected to the network to be understood so that they can communicate. The first element, network topology mapping & change of status indication, is being defined (topic of this paper). The second element describing how components are to communicate has been defined by ARFL with the electronic data sheets known as XTEDS. The first element, network mapping, is recent activities performed by Air Force Research Lab (ARFL), Naval Research Lab (NRL), NASA and US industry (Honeywell, Clearwater, FL, and others). This work has resulted in the development of a protocol that will perform the lower level functions of network mapping and Change Of Status (COS) indication required by Plug 'n' Play over SpaceWire. This work will be presented to the SpaceWire working group for standardization under European Cooperation for Space Standardization (ECSS) and to obtain a permanent Protocol ID (see SpaceWire Protocol ID: What Does it Mean to You; IEEE Aerospace Conference 2006). The portion of the Plug 'n' Play protocol that will be described in this paper is how the Host(s) of a SpaceWire network map the network and detect additions and deletions of devices on a SpaceWire network.

Rakow, Glenn↗
NASA NTRS1979

The cost benefits of the Spacelab system to scientific investigations and space applications

Cost advantages of the Spacelab system to scientific experiments in space and space operations are presented. The payload integration concepts developed for Spacelab are examined, and it is shown that Spacelab and Shuttle integration, communications and data processing, launch support requirements and flight operations will provide a considerable savings in the costs of space research relative to previous space systems. Spacelab modular design, incorporating features such as standard payload interfaces, optional mission dependent equipment and standard services, such as the Experiment Computer Operating System, is shown to offer the user a wider range of services than previous programs, also at significantly lower costs. It is concluded that the Spacelab system will greatly reduce the costs and broaden the opportunities for scientific investigation in space.

Jean, O. C.↗
NASA NTRS2002

Expedite the Processing of Unpressurized Payloads to the International Space Station Using the ExPRESS Pallet

The Expedite the PRocessing of Experiments to Space Station (ExPRESS) Pallet will be used as an experiment platform for external/unpressurized payloads to be flown aboard the International Space Station (ISS). The purpose of the ExPRESS Pallet is to provide an easy access to the ISS for Scientific Investigators that require an external platform for their experiment hardware. As the name of the ExPRESS Pallet implies, the objective of the ExPRESS program is to provide a simplified integration process in a short time period (24 months) for payloads to be flown on the ISS. The ExPRESS Pallet provides unique opportunities for research across many science disciplines, including earth observation, communications, solar and deep space viewing, and long-term exposure. The ExPRESS Pallet provides access to Ram, Wake, Nadir, Zenith and Earth Limb for viewing and exposure to the space environment. The ExPRESS Pallet will provide standard physical payload interfaces, and a standard integration template. The ExPS consists of the Pallet structure, payload Adapters, a subsystem assembly that includes data controller, power distribution and conversion, and Extra Vehicular Robotics compatibility. The ExPRESS Pallet provides the capability to changeout payloads on-orbit via the ExPRESS Pallet Adapter (ExPA). The following paragraphs will describe the Services and Accommodations available to the Payload developers by the ExPRESS Pallet and a brief description of the Integration process. More detailed information on the ExPRESS Pallet can be found in the ExPRESS Pallet Payload Accommodations Handbook, SSP 52000-PAH-EPP.

Bacskay, Allen S.↗
NASA NTRS1980

The payload connection - Approaches to onboard data processing for scientific systems on the Space Shuttle

The integration of payload instruments into the Command and Data Management Subsystem (CDMS) of the Space Shuttle Spacelab is discussed. Specific emphasis is on the distributed (self-contained processor) vs centralized (Spacelab Computer) approach to science payload utilization of these control and data handling capabilities. An overview of the Spacelab CDMS is first given. A synopsis of the integration process for Spacelab Missions 1, 2, and 3 is discussed. Three different hardware approaches to payload command and data handling are then categorized from which Spacelab implementations to date are derived. The different types of Spacelab Mission 3 payload CDMS hardware and software being used are discussed, including examples of microprocessors and data acquisition systems. Preliminary costs for Spacelab application software vs other flight software approaches are compared. A standard RAU interface that would permit a range of ECOS services to be provided, yet be implemented as a mass-produceable unit for incorporation into payloads, is proposed, in keeping with the trend toward simplifying the integration effort, standardizing CDMS interfaces, and ultimately lowering cost.

Konkel, C. R.↗
NASA NTRS1992

Recommendations for a service framework to access astronomical archives

There are a large number of astronomical archives and catalogs on-line for network access, with many different user interfaces and features. Some systems are moving towards distributed access, supplying users with client software for their home sites which connects to servers at the archive site. Many of the issues involved in defining a standard framework of services that archive/catalog suppliers can use to achieve a basic level of interoperability are described. Such a framework would simplify the development of client and server programs to access the wide variety of astronomical archive systems. The primary services that are supplied by current systems include: catalog browsing, dataset retrieval, name resolution, and data analysis. The following issues (and probably more) need to be considered in establishing a standard set of client/server interfaces and protocols: Archive Access - dataset retrieval, delivery, file formats, data browsing, analysis, etc.; Catalog Access - database management systems, query languages, data formats, synchronous/asynchronous mode of operation, etc.; Interoperability - transaction/message protocols, distributed processing mechanisms (DCE, ONC/SunRPC, etc), networking protocols, etc.; Security - user registration, authorization/authentication mechanisms, etc.; Service Directory - service registration, lookup, port/task mapping, parameters, etc.; Software - public vs proprietary, client/server software, standard interfaces to client/server functions, software distribution, operating system portability, data portability, etc. Several archive/catalog groups, notably the Astrophysics Data System (ADS), are already working in many of these areas. In the process of developing StarView, which is the user interface to the Space Telescope Data Archive and Distribution Service (ST-DADS), these issues and the work of others were analyzed. A framework of standard interfaces for accessing services on any archive system which would benefit archive user and supplier alike is proposed.

Travisano, J. J.↗