1、135-2016 Errata June 24, 2017 2017 ASHRAE. All rights reserved 1BACnet Errata ANSI/ASHRAE STANDARD 135-2016 A Data Communication Protocol for Building Automation and Control Networks June 24, 2017 This document lists all known errata to ANSI/ASHRAE Standard 135-2016 as of the above date. Each entry
2、is cited first by clause, then page number, except where an erratum covers more than one clause. The back page marking identifying the electronic publication of Standard 135-2016 is “Product code: D-86451 6/16”. Changes are indicated by using strikeout for text to be removed and italics for text to
3、be added, unless noted otherwise. Grey highlighting is used for marking small corrections. 1) Clause 4.1, p. 12: The list of standard datalink layer options for BACnet is misformatted. Ethernet (ISO 8802-3) Clause 7 ARCNET (ATA 878.1) Clause 8 MS/TP Cause9P l 10 LonTalk (ISO/IEC 14908.1) Clause 11 B
4、ACnet/IP Annex J BACnet/IPv6 Annex U ZigBee Annex O ZigBee Annex O 2) Table 13-7, p. 602: UNSIGNED RANGE is misplaced outside the table. The reference to Clause 13.3.9 is not shown. Table 13-7. Standardized Event Algorithms Event Algorithm Clause NONE 13.3.17. .UNSIGNED_OUT_OF_RANGE 13.3.15 UNSIGNED
5、_RANGE 13.3.9UNSIGNED_RANGE 3) Clause K.2.16, 2nd, p. 1055: Repeated word “the“. K.2.16 BIBB - Alarm and Event Management-View and Modify-A (AE-VM-A) Device A displays and modifies limits and related parameters in standard event-initiating objects. Device A shall support DS-RP-A and DS-WP-A. The A d
6、evice shall be capable of using ReadProperty to retrieve and WriteProperty to modify any of the the event and fault algorithm parameters listed in Tables K-11 and K-12. Such parameters may be present in individual properties, in event parameter properties, or in fault parameter properties. See the r
7、espective property specifications. Device A may use alternate services where support for execution of the alternate service is supported by Device B. . 135-2016 Errata June 24, 2017 2017 ASHRAE. All rights reserved 24) Clause K.2.16, 3rd, p. 1055: The word “writing“ is missing. . Devices claiming co
8、nformance to AE-VM-A shall be capable of reading, presenting and writing all standard properties in standard objects that are configuration parameters of standard event and/or fault algorithms that have high and low numerical limits, as listed in Tables K-11 and K-12. 5) Clause K.1.25 and K.1.26, p.
9、 1055: The word “Multiple“ is misspelled in the title. K.1.25 BIBB - Data Sharing-Change Of Value Mulitple Multiple-A (DS-COVM-A) K.1.26 BIBB - Data Sharing-Change Of Value Mulitple Multiple-B (DS-COVM-B) 6) Clause L.1, 1st, p. 1079: The second sentence is unclear. L.1 Operator Interface Profiles Th
10、e following table indicates which BIBBs shall be supported by the device types of this family, for each interoperability area. The B-XAWS is excluded from this table. The B-XAWS is not shown in this table and is described in Clause L.1.1. . 7) Table 12-71, p. 518, Clause 12.56.32, p. 533, Clause J.4
11、.3.2, p. 1028, and Clause J.4.5, 2nd, p. 1029: The references to J.7.8 are incorrect. Table 12-71. Properties of the Network Port Object Type Property Identifier Property Datatype Conformance Code Object_Identifier BACnetObjectIdentifier R. . .Profile_Name CharacterString O1 . . 9 Required to be pre
12、sent if the Network_Type is IPV4, Protocol_Level is BACNET_APPLICATION, and the device is capable of communicating through a NAT router as described in Clause J.7.8 J.7.5. 10 Required if Network_Type is IPV4, Protocol_Level is BACNET_APPLICATION, and the device is configured to communicate through a
13、 NAT router as described in Clause J.7.8 J.7.5. . 12.56.32 BACnet_IP_NAT_Traversal This property, of type BOOLEAN, indicates whether (TRUE) or not (FALSE) this port is configured to operate in a NAT environment, as described in Clause J.7.8 J.7.5, and the global address is indicated by the value of
14、the BACnet_IP_Global_Address property. . 135-2016 Errata June 24, 2017 2017 ASHRAE. All rights reserved 3J.4.3.2 Broadcast Distribution Table Format The BDT consists of one entry for the address of the BBMD for the local IP subnet and an entry for the BBMD on each remote IP subnet to which broadcast
15、s are to be forwarded. Each entry consists of the 6-octet B/IP address with which the BBMD is accessed and a 4-octet broadcast distribution mask. If the IP router to the subnet performs network address translation (NAT), then the BDT entry shall contain the global IP address of the IP router. The op
16、eration of BBMDs in the presence of NAT is described in Clause J.7.8 J.7.5. If messages are to be distributed on the remote IP subnet using directed broadcasts, the broadcast . J.4.5 BBMD Operation - Broadcast Distribution . address as well as to each foreign device currently in the BBMDs FDT. A BBM
17、D on a subnet with no other BACnet devices (such as a NAT-supporting BBMD, see Clause J.7.8 J.7.5) may omit the broadcast using the B/IP broadcast address. The method by which a BBMD determines whether or not other BACnet devices are present is a local matter. 8) Clause W.10, 2nd, p. 1209: The word
18、“it“ on first line of 2ndparagraph should be “its“. W.10 Representation of Metadata If metadata items are represented as part of their associated data item, they are represented in a brief “short form“ because their type is fixed and therefore assumed. The “short form“ encodes only the metadata name
19、 and its value or children. For example, when included along with it its associated data item, (e.g., /path/to/example), the minimum metadata is encoded as: 9) Clause 12.56.55, 2nd, p. 537: The reference to Clause 12 is misleading. 12.56.55 Auto_Slave_Discovery . Slave detection shall be accomplishe
20、d by the proxy device using ReadProperty services to read, at a minimum, the Device objects Protocol_Services_Supported property for each MAC address on the network connected to this port. The ReadProperty service shall use the special object instance of 4194303 as described in Clause 12 Clause 15.5
21、.2. If the device is found to support execution of the Who-Is service, it is ignored; otherwise, the device shall be added to the Slave_Address_Binding property. The slave detection algorithm shall be repeated periodically. The period at which it is repeated is a local matter. 10) Clause 21, BACnetP
22、ropertyIdentifier, p. 845: The word “see“ is missing in the numeric index for the Reliability property. BACnetPropertyIdentifier := ENUMERATED - see below for numerical order absentee-limit (244), . . zone-to (321), - -numerical order reference - see acked-transitions (0), . . - see reliability (103
23、), . . 135-2016 Errata June 24, 2017 2017 ASHRAE. All rights reserved 411) Table W-14, p. 1241: The error code WS_ERR_UNINITIALIZED is incorrect. Table W-14. Error Numbers Error Name Error Number HTTP Status Code Example Error Text . . . .WS_ERR_UNINITIALIZED_VALUE 43 403 “Data is uninitialized and
24、has no value“ . . . .12) Clause 12.10.22, Command object type, p. 209, Clause 12.11.68, Device object type, p. 220, Clause 12.12.25, Event Enrollment object type, p. 228, Clause 12.21.20, Notification Class object type, p. 288, Clause 12.25.37, Trend Log object type, p. 307, Clause 12.27.29, Event L
25、og object type, p. 322, Clause 12.28.32, Load Control object type, p. 332, Clause 12.30.35, Trend Log Multiple object type, p. 346, Clause 12.33.15, Access User object type, p. 375, Clause 12.34.12, Access Rights object type, p. 380, and Clause 12.35.26, Access Credential object type, p. 389: The Re
26、liability_Evaluation_Inhibit property language in these clauses refers to the Out_Of_Service property that does not exist in these object types. 12.X.Y Reliability_Evaluation_Inhibit This property, of type BOOLEAN, indicates whether (TRUE) or not (FALSE) reliability-evaluation is disabled in the obj
27、ect. This property is a runtime override that allows temporary disabling of reliability-evaluation. When reliability-evaluation is disabled, the Reliability property shall have the value NO_FAULT_DETECTED unless Out_Of_Service is TRUE and an alternate value has been written to the Reliability proper
28、ty. 13) Clause 15.7.3.1.2, p. 690, Clause 21, ReadAccessResult production, p. 870: The language on what to return for property identifier OPTIONAL misses the case of no optional properties are present, and no other properties were requested, so that no property value is returned for the object. 15.7
29、.3.1.2 List of Property References . The property identifier REQUIRED means that only those standard properties having a conformance code of “R“ or “W“ shall be returned. The property identifier OPTIONAL means that only those standard properties present in the object that have a conformance code “O“
30、 shall be returned. If no optional properties are present then no entries associated with the OPTIONAL property identifier shall be in the List of Results and if no other properties were requested, then the List of Results shall be present and empty. The Property_List property shall not be returned
31、when properties ALL or REQUIRED are requested. See the specification for the particular object type in Clause 12. If the property identifier ALL, REQUIRED, or OPTIONAL is specified and any of the selected properties is not readable by this service, then a Property Access Error for that property shal
32、l be returned in the List of Read Access Results as specified by Clause 15.7.3.2. 135-2016 Errata June 24, 2017 2017 ASHRAE. All rights reserved 5ReadAccessResult := SEQUENCE object-identifier 0 BACnetObjectIdentifier, list-of-results 1 SEQUENCE OF SEQUENCE property-identifier 2 BACnetPropertyIdenti
33、fier, property-array-index 3 Unsigned OPTIONAL, - used only with array datatype - if omitted with an array the entire - array is referenced read-result CHOICE property-value 4 ABSTRACT-SYNTAX. and by the American National Standards Institute on April 29, 2016. 1. . . . 1 19 Addendum ba to ANSI/ASHRA
34、E 135-2012 Approved by ASHRAE on April 29, 2016; and by the American National Standards Institute on April 29, 2016. 1. . . . 1 19 Addendum bc to ANSI/ASHRAE 135-2012 Approved by ASHRAE on April 29, 2016; and by the American National Standards Institute on April 29, 2016. 1. . . . 1 19 Addendum am t
35、o ANSI/ASHRAE 135-2012 Approved by ASHRAE on April 29, 2016; and by the American National Standards Institute on April 29, 2016. 1. . . . 1 19 Addendum ba to ANSI/ASHRAE 135-2012 Approved by ASHRAE on April 29, 2016; and by the American National Standards Institute on April 29, 2016. 1. . . . 1 19 A
36、ddendum bc to ANSI/ASHRAE 135-2012 Approved by ASHRAE on April 29, 2016; and by the American National Standards Institute on April 29, 2016. 1. . . . 22) Clause 12.53, p. 485: The Channel object type misses the statement on the event algorithm used for intrinsic reporting by this object. 12.53 Chann
37、el Object Type . . . Channel objects may optionally support intrinsic reporting to facilitate the reporting of fault conditions. Channel objects that support intrinsic reporting shall apply the NONE event algorithm. The object and its properties are summarized in Table 12-62 and described in detail
38、in this clause. . . . 135-2016 Errata June 24, 2017 2017 ASHRAE. All rights reserved 1023) Table 12-71, p. 517: Several properties should be optional, and only required if Protocol_Level is BACNET_APPLICATION. See also IR 135-2016-1. 12.56 Network Port Object Type . . . Table 12-71. Properties of th
39、e Network Port Object Type Property Identifier Property Datatype Conformance Code . . . . . . . . .Network_Number Unsigned16 R1O1, 25 Network_Number_Quality BACnetNetworkNumberQuality R O25 . . . . . . . . .APDU_Length Unsigned R O25 . . . . . . . . . 1 Required to be writable in routers, secure dev
40、ices, and any other device that requires knowledge of the network number for proper operation. . . . 24 . . . 25 Required to be present if Protocol_Level is BACNET_APPLICATION. 24) Clause 12.55, p. 508: The Binary Lighting Output object type misses the statement on the event algorithm used for intri
41、nsic reporting by this object. 12.55 Binary Lighting Output Object Type . . . Binary Lighting Output objects may optionally support intrinsic reporting to facilitate the reporting of fault conditions. Binary Lighting Output objects that support intrinsic reporting shall apply the NONE event algorith
42、m. The object and its properties are summarized in Table 12-69 and described in detail in this clause. . . . 135-2016 Errata June 24, 2017 2017 ASHRAE. All rights reserved 1125) Table 12-15, p. 223: Visible lines are missing after the row for NONE, and between OUT_OF_RANGE and SIGNED_OUT_OF_RANGE. T
43、able 12-15. Event Algorithm, Event Parameters and Event Algorithm Parameters Event Algorithm Event Parameters Event Algorithm Parameters NONE none noneACCESS_EVENT List_Of_Access_Events Access_Event_Time_Reference pAccessEvents Referents value is pAccessEventTime . . . . . . . . . OUT_OF_RANGE Time_
44、Delay Low_Limit High_Limit Deadband pTimeDelay pLowLimit pHighLimit pDeadband SIGNED_OUT_OF_RANGE Time_Delay Low_Limit High_Limit Deadband pTimeDelay pLowLimit pHighLimit pDeadband . . . . . . . . . 26) Clause 12.20, 2nd, p. 268: There is an extra space in CHANGE_OF _STATE that should be removed. 12
45、.20 Multi-state Value Object Type . . . Multi-state Value objects that support intrinsic reporting shall apply the CHANGE_OF_ STATE CHANGE_OF_STATE event algorithm. 27) Clause F.1.13, p. 969: Some encodings for the ConfirmedCOVNotificationMultiple service example are incorrect. The X27 for the Time
46、Remaining parameter does not agree with the value of 35. The binary value should be X23. The closing tags of the COV notification values should be X2F, not X2E. F.1.13 Encoding for Example E.1.13 - ConfirmedCOVNotificationMultiple Service . . . X29 SD Context Tag 2 (Time Remaining, L=1) X27 X23 35 .
47、 . . X42820000 65.0 X2E X2F PD Closing Tag 2 (Value) . . . X42A03333 80.1 X2E X2F PD Closing Tag 2 (Value) X1F PD Closing Tag 1 (List of Values)X4F PD Closing Tag 4 (List of COV Notifications) . . . 135-2016 Errata June 24, 2017 2017 ASHRAE. All rights reserved 1228) Clause 13.2.2.1.4, 1st, p. 595:
48、The example at the end of the first paragraph is incorrect. 13.2.2.1.4 Transition Actions This clause describes the actions to be taken when a transition of the event-state-detection state machine occurs. The actions are the same for all transitions and they shall be executed even if the transition
49、does not change the event state (e.g., to the ToOffNormal from the OffNormal state a transition from the OFFNORMAL event state to the OFFNORMAL event state). 29) Clause F.1.14, p. 969: The encoded PDU should be an unconfirmed request PDU. F.1.14 Encoding for Example E.1.14 - UnconfirmedCOVNotificationMultiple Service X00 PDU Type=0 (BACnet-Confirmed-Request-PDU, SEG=0, MOR=0, SA=0) X02 Maximum APDU Size Accepted=206 octets X0F Invoke ID=15 X10 PDU Type=1 (BACnet-Unconfirmed-Req
