BS ISO/IEC 10192-3:2017:2018 Edition
$215.11
Information technology. Home electronic system (HES) interfaces – Modular communications interface for energy management
Published By | Publication Date | Number of Pages |
BSI | 2018 | 100 |
This part of IEC 10192 specifies a UCM (Universal Communications Module) that transfers energy management data via a home network between an end-device and an energy management agent (specified in ISO/IEC 15067‑3) or an energy service provider. This document specifies the mechanical, electrical and logical characteristics of the interfaces of UCM to an end-device (hereafter referred to as an SGD — Smart Grid Device) and a choice of interfaces to a home communications network.
This document specifies the physical and data-link characteristics of the interface between the UCM and the SGD, along with certain higher-layer and application layer elements as needed to assure interoperability over a broad range of device capabilities. It specifies a mechanism through which network, transport and application layer messages specified in other documents listed in this document may be passed through the interface. For those end-devices that cannot process one of the “pass-through” command sets, a Simple Protocol is specified according to the OSI (Open System Interconnect) reference model (ISO/IEC 7498‑1) including application layer messaging for energy management.
The UCM specified in this document is intended to be installable by the purchaser, home occupant or professional installer. The connectors are integrated in a way that allows for easy, plug-in installation. However, the manufacturer may choose to pre-install a module during production or have installation handled by a manufacturer representative or professional installer.
The scope of this document does not include safety related construction, performance, marking or instruction requirements. UCM products should additionally comply with applicable product safety standard(s). Examples of such standards are presented in Annex G.
NOTE Some regulatory authorities require that appliances intended for participation in energy management, such as thermostats, be user installable.
PDF Catalog
PDF Pages | PDF Title |
---|---|
2 | undefined |
4 | CONTENTS |
9 | FOREWORD |
10 | INTRODUCTION |
11 | Figures Figure 1 – Illustrations of the modular communications interface (MCI) concept |
12 | 1 Scope 2 Normative references |
13 | 3 Terms, definitions and abbreviated terms 3.1 Terms and definitions 3.2 Abbreviated terms |
14 | 4 Conformance 5 Physical/electrical Interface 5.1 Form factors 5.2 Removal and exchange of a UCM 5.3 Block diagram |
15 | 6 Serial protocol 6.1 Protocol data unit 6.2 Message Type field Figure 2 – Modular communications interface (MCI) block diagram Tables Table 1 – Protocol data unit format |
16 | 6.3 Payload length field Table 2 – Message type assignments |
17 | 6.4 Checksum field 6.5 Bit and byte order 6.5.1 Bit order within a byte 6.5.2 Byte order for multi-byte messages 6.6 Message synchronization and timing 6.6.1 Message sequencing 6.6.2 Link layer timing |
18 | Figure 3 – Link layer timing Table 3 – Message timing requirements |
19 | 6.6.3 Randomized link layer retries 6.6.4 Application layer timing Figure 4 – Application layer timing |
20 | 6.7 SGD handling of conflicting messages 7 Simple Protocol Table 4 – Basic/Intermediate DR application layer timing parameters |
21 | 8 Link layer 8.1 Use of link layer messages 8.2 Link layer ACK/NAK Table 5 – Mandatory message summary Table 6 – ACK/NAK Packet |
22 | 8.3 Message Type “supported query” Table 7 – Link layer NAK codes Table 8 – Message type “supported query” |
23 | 9 Data-link messages 9.1 Message format Table 9 – Data-link message format |
24 | Table 10 – Data-link command set |
25 | 9.2 Interface power limit negotiation Table 11 – Interface power level indicator codes |
26 | 9.3 Bit rate negotiation |
27 | 9.4 Power-up and state reset 9.5 Security 9.6 Setting slot numbering Table 12 – Bit rate indicator |
28 | 10 Basic DR application (Message Type = 0x08, 0x01) 10.1 Basic DR application commands 10.1.1 Message format Table 13 – Basic application data format |
29 | Table 14 – Basic DR application command set |
32 | 10.1.2 Basic message fixed length 10.1.3 Event Duration field |
33 | 10.1.4 Grouped messages 10.2 Usage and details of basic DR application messages 10.2.1 Request for power level (Opcode 0x06) Figure 5 – Non-linear event duration scaling |
34 | 10.2.2 Relative price commands (Opcode 0x07 and 0x08) |
35 | 10.2.3 Time remaining in present price period (Opcode 0x09) 10.2.4 Operating state monitoring (Opcodes 0x12 and 0x13) Figure 6 – Non-linear relative price scaling |
36 | Table 15 – Operating state codes |
37 | 11 Intermediate DR application (Message Type = 0x08, 0x02) 11.1 Intermediate DR message set Table 16 – Operating-state codes for usage conditions |
38 | Table 17 – Intermediate DR application command set (command byte description) |
39 | Table 18 – Intermediate DR application command set |
40 | 11.2 Usage and details of Intermediate DR application messages 11.2.1 Info request Table 19 – Response code values |
43 | 11.2.2 Get/Set UTC time |
44 | 11.2.3 Get/Set energy price |
46 | 11.2.4 Get/Set tier |
47 | 11.2.5 Get/Set temperature offset |
48 | 11.2.6 Get/Set set point |
49 | 11.2.7 Autonomous cycling |
51 | 11.2.8 Demand reduction – terminate cycling 11.3 Demand response event schedules 11.3.1 Function |
52 | 11.3.2 Send scheduled events request 11.4 Energy consumption 11.4.1 Function 11.4.2 Commodity read |
55 | 11.4.3 Get/Set CommodityType Figure 7 – Illustration of energy storage capacity |
57 | 12 Commissioning and network messages (Message Type = 0x08, 0x04) 13 Pass-Through Mode 13.1 Pass-Through method 13.1.1 General Table 20 – Commissioning and network messages |
58 | 13.1.2 Full Encapsulation in the Message Payload 13.1.3 Message Type Field 13.1.4 Message Type Support Query 13.1.5 Maximum Message Length Negotiation 13.1.6 Pass-Through mode protocols 13.2 Pass-Through mode protocols 13.2.1 USNAP 1.0 protocol Pass-Through Table 21 – Pass-Through message Table 22 – USNAP1.0 over serial |
59 | 13.2.2 SEP1.0 or 1.1 Pass-Through 13.2.3 ClimateTalk Pass-Through 13.2.4 General Internet Protocol Pass-Through Table 23 – SEP1.0 or 1.1 over serial Table 24 – ClimateTalk over serial |
60 | 13.2.5 ISO/IEC 14543-4-3 Pass-Through 13.2.6 ISO/IEC 14543-3-1 Pass-Through Figure 8 – Internet Protocol Pass-Through (IPv6) Table 25 – ISO/IEC 14543-4-3 over serial |
61 | 13.2.7 ISO/IEC 14908-1 Pass-Through 13.2.8 SunSpec Pass-Through 14 Typical communication exchanges Table 26 – ISO/IEC 14543-3-1 over serial Table 27 – ISO/IEC 14908-1 over serial Table 28 – SunSpec over serial |
62 | 15 General security principles 16 Load management event randomization |
63 | Figure 9 – Illustration of randomization of events by communications modules |
64 | Annex A (normative)Low voltage DC form factor A.1 General A.2 Limitations A.3 Power for UCM A.4 Mechanical interface A.4.1 DC form factor board layout |
65 | A.4.2 Module configuration Figure A.1 – DC form factor PCB dimensions |
66 | Figure A.2 – DC form factor housing dimensions – top view |
67 | Figure A.3 – DC form factor housing dimensions – side view |
68 | A.4.3 Form factor A.4.4 Housing materials A.4.5 Connector type Figure A.4 – DC form factor housing dimensions – end view |
69 | A.4.6 Pin assignments A.5 Electrical interface A.5.1 Electrical Interface Levels A.5.2 Signal timing Figure A.5 – Pin assignment Figure A.6 – SPI Mode 0 bit timing |
70 | A.5.3 Interface circuits A.6 Data transfer protocol A.6.1 Control signals Table A.1 – Low voltage interface signal definitions |
71 | A.6.2 Clock and data rate A.6.3 Multiple slots A.7 Link layer data flow A.8 Messages A.8.1 Frame structure A.8.2 Message synchronization (frame delimiting) A.8.3 Message filling (inter-message byte filling) |
72 | A.8.4 Command/Response encoding A.8.5 Checksum calculation A.8.6 Master/Slave A.8.7 Flow control A.8.8 Error detection and recovery |
73 | A.9 Operation A.9.1 Transaction sequence Figure A.7 – SPI transaction sequence: SGD-initiated message to the UCM |
74 | Figure A.8 – SPI transaction sequence: UCM-initiated message to the SGD |
75 | Table A.2 – SPI physical timing requirements |
76 | A.9.2 SPI data transfer state machine Figure A.9 – SPI data transfer state machine |
77 | A.9.3 SGD transmitter operation A.9.4 SGD device receiver operation |
78 | A.9.5 UCM operations |
79 | Annex B (informative)Description of DC form factor applications B.1 General B.2 Applications of ISO/IEC 24379 B.3 Physical Form Factor Review |
80 | B.4 Observations with regard to UCM and ATA confusion B.4.1 General B.4.2 ATA into Smart Grid Device B.4.3 Universal Communication Module into ATA device bay B.5 Conclusion |
81 | Annex C (normative)AC form factor C.1 General C.2 Physical form C.2.1 AC SGD and AC UCM connector |
82 | Figure C.1 – Panel-mount AC connector form factor (device side shown) and pin-out Figure C.2 – PCB-mount AC UCM connector (housing) |
83 | Figure C.3 – Cable AC UCM connector (housing) |
84 | Figure C.4 – Panel mount AC SGD connector form factor dimensions |
85 | Figure C.5 – PCB mount connector dimensions Figure C.6 – Cable connector dimensions |
86 | C.2.2 AC enclosure requirements Figure C.7 – Contact dimensions for cable connector and PCB mount connector |
87 | Figure C.8 – Reserved area and dimensions on SGD (receptacle) |
88 | Figure C.9 – Right side and top view of maximum UCM dimensions |
89 | C.3 AC power Figure C.10 – Left side and bottom view of maximum UCM dimensions |
90 | Figure C.11 – Typical RS-485 polarity and byte transfer Figure C.12 – RS-485 connections |
91 | C.4 Obtaining message sync |
92 | Annex D (normative)Fletcher checksum D.1 Checksum method D.2 Calculating the checksum D.3 Decoding the checksum |
93 | Annex E (informative)Example Visual Basic code |
94 | F.1 Average Price versus Time Varying Charges F.2 Relative price command |
98 | Bibliography |