BSI PD IEC TS 61851-3-4:2023:2024 Edition
$215.11
Electric vehicles conductive charging system – DC EV supply equipment where protection relies on double or reinforced insulation. General definitions and requirements for CANopen communication
Published By | Publication Date | Number of Pages |
BSI | 2024 | 106 |
PDF Catalog
PDF Pages | PDF Title |
---|---|
2 | undefined |
4 | CONTENTS |
10 | FOREWORD |
12 | INTRODUCTION |
14 | 1 Scope 2 Normative references |
15 | 3 Terms and definitions |
18 | 4 Symbols and abbreviated terms |
19 | 5 General conditions for the tests |
20 | 6 Physical layer specification 6.1 General 6.2 Medium access unit 6.3 Transmission rates 6.4 Node-ID assignment |
21 | 6.5 Network topology 6.6 Gateway 7 Error handling 7.1 General 7.2 Enhancement of the emergency message handling Tables Table 1 – DRI EV supply equipment and external device node-ID assignment |
22 | Figures Figure 1 – Protocol emergency write for energy management applications |
23 | 7.3 Pre-defined error field 7.4 Error behaviour Table 2 – Value definition for EMCY message |
24 | 7.5 Additional error codes Table 3 – Additional error codes |
25 | 8 Operating principles 8.1 General 8.2 Functional description 8.2.1 General 8.2.2 Voltages, currents, loads |
26 | 8.2.3 Activating of the energy management system (EMS) |
27 | 8.2.4 Connection and disconnection of devices 8.2.5 “Sleep” 8.3 Use case specific definitions for EMSs in EVs 8.3.1 General 8.3.2 EMS in operation |
28 | 8.3.3 Design and implementation for EV supply system configurations Types “A-F” |
29 | Figure 2 – EV supply system cConfiguration type A |
30 | Figure 3 – EV supply system configuration type B |
31 | Figure 4 – EV supply system cConfiguration type C Figure 5 – EV supply system configuration type D |
32 | Figure 6 – EV supply sytem configuration type E Figure 7 – EV supply system configuration type F |
33 | 8.4 Virtual architecture of the EMS 8.4.1 General 8.4.2 Standard virtual EMS control network Figure 8 – Conversion device for configuration type C |
34 | 8.4.3 General application object (GAO) Figure 9 – Virtual standard architecture of the EMS |
35 | 8.4.4 Energy management system controller (EMSC) 8.4.5 Voltage converter unit (VCU) 8.4.6 Battery system |
36 | 8.4.7 Security unit (optional) 8.4.8 Manufacturer-specific virtual devices (optional) 9 Finite state automaton (device modelling) 9.1 General |
37 | 9.2 EMS finite state automaton (FSA) 9.2.1 State definition Figure 10 – Remote and local control |
38 | Table 4 – State description |
39 | 9.2.2 Transitions of the EMS FSA Figure 11 – EMS FSA |
40 | 10 General CANopen communication capabilities in EMSs 10.1 Network management Table 5 – Events and actions |
41 | 10.2 SDO communication 10.3 PDO communication 10.4 Bootloader 10.4.1 General 10.4.2 Bootloader mode |
42 | 10.4.3 Starting and stopping the application program Figure 12 – Flow chart for switching between bootloader mode and application |
43 | 10.4.4 Application program file format Figure 13 – Application program Figure 14 – Program identifier 1 Figure 15 – Program identifier 2 |
44 | Figure 16 – Program identifier 3 Figure 17 – Program identifier 4 Figure 18 – Program identifier 5 |
45 | Figure 19 – Example for program identifier handling Table X – xxx |
46 | Table 6 – Value definition |
47 | 10.4.5 Error management 11 Representation of analogue values 11.1 General 11.2 Representation of generic analogue values 11.2.1 Percent 11.2.2 Temperature 11.2.3 Temperature rate ((T) 11.2.4 Time (days) 11.2.5 Time (minutes) 11.2.6 Time (milliseconds) |
48 | 11.3 Electrical-related analogue value representation 11.3.1 Current 11.3.2 Electric charge 11.3.3 Electric charge (for statistical purposes) 11.3.4 Electric charge rate 11.3.5 Energy power (for statistical purposes) 11.3.6 Energy power 11.3.7 Frequency 11.3.8 Power 11.3.9 Power factor 11.3.10 Resistor 11.3.11 Voltage 11.4 Mechanical-related analogue value representation (optional) 11.4.1 Angle/circular position |
49 | 11.4.2 Distance (long) 11.4.3 Distance (short) 11.4.4 Force 11.4.5 Rotational speed 11.4.6 Revolutions 11.4.7 Torque 11.4.8 Velocity 11.5 Optical-related analogue value representation – Colour/brightness Figure 20 – Object structure |
50 | Annex A (informative)System architecture and use cases A.1 General A.2 Application profile for EMS A.2.1 General A.2.2 Maximum possible devices on a virtual EMS control network |
51 | A.2.3 Minimum virtual EMS control network Figure A.1 – Virtual maximum architecture of the EMS |
52 | A.3 General application object A.3.1 General A.3.2 Motor control unit A.3.3 Load monitoring unit Figure A.2 – Virtual minimum architecture of the EMS |
53 | A.3.4 Generator unit A.3.5 Load unit A.3.6 HMI unit A.3.7 Sensor unit A.3.8 Gateway A.3.9 IEC 61850 gateway A.4 Use cases (informative) A.4.1 EV use case |
54 | A.4.2 Stationary use case Figure A.3 – EMS application in EV |
55 | Figure A.4 – Typically stationary photovoltaic hybrid off-grid application |
56 | Figure A.5 – Use case according to self-consumption regulation |
57 | Annex B (normative)Energy management system controller (EMSC) B.1 General B.2 Object dictionary B.2.1 General B.2.2 NMT communication objects |
58 | B.2.3 Produced application objects Figure B.1 – Value structure Table B.1 – Value definition |
59 | Figure B.2 – Object structure Table B.2 – Object description Table B.3 – Entry description Table B.4 – Value definition EV type |
60 | Figure B.3 – Value structure Table B.5 – Value definition speed Table B.6 – Object description Table B.7 – Entry description |
61 | B.2.4 Consumed application objects Table B.8 – Value definition Table B.9 – Object description Table B.10 – Entry description |
62 | Table B.11 – Value definition Table B.12 – Object description |
63 | Table B.13 – Entry description |
64 | Table B.14 – Value definition Table B.15 – Object description |
65 | Table B.16 – Entry description |
66 | B.3 Tasks of an EMSC B.3.1 General Figure B.4 – Value structure Table B.17 – Value definition Table B.18 – Object description Table B.19 – Entry description |
67 | B.3.2 Start-up B.3.3 Compatibility check B.3.4 Releasing devices Table B.20 – Compatibility check |
68 | B.3.5 “Sleep”- mode |
69 | Annex C (informative)Implementation guidelines C.1 General C.2 Timings C.2.1 General C.2.2 Start up C.3 Master handling C.3.1 General C.3.2 Detecting master availability C.3.3 EMSC SDO handling |
70 | C.4 Design of voltage converter unit communication for EVs C.4.1 Use cases |
71 | C.4.2 Recommended power transfer protocol Figure C.1 – Voltage converter unit used as power supply for EV |
72 | Figure C.2 – Sequence diagram for startup of the connection |
73 | Figure C.3 – Sequence diagram “New device connected” |
74 | Figure C.4 – Preparation of the power transfer procedure |
75 | Table C.1 – Data transfer from battery system to VCU’s Table C.2 – Additional parameters relevant for power transfer process Table C.3 – Additional parameters relevant for power transfer process |
76 | Table C.4 – Most important parameters for limiting |
77 | Figure C.5 – Configuration of limitations Table C.5 – Limit calculation for battery systems |
78 | Figure C.6 – Start up procedure for initiate power transfer |
79 | Table C.6 – Data transfer from battery to VCUs Table C.7 – Data transfer from VCUs to the battery |
80 | Figure C.7 – Power transfer in progress |
81 | Annex D (normative)Power management via “sleep” D.1 General D.2 Operation principles D.2.1 General D.2.2 Pre-conditions D.2.3 Finite state automaton for power management |
82 | Figure D.1 – Power management FSA Table D.1 – State description |
83 | D.3 Services D.3.1 General D.3.2 Service “query sleep objection” and “sleep objection” Table D.2 – Events and actions |
84 | D.3.3 Service Set “sleep” Figure D.2 – “Sleep” inhibited by objection Figure D.3 – Transition into “sleep” without objection |
85 | D.3.4 Service “wake-up” Figure D.4 – Execution of “query sleep objection” service for a device in “sleep” Figure D.5 – Execution of “wake-up” service |
86 | D.3.5 Service “request sleep” D.4 Protocols D.4.1 Protocol “query sleep objection” D.4.2 Protocol “sleep objection” Figure D.6 – Execution of “request sleep” service Figure D.7 – Protocol “query sleep objection” |
87 | D.4.3 Protocol set “sleep” D.4.4 Protocol “wake-up” Figure D.8 – Protocol “sleep objection” Figure D.9 – Protocol set “sleep” |
88 | Figure D.10 – Protocol “wake-up” Figure D.11 – Protocol “wake-up” |
89 | D.4.5 Protocol “request sleep” D.5 Power management timing – Sleep/wake-up Figure D.12 – Protocol “request sleep” Figure D.13 – “Query sleep objection” protocol timing Table D.3 – Timing values for “query sleep objection” |
90 | D.6 Miscellaneous timing values Table D.4 – Timing values for “sleep” wait time Table D.5 – Miscellaneous timing values |
91 | Annex E (informative)Handling of multiple energy loads/sources E.1 General E.2 Consecutive power transfer to battery systems without power loss |
92 | E.3 Parallel charge and discharge Table E.1 – Example for battery system switching procedure |
93 | Table E.2 – Example for battery system handling in parallel |
94 | Annex F (normative)Communication connector F.1 General F.2 Configuration of 4-II for configuration type B |
95 | F.3 NFC description Figure F.1 – Configuration 4-II communication only |
96 | Table F.1 – NDEF message Table F.2 – NFC description |
97 | Figure F.2 – Position of NFC |
98 | Figure F.3 – Latching device |
99 | Figure F.4 – Position of NFC in vehicle inlet and socket-outlet according to IEC TS 62169-4:2019 sheet 4-II Figure F.5 – Overview |
100 | F.4 Communication connector Figure F.6 – Communication connector details |
101 | Figure F.7 – Overview of communication connector |
102 | Annex G (informative)Orientation G.1 General G.2 Orientation definitions for pedal driven EVs G.3 Orientations for non- pedal driven EV applications Figure G.1 – Orientation definition for EVs |
103 | Figure G.2 – Position of axes relative to orientation |
104 | Bibliography |