🔥🔥 Don’t Miss Out on Our End of Autumn Sale. If you have any questions, feel free to click the bottom right corner to contact our customer service..

Concat us[email protected]
Shopping Cart

No products in the cart.

🔍
BS EN 16603-50-15:2017

BS EN 16603-50-15:2017

$215.11

Space engineering. CANbus extention protocol

Published By Publication Date Number of Pages
BSI 2017 100
PDF Format Searchable Printable Preview Now
Guaranteed Safe Checkout
Category:

If you have any questions, feel free to reach out to our online customer service team by clicking on the bottom right corner. We’re here to assist you 24/7.
Email:[email protected]

This European Standard is applicable to spacecraft projects that opt to use the CAN Network for spacecraft on-board communications and control. It also defines the optional use of the CANopen standard as an application layer protocol operating in conjunction with the CAN Network data link layer.

This standard does not modify the basic CAN Network specification and complies with ISO 11898-1/-2:2003. This standard does define protocol extensions needed to meet spacecraft specific requirements.

This standard covers the vast majority of the on-board data bus requirements for a broad range of different mission types. However, there can be some cases where a mission has particularly constraining requirements that are not fully in line with those specified in this standard. In those cases this standard is still applicable as the basis for the use of CAN Network, especially for physical layer and redundancy management.

This standard may be tailored for the specific characteristic and constrains of a space project in conformance with ECSS-S-ST-00.

PDF Catalog

PDF Pages PDF Title
2 undefined
11 1 Scope
12 2 Normative references
14 3 Terms, definitions and abbreviated terms
3.1 Terms from other standards
3.2 Terms specific to the present standard
18 3.3 Abbreviated terms
19 3.4 Bit numbering convention
3.5 Nomenclature
21 4 Overview of the standard and principles
4.1 Document organization
4.2 Relationship of CAN Bus Network to existing Architectures
22 4.3 CANbus network
23 4.4 Physical layer
4.5 Communication model
4.6 CANopen higher layer protocol
25 4.7 Time distribution
4.7.1 Overview
26 4.7.2 SYNC message and protocol
4.7.3 Bit timing
4.8 Redundancy management and monitoring
4.8.1 Overview
27 4.8.2 Node Monitoring via Node-Guarding or Heartbeat Messages
28 4.8.3 Bus monitoring and reconfiguration management
29 4.9 Connectors and pin assignments
4.10 Minimal protocol set
30 5 Physical layer
5.1 Topology
5.1.1 Physical topology
5.1.1.1 General
31 5.1.1.2 Terminators
32 5.1.2 Maximum bus length and drop length
5.1.3 Number of network devices
33 5.2 Medium
5.2.1 Cable requirements
5.2.1.1 CAN primary bus
5.2.1.2 CAN redundant bus
5.2.1.3 CAN Network cable
5.2.1.4 Shield – system specific
34 5.2.2 Connectors
5.2.2.1 Connector type
5.2.2.2 Receptacles (Sockets)
5.2.2.3 Plugs
5.2.2.4 Reserved pins
5.3 Transceiver characteristics
5.3.1 General
35 5.3.2 ISO 11898-2:2003 transceiver electrical characteristics
5.3.3 Resistance to electrical CAN Network faults
5.3.3.1 General
36 5.3.3.2 Bus failure detection requirements
40 5.3.4 Transceiver isolation
5.3.5 Physical layer implementation based on RS-485 transceivers
41 5.3.6 Detailed implementation for RS-485 transceiver
5.4 Bit timing
5.4.1 Bit rate 1 Mbps
5.4.2 Other bit rates
5.4.3 Bit timing
42 5.5 Electromagnetic compatibility (EMC)
5.6 Data link layer
5.6.1 ISO 11898 compliance
5.6.2 Fault confinement
44 6 CANopen higher layer protocol
6.1 Service data objects
6.2 Process data objects
6.3 Synchronisation object
45 6.4 Emergency object
6.5 Network management objects
6.5.1 Module control services
6.5.2 Error control services
6.5.3 Bootup service
6.5.4 Node state diagram
46 6.6 Electronic data sheets
6.7 Device and application profiles
47 6.8 Object dictionary
6.9 Synchronous communications
6.10 COB-ID and NODE-ID assignment
49 7 Time distribution
7.1 Time objects
7.1.1 Time code formats
50 7.1.2 Spacecraft elapsed time objects
7.1.3 Spacecraft universal time coordinated objects
51 7.2 Time distribution and synchronization protocols
7.2.1 General
7.2.2 Time distribution protocol
52 7.2.3 High-resolution time distribution protocol
54 8 Redundancy management
8.1 General
8.2 Node internal bus redundancy architectures
8.2.1 General
8.2.2 Parallel bus access architecture
8.2.3 Selective bus access architecture
55 8.3 Bus monitoring and reconfiguration management
8.3.1 Bus redundancy management parameters
58 8.3.2 Start-up procedure
59 8.3.3 Bus monitoring protocol
62 9 Minimal implementation of the CANopen protocol for highly asymmetrical control applications
9.1 COB-ID assignment
9.2 Object dictionary
9.3 Minimal set CANopen Objects
63 9.4 Minimal Set Protocol
9.4.1 Definitions
64 9.4.2 Use of data bytes in application layer
65 9.4.3 Minimal Set Protocol data transmission
66 9.4.4 PDO transmit triggered by telemetry request
9.4.5 PDO mapping
67 9.4.6 Network management objects
9.4.6.1 Module control services
9.4.7 Special function objects
9.4.7.1 Time stamp objects
9.4.7.2 Emergency objects
9.4.7.3 SYNC objects
68 9.4.8 Communication error object
9.4.9 NMT error control objects
9.4.9.1 Heartbeat service
9.4.9.2 Bootup service
9.4.10 Miscellaneous authorized objects
72 9.5 Free COB–ID
75 10 Connectors and pin assignments
10.1 Overview
10.2 Naming convention
10.3 Circular connectors
10.3.1 MIL-C D38999 configuration B: Dual CAN Network
76 10.3.2 MIL-C D38999 configuration D: Single CAN Network
77 10.4 Sub-miniature D connectors (9-pin D-sub)
78 10.5 Sub-miniature D connectors (9-pin D-sub) – RS-485
79 11 CANopen standard applicability matrix
11.1 Introduction

Related products

BS EN 16603-50-15:2017
$215.11