{"id":416974,"date":"2024-10-20T06:13:40","date_gmt":"2024-10-20T06:13:40","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-en-61375-3-32012-2\/"},"modified":"2024-10-26T11:34:34","modified_gmt":"2024-10-26T11:34:34","slug":"bs-en-61375-3-32012-2","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-en-61375-3-32012-2\/","title":{"rendered":"BS EN 61375-3-3:2012"},"content":{"rendered":"
This part of IEC 61375 specifies the data communication bus inside consists that are based on CANopen. CANopen was developed for use in, but is not limited to, industrial automation applications. These applications may include devices such as input\/output modules, motion controllers, human machine interfaces, sensors, closed-loop controllers, encoders, hydraulic valves or programmable controllers.<\/p>\n
In the application field of rail vehicles CANopen networks are utilized to network subsystems in consists such as e.g. brake control system, diesel engine control system and interior or exterior lighting control system. In addition CANopen is utilized as consist network to enable the data exchange between the different subsystems within one single rail vehicle or a group of rail vehicles sharing the same Consist Network.<\/p>\n
This part of IEC 61375 applies to all equipment and devices operated on a CANopen-based consist network within TCN architecture as described in IEC 61375-1.<\/p>\n
The applicability of this standard to a TCN implementation allows for individual conformance checking of the implementation itself and is a pre-requisite for further interoperability checking between different TCN implementations. In any case, proof of compatibility between Train Backbone and the Consist Network will have to be brought by the supplier.<\/p>\n
This part of IEC 61375 applies to the architecture of communication systems in Open trains. In addition it may be applicable to closed trains and multiple unit trains when so agreed between purchaser and supplier.<\/p>\n
PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
---|---|---|---|---|---|---|---|
7<\/td>\n | English CONTENTS <\/td>\n<\/tr>\n | ||||||
15<\/td>\n | INTRODUCTION <\/td>\n<\/tr>\n | ||||||
16<\/td>\n | 1 Scope 2 Normative references <\/td>\n<\/tr>\n | ||||||
17<\/td>\n | 3 Terms, definitions and abbreviations 3.1 Terms and definitions <\/td>\n<\/tr>\n | ||||||
18<\/td>\n | 3.2 Abbreviations 3.3 Conventions 4 Architecture 4.1 Content 4.2 Logical CANopen-based consist network <\/td>\n<\/tr>\n | ||||||
19<\/td>\n | 4.3 Network topology 4.4 Addressing Figures Figure 1 \u2013 Logical network architecture of the consist network Figure 2 \u2013 Network topology of CANopen-based consist network <\/td>\n<\/tr>\n | ||||||
20<\/td>\n | 4.5 Data classes 5 Physical layer 5.1 Content 5.2 Cabling 5.3 Connector <\/td>\n<\/tr>\n | ||||||
21<\/td>\n | Figure 3 \u2013 9-pin D-sub connector Figure 4 \u2013 5-pin micro style connector Tables Table 1 \u2013 Pinning for 9-pin D-sub connector <\/td>\n<\/tr>\n | ||||||
22<\/td>\n | 5.4 Physical medium attachment 5.5 Physical signaling 6 Data Link layer 6.1 Content Table 2 \u2013 Pinning for 5-pin micro style connector Table 3 \u2013 Bit timing <\/td>\n<\/tr>\n | ||||||
23<\/td>\n | 6.2 CANopen data link layer 7 CANopen application layer 7.1 Content 7.2 Reference model 7.3 Field device model Figure 5 \u2013 Field device model <\/td>\n<\/tr>\n | ||||||
24<\/td>\n | Figure 6 \u2013 Minimum field device <\/td>\n<\/tr>\n | ||||||
25<\/td>\n | 7.4 CANopen communication objects 7.5 CANopen object dictionary Figure 7 \u2013 CANopen device structure <\/td>\n<\/tr>\n | ||||||
26<\/td>\n | Table 4 \u2013 CANopen object dictionary structure <\/td>\n<\/tr>\n | ||||||
27<\/td>\n | 7.6 Predefined CANopen communication objects 7.6.1 Content 7.6.2 Object 1000h: Device type 7.6.3 Object 1001h: Error register 7.6.4 Object 1014h: COB-ID emergency object 7.6.5 Object 1017h: Heartbeat producer 7.6.6 Object 1018h: Identity object 7.6.7 Object 1029h: Error behavior Figure 8 \u2013 Structure of the device type object <\/td>\n<\/tr>\n | ||||||
28<\/td>\n | 7.6.8 Object 67FFh: Device type 7.6.9 Service data objects (SDOs) 7.6.10 Process data objects (PDOs) 8 Application data 8.1 Content 8.2 CANopen application data representation 8.3 Recommended representation principle of application data 8.3.1 Content 8.3.2 Application data for door control <\/td>\n<\/tr>\n | ||||||
29<\/td>\n | 8.3.3 Consumed door control application objects Figure 9 \u2013 Object structure Table 5 \u2013 Value definition Table 6 \u2013 Object description <\/td>\n<\/tr>\n | ||||||
30<\/td>\n | 8.3.4 Produced door control application objects Figure 10 \u2013 Object structure Table 7 \u2013 Entry description Table 8 \u2013 Value definition Table 9 \u2013 Object description <\/td>\n<\/tr>\n | ||||||
31<\/td>\n | Figure 11 \u2013 Object structure Table 10 \u2013 Entry description <\/td>\n<\/tr>\n | ||||||
32<\/td>\n | 9 CANopen network management 9.1 Content Table 11 \u2013 Value definition Table 12 \u2013 Object description Table 13 \u2013 Entry description <\/td>\n<\/tr>\n | ||||||
33<\/td>\n | 9.2 CANopen NMT slave functionality 9.3 CANopen manager functionality 9.3.1 General <\/td>\n<\/tr>\n | ||||||
34<\/td>\n | 9.3.2 Object dictionary usage 9.3.3 Redundant networks <\/td>\n<\/tr>\n | ||||||
35<\/td>\n | 9.4 CANopen NMT start-up 9.4.1 NMT startup Figure 12 \u2013 NMT startup, part 1 <\/td>\n<\/tr>\n | ||||||
37<\/td>\n | Figure 13 \u2013 NMT startup, part 2 <\/td>\n<\/tr>\n | ||||||
38<\/td>\n | 9.4.2 NMT startup simple Figure 14 \u2013 NMT startup simple <\/td>\n<\/tr>\n | ||||||
39<\/td>\n | 9.4.3 Start process boot NMT slave Figure 15 \u2013 Start process boot NMT slave <\/td>\n<\/tr>\n | ||||||
40<\/td>\n | 9.5 Boot NMT slave Figure 16 \u2013 Boot NMT slave, part 1 <\/td>\n<\/tr>\n | ||||||
42<\/td>\n | Figure 17 \u2013 Boot NMT slave, part 2 <\/td>\n<\/tr>\n | ||||||
43<\/td>\n | Figure 18 \u2013 Boot NMT slave, part 3 <\/td>\n<\/tr>\n | ||||||
45<\/td>\n | 9.5.1 Check configuration Figure 19 \u2013 Check configuration <\/td>\n<\/tr>\n | ||||||
46<\/td>\n | 9.5.2 Check NMT state 9.5.3 NMT flying master start up Figure 20 \u2013 Check NMT state <\/td>\n<\/tr>\n | ||||||
47<\/td>\n | 9.5.4 Error status Table 14 \u2013 Error status <\/td>\n<\/tr>\n | ||||||
48<\/td>\n | 9.6 Error control 9.6.1 Start error control Figure 21 \u2013 Start error control <\/td>\n<\/tr>\n | ||||||
49<\/td>\n | 9.6.2 Error handler Figure 22 \u2013 Error handler <\/td>\n<\/tr>\n | ||||||
50<\/td>\n | 9.6.3 Bootup handler 9.7 Additional NMT master services and protocols 9.8 Object dictionary entries 9.8.1 Object 1020h: Verify configuration Figure 23 \u2013 Bootup handler <\/td>\n<\/tr>\n | ||||||
51<\/td>\n | 9.8.2 Object 102Ah: NMT inhibit time Table 15 \u2013 Object description Table 16 \u2013 Entry description <\/td>\n<\/tr>\n | ||||||
52<\/td>\n | 9.8.3 Object 1F20h: Store DCF Table 17 \u2013 Object description Table 18 \u2013 Entry description Table 19 \u2013 Object description <\/td>\n<\/tr>\n | ||||||
53<\/td>\n | 9.8.4 Object 1F22h: Concise DCF Table 20 \u2013 Entry description <\/td>\n<\/tr>\n | ||||||
54<\/td>\n | Figure 24 \u2013 Data stream definition of concise DCF Table 21 \u2013 Object description <\/td>\n<\/tr>\n | ||||||
55<\/td>\n | 9.8.5 Object 1F26h: Expected configuration date Table 22 \u2013 Entry description Table 23 \u2013 Object description <\/td>\n<\/tr>\n | ||||||
56<\/td>\n | 9.8.6 Object 1F27h: Expected configuration time Table 24 \u2013 Entry description Table 25 \u2013 Object description <\/td>\n<\/tr>\n | ||||||
57<\/td>\n | 9.8.7 Object 1F80h: NMT startup Figure 25 \u2013 Object structure Figure 26 \u2013 Bit structure of the configuration value Table 26 \u2013 Entry description <\/td>\n<\/tr>\n | ||||||
58<\/td>\n | Table 27 \u2013 Value NMT master (bit: 0) Table 28 \u2013 Value Start all nodes (bit: 1) Table 29 \u2013 Value NMT master start (bit: 2) Table 30 \u2013 Value Start node (bit: 3) Table 31 \u2013 Reset all nodes (bit: 4) Table 32 \u2013 Flying master (bit: 5) Table 33 \u2013 Stop all nodes (bit: 6) <\/td>\n<\/tr>\n | ||||||
59<\/td>\n | 9.8.8 Object 1F81h: NMT slave assignment Figure 27 \u2013 Object structure of the value Table 34 \u2013 Exceptions for NMT start-up capable devices Table 35 \u2013 Object description Table 36 \u2013 Entry description <\/td>\n<\/tr>\n | ||||||
60<\/td>\n | Figure 28 \u2013 Bit structure of the configuration value Table 37 \u2013 NMT slave (bit: 0) Table 38 \u2013 NMT boot slave (bit: 2) Table 39 \u2013 Mandatory (bit: 3) Table 40 \u2013 Reset communication (bit: 4) Table 41 \u2013 Software version (bit: 5) Table 42 \u2013 Software update (bit: 6) <\/td>\n<\/tr>\n | ||||||
61<\/td>\n | 9.8.9 Object 1F82h: Request NMT Table 43 \u2013 Restore (bit: 7) Table 44 \u2013 Object description Table 45 \u2013 Entry description <\/td>\n<\/tr>\n | ||||||
63<\/td>\n | Table 46 \u2013 Value definition Table 47 \u2013 Object description <\/td>\n<\/tr>\n | ||||||
64<\/td>\n | 9.8.10 Object 1F83h: Request node guarding Table 48 \u2013 Entry description <\/td>\n<\/tr>\n | ||||||
65<\/td>\n | Table\u00a049 \u2013 Value definition Table 50 \u2013 Object description <\/td>\n<\/tr>\n | ||||||
66<\/td>\n | 9.8.11 Object 1F84h: Device type identification Table 51 \u2013 Entry description <\/td>\n<\/tr>\n | ||||||
67<\/td>\n | 9.8.12 Object 1F85h: Vendor identification Table 52 \u2013 Object description Table 53 \u2013 Entry description <\/td>\n<\/tr>\n | ||||||
68<\/td>\n | 9.8.13 Object 1F86h: Product code Table 54 \u2013 Object description Table 55 \u2013 Entry description <\/td>\n<\/tr>\n | ||||||
69<\/td>\n | 9.8.14 Object 1F87h: Revision number Table 56 \u2013 Object description Table\u00a057 \u2013 Entry description <\/td>\n<\/tr>\n | ||||||
70<\/td>\n | 9.8.15 Object 1F88h: Serial number Table 58 \u2013 Object description Table 59 \u2013 Entry description <\/td>\n<\/tr>\n | ||||||
71<\/td>\n | 9.8.16 Object 1F89h: Boot time Table 60 \u2013 Object description Table\u00a061 \u2013 Entry description <\/td>\n<\/tr>\n | ||||||
72<\/td>\n | 9.8.17 Object 1F8Ah: Restore configuration Table 62 \u2013 Object description Table 63 \u2013 Entry description Table 64 \u2013 Object description <\/td>\n<\/tr>\n | ||||||
73<\/td>\n | 9.8.18 Object 1F91h: Self-starting nodes timing parameters Table 65 \u2013 Entry description Table 66 \u2013 Object description <\/td>\n<\/tr>\n | ||||||
74<\/td>\n | 10 Gateway functions 10.1 Content Table 67 \u2013 Entry description <\/td>\n<\/tr>\n | ||||||
75<\/td>\n | 10.2 Gateway architecture Figure 29 \u2013 Gateway between Train backbone and CANopen consist network <\/td>\n<\/tr>\n | ||||||
76<\/td>\n | 10.3 General principles and services 10.3.1 Content 10.3.2 Gateway class definitions 10.3.3 Service primitives definitions 10.4 Network access service specification 10.4.1 SDO access services <\/td>\n<\/tr>\n | ||||||
77<\/td>\n | Table 68 \u2013 Upload SDO service <\/td>\n<\/tr>\n | ||||||
78<\/td>\n | 10.4.2 PDO access services Table 69 \u2013 Download SDO parameters Table 70 \u2013 Configure SDO timeout parameters <\/td>\n<\/tr>\n | ||||||
79<\/td>\n | Table 71 \u2013 Configure RPDO service parameters <\/td>\n<\/tr>\n | ||||||
80<\/td>\n | Table 72 \u2013 Configure TPDO service parameters Table 73 \u2013 Read PDO data service parameters <\/td>\n<\/tr>\n | ||||||
81<\/td>\n | 10.4.3 CANopen NMT services Table 74 \u2013 Write PDO data service parameters Table 75 \u2013 RPDO received service parameters Table 76 \u2013 Start node service parameters <\/td>\n<\/tr>\n | ||||||
82<\/td>\n | Table 77 \u2013 Stop node service parameters Table 78 \u2013 Set node to pre-operational service parameters Table 79 \u2013 Reset node service parameters <\/td>\n<\/tr>\n | ||||||
83<\/td>\n | Table 80 \u2013 Reset communication service parameters Table 81 \u2013 Enable node guarding service parameters Table 82 \u2013 Disable node guarding service parameters <\/td>\n<\/tr>\n | ||||||
84<\/td>\n | 10.4.4 Device failure management services Table 83 \u2013 Start heartbeat consumer service parameters Table 84 \u2013 Disable heartbeat consumer service parameters Table 85 \u2013 Error control event received parameters <\/td>\n<\/tr>\n | ||||||
85<\/td>\n | 10.4.5 CANopen interface configuration services Table 86 \u2013 Read device error service parameters Table 87 \u2013 Emergency event received service parameters Table 88 \u2013 Initialize gateway service parameters <\/td>\n<\/tr>\n | ||||||
86<\/td>\n | Table 89 \u2013 Store configuration service parameters Table 90 \u2013 Restore configuration service parameters Table 91 \u2013 Set heartbeat producer service parameters <\/td>\n<\/tr>\n | ||||||
87<\/td>\n | 10.4.6 Gateway management services Table 92 \u2013 Set node-ID service parameters Table 93 \u2013 Start emergency consumer service parameters Table 94 \u2013 Stop emergency consumer service parameters <\/td>\n<\/tr>\n | ||||||
88<\/td>\n | 10.4.7 Manufacturer-specific services 10.5 ASCII mapping of network access services 10.5.1 Content Table\u00a095 \u2013 Set default network service parameters Table 96 \u2013 Start default node-ID service parameters Table 97 \u2013 Get version service parameters <\/td>\n<\/tr>\n | ||||||
89<\/td>\n | 10.5.2 Definitions Table 98 \u2013 Syntax and CANopen data types <\/td>\n<\/tr>\n | ||||||
90<\/td>\n | Table 99 \u2013 Command notation in BNF <\/td>\n<\/tr>\n | ||||||
91<\/td>\n | Table 100 \u2013 Response notation Table 101 \u2013 Internal error code (InEC) Table 102 \u2013 Notation for event triggered messages <\/td>\n<\/tr>\n | ||||||
92<\/td>\n | 10.5.3 Network access command specification Table 103 \u2013 Syntax for upload SDO command Table 104 \u2013 Examples for upload SDO command Table 105 \u2013 Syntax for Download SDO command Table 106 \u2013 Examples for download SDO command Table 107 \u2013 Syntax for configure SDO timeout command <\/td>\n<\/tr>\n | ||||||
93<\/td>\n | Table 108 \u2013 Syntax for configure RPDO command Table 109 \u2013 Examples for configure RPDO command Table 110 \u2013 Syntax for configure TPDO command Table 111 \u2013 Examples for configue TPDO command <\/td>\n<\/tr>\n | ||||||
94<\/td>\n | Table 112 \u2013 Syntax for read PDO data command Table 113 \u2013 Response syntax for read PDO data command Table 114 \u2013 Syntax for write PDO data command Table 115 \u2013 Syntax for RPDO receive command Table 116 \u2013 Examples RPDO received command Table 117 \u2013 Syntax for start node command <\/td>\n<\/tr>\n | ||||||
95<\/td>\n | Table 118 \u2013 Syntax for stop node command Table 119 \u2013 Syntax set node to pre-operational command Table 120 \u2013 Syntax reset node command Table 121 \u2013 Syntax reset communication command Table 122 \u2013 Syntax enable node guarding command <\/td>\n<\/tr>\n | ||||||
96<\/td>\n | Table 123 \u2013 Syntax disable node guarding command Table 124 \u2013 Syntax start heartbeat consumer command Table 125 \u2013 Syntax disable heartbeat consumer command Table 126 \u2013 Syntax for error control event received command <\/td>\n<\/tr>\n | ||||||
97<\/td>\n | Table 127 \u2013 Syntax for read device error command Table 128 \u2013 Syntax for emergency event received command Table 129 \u2013 Syntax for initialize gateway command Table 130 \u2013 Bit rate indices <\/td>\n<\/tr>\n | ||||||
98<\/td>\n | Table 131 \u2013 Syntax for store configuration command Table 132 \u2013 Storage specifier Table 133 \u2013 Syntax restore configuration command Table 134 \u2013 Syntax set heartbeat producer command Table 135 \u2013 Syntax set node-ID command <\/td>\n<\/tr>\n | ||||||
99<\/td>\n | Table 136 \u2013 Syntax set default network command Table 137 \u2013 Syntax set default node-ID command Table 138 \u2013 Syntax for get version command Table 139 \u2013 Response syntax for get version command <\/td>\n<\/tr>\n | ||||||
100<\/td>\n | 11 Train network management 11.1 Content Figure 30 \u2013 Management messages (informative) Table 140 \u2013 Example for get version response <\/td>\n<\/tr>\n | ||||||
101<\/td>\n | 11.2 Manager, Agents and interfaces (informative) 11.3 Management message protocol (informative) 11.4 Object interfaces (informative) 11.5 CANopen-specific management services 11.5.1 General 11.5.2 Agent interfaces on a Station connected to CANopen consist network <\/td>\n<\/tr>\n | ||||||
102<\/td>\n | 11.5.3 Management message structure for CANopen consist networks 11.5.4 Notation for the CANopen specific SIF_codes Figure 31 \u2013 Agent interface on a CANopen (gateway) station for message data Table 141 \u2013 Management message structure <\/td>\n<\/tr>\n | ||||||
103<\/td>\n | 11.5.5 Notation for a call CANopen management message 11.5.6 Notation for a reply CANopen management message 11.5.7 Notation for the TNM CANopen services command codes Table 142 \u2013 CANopen specific SIF_codes Table 143 \u2013 Notation for a call CANopen management message Table 144 \u2013 Notation for a reply CANopen management message <\/td>\n<\/tr>\n | ||||||
104<\/td>\n | 11.6 TNM CANopen services 11.6.1 Content 11.6.2 Call_Write_CANopen_Command (with reservation) Table 145 \u2013 TNM CANopen services command codes (reservation required) Table 146 \u2013 TNM CANopen services command codes (reservation not required) <\/td>\n<\/tr>\n | ||||||
105<\/td>\n | 11.6.3 Reply_Write_CANopen_Command (with reservation) 11.6.4 Call_Read_CANopen_Command (without reservation) Figure 32 \u2013 Call_Write_CANopen_Command Figure 33 \u2013 Reply_Write_CANopen_Command Table 147 \u2013 Value definition for Call_Write_CANopen_Command Table 148 \u2013 Value definition Reply_Write_CANopen_Command <\/td>\n<\/tr>\n | ||||||
106<\/td>\n | 11.6.5 Reply_Read_CANopen_Command (without reservation) 12 CANopen management message data handling 12.1 General Figure 34 \u2013 Call_Read_CANopen_Command (without reservation) Figure 35 \u2013 Reply_Read_CANopen_command (without reservation) Table 149 \u2013 Value definition for Call_Read_CANopen_Command (without reservation) Table 150 \u2013 Value definition for Reply_Read_CANopen_Command (without reservation) <\/td>\n<\/tr>\n | ||||||
107<\/td>\n | Figure 36 \u2013 CANopen device capable to handle TNM management messages <\/td>\n<\/tr>\n | ||||||
108<\/td>\n | 12.2 Message data format 12.3 Requirements for message data communication within CANopen networks Figure\u00a037 \u2013 Message data format comparison <\/td>\n<\/tr>\n | ||||||
109<\/td>\n | 12.4 Object 1F78h: CANopen message data reception Table 151 \u2013 Object description Table 152 \u2013 Entry description <\/td>\n<\/tr>\n | ||||||
110<\/td>\n | 13 Conformance testing <\/td>\n<\/tr>\n | ||||||
111<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Electronic railway equipment. Train communication network (TCN) – CANopen Consist Network (CCN)<\/b><\/p>\n |