BACnet Application Guide for Consulting Engineers

Transcription

1 BACnet Application Guide for Consulting Engineers s

2

3 BACnet Application Guide for Consulting Engineers T Rev. 1, January, 2012

4 Rev. 1, January, 2012 NOTICE The information contained within this document is subject to change without notice and should not be construed as a commitment by Siemens Building Technologies, Inc. Siemens Building Technologies, Inc. assumes no responsibility for any errors that may appear in this document. All software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. WARNING This equipment generates, uses, and can radiate radio frequency energy and if not installed and used in accordance with the instructions manual, may cause interference to radio communications. It has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC rules. These limits are designed to provide reasonable protection against such interference when operated in a commercial environment. Operation of this equipment in a residential area is likely to cause interference in which case users at their own expense will be required to take whatever measures may be required to correct the interference. SERVICE STATEMENT Control devices are combined to make a system. Each control device is mechanical in nature and all mechanical components must be regularly serviced to optimize their operation. All Siemens Building Technologies, Inc.branch offices and authorized distributors offer Technical Support Programs that will ensure your continuous, trouble-free system performance. For further information, contact your nearest Siemens Building Technologies, Inc. representative. Copyright 2007 by Siemens Building Technologies, Inc. TO THE READER Your feedback is important to us. If you have comments about this manual, please submit them to: SBT_technical.editor.us.sbt@siemens.com APOGEE is a registered trademark of Siemens Building Technologies, Inc. Tracer Summit is a trademark of The Trane Company BACnet is a registered trademark of American Society of Heating, Refrigeration and Air Conditioning Engineers (ASHRAE) Insight for Minicomputers is a registered trademark of Siemens Building Technologies, Inc. Insight for Personal Computers is a registered trademark of Siemens Building Technologies, Inc. Country of Origin: US

5 Table of Contents About this Application Guide... I Purpose of this Guide... I How this Guide is Organized... I Suggested Reference Materials... II Symbols... II Getting Help... III Where to Send Comments... III Chapter 1 Introduction to BACnet... 1 What is BACnet?... 1 Why BACnet was Developed... 2 How BACnet was Developed... 3 Certification... 3 BACnet Implementation within APOGEE... 3 Chapter 2 BACnet Objects and Services... 5 Objects Theory... 5 Properties of Objects... 6 The OBJECT_TYPE Property... 7 Command Priority Properties... 8 BACnet Device Point-Like Objects Analog Input Object...16 Analog Output Object Analog Value Object Binary Input Object Binary Output Object Binary Value Object...23 Multi-State Input Object Multi-State Output Object Multi-State Value Object Other Objects Supported by APOGEE BACnet Field Panels Calendar Object Command Object File Object Notification Class Object Siemens Building Technologies, Inc. i

6 Table of Contents Schedule Object Trend Log Object Viewing with the BACnet Browser Services Theory Services Supported Services Not Supported Chapter 3 BACnet Interoperability Interoperability Certification Specifying BACnet Protocol Implementation and Conformance Statement BACnet Interoperable Building Blocks BACnet Device Profiles...41 Building Controller Profile (B-BC) and Operator Workstation Profile (B-OWS) Chapter 4 BACnet Communications BACnet Networking Technologies Master-Slave/Token-Passing LonTalk Cautions BACnet Protocol Model Basic BACnet Networking Native BACnet Devices On The Same LAN Native BACnet Devices with Different LAN Technologies Native BACnet to Non-Native BACnet Devices BACnet Communications BACnet/IP BACnet Broadcast Management Device (BBMD) BACnet Foreign Devices BACnet Router vs. IP Router Chapter 5 BACnet Field Panel APOGEE BACnet Field Panel Field Panel Hardware Field Panel Features BTL Certification Chapter 6 Insight BACnet Option Insight BACnet Option Native BACnet and B-OWS Backward Compatibility...58 Insight Changes for BACnet ii Siemens Building Technologies, Inc.

7 Table of Contents BACnet Alarms Point Priority Initials Alarm Acks Event Information and Alarm Summary Unknown BACnet alarms BACnet Text Messages Alarm Priority Alarm Messages...60 APOGEE GO Attribute Duplicator BACNET Object Browser BACnet Browser Features BACnet Browser Limitations Point Commander Database Transfer Progress Tab Log Tab Upload Selected Dialog Object Types Backup and Restore Other Changes Dynamic Plotter Event Log Event Printer RENO Notification PXC Compact Slope/Intercept Program Editor Report Builder/Reports Display BACnet Priority Reports Point Definition Report...69 Panel Point Definition Report Panel Configuration Report Panel Display Report User Account Report System Profile Report Trend Definition Report Panel Trend Definition Report Trend Data Detail Report Totalization Log Report Scheduler Siemens Building Technologies, Inc. iii

8 Table of Contents System Profile Command Priority Array Strings BACnet Address Table BLN Definition FLN Devices Device Re-Initialization...73 Device Communication Control Who-Is Diagnostic Tool Time-of-Day Scheduling Trend Editor Trend Definitions User Accounts Command Priority...74 Insight Account Tab...76 BLN Account TAB BACnet Export Chapter 7 BACnet Scheduling BACnet Scheduling Theory Schedule Object BACnet Schedule Object Operation Command Object Calendar Object BACnet and Insight Scheduling Event Scheduling Start Stop Time Optimization (SSTO) BACnet Device Database Storage Schedule Object Properties that Can be Commanded BACnet Scheduling Examples BACnet Scheduling Example BACnet Scheduling Example BACnet Scheduling Example BACnet Scheduling Example BACnet Scheduling Example Chapter 8 BACnet Alarming...95 BACnet Alarming Theory...95 Change Of Value (COV) Reporting Algorithmic Change Reporting Intrinsic Reporting Notification Class Recipient List (Destinations) iv Siemens Building Technologies, Inc.

9 Table of Contents Transitions and Event States Alarm Acknowledgement Alarm and Event Priority BACnet and APOGEE Alarm Enable/Disable Floating Alarm Limits System Messages Initials Alarm Acknowledgements Get Event Information vs. Alarm Summary Unknown BACnet Alarms Life Safety Alarms BACnet Text Messages Alarm Priority Alarm Messages BACnet Browser Point Objects RENO Notification APOGEE GO BACnet Alarming Example L2SL Point LTD Point SAT Point SSP Point Notification Class Alarm Message Definition Chapter 9 BACnet Trending BACnet Trending Theory BACnet Trending in APOGEE APOGEE Trending: Non-BACnet vs. BACnet Scheduling Trends Scheduling Trend Collections Notification Class Chapter 10 BACnet Tools BAS-o-matic Protocol Analyzer Obtaining BAS-o-matic Connecting to a Network Connecting a Separate BAS-o-matic Computer Using the Insight Workstation for BAS-o-matic Commissioning Tool Support for APOGEE BACnet Field Panels Siemens Building Technologies, Inc. v

10 Table of Contents Firmware Loading Tool MMI Database Transfer Build System Profile Backup/Restore Terminal Emulation Copy Field Panel Point Transfer Non-Field Panel Data Transfer Point Summary Report Point Checkout Data Commissioning Report Generator Insight BACnet Communications Tools Multiple Device Configuration Global Broadcast Who-Is Custom Send Who-Is Diagnostic Tool Enable Device Discovery BACnet Device Communication Control BACnet Communication Diagnostic Glossary Index vi Siemens Building Technologies, Inc.

11 Table of Contents Siemens Building Technologies, Inc. vii

12

13 About this Application Guide This section discusses the following topics: Purpose of this guide. How this guide is organized. Suggested reference materials and Web sites. It also provides information on symbols used, how to access help, and where to direct comments about this guide. Purpose of this Guide This application guide discusses the Building Automation and Control networks (BACnet ) standard data communication protocol and gives details about the implementation of the Insight BACnet Option and the APOGEE BACnet Field Panels. This guide is intended to supplement all of the other APOGEE BACnet system documentation (online help, Getting Started, User Guides, etc.) by providing information not contained in those documents. It is assumed that the reader is technically capable of understanding the concepts of building automation and database management. It also assumes that they are familiar with APOGEE concepts and understand its operations. This application guide should help Branch and customer personnel understand how BACnet has been implemented in the APOGEE Building Automation System. How this Guide is Organized This application guide contains the following chapters: Chapter 1, Introduction to BACnet, describes BACnet in general terms and how it relates to the APOGEE Building Automation System. Chapter 2, BACnet Objects and Services, describes BACnet Objects and Services theory, and how the Insight application and the BACnet Browser are used to access objects and their properties. Chapter 3, BACnet Interoperability, describes the ability of APOGEE BACnet devices to integrate with BACnet products made by different manufacturers into a single system. Chapter 4, BACnet Communications, describes BACnet communication theory in relation to the Insight application. Chapter 5, BACnet Field Panel, describes the features and functions of the APOGEE BACnet field panel as well as the firmware used to operate it. Siemens Building Technologies, Inc. I

14 About this Application Guide Chapter 6, Insight BACnet Option, describes the Insight BACnet Option and the changes to the Insight application since Revision 3.2 Chapter 7, BACnet Scheduling, describes BACnet scheduling theory as it relates to scheduling in the APOGEE Building Automation System. Chapter 8, BACnet Alarming, describes BACnet alarming theory, how it relates to the APOGEE Building Automation System, and how to set up alarming in an APOGEE Building Automation System. Chapter 9, BACnet Trending, describes BACnet trending theory and trending in an APOGEE Building Automation System. Chapter 10, BACnet Tools, describes tools for analyzing BACnet communications in an APOGEE Building Automation System. The Glossary describes various terms and acronyms used in this application guide. The Index helps you locate information presented in this guide. Suggested Reference Materials In addition to this application guide, you may also want to become familiar with the following reference materials: ANSI/ASHRAE Standard available at: BACnet Web site: BACnet International (BI) Web site: See the Glossary for other references. Symbols The following table lists the symbols used in this guide to draw your attention to important information. Notation Symbol Meaning CAUTION: Indicates that equipment damage, or loss of data may occur if the user does not follow a procedure as specified. Note Tip Provides additional information or helpful hints that need to be brought to the reader's attention. Suggests alternative methods or shortcuts that may not be obvious, but can help the user better understand the capabilities of the product. II Siemens Building Technologies, Inc.

15 Table of Contents Getting Help For more information about regulated facilities, contact your local Siemens representative. Where to Send Comments Your feedback is important to us. If you have comments about this guide, please submit them to: Siemens Building Technologies, Inc. III

16 About this Application Guide IV Siemens Building Technologies, Inc.

17 Chapter 1 Introduction to BACnet Chapter 1 describes BACnet in general terms and how it relates to the APOGEE Building Automation System. It includes the following topics: What is BACnet? Why BACnet was Developed How BACnet was Developed Certification BACnet Implementation within the APOGEE Automation System What is BACnet? BACnet is an acronym for Building Automation and Control networks. It is the name for an ASHRAE and ANSI standard data communication protocol, which is a set of rules governing the exchange of data over a computer network. The rules govern hardware (for example, cable types, system topology) and software (for example, formation of request or command messages). The rules are in a published specification (ANSI/ASHRAE Standard ) that defines what is required to conform to the protocol. Figure 1. The BACnet Logo. The BACnet specification also defines the BACnet components: the object and services model, the network layer protocol, and a selection of various network transport technologies. (See Table 1.) As a result, the BACnet specification can govern the design of workstations, controllers, gateways, routers, and diagnostic tools. BACnet Components Table 1. Components of BACnet. Description Objects Services LANs and Internetworking Methods of Representing Information Methods of Making Requests and Interoperating Transport Systems Siemens Building Technologies, Inc. 1

18 Chapter 1 Introduction to BACnet BACnet was designed specifically for all building automation applications: HVAC control Fire detection and alarm Lighting control Security Elevator interface Utility company interface To achieve these capabilities, BACnet specifies nearly all of the common building control and monitoring functions, for example: analog and binary inputs, outputs, and values; control loops; schedules, etc. One of the strengths of BACnet is in accommodating future building automation applications. A vendor can easily add to the existing objects and services. This is not only expected, it is encouraged. Of course, for proprietary features to interoperate, vendor cooperation is required. Thousands BACnet sites are already operating both in the USA and in various countries around the world. Why BACnet was Developed The idea for BACnet was fostered by building automation system (BAS) users within ASHRAE. They believed that BAS technology had progressed sufficiently that standards could be established such that products from different manufacturers could all work together. In other words, BACnet could enable control product interoperability. The benefits of interoperability to BAS users are: One workstation can work with remote panels and controls from different manufacturers More competitive bidding on expansions and additions Freedom to select the manufacturer(s) that best meet the requirements of the project at the best price Allows the addition of technologies and services as they become available, regardless of manufacturer A higher likelihood that a current system can be expanded without having to replace it entirely thus protecting the control system investment The benefits of BACnet to controls system manufacturers and suppliers are: There is no charge (license fee) for its use anyone is permitted to develop and use implementations without cost. It is maintained by an ASHRAE committee representing all sectors of the industry. 2 Siemens Building Technologies, Inc.

19 How BACnet was Developed It is designed specifically for building control. It is designed to be implemented in devices of all sizes. It is designed to be readily enhanced and improved. Its design is not tied to present technologies. How BACnet was Developed To develop BACnet, ASHRAE established a Standard Project Committee (SPC-135). The original BACnet standard was published in To help ensure acceptance, the standard had been thoroughly reviewed, studied and analyzed by the industry. The participants in the original testing became the National Institute of Standards and Technology (NIST) BACnet Interoperability Testing Consortium. BACnet was introduced at the ASHRAE Winter Meeting in January, In the BACnet booth at the show, equipment from ten different vendors running various types of computers, operating systems, and LAN types were successfully interconnected. In 2001, the BACnet standard was updated with five addenda. In January 2003, the BACnet standard was approved as ISO Standard and as a European standard within the Committee for European Standardization (CEN). The BACnet specification is maintained by ASHRAE Standing Standard Project Committee (SSPC) 135. This committee works on refining and expanding the standard. Certification Conformance of a product to the BACnet standard is the responsibility of an independent organization called the BACnet Testing Labs (BTL). The BTL develops testing tools and scripts to certify and list devices that conform to device profiles. The BTL consists of a core group sponsored by the BACnet International (BI) and individual manufacturer participation. BACnet Implementation within APOGEE The goals of Siemens Building Technologies implementation of BACnet are: Support ANSI/ASHRAE standard BACnet IP throughout field panel and workstation architecture. Meet BTL requirements for the field panel and the workstation. Meet the global strategic BACnet requirements of Siemens Building Technologies, Inc. Maintain/Enhance APOGEE Automation System features, functionality, performance, look and feel. Maintain APOGEE Automation System backward compatibility. Siemens Building Technologies, Inc. 3

20 Chapter 1 Introduction to BACnet Maintain support for LonWorks Floor Level Network (FLN), P1 FLN, OP Drivers, Insight options, and InfoCenter. This is accomplished by the introduction of a BACnet MEC and MBC, and an enhanced Insight BACnet Client and Server Option along with Navigator Support (Commissioning Tool/Design Tool) and appropriate training, documentation, and rollout. 4 Siemens Building Technologies, Inc.

21 Chapter 2 BACnet Objects and Services Chapter 2 describes BACnet Objects and Services, and how the Insight application and the BACnet Browser are used to access objects and their properties. It includes the following topics: Objects Theory Services Theory Proprietary building automation systems from different manufacturers almost always have different functionality and different communication schemes. BACnet devices, however, all share a common communication standard regardless of manufacturer and the functionality within the device. This is accomplished through the use of objects to represent data and control, and services to convey requests, data, and information. The result is that each device looks the same on the communication medium. Objects Theory To standardize different systems from multiple of manufacturers, BACnet uses objects. An object is a collection of information about a particular function that is uniquely identified and is accessed over the communication medium in a standardized way. All information in a BACnet system is represented using objects. Standardized objects make all of the devices within a BACnet system look alike. Examples of objects are analog and binary inputs and outputs, schedules, control loops, alarms, logical groupings of points that perform a specific function, software calculations, and software processes. Of course, a specific object can only exist for a manufacturers product if the product has that function that the object represents. For example, you cannot write to the schedule object of a BACnet device if the device has no schedule function. Figure 2. Examples of BACnet Objects. Siemens Building Technologies, Inc. 5

22 Chapter 2 BACnet Objects and Services Properties of Objects All BACnet objects have a set of properties that are used to either get information from the object, or give information and commands to the object. An object s properties are often represented as a table with two columns. On the left is the name or identifier for the property, and on the right is the property s value. Some properties are read only meaning that you can look at the property value, but cannot change it. Some properties can be changed (written). Standard objects can have both required properties and optional properties. Vendors can also create non-standard objects and/or properties. In the APOGEE Automation System, if a property exists in a BACnet field panel, then the property may be accessed in one of three ways: Through the field panel MMI. Through the BACnet Object Browser an Insight application feature in which the properties are listed in tabular form where they can be read or written (if applicable). Through the Insight application s windows and dialog boxes if the property needs to be read, written, or commanded for the application being used. Some properties may be renamed. For example, the Object_Identifier property is called the Instance Number in the Insight application. A property of every BACnet object that is responsible for identifying the object is called the Object_Identifier. It is a numerical value that must be unique within the BACnet device in which it resides. (Property names appear with underbars in the BACnet specification.) Each BACnet object also has an Object_Name property. This is a string of printable characters that also must be unique within the BACnet device in which it resides. To further assist a user in identifying and managing objects within a BACnet device, each BACnet object has a Description property. It is a string of printable characters, but does not have to be unique in the BACnet device. Figure 3. BACnet Analog Input Representation of a Temperature Sensor. Figure 3 is an example of a temperature sensor that might be represented as a BACnet Analog Input object. The example shows a few of the properties that might be available with this object. In practice there would be many more properties than those shown. 6 Siemens Building Technologies, Inc.

23 Objects Theory The Object_Name property has the value of SPACE TEMP and Object_Type property has the value of ANALOG INPUT. The Present_Value property is the temperature that the sensor is currently reading (72.3). The remaining properties represent other information about the sensor object, such as whether it is functioning normally, and the values of the High and Low Limits for alarming purposes. The OBJECT_TYPE Property Another property of all BACnet objects is called the Object_Type. In BACnet, 23 standard object types have been established to contain much of the information that can be associated with a building automation system. Table 2 lists these object types in seven categories. Table 2. BACnet Standard Object Types. Object Type Point-like Binary Input Binary Output Binary Value Analog Input Analog Output Analog Value Multi-state Input Multi-state Output Multi-state Value Event Enrollment Event Reporting Scheduling/Logging Notification Class Schedule Calendar Trend Log Control Program Loop Averaging Life Safety Point Group Device Life Safety Grouping Device Level Life Safety Zone Command Each occurrence of an object within a device is marked by the Instance Number. For example, if there are three Notification Class objects in a device, they will carry Instance Numbers 1, 2 and 3, respectively. Some objects have the Instance Number as a property. For example, in the Notification Class object, the value of its Notification_Class property is its Instance Number. The Instance Number is part of what makes up an object s Object_Identifier property. The relationship is: Object_Identifier = Object_Type + Instance Number File Siemens Building Technologies, Inc. 7

24 Chapter 2 BACnet Objects and Services Command Priority Properties BACnet has an application-controlled prioritization mechanism, the Command Priority Array, that determines which application is commanding an object property. The Command Priority Array is similar to the Point Command Priority in the APOGEE Automation System. The BACnet properties that implement the command priority array are Priority_Array and Relinquish_Default. Every commandable object property supports a 16-slot Priority_Array plus a Relinquish_Default value that serves as a default if no applications are controlling the object value when all 16 slots are empty. Figure 4 shows the standard priorities within the 16 slots along with BACnet s recommended applications for these priorities. The unused slots are available for other priorities. Figure 4. BACnet Standard Priorities. When multiple applications, each with a different priority, have active commands to the object, the object decides which to accept based on the relative priorities of the applications. As commands are set and released, the object will continuously re-evaluate which command to use. Each commanding application must stay in its own priority slot and not interfere with commands from other applications. If all commands are released, the object will default to the value held in the mandatory Relinquish_Default object property. Figure 5 shows an example of how the Command Priority Array operates. 8 Siemens Building Technologies, Inc.

25 Objects Theory Figure 5. Example of the BACnet Command Priority Array Operation. Command Priority Array vs. APOGEE The BACnet Command Priority Array, which is similar to APOGEE s Point Command Priority, manages the Present_Value property. Each Insight application that commands points has a configurable default priority that is used for point commands and releases. Table 3 shows the Command Priority Array, along with the default mapping to APOGEE priorities. If desired, any of the six defaults can be changed by the user. For OPERATOR, the value in the table is used as the highest priority slot available for commanding. For example, the user can command at this priority and lower. Table 3. BACnet Command Priority Array Mapped to APOGEE Priorities. Slot BACnet Names APOGEE Priority 1 Manual Life Safety 2 Automatic Life Safety 3 Available 4 Available 5 Critical Equipment Control 6 Minimum On/Off 7 Available 8 Manual Operator OPERATOR 9 Available 10 Available SMOKE 11 Available 12 Available EMERGENCY 13 Available Siemens Building Technologies, Inc. 9

26 Chapter 2 BACnet Objects and Services Slot BACnet Names APOGEE Priority 14 Available PDL 15 Available 16 Available SCHEDULING, PPCL, NONE, TEC TOOL Relinquish Default TEC APPLICATION BACnet commands do not provide enough information for CFR-11 logging. As a result, the CFR-11 feature is not available in the BACnet field panel. Modifying the Priority Array The BACnet Priority Array can be modified from the System menu in the Insight System Profile application (Figure 6). Figure 6. Accessing Priority Array from System Profile. The BACnet Command Priority Array dialog box (Figure 7) displays the current Text and Abbreviated Text for each priority level. 10 Siemens Building Technologies, Inc.

27 Objects Theory Figure 7. Command Priority Array Dialog Box. The Edit button allows modification of the Priority Text and Abbreviated Text via the Modify Priority Text dialog box (Figure 8). Figure 8. Modify Priority Text Dialog Box. After clicking OK in both dialog boxes, the BACnet Command Priority Array dialog displays the updated priority text (Figure 9). Siemens Building Technologies, Inc. 11

28 Chapter 2 BACnet Objects and Services Operation Figure 9. BACnet Command Priority Array after Modification. The BACnet priority array operation can cause different operation at times when compared to the current APOGEE Automation System. The following scenario illustrates the change: APOGEE Automation System: 1) The Scheduler application turns the lights off at the end of the workday. 2) A maintenance technician uses the Insight workstation to command the lights ON. 3) After performing service, the maintenance technician releases the command. 4) The end result is that the lights remain ON all night. BACnet: 1) The equipment scheduler turns the lights off at the end of the workday. 2) A maintenance technician uses the Insight workstation to command the lights ON. 3) After performing service, the maintenance technician releases the command, returning control of the lights to the scheduler application, which turns the light OFF. 4) The lights remain OFF until commanded ON by the scheduler the next morning. Another difference is that with BACnet, unlike the current APOGEE Automation System, commands cannot be dropped if the priority of the command is lower than the existing priority. The lower priority command must be properly entered into the command priority table for implementation whenever the higher priority command is released. Another difference is that input points can be commanded when the object is out of service. The APOGEE Automation System selectively restricts input commanding for local points, but allows it for TEC subpoints. In BACnet, any point that is out of service can be commanded. Conversely, a physical point must be out of service to be commanded. 12 Siemens Building Technologies, Inc.

29 Objects Theory Impact to MMI The MMI must show which priority array entry is currently controlling the object. The MMI must also allow configuration of the highest priority allowed, such that priority levels used for life safety may be intentionally prohibited or allowed. See Point Objects for exact details. Impact to PPCL PPCL, like all of the other BACnet APOGEE applications that commands points, has a configurable default priority that is used for point commands and releases. Upon saving a new PPCL program in the Program Editor application, the Save As dialog box prompts the user to choose a priority level (Figure 10). The choices are established in the user s account. PPCL programs will use the PPCL default priority level for point commands and releases if a priority is not specified in the statement. If a PPCL Command Priority (default priority) is not selected when a new program is saved, the PPCL value in the table (for example, BACnet priority level 16 if Table 3 were to apply) is used as the default priority level for the whole program. Figure 10. PPCL Command Priority Setting. A BACnet field panel positively acknowledges a command without changing the value if the value is under the control of higher priority. This is a change in operation from non-bacnet field panels, in which the PPCL interpreter would continuously re-command the point if the value didn t change. Additionally, in a BACnet field panel, the RELEASE statement releases only the one priority level that is designated after symbol. If priority is defined, RELEASE will default to releasing level 16. Therefore, when using existing PPCL programs that and Release, check if they have to be re-written to operate correctly. When using statements in BACnet field panels, only the top four APOGEE priorities (with their BACnet priority equivalents) can be used. For example. if Table 3 were the BACnet to APOGEE priority mapping for a field panel, then only OPERATOR, SMOKE, EMER and PDL can be used in statements. Siemens Building Technologies, Inc. 13

30 Chapter 2 BACnet Objects and Services Impact to TEC Subpoints In a BACnet field panel, commanding a TEC point will cause it to unbundle and use additional field panel memory. Like with any other point, the Present_Value will be set to the highest priority level. When a TEC point is browsed, the Relinquish_Default property will contain the current Present_Value of the point, and the Priority_Array property will initially display as empty. EEPROM points can only be written by commands with a priority higher (smaller priority number) than OPERATOR. Therefore, EEPROM points cannot be commanded by PPCL. If a remote third-party device commands an EEPROM point and the command has a priority higher than OPERATOR, the command will be blocked. The point s Reliability property will display Unreliable because the Present Value and the Relinquish_Default disagree. BACnet Device A BACnet Device is a collection of objects that represent the functions actually present in a given real device. Figure 11 shows one example of how a group of objects make up a field panel type of BACnet device. Although only one instance of each kind of object is shown, a more typical field panel type of BACnet device might have 16 DI and DO objects, two or three Schedule objects, etc. Figure 11. Example BACnet Device. Note that a BACnet Device contains something called a Device object. The properties of this object are where information about the BACnet device resides. The properties include the device s manufacturer and model number. There is only one Device object in a BACnet Device. The Device object s Object_Identifier property uniquely identifies the BACnet device on the communications network. Therefore, the Object_Identifier number must be unique on the network. The Device object also has an Object_Name property, which also must be unique on the network. Table 4 shows the properties of the Device object along with information about how they interface to the APOGEE Automation System. 14 Siemens Building Technologies, Inc.

31 Objects Theory Table 4. Device Object Properties. Property_Identifier Support Access Notes Object_Identifier Yes Range is 0 to 4 MB. Configured in IP Settings. Object_Name Yes Field Panel Name, limited to 30 characters, Configured in IP Settings. Object_Type Yes Encoded name component BACDev System_Status Yes OPERATIONAL status used to set Ready status Vendor_Name Yes "Siemens BAU" Vendor_Identifier Yes All Siemens ISA devices = 7 Model_Name Yes "Siemens BACnet EMEC" Firmware_Revision Yes Firmware Rev String that is, "BCE V3.0 APOGEE Application_Software_Version Yes Firmware Rev String that is, "BCE3001 Location Yes Limited to 40 characters, Configured in IP Settings. Description Yes Limited to 40 characters, Configured in IP Settings. Protocol_Version Yes 1 Protocol_Revision Yes 4 Protocol_Services_Supported Yes See Table 14 for a listing of supported services. Protocol_Object_Types _Supported Yes See the Object Summary table in Chapter 5 BACnet Field Panels. Object_List Yes List of object Ids for all points in this field panel. Max_APDU_Length_Accepted Yes 1497 Segmentation_Supported Yes BACNET_SEGMENTATION_TYPE_BOTH Max_Segments_Supported Yes 32 VT_Classes_Supported Active_VT_Sessions Local_Time Yes Field Panel Time Local_Date Yes Field Panel Date No No UTC_Offset No The number of minutes between the local time and UTC time. Daylight_Savings_Status Yes APDU_Segment_Timeout Yes 3000 APDU_Timeout Yes 3000 Number_Of_APDU_Retries Yes 3 List_Of_Session_Keys Time_Sync_Recipients Max_Master Max_Info_Frames No No No No Siemens Building Technologies, Inc. 15

32 Chapter 2 BACnet Objects and Services Property_Identifier Support Access Notes Device_Address_Binding Yes Database_Revision Yes Logical revision number for the database, incremented when objects are created and/or deleted, an object's name is changed, or a database restore is performed. Configuration_Files Yes List of files to be backed up. Valid only during the backup procedure. Last_Restore_Time Yes Time of last file download. Applies only to BACnet file transfer services. Backup_Failure_Timeout Yes Writable How long to wait before aborting a backup or restore operation. Active_COV_Subscriptions Yes A list of active subscriptions. Applies to the server side. Slave_Proxy_Table Manual_Slave_Address_Binding Auto_Slave_Discovery Slave_Address_Binding Profile_Name Point-Like Objects No No No No No Table 2 lists the BACnet objects that resemble points in a building automation system. As with all BACnet objects, point-like objects are just representations of a BACnet device s points to other BACnet devices on the network. The points structure inside of the manufacturer s device may be entirely different perhaps representing the manufacturer s proprietary and/or legacy software architecture. The following are some of the highlights of the point-like objects. Analog Input Object The Analog Input Object is a representation of a physical analog input point in the BACnet device. Table 5 shows the properties of the Analog Input object along with information about how they interface to the APOGEE Automation System. Table 5. Analog Input Object Properties. Property_Identifier Support Access Notes Object_Identifier Yes Range is 0 to 4 MB. Automatically assigned by default. Object_Name Yes System Name, limited to 30 characters. Object_Type Yes Encoded name component AI. Present_Value Yes Writable REAL Description Yes Writable Limited to 16 characters. 16 Siemens Building Technologies, Inc.

33 Objects Theory Property_Identifier Support Access Notes Device_Type Yes Text corresponding to the APOGEE LAI sensor type is as follows: "current" "voltage" "pneumatic" "100k Thermistor" "1K Platinum RTD" "LType" "custom" Status_Flags Yes IN_ALARM = true if point is in alarm, else false. FAULT = true if point is failed, else false. OVERRIDDEN = true if point is in hand mode, else false. OUT_OF_SERVICE = false. Event_State Yes If point is in alarm, then Event_State = OFFNORMAL, else if point is failed, then Event_State = FAULT, else Event_State = NORMAL. Reliability Yes If point is in trouble, then Reliability = OPEN_LOOP, else if point is failed, then Reliability = UNRELIABLE_OTHER, else Reliability = NO_FAULT_DETECTED. Out_Of_Service Yes Writable Must be set to override Present_Value. Update_Interval No Units Yes Writable Uses BACnet enumeration corresponding to fixed engineering units strings. Min_Pres_Value Max_Pres_Value No No Resolution Yes Slope COV_Increment Yes Writable COV Limit Time_Delay Alarm Always equals zero. Notification Class Alarm Writable High_Limit Alarm Writable High Limit Low_Limit Alarm Writable Low Limit Deadband Alarm Always equals zero. Limit_Enable Alarm If alarming enabled, then low_limit and high_limit both enabled. Event_Enable Alarm Writable If alarming enabled, then to-offnormal, to-fault, and to-normal all set to TRUE. Acked_Transitions Alarm Indicates which of the transitions have been acknowledged, TO_OFFNORMAL, TO_FAULT, TO_NORMAL. Notify_Type Alarm Always = Alarm Event_Time_Stamps Alarm Timestamps of the following event transitions, TO_OFFNORMAL, TO_FAULT, TO_NORMAL. Profile_Name No The Present_Value property is the current value of the point. Note that the Out_Of_Service property must be TRUE, before you can write a value into the Present_Value property. Siemens Building Technologies, Inc. 17

34 Chapter 2 BACnet Objects and Services Analog Output Object The Analog Output Object is a representation of a physical analog output point in the BACnet device. Table 6 shows the properties of the Analog Output object along with information about how they interface to the APOGEE Automation System. Table 6. Analog Output Object Properties. Property_Identifier Support Access Notes Object_Identifier Yes Range is 0 to 4 MB. Automatically assigned by default. Object_Name Yes System Name, limited to 30 characters. Object_Type Yes Encoded name component AO. Present_Value Yes Writable REAL Description Yes Writable Limited to 16 characters. Device_Type Yes Associated APOGEE Point type. Status_Flags Yes IN_ALARM = true if point is in alarm, else false. FAULT = true if point is failed, else false. OVERRIDDEN = true if point is in hand mode, else false. OUT_OF_SERVICE = false. Event_State Yes If point is in alarm, then Event_State = OFFNORMAL, else if point is failed, then Event_State = FAULT, else Event_State = NORMAL. Reliability Yes if point is in trouble, then Reliability = OPEN_LOOP, else if point is failed, then Reliability = UNRELIABLE_OTHER, else Reliability = NO_FAULT_DETECTED. Out_Of_Service Yes Always FALSE Units Yes Uses BACnet enumeration corresponding to fixed engineering units strings. Min_Pres_Value Max_Pres_Value No No Resolution Yes Slope Priority_Array Yes For commanding the present value. Relinquish_default Yes For releasing the present value when the Priority Array is empty. COV_Increment Yes Writable COV Limit Time_Delay Alarm Always equals zero. Notification Class Alarm Writable High_Limit Alarm Writable High Limit Low_Limit Alarm Writable Low Limit Deadband Alarm Always equals zero. Limit_Enable Alarm If alarming enabled, then low_limit and high_limit both enabled. Event_Enable Alarm Writable If alarming enabled, then to-offnormal, to-fault, and to-normal all set to TRUE. 18 Siemens Building Technologies, Inc.

35 Objects Theory Property_Identifier Support Access Notes Acked_Transitions Alarm Indicates which of the transitions have been acknowledged, TO_OFFNORMAL, TO_FAULT, TO_NORMAL. Notify_Type Alarm Always equals Alarm. Event_Time_Stamps Alarm Timestamps of the following event transitions, TO_OFFNORMAL, TO_FAULT, TO_NORMAL. Profile_Name No The Present_Value property is the current value of the point. Since this is an output, its Present_Value property is always writeable. Analog Value Object The Analog Value Object is a representation of a virtual analog output point or a software parameter in the BACnet device. Table 7 shows the properties of the Analog Value object along with information about how they interface to the APOGEE Automation System. Table 7. Analog Value Object Properties. Property_Identifier Support Access Notes Object_Identifier Yes Range is 0 to 4 MB. Automatically assigned by default. Object_Name Yes System Name, limited to 30 characters. Object_Type Yes Encoded name component AV Present_Value Yes Writable REAL Description Yes Writable Limited to 16 characters. Status_Flags Yes IN_ALARM = true if point is in alarm, else false. FAULT = true if point is failed, else false. OVERRIDDEN = true if point is in hand mode, else false. OUT_OF_SERVICE = false. Event_State Yes If point is in alarm, then Event_State = OFFNORMAL, else if point is failed, then Event_State = FAULT, else Event_State = NORMAL. Reliability Yes If point is in trouble, then Reliability = OPEN_LOOP, else if point is failed, then Reliability = UNRELIABLE_OTHER, else Reliability = NO_FAULT_DETECTED. Out_Of_Service Yes Always FALSE. Units Yes Uses BACnet enumeration corresponding to fixed engineering units strings. Priority_Array Yes For commanding the present value. Relinquish_default Yes For releasing the present value when the Priority Array is empty. COV_Increment Yes Writable COV Limit Time_Delay Alarm Always equals zero. Notification Class Alarm Writable Siemens Building Technologies, Inc. 19

36 Chapter 2 BACnet Objects and Services Property_Identifier Support Access Notes High_Limit Alarm Writable High Limit Low_Limit Alarm Writable Low Limit Deadband Alarm Always equal zero. Limit_Enable Alarm If alarming enabled, then low_limit and high_limit both enabled. Event_Enable Alarm Writable If alarming enabled, then to-offnormal, to-fault, and to-normal all set to TRUE. Acked_Transitions Alarm Indicates which of the transitions have been acknowledged, TO_OFFNORMAL, TO_FAULT, TO_NORMAL. Notify_Type Alarm Always equals Alarm. Event_Time_Stamps Alarm Timestamps of the following event transitions, TO_OFFNORMAL, TO_FAULT, TO_NORMAL. Profile_Name No The Present_Value property is the current value of the point. Note that it should be writeable if it is commandable or if Out_Of_Service is TRUE. Binary Input Object The Binary Input Object is a representation of a physical binary or digital input point in the BACnet device. Table 8 shows the properties of the Binary Input object along with information about how they interface to the APOGEE Automation System. Table 8. Binary Input Object Properties. Property_Identifier Support Access Notes Object_Identifier Yes Range is 0 to 4 MB. Automatically assigned by default. Object_Name Yes System Name, limited to 30 characters. Object_Type Yes Encoded name component BI. Present_Value Yes Writable Binary Value Description Yes Writable Limited to 16 characters. Device_Type Yes Associated APOGEE Point type Status_Flags Yes IN_ALARM = true if point is in alarm, else false. FAULT = true if point is failed, else false. OVERRIDDEN = true if point is in hand mode, else false. OUT_OF_SERVICE = false. Event_State Yes If point is in alarm, then Event_State = OFFNORMAL, else if point is failed, then Event_State = FAULT, else Event_State = NORMAL. Reliability Yes if point is in trouble, then Reliability = OPEN_LOOP, else if point is failed, then Reliability = UNRELIABLE_OTHER, else Reliability = NO_FAULT_DETECTED. Out_Of_Service Yes Writable Must be set in order to override the Present_Value. 20 Siemens Building Technologies, Inc.

37 Objects Theory Property_Identifier Support Access Notes Polarity Yes Normally Closed Inactive_Text Yes Correspond with first entry in the points State Text Table. Active_Text Yes Correspond with second entry in the points State Text Table. Change_Of_State_Time Change_Of_State_Count Time_Of_ State_Count_Reset No No No Elapsed_Active_Time Yes Writable Totalization Time_Of_ Active_Time_Reset Yes Totalization_Reset_Time Time_Delay Alarm Always equals zero. Notification Class Alarm Writable Alarm_Value Alarm Specifies what the Present_Value is when the point is in Alarm. Event_Enable Alarm Writable If alarming enabled, then to-offnormal, to-fault, and to-normal all set to TRUE. Acked_Transitions Alarm Indicates which of the transitions have been acknowledged, TO_OFFNORMAL, TO_FAULT, TO_NORMAL. Notify_Type Alarm Always equals Alarms Event_Time_Stamps Alarm Timestamps of the following event transitions, TO_OFFNORMAL, TO_FAULT, TO_NORMAL. Profile_Name No The Present_Value property is the current value of the point. Note that the Out_Of_Service property must be TRUE for the Present_Value to be writeable. The Polarity property indicates the relationship of the physical state of the input to the logical state represented by the Present_Value property. Binary Output Object The Binary Output Object is a representation of a physical Binary output point in the BACnet device. Table 9 shows the properties of the Binary Output object along with information about how they interface to the APOGEE Automation System. Table 9. Binary Output Object Properties. Property_Identifier Support Access Notes Object_Identifier Yes Range is 0 to 4 MB. Automatically assigned by default. Object_Name Yes System Name, limited to 30 characters. Object_Type Yes Encoded name component BO. Present_Value Yes Writable Binary Value Description Yes Writable Limited to 16 characters. Siemens Building Technologies, Inc. 21

38 Chapter 2 BACnet Objects and Services Property_Identifier Support Access Notes Device_Type Yes Associated APOGEE Point type Status_Flags Yes IN_ALARM = true if point is in alarm, else false. FAULT = true if point is failed, else false. OVERRIDDEN = true if point is in hand mode, else false. OUT_OF_SERVICE = false. Event_State Yes If point is in alarm, then Event_State = OFFNORMAL, else if point is failed, then Event_State = FAULT, else Event_State = NORMAL. Reliability Yes if point is in trouble, then Reliability = OPEN_LOOP, else if point is failed, then Reliability = UNRELIABLE_OTHER, else Reliability = NO_FAULT_DETECTED. Out_Of_Service Yes Always FALSE. Polarity Yes Inverted Inactive_Text Yes Correspond with first entry in the points State Text Table. Active_Text Yes Correspond with second entry in the points State Text Table. Change_Of_State_Time Change_Of_State_Count Time_Of_ State_Count_Reset No No No Elapsed_Active_Time Yes Writable Totalization Time_Of_ Active_Time_Reset Minimum_Off_time Minimum_On_time Yes No No Totalization_Reset_Time Priority_Array Yes For commanding the present value. Relinquish_default Yes For releasing the present value when the Priority Array is empty. Time_Delay Alarm Proof Delay Notification Class Alarm Writable Feedback_Value Alarm Current value of the proof point for APOGEE proof points, set equal to the Present_Value for points without proofing. Event_Enable Alarm Writable If alarming enabled, then to-offnormal, to-fault, and to-normal all set to TRUE. Acked_Transitions Alarm Indicates which of the transitions have been acknowledged, TO_OFFNORMAL, TO_FAULT, TO_NORMAL. Notify_Type Alarm Always equals Alarm. Event_Time_Stamps Alarm Timestamps of the following event transitions, TO_OFFNORMAL, TO_FAULT, TO_NORMAL. Profile_Name No The Present_Value property is the current value of the point. Since this is an output, its Present_Value property is always writeable. 22 Siemens Building Technologies, Inc.

39 Objects Theory Binary Value Object The Binary Value Object is a representation of a virtual Binary output point or a software parameter in the BACnet device. Table 10 shows the properties of the Binary Value object along with information about how they interface to the APOGEE Automation System. Table 10. Binary Value Object Properties. Property_Identifier Support Access Notes Object_Identifier Yes Range is 0 to 4 MB. Automatically assigned by default. Object_Name Yes System Name, limited to 30 characters. Object_Type Yes Encoded name component BV. Present_Value Yes Writable Binary Value Description Yes Writable Limited to 16 characters. Status_Flags Yes IN_ALARM = true if point is in alarm, else false. FAULT = true if point is failed, else false. OVERRIDDEN = true if point is in hand mode, else false. OUT_OF_SERVICE = false. Event_State Yes If point is in alarm, then Event_State = OFFNORMAL, else if point is failed, then Event_State = FAULT, else Event_State = NORMAL. Reliability Yes if point is in trouble, then Reliability = OPEN_LOOP, else if point is failed, then Reliability = UNRELIABLE_OTHER, else Reliability = NO_FAULT_DETECTED. Out_Of_Service Yes Always FALSE. Inactive_Text Yes Correspond with first entry in the points State Text Table. Active_Text Yes Correspond with second entry in the points State Text Table. Change_Of_State_Time Change_Of_State_Count Time_Of_ State_Count_Reset No No No Elapsed_Active_Time Yes Writable Totalization Time_Of_ Active_Time_Reset Minimum_Off_time Minimum_On_time Yes No No Totalization_Reset_Time Priority_Array Yes For commanding the present value. Relinquish_default Yes For releasing the present value when the Priority Array is empty. Time_Delay Alarm Proof Delay Notification Class Alarm Writable Alarm_Value Alarm Specifies what the Present_Value is when the point is in Alarm. Siemens Building Technologies, Inc. 23