DIN CEN TS 15231-2006 Open data communication in building automation controls and building management - Mapping between LONWORKS and BACnet English version CEN TS 15231 2006《建筑自动化、.pdf

1、August 2006 Normenausschuss Heiz- und Raumlufttechnik (NHRS) im DINDKE Deutsche Kommission Elektrotechnik Elektronik Informationstechnik im DIN und VDEPreisgruppe 15DIN Deutsches Institut fr Normung e.V. Jede Art der Vervielfltigung, auch auszugsweise, nur mit Genehmigung des DIN Deutsches Institut

2、fr Normung e.V., Berlin, gestattet.ICS 35.240.99; 97.120!,awN“9628443www.din.deDVornormDIN CEN/TS 15231Offene Datenkommunikation fr die Gebudeautomation undGebudemanagement Gegenseitige Abbildung von LONWORKS- und BACnet-Objekten;Englische Fassung CEN/TS 15231:2006Open data communication in building

3、 automation, controls and building management Mapping between LONWORKS and BACnet;English version CEN/TS 15231:2006Rseau ouvert de communication de donnes pour lautomatisation, la rgulation et lagestion technique du btiment Intgration des fonctionnalits (mapping) entre LONWorks et BACnet;Version ang

4、laise CEN/TS 15231:2006Alleinverkauf der Normen durch Beuth Verlag GmbH, 10772 Berlin www.beuth.deGesamtumfang 37 SeitenDIN CEN/TS 15231:2006-08 2 Nationales Vorwort Dieses Dokument (CEN/TS 15231:2006) wurde im Technischen Komitee CEN/TC 247 Gebudeautomation und Gebudemanagement“, dessen Sekretariat

5、 vom SNV (Schweiz) gehalten wird, erarbeitet. Der Arbeitsausschuss NHRS NA 041-03-68 AA Systemneutrale Datenbertragung fr HLK-Anwendungen“ des Normenausschusses Heiz- und Raumlufttechnik (NHRS) im DIN Deutsches Institut fr Normung e. V. war als deutscher Spiegelausschuss ber die Erstellung dieses Do

6、kuments informiert. Eine Vornorm ist das Ergebnis einer Normungsarbeit, das wegen bestimmter Vorbehalte zum Inhalt oder wegen des gegenber einer Norm abweichenden Aufstellungsverfahrens vom DIN noch nicht als Norm herausgegeben wird. Zur vorliegenden Vornorm wurde kein Entwurf verffentlicht. Erfahru

7、ngen mit dieser Vornorm sind erbeten an vorzugsweise als Datei per E-Mail an nhrsdin.de in Form einer Tabelle. Die Vorlage dieser Tabelle kann im Internet unter http:/www.din.de/stellungnahme abgerufen werden; oder in Papierform an den Normenausschuss Heiz- und Raumlufttechnik (NHRS) im DIN, 10772 B

8、erlin (Hausanschrift: Burggrafenstr. 6, 10787 Berlin). Dieses Dokument (CEN/TS 15231:2006) mit dem Titel Offene Datenkommunikation fr die Gebudeautomation und Gebudemanagement Gegenseitige Abbildung von LONWORKS- und BACnet-Objekten wurde unverndert im englischen Originaltext bernommen. Da davon aus

9、zugehen ist, dass die Fachleute der Kommunikationstechnik sich bereits mit der englischen Fassung befasst haben, wurde von einer bersetzung ins Deutsche abgesehen. Nach dem DIN Prsidiumsbeschluss 13/1983 ist insbesondere auf dem Gebiet der Informatik die Verffentlichung in Englisch zulssig, insbeson

10、dere wenn dadurch Fehler bei der bertragung vermieden werden knnen. Vornorm TECHNICAL SPECIFICATION SPCIFICATION TECHNIQUE TECHNISCHE SPEZIFIKATION CEN/TS 15231 May 2006 ICS 35.240.99 English Version Open data communication in building automation, controls and building management Mapping between LON

11、WORKS and BACnet Rseau ouvert de communication de donnes pour lautomatisation, la rgulation et la gestion technique du btiment Intgration des fonctionnalits (mapping) entre LONWorks et BACnet Offene Datenkommunikation fr die Gebudeautomation und Gebudemanagement Gegenseitige Abbildung von LONWORKS-

12、und BACnet-Objekten This Technical Specification (CEN/TS) was approved by CEN on 22 August 2005 for provisional application. The period of validity of this CEN/TS is limited initially to three years. After two years the members of CEN will be requested to submit their comments, particularly on the q

13、uestion whether the CEN/TS can be converted into a European Standard. CEN members are required to announce the existence of this CEN/TS in the same way as for an EN and to make the CEN/TS available promptly at national level in an appropriate form. It is permissible to keep conflicting national stan

14、dards in force (in parallel to the CEN/TS) until the final decision about the possible conversion of the CEN/TS into an EN is reached. CEN members are the national standards bodies of Austria, Belgium, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Irel

15、and, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland and United Kingdom. EUROPEAN COMMITTEE FOR STANDARDIZATION COMIT EUROPEN DE NORMALISATION EUROPISCHES KOMITEE FR NORMUNG Management Centre: rue de Stassart

16、, 36 B-1050 Brussels 2006 CEN All rights of exploitation in any form and by any means reserved worldwide for CEN national Members. Ref. No. CEN/TS 15231:2006: ECEN/TS 15231:2006 (E) 2 Contents Page Foreword4 Introduction .5 1 Scope 6 2 Normative references 6 3 Terms and definitions .6 4 Object Struc

17、tures.7 4.1 LONWORKS Objects (Functional Profile) .7 4.2 BACnet Objects8 4.3 Relationship of LONWORKS to BACnet8 5 Properties Needed for Mapping .9 5.1 Object_Identifier.9 5.2 Object_Name. 10 5.3 Object_Type 10 5.4 Present_Value . 10 5.5 Description 11 5.6 Status_Flags 11 5.7 Event_State . 11 5.8 Re

18、liability. 11 5.9 Out_Of_Service. 11 5.10 Units . 11 5.11 Priority_Array 16 5.12 Relinquish_Default . 16 5.13 Profile_Name. 16 5.14 Polarity. 16 5.15 Max_Pres_Value 16 5.16 Min_Pres_Value 16 5.17 Resolution . 16 5.18 Number_Of_States 16 5.19 State_Text 17 5.20 System_Status 17 5.21 Vendor_Name 17 5.

19、22 Vendor_Identifier 17 5.23 Model_Name 17 5.24 Firmware_Revision. 17 Vornorm CEN/TS 15231:2006 (E) 3 Page 5.25 Application_Software_Revision.17 5.26 Protocol_Version.18 5.27 Protocol_Revision.18 5.28 Protocol_Services_Supported .18 5.29 Protocol_Object_Types_Supported 18 5.30 Object_List .18 5.31 M

20、ax_APDU_Length_Accepted .18 5.32 Segmentation_Supported.18 5.33 APDU_Timeout 18 5.34 Number_Of_APDU_Retries.18 5.35 Device_Address_Binding .18 5.36 Database_Revision18 5.37 COV_Increment18 6 Mapping Rules .19 6.1 Mapping Rules for the BACnet Device Object Type 19 6.2 Mapping Rules for BACnet Analog

21、Input Object Type 19 6.3 Mapping Rules for BACnet Analog Output Object Type .20 6.4 Mapping Rules for BACnet Analog Value Object Type .21 6.5 Mapping Rules for BACnet Binary Input Object Type .21 6.6 Mapping Rules for BACnet Binary Output Object Type 22 6.7 Mapping Rules for BACnet Binary Value Obje

22、ct Type 22 6.8 Mapping Rules for BACnet Multi-state Input Object Type 23 6.9 Mapping Rules for BACnet Multi-state Output Object Type .23 6.10 Mapping Rules for BACnet Multi-state Value Object Type .24 6.11 Mapping physical and mathematical LONWORKS SNVTs24 6.12 Mapping enumerated LONWORKS SNVTs .29

23、6.13 Mapping structured LONWORKS SNVTs31 6.14 Defining Proprietary Object Types 31 6.15 Defining Proprietary Properties .31 6.16 Mapping other LONWORKS SNVTs.33 Annex A (informative) LONMARK Standard Program ID 34 Bibliography35 Vornorm CEN/TS 15231:2006 (E) 4 Foreword This Technical Specification (

24、CEN/TS 15231:2006) has been prepared by Technical Committee CEN/TC 247 “Building automation, controls and building management”, the secretariat of which is held by SNV. This publication is copyright under the Berne Convention and the Universal Copyright Convention. No part of this publication may be

25、 reproduced, stored in a retrieval system, or transmitted, in any form or by means, electronic, mechanical, photocopying, recording, or otherwise, without the permission of the European Committee for Standardization (CEN), the European Committee for Electrotechnical Standardization (CENELEC), their

26、National Standards Bodies and their Licensees to reproduce this document in full and including this copyright notice for the purposes of European standardisation. This technical specification covers the methods of mapping LONWORKS objects and services to BACnet objects and services and vice versa. T

27、he LONWORKS objects and services are defined in the standard EN 14908-1 “Control Network Protocol“ and the BACnet objects and services are defined in the standard EN ISO 16484-5 “Data Communication Protocol“. According to the CEN/CENELEC Internal Regulations, the national standards organizations of

28、the following countries are bound to announce this CEN Technical Specification: Austria, Belgium, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovak

29、ia, Slovenia, Spain, Sweden, Switzerland and United Kingdom. Vornorm CEN/TS 15231:2006 (E) 5 Introduction This Technical Specification specifies methods for the mapping of objects and services of the Control Network Protocol (CNP) , called LONWORKS (see EN 14908-1), and the Data communication protoc

30、ol, called BACnet (see EN ISO 16484-5), for exchanging information between both systems. This Technical Specification has been prepared to provide mechanisms through which various vendors of building automation, control, and building-management systems, may exchange information in a standardised way

31、 between both LONWORKS and BACnet communication systems. It specifies communication and internal-documentation requirements. This Technical Specification is for use by all involved in design, manufacture, engineering, installation, and commissioning activities; and has been made in response to the e

32、ssential requirements of the Construction Products Directive. Vornorm CEN/TS 15231:2006 (E) 6 1 Scope The LONWORKS communication system is widely used in building automation systems for field-level and application-level functions for residential and non-residential controls in lighting, sun protecti

33、on, HVAC, energy management and security applications. The BACnet communication system is also used in building automation systems for management-level and application-level functions. This Technical Specification defines the methods for combining BACnet networks with LONWORKS networks, and standard

34、izes the interface between BACnet and LONWORKS systems. 2 Normative references The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (inclu

35、ding any amendments) applies. EN ISO 16484-5:2003, Building automation and control systems Part 5: Data communication protocolcity (ISO 16484-5:2003). prEN 14908-5, Open Data Communication in Building Automation Controls and Building Management Control Network Protocol Part 5: Implementation Guideli

36、ne. 3 Terms and definitions For the purposes of this Technical Specification, the following terms and definitions apply. 3.1 Functional Profile FP A template that describes common units of functional behaviour. Functional profiles are also known as profiles, or FPs; which can be represented with a m

37、achine-readable functional-profile template (FPT). Standard functional profiles are also known as LONMARK profiles. Each functional profile consists of a profile description and a specified set of network variables and configuration properties designed to perform a single function on a device. The n

38、etwork variables and configuration properties specified by the functional profile are called the functional-profile members. A functional profile specifies whether the implementation of each functional-profile member is mandatory or optional. A profile is uniquely identified by a program-ID template

39、, scope, and functional-profile number. 3.2 LONWORKS LONWORKS is the name of the whole technology used in LONWORKS. It describes the language, the transceivers and the Neuron Chips. The communication is typically based on network variables organized in functional profiles, which are standardized by

40、LONMARK International. 3.3 LONMARK International LONMARK Internationals mission is to enable the easy integration of multi-vendor systems based on CNP networks. LONMARK INTERNATIONAL provides an open forum for member companies to work together on marketing and technical programs to promote the avail

41、ability of open, interoperable control devices. 3.4 Network Variable NV A data item that a particular device application program expects to get from other devices on a network (an input network variable) or expects to make available to other devices on a network (an output network Vornorm CEN/TS 152

42、31:2006 (E) 7 variable). Examples are a temperature, switch value, and actuator position setting. Network variable data is typically stored in a devices volatile memory. 3.5 Node A node is a physical device in LONWORKS. Each LONWORKS device can be a member of maximum two domains. In each domain a ma

43、ximum number of 255 subnets with 127 devices each can be addressed. 3.6 Standard Configuration Property Type SCPT A configuration property type that has been standardized by LONMARK International. A SCPT is a standardized definition of the units, scaling, encoding, valid range, and meaning of the co

44、ntents of configuration properties. 3.7 Standard Network Variable Type SNVT A network variable type that has been standardized by LONMARK International. 4 Object Structures 4.1 LONWORKS Objects (Functional Profile) 4.1.1 General The primary function of a LONMARK certified device must be implemented

45、using one or more LONMARK profiles which represent the application layer interface of the node. Functional Profiles are divided into mandatory and optional network variables, configuration properties, and a manufacturer defined section that is non-interoperable. They are based on six standard object

46、s listed below. Table 1 Standard LONWORKS Objects Standard Objects Function Node Object Monitoring on functions inside a single node; scanning from status- and alert functions Open Loop Sensor Object Detecting devices, measuring absolute values without feedback (temperature sensor, digital contact)

47、Closed Loop Sensor Object Detecting devices with feedback, making a check on an actor object using several sensor objects or vice versa Open Loop Actuator Object Operating devices without feedback Closed Loop Actuator Object Operating devices with feedback Controller Object Control algorithms Vornor

48、m CEN/TS 15231:2006 (E) 8 4.1.2 Node Object The Node Object in a LONWORKS node implements the application-level network management of the node as a whole. It contains two mandatory network variables (nvi_request and nvo_status). 4.1.3 Sensor Object Sensor objects are generic objects that can be used

49、 with any form of sensor for analog values such as temperature, pressure, humidity or for digital values of switches or buttons. Via an output network variable nvoValue the data can be supplied directly to an actuator object or to a control loop located within a controller object. 4.1.4 Actuator Object The actuator objects are generic objects that may be used with any type of actuator, such as a valve, a light dimmer or a motor. They may be controlled by a remote controller o