Search NASA⌕ Search

SEARCH · Search NASA

Results for “SpaceWire”

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
All sourcesNASA NTRSDOE OSTI
NASA NTRS2012

Use of CCSDS Packets Over SpaceWire to Control Hardware

For the Lunar Reconnaissance Orbiter, the Command and Data Handling subsystem consisted of several electronic hardware assemblies that were connected with SpaceWire serial links. Electronic hardware would be commanded/controlled and telemetry data was obtained using the SpaceWire links. Prior art focused on parallel data buses and other types of serial buses, which were not compatible with the SpaceWire and the core flight executive (CFE) software bus. This innovation applies to anything that utilizes both SpaceWire networks and the CFE software. The CCSDS (Consultative Committee for Space Data Systems) packet contains predetermined values in its payload fields that electronic hardware attached at the terminus of the SpaceWire node would decode, interpret, and execute. The hardware s interpretation of the packet data would enable the hardware to change its state/configuration (command) or generate status (telemetry). The primary purpose is to provide an interface that is compatible with the hardware and the CFE software bus. By specifying the format of the CCSDS packet, it is possible to specify how the resulting hardware is to be built (in terms of digital logic) that results in a hardware design that can be controlled by the CFE software bus in the final application

Haddad, Omar↗
NASA NTRS2016

Essential SpaceWire Hardware Capabilities for a Robust Network

The Geostationary Operational Environmental Satellite R-Series Program (GOES-R) mission is a joint program between National Oceanic & Atmospheric Administration (NOAA) and National Aeronautics & Space Administration (NASA) Goddard Space Flight Center (GSFC). GOES-R project selected SpaceWire as the best solution to satisfy the desire for simple and flexible instrument to spacecraft command and telemetry communications. GOES-R development and integration is complete and the observatory is scheduled for launch October 2016. The spacecraft design was required to support redundant SpaceWire links for each instrument side, as well as to route the fewest number of connections through a Slip Ring Assembly necessary to support Solar pointing instruments. The final design utilized two different router designs. The SpaceWire standard alone does not ensure the most practical or reliable network. On GOES-R a few key hardware capabilities were identified that merit serious consideration for future designs. Primarily these capabilities address persistent port stalls and the prevention of receive buffer overflows. Workarounds were necessary to overcome shortcomings that could be avoided in future designs if they utilize the capabilities, discussed in this paper, above and beyond the requirements of the SpaceWire standard.

SpaceWire↗
NASA NTRS2011

Backplane Design Considerations for High Speed SpaceWire Networks

SpaceWire is becoming a preferred protocol for board to board communication over a backplane in addition to its existing use over cabled interfaces, replacing other protocols due to its simplicity and readily available flight quality physical layer devices, IP cores and test equipment. However, without specific guidelines for implementing SpaceWire over a backplane, designers are left to make trade decisions regarding connector selection, layout design rules and test accessibility issues. This paper will discuss NASA's Goddard Space Flight Center s implementation of high speed SpaceWire over backplane on James Webb Space Telescope and other missions.

Pagen, Shahana Aziz↗
NASA NTRS2003

SpaceWire Driver Software for Special DSPs

A computer program provides a high-level C-language interface to electronics circuitry that controls a SpaceWire interface in a system based on a space qualified version of the ADSP-21020 digital signal processor (DSP). SpaceWire is a spacecraft-oriented standard for packet-switching data-communication networks that comprise nodes connected through bidirectional digital serial links that utilize low-voltage differential signaling (LVDS). The software is tailored to the SMCS-332 application-specific integrated circuit (ASIC) (also available as the TSS901E), which provides three highspeed (150 Mbps) serial point-to-point links compliant with the proposed Institute of Electrical and Electronics Engineers (IEEE) Standard 1355.2 and equivalent European Space Agency (ESA) Standard ECSS-E-50-12. In the specific application of this software, the SpaceWire ASIC was combined with the DSP processor, memory, and control logic in a Multi-Chip Module DSP (MCM-DSP). The software is a collection of low-level driver routines that provide a simple message-passing application programming interface (API) for software running on the DSP. Routines are provided for interrupt-driven access to the two styles of interface provided by the SMCS: (1) the "word at a time" conventional host interface (HOCI); and (2) a higher performance "dual port memory" style interface (COMI).

Clark, Douglas↗
NASA NTRS2012

Time Distribution Using SpaceWire in the SCaN Testbed on ISS

A paper describes an approach for timekeeping and time transfer among the devices on the CoNNeCT project s SCaN Testbed. It also describes how the clocks may be synchronized with an external time reference; e.g., time tags from the International Space Station (ISS) or RF signals received by a radio (TDRSS time service or GPS). All the units have some sort of counter that is fed by an oscillator at some convenient frequency. The basic problem in timekeeping is relating the counter value to some external time standard such as UTC. With SpaceWire, there are two approaches possible: one is to just use SpaceWire to send a message, and use an external wire for the sync signal. This is much the same as with the RS- 232 messages and l pps line from a GPS receiver. However, SpaceWire has an additional capability that was added to make it easier - it can insert and receive a special "timecode" word in the data stream.

Lux, James P.↗
NASA NTRS2007

Magnetospheric Multiscale Mission SpaceWire Implementation

This viewgraph presentation reviews the use of SpaceWire in the Magnetospheric Multiscale Mission (MMS). The Science Objectives of the are to Discover the fundamental plasma physics process of reconnection in the Earth's magnetosphere using temporal scales of milliseconds to seconds and spatial scales of 10s to 100s of km. MMS should be the first NASA mission to fly several new Spacewire protocols including: - Remote Memory Access Protocol - Distributed interrupt Protocol - Standardized Backplane These are briefly reviewed in the presentation.

Jackson, George↗
NASA NTRS2008

NASA Activities: SpaceWire Working Group Meeting

This brief presentation highlights the efforts of the SpaceWire working group. The European Space Agency (ESA) contracted with the University of Dundee (UoD) to develop a prototype SpaceFibre Codec, which UoD has been demonstrated in hardware. UoD released a SpaceFibre Outline Specification which NASA plans to evaluate using a SpaceFibre sub-orbital demonstration (in development). Comments, questions and recommendations for ESA and UoD are provided here to generate discussion and expand participation. General findings are that the system level behavior of SpaceFibre is missing from the SpaceFibre Outline Specification, there is a need to understand how SpaceWire maps to SpaceFibre (and vice versa), and there is a need to clarify user interface to resolve inconsistencies. Architecture, virtual channel and programmatic recommendations are presented.

Rakow, Glenn↗
NASA NTRS2016

The Geostationary Operational Satellite R Series SpaceWire Based Data System

The Geostationary Operational Environmental Satellite R-Series Program (GOES-R, S, T, and U) mission is a joint program between National Oceanic & Atmospheric Administration (NOAA) and National Aeronautics & Space Administration (NASA) Goddard Space Flight Center (GSFC). SpaceWire was selected as the science data bus as well as command and telemetry for the GOES instruments. GOES-R, S, T, and U spacecraft have a mission data loss requirement for all data transfers between the instruments and spacecraft requiring error detection and correction at the packet level. The GOES-R Reliable Data Delivery Protocol (GRDDP) [1] was developed in house to provide a means of reliably delivering data among various on board sources and sinks. The GRDDP was presented to and accepted by the European Cooperation for Space Standardization (ECSS) and is part of the ECSS Protocol Identification Standard [2]. GOES-R development and integration is complete and the observatory is scheduled for launch November 2016. Now that instrument to spacecraft integration is complete, GOES-R Project reviewed lessons learned to determine how the GRDDP could be revised to improve the integration process. Based on knowledge gained during the instrument to spacecraft integration process the following is presented to help potential GRDDP users improve their system designs and implementation.

Networks↗
NASA NTRS2016

Using SpaceWire Time Codes for Spacecraft Time Synchronization

This paper describes how SpaceWire Time Codes can be used for synchronizing time within various subsystems of a spacecraft as well as, maintaining a common time reference needed for coordinating operations within a spacecraft. The algorithms to account for inaccuracies in the time distribution method were based on the NASA-4009 Space Telecommunication Radio System (STRS) standard [1], which defined an interface for synchronizing clocks running at different tick rates and tick resolutions.

SpaceWire Time Distribution Protocol↗
NASA NTRS2006

SpaceWire Protocol ID: What Does it Mean to You?

This document is a slide presentation reviewing the SpaceWire (SW) Protocol. The purpose of the presentation is to describe the latest work of the SW working group to promote upper level protocol standardization. The presentation also briefly describes the SW protocol.

Rakow, Glenn Parker↗
NASA NTRS2007

SpaceWire Plug and Play Updates

This viewgraph presentation reviews the work of the SpaceWire Plug N Play Workgroup. (SpW PnP WG). The chief product of SpW PnP WG will be to develop specification of necessary hardware features required in support upper layer (software) PnP implementations.

Rakow, Glenn↗
NASA NTRS2006

NASA SpaceWire Activities/Comments/Recommendations

This viewgraph presentation reviews NASA's activities, and proposes recommendations for the further use of the SpaceWire (SpW). The areas covered in this presentation are: (1) Protocol ID assignment, (2) Protocol development, (3) Plug & Play (PnP), (4) Recommended additions t o SpW protocol and (5) SpaceFibre trade.

Rakow, Glenn↗
NASA NTRS2010

The Geostationary Operational Satellite R Series SpaceWire Based Data System Architecture

The GOES-R program selected SpaceWire as the best solution to satisfy the desire for simple and flexible instrument to spacecraft command and telemetry communications. Data generated by GOES-R instruments is critical for meteorological forecasting, public safety, space weather, and other key applications. In addition, GOES-R instrument data is provided to ground stations on a 24/7 basis. GOES-R requires data errors be detected and corrected from origin to final destination. This paper describes GOES-R developed strategy to satisfy this requirement

Krimchansky, Alexander↗
NASA NTRS2011

Radiation-Tolerant, SpaceWire-Compatible Switching Fabric

Current and future near-Earth and deep space exploration programs and space defense programs require the development of robust intra-spacecraft serial data transfer electronics that must be reconfigurable, fault-tolerant, and have the ability to operate effectively for long periods of time in harsh environmental conditions. Existing data transfer systems based on state-of-the-art serial data transfer protocols or passive backplanes are slow, power-hungry, and poorly reconfigurable. They provide limited expandability and poor tolerance to radiation effects and total ionizing dose (TID) in particular, which presents harmful threats to modern submicron electronics. This novel approach is based on a standard library of differential cells tolerant to TID, and patented, multi-level serial interface architecture that ensures the reliable operation of serial interconnects without application of a data-strobe or other encoding techniques. This proprietary, high-speed differential interface presents a lowpower solution fully compatible with the SpaceWire (SW) protocol. It replaces a dual data-strobe link with two identical independent data channels, thus improving the system s tolerance to harsh environments through additional double redundancy. Each channel incorporates an automatic line integrity control circuitry that delivers error signals in case of broken or shorted lines.

Katzman, Vladimir↗
NASA NTRS2011

SpaceWire Tiger Team Findings and Suggestions

This technical report intends to highlight the key findings and recommendations of the SpaceWire Tiger Team for the CoNNeCT project. It covers findings which are technical in nature, covering design concepts and approaches.

Ishac, Joseph A.↗