1、 ANSI/CTA Standard Modular Communications Interface for Energy Management ANSI/CTA-2045 Amendment 1 (Formerly ANSI/CEA-2045) July 2014 NOTICE Consumer Technology Association (CTA) Standards, Bulletins and other technical publications are designed to serve the public interest through eliminating misu
2、nderstandings between manufacturers and purchasers, facilitating interchangeability and improvement of products, and assisting the purchaser in selecting and obtaining with minimum delay the proper product for his particular need. Existence of such Standards, Bulletins and other technical publicatio
3、ns shall not in any respect preclude any member or nonmember of the Consumer Technology Association from manufacturing or selling products not conforming to such Standards, Bulletins or other technical publications, nor shall the existence of such Standards, Bulletins and other technical publication
4、s preclude their voluntary use by those other than Consumer Technology Association members, whether the standard is to be used either domestically or internationally. Standards, Bulletins and other technical publications are adopted by the Consumer Technology Association in accordance with the Ameri
5、can National Standards Institute (ANSI) patent policy. By such action, the Consumer Technology Association does not assume any liability to any patent owner, nor does it assume any obligation whatever to parties adopting the Standard, Bulletin or other technical publication. Note: The users attentio
6、n is called to the possibility that compliance with this standard may require use of an invention covered by patent rights. By publication of this standard, no position is taken with respect to the validity of this claim or of any patent rights in connection therewith. The patent holder has, however
7、, filed a statement of willingness to grant a license under these rights on reasonable and nondiscriminatory terms and conditions to applicants desiring to obtain such a license. Details may be obtained from the publisher. This document does not purport to address all safety problems associated with
8、 its use or all applicable regulatory requirements. It is the responsibility of the user of this document to establish appropriate safety and health practices and to determine the applicability of regulatory limitations before its use. This document is copyrighted by the Consumer Technology Associat
9、ion and may not be reproduced, in whole or part, without written permission. Federal copyright law prohibits unauthorized reproduction of this document by any means. Organizations may obtain permission to reproduce a limited number of copies by entering into a license agreement. Requests to reproduc
10、e text, data, charts, figures or other material should be made to the Consumer Technology Association. (Formulated under the cognizance of the CTA R7.8 Modular Communication Interface for Energy Management Subcommittee.) Published by CONSUMER TECHNOLOGY ASSOCIATION 2015 Technology ISO/IEC 14908-1, “
11、Information Technology - Control network protocol - Part 1: Protocol stack“)” *Footnote: ECHONET Lite has been proposed as ISO/IEC 14543-4-3, “Information Technology - Home Electronic System (HES) architecture - Part 4-3: Application layer - light version for network enhanced control devices of HES
12、Class 1,“ currently under development. The specification for ECHONET Lite Ver1.1 is available at http:/www.echonet.gr.jp/english/index.htm. In section 2.1.6 Add “10. EchoNet Lite protocol www.echonet.gr.jp/english/index.htm” Add “11. KNX (ISO/IEC 14543-3-1) - http:/www.iso.org/iso/home/store/catalog
13、ue_ics.htm” Add “12 LonTalk (ANSI/CEA 709.1-C) - http:/www.iso.org/iso/home/store/catalogue_ics.htm” In section 4.1.1 Message Type Field. Add the following row to Table 4-2 0x09 0x08 ECHONET Lite Pass-Through 0x09 0x09 KNX Pass-Through 0x09 0x0A LonTalk Pass-Through ANSI/CEA-2045 Amendment 1 4 In se
14、ction 4.1.1 Message Type Field. Change the following row to Table 4-2. Current row: 0x09 0x08 to 0xFF For Future Assignment Replace above row with: 0x09 0x0B to 0xFF For Future Assignment Add the following section 10.1.5 after section 10.1.4. 10.1.5 ECHONET Lite Pass-Through This section shows how t
15、he ECHONET Lite 1.1 protocol is supported by the CEA-2045 interface. The messages will be formatted as follows, with the message type being a 0x09 0x08, and the payload being defined entirely by the ECHONET Consortium. Message Type = 0x09, 0x08 Reserved Must be 0x0 Payload Length ECHONET Lite Messag
16、e Checksum 2 Bytes 3 Bits 13 Bits Variable 2 Bytes Figure 10-6 ECHONET Lite Over Serial The bit order of the payload is to be the same as that specified for the DC and AC form factors in section 4.1.4 of this document. Byte order of multi-byte quantities within the EchoNet Lite payload is per the Ec
17、hoNet Lite specification. ANSI/CEA-2045 Amendment 1 5 10.1.6 KNX Pass-Through This section shows how the KNX protocol is supported by the CEA-2045 interface. The messages will be formatted as follows, with the message type being a 0x09 0x09. Message Type = 0x09, 0x09 Reserved Must be 0x0 Payload Len
18、gth KNX Message Checksum 2 Bytes 3 Bits 13 Bits Variable 2 Bytes Figure 10-7 KNX Over Serial The bit order of the payload is to be the same as that specified for the DC and AC form factors in section 4.1.4 of this document. 10.1.7 LonTalk Pass-Through This section shows how the LonTalk protocol is s
19、upported by the CEA-2045 interface. The messages will be formatted as follows, with the message type being a 0x09 0x0A, and the payload being defined entirely by the LonMark Association. Message Type = 0x09, 0x0A Reserved Must be 0x0 Payload Length LonTalk Message Checksum 2 Bytes 3 Bits 13 Bits Var
20、iable 2 Bytes Figure 10-8 LonTalk Over Serial The bit order of the payload is to be the same as that specified for the DC and AC form factors in section 4.1.4 of this document. ANSI/CEA-2045 Amendment 1 6 3. Correction of the Checksum calculation in Appendix C Replace Appendix C with the following t
21、ext: 17 Appendix C Fletcher Checksum (normative) The checksum method for this protocol shall be a “Fletchers 16-bit 1s complement checksum”. The two bytes are coded and decoded as follows: 17.1 Calculating the Checksum Initialize checksum1 to 0xAA and checksum2 to 0x00 Loop through the message (this
22、 example uses variable “I”) from the first Message Type byte to end of payload, to calculate the 2-byte checksum. This loop excludes the checksum bytes as they are not yet created. checksum1 = (checksum1 + sendDataI) Mod 255 checksum2 = (checksum2 + checksum1) Mod 255 Find the bytes to append in the
23、 following manner: mscheckbyte = 255 - (checksum1 + checksum2) Mod 255) (the MSB of the new checksum) lscheckbyte = 255 - (checksum1 + mscheckbyte) Mod 255) (the LSB of the new checksum) 17.2 Decoding the Checksum As shown in the example below, calculate the checksum exactly as it is done for creati
24、ng the checksum bytes, from the first Message Type byte to end of the payload not including the checksum bytes. The calculated checksum should equal the following two checksum bytes in the received message. ANSI/CEA-2045 Amendment 1 7 Alternatively, loop through the incoming message from the first b
25、yte to the end, including the two checksum bytes. Once the entire message including the two checksum bytes have been analyzed, checksum1 and checksum2 should equal 0x00. 17.3 Example VB Code Creating Checksum: ANSI/CEA-2045 Amendment 1 8 Decoding Checksum ANSI/CEA-2045 Amendment 1 9 4. Removal of gu
26、ide pins from DC Form Factor Replace: Figure 15-2 DC Form Factor Housing Dimensions Top View With the following: ANSI/CEA-2045 Amendment 1 10 Replace: Figure 15-3 DC Form Factor Housing Dimensions Side View With the following: ANSI/CEA-2045 Amendment 1 11 Replace: Figure 15-4 DC Form Factor Housing
27、Dimensions End View With the following: ANSI/CEA-2045 Amendment 1 12 5. Clarification on Conflict Handling Replace section 4.1.6 with the following text: CEA-2045 supports multiple possible application layer protocols, including the basic and intermediate DR commands defined herein in addition to th
28、e pass-through of other industry standard protocols. Among these varied protocols are many different commands related to demand response. It is the responsibility of the UCM, and the system in which it participates, to provide SGDs with single, clear indications of the conditions at any time. In the
29、 event that an SGD is presented with conflicting curtailment mode actions, the curtailment mode triggered by the last command received of equal or greater priority shall take precedence. For example, a cost triggered load change should not override a shed command. The priority of commands in the Bas
30、ic DR (Section 7) and Intermediate DR (Section 8) applications are indicated in the “Priority:” sub-row of the “Usage” column in Table 7-2 and Table 8-2. If the curtailment mode triggered by a command of priority “High“ is currently active, only another command of priority “High“ will be acted on by
31、 the SGD and replace the current curtailment mode. If the curtailment mode triggered by a command of priority “Low“ is currently active, then the most recently received command of either priority “Low“ or “High“ will be acted on by the SGD and replace the current curtailment mode. For the special ca
32、se of commands with priority “Low“ where the information is being used for display purposes only (such as displaying the current price) then it may be displayed by the SGD during an active priority “High“ command, but not affect the curtailment mode caused by the “High” command. Commands with priori
33、ty “Not Applicable“ are not related to curtailment and will be acted upon as soon as received. Page 20, Section 7, completely remove this paragraph (originally third on the page), as it has been moved to Section 4.1.6. Commands in the “Basic DR“ application have a priority, as indicated in “Priority
34、:” sub-row of the Usage column in Table 7-2, that affects whether the SGD should act on the most recently received command. If a command of priority “High“ is currently active, only another command ANSI/CEA-2045 Amendment 1 13 of priority “High“ will be acted on by the SGD and replace the current. I
35、f a command of priority “Low“ is currently active, then the most recently received command of priority “Low“ or “High“ will be acted on by the SGD and replace the current. For the special case of commands with priority “Low“ where the information is being used for display purposes only (such as disp
36、laying the current price) then it may be displayed by the SGD during an active priority “High“ command, but not affect curtailment. Commands with priority “Not Applicable“ are not related to curtailment and will be acted upon as soon as received. 6. Formatting changes Typo: Page 30, Section 8, Parag
37、raph 2, Remove extra Table 8-2 (the one without reference hyperlink). Formatting: Original Page 30, Section 8, Paragraph 4, add hyperlink reference to Table 8-1. ANSI/CEA-2045 Amendment 1 14 7. Add priority designations to Intermediate DR Application Commands Replace table 8-2 with the following: Pa
38、yload Description Opcode1 Opcode2 Additional Payload Definitions Usage Info Request 0x01 0x01 Defined in Section 8.1.1 Request device information Priority: “Not Applicable” Get/Set UTC Time 0x02 0x00 Defined in Section 8.1.2 Set or request Time Priority: “Not Applicable” Get/Set Energy Price 0x03 0x
39、00 Defined in Section 8.1.3 Set or request the current price of energy Priority: “Low” Get/Set Tier 0x03 0x01 Defined in Section 8.1.4 Set or request the current tier value Priority: “Low” Get/Set Temperature Offset 0x03 0x02 Defined in Section 8.1.5 Set or request the current temperature offset val
40、ue Priority: “High” Get/Set SetPoint 0x03 0x03 Defined in Section 8.1.6 Set or request the current temperature set point value(s) Priority: “High” Start Autonomous 0x04 0x00 Defined in Section Start a Demand Reduction cycling event per the parameters passed in the command ANSI/CEA-2045 Amendment 1 1
41、5 Payload Description Opcode1 Opcode2 Additional Payload Definitions Usage Cycling 8.1.7 Priority: “High” Terminate Autonomous Cycling 0x04 0x01 Defined in Section 8.1.8 Terminate a Demand Reduction cycling event Priority: “High” Demand Response Event Schedules 0x05 0x00 Defined in Section 8.2.1 Sen
42、d Scheduled Events Request Priority: “Not Applicable” Get/Set Commodity Read 0x06 0x00 Defined in Section 8.3.1 Get or Set(Publish) Energy Consumption Values Priority: “Not Applicable” Get/Set Commodity Subscription 0x06 0x01 Defined in Section 8.3.2 Gets the Commodity Types supported by a metering
43、device/system and the update frequency. Sets the types that are being subscribed to. Priority: “Not Applicable” ANSI/CEA-2045 Amendment 1 16 This page intentionally left blank. Consumer Technology Association Document Improvement Proposal If in the review or use of this document a potential change is made evident for safety, health or technical reasons, please email your reason/rationale for the recommended change to standardsce.org. Consumer Technology Association Technology & Standards Department 1919 S Eads Street, Arlington, VA 22202 FAX: (703) 907-7693 standardsce.org
