Bsi bs en 50090 3 3 2009

Licensed Copy: athen reading, Reading University Library, 24/01/2010 04:42, Uncontrolled Copy, (c) BSI BS EN 50090-3-3:2009 BSI Standards Publication Home and Building Electronic Systems (HBES) — Part 3-3: Aspects of application — HBES Interworking model and common HBES data types NO COPYING WITHOUT BSI PERMISSION EXCEPT AS PERMITTED BY COPYRIGHT LAW raising standards worldwide™ BRITISH STANDARD Licensed Copy: athen reading, Reading University Library, 24/01/2010 04:42, Uncontrolled Copy, (c) BSI BS EN 50090-3-3:2009 National foreword This British Standard is the UK implementation of EN 50090-3-3:2009 The UK participation in its preparation was entrusted to Technical Committee IST/6, Data communications A list of organizations represented on this committee can be obtained on request to its secretary This publication does not purport to include all the necessary provisions of a contract Users are responsible for its correct application © BSI 2010 ISBN 978 580 64399 ICS 97.120 Compliance with a British Standard cannot confer immunity from legal obligations This British Standard was published under the authority of the Standards Policy and Strategy Committee on 31 January 2010 Amendments issued since publication Amd No Date Text affected Licensed Copy: athen reading, Reading University Library, 24/01/2010 04:42, Uncontrolled Copy, (c) BSI BS EN 50090-3-3:2009 EUROPEAN STANDARD EN 50090-3-3 NORME EUROPÉENNE May 2009 EUROPÄISCHE NORM ICS 97.120 English version Home and Building Electronic Systems (HBES) Part 3-3: Aspects of application HBES Interworking model and common HBES data types Systèmes électroniques pour les foyers domestiques et les bâtiments (HBES) Partie 3-3: Aspects de l'application Modèle d'inter-fonctionnement des HBES et types de données communes Elektrische Systemtechnik für Heim und Gebäude (ESHG) Teil 3-3: Anwendungsaspekte ESHG-Interworking-Modell und übliche ESHG-Datenformate This European Standard was approved by CENELEC on 2008-12-01 CENELEC members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this European Standard the status of a national standard without any alteration Up-to-date lists and bibliographical references concerning such national standards may be obtained on application to the Central Secretariat or to any CENELEC member This European Standard exists in two official versions (English, French) A version in any other language made by translation under the responsibility of a CENELEC member into its own language and notified to the Central Secretariat has the same status as the official versions CENELEC members are the national electrotechnical committees of Austria, Belgium, Bulgaria, Cyprus, the Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, the Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland and the United Kingdom CENELEC European Committee for Electrotechnical Standardization Comité Européen de Normalisation Electrotechnique Europäisches Komitee für Elektrotechnische Normung Central Secretariat: Avenue Marnix 17, B - 1000 Brussels © 2009 CENELEC - All rights of exploitation in any form and by any means reserved worldwide for CENELEC members Ref No EN 50090-3-3:2009 E Licensed Copy: athen reading, Reading University Library, 24/01/2010 04:42, Uncontrolled Copy, (c) BSI BS EN 50090-3-3:2009 EN 50090-3-3:2009 -2- Foreword This European Standard was prepared by the Technical Committee CENELEC TC 205, Home and Building Electronic Systems (HBES), joined by the co-operating partner KNX Association The text of the draft was submitted to the Unique Acceptance Procedure and was approved by CENELEC as EN 50090-3-3 on 2008-12-01 CENELEC takes no position concerning the evidence, validity and scope of patent rights KNX Association as Cooperating Partner to CENELEC confirms that to the extent that the standard contains patents and like rights, the KNX Association's members are willing to negotiate licenses thereof with applicants throughout the world on fair, reasonable and non-discriminatory terms and conditions KNX Association De Kleetlaan 5, bus 11 B - 1831 Diegem Tel.: + 32 775 85 90 Fax.: + 32 675 50 28 e-mail: info@knx.org www.knx.org Attention is drawn to the possibility that some of the elements of this standard may be the subject of patent rights other than those identified above CENELEC shall not be held responsible for identifying any or all such patent rights The following dates were fixed: – – latest date by which the EN has to be implemented at national level by publication of an identical national standard or by endorsement latest date by which the national standards conflicting with the EN have to be withdrawn (dop) 2009-12-01 (dow) 2011-12-01 EN 50090-3-3 is part of the EN 50090 series of European Standards, which will comprise the following parts: Part 1: Standardization structure Part 2: System overview Part 3: Aspects of application Part 4: Media independent layers Part 5: Media and media dependent layers Part 6: Interfaces Part 7: System management Part 8: Conformity assessment of products Part 9: Installation requirements Licensed Copy: athen reading, Reading University Library, 24/01/2010 04:42, Uncontrolled Copy, (c) BSI -3- BS EN 50090-3-3:2009 EN 50090-3-3:2009 Contents Introduction Scope Normative references Terms, definitions and abbreviations 3.1 Terms and definitions 3.2 Abbreviations HBES Interworking model 4.1 Principles of HBES Interworking 11 4.2 Busload 12 4.3 Datapoint Type error handling 13 4.4 Interpretability of data and data integrity 15 General Functional Block Design and Implementation Rules 15 5.1 Introduction 15 5.2 Describe the Application Domain 15 5.3 Describe the Application 15 5.4 Describe the Functional Block 19 5.5 Describing the Datapoint Types 29 Annex A (informative) Common HBES data types 38 Figures Figure – The HBES Interworking Model An Application Domain can contain one or more Applications Figure – The HBES Interworking Model An Application Model may contain one or more Functional Blocks Figure – Standard representation for Functional Blocks Figure – Datapoints indicated in Functional Blocks Figure – Functional Blocks grouped in devices and linked Figure – Functional Block with Datapoints 10 Figure – The information contained in a Datapoint Type definition 10 Figure – Example of an Interworking specification 11 Figure – Functional Block diagram (Example) 20 Figure 10 – Table listing separate datapoints of a functional block 21 Figure 11 – Specification form for Inputs and Outputs 22 Figure 12 – Specification form for Parameters and Diagnostic Data 29 Figure 13 – Example of multi-state datapoint 32 Figure 14 – Datapoint Type specification form 34 Figure A.1 – Structure of Datapoint Types 38 Figure A.2 – December 12, 2006 encoded according DPT_Date in an A_GroupValue_Write-frame (example on TP1) 39 Licensed Copy: athen reading, Reading University Library, 24/01/2010 04:42, Uncontrolled Copy, (c) BSI BS EN 50090-3-3:2009 EN 50090-3-3:2009 -4- Tables Table – Use of heart-beat 12 Table – Authorisation level names 27 Table – Datatypes notation styles 35 Table A.1 – Compatibility rules 67 Licensed Copy: athen reading, Reading University Library, 24/01/2010 04:42, Uncontrolled Copy, (c) BSI -5- BS EN 50090-3-3:2009 EN 50090-3-3:2009 Introduction Interworking between devices signifies that these products send and receive datagrams and are able to properly understand and react on them This ability is provided without additional equipment (like translators or gateways) NOTE Media couplers are needed if different media are used in an installation The market requires Interworking for a multi-vendor approach, this is, products from different manufacturers can interwork in a certain application segment or domain as well as across different applications (cross discipline Interworking) Such an Interworking is only possible if a set of requirements is complied with as defined in an Interworking model For this, Functional Blocks need to be defined, which in turn specify Datapoints and the communication mechanisms to be used Such a set of requirements is referred to as "Application Interworking Specifications" (AIS) AIS allow Interworking independent of the implementation by a manufacturer Besides the advantages for the user (multi-vendor offer) Interworking also allows a broad OEM market and easy market access for niche-products providers Furthermore Interworking allows the establishment of a common market infrastructure (i.e common configuration tool, training, etc.) Licensed Copy: athen reading, Reading University Library, 24/01/2010 04:42, Uncontrolled Copy, (c) BSI BS EN 50090-3-3:2009 EN 50090-3-3:2009 -6- Scope This European Standard gives general guidelines and recommendations to ensure interworking between HBES devices made by different manufacturers It also contains design guidelines for the design of Functional Blocks and new datapoint types, the building blocks of HBES interworking In this way, the standard can be used as a basis to design application specifications relative to an Application Domain If designed and supported by a large group of manufacturers, such application specifications will ensure to end customers a high degree of interoperability between products based on the HBES Communication System of different manufacturers This European Standard is used as a product family standard It is not intended to be used as a stand-alone standard 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 50090-1 1) Home and Building Electronic Systems (HBES) – Part 1: Standardization structure EN 50090-3-2:2004 Home and Building Electronic Systems (HBES) – Part 3-2: Aspects of application – User process for HBES Class EN 50090-4-1:2004 Home and Building Electronic Systems (HBES) – Part 4-1: Media independent layers – Application Layer for HBES Class EN 50090-4-2: 2004 Home and Building Electronic Systems (HBES) – Part 4-2: Media independent layers – Transport layer, network layer and general parts of data link layer for HBES Class 1) Under consideration Licensed Copy: athen reading, Reading University Library, 24/01/2010 04:42, Uncontrolled Copy, (c) BSI -7- BS EN 50090-3-3:2009 EN 50090-3-3:2009 Terms, definitions and abbreviations 3.1 Terms and definitions For the purposes of this document, the definitions given in EN 50090-1 apply 3.2 Abbreviations AIS Application Interworking Specifications COV Change of Value DMA Direct Memory Access DP Data Point DPT Datapoint type DPT ID Datapoint type identifier FB Functional Block GO Group Object IO Interface Object lsb least significant bit M Mandatory msb most significant bit MSB Most Significant Byte NA Not Applicable O Optional PDT Property Data Type PID Property Identifier OEM Original Equipment Manufacturer HBES Interworking model HBES Interworking can be applied in many application domains Each Application Domain can encompass one or more Applications Application Domain Application Figure - The HBES Interworking Model An Application Domain can contain one or more Applications The Application Modelling or the process of analysing, deciding on the solution and specifying the model for such an Application needs to be agreed upon amongst manufacturers in Application Specification Groups Licensed Copy: athen reading, Reading University Library, 24/01/2010 04:42, Uncontrolled Copy, (c) BSI BS EN 50090-3-3:2009 EN 50090-3-3:2009 -8- Applications shall not be defined in terms of products, but analysed and split up into Functional Blocks, which communicate with one another The term Distributed Application indicates this approach: the total functionality of an Application is spread over a number of Functional Blocks implemented in various devices in the network A Functional Block transports its data over the bus via one or more Datapoints (these are Inputs, Outputs, Parameters and Diagnostic Data) A Functional Block thus describes the standard specification of the chosen solution for one given task of an application These Datapoints and their described functionality are implemented by the product developer The following picture shows the Interworking model as defined so far Application Domain Application Model Functional Block Figure - The HBES Interworking Model An Application Model may contain one or more Functional Blocks The Functional Blocks shall be described as objects; this is a set of Datapoints and a well-defined behaviour The standard graphical representation for a Functional Block shall be the following: Functional Block name Input(s) Name Input I1 DPT I1 I1 Name Input I2 DPT I2 I2 O1 Output(s) DPT O1 Parameter(s) Name Parameter P1 Name Output O1 Diagnostic Data DPT P1 P1 DD1 DPT DD1 Figure - Standard representation for Functional Blocks Licensed Copy: athen reading, Reading University Library, 24/01/2010 04:42, Uncontrolled Copy, (c) BSI BS EN 50090-3-3:2009 EN 50090-3-3:2009 A.2.19.2.6 - 60 - Remarks to the field Quality of Clock in DPT_DateTime Bit of the octet shall be used for “Quality of Clock” bit (CLQ) The other bits of this octet are reserved for future extensions Their values shall be If this Datapoint Type is used for transmitting data, transmitters shall set the lower bits to Receivers shall check these bits to be The encoding of the bit shall have the following meaning: CLQ = shall indicate that the clock does not have an external synchronisation signal The device sending date and time information has only a local clock, which may be inaccurate CLQ = shall indicate that the clock has an external synchronisation signal (like DCF77, videotext, etc.) The device sending date and time information sends signals which are synchronised (from time to time) with external date and time information The default value shall be After start-up an externally synchronised clock shall also send CLQ = until reception of first synchronisation signal or after a synchronisation timeout CLQ information may be used to resolve system clock master conflicts: a system clock master sending CLQ = shall then take over from a system clock master sending CLQ = If the Datapoint Type DPT_DateTime is used for parameters like scheduler information, CLQ bit shall be set to A.2.20 Datapoint Types N8 Format: octet: N8 Octet nr.: Field names: field1 Encoding: NNNNNNNN Encoding: Encoding absolute value N = [0 … 255] Unit: None Resol.: None PDT: PDT_ENUM8 (alt: PDT_UNSIGNED_CHAR) BS EN 50090-3-3:2009 EN 50090-3-3:2009 Licensed Copy: athen reading, Reading University Library, 24/01/2010 04:42, Uncontrolled Copy, (c) BSI - 61 - Datapoint Types ID 20.001 Name DPT_SCLOMode Encoding = autonomous Range [0 … 3] = slave = master …255 not used; reserved 20.002 DPT_BuildingMode = building in use [0 …3] = building not used = building protection 20.003 DPT_OccMode = occupied [0 … 3] = standby = not occupied …255 not used; reserved 20.004 a DPT_Priority is highest priority [0 … 3] = high = medium = low = ‘void’ … 255 not used; reserved 20.007 DPT_AlarmClassType = reserved (not used) [0 … 3] = simple alarm = basic alarm = extended alarm … 255 = reserved, shall not be used 20.011 DPT_ErrorClass_System = no fault [0 … 5] = general device fault (e.g RAM, EEPROM, UI, watchdog, …) = communication fault = configuration fault = hardware fault = software fault … 266 = reserved, shall not be used 20.012 DPT_AlarmClass_HVAC = no fault [0 … 4] = sensor fault = process fault / controller fault = actuator fault = other fault … 255 = reserved, shall not be used a This Datapoint Type is used for parameters, not for runtime interworking It is used e.g to define the alarm priority of a configurable digital alarm input in a device Licensed Copy: athen reading, Reading University Library, 24/01/2010 04:42, Uncontrolled Copy, (c) BSI BS EN 50090-3-3:2009 EN 50090-3-3:2009 A.2.21 Format: Encoding: - 62 - Datapoint Type DPT_VarString_8859_1 variable length: A[n] N MSB LSB A … 00 This Datapoint Type shall be used to transmit strings of textual characters The length is not fixed, but variable; the string shall be terminated by a single character NULL (00h) No length information shall be transmitted in the APDU a) Non-supported lengths shall be handled as follows: Data Link Layer: ignore the frame Application Layer: MSB cut to the maximum supported length, keeping the characters at the beginning, i.e starting with the Interface Object Server The implicit array structure of a property value of an Interface Object property can be used to store multiple strings Every array element shall contain exactly one string These array elements can have a different length The APDU's used to read/write these strings shall only contain entire strings; exactly one NULL-character shall appear between string elements and at the end of the last string The NULL character is part of the the DPT_VarString_8859_1 format This means that strings that not fit in the supported array length shall not be cut off If a property value is read which would lead to an APDU longer than the length supported by the server, the server shall respond with a negative response; i.e the APDU shall not be limited to the number of elements that does fit, but instead contain no property value data The client can then read a smaller number of array elements Each character shall be encoded according ISO 8859-1 Example HBES is OK’ is encoded as follows : 48 42 45 53 20 69 73 20 6F 6B 00h Example ‘This format allows transmission of very long strings!’ is encoded as follows : 54h 68h 69h 73h 20h 66h 6Fh 72h 6Dh 61h 74h 20h 61h 6Ch 6Ch 6Fh 77h 73h 20h 74h 72h 61h 6Eh 73h 6Dh 69h 73h 73h 69h 6Fh 6Eh 20h 6Fh 66h 20h 76h 65h 72h 79h 20h 6Ch 6Fh 6Eh 67h 20 73h 74h 72h 69h 6Eh 67h 73h 21h 00h Unit: Not applicable PDT: Datapoint Types ID 24.001 a Name DPT_VarString_8859_1 Range Acc DPT 4.002 (DPT_Char_8859_1) Length information is implicitly in the frame (by the Data Link Layer) BS EN 50090-3-3:2009 EN 50090-3-3:2009 Licensed Copy: athen reading, Reading University Library, 24/01/2010 04:42, Uncontrolled Copy, (c) BSI - 63 A.2.22 Datapoint Type DPT_SceneInfo Format: octet: r1B1U6 Octet nr.: Field names: R B SceneNumber Encoding: b UUUUUU Encoding: All values binary encoded Range: See below Unit: Not applicable Resol.: Not applicable PDT: PDT_GENERIC_01 Datapoint Types ID Name 26.001 Encoding DPT_SceneInfo r B SceneNumber Range reserved (0) none info: [0, 1] 0= scene is active 1= scene is inactive Scene number [0 … 63] NOTE DPT_SceneInfo allows numbering the scene from to 63 It is recommended to display these scene numbers to users numbered from to 64, this is, with an offset of compared to the actual transmitted value A.2.23 Datapoint Type DPT_AlarmInfo A.2.23.1 Encoding Format: octets: U8N8N8N8B8B8 Octet nr.: MSB Field names: LogNumber AlarmPriority ApplicationArea ErrorClass Attributes Encoding: UUUUUUUU NNNNNNNN NNNNNNNN NNNNNNNN 0 BBBBBB Octet nr.: LSB Field names: AlarmStatusAttributes Octet nr.: 0 0 BBB Encoding: Binary encoded values Unit: Not applicable Resol.: Not applicable PDT: PDT_ALARM_INFO (alt: PDT_GENERIC_06) Licensed Copy: athen reading, Reading University Library, 24/01/2010 04:42, Uncontrolled Copy, (c) BSI BS EN 50090-3-3:2009 EN 50090-3-3:2009 - 64 - Datapoint Types ID 219.001 Name DPT_AlarmInfo Encoding Range LogNumber: U8 Log Number [0 … 255] AlarmPriority: N8 Alarm Priority [0 … 2] See DPT_Priority priorities = highest priority; for “no priority”, ‘03h is used (=’void’) A.2.23.2 A.2.23.2.1 ApplicationArea: N8 Application Area see Note ErrorClass: N8 Error Class see Note Attributes: B8 Attributes: Boolean B0: Ack_Sup = False, = True {0, 1} B1: TimeStamp_Sup = False, = True {0, 1} B2: AlarmText_Sup = False, = True {0, 1} B3: ErrorCode_Sup = False, = True {0, 1} B4 … B7: reserved Fixed to - AlarmStatusAttributes: B8 Alarm Status (attributes) B0: InAlarm = False, = True {0, 1} B1: AlarmUnAck = False, = True {0, 1} B2: Locked = False, = True {0, 1} B3 … B7: reserved Fixed to - Remarks to the encoding of DPT_Alarminfo General Alarm messages contain an ‘Application area’ information to allow filtering of alarm messages in subsystems For coding, see A.2.23.2.3 A.2.23.2.2 Remarks to the field Ack_Sup in DPT_Alarminfo B0 in attributes field (Ack_Sup) shall indicate whether the alarm is a simple error which can never be acknowledged (0) or an alarm with acknowledge and/or ‘alarm reset’ mechanism If it is a simple error without acknowledge, the alarm source shall send ‘acknowledged’ (bit ‘AlarmUnAck’ = 0) as status information in the alarm status attributes Licensed Copy: athen reading, Reading University Library, 24/01/2010 04:42, Uncontrolled Copy, (c) BSI - 65 A.2.23.2.3 BS EN 50090-3-3:2009 EN 50090-3-3:2009 Remarks to the field Application Area DPT_Alarminfo The coding shall be as follows: Code A.2.23.2.4 Application Area no fault system & functions of common interest 2…9 reserved 10 HVAC General FB´s 11 HVAC Hot Water Heating 12 HVAC Direct Electrical Heating 13 HVAC Terminal Units 14 HVAC VAC 15 … 19 reserved (HVAC) 20 lighting 21 29 reserved (Lighting) 30 security 31 … 39 reserved (Security) 50 shutters & Blinds … … … 255 not used Encoding of the field Error class in DPT_Alarminfo for Application Area System Code Error Class no fault general device fault (e.g RAM, EEPROM, UI, Watchdog, …) communication fault configuration fault HW fault SW fault not used … not used 255 not used EXAMPLES: • Detection of ‘two devices with same individual addresses shall lead to the error code ‘configuration fault’ • Detection of a ‘multiple system clock master conflict’ (without automatic resolution) shall lead to the error code ‘configuration fault’ • Detection of failure of a (formerly present) communication partner shall lead to the error code ‘communication fault’ • Timeout detection on the System Clock Signal (heartbeat) shall lead to the error code ‘communication fault’ Licensed Copy: athen reading, Reading University Library, 24/01/2010 04:42, Uncontrolled Copy, (c) BSI BS EN 50090-3-3:2009 EN 50090-3-3:2009 A.2.23.2.5 - 66 - Encoding of the field Error class in DPT_Alarminfo for Application Area HVAC Code A.2.24 Error Class no fault sensor fault process fault/controller fault actuator fault other faults not used … not used 255 not used Datapoint Type DPT_Version A.2.24.1 Encoding of DPT_Version Format: octet: U5U5U6 Octet nr.: MSB Field names: Magic Number Encoding: UUUUUUUU UUUUUUUU LSB Version Number Encoding: All values binary encoded Unit: None PDT: PDT_VERSION Revision Number (alt: PDT_GENERIC_02) Datapoint Types ID 217.001 Name DPT_Version Field Magic Number Description Encoding An incrementation of the Magic Number shall indicate an U5 incompatible change, i.e no forward or backwards compatibility is ensured Range Resol.: … 31 … 31 … 63 This field of the version information shall be used for compatibility checks but it is normally not displayed (invisible) If the Magic Number is incremented, the Version Number shall also be incremented (i.e higher number) It is recommended to start with Version Number Version Number shall be incremented (i.e higher number) if a new U5 version has new features Usage: If the Magic Number is incremented, the Version Number shall be incremented as well This shall denote an incompatible change If the Magic Number is not incremented and the Version Number is incremented, this shall denote a backwards compatible extension It is recommended to start with Revision Number The revision Number shall be incremented (i.e higher number) for U6 minor changes not affecting forward and/or backward functional compatibility between newer and older version It is recommended to start with BS EN 50090-3-3:2009 EN 50090-3-3:2009 Licensed Copy: athen reading, Reading University Library, 24/01/2010 04:42, Uncontrolled Copy, (c) BSI - 67 A.2.24.2 Further remarks on DPT_Version DPT_Version can be used to encode version information e.g to indicate software, hardware version, data-interface version etc DPT_Version allows encoding of Version Revision information and of a compatibility identifier called ‘Magic Number’ EXAMPLES M.V.R M.V.R previous version new version Meaning 0.1.0 0.1.1 minor modification without effect on compatibility 0.1.1 0.2.0 backwards compatible change 0.2.0 1.3.0 incompatible change If the version information that is transferred using DPT_Version is invalid, void or undefined, this shall be indicated by setting the values of each individual field to its maximum encodable value Invalid version information shall thus be encoded as M.V.R = 31.31.63 Table A.1 below specifies the compatibility rules Table A.1 – Compatibility rules M V R Compatibility = = = compatible version = = > minor changes without effects on forward and backward functional compatibility between previous and new version = > any value new version has new features but is still backwards compatible to the previous version (all old features are supported) > = any value combination is not allowed: in case of change of the magic number also the version number shall be incremented > > any value no forward or backwards compatibility Key > This field has been incremented compared to the previous version = This field did not change compared to the previous version Licensed Copy: athen reading, Reading University Library, 24/01/2010 04:42, Uncontrolled Copy, (c) BSI BS EN 50090-3-3:2009 EN 50090-3-3:2009 A.3 - 68 - Datapoint Types for use in HVAC applications A.3.1 Datapoint Types B1 Format: bit: B1 Octet nr: Field names: b Encoding: B Encoding: See below Range: b = {0,1} Unit: See below Resol.: (not applicable) PDT: PDT_BINARY_INFORMATION (alt: PDT_UNSIGNED_CHAR) Datapoint Types ID Name 1.100 A.3.2 Encoding DPT_Heat/Cool = Cooling = Heating Datapoint Types N8 Format: octet: N8 Octet nr.: Field names: field1 Encoding: NNNNNNNN Encoding: Encoding absolute value N = [0 … 255] Unit: None Resol.: None PDT: PDT_ENUM8 (alt: PDT_UNSIGNED_CHAR) Datapoint Types ID 20.102 20.103 Name DPT_HVACMode DPT_DHWMode Encoding = Auto = Comfort = Standby = Economy = [0 … 4] Building Protection … 255 = reserved = Auto = LegioProtect = Normal = Reduced = Off/FrostProtect … 255 = Range reserved [0 … 4] BS EN 50090-3-3:2009 EN 50090-3-3:2009 Licensed Copy: athen reading, Reading University Library, 24/01/2010 04:42, Uncontrolled Copy, (c) BSI - 69 - Datapoint Types ID 20.104 20.105 20.106 20.107 20.108 20.109 Name DPT_LoadPriority DPT_HVACContrMode DPT_HVACEmergMode DPT_ChangeoverMode DPT_ValveMode DPT_DamperMode Encoding = None = Shift load priority = Absolute load priority … 255 = reserved = Auto = Heat = Morning Warmup = Cool = Night Purge = Precool = Off = Test = Emergency Heat = Fan only 10 = Free Cool 11 = Ice 12 … 19 = reserved 20 NoDem = 21 … 255 = reserved = Normal = EmergPressure = EmergDepressure = EmergPurge = EmergShutdown = EmergFire … 255 = reserved = Auto = CoolingOnly = HeatingOnly … 255 = reserved = reserved = Heat stage A for normal heating = Heat stage B for heating with two stages (A + B) = Cool stage A for normal cooling = Cool stage B for cooling with two stages (A + B) = Heat/Cool for changeover applications … 255 = reserved reserved = = Fresh air, e.g for fancoils = Supply Air e.g for VAV = Extract Air e.g for VAV … 255 = reserved Range [0 … 2] {[0 … 11], 20} [0 … 5] [0 … 2] [1 … 5] [1 … 3] Licensed Copy: athen reading, Reading University Library, 24/01/2010 04:42, Uncontrolled Copy, (c) BSI BS EN 50090-3-3:2009 EN 50090-3-3:2009 - 70 - Datapoint Types ID 20.110 20.111 20.112 20.113 Name Encoding DPT_HeaterMode DPT_FanMode DPT_MasterSlaveMode DPT_StatusRoomSetp = reserved = Heat Stage A On/Off = Heat Stage A Proportional = Heat Stage B Proportional … 255 = reserved Not running = = Permanently running = Running in intervals … 255 = reserved = autonomous = master = slave … 255 = reserved = Normal setpoint = Alternative setpoint = Building protection setpoint … 255 = A.3.3 Range [1 … 3] [0 … 2] [0 … 2] [0 … 2] reserved Data Type “3x 16-Float Value ” A.3.3.1 Format: Encoding: Datapoint Type “3x set of RoomTemperature Setpoint Values ” octet; F16F16F16 MSB TempSetp Comf LSB TempSetp Comf MSB TempSetp Stdby LSB TempSetp Stdby FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF MSB TempSetp Eco LSB TempSetp Eco FFFFFFFF FFFFFFFF see below For all fields “Comfort”, “Standby” and “Economy”, only the value 7FFFh shall be used to denote invalid data Range: see below Unit: °C Datapoint Types ID 222.100 Name DPT_TempRoomSetpSetF16[3] Data fields Range see below Description Unit see below Unit / Range TempSetpComf room temperature setpoint comfort -273 °C to 670 760 °C TempSetpStdby room temperature setpoint standby -273 °C to 670 760 °C TempSetpEco room temperature setpoint economy -273 °C to 670 760 °C BS EN 50090-3-3:2009 EN 50090-3-3:2009 Licensed Copy: athen reading, Reading University Library, 24/01/2010 04:42, Uncontrolled Copy, (c) BSI - 71 A.3.3.2 Format: Datapoint Type “3x set of RoomTemperature Setpoint Shift Values ” octet; F16F16F16 Encoding: MSB TempSetp ShiftComf LSB TempSetp ShiftComf MSB TempSetp ShiftStdby LSB TempSetp ShiftStdby FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF MSB TempSetp ShiftEco LSB TempSetp ShiftEco FFFFFFFF FFFFFFFF see below For all fields “Comfort”, “Standby” and “Economy”, only the value 7FFFh shall be used to denote invalid data Range: see below Unit: K Datapoint Types ID 222.101 Name DPT_TempRoomSetpSetShiftF16[3] Data fields Range see below Unit see below Description Unit / Range TempSetpShiftComf room temperature setpoint shift comfort (delta value) -670 760 K…670 760 K TempSetpShiftStdby room temperature setpoint shift standby (delta value) -670 760 K…670 760 K TempSetpShiftEco room temperature setpoint shift economy (delta value) -670 760 K…670 760 K This page deliberately left blank Licensed Copy: athen reading, Reading University Library, 24/01/2010 04:42, Uncontrolled Copy, (c) BSI This page deliberately left blank Licensed Copy: athen reading, Reading University Library, 24/01/2010 04:42, Uncontrolled Copy, (c) BSI Licensed Copy: athen reading, Reading University Library, 24/01/2010 04:42, Uncontrolled Copy, (c) BSI British Standards Institution (BSI) BSI is the independent national body responsible for preparing British Standards and other standards-related publications, information and services It presents the UK view on standards in Europe and at the international level It is incorporated by Royal Charter Revisions Information on standards British Standards are updated by amendment or revision Users of British Standards should make sure that they possess the latest amendments or editions It is the constant aim of BSI to improve the quality of our products and services We would be grateful if anyone finding an inaccuracy or ambiguity while using this British Standard would inform the Secretary of the technical committee responsible, the identity of which can be found on the inside front cover Tel: +44 (0)20 8996 9001 Fax: +44 (0)20 8996 7001 BSI provides a wide range of information on national, European and international standards through its Knowledge Centre BSI offers Members an individual updating service called PLUS which ensures that subscribers automatically receive the latest editions of standards Tel: +44 (0)20 8996 7669 Fax: +44 (0)20 8996 7001 Email: plus@bsigroup.com Buying standards You may buy PDF and hard copy versions of standards directly using a credit card from the BSI Shop on the website www.bsigroup.com/shop In addition all orders for BSI, international and foreign standards publications can be addressed to BSI Customer Services Tel: +44 (0)20 8996 9001 Fax: +44 (0)20 8996 7001 Email: orders@bsigroup.com In response to orders for international standards, it is BSI policy to supply the BSI implementation of those that have been published as British Standards, unless otherwise requested Tel: +44 (0)20 8996 7004 Fax: +44 (0)20 8996 7005 Email: knowledgecentre@bsigroup.com Various BSI electronic information services are also available which give details on all its products and services Tel: +44 (0)20 8996 7111 Fax: +44 (0)20 8996 7048 Email: info@bsigroup.com BSI Subscribing Members are kept up to date with standards developments and receive substantial discounts on the purchase price of standards For details of these and other benefits contact Membership Administration Tel: +44 (0)20 8996 7002 Fax: +44 (0)20 8996 7001 Email: membership@bsigroup.com Information regarding online access to British Standards via British Standards Online can be found at www.bsigroup.com/BSOL Further information about BSI is available on the BSI website at www.bsigroup.com/standards Copyright Copyright subsists in all BSI publications BSI also holds the copyright, in the UK, of the publications of the international standardization bodies Except as permitted under the Copyright, Designs and Patents Act 1988 no extract may be reproduced, stored in a retrieval system or transmitted in any form or by any means – electronic, photocopying, recording or otherwise – without prior written permission from BSI This does not preclude the free use, in the course of implementing the standard of necessary details such as symbols, and size, type or grade designations If these details are to be used for any other purpose than implementation then the prior written permission of BSI must be obtained Details and advice can be obtained from the Copyright & Licensing Manager Tel: +44 (0)20 8996 7070 Email: copyright@bsigroup.com BSI Group Headquarters 389 Chiswick High Road London W4 4AL UK Tel +44 (0)20 8996 9001 Fax +44 (0)20 8996 7001 www.bsigroup.com/standards raising standards worldwide™