CEN/TS 15231:2006
Withdrawn
A Withdrawn Standard is one, which is removed from sale, and its unique number can no longer be used. The Standard can be withdrawn and not replaced, or it can be withdrawn and replaced by a Standard with a different number.
Open data communication in building automation, controls and building management - Mapping between Lonworks and BACnet
20-01-2023
24-05-2006
Foreword
Introduction
1 Scope
2 Normative references
3 Terms and definitions
4 Object Structures
4.1 LONWORKS Objects (Functional Profile)
4.2 BACnet Objects
4.3 Relationship of LONWORKS to BACnet
5 Properties Needed for Mapping
5.1 Object_Identifier
5.2 Object_Name
5.3 Object_Type
5.4 Present_Value
5.5 Description
5.6 Status_Flags
5.7 Event_State
5.8 Reliability
5.9 Out_Of_Service
5.10 Units
5.11 Priority_Array
5.12 Relinquish_Default
5.13 Profile_Name
5.14 Polarity
5.15 Max_Pres_Value
5.16 Min_Pres_Value
5.17 Resolution
5.18 Number_Of_States
5.19 State_Text
5.20 System_Status
5.21 Vendor_Name
5.22 Vendor_Identifier
5.23 Model_Name
5.24 Firmware_Revision
5.25 Application_Software_Revision
5.26 Protocol_Version
5.27 Protocol_Revision
5.28 Protocol_Services_Supported
5.29 Protocol_Object_Types_Supported
5.30 Object_List
5.31 Max_APDU_Length_Accepted
5.32 Segmentation_Supported
5.33 APDU_Timeout
5.34 Number_Of_APDU_Retries
5.35 Device_Address_Binding
5.36 Database_Revision
5.37 COV_Increment
6 Mapping Rules
6.1 Mapping Rules for the BACnet Device Object Type
6.2 Mapping Rules for BACnet Analog Input Object Type
6.3 Mapping Rules for BACnet Analog Output Object Type
6.4 Mapping Rules for BACnet Analog Value Object Type
6.5 Mapping Rules for BACnet Binary Input Object Type
6.6 Mapping Rules for BACnet Binary Output Object Type
6.7 Mapping Rules for BACnet Binary Value Object Type
6.8 Mapping Rules for BACnet Multi-state Input Object Type
6.9 Mapping Rules for BACnet Multi-state Output Object Type
6.10 Mapping Rules for BACnet Multi-state Value Object Type
6.11 Mapping physical and mathematical LONWORKS SNVTs
6.12 Mapping enumerated LONWORKS SNVTs
6.13 Mapping structured LONWORKS SNVTs
6.14 Defining Proprietary Object Types
6.15 Defining Proprietary Properties
6.16 Mapping other LONWORKS SNVTs
Annex A (informative) LONMARK Standard Program ID
Bibliography
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 security applications. The BACnet communication system as well 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 and LONWORKS systems.
| Committee |
CEN/TC 247
|
| DocumentType |
Technical Specification
|
| PublisherName |
Comite Europeen de Normalisation
|
| Status |
Withdrawn
|
| Standards | Relationship |
| DIN CEN/TS 15231:2006-08 | Identical |
| XP CEN/TS 15231 : 2008 XP | Identical |
| DD CEN/TS 15231:2006 | Identical |
| PKN CEN/TS 15231 : 2007 | Identical |
| I.S. CEN/TS 15231:2006 | Identical |
| UNI CEN/TS 15231 : 2006 | Identical |
| NEN NPR CEN/TS 15231 : 2006 | Identical |
| EN 14908-1:2014 | Open Data Communication in Building Automation, Controls and Building Management - Control Network Protocol - Part 1: Protocol Stack |
| ISO 16484-5:2017 | Building automation and control systems (BACS) — Part 5: Data communication protocol |
| EN ISO 16484-5:2017 | Building automation and control systems (BACS) - Part 5: Data communication protocol (ISO 16484-5:2017) |
Access your standards online with a subscription
Features
-
Simple online access to standards, technical information and regulations.
-
Critical updates of standards and customisable alerts and notifications.
-
Multi-user online standards collection: secure, flexible and cost effective.