ExoMars Rover Vehicle
|
|
- Scot Todd
- 6 years ago
- Views:
Transcription
1
2 Page: 2 of 21 PAGE INTENTIONALLY LEFT BLANK
3 Page: 3 of 21 TABLE OF CONTENTS 1 INTRODUCTION Purpose and Scope Priority of requirements Guidelines and Traceability DOCUMENTS Normative Documents Informative Documents TERMINOLOGY & SYSTEM DESCRIPTIONS Terms & Definitions Abbreviations Conventions Description of the System SpaceWire Interface Definition Physical Level Exchange Level Network Level Logical Address Use of RMAP RMAP commands supported RMAP command and reply fields Target SpaceWire Address field Target Logical Address field Protocol Identifier Instruction field Key Reply Address field Initiator Logical Address field Transaction Identifier field Extended Address field Address field Data Length field Header CRC field Data field Mask field Data CRC field Reply SpaceWire Address field Status field APPENDIX A: List of TBD's APPENDIX B: List of TBC's LIST OF TABLES Table 4.3-1: Logical Address Allocation Table 5.2-1: RMAP Keys LIST OF FIGURES Figure 3.4-1: Diagram showing Rover data links to the OBC... 9 Figure 3.4-2: Diagram showing nodes in the Rover SpaceWire network Figure 3.4-3: Illustration of Data acquisition request and send to OBC Processor Module... 11
4 Page: 4 of 21 INTENTIONALLY BLANK
5 Page: 5 of 21 1 INTRODUCTION 1.1 Purpose and Scope The document contains the requirements for the SpaceWire interfaces between instruments and the On Board Computer. It includes the use of the SpW RMAP protocol and details of the packet contents. This document supersedes the Rover SpaceWire ICD [EXM-RM-RQM-ASU-0041]. 1.2 Priority of requirements The priority of the requirement is indicated by the use of shall or "should as follows: Priority Meaning Description shall Mandatory Mandatory requirements, or hard requirements, which must be implemented. They constitute core requirements of the project in order to fulfil the mission objectives should Goal These requirements are aiming at improving the performances or outcome of the mission. They may be eventually be re-negotiated if their implementation would be demonstrated to be conflicting with the implementation of a mandatory requirement, or overall programmatic constraints. 1.3 Guidelines and Traceability Traceability of these requirements from Rover Level will be maintained using the DOORS system. Requirements within this document are shown in an italic font. Each requirement is preceded by a summary line that contains the following fields, delimited by "/". Doors Requirement Number Intended Verification Method The Doors Requirement Number has the form RV-SPW-xxxx where xxxx is a unique number assigned consecutively. Traceability back to a parent requirement is shown following the DOORS Requirement Number The Intended Verification Method codes are as follows: R - Review - review of design (usually as part of a design review - i.e. reviewing the documentation supplied as part of a datapack). A - Analysis - detailed analysis showing that the equipment satisfies the specified requirement. I - Inspection - visual inspection or a single measurement. e.g. physical feature or a single measurement; mass, dimension verifies that the requirement is satisfied. T - Test - a test or series of tests to demonstrate that the equipment/subsystem meets a performance requirement or survives and/or operates in a particular environment. The requirement text follows the summary line. If tables are considered as part of requirement they are referenced clearly in the text and inserted after and separated from the requirement and are managed as free text attached to the identifier requirement. All document elements not presented in the format explained above are not requirements and will not be verified or tracked.
6 Page: 6 of 21 2 DOCUMENTS 2.1 Normative Documents Normative References are directly applicable in their entirety to this document and are listed below. The applicability is referred to the latest issue available. In case of conflict between a Normative Document and this document the contractor shall inform Astrium for resolution. [NR 01] SpaceWire - Links, nodes, routers and networks ECSS-E-ST-50-12C [NR 02] SpaceWire - Remote memory access protocol ECSS-E-ST-50-52C 2.2 Informative Documents Informative references are applicable to this document only when specifically called up in the text with specific indications of the part of the document that are to be applicable. Otherwise the documents are listed below for information only as an aid for the purpose of understanding. None
7 Page: 7 of 21 3 TERMINOLOGY & SYSTEM DESCRIPTIONS 3.1 Terms & Definitions Instrument This term is used to describe all SpaceWire nodes external to the OBC. This includes payload and platform nodes. NavCam Navigation Stereo Bench Unit, situated on the top of the Mast. Stereo images from this unit are used for generating a DEM of the terrain. LocCam PanCam MicrOmega CLUPI On Board Computer Processor Module Co-Processor Module Navigation Localisation Digital Elevation Map (DEM) Localisation Stereo Bench Unit, mounted on the front of the Rover at the base of the Mast. Stereo images from this unit are used to track the progress of the Rover over a planned path. Panoramic Camera System. An instrument comprising two wide-angle cameras and one high resolution camera. Mounted on the mast. Used to visually characterise the Rover's environment and its geology. Also very important for scientific target selection. Infrared microscope. Used to visually examine the collected sample looking for morphological evidence of life-related processes. Close-up Imager. A robotic replacement for the hand lens. Mounted on the bottom end of the Drill case. Used to visually examine surface rocks at close proximity. Also, to image the fines being produced when drilling. Central control computer of the Rover. It provides the processing platform for Rover control, Payload control and non-volatile data storage. Primary processor of the On Board Computer. The software running on this processor is responsible for all thermal control, power control, data handling and mechanism control. Secondary processor of the On Board Computer. It is dedicated to running processor-intensive image processing algorithms that are used for Navigation and Localisation. Calculation of a DEM from stereo NavCam images of the surrounding terrain and then planning a path to the target destination avoiding any obstacles in the way. Estimation of Rover location and orientation by comparison of successive stereo LocCam images taken whilst moving. Specifies a height (z value) for each ( x, y ) location on a grid. Referred to as 2.5D as overhangs cannot be represented. 3.2 Abbreviations Abbreviation CRC DEM DH DHS EGSE FDIR FIFO FOV HK Meaning Cyclic Redundancy Check Digital Elevation Map Data Handling Data Handling System Electrical Ground Support Equipment Failure Detection, Isolation and Recovery First In First Out Field Of View Housekeeping
8 Page: 8 of 21 Abbreviation HKTM HW (H/W) ICD IR IRD LSB LVDS MSB NR OBC RAM RD RM RMAP ROV or RV SOW SpW SW (S/W) TBC TBD TBW TM/TC Meaning Housekeeping Telemetry HardWare Interface Control Document Informative Reference (Reference Document) Interface Requirement Document Least Significant Bit Low Voltage Differential Signalling Most Significant Bit Normative Reference (Applicable Document) On Board Computer Random Access Memory Reference Document Rover Module Remote Memory Access Protocol (SpW) Rover Statement Of Work SpaceWire SoftWare To Be Confirmed To Be Defined To Be Written TeleMetry /TeleCommand 3.3 Conventions In this document hexadecimal numbers are written with the prefix 0x, for example 0x34 and 0xDF15. Binary numbers are written with the prefix 0b, for example 0b and 0b01. Decimal numbers have no prefix. 3.4 Description of the System The OBC is connected to several instruments (payload cameras and microscopes as well as navigation and localisation camera units). The instruments are connected to the OBC via non-redundant SpW links.
9 Page: 9 of 21 Figure 3.4-1: Diagram showing Rover data links to the OBC whole or in part be reproduced, copied, or communicated to any person without written permission from the owner.
10 Page: 10 of 21 The OBC contains two interconnected SpW routers that connect the Processor Module (PM) and the Co- Processor (CoPM) to each of the SpW equipment. The OBC uses logical addressing. Figure 3.4-2: Diagram showing nodes in the Rover SpaceWire network RMAP write commands are used: by the PM to send configuration and data acquisition commands to instruments. RMAP read commands are used: to read-back configuration data to the OBC Processing Module. to read-back stored acquisition data to the OBC Processing Module. to read-back housekeeping data to the OBC Processing Module. Figure indicates the flow of SpaceWire commands to take an image send the data back to the OBC. It is drawn from the point of view of a single instrument supplier and hence does not show all the instruments. This does not define the architecture of the OBC and does not include redundancy. Any configuration commands that may be required prior to data acquisition commands are not included. Also any commands internal to the OBC are not shown.
11 Page: 11 of 21 Figure 3.4-3: Illustration of Data acquisition request and send to OBC Processor Module
12 Page: 12 of 21 4 SPACEWIRE INTERFACE DEFINITION RV-SPW-468 / ROV-2357 / R All SpaceWire interfaces shall be compliant with [NR 01]. Terminology used in this section is defined in [NR 01]. 4.1 Physical Level RV-SPW-467 / CREATED / T All SpaceWire interfaces shall operate at a data rate of 100 Mbit/s (TBC). RV-SPW-801 / ROV-2357 / R All SpaceWire interfaces shall use 3.3V LVDS transceivers. 4.2 Exchange Level RV-SPW-434 / CREATED / R For each SpW link between OBC and instrument, the transceiver on the instrument shall be set to auto_start mode. Note: The exception is the OBC EGSE link where the OBC transceiver is set to auto_start mode. RV-SPW-435 / CREATED / R For each SpW link between OBC and instrument, the transceiver on the OBC shall be set to link_start mode. Note: The exception is the OBC EGSE link where the EGSE transceiver is set to link_start mode. It is always the OBC that initiates the sending of NULL characters to move the SpW transceiver state machines from Ready to Started. 4.3 Network Level RV-SPW-892 / CREATED / T,R All nodes on the Rover SpaceWire network shall use logical addressing Logical Address RV-SPW-824 / CREATED / T The Logical Address of each node in the Rover SpaceWire network shall be allocated as shown in Table (TBC)
13 Page: 13 of 21 Equipment / Unit Logical Address OBC Initiator Nodes Active PM CoPM OBC EGSE 0x21 0x22 0x24 Platform Target Nodes NavCam Front LocCam Rear LocCam Sun Sensor Spare Router A Spare Router B 0x30 0x33 0x35 0x36 0x39 0x3C Payload Target Nodes PanCam MicrOmega CLUPI LMC 0x41 0x42 0x44 0x46 Table 4.3-1: Logical Address Allocation
14 Page: 14 of 21 5 USE OF RMAP The Remote Memory Access Protocol (RMAP) will be used as the communication protocol on the Rover SpaceWire network. RMAP Write Commands are used for all data acquisition and configuration commands. This includes commands that are not logically memory writes e.g. "Take picture" commands to cameras. RMAP Read Commands are used to read instrument data and, if applicable, configuration and housekeeping data. RV-SPW-925 / CREATED / R All SpaceWire nodes shall be compliant with [NR 02]. 5.1 RMAP commands supported RV-SPW-470 / CREATED / R The SpaceWire interfaces shall support RMAP Write Commands (Logical Addressing) from OBC to instrument. RV-SPW-471 / CREATED / R The SpaceWire interfaces shall support RMAP Write Replies (Logical Addressing) from instrument to the OBC. RV-SPW-474 / CREATED / R The SpaceWire interfaces shall support RMAP Read Commands (Logical addressing) from OBC to instrument. RV-SPW-475 / CREATED / R The SpaceWire interfaces shall support RMAP Read Replies (Logical addressing) from instrument to OBC. 5.2 RMAP command and reply fields This section describes header field usage common to all OBC external SpW interfaces. These header fields are as described in [NR 02] Target SpaceWire Address field RV-SPW-807 / CREATED / T,R The target SpaceWire address field shall have zero bytes as the Rover SpaceWire network uses logical addressing Target Logical Address field The use of the Target Logical Address field is described in [NR 02] Protocol Identifier RV-SPW-484 / CREATED / T The Protocol Identifier shall be set to 0x01 in all cases (indicating RMAP).
15 Page: 15 of Instruction field Packet type field The use of the packet type field is described in [NR 02] Command field Write/Read bit The use of the Write/Read bit is described in [NR 02] Verify bit RV-SPW-512 / CREATED / T Write Commands to the instruments shall support verification (TBC) (verify bit set to '1'). Note: The supplier must identify any constraints when using verification. This bit is only used for RMAP Write Commands Reply bit The use of the Reply bit is described in [NR 02]. Write Command acknowledgements are referred to in [NR 02] as Write replies. RV-SPW-800 / CREATED / T,R All instruments shall provide Write replies when Reply bit is set to '1' Increment bit RV-SPW-715 / CREATED / R The use of the increment bit on all Write Commands and Read Commands to the instruments from the OBC shall be determined by the instrument supplier for each instrument. The only time when an increment bit is set to not increment ('0') is when interfacing to a FIFO Reply Address length field RV-SPW-813 / CREATED / T,R The Reply Address length field shall be set to 0b Key RV-SPW-486 / CREATED / T Keys shall be allocated as shown in Table
16 Page: 16 of 21 Equipment / Unit Key OBC Modules Processor Module (PM) Co-Processor Module (CoPM) OBC EGSE interface 0x11 0x12 0x13 Platform Instruments NavCam Front LocCam Rear LocCam Sun Sensor 0x21 0x22 0x23 0x24 Payload Instruments PanCam MicrOmega CLUPI 0x31 0x32 0x33 Table 5.2-1: RMAP Keys Any Nominal / Redundant instances of a given function have the same key. Distinct keys are intended to detect routing errors particularly when multi-stage routing is required, which is not the case here. It is also less useful when no write acknowledgement is requested. They are included here to comply with the RMAP protocol Reply Address field RV-SPW-818 / CREATED / T,R The target Reply Address field shall have zero bytes as the Rover SpaceWire network uses logical addressing Initiator Logical Address field The Initiator Logical Address field will be set by one of the initiator nodes and the value of the field will be one of those specified in the OBC Initiator Nodes section of Table Transaction Identifier field The transaction identifier is only useful when a reply is requested, since this reply will then contain the same transaction identifier and can be identified by the initiator Extended Address field Extended memory addresses may be requested by the instrument supplier Address field RV-SPW-916 / CREATED / R The range of memory addresses that can be addressed in a RMAP Write Command or RMAP Read Command shall be defined by the instrument supplier.
17 Page: 17 of Data Length field The Data Length field will be specific to each instrument and will depend on the requirements of each instrument Header CRC field The use of the Header CRC field is described in [NR 02] Data field The format of the data field will be specific to each instrument and will depend on the requirements of each instrument Mask field The Mask field and the RMAP Read-Modify-Write Command are not used on the Rover SpaceWire network Data CRC field The use of the Data CRC field is described in [NR 02] Reply SpaceWire Address field RV-SPW-922 / CREATED / T,R The Reply SpaceWire Address field shall have zero bytes as the Rover SpaceWire network uses logical addressing Status field The use of the Status field is described in [NR 02].
18 Page: 18 of 21 6 APPENDIX A: LIST OF TBD'S There are no TBD s.
19 Page: 19 of 21 7 APPENDIX B: LIST OF TBC'S TBC-01 TBC-02 TBC-03 RV-SPW-467 RV-SPW-512 RV-SPW-824
20 Page: 20 of 21 Requirement/Section Cross Reference Page numbers are the pages where the sections start RV-SPW RV-SPW RV-SPW RV-SPW RV-SPW RV-SPW RV-SPW RV-SPW RV-SPW RV-SPW RV-SPW RV-SPW RV-SPW RV-SPW RV-SPW RV-SPW RV-SPW RV-SPW RV-SPW RV-SPW RV-SPW RV-SPW
21 Page: 21 of 21 DOCUMENT CHANGE DETAILS ISSUE CHANGE AUTHORITY CLASS RELEVANT INFORMATION/INSTRUCTIONS A First Issue B Updates to logical address allocations DISTRIBUTION LIST INTERNAL EXTERNAL ASU: Rover Team TAS-I: P. Fissore (Configuration Management) F. Ravera P. Elia Configuration Management Library ESA: M. Clissold (Configuration Management) P. Baglioni A. Winton Astrium Ltd owns the copyright of this document which is supplied in confidence and which shall not be used for any purpose other than that for which it is supplied and shall not in
6 Remote memory access protocol (normative)
6 Remote memory access protocol (normative) 6.1 General 6.1.1 Purpose The remote memory access protocol (RMAP) has been designed to support a wide range of SpaceWire applications. Its primary purpose however
More informationSpace engineering. SpaceWire Protocols
Space engineering SpaceWire Protocols This ECSS is a draft standard circulated for xxxxxxxxxx. It is therefore subject to change without notice and may not be referred to as an ECSS Standard until published
More informationLISA Pathfinder Sheet : 1
Pathfinder Sheet : 1 Issue : A Date : 7.3.5 Inputs to LISA Pathfinder Space-Ground Interface Document (SGICD) - Part 2, Baseband. CI CODE: 1240000 Prepared by: Date: Robin Ashencaen Checked by: Date: Kevin
More informationSystem Approach for a SpaceWire Network Template reference : C-EN
System Approach for a SpaceWire Network Template reference : 100181700C-EN Prepared by Stephane DETHEVE / Bruno MASSON PLAN Page 2 SYSTEM APPROACH FOR A SPACEWIRE NETWORK INTRODUCTION SIMULATION BREADBOARDING
More informationSpaceWire RMAP Protocol
SpaceWire RMAP Protocol SpaceWire Working Group Meeting Steve Parkes University of Dundee Aims of RMAP Remote Memory Access Protocol Provide a means of Writing to Reading from Registers or memory on a
More informationRemote Memory Access in Embedded Networked Systems
Remote Memory Access in Embedded Networked Systems Valentin Olenev, I Korobkov, Liudmila Koblyakova, Felix Shutenko SUAI Introduction A Modern Embedded Networked Systems frequently consist of a large quantity
More informationSpaceWire Remote Memory Access Protocol
SpaceWire Remote Memory Access Protocol Steve Parkes and Chris McClements University of Dundee, Applied Computing, Dundee, DD1 4HN, Scotland, UK. sparkes@computing.dundee.ac.uk,, cmclements@computing.dundee.ac.uk.
More informationAeroflex Colorado Springs Application Note
Aeroflex Colorado Springs Application Note AN-SPW-005-001 Configuration of the UT200SpW4RTR Table 1: Cross Reference of Applicable Products Product Name: Manufacturer Part SMD # Device Internal PIC Number
More informationStandardisation of PF/PL interfaces TAS point of view
ADCSS-2014 workshop Day 3 ESTEC October 29, 2014 30/10/2014 Standardisation of PF/PL interfaces TAS point of view 83230352-DOC-TAS-EN-002 Ref.: Agenda For Proteus, H/P, Sentinel 3, Telecom, the following
More informationVideo Processing Chain VPC2 SpaceWire Networking Protocol Meeting July 2005
Video Processing Chain VPC2 SpaceWire Networking Protocol Meeting 4 19-20-21 July 2005 Page 1 Summary VPC2 and SPADA_RT Activity VPC2 Architecture Data Exchange VPC2 RMAP Implementation Issue FPGA Implementation
More informationSpaceWire RMAP Protocol
SpaceWire RMAP Protocol SpaceWire Working Group Meeting Steve Parkes University of Dundee RMAP Review Final review before ECSS Changes since last meeting/draft C Go through book section by section Review
More informationCoordinate Systems Specification
Page: 1 of 22 ExoMars Rover DRD: ENG-32 CI CODE: E211000300 Prepared by: N Silva GNC Architect Date: Checked by: A R Davies GNC Architect R Slade Mechanical Architect Date: Approved by: J Clemmet Engineering
More informationTowards SpaceWire Plug-And-Play ECSS Standard
Towards SpaceWire Plug-And-Play ECSS Standard David Jameux SpaceWire 2011, San Antonio (TX), USA 08/11/2011 Background 1. SpaceWire: a. initiated by ESA b. allows embarking high speed data networks on
More informationCGS User Group Meeting September, 19-20, Noordwijk
CGS User Group Meeting September, 19-20, 2000 - Noordwijk Packet Utilisation Standard with CGS by Thomas Kaufungen Thomas Schuler Astrium GmbH Earth Observation & Science Division Dept.: ED533 - Electrical
More informationSpaceNet - SpaceWire-RT. Initial Protocol Definition
SpaceNet - SpaceWire-RT Initial Revision: Draft A Issue 1.1 Date: 12 th May 2008 ESA Contract Number 220774-07-NL/LvH Ref: SpW-RT WP3-200.1 Space Technology Centre School of Computing University of Dundee
More informationSVF User Requirements Specification
LlSA Pathfinder S2.ASU RS 5030 I SVF User Requirements Specification CI CODE: 124 4200 UK EXPORT CONTROL RATING: Not Listed Rated By: T. Remion Prepared by: Barry McMahon & Thomas Remion Checked by: Dave..
More informationModeling Of Spacewire Traffic. - ESA study Contract No /10/NL/LvH. Executive Summary & Final Report
Modeling Of Spacewire Traffic - ESA study Contract No. 23037/10/NL/LvH Executive Summary & Final Report 2/25 Left Blank 3/25 OVERVIEW...5 CONTRACT EXECUTIVE SUMMARY...7 FINAL REPORT...10 1.1 Objectives...
More informationThe SOIS Plug-and-Play Architecture and Its Proposed Mapping onto SpaceWire
Distributed, Real- Time, Embedded Systems The SOIS Plug-and-Play Architecture and Its Proposed Mapping onto SpaceWire S.D. Fowell, SciSys Ltd, UK Presented by: Stuart D Fowell www.scisys.co.uk Overview
More informationINTERNAL THALES ALENIA SPACE STANDARD : DATE : CHANGE RECORDS. Paragraphs Change Record (List of paragraphs modified, new or deleted)
ISSUE : 01 PAGE : 2/10 CHANGE RECORDS Paragraphs Change Record (List of paragraphs modified, new or deleted) Issue Date Change Record Description Author Draft 17/09/10 First preliminary issue 01 First
More informationMOST (Modelling of SpaceWire Traffic): MTG-I simulation presentation
MOST (Modelling of SpaceWire Traffic): MTG-I simulation presentation PART 1 2 1 INTRODUCTION, HISTORY and CONTEXT MTG SpaceWire Network MOST presentation (1/5) 3 MOST (Modelling of SpaceWire Traffic) was
More informationREFERENCE: DATE : CHANGE RECORDS ISSUE DATE CHANGE RECORDS AUTHOR
REFERENCE: ISSUE : 02 Page : 2/156 CHANGE RECORDS ISSUE DATE CHANGE RECORDS AUTHOR 01 06/08/2014 First issue U. Di Tommaso 02 19/03/2015 Updated paragraphs 2.1, 3.2.2, 4.6.1 Removed paragraph 4.6.4 U.
More informationSpaceWire-R DRAFT. SCDHA Issue September 2013
SpaceWire-R DRAFT SCDHA 151-0.3 Issue 0.3 13 September 2013 Takahiro Yamada Japan Aerospace Exploration Agency (JAXA) Institute of Space and Astronautical Science (ISAS) 1 CONTENTS 1. INTRODUCTION... 3
More informationSpaceWire Backplane Application Requirements
SpaceWire Backplane Application Requirements Alan Senior 15 th December 2011 Classification Summary The work presented is part of the ESA funded SpaceWire Backplane activity reference TEC EPD/2010.88 The
More informationSpaceFibre Flight Software Workshop 2015
SpaceFibre Flight Software Workshop 2015 Steve Parkes, University of Dundee Albert Ferrer Florit, Alberto Gonzalez Villafranca, STAR-Dundee Ltd. David McLaren, Chris McClements, University of Dundee Contents
More informationThe SpaceWire-PnP Draft Standard. Peter Mendham Stuart Mills, Steve Parkes, Martin Kelly, Stuart Fowell
The SpaceWire-PnP Draft Standard Peter Mendham Stuart Mills, Steve Parkes, Martin Kelly, Stuart Fowell Agenda The draft standard Conceptual view of a network SpaceWire Network Management Architectural
More informationNetwork on Chip round table European Space Agency, ESTEC Noordwijk / The Netherlands 17 th and 18 th of September 2009
Network on Chip round table European Space Agency, ESTEC Noordwijk / The Netherlands 17 th and 18 th of September 2009 Ph. Armbruster Head of Data Systems Division European Space Agency - ESTEC 17 th of
More informationCONTROLLED DISTRIBUTION REFERENCE
ISSUE : 01 PAGE: 2/14 CHANGE RECORDS ISSUE DATE CHANGE RECORDS AUTHOR 01 26/05/09 First issue MS - PF ISSUE : 01 PAGE: 3/14 TABLE OF CONTENTS 1. PURPOSE... 4 2. DOCUMENTS... 5 2.1 Normative Documents...5
More informationProposed SOIS Plug-and-Play Architecture and Resulting Requirements on SpaceWire Mapping
Distributed, Real- Time, Embedded Systems Proposed SOIS Plug-and-Play Architecture and Resulting Requirements on SpaceWire Mapping, Dundee, UK Presented by: Stuart D Fowell www.scisys.co.uk Overview Existing
More informationMARC Mini-Project and SpaceWire-RT
Distributed, Real- Time, Embedded Systems MARC Mini-Project and SpaceWire-RT SpaceWire Working Group Meeting #12 17 th February 2009, ESTEC Presented by: Stuart D Fowell www.scisys.co.uk Proprietary Information
More informationSpaceWire Technologies deliver multi-gigabit data rates for on-board Spacecraft. SpaceTech Expo Gregor Cranston Business Development Manager
SpaceWire Technologies deliver multi-gigabit data rates for on-board Spacecraft SpaceTech Expo 2013 Gregor Cranston Business Development Manager 1 Introducing SpaceFibre A very high-speed serial data-link
More informationCRITICAL DESIGN REVIEW
STUDENTS SPACE ASSOCIATION THE FACULTY OF POWER AND AERONAUTICAL ENGINEERING WARSAW UNIVERSITY OF TECHNOLOGY CRITICAL DESIGN REVIEW November 2016 Issue no. 1 Changes Date Changes Pages/Section Responsible
More informationHerschel EGSE Packet Router ICD
Doc. no. : SRON-G//ICD/2001-001 Page : 1 of 14 Title Prepared by : Albrecht de Jonge Date : July 30, 2001 Oct 23, 2001 Agreed by : EGSE manager: L. Dubbeldam Date : ICC manager: P. Roelfsema PACS EGSE
More informationSTUP. SpaceWire Protocol
Page: 2 of 7 Table of Contents 1. INTRODUCTION... 4 1.1 LIST OF APPLICABLE DOCUMENTS... 4 1.2 LIST OF REFERENCE DOCUMENTS... 4 2. PROTOCOL DESCRIPTION... 5 2.1 INTRODUCTION... 5 2.2 PROTOCOL FORMAT...
More informationDesign of Satellite Telemetry Based on PUS under Limited Downlink Channel
International Conference on Manufacturing Science and Engineering (ICMSE 2015) Design of Satellite Telemetry Based on PUS under Limited Downlink Channel Yang LIUa*, Zongde LI, Xuejing DINGb and Yuanyuan
More informationHerschel EGSE Packet Router ICD
Page : 1 of 14 Title Prepared by : Albrecht de Jonge Date : Checked by : Date : Agreed by : : Date : PACS: SPIRE: HSC: Authorised by : Date : Page : 2 of 14 Distribution list Page : 3 of 14 Document Change
More informationSpaceNet - SpaceWire-T. Initial Protocol Definition
SpaceNet - SpaceWire-T Revision: Draft A Issue 3.1 Date: 24th August 2009 ESA Contract Number 220774-07-NL/LvH Ref: SpW-RT WP3-200.1 Space Technology Centre School of Computing University of Dundee Dundee,
More informationSWIFU: SPACEWIRE INTERFACE UNIT FOR VERSATILE SENSOR
SWIFU: SPACEWIRE INTERFACE UNIT FOR VERSATILE SENSOR INTEGRATION ON THE EXOMARS CHASSIS BREADBOARD Session: Spacewire Missions and Applications Short Paper Lee C. G.-Y., Obstei R. von Hoerner & Sulger
More informationImplimentation of SpaceWire Standard in SpaceWire CODEC using VHDL
International Journal of Engineering Research and Development e-issn: 2278-067X, p-issn: 2278-800X, www.ijerd.com Volume 9, Issue 2 (November 2013), PP. 36-40 Implimentation of SpaceWire Standard in SpaceWire
More informationMeteosat Second Generation Interface Control Document Station Key Unit
Issue: 11 Interface Control Document Station Key Unit Document Signature Table Issue: 11 Document Signature Table Name Function Signature Date Prepared by Niklas Sinander Telecommunications Engineer Checked
More informationestec SVM Electrical Simulator Requirement Specification
estec European Space Research and Technology Centre Keplerlaan 1 2201 AZ Noordwijk The Netherlands T +31 (0)71 565 6565 F +31 (0)71 565 6040 www.esa.int SVM Electrical Simulator Requirement Specification
More informationRemote Memory Access in Embedded Networked Systems
Remote Memory Access in Embedded Networked Systems V. Olenev, I. Korobkov, L. Koblyakova, F. Shutenko SUAI 190000, B.Morskaya 67, Saint_Petersburg, Russia valentin.olenev@guap.ru, zelwa@yandex.ru, Luda_o@rambler.ru,
More informationESA-EOP needs for SpaceFibre
ESA-EOP needs for SpaceFibre Prepared by: Josep Roselló, ESA/ESTEC/EOP-SFT (Technology Coord. & Frequency Mngt Section, EO Future Missions Division) Earth Observation Programme (EOP) Directorate @ ESA/ESTEC
More informationSpaceWire-RT. SpaceWire-RT Status SpaceWire-RT IP Core ASIC Feasibility SpaceWire-RT Copper Line Transceivers
SpaceWire-RT SpaceWire-RT Status SpaceWire-RT IP Core ASIC Feasibility SpaceWire-RT Copper Line Transceivers 1 Overview of SpaceWire-RT Project Aims The SpaceWire-RT research programme aims to: Conceive
More informationScalable Sensor Data Processor Development Status DSP Day - September 2014
Scalable Sensor Data Processor Development Status DSP Day - September 2014 83230347-DOC-TAS-EN-003 Presentation of the SSDP ASIC Program & Context SSDP will be the first Space Qualified European multi-core
More informationEXOMARS ROVER VEHICLE MOBILITY FUNCTIONAL ARCHITECTURE AND KEY DESIGN DRIVERS
EOMARS ROVER VEHICLE MOBILITY FUNCTIONAL ARCHITECTURE AND KEY DESIGN DRIVERS Nuno Silva (1), Richard Lancaster (2), Jim Clemmet (3) (1) Astrium Ltd, Gunnels Wood Road Stevenage - SG1 2AS - UK, Email: nuno.silva@astrium.eads.net
More information1 COMMAND AND DATA HANDLING (C&DH)
1 COMMAND AND DATA HANDLING (C&DH) 1.1 Requirements and Design Drivers 1.1.1 Functional The command and data handling shall provide the capability to: Transfer information in digital or discrete representation
More informationAdvanced Validation Strategies for On-Board Satellite Software in the Galileo IOV Programme
Olivier Croatto, Michael Uemminghaus Garching, Oct. 7th, 2008 Advanced Validation Strategies for On-Board Satellite Software in the Galileo IOV Programme Astrium Proprietary Information Agenda 1 - Overview
More informationSpaceWire-RT Project and Baseline Concepts
SpaceWire-RT Project and Baseline Concepts Steve Parkes, Albert Ferrer Space Technology Centre, University of Dundee Yuriy Sheynin, St Petersburg University of Aerospace Instrumentation 1 Aims Overview
More informationUNIVERSAL SPACEWIRE INTERFACE TO/FROM VME AND TO/FROM PCI
UNIVERSAL SPACEWIRE INTERFACE TO/FROM VME AND TO/FROM PCI Session: Poster Session Short Paper ir. G.J. Vollmuller, ing. A. Pleijsier National Aerospace Laboratory NLR Anthony Fokkerweg 2, 1059CM, Amsterdam
More informationCOTS Commercial is not always advertising Monica Alderighi
COTS Commercial is not always advertising Monica Alderighi Astro-Siesta, 30/01/2014 M. Alderigh, Astro-Siesta, 30/01/2014 1 COTS - Definition By Commercial Off-The-Shelf (COTS) is meant software or hardware
More informationSpaceWire ECSS-E50-12A International SpaceWire Seminar (ISWS 2003)
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,
More informationOn-Board Control Procedures: Autonomous and Updateable Spacecraft Operator Onboard and Beyond
On-Board Control Procedures: Autonomous and Updateable Spacecraft Operator Onboard and Beyond Marek Prochazka / Kjeld Hjortnaes European Space Agency, ESTEC, Software Systems Division. FSW-10, Pasadena
More informationTAS RTU PRODUCTS. ADCSS 2015 Noordwijk. Thales Alenia Space 23/10/2015. Ref.: DOC-TAS-EN-001
TAS RTU PRODUCTS ADCSS 2015 Noordwijk 83230356-DOC-TAS-EN-001 TAS PRODUCTS & DEVELOPMENT 83230356-DOC-TAS-EN-001 TAS-BELGIUM HIGH POWER AVIONICS Development programme underway under ARTES R&D Modular PLDIU
More informationOn-Board Data Systems
On-Board Data Systems Ph. Armbruster TEC-ED Email: philippe.armbruster@esa.int Slide : 1 Avionics for multi-mission platforms, hard Facts Avionics take an important share of the platform cost Many building
More informationHigh Accuracy Time Synchronization over SpaceWire Networks
High Accuracy Time Synchronization over SpaceWire Networks Final Report SPWCUC-REP-0004 Version 1.0 18 December 2013 i Final Report ESTEC Contract 400105931 EUROPEAN SPACE AGENCY CONTRACT REPORT The work
More informationCitation for published version (APA): Bhanderi, D. (2001). ACS Rømer Algorithms Verification and Validation. RØMER.
Aalborg Universitet ACS Rømer Algorithms Verification and Validation Bhanderi, Dan Publication date: 2001 Document Version Publisher's PDF, also known as Version of record Link to publication from Aalborg
More informationPage 1 SPACEWIRE SEMINAR 4/5 NOVEMBER 2003 JF COLDEFY / C HONVAULT
Page 1 SPACEWIRE SEMINAR 4/5 NOVEMBER 2003 JF COLDEFY / C HONVAULT INTRODUCTION The SW IP was developped in the frame of the ESA 13345/#3 contract "Building block for System on a Chip" This presentation
More informationPatching Flight Software on Mars
Patching Flight Software on Mars Ed Benowitz / Mark Maimone MSL Flight Software Developers NASA/Jet Propulsion Laboratory California Institute of Technology Copyright 2015 California Institute of Technology.
More informationSpaceWire Router ASIC
SpaceWire Router ASIC Steve Parkes, Chris McClements Space Technology Centre, University of Dundee Gerald Kempf, Christian Toegel Austrian Aerospace Stephan Fisher Astrium GmbH Pierre Fabry, Agustin Leon
More informationThe SpaceWire RTC: Remote Terminal Controller
SpaceWire-SnP Working Group ESTEC, Sept 15 th, 2004 The : Remote Terminal Controller Data Systems Division luca.tunesi@esa.int ESTEC, Sept 15 th, 2004 slide: 1 Background: the OPDPS Low/Med. Speed Bus:CAN
More informationS5p INTENTIONALLY BLANK
S5P.IRD.ASU.SC.00001 Page 2 of 106 INTENTIONALLY BLANK S5P.IRD.ASU.SC.00001 Page 3 of 106 CONTENTS 1. INTRODUCTION...6 1.1 Purpose...6 1.2 Acronyms List...6 2. DOCUMENTS...7 2.1 Applicable Documents...7
More informationSPACEWIRE DRIVEN ARCHITECTURE FOR THE ASTRO-H SATELLITE
SPACEWIRE DRIVEN ARCHITECTURE FOR THE ASTRO-H SATELLITE Session: SpaceWire missions and applications Long Paper Masanobu Ozaki, Tadayuki Takahashi, Motohide Kokubun, Takeshi Takashima, Hirokazu Odaka Institute
More informationOBC Mass Memories Final Presentation
OBC Mass Memories Final Presentation Patrik Sandin, Chief Engineer, Digital Product Unit, AB Dietmar Walter, Hardware Group, DSI-IT GmbH Glenn Johnson, Onboard Software Group, SCISYS UK Ltd ESA Contract
More informationSpacecraft Monitoring & Control Systems
Spacecraft Monitoring & Control Systems TSC & CCS - Presentation, May 2015 http://ccs.terma.com SATELLITE CHECKOUT & OPERATIONS SCOE TSC P/L EGSE CCS Unified Monitoring & Control data model procedures
More informationRapidIO Interconnect Specification Part 3: Common Transport Specification
RapidIO Interconnect Specification Part 3: Common Transport Specification Rev. 1.3, 06/2005 Copyright RapidIO Trade Association RapidIO Trade Association Revision History Revision Description Date 1.1
More informationfor On-Board Communications Project Status Noordwijk, Netherlands
Protocol Validation System for On-Board Communications Project Status 13th S Wi W ki G M ti 14th 15th S t b 2009 13th SpaceWire Working Group Meeting, 14th-15th September 2009 Noordwijk, Netherlands Presentation
More informationAdvanced On-board Control Procedure
1 Overview The Advanced On-Board Control Procedure (AOBCP) product is one of a set of technologies that allows to implement cost effective operation and control of a spacecraft. Together these technologies
More informationFPU-16 A-B PROTOCOL/DATA LOGGER MANUAL
FPU-6 A-B PROTOCOL/DATA LOGGER MANUAL FEBRUARY 26, 22 PRELIMINARY Copyright 22 by Startco Engineering Ltd. All rights reserved. Publication: FPU-6-AB-M Document: S95-F6-AB Printed in Canada. Startco Engineering
More informationEagleEye TSP Porting to HWIL Configuration (RTB)
EagleEye TSP Porting to HWIL Configuration (RTB) Final project presentation 12.12.2017 Presenter: Dharma Teja Srungavruksham Overview_ Background Team Goals Execution Results Future Background_ EagleEye
More informationSpaceWire 101. Webex Seminar. February 15th, 2006
SpaceWire 101 Webex Seminar February 15th, 2006 www.aeroflex.com/spacewire SpaceWire 101 What is SpaceWire Protocol, Links, Basic Communication Architecture Physical Layer Interface and Network Components
More informationMETOP Direct Broadcast Satellite to Ground Interface details for HRPT users
METOP Direct Broadcast Satellite to Ground Interface details for HRPT users Regional Advanced Retransmission Service (RARS) L band acquisition data 1 Go to View menu and click on Slide Master to update
More informationOPEN BASE STATION ARCHITECTURE INITIATIVE
OPEN BASE STATION ARCHITECTURE INITIATIVE Conformance Test Cases Appendix C RP interface and TM module Version.00 Issue.00 (4) FOREWORD OBSAI description and specification documents are developed within
More informationDATA ITEM DESCRIPTION
helping projects succeed... DATA ITEM DESCRIPTION 1. TITLE VERIFICATION REQUIREMENTS SPECIFICATION (VRS) 2. Identification Number PPA-003914-7 17 August 2017 3. DESCRIPTION/PURPOSE OF THE VRS 3.1 The Verification
More informationAnalysis of the Transport Protocol Requirements for the SpaceWire On-board Networks of Spacecrafts
Analysis of the Transport Protocol Requirements for the SpaceWire On-board Networks of Spacecrafts Irina Lavrovskaya, Valentin Olenev, Ilya Korobkov Saint-Petersburg State University of Aerospace Instrumentation
More informationSpaceFibre IP Core, Alpha Test Programme, and Planned SpaceFibre Contracts
SpaceFibre IP Core, Alpha Test Programme, and Planned SpaceFibre Contracts Steve Parkes 1, Martin Suess 2 1 Space Technology Centre, University of Dundee, UK 2 ESA, ESTEC 1 Contents SpaceFibre IP Core
More informationCubeSense. An integrated sun and nadir sensor module. Interface Control Document
CubeSense An integrated sun and nadir sensor module Interface Control Document Page: 2 Table of Contents List of Acronyms/Abbreviations... 3 1. Introduction... 4 2. Specifications... 5 3. Electrical Interface...
More informationSCOS-2000 OBSM External Interfaces Control Document
ESA/OPS-GIC SCOS-2000 OBSM External Interfaces Control Document Document Reference: EGOS-MCS-S2K-ICD-0014 Document Status: Version 1.4 Prepared By: SCOS-2000 Team SCOS-2000 OBSM External Interfaces ICD
More informationRPWI Software Design SWEDISH INSTITUTE OF SPACE PHYSICS. Reine Gill
RPWI Software Design SWEDISH INSTITUTE OF SPACE PHYSICS Reine Gill 2012-05-08 Software Environment (Design A, Design B) - Dataflows (Instruments, Spacecraft TM/TC) - Signals (Clocks, Interrupts, Pulse
More informationestec GS input to on-board data architecture Prepared by Michele Zundo Reference PE-TN-ESA-GS-405 Issue 1 Revision 3 Date of Issue
estec Keplerlaan 1, 2200 AG Noordwik. The Netherlands +31-71-5656565 PE-TN-ESA-GS-405 GS inputs to on-board data architecture v1_3.docx Prepared by Michele Zundo Reference PE-TN-ESA-GS-405 Issue 1 Revision
More informationSpacewire related activities in JAXA & science community ~Summary~
Working Group Meeting (July 19-20, 2005) Spacewire related activities in JAXA & science community ~Summary~ Y. Kasaba, T. Takashima (ISAS/JAXA) JAXA/BepiColombo Project Office T. Takahashi, M. Ozaki (ISAS/JAXA)
More informationSURVEILLANCE DATA EXCHANGE
EUROPEAN ORGANISATION FOR THE SAFETY OF AIR NAVIGATION EUROCONTROL EUROCONTROL STANDARD DOCUMENT FOR SURVEILLANCE DATA EXCHANGE Part 15: Category 65 SUR.ET1.ST05.2000-STD-15-01 Edition : 1.2 Edition Date
More informationSpaceFibre Specification Draft F3
SpaceFibre Specification Draft F3 LIKELY TO CHANGE! Authors: Steve Parkes Albert Ferrer Alberto Gonzalez Chris McClements Copyright 2013 University of Dundee This page is blank intentionally. 2 Change
More informationDevelopment an update. Aeroflex Gaisler
European SpaceWire Router Development an update Sandi Habinc Aeroflex Gaisler Demand for SpaceWire Router Both European and international customers have shown interest in SpaceWire router with greater
More informationFeliCa Card User's Manual Excerpted Edition
Technical Document FeliCa Card User's Manual Excerpted Edition Version 2.0 No. M617-E02-00 Introduction This document describes the protocol specifications and the command specifications of any contactless
More informationSURVEILLANCE DATA EXCHANGE
EUROPEAN ORGANISATION FOR THE SAFETY OF AIR NAVIGATION EUROCONTROL EUROCONTROL STANDARD DOCUMENT FOR SURVEILLANCE DATA EXCHANGE Part 10: Category 63 SUR.ET1.ST05.2000-STD-10-01 Edition : 1.3 Edition Date
More informationMega Menu Add-on User Guide
Mega Menu Add-on User Guide A guide to using the Mega Menu add-on interface Last updated: February 7, 2018 Version: 1.0 2017-2018 Cybage. All rights reserved. The information contained in this document
More informationElectrical Ground Support Equipment (EGSE) and
Electrical Ground Support Equipment (EGSE) Specialised Spacecraft Check-Out Systems TELETEL, founded in 1995, is a private Greek software and hardware, design and development company with a long history
More informationLunar Reconnaissance Orbiter (LRO)
Lunar Reconnaissance Orbiter (LRO) CRaTER Technical Interchange Meeting C&DH Flight Software April 14, 2005 1 C&DH Software Overview Command and Data Handling (C&DH) includes the following functions: Decoding
More informationSpaceWire Router - Status
Router - Status Working Group Meeting Dr. Stephan Fischer Dr. Steve Parkes Gerald Kempf Pierre Fabry EADS Astrium GmbH University of Dundee Austrian Aerospace GmbH ESA ESA, Noordwijk 15. Sep. 004 Outline
More informationIBM Rational Rhapsody Gateway Add On. Customization Guide
Customization Guide Rhapsody IBM Rational Rhapsody Gateway Add On Customization Guide License Agreement No part of this publication may be reproduced, transmitted, stored in a retrieval system, nor translated
More informationINTERFACE CONTROL DOCUMENT
STUDENTS SPACE ASSOCIATION THE FACULTY OF POWER AND AERONAUTICAL ENGINEERING WARSAW UNIVERSITY OF TECHNOLOGY INTERFACE CONTROL DOCUMENT November 2016 Issue no. 2 (March 2017) Changes Date Changes Pages/Section
More informationPart 3: Applications
Provläsningsexemplar / Preview INTERNATIONAL STANDARD ISO 14223-3 First edition 2018-02 Radiofrequency identification of animals Advanced transponders Part 3: Applications Identification des animaux par
More informationA Issue A Original. Instruction Manual. nxds Serial Comms Interface
Instruction Manual A735-01-860 Issue A Original nxds Serial Comms Interface Description nxds6i nxds10i nxds15i nxds20i Item Number A735-01-983 A736-01-983 A737-01-983 A738-01-983 nxds6ic nxds10ic nxds15ic
More informationWELL CONNECTED. The SpaceWire on-board data-handling network
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,
More informationSURVEILLANCE DATA EXCHANGE
EUROPEAN ORGANISATION FOR THE SAFETY OF AIR NAVIGATION EUROCONTROL EUROCONTROL STANDARD DOCUMENT FOR SURVEILLANCE DATA EXCHANGE Part 10: Category 63 SUR.ET1.ST05.2000-STD-10-01 Edition : 0.21 Edition Date
More informationElectrical Ground Support Equipment Verification Test Support. EGSE Verification Test Support
Electrical Ground Support Equipment Verification Test Support Tom Leisgang Orbital Network Engineering tleisgang@orbitalnetwork.com T. Leisgang 1 EGSE Functions Provide common infrastructure Command and
More informationOptical Data Interface ODI-2.1 High Speed Data Formats Preliminary Specification. Revision Date
Optical Data Interface O-2.1 High Speed Data Formats Preliminary Specification Revision Date 171002 2 O 3-part Specification O-2.1: High-Speed Formats 8 to 16 bit data formats Packing Methods Optimized
More informationPrototyping of Space Protocol(s) for SPI
Prototyping of Space Protocol(s) for SPI Carlos Urbina Ortega 12/12/2017 ESA UNCLASSIFIED - For Official Use CONTRACT DETAILS Budget + Program: TRP (two parallel contracts) Planned Duration: 12 months
More informationPLC2 Board Communication Manual CANopen Slave
PLC2 Board Communication Manual CANopen Slave 02/2006 Series: PLC2 0899.5809 E/3 Contents Contents List of Tables 4 List of Figures 4 About the Manual 5 Abbreviations and Definitions...............................
More informationFRACTIONATED SATELLITES
EXECUTIVE SUMMARY February 2010 Page : ii/12 FRACTIONATED Executive Summary Toulouse, February 2010-02-08 Prepared by: C. Cougnet, B. Gerber ESA Project Manager: EADS Astrium Project Manager: J. F. Dufour
More information