1、Page 1 of 1 2016 ASHRAE. All Rights reserved. INTERPRETATION IC 135-2016-1 OF ANSI/ASHRAE STANDARD 135-2016 BACnet - A Data Communication Protocol for Building Automation and Control Networks Approval Date: July 21, 2016 Request from: Carl Neilson, Delta Controls, 17850 56thAve., Surrey, BC V3S1C7.
2、Reference: This request for interpretation refers to the requirements presented in ANSI/ASHRAE Standard 135-2016, Clause 12.56, regarding the Network Port object. Background: The description of the Network Port object type is conflicted with respect to whether or not the Network_Number, Network_Numb
3、er_Quality and APDU_Length properties are required. In Table 12-71, “Properties of the Network Port Object Type” these properties are marked with the conformance code R (required). In Table 12-74, “Properties of the Network Port Object Type Only Used when Protocol_Level is BACNET_APPLICATION” these
4、properties are listed, thus implying that the properties are optional (not present in Network Port object whose Protocol_Level is not BACNET_APPLICATION). In Figure 12-20, “Example Network Port Hierarchy Chain Showing Property Inheritance” these properties are only present in the Network Port object
5、 with a Protocol_Level of BACNET_APPLICATION. These properties were required in the original Network Port object description (Protocol_Revision 17) and there was no conflict in the language. The changes made to the Network Port object description in addendum 135-2012bf added in the conflicting table
6、 and figures and as such it appears that the intent was to make these properties optional in the manner described by Table 12-74 and Figure 12-20. Interpretation: The Network_Number, Network_Number_Quality and APDU_Length properties are required in Network Port objects with a Protocol_Level of BACNET_APPLICATION, and are not present in Network Port objects with a Protocol_Level other than BACNET_APPLICATION. Question: Is this Interpretation correct? Answer: Yes
