1、DRAFT FOR DEVELOPMENTDD CEN/TS 15231:2006Open data communication in building automation, controls and building management Mapping between Lonworks and BACnetICS 35.240.99g49g50g3g38g50g51g60g44g49g42g3g58g44g55g43g50g56g55g3g37g54g44g3g51g40g53g48g44g54g54g44g50g49g3g40g59g38g40g51g55g3g36g54g3g51g4
2、0g53g48g44g55g55g40g39g3g37g60g3g38g50g51g60g53g44g42g43g55g3g47g36g58DD CEN/TS 15231:2006This Draft for Development was published under the authority of the Standards Policy and Strategy Committee on 29 December 2006 BSI 2006ISBN 0 580 49889 1National forewordThis Draft for Development was publishe
3、d by BSI. It is the UK implementation of CEN/TS 15231:2006. This publication is not to be regarded as a British Standard.It is being issued in the Draft for Development series of publications and is of a provisional nature. It should be applied on this provisional basis, so that information and expe
4、rience of its practical application can be obtained.Comments arising from the use of this Draft for Development are requested so that UK experience can be reported to the European organization responsible for its conversion to a European standard. A review of this publication will be initiated not l
5、ater than 3 years after its publication by the European organization so that a decision can be taken on its status. Notification of the start of the review period will be made in an announcement in the appropriate issue of Update Standards.According to the replies received by the end of the review p
6、eriod, the responsible BSI Committee will decide whether to support the conversion into a European Standard, to extend the life of the Technical Specification or to withdraw it. Comments should be sent to the Secretary of the responsible BSI Technical Committee at British Standards House, 389 Chiswi
7、ck High Road, London W4 4AL.The UK participation in its preparation was entrusted to Technical Committee RHE/16, Performance requirements for control systems.A list of organizations represented on RHE/16 can be obtained on request to its secretary.This publication does not purport to include all the
8、 necessary provisions of a contract. Users are responsible for its correct application.Amendments issued since publicationAmd. No. Date CommentsTECHNICAL SPECIFICATIONSPCIFICATION TECHNIQUETECHNISCHE SPEZIFIKATIONCEN/TS 15231May 2006ICS 35.240.99English VersionOpen data communication in building aut
9、omation, controls andbuilding management - Mapping between Lonworks and BACnetRseau ouvert de communication de donnes pourlautomatisation, la rgulation et la gestion technique dubtiment - Intgration des fonctionnalits (mapping) entreLONWorks et BACnetOffene Datenkommunikation fr die Gebudeautomation
10、und Gebudemanagement - Gegenseitige Abbildung vonLONWORKS- und BACnet-ObjektenThis 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
11、requested to submit theircomments, particularly on the question 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 availablepromptly at national level in an appropriate for
12、m. It is permissible to keep conflicting national standards 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, Finl
13、and, 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 EUROPEN DE NORMALISATIONEUROPISCHES KOMITE
14、E FR NORMUNGManagement Centre: rue de Stassart, 36 B-1050 Brussels 2006 CEN All rights of exploitation in any form and by any means reservedworldwide for CEN national Members.Ref. No. CEN/TS 15231:2006: E2 Contents Page Foreword4 Introduction .5 1 Scope 6 2 Normative references 6 3 Terms and definit
15、ions .6 4 Object Structures.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 E
16、vent_State . 11 5.8 Reliability. 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
17、5.21 Vendor_Name 17 5.22 Vendor_Identifier 17 5.23 Model_Name 17 5.24 Firmware_Revision. 17 CEN/TS 15231:20063 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.
18、31 Max_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 Ana
19、log 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
20、Object 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
21、.29 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 CEN/TS 15231:20064 Foreword This Technical Specification (CEN/TS 15
22、231: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 reproduc
23、ed, 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 National
24、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. The LONWOR
25、KS 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 the follo
26、wing 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, Slovakia, Slove
27、nia, Spain, Sweden, Switzerland and United Kingdom. CEN/TS 15231:20065 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 protocol, called BACnet (see
28、 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 between both LONWORKS
29、 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 essential requirements
30、of the Construction Products Directive. CEN/TS 15231:20066 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 protection, HVAC, energy management and sec
31、urity 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 standardizes the interface between BACnet a
32、nd 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 (including any amendments) applies. EN IS
33、O 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 Guideline. 3 Terms and definitions F
34、or 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 machine-readable functional-pr
35、ofile 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 network variables and configur
36、ation 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, scope, and functional-profi
37、le 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 LONMARK International. 3.3 LO
38、NMARK 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 availability of open, interoperabl
39、e 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 CEN/TS 15231:20067 variable). Examples are a te
40、mperature, 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 maximum number of 255 subnets with 127 devic
41、es 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 contents of configuration properties. 3.7 St
42、andard 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 using one or more LONMARK profiles which r
43、epresent 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 objects listed below. Table 1 Standard LONWORKS
44、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) Closed Loop Sensor Object Detecting devices
45、 with feedback, making a check on an actor objectusing 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 CEN/TS 15231:20068 4.1.2 Node Object The Node Obje
46、ct 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 with any form of sensor for analog values such as temper
47、ature, 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
48、used with any type of actuator, such as a valve, a light dimmer or a motor. They may be controlled by a remote controller object or directly by a sensor object. 4.1.5 Closed Loop Object A closed loop object gives a feedback to the sensor objects. It is used to synchronize sensor(s) and actuator(s).
49、4.1.6 Controller Object A controller object is used for complex algorithms to control actuator(s). The controller object is not part of the prEN14908-5 standard. 4.1.7 Analog Output Object The analog output object is used to integrate devices that do not have the ability to interface directly to LONWORKS, but rather utilize an analog output conversion device that is LONMARK compliant. 4.1.8 Analog Input Object The analog input object is used to integrate devices that do not have the ability to interface directly to LONWORKS, but rather utilize an analog input conversi
