1、BS EN14908-5:2009ICS 35.240.99; 91.140.01; 97.120NO COPYING WITHOUT BSI PERMISSION EXCEPT AS PERMITTED BY COPYRIGHT LAWBRITISH STANDARDOpen DataCommunication inBuilding Automation,Controls andBuilding ManagementImplementationGuideline ControlNetwork ProtocolPart 5: ImplementationThis British Standar
2、dwas published under theauthority of the StandardsPolicy and StrategyCommittee on 30 June2009. BSI 2009ISBN 978 0 580 56866 4Amendments/corrigenda issued since publicationDate CommentsBS EN 14908-5:2009National forewordThis British Standard is the UK implementation of EN 14908-5:2009.The UK particip
3、ation in its preparation was entrusted to TechnicalCommittee RHE/16, Performance requirements for control systems.A list of organizations represented on this committee can be obtained onrequest to its secretary.This publication does not purport to include all the necessary provisionsof a contract. U
4、sers are responsible for its correct application.Compliance with a British Standard cannot confer immunityfrom legal obligations.BS EN 14908-5:2009EUROPEAN STANDARDNORME EUROPENNEEUROPISCHE NORMEN 14908-5April 2009ICS 35.240.99; 91.140.01English VersionOpen Data Communication in Building Automation,
5、 Controls andBuilding Management Implementation Guideline - ControlNetwork Protocol - Part 5: ImplementationRseau ouvert de communication de donnes pourlautomatisation, la rgulation et la gestion technique dubtiment - Protocole de rseau pour le btiment - Partie 5 :ImplmentationFirmenneutrale Datenko
6、mmunikation fr dieGebudeautomation und Gebudemanagement - GebudeNetzwerk Protokoll - Teil 5: ImplementierungThis European Standard was approved by CEN on 1 September 2007.CEN members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this European
7、Standard the status of a national standard without any alteration. Up-to-date lists and bibliographical references concerning such nationalstandards may be obtained on application to the CEN Management Centre or to any CEN member.This European Standard exists in three official versions (English, Fre
8、nch, German). A version in any other language made by translationunder the responsibility of a CEN member into its own language and notified to the CEN Management Centre has the same status as theofficial versions.CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Cyprus, C
9、zech Republic, Denmark, Estonia, Finland,France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal,Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland and United Kingdom.EUROPEAN COMMITTEE FOR STANDARDIZATIONCOMIT EUROP
10、EN DE NORMALISATIONEUROPISCHES KOMITEE FR NORMUNGManagement Centre: Avenue Marnix 17, B-1000 Brussels 2009 CEN All rights of exploitation in any form and by any means reservedworldwide for CEN national Members.Ref. No. EN 14908-5:2009: EBS EN 14908-5:2009EN 14908-5:2009 (E) 2 Contents Page Foreword
11、. 5 Introduction 6 1 Scope 7 2 Normative references . 7 3 Terms and definitions 7 3.1 application set 7 3.2 base type 7 3.3 changeable-type network variable 8 3.4 configuration property CP . 8 3.5 configuration-property member 8 3.6 configuration-property member number . 8 3.7 configuration-property
12、 type index . 8 3.8 device . 8 3.9 device channel ID . 8 3.10 device class 8 3.11 device interface 8 3.12 device-location field . 9 3.13 device self-documentation string DSDS . 9 3.14 device subclass 9 3.15 dynamic functional block . 9 3.16 dynamic network variable 9 3.17 format . 9 3.18 functional
13、block 9 3.19 functional-block index . 9 3.20 functional profile FP . 9 3.21 functional-profile key . 10 3.22 functional-profile member . 10 3.23 functional-profile member number 10 3.24 functional-profile number 10 3.25 functional-profile selector 10 3.26 functional-profile template . 11 3.27 global
14、 index 11 3.28 inheriting profile . 11 3.29 interoperability . 11 3.30 CNP device . 11 3.31 CNP network . 11 3.32 manufacturer ID MID 11 3.33 network-interface selection . 11 3.34 network variable NV . 12 3.35 network-variable declaration . 12 3.36 network-variable index . 12 3.37 network-variable m
15、ember 12 3.38 network-variable member number 12 3.39 network-variable programmatic name 12 3.40 network-variable selection . 12 BS EN 14908-5:2009EN 14908-5:2009 (E) 3 3.41 network-variable type . 12 3.42 network-variable type index . 13 3.43 unique node ID . 13 3.44 node 13 3.45 passive configurati
16、on tool PCT . 13 3.46 primary functional block 13 3.47 primary functional profile. 13 3.48 proprietary data 13 3.49 self-documentation string SD string . 13 3.50 self-documentation text . 14 3.51 shared-media channel 14 3.52 standard configuration-property type SCPT . 14 3.53 standard network-variab
17、le type SNVT . 14 3.54 standard program ID SPID . 14 3.55 static functional block 14 3.56 static network variable . 14 3.57 subsystem 14 3.58 successful commissioning 15 3.59 system 15 3.60 unconfigured device 15 3.61 usage 15 3.62 usage ID 15 3.63 user data . 15 3.64 wink function 15 4 Device Inter
18、faces 15 4.1 General . 15 4.2 Unique Node ID . 16 4.3 Standard Program ID 17 4.3.1 General . 17 4.3.2 Format Field 17 4.3.3 Manufacturer Field . 17 4.3.4 Device Class Field 17 4.3.5 Usage Field . 17 4.3.6 Channel Type Field . 18 4.3.7 Model Number Field . 18 4.4 Device Channel ID 19 4.5 Device Locat
19、ion Field . 19 4.6 Device Self-Documentation String (DSDS) 20 4.7 Functional Blocks 21 4.7.1 General . 21 4.7.2 Implementing a Functional Block 22 4.7.3 Network Variables 23 4.7.4 Configuration Properties . 30 4.8 Device and Functional Block Versioning 39 4.9 Device Interface (XIF) File 40 5 Resourc
20、e Files 40 5.1 Resource File Definitions . 40 5.1.1 General . 40 5.1.2 Type Definitions . 42 5.1.3 Functional Profiles . 44 5.1.4 Language Strings . 46 5.1.5 Formats . 47 5.2 Identifying Appropriate Resources . 50 5.2.1 Standard and User Resources . 50 BS EN 14908-5:2009EN 14908-5:2009 (E) 4 5.2.2 U
21、sing Standard Resources 51 5.2.3 Using User Resources . 51 6 Network Installation . 52 6.1 General . 52 6.2 Network Addressing 52 6.2.1 Network Addressing Scheme 52 6.2.2 Address-Table Entries . 53 6.2.3 Network Variable Aliases . 54 6.2.4 Domain-Table Entries. 54 6.2.5 Self-Installed Devices. 54 6.
22、2.6 Field-Installed Devices . 55 6.3 Passive Configuration Tools . 55 6.4 Service Pin 56 6.5 Gateways to Command-Based Systems . 56 6.6 Shared-Media Considerations . 57 Bibliography 58 BS EN 14908-5:2009EN 14908-5:2009 (E) 5 Foreword This document (EN 14908-5:2009) has been prepared by Technical Com
23、mittee CEN/TC 247 “Building automation and controls and building management”, the secretariat of which is held by SNV. This European Standard shall be given the status of a national standard, either by publication of an identical text or by endorsement, at the latest by October 2009, and conflicting
24、 national standards shall be withdrawn at the latest by October 2009. This standard is part of a series of standards for open data transmission in building automation, control and in building management systems. The content of this standard covers the data communications used for management, automat
25、ion/control and field functions. The EN 14908-5 is part of a series of European Standards under the title, Open Data Communication in Building Automation, Controls and Building Management Control Network Protocol (CNP), which comprises the following parts: Part 1: Protocol Stack Part 2: Twisted Pair
26、 Communication Part 3: Power Line Channel Specification Part 4: IP Communication Part 5: Implementation Part 6: Application elements Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. CEN and/or CENELEC shall not be held responsible
27、for identifying any or all such patent rights. According to the CEN/CENELEC Internal Regulations, the national standards organizations of the following countries are bound to implement this European Standard: Austria, Belgium, Bulgaria, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germ
28、any, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland and the United Kingdom. BS EN 14908-5:2009EN 14908-5:2009 (E) 6 Introduction This document specifies the Layered Impleme
29、ntation Guidelines (LIG) for the Control Network Protocol (CNP) Specification: EN 14908-1:2005. The CNP specification model is based on the ISO Open Systems Interconnection Reference Model. There are also important extensions to the 7-layer OSI Reference Model. Figure 1 shows the scope of this speci
30、fication in reference to the CNP and companion specifications for handling various data-transport media at the lower ISO protocol layers. A dashed line is used to show that the scope of this document is not treated as redundant, compared with other specifications covering their respective layers but
31、 as a complement to those specifications in implementing them in an interoperable fashion. In this document, the guidelines for implementing a device based on CNP are specified to increase the ability for devices to interoperate regardless of the installer or manufacturer of the devices. Anything ou
32、tside this boundary is covered in other parts of the standard. Similar specifications exist for CNP data-transport media. This standard has been prepared to provide mechanisms through which various vendors of building automation, control, and of building-management systems, may exchange information
33、in a standardised way. It defines communication and internal-documentation requirements. This standard is contributing to the general European policy for energy savings particularly in the field of the “Energy Performance of Building Directive” and the Construction Products Directive (ER No. 6 “Ener
34、gy Economy and Heat Retention”). Figure 1 Scope of this specification BS EN 14908-5:2009EN 14908-5:2009 (E) 7 1 Scope This specification provides mechanisms through which various vendors of networked control systems in commercial building automation, control, and building management may exchange inf
35、ormation in a standardised way. This specification contains all the information necessary to facilitate the exchange of data and control information in an interoperable fashion using EN 14908-1 and its associated data-transport media specifications. This specification establishes a minimal set of ru
36、les for compliance. It does not rule-out extended services to be provided, given that the rules are adhered-to within the system. It is the intention of the standard to permit extended services to coexist and defines the bounds in which those services function, including the format for internal devi
37、ce-documentation of those services. Services outside purvey of this specification so long as they are adherents of the system are permitted but will not necessarily be interoperable with any other devices and shall not be essential for the functioning of the device. Certain aspects of this standard
38、are defined in other documents. These documents are referenced where relevant. In the case where a referenced standard conflicts with this document, this document will prevail. 2 Normative references The following referenced documents are indispensable for the application of this document. For dated
39、 references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. EN 14908-1:2005 Open Data Communication in Building Automation, Controls and Building Management Control Network Protocol Part 1: Protocol Stack prEN
40、 14908-6, Open Data Communication in Building Automation, Controls and Building Management Control Network Protocol Part 6: Application elements 3 Terms and definitions For the purposes of this document, the terms and definitions given in EN 14908-1:2005 and the following apply. 3.1 application set
41、function block or function blocks to which a configuration property applies EXAMPLE A network variable, a series or compilation of network variables, a functional block, a series or compilation of functional blocks, or the entire device. 3.2 base type fundamental type that can be used as the basis o
42、f a network-variable type or configuration-property type NOTE The available base types are defined in 5.1.2.2. BS EN 14908-5:2009EN 14908-5:2009 (E) 8 3.3 changeable-type network variable network variable whose type can be changed during installation NOTE See 4.7.3.3. 3.4 configuration property CP d
43、ata value used to configure the application program in a device NOTE Configuration properties are used to set parameters such as maximum, minimum, default, and override values. CPs are implemented using configuration network variables or as data items within configuration files. Configuration-proper
44、ty data are kept in a devices non-volatile memory. 3.5 configuration-property member part of a functional profile NOTE See 3.22. 3.6 configuration-property member number part of a functional profile NOTE See 3.23. 3.7 configuration-property type index 16-bit number that uniquely identifies a configu
45、ration-property type within the scope defined by the scope number and program-ID template of the resource file that contains the configuration-property type definition 3.8 device logical and physical entity of the network containing an application that is designed to communicate with other logical a
46、nd physical entities 3.9 device channel ID number that optionally specifies the channel to which a device is attached 3.10 device class two-byte field identifying the primary function of a device and part of the SPID of the device 3.11 device interface network-visible interface to a device consistin
47、g of the unique node ID, program ID, channel ID, location field, device self-documentation string, device configuration properties, and functional blocks BS EN 14908-5:2009EN 14908-5:2009 (E) 9 3.12 device-location field string or number that optionally specifies the location of a device 3.13 device
48、 self-documentation string DSDS string that specifies the structure of the contents of the self-documentation strings, the functional blocks, and optionally describes the function of a device 3.14 device subclass two-byte field specifying the usage in the first byte and the channel type in the secon
49、d byte and is part of the SPID of a device NOTE See the usage and channel-type definitions. 3.15 dynamic functional block functional block that is added to a device by a network tool after the device is installed 3.16 dynamic network variable network variable that is added to a device by a network tool after the device is installed 3.17 format four-bit value defining the structure of the program ID as being a Standard Program Identifier (SPID) and device self-documentation string (DSDS) in the device string that provides formatting instructions for a networ
