DOCSLIB.ORG

A Link-Layer Broadcast Service for Spacewire Networks Allison Roberts, Sandra G

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
A Link-Layer Broadcast Service for Spacewire Networks Allison Roberts, Sandra G A Link-Layer Broadcast Service for SpaceWire Networks Allison Roberts, Sandra G. Dykes, Robert Klar, Christopher C. Mangels Southwest Research Institute® 6220 Culebra Road San Antonio TX 78238-5166 210.522.3248 {allison.roberts, sandra.dykes, robert.klar, christopher.mangels}@swri.org Abstract—SpaceWire, a recent ESA standard, is gaining dynamically configured environment. For example, it may popularity because of its simple circuitry, low power be suitable for manned missions, such as NASA’s Crew consumption, and high-link speed. However network Exploration Vehicle (CEV). Introducing the human management on SpaceWire networks is hampered by the element introduces the potential for the addition or removal lack of a link-layer broadcast mechanism which is required of devices from the network. Another possible scenario for services such as the Address Resolution Protocol (ARP) would be coordinated collaborative measurements between and the Dynamic Host Configuration Protocol (DHCP). SpaceWire-based Science Instruments on multiple Currently, address resolution and host IP assignments spacecraft as they move through orbits, creating dynamic, require manual configuration. This paper describes a link- short-duration networks. SpaceWire has also been layer broadcast service and encapsulation service for suggested for some terrestrial applications, such as SpaceWire that is implemented in the host node software streaming video. Users of such applications would drivers and requires no change to routers or host node undoubtedly want to make use of automatic network interface hardware. We believe this work will help move configuration support. SpaceWire towards a future of Plug And Play networks, decreasing the cost and time required to develop and To achieve the goal of automatic network configuration, we integrate space systems.12 offer a plan which leverages support from well established existing standards, including Address Resolution Protocol TABLE OF CONTENTS (ARP) and Dynamic Host Configuration Protocol (DHCP) and introduces a dynamic routing protocol. None of these 1. AUTOMATIC CONFIGURATION OF SPACEWIRE ...1 technologies are currently supported directly by SpaceWire 2. SPACEWIRE NETWORK LAYER ............................2 networks as defined by the standard (ESA specification 3. SPACEWIRE MESSAGES ........................................3 ECSS-E-50-12A) [4]. One element missing from 4. SPACEWIRE BROADCAST PROTOCOL ..................3 SpaceWire that would help support such standard protocols 5. BROADCAST AND HIGHER-LEVEL SERVICES .......5 is a link-layer broadcast. ARP utilizes broadcasts to 6. IP OVER SPACEWIRE............................................6 discover the mapping between an IP (network-layer) 7. BROADCAST PROTOCOL DEVELOPMENT .............6 address and a unique hardware (link-layer) address. DHCP 8. RELATED WORK ...................................................8 clients use broadcast to discover the DHCP server that 9. CONCLUSIONS .......................................................8 dynamically assigns a unique network address. Routing REFERENCES .............................................................9 protocols for wired networks typically rely on router-to- BIOGRAPHY .............................................................10 router communication, rather than link-layer broadcast ACKNOWLEDGEMENTS ...........................................10 (although broadcasts are fundamental to ad hoc routing protocols). SpaceWire differs from most wired networks in 1. AUTOMATIC CONFIGURATION OF SPACEWIRE that the host nodes must specify the packet destination address and, if regions are used, must also specify the SpaceWire was introduced as a high-speed (10-400Mbps), address of the appropriate regional gateway. Broadcast low-power, and low-cost network for spacecraft. It is in use could be used to disseminate the addresses of regional on several current and future space missions from NASA, gateways to the host nodes. While this method does not the European Space Agency (ESA), the Japanese Space address dynamic updating of the router forwarding tables, it Agency (JAXA), and the Russian Space Agency. These does provide a simple “first step” that dynamically missions include the Geostationary Environmental Satellite configures route information on host nodes. Program (GOES-R), the James Webb Space Telescope, and the Lunar Reconnaissance Orbiter [5]. This paper presents three central concepts. The first concept is that of a unique address for a SpaceWire host. While most current applications of SpaceWire support The SpaceWire standard specifies that hosts may be statically configured networks, it is easy to envision a future assigned a logical address (LA) which is unique within a where it would prove advantageous to use SpaceWire in a region. However network-wide uniqueness is not 1 guaranteed since, a LA may be reused by another host in a 1 different region. Regions are inferred from information in 1-4244-0525-4/07/$20.00 ©2007 IEEE. 2 the router forwarding tables and do not have explicit IEEEAC paper #1484, Version 4, Updated January 15, 2007 1 identifiers. In our approach, each region is explicitly [1..31] is known as a “path address” and specifies which assigned a unique region identifier (RID). We combine the physical port the packet should travel through. An address RID with the host node LA to form a host address that is in the range [32..255] is known as a “logical address.” unique across the entire network. A unique address is When a SpaceWire router receives a packet with a logical required to support a standard ARP protocol [9]. address, it consults the routing table to find the next packet destination. The logical addresses of 254 and 255 are The second concept we introduce is that of a link-layer reserved. For more detail on SpaceWire addressing, refer to broadcast mechanism. An earlier version of our broadcast [4]. protocol was introduced at the 2006 Space Internetworking Workshop [3]. Implementing link-layer broadcast entirely SpaceWire routing is performed by configuration of routing in the host nodes allows the use of ARP, DHCP, and other tables stored on the routers. The standard method for a configuration protocols without modification to existing router table update is a manual configuration. Routers may Commercial-Off-the-Shelf (COTS) SpaceWire routers or be configured to delete the first byte of the address as the host interface hardware. The broadcast algorithm conforms packet is forwarded, a technique known as header deletion. to the SpaceWire standard [4], adding only the concept of Header deletion is commonly applied to path addressing, to the region identifier. reveal the next physical port the message will be directed to. The third contribution of this paper is a method to Since SpaceWire uses a single byte for logical addresses, dynamically and automatically update route information on there are only 222 unique logical addresses available. To host nodes using the link-layer broadcast mechanism. Our allow for larger networks, or to support the re-use of logical method broadcasts regional gateway update messages to all addresses, SpaceWire regions were introduced. Each region hosts that contain the logical addresses of gateways between is guaranteed to have a non-repeating set of logical each region. To send a SpaceWire message, a host node addresses. need only add the logical gateway address(es) and the destination’s logical address. Hosts do not need to know Regional Gateways network topology or path information. This reduces the When a packet needs to travel between SpaceWire regions, problem of route discovery to maintaining router a special logical address known as a gateway is used. forwarding tables. Nodes in different regions typically use different gateways to reach the same destination. This requires that each host Our approach to unique address formation, broadcast, and node know the gateway as well as the logical address to dissemination of routing information to hosts can be each potential destination. Routers are configured to confined to software on the host nodes, and in particular to perform header deletion on gateway addresses. SpaceWire interface drivers. No changes are required to the SpaceWire specification, to SpaceWire routers, nor to host interface hardware. Region 1 Gateway to Region 2 Region 2 While extending the breadth of SpaceWire network Router Router A 67 B services, it is important to remain compatible with the 52 PID Data 3 established SpaceWire standard and to support existing hardware. This improves interoperability and encourages N1 N2 N3 N4 N5 acceptance. The broadcast service and routing protocol LA 32 LA 33 LA 34 LA 32 LA 52 described in this paper are designed to be entirely RX compatible with the SpaceWire standard. Although last TX 52 PID Data 67 52 PID Data Message year we presented a packet encapsulation service [2] to Message provide a mechanism for identifying packet application or stack association, we have chosen to instead implement the Figure 1. SpaceWire Gateway Addressing encapsulation service more recently introduced by the SpaceWire Working Group [6]. The improvements Figure 1 shows an example of gateway addressing. To presented in this paper are designed to support multiple direct a packet from Region 1, Node 2 to Region 2, Node 5, higher-level network stacks (IPv4, IPv6, SCPS-NP) as well the gateway address “67” is first used to move to the new as custom applications that directly interface to the driver. region. When the
Load more

Recommended publications
  • Spacewire Links Routers and Networks ECSS-E50-12A
    SpaceWire Links Routers and Networks ECSS-E50-12A Presented by Ph. Armbruster ESA/ESTEC/TOS-ED Data Systems Division [email protected] Credit – University of Dundee - European Space Agency Contents Part 1 Contents Part 2 § Introduction § SpaceWire Packets § Physical Level § Routing Switch Concepts § Signal Level – Worm-hole routing § Character Level – Header deletion – Path addressing § Exchange Level – Logical addressing § Packet Level – Priority – Arbitration – Group adaptive routing – Fault tolerance § Networks § Time Codes SpaceWire § SpaceWire is a standard for spacecraft onboard data-handling – ESA ECSS-E-50-12A § SpaceWire based on two commercial standards – IEEE-1355 – LVDS (Low Voltage Differential Signalling) § SpaceWire is the result of work by many people in ESA, NASA, the space industry and academia. SpaceWire Key Features § High data rate ( > 100 Mbps) § Distance of 10m + § Scalable § Low error rate § Good EMC performance § Low-power § Fault tolerance support § Radiation tolerant components Purpose § SpaceWire provides a unified high-speed data- handling infrastructure for connecting together – sensors, – processing elements, – mass-memory units, – downlink telemetry sub-systems, and – EGSE equipment. Purpose § The purpose of the SpaceWire standard is – to facilitate the construction of high-performance onboard data-handling systems – to help reduce system integration costs – to promote compatibility between data-handling equipment and sub-systems – to encourage re-use of data handling equipment across several different missions. Scope § SpaceWire links are – full-duplex, point-to-point, serial data communication links. § The scope of the SpaceWire standard is the – physical connectors and cables, – electrical properties, and – logical protocols. Scope § The SpaceWire standard covers the following normative protocol levels – Physical Level: Connectors, cables, cable assemblies and PCB tracks – Signal Level: Signal encoding, voltage levels, noise margins, and data rates.
    [Show full text]
  • Spacewire Protocol ID: What Does It Means to You?
    Spacewire Protocol ID: What Does It Means To You? Glenn Rakow Richard Schnurr Daniel Gilley Steve Parkes NASA GSFC NASA GSFC Lockheed Martin University of Dundee Code 561 Code 561 Greenbelt, MD Greenbelt, MD Sunnyvale, CA Dundee, Scotland, UK 301-286-5993 301-2864 852 00441382345194 [email protected] [email protected] daniel.nilley6dlmco.com sparkes@,computing.dundee.ac.uk Abstract- Spacewire is becoming a popular solution for standard but with one restriction. The restriction is that the satellite high-speed data buses because it is a simple first byte seen at the destination by the user needs to be a standard that provides great flexibility for a wide range of logical address, independent of the addressing scheme used. system requirements. It is simple in packet format and The second field is defined as the Protocol ID, which is protocol, allowing users to easily tailor their implementation usually one byte in length. The packet cargo (user defined) for their specific application. Some of the attractive aspects follows the Protocol ID. After the packet cargo is the EOP, of Spacewire that make it easy to implement also make it which defines the end of packet. The value of the Protocol hard for future reuse. Protocol reuse is difticult because ID is assigned by the Spacewire working group and the Spacewire does not have a defined mechanism to protocol description published for others to use. communicate with the higher layers of the protocol stack. This has forced users of Spacewire to define unique packet The development of Protocols for Spacewire is currently formats and define how these packets are to be processed.
    [Show full text]
  • Status of the James Webb Space Telescope Integrated Science Instrument Module System
    https://ntrs.nasa.gov/search.jsp?R=20110015230 2019-08-31T16:13:29+00:00Z Status of the James Webb Space Telescope Integrated Science Instrument Module System Matthew A. Greenhouse*, Michael P. Drury, Jamie L. Dunn, Stuart D. Glazer, Ed Greville, Gregory Henegar, Eric L. Johnson, Ray Lundquist, John C. McCloskey, Raymond G. Ohl IV, Robert A. Rashford, and Mark F. Voyton Goddard Space Flight Center, Greenbelt, MD 20771 ABSTRACT The Integrated Science Instrument Module (ISIM) of the James Webb Space Telescope (JWST) is discussed from a systems perspective with emphasis on development status and advanced technology aspects. The ISIM is one of three elements that comprise the JWST space vehicle and is the science instrument payload of the JWST. The major subsystems of this flight element and their build status are described. Keywords: JWST, Instrumentation 1. INTRODUCTION The James Webb Space Telescope (Figure 1) is under development by NASA for launch during 2014 with major contributions from the European and Canadian Space Agencies. The JWST mission is designed to enable a wide range of science investigations across four broad themes: [1] observation of the first luminous objects after the Big Bang, [2] the evolution of galaxies, [3] the birth of stars and planetary systems, and [4] the formation of planets and the origins of life.1, 2, 3 Its Integrated Science Instrument Module (ISIM) is the science payload of the JWST.4, 5, 6 Along with the telescope and spacecraft, the ISIM is one of three elements that comprise the JWST space vehicle. At 1.4 mT, it makes up approximately 20% of both the observatory mass and cost to launch.
    [Show full text]
  • Arxiv:0706.2344V1 [Astro-Ph] 15 Jun 2007 Ate .Grio,Toa Ono,Sihrs Manthripragad S
    Detectors for the James Webb Space Telescope Near-Infrared Spectrograph I: Readout Mode, Noise Model, and Calibration Considerations Bernard J. Rauscher and Ori Fox1 NASA Goddard Space Flight Center, Greenbelt, MD 20771 [email protected] Pierre Ferruit2,3 Universit´ede Lyon, Lyon, F-69003, France Robert J. Hill8, Augustyn Waczynski4, Yiting Wen6, Wei Xia-Serafino4, Brent Mott, David Alexander, Clifford K. Brambora, Rebecca Derro, Chuck Engler, Matthew B. Garrison, Thomas Johnson, Sridhar S. Manthripragada, James M. Marsh, Cheryl Marshall, Robert J. Martineau, Kamdin B. Shakoorzadeh7, Donna Wilson, Wayne D. Roher5, and Miles Smith NASA Goddard Space Flight Center, Greenbelt, MD 20771 Craig Cabelli, James Garnett, Markus Loose, Selmer Wong-Anglin, Majid Zandian, and Edward Cheng8 Teledyne Imaging Sensors, 5212 Verdugo Way, Camarillo, CA 93012 arXiv:0706.2344v1 [astro-ph] 15 Jun 2007 Timothy Ellis, Bryan Howe, Miriam Jurado, Ginn Lee, John Nieznanski, Peter Wallis, and James York ITT Space Systems Division, 1447 St. Paul Street, Rochester, NY, 14653 Michael W. Regan Space Telescope Science Institute, 3700 San Martin Drive, Baltimore, MD 21218 Donald N.B. Hall and Klaus W. Hodapp –2– Institute for Astronomy, 640 North A´ohoku Place, #209, Hilo HI 96720 and Torsten B¨oker, Guido De Marchi, Peter Jakobsen, and Paolo Strada ESTEC, Astrophysics Division, Postbus 299, Noordwijk, NL2200 AG, Netherlands Received ; accepted Accepted by Publications of the Astronomical Society of the Pacific 1Also at Department of Astronomy, University of Virginia,
    [Show full text]
  • → Well Connected
    spacewire technology → → WELL CONNECTED The SpaceWire on-board data-handling network Steve Parkes University of Dundee, Scotland, UK Philippe Armbruster & Martin Suess Directorate of Technical and Quality Management, ESTEC, Noordwijk, The Netherlands In the next decade, SpaceWire-enabled missions SpaceWire has gained such a wide acceptance because will be monitoring our planet, exploring the distant it solved a significant problem. It replaced the collection realms of our Solar system and reaching through of different data interfaces with a standard that worked space and time to help understand the origins of well enough to meet the requirements of many space the Universe. missions. The result of an extremely successful collaboration between The benefits gained by the widespread adoption of ESA, academia and space industry, involving spacecraft SpaceWire have gone far beyond the original aspirations engineers from around the world, SpaceWire is a standard of its creators. SpaceWire-enabled instrumentation is for high-speed links and networks used on spacecraft. being reused on new missions, standard sensors with SpaceWire is now being used widely in the space industry, SpaceWire interfaces are appearing in equipment supplier by all the major space agencies and, in particular, on many catalogues and many SpaceWire components and sub- current space missions of ESA, NASA and JAXA. systems are available. 28 www.esa.int European Space Agency | Bulletin 145 | February 2011 29 → What is SpaceWire? spacewire technology → As a data-handling network standard for use on spacecraft, It offers high-speed, low-power, simplicity, relatively low Since the SpaceWire standard was published (under connecting instruments, mass-memory and other on-board implementation cost and architectural flexibility, making the reference number ECSS-E-50-12A) by the European sub-systems, SpaceWire can be compared to Universal Serial it ideal for many space missions.
    [Show full text]
  • Comparison of Communication Architectures for Spacecraft Modular Avionics Systems D.A
    National Aeronautics and NASA/TM—2006–214431 Space Administration IS20 George C. Marshall Space Flight Center Marshall Space Flight Center, Alabama 35812 Comparison of Communication Architectures for Spacecraft Modular Avionics Systems D.A. Gwaltney and J.M. Briscoe Marshall Space Flight Center, Marshall Space Flight Center, Alabama June 2006 The NASA STI Program Office…in Profile Since its founding, NASA has been dedicated to • CONFERENCE PUBLICATION. Collected the advancement of aeronautics and space papers from scientific and technical conferences, science. The NASA Scientific and Technical symposia, seminars, or other meetings sponsored Information (STI) Program Office plays a key or cosponsored by NASA. part in helping NASA maintain this important role. • SPECIAL PUBLICATION. Scientific, technical, or historical information from NASA programs, The NASA STI Program Office is operated by projects, and mission, often concerned with Langley Research Center, the lead center for subjects having substantial public interest. NASA’s scientific and technical information. The NASA STI Program Office provides access to • TECHNICAL TRANSLATION. the NASA STI Database, the largest collection of English-language translations of foreign aeronautical and space science STI in the world. scientific and technical material pertinent to The Program Office is also NASA’s institutional NASA’s mission. mechanism for disseminating the results of its research and development activities. These results Specialized services that complement the STI are published by NASA in the NASA STI Report Program Office’s diverse offerings include creating Series, which includes the following report types: custom thesauri, building customized databases, organizing and publishing research results…even • TECHNICAL PUBLICATION. Reports of providing videos. completed research or a major significant phase of research that present the results of For more information about the NASA STI Program NASA programs and include extensive data Office, see the following: or theoretical analysis.
    [Show full text]
  • Design and Analysis of a Dynamic Spacewire Routing Protocol for Recongurable and Distributed On-Board Computing Systems
    Design and Analysis of a Dynamic SpaceWire Routing Protocol for Recongurable and Distributed On-Board Computing Systems Prem Kumar Hari Krishnan Space Engineering, master's level (120 credits) 2019 Luleå University of Technology Department of Computer Science, Electrical and Space Engineering Master Thesis Design and Analysis of a Dynamic SpaceWire Routing Protocol for Reconfigurable and Distributed On-Board Computing Systems Prem Kumar Hari Krishnan Master in Space Science and Technology SpaceMaster, 2017-19 Abstract Future spacecrafts will require more computational and processing power to keep up with the growing demand in requirements and complexity. ScOSA is the next generation on-board com- puter developed by the German Aerospace Centre (DLR). The main motivation behind ScOSA is to replace the conventional on-board computer with distributed and reconfigurable computing nodes which provides higher performance, reliability, availability and stability by using a com- bination of the COTS components and reliable computing processors that are space qualified. In the current ScOSA system reconfiguration and routing of data between nodes are based on a static decision graph. SpaceWire protocol is used to communicate between nodes to provide reliability. The focus of the thesis is to design and implement a dynamic routing protocol for ScOSA which can be used in future for not only communicating between the nodes but also for reconfiguration. SpaceWire IPC is a customized protocol developed by DLR to provide communication between the nodes in a distributed network and to support monitoring, management and reconfiguration services. The dynamic routing protocol proposed in this thesis is primarily derived from the monitoring mechanism used in the SpaceWire IPC.
    [Show full text]
  • Spacewire Handbook DRAFT - SVN Version 60 - April 10, 2013
    SpaceWire Handbook DRAFT - SVN version 60 - April 10, 2013 4Links Limited Suite E U 2 BletchleyPark Milton Keynes, MK3 6EB United Kingdom Copyright © 2013 4Links Limited. SpaceWire Handbook DRAFT - SVN version 60 - April 10, 2013 Foreword This Draft Handbook is 4Links Limited’sinitial contribution to the forthcoming ECSS SpaceWire Handbook. Change Log Date Version 29th June 2012 First draft issue 24th September 2012 Second draft issue 10th April 2013 Third draft issue Copyright © 2013 4Links Limited. 2 SpaceWire Handbook DRAFT - SVN version 60 - April 10, 2013 Table of Contents Title Page ......................... 1 Foreword . ........................ 2 Change Log ........................ 2 1. Introduction ....................... 6 1.1. Purpose ....................... 6 1.2. Scope ........................ 6 1.3. Acknowledgements . ................... 6 1.4. Document structure . ................... 7 2. Terms, definitions and abbreviations ............... 8 2.1. Terms and definitions from other documents ............ 8 2.2. Terms specific to the present handbook ............. 14 2.3. Abbreviated terms .................... 14 3. References ........................ 17 4. Introduction to SpaceWire .................. 18 4.1. Background and History .................. 18 4.1.1. 1960 -AModular Computer ............... 18 4.1.2. 1980 -System on Chip, Serial Interfaces . ........... 19 4.1.3. Transputer serial links in space ............... 20 4.1.4. Modularity ..................... 20 4.1.5. 1990+ Transputer links to IEEE-1355 ............ 20 4.1.6. IEEE-1355 and early SpaceWire in Space ........... 21 4.2. The current SpaceWire Standard ................ 21 4.2.1. Data-Strobe encoding . ................. 23 4.2.2. Low-levelflow-control . ................ 23 4.2.3. Packets . ..................... 23 4.2.4. Packet Routing .................... 24 4.2.5. Time Codes and their distribution . ............. 24 4.2.6. SpaceWire in comparison with other communication techniques ...
    [Show full text]
  • Deterministic Spacewire Networks
    University of Dundee DOCTOR OF PHILOSOPHY Deterministic SpaceWire Networks Gibson, David James Award date: 2017 Link to publication General rights Copyright and moral rights for the publications made accessible in the public portal are retained by the authors and/or other copyright owners and it is a condition of accessing publications that users recognise and abide by the legal requirements associated with these rights. • Users may download and print one copy of any publication from the public portal for the purpose of private study or research. • You may not further distribute the material or use it for any profit-making activity or commercial gain • You may freely distribute the URL identifying the publication in the public portal Take down policy If you believe that this document breaches copyright please contact us providing details, and we will remove access to the work immediately and investigate your claim. Download date: 24. Sep. 2021 Deterministic SpaceWire Networks David James Gibson Doctor of Philosophy University of Dundee October 2017 ii Table of Contents List of Figures ......................................................................................................... xiii List of Tables............................................................................................................ xix List of Acronyms ..................................................................................................... xxi Glossary .................................................................................................................
    [Show full text]
  • Electronic Format Submission URSI FG Matera
    SpaceWire ECSS-E50-12A International SpaceWire Seminar (ISWS 2003) 4-5 November 2003, ESTEC Noordwijk, The Netherlands Steve Parkes (1), Josep Rosello (2) (1) University of Dundee, Applied Computing, Dundee, DD1 4HN, Scotland, UK. Email:[email protected] (2) European Space Agency ESTEC, Noordwijk, The Netherlands Email: [email protected] ABSTRACT SpaceWire[1] is a communications network for use onboard spacecraft. It is designed to connect high data-rate sensors, large solid-state memories, processing units and the downlink telemetry subsystem providing an integrated onboard, data-handling network. SpaceWire links are serial, high-speed (2 Mbits/sec to 400 Mbits/sec), bi-directional, full- duplex, point-to-point data links which connect together SpaceWire equipment. Application information is sent along a SpaceWire link in discrete packets. Control and time information can also be sent along SpaceWire links. SpaceWire is defined in the European Cooperation for Space Standardization ECSS-E50-12A standard. SpaceWire is based on the “DS-DE” part of the IEEE-1355 standard [2] combined with the TIA/EIA-644 Low Voltage Differential Signalling (LVDS) standard [3]. Several problems with IEEE-1355 have been solved in the SpaceWire standard and connectors and cables suitable for space application are defined. The SpaceWire standard is divided into several protocol levels: ! Physical Level which provides connectors, cables and EMC specifications. ! Signal Level which defines signal encoding, voltage levels, noise margins and data rates. ! Character Level which specifies the data and control characters used to manage the flow of data across a link. ! Exchange Level which covers the protocol for link initialisation, flow control, fault detection and link restart.
    [Show full text]
  • Applied Dynamics Adds Spacewire Support to the Advantage Framework
    For Immediate Release: Applied Dynamics Adds SpaceWire Support to the ADvantage Framework September 26, 2017. Ann Arbor, Michigan. Applied Dynamics (ADI) today announced the addition of SpaceWire to the growing list of communication protocols supported by the ADvantage Framework. Support for this communication standard, widely used throughout the space industry, allows users to further leverage the power of the ADvantage Framework in their spacecraft and satellite real- time systems. About SpaceWire Originally utilized by the European Space Agency, SpaceWire communication networks are now used worldwide by national space agencies, including NASA, JAXA, and the RKA, in addition to wide use within the private space industry. Current NASA projects utilizing SpaceWire include the Mars Science Laboratory, the Lunar Reconnaissance Orbiter, the James Webb Space Telescope and many more. Based in part on the IEEE 1355 standard, the SpaceWire protocol has been designed specifically to meet the unique demands of operation in space. SpaceWire supports arbitrary network topologies, allowing for the design of highly fault-tolerant and robust networks. The use of Low Voltage Differential Signaling (LVDS) and a low number of logic gates allows SpaceWire networks to consume little power while still supporting bidirectional communication rates up to 400 Megabits per second. Many SpaceWire devices are available in radiation tolerant form factors. The adoption of the SpaceWire standard throughout the space industry has allowed data handling hardware to be reused by multiple missions, reducing costs and improving system reliability. About the ADvantage Framework The ADvantage Framework provides a real-time usability layer on top of Linux (and other real-time or non-real-time operating systems), and is used to manage data handling, execution of analytics algorithms, control algorithms, simulations, data acquisition, and a range of other real-time computational tasks.
    [Show full text]
  • Remote Memory Access in Embedded Networked Systems
    _________________6TH SEMINAR OF FINNISH-RUSSIAN UNIVERSITY COOPERATION IN TELECOMMUNICATIONS Remote Memory Access in Embedded Networked Systems V. Olenev, I. Korobkov, L. Koblyakova, F. Shutenko SUAI 190000, B.Morskaya 67, Saint_Petersburg, Russia [email protected], [email protected], [email protected], [email protected] Abstract Remote memory access is one of the important tasks in modern Embedded Networked Systems. Each developer of system has a vision of solution of the given task. In this paper the approach to solution the remote access to memory in standard SpaceWire by means of RMAP protocol is considered. The newest UniPro standard of data transfer has a similar problem. The solution of remote access to memory in UniPro can be different. In article it is offered to use RMAP protocol for these purposes. Also RMAP software and hardware implementation is presented here with some technical characteristics. Index Terms: Embedded Networked Systems, SpaceWire, RMAP, UniPro, MCK-01, SWIC. I. INTRODUCTION Modern Embedded Networked Systems are frequently consist of a considerable quantity of devices (nodes) allocated on different distances from each other. Nodes can be use as initiators or targets. It is necessary to configure the devices: to set the logic address, the routing table, a device operating mode and other parameters. It is also necessary for devices to communicate during the operating process, for example, to update the routing table at connection or disconnection of new devices, or write some information to memory of remote device, e.g. at transferring of useful data from one user to another. In most cases it could be done by using write and read commands in appropriate program- accessible components of the remote device (e.g.
    [Show full text]