Embed Size (px)
Citation preview
www.sbt.siemens.com
BACnetApplication Guide
Rev. 3
BACnet® for APOGEE Systems Application Guide 125-1984 Rev. 3, September, 2013 Restricted
Rev. 3, September, 2013
NOTICE
The information contained within this document is subject to change without notice and should not be construed as a commitment by Siemens Industry, Inc. Siemens Industry, 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 Industry, 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 Industry, Inc. representative.
Copyright 2013 by Siemens Industry, Inc.
TO THE READER
Your feedback is important to us. If you have comments about this manual, please submit them to: [email protected]
APOGEE is a registered trademark of Siemens Industry, 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 Industry, Inc. Insight for Personal Computers is a registered trademark of Siemens Industry, Inc. Country of Origin: US
Siemens Industry, Inc. i
Table of Contents About this Application Guide ........................................................................................ I
Purpose and Intended Audience of this Guide .............................................................. II
How this Guide is Organized .......................................................................................... II
Suggested Reference Materials .................................................................................... III
Symbols ......................................................................................................................... III
Getting Help .................................................................................................................. IV
Where to Send Comments ............................................................................................ IV
Chapter 1–Overview of Siemens BACnet Products and Solutions ................................. 7
Brief History of BACnet Implementation within APOGEE .............................................. 7
Architecture Overview of APOGEE BACnet System ..................................................... 14
BACnet Networks Overview ...................................................................................... 14
Panel Connections ..................................................................................................... 15
Routers ....................................................................................................................... 15
Network Numbering .................................................................................................. 15
Some Basic BACnet Terminology ................................................................................. 15
BACnet/IP ................................................................................................................... 16
BACnet Client/Server ................................................................................................. 16
User Datagram Protocol (UDP) .................................................................................. 16
Internet Protocol ....................................................................................................... 16
MS/TP Networks ........................................................................................................ 16
MS/TP Addressing ...................................................................................................... 17
Chapter 2–BACnet Objects and Services ..................................................................... 19
Objects Theory ............................................................................................................. 19
Properties of Objects ................................................................................................. 20
The OBJECT_TYPE Property ..................................................................................... 21
Command Priority Properties .................................................................................. 22
BACnet Device ........................................................................................................... 29
Point-Like Objects ...................................................................................................... 31
Analog Input Object ................................................................................................ 32
Analog Output Object ............................................................................................. 33
Analog Value Object ................................................................................................ 35
Binary Input Object ................................................................................................. 36
Table of Contents
ii Siemens Industry, Inc.
Binary Output Object .............................................................................................. 37
Binary Value Object ................................................................................................. 39
Multi-state Input Object .......................................................................................... 40
Multi-state Output Object ....................................................................................... 41
Multi-state Value Object ......................................................................................... 42
Other Objects Supported by APOGEE BACnet Field Panels ...................................... 43
Calendar Object ....................................................................................................... 43
Command Object ..................................................................................................... 43
File Object ................................................................................................................ 44
Notification Class Object ......................................................................................... 44
Schedule Object ....................................................................................................... 44
Trend Log Object ..................................................................................................... 44
Viewing with the BACnet Browser ............................................................................. 44
Services Theory ............................................................................................................ 46
Services Supported .................................................................................................... 48
Services Not Supported ............................................................................................. 49
Chapter 3–BACnet Interoperability ............................................................................ 51
Interoperability ............................................................................................................ 51
Certification .................................................................................................................. 52
Specifying BACnet ...................................................................................................... 53
Protocol Implementation and Conformance Statement ........................................ 53
BACnet Interoperable Building Blocks .................................................................... 55
BACnet Device Profiles ................................................................................................. 59
BACnet Building Controller Profile (B-BC), Advanced Application Controller Profile (B-AAC), and Advanced Workstation Profile (B-AWS) ............................................... 60
APOGEE BACnet Field Panel Interoperability .............................................................. 64
Data Sharing ............................................................................................................... 65
Object Names and Instance Numbers ..................................................................... 65
Services Supported .................................................................................................. 66
Objects Supported ................................................................................................... 66
Services to Support the BACnet Browser ................................................................ 66
PPCL ......................................................................................................................... 66
TEC Subpoints .......................................................................................................... 66
Point Commanding .................................................................................................. 67
Table of Contents
Siemens Industry, Inc. iii
Alarm and Event Management .................................................................................. 67
System Messages .................................................................................................... 67
COVs ........................................................................................................................ 67
Scheduling .................................................................................................................. 68
Command Object ..................................................................................................... 68
Trending ..................................................................................................................... 68
Device And Network Management ........................................................................... 68
Upload and Download ............................................................................................. 68
Dialout ..................................................................................................................... 68
Proprietary Applications .......................................................................................... 68
Field Panel Tools ...................................................................................................... 69
Foreign Device ......................................................................................................... 69
BBMD ....................................................................................................................... 69
Backup and Restore Password ................................................................................ 69
Insight Interoperability ................................................................................................. 69
BACnet Client and Server Options ............................................................................. 70
Insight Data Sharing ................................................................................................... 70
Point-Like Objects .................................................................................................... 70
Point Names ............................................................................................................ 70
BACnet Object Browser ........................................................................................... 71
Point Commanding .................................................................................................. 71
Third-Party Proprietary Objects .............................................................................. 71
Insight Alarm and Event Management ...................................................................... 71
Initials ...................................................................................................................... 71
Alarm Acknowledgements ...................................................................................... 72
Notification Class ..................................................................................................... 72
Insight Scheduling ...................................................................................................... 72
Command Object Editing ........................................................................................ 74
Insight Trending ......................................................................................................... 74
Insight Device and Network Management ................................................................ 74
Field Panel Database Upload/Download ................................................................ 75
Foreign Device ......................................................................................................... 75
Cloaking ................................................................................................................... 75
BBMD ....................................................................................................................... 75
Table of Contents
iv Siemens Industry, Inc.
Database Transfer of Object Types ......................................................................... 75
BACnet Field Panel Definition ................................................................................. 75
Backup and Restore Password ................................................................................ 76
Field Level Network Devices .................................................................................... 76
Cross-Trunk .............................................................................................................. 76
Upload and Download ............................................................................................. 76
DesigoTM CC .................................................................................................................. 76
Compatibility .............................................................................................................. 77
BACnet Firmware Compatibility with Desigo CC Software ..................................... 78
Desigo CC Scheduling ................................................................................................. 79
Desigo CC Device and Network Management ........................................................... 80
Open Architecture ..................................................................................................... 81
Examples of Third-Party Equipment Integration ......................................................... 82
APOGEE BACnet Product Positioning ........................................................................ 83
BACnet Solutions ..................................................................................................... 83
Chapter 4–BACnet Communications ........................................................................... 85
BACnet Networking Technologies................................................................................ 85
BACnet Over Ethernet ............................................................................................... 86
BACnet/IP ................................................................................................................... 86
Master-Slave/Token-Passing ..................................................................................... 86
LonTalk ....................................................................................................................... 87
BACnet Protocol Model ............................................................................................. 87
BACnet Cimetrics BACstac ....................................................................................... 90
Basic BACnet Networking .......................................................................................... 91
Native BACnet Devices on the Same LAN ............................................................... 91
Native BACnet Devices with Different LAN Technologies ....................................... 91
Native BACnet to Non-Native BACnet Devices ....................................................... 92
BACnet Communications ........................................................................................... 93
BACnet/IP ................................................................................................................ 93
BACnet Broadcast Management Device (BBMD) .................................................... 94
BACnet Foreign Devices .......................................................................................... 97
BACnet Router vs. IP Router .................................................................................... 98
APOGEE Communication with BACnet ........................................................................ 99
BACnet Client and Server Options ............................................................................. 99
Table of Contents
Siemens Industry, Inc. v
BACnet Client ......................................................................................................... 100
BACnet Server ........................................................................................................ 100
BACnet MS/TP .......................................................................................................... 101
BACnet MS/TP Performance Guidelines ............................................................... 102
RS-485 MS/TP ALN ................................................................................................ 106
BACnet MS/TP ALN Performance Considerations................................................. 107
Advantages for products residing on BACnet MS/TP ALN .................................... 108
Disadvantages for products residing on BACnet MS/TP ALN ............................... 109
RS-485 MS/TP FLN ................................................................................................. 109
BACnet MS/TP FLN Performance Considerations ................................................. 110
Disadvantages for Products Residing on BACnet MS/TP FLN ............................... 114
BACnet MS/TP FLN Design Considerations ........................................................... 114
BACnet Driver for Firmware .................................................................................. 115
BACnet MS/TP Router ........................................................................................... 122
Physical Network Configurations ............................................................................. 123
Insight with Dedicated ALN on Separate MLN and BACnet Networks ................. 123
Insight with Dedicated ALN on a Common MLN/BACnet Network ...................... 124
Insight with a Remote AEM ALN on a Common MLN/BACnet ALN ...................... 126
Insight with APOGEE BACnet Field Panels on a Common MLN/BACnet ALN ....... 127
Insight with Routers Using BBMDs and Foreign Devices ...................................... 129
BACnet Network Communication Features ............................................................ 130
BACnet Broadcast Management Device Functionality ......................................... 130
Foreign Device ....................................................................................................... 132
Cross-Trunk Communications ............................................................................... 133
BACnet Network COVs .......................................................................................... 134
Network Bandwidth Usage ................................................................................... 135
Insight BACnet Option Security ............................................................................. 136
Device Discovery ................................................................................................... 136
Time Synchronization ............................................................................................ 139
Example BACnet Job (Internetwork) ....................................................................... 142
System Configuration ............................................................................................ 142
Chapter 5–BACnet Field Panel ................................................................................... 149
APOGEE BACnet Field Panel ....................................................................................... 149
APOGEE P2 and BACnet Comparison ...................................................................... 149
Table of Contents
vi Siemens Industry, Inc.
Field Panel Hardware ............................................................................................... 150
Maximum Number of MS/TP Devices per Network ................................................ 154
Field Panel Features ................................................................................................. 155
APOGEE BACnet Firmware Compatibility with Insight ............................................ 155
Firmware Compatibility Chart ................................................................................. 157
PXC Modular Series for BACnet Networks .............................................................. 159
PXC Compact Series for BACnet Networks .............................................................. 159
Power MEC for BACnet ............................................................................................ 160
BTL Certification ....................................................................................................... 161
Firmware .................................................................................................................... 162
Object Basics ............................................................................................................ 162
Object Support Summary ...................................................................................... 162
Object Names and Instance Numbers ................................................................... 165
Encoded Object Names ......................................................................................... 165
Device Specific Names ........................................................................................... 167
Instance Number Allocation .................................................................................. 167
Point-Like Objects .................................................................................................... 167
BACnet Implementation of APOGEE Logical Points .............................................. 167
The Command Priority Array ................................................................................... 168
TEC Subpoints ........................................................................................................ 168
FLN Commands ...................................................................................................... 170
Relinquish Default ................................................................................................. 171
The Out-Of-Service Property ................................................................................. 171
Engineering Units .................................................................................................. 172
State Text ............................................................................................................... 172
Totalization ............................................................................................................ 172
Pulse Accumulator ................................................................................................. 173
Network Management ............................................................................................ 173
BBMD Routing Tables ............................................................................................ 173
Foreign Device Support ......................................................................................... 174
DHCP and DNS Support ......................................................................................... 174
Trending ................................................................................................................... 174
Alarm and Event Applications .................................................................................. 175
Alarms .................................................................................................................... 175
Table of Contents
Siemens Industry, Inc. vii
Events–System Messages ...................................................................................... 175
Scheduling ................................................................................................................ 176
PPCL ......................................................................................................................... 177
Resident Points ........................................................................................................ 179
APOGEE BACnet Field Panel Firmware Revision 3.2.4 ............................................... 181
Certifications ............................................................................................................ 182
APOGEE Firmware Revision 3.2.3 .............................................................................. 182
APOGEE Firmware Revision 3.2.2 .............................................................................. 183
HMI ............................................................................................................................. 183
Application Summary............................................................................................... 183
System Summary ..................................................................................................... 183
Point Command Priority .......................................................................................... 184
Chapter 6–BACnet FLN Devices ................................................................................. 185
BACnet Programmable TEC (PTEC) ............................................................................ 185
Systems Integration Benefits ................................................................................... 186
Field Panel Requirements ........................................................................................ 186
Required Components ............................................................................................. 186
Software ................................................................................................................ 186
Hardware ............................................................................................................... 186
PTEC Controller Applications, Product Numbers, and Firmware Revisions ............ 187
BACnet Standardized Device Profiles and Interoperabiltiy Building Blocks (BIBBs) for PTECs ........................................................................................................................ 188
BACnet PTEC Terminal Box VAV Controller ........................................................... 188
BACnet PTEC VAV with Series Fan and 3-Stage Electric Heat Controller .............. 189
BACnet PTEC Unit Conditioner (Fan Coil) Controller ............................................ 190
BACnet PTEC Unit Vent Controller ........................................................................ 191
BACnet PTEC Heat Pump Controller ...................................................................... 191
BACnet PTEC Extended I/O Controller .................................................................. 192
BACnet PTEC Dual Duct Controller ........................................................................ 193
BACnet PTEC Constant Volume Controllers .......................................................... 193
BACnet Programmable VAV with Chilled Beam, CO2-Based Demand Control Ventilation, Floating or Analog Output ................................................................. 194
Chapter 7–BACnet Field Panel Web Server ................................................................ 197
Basic Product Description .......................................................................................... 197
Table of Contents
viii Siemens Industry, Inc.
Web Server Communication ...................................................................................... 199
Network Bandwidth Effect ......................................................................................... 199
Web Server Limitations .............................................................................................. 200
Web Server Access and Security ................................................................................ 200
Remote Access to Building Automation System ........................................................ 203
Chapter 8–Insight BACnet Option .............................................................................. 211
Insight BACnet Option ................................................................................................ 211
Native BACnet and B-OWS ...................................................................................... 211
Backward Compatibility ........................................................................................... 212
Insight Features for BACnet ....................................................................................... 212
Alarms ...................................................................................................................... 212
Point Priority.......................................................................................................... 212
Initials .................................................................................................................... 212
Alarm Acks ............................................................................................................. 212
Event Information and Alarm Summary ............................................................... 213
Unknown BACnet alarms ...................................................................................... 213
BACnet Text Messages .......................................................................................... 213
Alarm Priority ........................................................................................................ 214
Alarm Messages .................................................................................................... 214
APOGEE GO .............................................................................................................. 214
Attribute Duplicator ................................................................................................. 215
BACnet Export Map Entries Tool ............................................................................. 216
BACnet Communication Diagnostic ...................................................................... 216
BACNET Object Browser .......................................................................................... 218
BACnet Browser Features ..................................................................................... 219
BACnet Browser Limitations .................................................................................. 220
Commander ............................................................................................................. 220
Database Transfer .................................................................................................... 223
Progress Tab .......................................................................................................... 223
Log Tab .................................................................................................................. 224
Upload Selected Dialog ......................................................................................... 224
Object Types .......................................................................................................... 225
Backup and Restore ............................................................................................... 225
Dynamic Plotter ....................................................................................................... 226
Table of Contents
Siemens Industry, Inc. ix
Error Messages ........................................................................................................ 226
BACnet ALN Sorting Options ................................................................................. 226
BACnet Multiple Device Editing ............................................................................ 227
Other System profile BACnet Features ................................................................. 229
Event Builder ............................................................................................................ 229
Command Object ................................................................................................... 229
Event Printer ............................................................................................................ 232
Global Commander .................................................................................................. 232
Graphics ................................................................................................................... 232
Object Selector ........................................................................................................ 232
Cloaked Panels ...................................................................................................... 232
PXC Compact ......................................................................................................... 232
PXC Compact Support .............................................................................................. 232
Point Details ............................................................................................................. 233
Point Editor .............................................................................................................. 233
Engineering Units .................................................................................................. 233
BACnet Data .......................................................................................................... 234
BACnet FLN Device Points ..................................................................................... 234
Support for Deadband, Time Delay, Minimum On Time, and Minimum Off Time BACnet Properties ................................................................................................. 234
RENO Notification ................................................................................................. 235
PXC Compact Slope/Intercept ............................................................................... 235
Program Editor ......................................................................................................... 236
Report Builder/Reports ........................................................................................... 236
Display BACnet Priority ......................................................................................... 236
Reports ..................................................................................................................... 236
Application Log Report .......................................................................................... 236
Panel Configuration Report ................................................................................... 236
Panel Display Report ............................................................................................. 237
Panel Point Definition Report ............................................................................... 237
Panel Trend Data Detail Report ............................................................................ 237
Panel Trend Definition Report .............................................................................. 238
Point Definition Report ......................................................................................... 238
System Profile Report ............................................................................................ 238
Totalization Log Report ......................................................................................... 238
Table of Contents
x Siemens Industry, Inc.
Trend Collection Report ........................................................................................ 238
Trend Definition Report ........................................................................................ 238
Trend Data Detail Report ...................................................................................... 238
Trend Interval Report ............................................................................................ 239
Trend Sample Report............................................................................................. 239
Trend Summary Report ......................................................................................... 239
User Account Report ............................................................................................. 239
Scheduler ................................................................................................................. 240
Event Log .................................................................................................................. 240
System Profile .......................................................................................................... 240
BACnet MS/TP ALN Configuration......................................................................... 240
BACnet MS/TP FLN Configuration ......................................................................... 240
Logical Grouping of BACnet FLN Devices .............................................................. 241
BACnet FLN Device Definition Dialog Box ............................................................. 242
Application Initial Values ....................................................................................... 243
Command Priority Array Strings ............................................................................ 244
BACnet Address Table ........................................................................................... 245
ALN Definition ....................................................................................................... 246
Panel Definition ..................................................................................................... 250
FLN Devices ........................................................................................................... 260
Device Re-Initialization .......................................................................................... 261
Device Communication Control ............................................................................ 262
Who-Is Diagnostic Tool .......................................................................................... 263
Application Initial Values Dialog Box ..................................................................... 264
Time-of-Day Scheduling ........................................................................................... 264
Trend Editor ............................................................................................................. 264
Trend Definitions ................................................................................................... 264
Trend Definition Editor .......................................................................................... 264
User Accounts .......................................................................................................... 267
Command Priority ................................................................................................. 268
Insight Account Tab ............................................................................................... 269
ALN Account TAB ................................................................................................... 270
BACnet Export ....................................................................................................... 270
Chapter 9–BACnet Scheduling ................................................................................... 273
Table of Contents
Siemens Industry, Inc. xi
BIBBs Specifications for BACnet Scheduling .............................................................. 273
Overview of BACnet Scheduling ................................................................................. 273
Comparison to APOGEE ........................................................................................... 273
Scheduling Theory ...................................................................................................... 274
Setup DBCS for Scheduling Through Insight/Commissioning Tool ............................ 275
Step 1 ....................................................................................................................... 275
Step 2 ....................................................................................................................... 275
Step 3 ....................................................................................................................... 275
Step 4 ....................................................................................................................... 276
Step 5 ....................................................................................................................... 276
Step 6 ....................................................................................................................... 276
BACnet Calendars ....................................................................................................... 276
BACnet Time Setup .................................................................................................. 277
Creating a BACnet Calendar .................................................................................... 277
BACnet Calendar Properties Dialog Box ................................................................ 278
Calendar Properties Date List ................................................................................ 279
BACnet Object Commands ......................................................................................... 280
Creating Command Objects ..................................................................................... 280
BACnet Command Dialog Box ............................................................................... 280
BACnet Schedules ...................................................................................................... 281
Scheduling Point Objects ......................................................................................... 282
Insight Rules ............................................................................................................. 282
Creating BACnet Schedules Through Insight/Commissioning Tool ......................... 282
Advanced BACnet Schedule Properties................................................................. 284
Creating BACnet Schedules/Commands/Calendars Through the Field Panel Web Server ....................................................................................................................... 288
Schedule/Command/Calendar Object Editors Overview ...................................... 288
Using the Schedule/Command/Calendar Object Editors ...................................... 290
Command Objects ................................................................................................. 297
Calendar Objects ................................................................................................... 299
Event Scheduling ...................................................................................................... 300
Start Stop Time Optimization (SSTO) Implementation in PPCL ............................... 301
Insight Soft Controller APOGEE SSTO .................................................................... 301
BACnet Device Database Storage ............................................................................ 303
Schedule Object Properties that Can be Commanded ............................................ 304
Table of Contents
xii Siemens Industry, Inc.
Using BACnet Calendar Days in an APOGEE BACnet Field Panel .......................... 305
Accessing a Calendar Object with the BACnet Object Browser ............................ 306
BACnet Scheduling Examples ..................................................................................... 307
BACnet Scheduling Example 1 ................................................................................. 307
BACnet Scheduling Example 2 ................................................................................. 309
BACnet Scheduling Example 3 ................................................................................. 310
BACnet Scheduling Example 4 ................................................................................. 310
BACnet Scheduling Example 5 ................................................................................. 311
Chapter 10–BACnet Alarming .................................................................................... 313
BACnet Alarming Overview ........................................................................................ 313
Transitional States ................................................................................................... 314
BACnet and APOGEE Alarming ................................................................................... 314
Alarm Messages ....................................................................................................... 316
Token Messages .................................................................................................... 318
Notification Classes .................................................................................................. 319
Upper Section Configuration ................................................................................. 320
Lower Section Configuration ................................................................................. 322
Event Enrollment ..................................................................................................... 324
Event Enrollment Object Types ............................................................................. 324
Event Enrollment Creation .................................................................................... 325
Alarm Enable/Disable .............................................................................................. 327
Floating Alarm Limits ............................................................................................... 327
System Messages ..................................................................................................... 327
Initials ....................................................................................................................... 327
Alarm Acknowledgements ....................................................................................... 328
Get Event Information vs. Alarm Summary ............................................................. 328
Unknown BACnet Alarms ........................................................................................ 328
Life Safety Alarms .................................................................................................... 328
BACnet Text Messages ............................................................................................. 329
Alarm Priority ........................................................................................................... 329
Alarm Messages ....................................................................................................... 330
BACnet Browser ......................................................................................................... 330
Point Objects ............................................................................................................ 330
RENO Notification ...................................................................................................... 331
Table of Contents
Siemens Industry, Inc. xiii
APOGEE GO ................................................................................................................ 331
Setting Up BACnet Algorithmic Alarming ................................................................... 331
Point Editor Event Enrollment ................................................................................. 331
Event Enrollment Object Creating and Editing ........................................................ 336
Event Enrollment Object Alarm Messages .............................................................. 337
Alarm Messages ....................................................................................................... 339
Alarm Notification Classes ....................................................................................... 339
Recipient List ......................................................................................................... 339
Alarm Priority Colors ................................................................................................ 339
Setting Up BACnet Intrinsic Alarming ........................................................................ 340
Insight ...................................................................................................................... 340
Point Alarm Setup ................................................................................................. 340
Alarm Notification Classes and Messages ............................................................. 343
Alarm Priority Colors ............................................................................................. 348
BACnet Intrinsic Alarming Example ........................................................................... 348
L2SL Point ................................................................................................................. 349
LTD Point .................................................................................................................. 350
SAT Point .................................................................................................................. 351
SSP Point .................................................................................................................. 354
Notification Class ..................................................................................................... 355
Alarm Message Definition ..................................................................................... 356
Chapter 11–BACnet Trending .................................................................................... 359
BACnet Trending Theory ............................................................................................ 359
BACnet Trending in APOGEE ...................................................................................... 362
APOGEE Trending: Non-BACnet vs. BACnet ............................................................ 362
Support for Trend Log Objects in Other Devices ..................................................... 362
Dynamic Plotter ..................................................................................................... 363
Report Builder/Viewer .......................................................................................... 363
Trend Definition Editor .......................................................................................... 364
Scheduling Trends .................................................................................................... 366
Scheduling Trend Collections ................................................................................... 370
Setup Steps .............................................................................................................. 371
Notification Class ................................................................................................... 376
Chapter 12–BACnet Tools .......................................................................................... 383
Table of Contents
xiv Siemens Industry, Inc.
BAS-o-matic Protocol Analyzer .................................................................................. 383
Obtaining BAS-o-matic ............................................................................................. 383
Connecting to a Network ......................................................................................... 384
Connecting a Separate BAS-o-matic Computer .................................................... 384
Using the Insight Workstation for BAS-o-matic .................................................... 385
Installing BAS-o-matic v5.0 ...................................................................................... 385
Using BAS-o-matic on BACnet/IP ............................................................................. 386
Using BAS-o-matic for BACnet on Ethernet ............................................................. 389
Commissioning Tool Support for APOGEE BACnet Field Panels ................................ 390
Firmware Loading Tool ............................................................................................ 391
HMI Database Transfer ............................................................................................ 391
Build System Profile ............................................................................................... 391
Backup/Restore ..................................................................................................... 391
Terminal Emulation ............................................................................................... 391
Copy Field Panel ....................................................................................................... 392
Point Transfer .......................................................................................................... 392
Non-Field Panel Data Transfer ................................................................................. 392
Point Summary Report ............................................................................................ 393
Point Checkout Data ................................................................................................ 393
Commissioning Report Generator ........................................................................... 393
Insight BACnet Communications Tools ...................................................................... 394
Multiple Device Configuration ................................................................................. 394
Global Broadcast Who-Is ......................................................................................... 395
Custom Send Who-Is Diagnostic Tool ...................................................................... 395
Enable Device Discovery .......................................................................................... 395
BACnet Device Communication Control .................................................................. 396
BACnet Communication Diagnostic ......................................................................... 397
Chapter 13–BACnet Network Setup, Troubleshooting, and its Impact on IT .............. 401
Port Usage .................................................................................................................. 401
Insight Firewall Ports ............................................................................................... 401
Desigo CC Firewall Ports .......................................................................................... 404
BACnet Network Setup .............................................................................................. 405
BACnet/IP ALN ......................................................................................................... 405
Standard BACnet/IP Networks .............................................................................. 405
Table of Contents
Siemens Industry, Inc. xv
BBMD’s .................................................................................................................. 406
Foreign Device ....................................................................................................... 409
Setting or Modifying the Field Panel IP Configuration .......................................... 409
LocalNet Config Utility ............................................................................................. 413
BACnet MS/TP ALN .................................................................................................. 414
Rules for BACnet MS/TP ALN’s .............................................................................. 415
Adding a BACnet Field Panel as a MS/TP ALN Node ............................................. 415
Modifying BACnet Device Settings ........................................................................ 416
Modifying MS/TP ALN Settings ............................................................................. 417
BACnet MS/TP FLN ................................................................................................... 418
MS/TP FLN versus MS/TP ALN ............................................................................... 420
Adding a BACnet MS/TP PXC Compact 16/24 or UEC to a MS/TP FLN Network .. 420
Adding a BACnet TEC or a Third-party MS/TP Device to a BACnet Field Panel .... 423
Cimetrics MS/TP Router Set Up for Communication with BACnet TECs .............. 429
Troubleshooting the BACnet Network Using Wireshark ......................................... 438
Overview ............................................................................................................... 438
Installation ............................................................................................................. 438
Setting Up Wireshark Capture Software ............................................................... 439
Starting Wireshark ................................................................................................. 441
Starting and Stopping Wireshark Capture for an IP Network ............................... 442
Starting and Stopping Wireshark Capture for MS/TP Network Using MS/TPCAP 443
Saving Wireshark Capture ....................................................................................... 444
Display Filters ........................................................................................................... 445
Comparison Operators .......................................................................................... 446
Logical Operators .................................................................................................. 446
Common keywords – MAC address ...................................................................... 446
Common keywords – BACnet ................................................................................ 446
BACnet Object Type – Values ................................................................................ 447
BACnet Confirmed Service – Values ...................................................................... 447
BACnet Unconfirmed Service – Values ................................................................. 448
Building Filters ......................................................................................................... 448
Building Display Filter Expression .......................................................................... 448
Building Display Filter Packet Details Pane ........................................................... 448
Displaying Statistics ................................................................................................. 449
Table of Contents
xvi Siemens Industry, Inc.
Using Filter Expressions to Display COV Traffic ..................................................... 450
Using Filter Expressions to Display Alarms ............................................................ 452
Using Filter Expressions to Find Duplicate BBMD/Broadcast Storms ................... 452
Typical Bandwidth Usage ........................................................................................... 453
Chapter 14–System Cyber Security ............................................................................ 455
The Importance of Cyber Security ............................................................................. 455
Best Practices to Enhance Network Security ............................................................. 455
User Names and Passwords for Network Access .................................................... 455
User Accounts ........................................................................................................ 456
Passwords .............................................................................................................. 456
Avoid the Use of Internet Access to the APOGEE BAS Network ............................. 457
APOGEE BAS Network Security Features ................................................................... 457
Insight Network Security Features .......................................................................... 458
APOGEE Automation Field Panel Security Features ................................................ 459
APOGEE Network Security Best Practices ............................................................... 460
System Cyber Security Risk Assessment .................................................................... 461
Glossary .................................................................................................................... 465
Index ......................................................................................................................... 476
Siemens Industry, Inc. I
About this Application Guide This application guide is an update of the application guide titled BACnet Application Guide, which was last formally published in August 2007, although a draft update was developed in April 2010. Updates included in this version of the guide address the following:
• Major enhancements to the APOGEE field panel firmware.
• Major enhancements to the APOGEE software and hardware that have occurred since then; for example firmware revisions 3.1 – 3.2.4.
• Software support for algorithmic alarming and external trending.
• New BACnet supported hardware products such as PXCs, TECs, and PTECs.
• Network capacities, constraints and guidelines for device loading (regarding the number of devices, network performance variables, etc.).
• Optimal performance guidelines and settings have been added to this revision of the guide.
Chapter 12 includes typical questions and associated answers regarding the guidelines for BACnet/IP implementation and its impact on IT, and Chapter 13 discusses network security and provides guidelines for making networks more secure.
Finally, the section on Examples of Third-Party Equipment Integration in Chapter 3 of this guide present sinformation and examples of integrating APOGEE field panel devices with third-party equipment.
This section of the guide discusses the following topics:
• Purpose and intended audience 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.
About this Application Guide
II Siemens Industry, Inc.
Purpose and Intended Audience 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, the APOGEE BACnet Field Panels and Firmware revisions that support BACnet, and BACnet FLN devices. Therefore, the intended audience for this guide is primarily Design Engineers and Systems Specialists in the Siemens Building Technologies BAU field organization. This guide is intended to supplement all of the other APOGEE BACnet system documentation (APOGEE Insight online help, Getting Started, APOGEE BACnet ALN Field Panel User’s Manual, Networking Essentials for APOGEE, 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, Evolution of Siemens BACnet Products, 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.
• Chapter 6, BACnet FLN Devices, describes the hardware and software features of the Programmable TEC (PTEC) and its applications
• Chapter 7, Insight BACnet Option, describes the Insight BACnet Option and the changes to the Insight application since Revision 3.2
• Chapter 8, BACnet Scheduling, describes BACnet scheduling theory as it relates to scheduling in the APOGEE Building Automation System.
Table of Contents
Siemens Industry, Inc. III
• Chapter 9, 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 10, BACnet Trending, describes BACnet trending theory and trending in an APOGEE Building Automation System.
• Chapter 11, BACnet Tools, describes tools for analyzing BACnet communications in an APOGEE Building Automation System.
• Chapter 12, Q & A on BACnet/IP Implementation and its Impact on IT, describes…
• Chapter 13, Network Security, discusses network security and provides guidelines for making networks more secure.
• 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 135-2010 A Data Communication Protocol for Building Automation and Control Networks (BACnet) available for purchase at: www.ashrae.org. It is also posted on the following Siemens iShare drive; however, you must be a Siemens employee and be granted access to this drive: http://ishare.siemens.com/sii/bt/cps/rnd/sys/AppGuides/BACnetGuide/Shared Documents.
• BACnet Web site: www.BACnet.org
• BACnet International (BI) Web site: www.bacnetinternational.org
• 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
Provides additional information or helpful hints that need to be brought to the reader's attention.
About this Application Guide
IV Siemens Industry, Inc.
Notation Symbol Meaning
Tip
Suggests alternative methods or shortcuts that may not be obvious, but can help the user better understand the capabilities of the product.
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: [email protected]
Table of Contents
Siemens Industry, Inc. V
Siemens Industry, Inc. 7
Chapter 1–Overview of Siemens BACnet Products and Solutions
Chapter 1 describes a brief history of Siemens BACnet products and solutions and gives a brief overview of APOGEE BACnet solutions. This will give the reader an appreciation of the evolution of BACnet compliant products over the years and continuing commitment of Siemens to provide a full range of BACnet solutions to the marketplace.
Brief History of BACnet Implementation within APOGEE The goals of Siemens’ implementation of BACnet have always been:
• The support of ANSI/ASHRAE standard BACnet/IP throughout field panel and workstation architecture.
• Meeting BTL requirements for the field panel and the workstation.
• Meeting the global strategic BACnet requirements of Siemens Industry, Inc.
• Maintaining and enhancing the APOGEE Automation System features, functionality, performance, look and feel.
• Maintaining APOGEE Automation System backward compatibility.
• Maintaining the support for LonWorks Field Level Network (FLN), P1 FLN, Integration Drivers (currently on the PXC platform), Insight options, and InfoCenter.
This has been accomplished over time starting in February 2006 with the introduction of a BACnet MEC and MBC with Field Panel Firmware 3.0, and an enhanced Insight BACnet Client and Server Option (see Product Announcement-638: BACnet Field Panel Firmware Revision 3.0 and Insight Revision 3.7 BACnet Option), along with Navigator Support (Commissioning Tool/Design Tool) and appropriate training, documentation, and rollout. PA-638 introduced the following BACnet capabilities on the APOGEE BAS:
Table 1: BACnet Features and Capabilities Introduced with Insight 3.7.
Protocol Datalink
Communications Description Support by APOGEE
System?
BACnet over Ethernet BACnet over IEEE 8802-3 Ethernet Supported by Insight 3.7 BACnet Option
BACnet/IP BACnet over Internet Protocol on Supported by Insight 3.7 BACnet
Chapter 1–Overview of Siemens BACnet Products and Solutions
8 Siemens Industry, Inc.
Protocol Datalink
Communications Description Support by APOGEE
System?
Ethernet Option and Field Panel Firmware Revision 3.0
MS/TP Master Slave/Token Passing over EIA-485 network
Supported through APOGEE BACnet MS/TP Driver and third-party BACnet routers
PTP Point-to-Point over EIA-232 Supported through APOGEE Trane Driver and third-party BACnet routers
LonTalk BACnet over LonTalk Not supported in APOGEE system
ARCnet BACnet over ARCnet Supported through third-party BACnet routers only
Table 2 shows a timeline of the additional features have been added to the Siemens implementation of BACnet over the years. Hyperlinks to the Product Announcements or Sales Releases posted on InfoLink have been added under the Product Announcement or Sales Release Product Number column.
Table 2: Timeline of APOGEE Enhancements to Incorporate BACnet Features and Functions.
Date Product Announcement
or Sales Release
Document Number
Title Enhancement Description
Feb 2006 PA-638 BACnet Field Panel Firmware Revision 3.0 and Insight 3.7 BACnet Option
Introduced the BACnet Option for Insight. The Insight BACnet Option provides APOGEE with BACnet Ethernet and BACnet/IP Client and Server integration capabilities. The BACnet Client Option provides BACnet communication with both APOGEE and third-party BACnet devices and systems, enabling functionality such as:
• Monitoring and commanding BACnet Objects
• Establishing BACnet Schedules and Calendars
• Backing up databases in BACnet devices
• Receiving and acknowledging BACnet alarms
• Establishing and reading BACnet trend logs
Mar 2007
PA-638R2 BACnet Field Panel Firmware Revision 3.0 and Insight 3.7 (and
PA-638R2 is a revision to PA 638 and PA638R that includes the new BACnet MS/TP Driver and the PXC Compact Field Panel with Firmware Revision 3.0.
Brief History of BACnet Implementation within APOGEE
Siemens Industry, Inc. 9
Date Product Announcement
or Sales Release
Document Number
Title Enhancement Description
later) BACnet Option
Mar 2007
PA-651 TX-I/O Range TX-I/O technology is introduced.
Jun 2007 PA-668 PXC Modular Series PXC modular hardware platform introduced.
Jul 2007 PA-664 Insight Revision 3.8.1 The significant change to Insight® Revision 3.8.1 software is the support for the PXC MODULAR Field Panel.
Oct 2007 PA-669 MBC Pre-Retirement Notice
Announced that the MBC field panel will be officially retired on October 1, 2008.
Jul 2008 PS-700 BACnet Field Panels on Firmware Revision 3.1
MS/TP supported by Insight 3.9.1 BACnet Option through Field Panel Firmware Revision 3.1, and the BACnet MS/TP Driver on previous firmware revisions
Jul 2008 PA-702 Insight Revision 3.9.1 With this announcement of APOGEE Insight 3.9.1, along with Firmware Revision 3.1, the APOGEE Automation System is positioned for comprehensive BACnet support throughout the system architecture.
The PXC Modular must be used to bridge BACnet/IP ALN and BACnet MS/TP ALN. The PXC Modular must be used to support BACnet MS/TP ALN and configurable P1 or BACnet MS/TP FLN.
Aug 2008
PA-704 Retirement of Integration Drivers on Open Processors Platform
After September 30, 2008, the Open Processor and the Modular Building Controller (MBC) went into retirement. This included all Open Processor platform-based integration driver products. The PXC Modular product line with TX-I/O replaced the MBC.
Jun 2009 PA-725 Insight Revision 3.10 Supported BACnet Event Enrollment for the first time. The Event Enrollment allows the user to determine multiple alarm/event conditions and manage notification recipients for a device that otherwise cannot create an alarm/event message on its own, such as a BACnet TEC. The Event Enrollment can notify the user immediately or after a preset time delay in the event of the following conditions: change-of-state, command failure, floating range limit, and out-of-range. The Event Enrollment Object allows the user to monitor all aspects of their system.
Insight software now passed BTL testing requirements for BACnet Operator WorkStation (B-OWS) for the first time.
Sep 2009 PA-735 PXC Compact 36 The PXC Compact 36 is introduced.
Oct 2009 PA-736 BACnet Field Panels on Firmware Revision 3.2.
Provided support for the following features:
• Easily installed and hot swappable HOA module accessory for supporting all PXC Compact controllers including PXC-16, PXC-24, and PXC-36.
• PXC Compact 36 on BACnet/IP with BACnet MS/TP or P1
Chapter 1–Overview of Siemens BACnet Products and Solutions
10 Siemens Industry, Inc.
Date Product Announcement
or Sales Release
Document Number
Title Enhancement Description
FLN and TX I/O support. BACnet/IP to BACnet MS/TP router functionality at the ALN is supported.
• PXC Compact 16 and 24 on BACnet/IP. PXC Compact 16 and 24 on BACnet/IP includes support for one FLN configurable for BACnet MS/TP or one FLN for P1.
• PXC Compact 16 and 24 resides on BACnet MS/TP ALN or FLN.
• PXC Modular on BACnet/IP includes support for one FLN configurable for BACnet MS/TP or three FLN ports for P1. BACnet/IP to BACnet MS/TP router functionality at the ALN is supported.
• Power MEC and Power Open Processor with BACnet support the TX I/O modules on the MEC Expansion Bus or P1 FLN.
• Power Open Processor on BACnet/IP includes support for one FLN configurable for BACnet MS/TP or three FLN ports for P1.
Feb 2010 PA-747 SNMP Agent for BACnet Firmware 3.2
• The Simple Network Management Protocol (SNMP) is an application layer protocol that facilitates the exchange of management information between network devices. SNMP leverages the Transmission Control Protocol/Internet Protocol (TCP/IP) suite. SNMP enables network administrators to manage network performance, find and solve network problems and plan for network growth.
• The SNMP Agent is available as a licensable feature for the PXC Modular controller on Firmware Revision 3.2. The SNMP Agent reports information to the SNMP Network Management System (NMS also known as the SNMP Manager). The PXC Modular loaded with the SNMP Agent firmware and license acts as a data concentrator for SNMP messages and allows information from the APOGEE Automation System to be mapped into the PXC Modular controller and then exported using the SNMP protocol to an SNMP Manager or NMS. One PXC Modular controller acts as an SNMP Agent on behalf of a network of PXC controllers on the BACnet/IP network as well as managed BACnet MS/TP devices or P1 devices on the Field Level Network (FLN). Note that it is recommended to use one PXC Modular as an SNMP Agent device for each BACnet/IP Automation Level Network (ALN) trunk.
Sept 2010
POA-001 Modular Equipment Controller (MEC)
• Announces that effective October 1, 2010, the MEC product line will go into retirement. After this date, only
Brief History of BACnet Implementation within APOGEE
Siemens Industry, Inc. 11
Date Product Announcement
or Sales Release
Document Number
Title Enhancement Description
Product Line Retirement Plan
repair parts (Rparts) (which should be used only for replacement of failed units) will be available until October 1, 2017.
Oct 2010 SR-761 Insight Revision 3.11 • Condenses the existing BACnet Scheduler interface into a single dialog that is easier and quicker to use.
• BTL Certified as BACnet AWS (Advanced WorkStation)
Jan 2011 SR-773 APOGEE BACnet Scalable Solution
Key features and benefits include:
• PXC controller-based BACnet Web Server which provides a cost-effective Internet Web Browser user interface for any number of users, without the requirement for a dedicated computer and the Insight® software package with user licenses.
• Daily system operation monitoring, commanding, alarm management, scheduling and trending available remotely via Internet Web Browser through PXC-based Web Server on BACnet/IP.
• Cost effective, freely programmable Unitary Equipment Controller on BACnet MS/TP network, for flexibility to fit the controller to the equipment control needs.
• I/O modules on the BACnet MS/TP networks to cost effectively management remote I/O.
• BTL certified solutions to meet the customer needs for interoperability and to meet strict BACnet protocol implementation guidelines.
Jan 2011 SR-771 Field Panel Web Server The Field Panel Web Server provides a Web-based Graphical User Interface compatible with BACnet® networks that is hosted directly from APOGEE Field Panels. The Web Server allows remote access through an intuitive Web-based user interface to monitor, control, command and configure an APOGEE® building automation system.
Feb 2011 SR-770 BACnet MS/TP Point Pickup Modules
• The Siemens BACnet MS/TP Point Pickup Modules (PPM's) are expansion I/O devices that communicate on a BACnet MS/TP network, allowing for the incorporation of a cluster of remote points into the BAS.
• The PPM family leverages the RS-485 network to extend the reach of any BTL-listed BACnet Building Controllers features and application program.
• Each Universal Input can be configured for analog or digital input. Input/output type is configured by writing to BACnet object properties eliminating the need for a custom or proprietary tool.
• The PPM family is designed to make the Siemens BACnet
Chapter 1–Overview of Siemens BACnet Products and Solutions
12 Siemens Industry, Inc.
Date Product Announcement
or Sales Release
Document Number
Title Enhancement Description
system more scalable, flexible, adaptive, and cost effective.
May 2011
POA-006 Retirement of LON TECs and Room Units
• Retirement of LON TECs and Room Units effective October 1, 2011.
Dec 2011 SR-785 BACnet Field Panel Web Server Version 2 Update
The BACnet Field Panel Web Server provides a Web-based Graphical User Interface compatible with BACnet® networks that is hosted directly from APOGEE Field Panels. The Web Server allows remote access through an intuitive Web-based user interface to monitor, control, command and configure any Siemens building automation system. Version 2 extends the capabilities of the solution to include: • Email notification of alarm and event conditions for a
more extensive remote solution. • The industry’s most comprehensive native mobile app
solution, including remote access to system information via Android and BlackBerry mobile devices.(iOS version coming soon)
• Substantial BACnet MS/TP and UI database refresh performance improvements for an optimized user experience.
June 2012
SR-790 Insight 3.12 Insight 3.12 is BTL listed for BACnet AWS. BACnet Schedule Properties:
• The Exception schedules which indicate BACnet schedule overrides, now display in the BACnet Schedule Properties window. Now users can see in one screen the standard schedule with exceptions and easily determine when the Exception schedule will execute.
Event Enrollment Enhancements: • Event Enrollment window filers the supported
Event Types by APOGEE BACnet panels. July 2012 SR-789 DesigoTM CC Version 1 Desigo CC, a new management workstation, is introduced.
This workstation can replace the Insight APOGEE workstation on the Management Level Network (MLN) and also integrates fire safety systems and real-time video capabilities.
June 2013
SR-816 DesigoTM CC Version 1.1 Additional main features of Version 1.1 • Desigo CC OPC server option • System Management Console • MXL Line Card (MLC) support on XLS • Desigo S-Line and C-Line Detectors for • FireFinder XLS support • Support of multiple XLS/MXL networks, each with 63
Brief History of BACnet Implementation within APOGEE
Siemens Industry, Inc. 13
Date Product Announcement
or Sales Release
Document Number
Title Enhancement Description
notes, with a front end processor (FEP) • Integration of both Apogee BACnet panel networks
and Desigo Fire Safety panel networks with proper configuration
• UL approved use of non-UL PCs for fire system remote monitoring. Remote access from non UL PCs via fast VPN for monitoring only
Quality and performance enhancements in V1.1
• All V1.0 Service Releases and the LMU IT24 fix are included
• Only 13 V1.0 defects reported by technical support. All major defects fixed
• Faster graphic display using new AHU graphic symbols Aug 2013
SR-810 BACnet (MS/TP or IP) Driver
The BACnet MS/TP Driver has been updated to include new features and functions. This driver has been renamed the BACnet Driver.
• The BACnet Driver has been enhanced to communicate with BACnet/IP protocol in addition to MS/TP protocol which further extends its functionality and interoperability.
• Flexibility in point selection and point naming from BACnet/IP third-party devices.
• Use of the BACnet Driver in IP mode to improve system functionality by treamlining BACnet point lists in graphics, programs, alarms, reports, subpoint log and more.
• The Country of Origin (COO) for the BACnet Driver loaded on a PXC Compact 36 is USA.
• Desigo CC can be used with the BACnet Firmware Revision of this driver. However the BACnet driver license is not compatible on the same controller as the BACnet Field Panel Web Server License.
Chapter 1–Overview of Siemens BACnet Products and Solutions
14 Siemens Industry, Inc.
Architecture Overview of APOGEE BACnet System
Figure 1: Example of APOGEE BACnet Network.
BACnet Networks Overview
BACnet BLNs are typically set up using an Ethernet network physical structure. BACnet/IP is the preferred communication method for the MLN and ALN in a Siemens BACnet installation.
Siemens BACnet field panel firmware supports either a single MSTP FLN or standard P1 FLNs. Only one option is permitted per panel:
• MS/TP is the preferred method of communications for use on BACnet FLNs. This keeps the entire network “native”, or pure, BACnet.
• Siemens BACnet field panels can support BACnet/IP, MS/TP ALN, and MS/TP FLN all at the same time, but this is not recommended.
Siemens BACnet systems are not usually designed for MS/TP ALN support. MS/TP ALNs:
• Are occasionally used for integrating third-party BACnet devices.
• Can provide field panel connectivity if IP addresses for use with BACnet/IP are not available.
• Are created and connected to the system through a BACnet/IP field panel.
• Can have a maximum of 10 panels, including the panel connecting the ALN to the BACnet/IP network. Only one MS/TP ALN is permitted per BACnet/IP ALN.
Some Basic BACnet Terminology
Siemens Industry, Inc. 15
Panel Connections
BACnet ALN devices are wired using Ethernet network cables.
• Switches, routers, and other network hardware will be required.
• BACnet panels and RS-485 P2 or Ethernet panels cannot directly communicate. Shared points are accessible only with an Insight workstation computer “bridging” the different BLNs using the cross-trunk service.
Routers
Routers connect networks of different types, or multiple subnets. In general, routers:
• Routinely block global transmissions on a network, keeping traffic at a minimum and maintaining communication efficiency.
• Can connect networks with different architectures and protocols.
• Forward messages to the correct destination over the most efficient route.
• Must be configured for each individual network.
− Networks are defined as being on either side of the router.
A router that allows MS/TP device connection without a field panel is manufactured by Cimetrics (model B6000).
• Supports up to 50 MS/TP master devices (no slaves).
Network Numbering
BACnet allows network numbers ranging from 1 to 65535.
• Each network in a BACnet system is required to have a unique number in this range.
• Network numbers cannot be duplicated.
• The BACnet/IP network default is network number 1.
• It is normally left at the default value.
• Every MS/TP network must also have a unique network number.
• Siemens recommends thatMS/TP networks use the connecting panel's instance number as their network number.They will always be unique.
Some Basic BACnet Terminology The following are some basic BACnet terms used to describe BACnet networks. The Glossary at the back of this guide contains a much more extensive list and definition of BACnet terms.
Chapter 1–Overview of Siemens BACnet Products and Solutions
16 Siemens Industry, Inc.
BACnet/IP
BACnet messages can travel over networks that use the Internet Protocol (IP) by using BACnet/IP. With BACnet/IP, the BACnet device is an IP device (IP node), complete with its own IP address and IP protocol stack.
BACnet Client/Server
The terminology in BACnet systems differs from standard APOGEE.
• One computer (client) requests information from another computer (server).
• The request and the response are addressed directly from one computer to another computer.
User Datagram Protocol (UDP)
User Datagram Protocol is an alternative transport service to the Transmission Control Protocol (TCP).
Most internet messages are encapsulated in a TCP frame.
• TCP is a connection-oriented transport service that guarantees that the message reaches its destination.
• Since the BACnet protocol itself guarantees delivery, TCP is not required. BACnet uses UDP instead.
UDP is a connectionless transport layer protocol that exchanges datagrams (packetized data) without acknowledgments or guaranteed delivery.
• Datagrams are short messages. They might arrive out of order or go missing without notice.
• UDP manages how the sending computer disassembles a message into smaller packets. It then transmits the packets across the network to another computer.
Internet Protocol (IP)
The Internet Protocol handles the addressing of each packet that is sent.
• Ensures that the packets get to the proper destination.
• Acts as a sort of mail service on the network.
MS/TP Networks
Master-Slave/Token-Passing (MS/TP) uses a token to control access to a bus network.
• A master node can initiate the transmission of data when it holds the token.
Some Basic BACnet Terminology
Siemens Industry, Inc. 17
• Slave nodes may transmit data in response to requests from master nodes.
• In MS/TP systems with multiple masters, the token determines which master can initiate transmissions.
• Masters can answer requests from other Masters (peer-to-peer) as well as making requests for information from slaves.
APOGEE MS/TP slave nodes never hold the token. When a request that expects a reply is sent to an MS/TP slave node, the master waits for the reply to be returned before sending further communication.
• BACnet PTECs/BTECs are BACnet MS/TP network devices only.
• Each PTEC/BTEC must have a unique user defined MAC address (subpoint 1) and Device Object ID (instance number).
− Applies to every device on the MS/TP network (third-party, etc.).
• Early Edition BTECs supported baud rates up to 38400.
• PTECs and newer BTECs support baud rates up to 76800.
• Siemens recommends thatSiemens MS/TP FLNs use 38400 as their baud rate for best performance.
MS/TP Addressing The BACnet MSTP specification theoretically allows up to 255 devices on the MSTP network.
• A Siemens BACnet MSTP FLN is limited to a maximum of 50 devices.
• The PXC16 and PXC24 are limited to a maximum of 32 devices. The actual application of the BACnet MSTP addressing scheme is left up to the company implementing it in their particular devices. In a Siemens MSTP FLN device:
• MAC address (subpoint 1) range 0-127 can be used for slave or master designated devices.
• MAC address (subpoint 1) range 128-254 can be used for slave designated devices only.
• Siemens recommends thatmaster devices only use addresses in the 0-127 range, and slave devices only use addresses in the 128-254 range.
− This can prevent conflict with third-party devices that do not have the addressing flexibility that Siemens devices have.
Siemens Industry, Inc. 19
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 usually 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 by using 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.
Chapter 2–BACnet Objects and Services
20 Siemens Industry, Inc.
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 HMI (human-machine interface).
• 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. The Object_Identifier 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. The Object_Name 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.
Objects Theory
Siemens Industry, Inc. 21
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.
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 ANSI/ASHRAE Standard 135-2012, 50 standard object types have been established to contain much of the information that can be associated with a building automation system. Table 3 lists these object types in seven categories.
Table 3. Standard Object Types in ANSI/ASHRAE Standard 135-2012.
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
BitString Value Accumulator Integer Value
OctetString Value Large Analog Value CharacterString Value
Positive Integer Value DateTime Value Time Value
Time Pattern Value DateTime Pattern Date Value
Date Pattern Value
Event Reporting
Event Enrollment Event Log Notification Class
Scheduling/Logging
Schedule Calendar Trend Log
Trend Log Multiple
Control
Program Loop Averaging
Chapter 2–BACnet Objects and Services
22 Siemens Industry, Inc.
Access Door Pulse Converter Load Control
Life Safety
Life Safety Point Life Safety Zone
Grouping
Group Structured View Command
Authentification and Authorization
Access Point Access User Access Zone
Access Rights Credential Data Input Access Credential
Network Security
Device Level
Device File
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
Command Priority Properties
The Command Priority Array is a BACnet application-controlled prioritization mechanism 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 that may be set by the building automation system application.
Objects Theory
Siemens Industry, Inc. 23
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.
Figure 5. Example of the BACnet Command Priority Array Operation.
Chapter 2–BACnet Objects and Services
24 Siemens Industry, Inc.
BACnet Command Priority Array vs. Proprietary 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 4 shows the Command Priority Array, along with the default mapping to APOGEE priorities. If desired, any of the six default BACnet Priority Names 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 higher.
Table 4. BACnet Command Priority Array Mapped to APOGEE Priorities.
Slot BACnet Names Proprietary 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
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.1 As a result, the CFR-11 feature is not available in the BACnet field panel.
1 Title 21 CFR Part 11 of the Code of Federal Regulations deals with guidelines on electronic records and electronic signatures. Part
11, as it is commonly called, defines the criteria under which electronic records and electronic signatures are considered to be trusworkthy, reliable and equivalent to paper records.
Objects Theory
Siemens Industry, Inc. 25
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.
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).
Chapter 2–BACnet Objects and Services
26 Siemens Industry, Inc.
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).
Figure 9. BACnet Command Priority Array after Modification.
Objects Theory
Siemens Industry, Inc. 27
Operation
The BACnet priority array operation can cause different operation at times when compared to the proprietary APOGEE Automation System. The following scenario illustrates the change:
Proprietary 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 result is that the lights remain ON all night.
APOGEE BACnet Automation System:
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 APOGEE BACnet, unlike the proprietary 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 allows input commanding for virtual AI and DI points and restricts it for physical AI and DI 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.
Impact to HMI
The HMI must show which priority array entry is currently controlling the object. The HMI 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.
Chapter 2–BACnet Objects and Services
28 Siemens Industry, Inc.
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 4 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 the @ symbol. If no @ priority is defined, RELEASE will default to releasing level 16. Therefore, when using existing PPCL programs that use @Priority and Release, check if they have to be re-written to operate correctly.
When using the @<Priority> statements in BACnet field panels, only the top four APOGEE priorities (with their BACnet priority equivalents) can be used. For example, if Table 4 were the BACnet to APOGEE priority mapping for a field panel, then only OPERATOR, SMOKE, EMER and PDL can be used in the @<Priority> statements.
Objects Theory
Siemens Industry, Inc. 29
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 priority level 8 (Manual Operator).
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.
Chapter 2–BACnet Objects and Services
30 Siemens Industry, Inc.
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 5 shows the properties of the Device object along with information about how they interface to the APOGEE Automation System.
Table 5. BACnet Device Object Properties and How They Interface to APOGEE.
BACnet Property_Identifier
APOGEE Support
Read/Write Access
Notes
Object_Identifier Yes R Range is 0 to 4 MB. Configured in IP Settings.
Object_Name Yes R Field Panel Name, limited to 30 characters, Configured in IP Settings.
Object_Type Yes R Encoded name component “BACDev”
System_Status Yes R OPERATIONAL status used to set Ready status
Vendor_Name Yes R "Siemens BAU"
Vendor_Identifier Yes R All Siemens ISA devices = 7
Model_Name Yes R "Siemens BACnet EMEC"
Firmware_Revision Yes R Firmware Rev String that is, "BCE V3.0 APOGEE”
Application_Software_Version Yes R Firmware Rev String that is, "BCE3001”
Location Yes R Limited to 40 characters, Configured in IP Settings.
Description Yes R Limited to 40 characters, Configured in IP Settings.
Protocol_Version Yes R 1
Protocol_Revision Yes R 4
Protocol_Services_Supported Yes R See Table 15 for a listing of supported services.
Protocol_Object_Types _Supported
Yes R See the Object Summary table in Chapter 5–BACnet Field Panels.
Object_List Yes R List of object Ids for all points in this field panel.
Max_APDU_Length_Accepted Yes R 1497
Segmentation_Supported Yes R BACNET_SEGMENTATION_TYPE_BOTH
Max_Segments_Supported Yes R 32
VT_Classes_Supported No R
Active_VT_Sessions No R
Local_Time Yes R Field Panel Time
Local_Date Yes R Field Panel Date
UTC_Offset No R The number of minutes between the local time and
Objects Theory
Siemens Industry, Inc. 31
BACnet Property_Identifier
APOGEE Support
Read/Write Access
Notes
UTC2 time.
Daylight_Savings_Status Yes R
APDU_Segment_Timeout Yes R 3000
APDU_Timeout Yes R 3000
Number_Of_APDU_Retries Yes R 3
List_Of_Session_Keys No R
Time_Sync_Recipients No R
Max_Master No R
Max_Info_Frames No R
Device_Address_Binding Yes R
Database_Revision Yes R 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 R List of files to be backed up. Valid only during the backup procedure.
Last_Restore_Time Yes R Time of last file download. Applies only to BACnet file transfer services.
Backup_Failure_Timeout Yes W How long to wait before aborting a backup or restore operation.
Active_COV_Subscriptions Yes R A list of active subscriptions. Applies to the server side.
Slave_Proxy_Table No R
Manual_Slave_Address_Binding No R
Auto_Slave_Discovery No R
Slave_Address_Binding No R
Profile_Name No R
Point-Like Objects
Table 3 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.
2 (Wikipedia definition): Coordinated Universal Time (UTC) is the primary time standard by which the world regulates clocks and
time. It is one of several closely related successors to Greenwich Mean Time (GMT).
Chapter 2–BACnet Objects and Services
32 Siemens Industry, Inc.
Analog Input Object
The Analog Input Object is a representation of a physical analog input point in the BACnet device. Table 6 shows the properties of the Analog Input object along with information about how they interface to the APOGEE Automation System.
Table 6. BACnet Analog Input Object Properties and How They Interface to APOGEE.
BACnet Property_Identifier
APOGEE 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 W REAL
Description Yes W Limited to 16 characters.
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 W Must be set to override Present_Value.
Update_Interval No
Units Yes W Uses BACnet enumeration corresponding to fixed engineering units strings.
Min_Pres_Value No
Max_Pres_Value No
Resolution Yes Slope
COV_Increment Yes W COV Limit
Time_Delay Alarm Configurable
Objects Theory
Siemens Industry, Inc. 33
BACnet Property_Identifier
APOGEE Support
Access Notes
Notification Class Alarm W
High_Limit Alarm W High Limit
Low_Limit Alarm W Low Limit
Deadband Alarm Configurable
Limit_Enable Alarm If alarming enabled, then low_limit and high_limit both enabled.
Event_Enable Alarm W 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.
Analog Output Object
The Analog Output Object is a representation of a physical analog output point in the BACnet device. Table 7 shows the properties of the Analog Output object along with information about how they interface to the APOGEE Automation System.
Table 7. BACnet Analog Output Object Properties and How They Interface to APOGEE.
BACnet Property_Identifier
APOGEE 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 W REAL
Description Yes W 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.
Chapter 2–BACnet Objects and Services
34 Siemens Industry, Inc.
BACnet Property_Identifier
APOGEE Support
Access Notes
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 No
Max_Pres_Value 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 W COV Limit
Time_Delay Alarm Configurable
Notification Class Alarm W
High_Limit Alarm W High Limit
Low_Limit Alarm W Low Limit
Deadband Alarm Configurable
Limit_Enable Alarm If alarming enabled, then low_limit and high_limit both enabled.
Event_Enable Alarm W 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.
Objects Theory
Siemens Industry, Inc. 35
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 8 shows the properties of the Analog Value object along with information about how they interface to the APOGEE Automation System.
Table 8. BACnet Analog Value Object Properties and How They Interface to APOGEE.
BACnet Property_Identifier
APOGEE 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 W REAL
Description Yes W 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 W COV Limit
Time_Delay Alarm Configurable
Notification Class Alarm W
High_Limit Alarm W High Limit
Low_Limit Alarm W Low Limit
Deadband Alarm Configurable
Limit_Enable Alarm If alarming enabled, then low_limit and high_limit both enabled.
Event_Enable Alarm W If alarming enabled, then to-offnormal, to-fault, and to-normal all set to TRUE.
Chapter 2–BACnet Objects and Services
36 Siemens Industry, Inc.
BACnet Property_Identifier
APOGEE 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. 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 9 shows the properties of the Binary Input object along with information about how they interface to the APOGEE Automation System.
Table 9. BACnet Binary Input Object Properties and How They Interface to APOGE.
BACnet Property_Identifier
APOGEE 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 W Binary Value
Description Yes W 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 W Must be set in order to override the Present_Value.
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.
Objects Theory
Siemens Industry, Inc. 37
BACnet Property_Identifier
APOGEE Support
Access Notes
Change_Of_State_Time No
Change_Of_State_Count No
Time_Of_ State_Count_Reset
No
Elapsed_Active_Time Yes W Totalization
Time_Of_ Active_Time_Reset
Yes Totalization_Reset_Time
Time_Delay Alarm Configurable
Notification Class Alarm W
Alarm_Value Alarm Specifies what the Present_Value is when the point is in Alarm.
Event_Enable Alarm W 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 10 shows the properties of the Binary Output object along with information about how they interface to the APOGEE Automation System.
Table 10. BACnet Binary Output Object Properties and How They Interface to APOGEE.
BACnet Property_Identifier
APOGEE 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 W Binary Value
Chapter 2–BACnet Objects and Services
38 Siemens Industry, Inc.
BACnet Property_Identifier
APOGEE Support
Access Notes
Description Yes W 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.
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 No
Change_Of_State_Count No
Time_Of_ State_Count_Reset
No
Elapsed_Active_Time Yes W Totalization
Time_Of_ Active_Time_Reset
Yes Totalization_Reset_Time
Minimum_Off_time No
Minimum_On_time No
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 W
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 W 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.
Objects Theory
Siemens Industry, Inc. 39
BACnet Property_Identifier
APOGEE Support
Access Notes
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.
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 11 shows the properties of the Binary Value object along with information about how they interface to the APOGEE Automation System.
Table 11. BACnet Binary Value Object Properties and How They Interface to APOGEE.
BACnet Property_Identifier
APOGEE 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 W Binary Value
Description Yes W 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 No
Change_Of_State_Count No
Time_Of_ State_Count_Reset
No
Chapter 2–BACnet Objects and Services
40 Siemens Industry, Inc.
BACnet Property_Identifier
APOGEE Support
Access Notes
Elapsed_Active_Time Yes W Totalization
Time_Of_ Active_Time_Reset
Yes Totalization_Reset_Time
Minimum_Off_time No
Minimum_On_time No
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 W
Alarm_Value Alarm Specifies what the Present_Value is when the point is in Alarm.
Event_Enable Alarm W 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.
A number of Binary Value object properties have a conformance code of O (optional). Those with footnote number 6 relate to intrinsic reporting, which is one of several methodologies used for alarming. The Siemens field panels support intrinsic reporting and therefore have all of the O6 properties in all of their Binary point-like objects. See Chapter 8-BACnet Alarming for more details.
Multi-state Input Object
The Multi-state Input Object has no analogy in the APOGEE BACnet field panel and is not supported.
Objects Theory
Siemens Industry, Inc. 41
Multi-state Output Object
The Multi-state Output Object is a representation of a physical Multi-state output point in the BACnet device. This point supports L2SL, L2SP, LOOAL, LOOAP, LFSSL, and LFSSP points in APOGEE field panels. Table 12 shows the properties of the Multi-State Output object along with information about how they interface to the APOGEE Automation System.
Table 12. BACnet Multi-state Output Object Properties and How They Interface to APOGEE.
BACnet Property_Identifier
APOGEE 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 “MO”.
Present_Value Yes W Unsigned
Description Yes W 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 W
Number_Of_States Yes Correspond to size of State Text Table.
State_Text Yes Corresponds with State Text Table.
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 W
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 W 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.
Chapter 2–BACnet Objects and Services
42 Siemens Industry, Inc.
BACnet Property_Identifier
APOGEE Support
Access Notes
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 has a Conformance Code of W meaning that it is always writeable.
Multi-state Value Object
The Multi-state Value Object is a representation of a virtual Multi-state output point or a software parameter in the BACnet device. This point is the equivalent of the LENUM point in the APOGEE field panel. Table 13 shows the properties of the Multi-state Value object along with information about how they interface to the APOGEE Automation System.
Table 13. BACnet Multi-state Value Object Properties and How They Interface to APOGEE.
BACnet Property_Identifier
APOGEE 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 “MV”.
Present_Value Yes W Unsigned
Description Yes W 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 W
Number_Of_States Yes Correspond to size of State Text Table.
State_Text Yes Corresponds with State Text Table.
Priority_Array Yes For commanding the present value.
Objects Theory
Siemens Industry, Inc. 43
BACnet Property_Identifier
APOGEE Support
Access Notes
Relinquish_default Yes For releasing the Present_Value when the Priority Array is empty.
Time_Delay Alarm Configurable
Notification Class Alarm W
Alarm_Values Alarm
Fault_Values Alarm
Event_Enable Alarm W
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.
Other Objects Supported by APOGEE BACnet Field Panels
Other BACnet objects that are supported by APOGEE BACnet Field Panels are:
• Calendar Object
• Command Object
• File Object
• Notification Class Object
• Schedule Object
• Trend Log Object (Internal and External)
Calendar Object
See Chapter 7-BACnet Scheduling for details.
Command Object
See Chapter 7-BACnet Scheduling for details.
Chapter 2–BACnet Objects and Services
44 Siemens Industry, Inc.
File Object
This object is involved with the database uploads and downloads of an APOGEE field panel. Table 14 shows the properties of the File object along with information about how they interface to the APOGEE Automation System.
Table 14. BACnet File Object Properties and How They Interface to APOGEE.
BACnet Property_Identifier
APOGEE 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 “FI”.
Description Yes Limited to 16 characters.
File_Type Yes
File_Size Yes W
Modification_Date Yes
Archive Yes W
Read_only Yes
File_Access_Method Yes
Record_Count No
Profile_Name No
Notification Class Object
See Chapter 8-BACnet Alarming for details.
Schedule Object
See Chapter 7-BACnet Scheduling for details.
Trend Log Object
See Chapter 9-BACnet Trending for details.
Viewing with the BACnet Browser
BACnet objects and their properties can be viewed using the BACnet Object Browser. The Object Browser is accessed from the Tools menu in System Profile. An Automation Level Network (ALN, formerly called “Building Level Network,” or “BLN”) must first be chosen to un-gray the BACnet Object Browser.
Objects Theory
Siemens Industry, Inc. 45
Figure 12. Accessing the BACnet Object Browser.
Then the navigation pane in the browser can be used to choose the desired BACnet device (field panel). Choosing a BACnet device will cause its objects to display in the navigation panel and the properties of that device to display on the right side of the screen (assuming you select View Device Properties from the View selection). See Figure 13.
Chapter 2–BACnet Objects and Services
46 Siemens Industry, Inc.
Figure 13. BACnet Object Browser Screen.
Services Theory
This section is included to provide a greater understanding of how BACnet operates. Most of the operation of BACnet services is behind the scenes and not visible to the user.
BACnet services are actions that a BACnet device takes to share data with another BACnet device. Services are the means by which one BACnet device acquires information from another device, commands another device to perform some actions, or announces to one or more devices that some event has taken place.
BACnet is based on a Client-Server communications model, and these messages are carried out by the server at the request of the client. Therefore, BACnet messages are service requests. A client computer sends a service request to a server computer that then performs the service and reports the result back to the client. Each service request issued and service acknowledgment (reply) returned becomes a message packet transferred over the network from the sending to the receiving device.
The BACnet message-passing and object access services are divided into five groups or classes of Application Services:
• Object Access Services–Provide the means to read, modify and write properties, as well as add and delete objects.
Services Theory
Siemens Industry, Inc. 47
• Alarm and Event Services–Deal with changes in conditions seen by a BACnet device such as problems, error conditions, sensors reading out of normal range or alarms returning to normal operation. Also included are Changes-Of-Values or COVs.
• File Access Services–Used to read and manipulate files in BACnet devices. In BACnet, files represent groups of data of arbitrary length and meaning; they do not necessarily relate to any kind of mass storage device. Every BACnet-accessible file has a File Object associated with it.
• Remote Device Management Services–Provide a number of assorted functions, including operator control, specialized message transfer, addressing/auto-configuring functions, discovery of devices and objects, device control, time synchronization file access, reading, and writing.
• Virtual Terminal Services–Used by an operator to establish a bi-directional text-based connection with an application program executing in a remote device. In effect, for the duration of a VT session established with the remote device, the operator's device looks like a terminal connected to the remote application program.
Service requests are issued or processed by application program software running on the BACnet device. In the case of an operator workstation, the software might maintain a display of several sensor inputs and would periodically issue service requests to the appropriate objects in the target devices to obtain the latest values of the inputs. In the monitored device, the service request would be processed in its application program and the reply containing the requested data would be returned (Figure 14).
Figure 14. Example Service Request and Reply.
Services are categorized as Confirmed in which a reply, typically with data, is expected, or Unconfirmed in which no reply is expected. BACnet devices are not required to implement every single Service. Just one Service, ReadProperty, is required to be processed by all BACnet devices. Depending upon the function and complexity of the device, additional Services may be initiated or executed.
Chapter 2–BACnet Objects and Services
48 Siemens Industry, Inc.
Services Supported
The APOGEE BACnet solution only supports the services listed in Table 15.
Table 15. Services Supported by the APOGEE BACnet Solution.
Service Name
ACKNOWLEDGE_ALARM
ADD_LIST_ELEMENT
ATOMIC_READ_FILE
ATOMIC_WRITE_FILE
CONFIRMED_COV_NOTIFICATION
CONFIRMED_EVENT_NOTIFICATION
CONFIRMED_PRIVATE_TRANSFER
CONFIRMED_TEXT_MESSAGE
CREATE_OBJECT
DELETE_OBJECT
DEVICE_COMMUNICATION_CONTROL
GET_ALARM_SUMMARY
GET_ENROLLMENT_SUMMARY
GET_EVENT_INFORMATION
I_AM
I_HAVE
READ_PROPERTY
READ_PROPERTY_MULTIPLE
READ_RANGE
REINITIALIZE_DEVICE
REMOVE_LIST_ELEMENT
SUBSCRIBE_COV
TIME_SYNCHRONIZATION
UNCONFIRMED_COV_NOTIFICATION
UNCONFIRMED_EVENT_NOTIFICATION
UNCONFIRMED_TEXT_MESSAGE
WHO_HAS
WHO_IS
WRITE_PROPERTY
WRITE_PROPERTY_MULTIPLE
Services Theory
Siemens Industry, Inc. 49
Services Not Supported
The APOGEE BACnet solution does not support the services listed in Table 16.
Table 16. Services Not Support by the APOGEE BACnet Solution.
Service Name
AUTHENTICATE
LIFE_SAFETY_OPERATION
READ_PROPERTY_CONDITIONAL
REQUEST_KEY
SUBSCRIBE_COV_PROPERTY
UNCONFIRMED_PRIVATE_TRANSFER
UTC_TIME_SYNCHRONIZATION
VT_CLOSE
VT_DATA
VT_OPEN
Siemens Industry, Inc. 51
Chapter 3–BACnet Interoperability Chapter 3 describes the ability of APOGEE BACnet devices to integrate with BACnet products made by different manufacturers into a single system. It includes the following topics:
• Interoperability
• Certification
• BACnet Device Profiles
• APOGEE BACnet Field Panel Interoperability
• Insight Interoperability
• Information and examples on third-party equipment integration with APOGEE BACnet devices
Interoperability BACnet Interoperability is the ability to integrate BACnet products made by different manufacturers into a single system. Interoperability does not mean that installations must have multiple vendors, just that the site can have multiple BACnet vendors if desired. Many automation system users prefer the benefits of dealing with a single vendor, and a system using the BACnet protocol in no way prevents this.
Note that Interoperability is not plug-and-play. You still have to make choices about what functionality is needed. Also, BACnet interoperability does not address:
• Configuration
• Programming (programming language)
• User interface (look and feel)
Some obstacles to interoperability are:
• Many properties are optional.
• Manufacturers may interpret the specification differently and make different design assumptions.
• Differing character sets are used around the world.
Chapter 3–BACnet Interoperability
52 Siemens Industry, Inc.
Certification BACnet is a registered trademark of ASHRAE. ASHRAE does not endorse, approve, or test products for BACnet compliance. That is the responsibility of BACnet International (formerly the BACnet Manufacturers Association and the BACnet Interest Group - North America). To test manufacturers’ BACnet devices for interoperability and certify the results, BACnet International (BI) established the BACnet Testing Laboratories (BTL). The BTL logo is a trademark of BI. Products that have been successfully tested by the BTL are eligible to display the BTL logo as part of the listing process.
The main functions of the BTL are to:
• Sponsor an annual BACnet Interoperability Workshop.
• Develop testing procedures and rules to certify that BACnet devices conform to the BACnet standard so that the devices may carry the BTL certification mark (Figure 15).
Figure 15. BACnet Testing Laboratories Certification Mark.
The APOGEE BACnet Field Panels are BACnet Testing Laboratories (BTL) certified and listed BACnet Building Controllers (B-BC). They carry the BTL certification mark and can meet specifications calling for native BACnet field panels. They provide interoperability with third-party BACnet workstations.
Starting with Insight Revision 3.7 this version of Insight workstation with the BACnet Option can be considered a native BACnet workstation. It has been developed to conform to the BACnet Operator Workstation (B-OWS) test specification. The BACnet Testing Laboratories has since added the “B-AWS” designation, which stands for “BACnet Advanced Workstation.” As of Insight Revision 3.11, Insight is B-AWS approved.
Certification
Siemens Industry, Inc. 53
Specifying BACnet
Specifying BACnet is challenging because the protocol purposely defines more functionality than any particular device will likely implement, and devices can vary greatly in their implementation of BACnet and BACnet functionality. A document called a Protocol Implementation and Conformance Statement (PICS) was devised to disclose BACnet information such that vendors, customers, and consulting engineers can understand the functionality implemented in a given device. From this information they can determine realistic expectations for interoperability between any given BACnet devices.
The original format of the PICS contained information about the device’s conformance class and support for functional groups. This format created some confusion among its intended users and in 2001 it was replaced by a new approach called BACnet Interoperability Building Blocks (BIBBs) that describes the device’s interoperability capabilities. BACnet Interoperability Building Blocks (BIBBs) are defined in part of PICS. BIBBs are sets and groupings of functionality that can be easily mapped from device-to-device, to determine the functionality that is likely interoperable between devices. Both of these formats (PICS and BIBBs) are still used today.
Protocol Implementation and Conformance Statement
The Protocol Implementation and Conformance Statement (PICS) is a BACnet specification sheet containing a list of a device's BACnet capabilities. Written in a standard format specified by ASHRAE, the PICS contains a general product description, a product's BACnet capabilities, available LAN options, and other items relating to character sets and special functionality.
Every BACnet device must have a PICS.
Consulting engineers, vendors, and customers can use a PICS to determine what capabilities a BACnet device might have. The PICS may be used to determine what functionality devices are capable of supporting and what functionality is interoperable with other devices.
The PICS provides the following information about a BACnet device:
• Product name, version, and description
• Device profile (Standard 135-2012, Annex L) to which the device conforms:
− B-AWS (BACnet Advanced Workstation)
− B-OWS (BACnet Operator Workstation)
− B-BC (BACnet Building Controller)
Chapter 3–BACnet Interoperability
54 Siemens Industry, Inc.
− B-AAC (BACnet Advanced Application Controller)
− B-ASC (BACnet Application Specific Controller)
− B-SS (BACnet Smart Sensor)
− B-SA (BACnet Smart Actuator)
• BIBBs supported by the device:
− Data Sharing
− Scheduling
− Trending (includes Viewing and Modifying Trends External-B)
− Network Management
− Alarm and Event
− Device Management
• Segmentation support and window size
• Standard object types supported, plus an indication of objects that can be created and deleted by a third-party BACnet system/device:
− Analog Input, Output, Value
− Averaging
− Binary Input, Output, Value
− Calendar
− Command
− Device
− Event Enrollment
− File
− Group
− Life Safety Point, Zone
− Loop
− Multi-State Input, Output, Value
− Notification Class
− Program
− Schedule
− Trend Log
− Proprietary
• Datalink and physical network layers support:
− BACnet/IP (Standard 135-2012, Annex J)
Certification
Siemens Industry, Inc. 55
− BACnet Ethernet (10Base-2, 10Base-5, 10Base-T, Fiber)
− BACnet ARCnet
− BACnet MS/TP (EIA-485 Master-Slave/Token Passing)
− BACnet Point-To-Point (EIA-232)
− BACnet LonTalk
• Device address binding support
• Networking datalink options support:
− Router
− BACnet Tunneling (Standard 135-2012, Annex H)
− BACnet/IP BBMD (BACnet Broadcast Management Device) (Standard 135-2012, Annex J)
− BACnet/IP Foreign Device
• Character sets support:
− ANSI X3.4
− ISO 10646 (ICS-4)
− IBM/Microsoft DBCS
− ISO 10646 (UCS2)
− JIS C 6226
− ISO 8859-1
BACnet Interoperable Building Blocks
BACnet Interoperable Building Blocks (BIBBs) are meaningful units of functionality of a BACnet device. The BIBBs of one BACnet device can be compared to the same BIBBs of another device to determine what functionality is likely to interoperate between the devices.
BIBBS descriptions are abbreviated as shown in the examples in Table 17.
Table 17. Data Sharing BIBBs Abbreviation Examples.
Description Client BIBBS (initiate) Server BIBBs (execute)
Data Sharing, Read Property DS-RP-A DS-RP-B
Data Sharing, Read Property, Multiple
DS-RPM-A DS-RPM-B
Data Sharing, Read Property, Conditional
DS-RPC-A DS-RPC-B
Data Sharing, Write Property DS-WP-A DS-WP-B
Data Sharing, Write Property, DS-WPM-A DS-WPM-B
Chapter 3–BACnet Interoperability
56 Siemens Industry, Inc.
Multiple
Each BIBB abbreviation ends with an “A” or “B” to denote its prescribed functional support. Definitions of “A” and “B” support are as follows:
• A: User of data as a client–initiate function
• B: Provider of data as a server–execute function
Achieving interoperability between two or more BACnet devices requires support in the device acting as the requester of data for the A type functionality, and support in the provider of the data for the B type of functionality. All devices expected to be interoperable must support the function required (BIBB) and the Initiate or Execute side of the functionality, depending on the role of the device (Figure 16).
Figure 16. BIBB Client and Server Interaction for Interoperability.
Figure 17 is an example Trending BIBB. Device B could be a BACnet field panel and device A could be workstation that archives the trended data.
Figure 17. Sample BIBB for Trending.
Certification
Siemens Industry, Inc. 57
BIBBs interoperable functionality can be grouped into six categories or interoperability areas (IA):
• Data Sharing
• Scheduling
• Trending
• Network Management
• Device Management
• Alarm and Event Management
Data Sharing
The Data Sharing IA defines monitoring and commanding of property values, COV subscriptions, and object configuration. This functionality is similar to APOGEE logical point operations:
• Read/write property
• Read/write multiple properties
• Read property conditional
• COV (Change-of-Value)
• Unsolicited COV
Scheduling
The Scheduling IA defines objects for calendars and scheduled commands for predefined lists of object properties:
• Scheduling–internal
• Scheduling–external
Trending
The Trending IA defines functionality for configuring trends and transferring trend data over the network:
• Viewing and modifying trends–internal
• Viewing and modifying trends–external
• Automated trend retrieval
Network Management
Network management defines functionality for determining which devices are present on a given network:
Chapter 3–BACnet Interoperability
58 Siemens Industry, Inc.
• Device connection establishment
• Router configuration
Device Management
Device management defines functionality of some of the operational capabilities of a device, including:
• Backup and restore device database
• Device binding–discovery and connection
• Device communication control
• List manipulation
• Object binding–discovery and connection
• Object creation and deletion
• Private transfer of message
• Reinitialize device communications
• Text message
• Time synchronization
• UTC time synchronization
• Virtual terminal
Alarm and Event Management
Alarm and Event Management defines functionality including:
• Annunciation and acknowledgment of alarms
• Display of data indicating the basis for the alarm annunciation
• Sharing of events for the purpose of logging or distributed control applications
• Modification of alarm limits and routing
• Production of summaries of the occurrence of such alarms and events.
BACnet supports two mechanisms for the generation of alarms and events:
• Intrinsic Reporting–this relies on using properties that are part of, or "intrinsic" to, the object that is being monitored for alarms or events.
• Algorithmic Change Reporting–this method is more general, but it also requires the overhead of an additional object called the Event Enrollment object. The intrinsic reporting method is preferred under circumstances where it meets the objectives of the intended application.
− Alarm and event notification–internal
BACnet Device Profiles
Siemens Industry, Inc. 59
− Alarm and event notification–external
− Alarm acknowledgement
− Alarm and event summary
− Alarm enrollment summary
− Alarm information
− Life safety alarm
BACnet Device Profiles BACnet Device Profiles indicate which BIBBs must be supported for each of a number of device types. Thus the profiles provide guidelines for interoperability. The device types include:
• B-AWS (Advanced Workstations), the target profile for APOGEE Insight and Desigo CC
• B-OWS (Operator Workstations), the previous target profile for APOGEE Insight, prior to Revision 3.11.
• B-BC (Building Controllers), the target profile for the APOGEE BACnet field panels (PXC Compact, PXC Modular, and retired Open Processor and MEC)
• B-AAC (Advanced Application Controllers) the target profile for the APOGEE PXC Compact UEC
• B-ASC (Application Specific Controllers), the target profile for the BACnet TEC
• BACnet Smart Sensor (B-SS)
• BACnet Smart Actuator (B-SA)
Figure 18 shows the functional relationship and hierarchy of the device types in a building automation system. Included are the APOGEE Automation System devices.
Chapter 3–BACnet Interoperability
60 Siemens Industry, Inc.
Figure 18. Functional Relationship of BACnet Devices for Device Profiles.
BACnet Building Controller Profile (B-BC), Advanced Application Controller Profile (B-AAC), and Advanced Workstation Profile (B-AWS)
The B-BC and B-AWS profiles specify functionality in each of the interoperability areas that the BACnet committee deemed appropriate for field-panel class devices and workstations, respectively. However, the profiles are vague targets, specifying functionality at a high level and leaving many items optional or open to interpretation. The BACnet Test Labs (BTL), on the other hand, specifies a series of conformance tests and provides an automated testing framework that usually reduces ambiguity and improves chances for interoperability but also reduces a vendor’s opportunities for creativity.
Each device sent to the BTL must be accompanied by an Electronic Protocol Implementation Conformance Statement (EPICS), which specifies the Objects and Services supported by the device.
The BTL will use the EPICS to tailor the test suite to the specific implementation.
ASC
AWS
BC BC BC
BACnet Advanced Workstation
BACnet Building Controller (B-BC) – PXC16, PXC24, PXC36, Climatix, Desigo PX Compact, D i PX M d l ASC
ASC
S A
BACnet Application Specific Controller (B-ASC) – Desigo PXC3 BACnet
BACnet Smart Sensor/Actuator
BACnet Device Profiles
Siemens Industry, Inc. 61
BACnet Building Controller (B-BC) Profile
A BACnet Building Controller (B-BC) is a general-purpose, field-programmable device capable of carrying out a variety of building automation and control tasks. Profiles are specified in terms of BIBBs3, which are small pieces of functionality (Table 18).
Table 18. Required BIBBs for B-BC Profile.
B-BC Profile Supported BIBBs
Description
Data Sharing DS-RP-A,B
DS-RPM-A,B
DS-WP-A,B
DS-WPM-B
Read Property, A and B
Read Property Multiple, A and B
Write Property, A and B
Write Property Multiple, B
Alarm and Event Management AE-N-I-B
AE-ACK-B
AE-INFO-B
AE-ESUM-B
Alarm and Event Notification, Internal, B
Alarm and Event Acknowledgement, B
Alarm and Event Information, B
Alarm and Event Enrollment Summary, B
Scheduling SCHED-E-B Scheduling External, B
Trending T-VTM-I-B Trending, Viewing and Modifying Trends, Internal, B
T-ATR-B Trending, Automated Trend Retrieval, B
Device and Network Management DM-DDB-A,B Device Management, Dynamic Device Binding, A and B
DM-DOB-B Device Management, Dynamic Object Binding, B
DM-DCC-B Device Management, Device Communication Control, B
DM-TS-B or DM-UTC-B
Device Management Time Synchronization, B or Device Management UTC Time Synchronization, B
DM-RD-B Device Management Reinitialization Device, B
DM-BR-B Device Management Backup and Restore, B
BACnet Advanced Application Controller (B-AAC) Profile
A BACnet Advanced Application Controller (B-AAC) is a native BACnet, fully programmable controller designed for general purpose applications. This controller can be used in stand-alone environments or networked to other BACnet devices. As part of a complete facilities management system, a B-AAC controller provides precise monitoring and control of connected points (Table 19).
3 In the Jargon of BIBBs, an “A” device is one who used the data (client) while the “B” device is the one who provides the data
(server).
Chapter 3–BACnet Interoperability
62 Siemens Industry, Inc.
The Siemens PXC Compact Unitary Equipment Controllers (PXC16.3-UCM.A and PXC24.3-UCM.A) and the TC Compact Unitary Equipment Controllers (TC16.3-UCM.T and TC24.2-UCM.T) are listed with BTL as B-AAC devices (see http://www.bacnetinternational.net/btl/index.php?m=23).
Table 19. Required BIBBs for B-AAC Profile.
B-AAC Profile Supported BIBBs
Description
Data Sharing DS-RP-B
DS-RPM-B
DS-WP-B
DS-WPM-B
Read Property, B
Read Property Multiple, B
Write Property, B
Write Property Multiple, B
Alarm and Event Management AE-N-I-B
AE-ACK-B
AE-INFO-B
Alarm and Event Notification, Internal, B
Alarm and Event Acknowledgement, B
Alarm and Event Information, B
Scheduling SCHED-I-B Scheduling Internal, B
Device and Network Management DM-DDB-B Device Management, Dynamic Device Binding, B
DM-DOB-B Device Management, Dynamic Object Binding, B
DM-DCC-B Device Management, Device Communication Control, B
DM-TS-B or DM-UTC-B
Device Management Time Synchronization, B or Device Management UTC Time Synchronization, B
DM-RD-B Device Management Reinitialization Device, B
BACnet Operator Workstation (B-OWS) Profile
The B-OWS is the operator's window into a BACnet system. While the B-OWS is primarily used for the operation of a system, it may be used for configuration activities that are beyond the scope of the BACnet standard. Insight version 3.10 and earlier operator workstations were BTL listed for B-OWS. The B-OWS profile is specified in Table 20.
BACnet Device Profiles
Siemens Industry, Inc. 63
Table 20. Required BIBBs for B-OWS Profile.
B-AAC Profile Supported BIBBs
Description
Data Sharing DS-RP-A,B
DS-RPM-A
DS-WP-A
DS-WPM-A
DS-V-A
DS-M-A
Read Property, A and B
Read Property Multiple, A
Write Property, A
Write Property Multiple, A
Data Sharing, View, A
Data Sharing, Modify, A
Alarm and Event Management AE-N-A
AE-ACK-A
AE-AS-A
AE-VM-A
AE-VN-A
Alarm and Event Notification, A
Alarm and Event Acknowledgement, A
Alarm and Event Alarm Summary View, A
Alarm and Event View and Modify, A
Alarm and Event View Management View Notifications, A
Scheduling SCHED-VM-A Scheduling View and Modify, A
Trending T-V-A Trending, View, A
Device and Network Management DM-DDB-A,B Device Management, Dynamic Device Binding, A and B
DM-DOB-B Device Management, Dynamic Object Binding, B
DM-MTS-A Device Management Manual Time Synchronization, A
BACnet Advanced Workstation (B-AWS) Profile
The B-AWS listing is an advanced version of the B-OWS listing and is primarily used for the operation of a system. It may be used for configuration activities that are beyond the scope of the BACnet standard. Insight version 3.11 and later and Desigo CC operator workstations are BTL listed for B-AWS. The B-AWS profile is specified in Table 21.
Chapter 3–BACnet Interoperability
64 Siemens Industry, Inc.
Table 21. Required BIBBs for B-AWS Profile.
B-AAC Profile Supported BIBBs
Description
Data Sharing DS-RP-A,B
DS-RPM-A
DS-WP-A
DS-WPM-A
DS-AV-A
DS-AM-A
Read Property, A and B
Read Property Multiple, A
Write Property, A
Write Property Multiple, A
Data Sharing, Advanced View, A
Data Sharing, Advanced Modify, A
Alarm and Event Management AE-N-A
AE-ACK-A
AE-AS-A
AE-AVM-A
AE-AVN-A
Alarm and Event Notification, A
Alarm and Event Acknowledgement, A
Alarm and Event Alarm Summary View, A
Alarm and Event Management, Advanced View and Modify, A
Alarm and Event View Management, Advanced View Notifications, A
Scheduling SCHED-AVM-A Scheduling, Advanced View and Modify, A
Trending T-AVM-A Trending, Advanced View and Modify, A
Device and Network Management DM-DDB-A,B Device Management, Dynamic Device Binding, A and B
DM-ANM-A Device Management, Automatic Network Mapping, A
DM-ADM-A Device Management, Automatic Device Mapping, A
DM-DOB-B Device Management, Dynamic Object Binding, B
DM-DCC-A Device Management, Device Communication Control, A
DM-MTS-A Device Management Manual Time Synchronization, A
DM-OCD-A Device Management, Object Creation and Deletion, A
DM-RD-A Device Management, Reinitialization Device, A
DM-BR-A Device Management, Backup and Restore, A
APOGEE BACnet Field Panel Interoperability This section describes the Interoperability Areas of the APOGEE BACnet field panel. It can be used to help develop interface strategies to third-party workstations and field panels.
APOGEE BACnet Field Panel Interoperability
Siemens Industry, Inc. 65
Data Sharing
The APOGEE BACnet field panel accesses points (local and FLN) on the BACnet as basic object types (analog, binary, multi-state). It supports basic BACnet read and write services.
Interoperability is between ALN-class components, both APOGEE Automation System and third-party. Examples of third-party equipment integration will be covered in Chapter 3 under the section Examples of Third-Party Equipment Integration, starting on page 82. Examples include integration to Sinamics G120 and Vacon BT300 drives. The integration of third-party devices is the domain of the Building Technologies Division integrated solutions team of Siemens Industry, Inc. Also, interoperability does not include any BACnet FLN devices.
Through the APOGEE field panel HMI, you can specify panels (including third-party panels) that are to be on your ALN for the purpose of point logs, commanding and viewing. This limits the point log from becoming too big by limiting the number of points included in the log. But, by using the encoded name or the device specific name, various APOGEE BACnet field panel applications, like PPCL, can use points from third-party panels. These points do not have to be specified to be on the APOGEE BACnet field panel’s ALN.
Object Names and Instance Numbers
Although BACnet allows unlimited point name length and allows duplicate point names in the system, each object must have a unique name within its BACnet Device. Local object names within the APOGEE BACnet field panel database are limited to 30 characters and are case insensitive. However, the BACnet field panel applications preserve case sensitive object name references in order to support remote object names in third-party panels that are case sensitive.
Names for point-like objects can be in an encoded format or a device specific format (see Chapter 5–BACnet Field Panel) to access third-party devices for the following functions:
• Point Command
• Point Log
• Point Look
• Point Priority Array Display
• Point Release
• Point Service Disable (out of service)
• Point Service Enable ( return to service)
• PPCL point name references
Chapter 3–BACnet Interoperability
66 Siemens Industry, Inc.
• Reset Total Command
• Totalization Log
Services Supported
See Chapter 2–BACnet Objects and Services.
Objects Supported
See Chapter 5–APOGEE BACnet Field Panel.
Services to Support the BACnet Browser
The field panel supports an object server that allows a BACnet Browser, such as that in the Insight workstation, access to the properties of each object. BACnet Services common to all object types are:
• Read Property Service
• Read Property Multiple Service
• The BACnet Properties common to all objects that can be accessed by these services are:
• Object_Identifier
• Object_Name
• Object_Type
• Description
PPCL
PPCL in BACnet field panels supports monitoring and commanding of Present_Value, Status, and Priority of points defined locally, over the ALN to other BACnet field panels, and over the ALN to third-party devices.
TEC Subpoints
In a BACnet field panel, commanding a TEC point will cause it to unbundle and use additional field panel memory. As with any other point, the Present_Value will be set to the highest filled-in priority level.
When a TEC point is initially browsed, the Relinquish_Default property will contain the current Present_Value of the point, and the Priority_Array property will initially display as empty.
APOGEE BACnet Field Panel Interoperability
Siemens Industry, Inc. 67
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.
Point Commanding
The panel uses BACnet services for point commands and polling. The OUT_OF_SERVICE flag of the Status_Flags property is enabled for input points only.
Alarm and Event Management
Allows BACnet clients to use BACnet services to acknowledge BACnet alarms in the panel and retrieve BACnet alarm summaries from the panel.
Allows BACnet clients to register for alarm notifications. Send alarms to BACnet clients.
System Messages
APOGEE BACnet field panels can generate system messages as a result of some system event, such as PPCL run-time errors, logins, and logouts. These APOGEE Automation System messages are made available to third-party devices via the ConfirmedTextMessage service and the UnconfirmedTextMessage service. If a third-party device supports these services, it can receive APOGEE Automation System messages. Likewise, since the APOGEE BACnet field panel supports these services, messages from third-party devices can be displayed at the field panel’s HMI.
COVs
BACnet has a service called SubscribeCOV (see section 13.14 of the ANSI/ASHRAE Standard 135-2012) to send notifications of changes of value (COV) that may occur in a property of an object. The APOGEE BACnet field panel supports COV subscriptions.
The field panel also has an Unsolicited COV Subscription feature that can be configured to send COVs to a BACnet device even when the device does not ask for (subscribe to) COVs. This feature can be used to send COVs to a third-party BACnet device that lacks the SubscribeCOV mechanisms.
Chapter 3–BACnet Interoperability
68 Siemens Industry, Inc.
Scheduling
The APOGEE BACnet field panel allows BACnet clients (for example, workstations) to use BACnet services to configure its Schedule and Calendar objects. It also allows basic BACnet point-like objects in third-party devices to be used in scheduling.
Command Object
If a command is created for an APOGEE field panel, the Property ID is set to Present value and disabled.
Trending
The APOGEE BACnet field panel allows BACnet clients (for example, workstations) to use BACnet services for configuration and upload of trend logs. Also supported is the use of BACnet objects (internal and external) in Point Logs. (This applies only to BACnet devices on the same logical ALN.)
Device And Network Management
The APOGEE BACnet field panel can supervise COV links and support timed re-subscriptions and node status. It can collect and display communications diagnostics, support time synchronization, device communications control, scanning and diagnostics, and device initialization.
Upload and Download
Allows BACnet clients (for example, workstations) to use the BACnet File object and file transfer services to upload and download the field panel’s database, even though the client has no understanding of the content of the file (database). This excludes downloads or uploads of incremental parts of the database, which requires the APOGEE-specific Confirmed Private Transfer function also supported by this field panel.
Dialout
Establish and terminate half-router connections for BACnet dialout support.
Proprietary Applications
Applications whose interfaces are not specified by BACnet (SSTO, PDL, PPCL, etc) must be configured using the APOGEE-specific Confirmed Private Transfer function.
Allows clients to subscribe for device restart notifications. Support standard BACnet device status indications.
Insight Interoperability
Siemens Industry, Inc. 69
Field Panel Tools
When APOGEE BACnet field panels are deployed with a third-party BACnet workstation that serves as the primary day-to-day operator interface, APOGEE tools are still required for mass storage, configuration, and programming. The ability for BACnet field panels to be configured by third-party clients is beyond BTL requirements.
Foreign Device
An APOGEE BACnet field panel can act as a Foreign Device so it can join to a BACnet/IP network through a BBMD (BACnet Broadcast Management Device). The Insight Foreign Device Settings dialog box allows you to set up APOGEE BACnet field panels as foreign devices, but not third-party field panels. For details about Foreign Device, see Chapter 4-BACnet Communications.
BBMD
An APOGEE BACnet field panel can act as a BBMD (BACnet Broadcast Management Device). This can be set up from the Insight workstation. For details about BBMDs and how to set it up from the Insight workstation, see Chapter 4-BACnet Communications.
Backup and Restore Password
Some third-party systems have a password for each field panel for database backups and restorations. APOGEE BACnet field panels require use of their HIGH account password for database backups and restorations.
Insight Interoperability This section covers details about the Interoperability Areas of Insight with the BACnet Option. It can serve to help you develop interface strategies to third-party B-BC class controllers.
Chapter 3–BACnet Interoperability
70 Siemens Industry, Inc.
BACnet Client and Server Options
The BACnet option for Insight has two components–the Client Option and the BACnet Server Option. The option with BACnet ALN field panel support is a software add-on to the Insight workstation that was introduced in February 2006 and was designed to work with Insight Revision 3.7 and later to provide communication with BACnet networks.4 The option allows you to monitor and command BACnet points from Insight Graphics and Point Commander, or from a third-party BACnet workstation. BACnet alarms appear in the alarm application. BACnet points can be used in dynamic trends. BACnet device network status appears on the System Profile. The BACnet Option supports communication with BACnet devices over Ethernet and BACnet/IP networks.
The BACnet Client Option provides communication with both the APOGEE Automation System and third-party BACnet devices and systems, enabling functionality such as to monitor and command BACnet objects, establish BACnet schedules and calendars, back-up databases in BACnet devices, receive and acknowledge BACnet alarms, and establish and read BACnet trend logs.
The BACnet Server Option can export P2 proprietary protocol APOGEE point information as BACnet objects, so that a third-party BACnet client system may monitor and command APOGEE points, and monitor and acknowledge alarms within APOGEE proprietary P2 networks and field panels.
Insight Data Sharing
Point-Like Objects
The Insight BACnet Option supports BACnet’s basic point-like objects (analog, binary, multistate) in Insight applications.
Point Names
When uploading points from third-party BACnet field panels, there are four ways in which the names can be created:
• Encoded Name (BAC_1234_BI_1)
• Device Instance and Object Name (1234_FAN)
• Object Name and Device Instance (FAN_1234)
• Device Name and Object Name (PANEL1_FAN)
4 The Insight BACnet option was introduced in March 2000 with Insight Revision 3.2 but this option only allowed communication with
third-party BACnet devices.
Insight Interoperability
Siemens Industry, Inc. 71
The first, and recommended way, is to use encoded names that contain the Device ID, Object Type, and Object Instance number in the name. For example, a Binary Input with Instance Number 1 from Device 1200 would have a point name of BAC_1200_BI_1.
The remaining choices use the object name with the device name or Instance Number appended. Regardless of choice, APOGEE point names must be unique system wide and be 30 characters or less.
BACnet Object Browser
The Insight software includes a BACnet Object Browser that allows viewing third-party objects and properties, even if they do not integrate with standard Insight applications.
Point Commanding
Out-of-Service will be enabled for third-party BACnet points.
Third-Party Proprietary Objects
The Insight software does not provide integration of third-party proprietary BACnet objects (or group objects), properties and services into Insight applications. However, third-party proprietary objects and properties are accessible (readable) via the BACnet Browser included in the Insight software.
Insight Alarm and Event Management
The Insight BACnet Option registers with BACnet devices as an alarm recipient. It uses BACnet services to display and acknowledge BACnet alarms and supports display of BACnet alarm summaries.
Initials
When alarms are acknowledged by an Insight operator, the correct user initials will be displayed. Alarms that are acknowledged by a third-party system will display BAC at the Insight workstation. The initials SYS will be displayed at the Insight workstation for alarms that do not require acknowledgements.
Chapter 3–BACnet Interoperability
72 Siemens Industry, Inc.
Alarm Acknowledgements
In BACnet, each one of the three state transitions (To-OffNormal, To-Fault, and To-Normal) can require a separate acknowledgement. If an operator acknowledges an item in the alarm window from the Insight workstation, it will send up to three acknowledgements to the BACnet device (software keeps track of how many acknowledgements to send). A means to acknowledge a single transition is not provided. Conversely, if a third-party workstation acknowledges only one state, when three states require acknowledgement, the Insight application will not display the alarm as acknowledged until all three states have been acknowledged.
Notification Class
The Insight software has a Notification Class dialog box where you can edit Notification Classes for BACnet field panels. You can create/add/modify/remove Notification Classes in third-party panels as well as APOGEE BACnet field panels. For details about notification classes, see Chapter 8–BACnet Alarming.
Insight Scheduling
Schedule and Calendar objects for Siemens BACnet panels are stored in the Insight database. Therefore, these objects can be edited even if the Insight workstation is not communicating with the panel (editing may be performed online or offline). Schedule and Calendar objects for third-party BACnet devices are stored in the third-party devices only. Therefore, these objects can be edited only when the Insight workstation is in communication with the device (editing must be performed online only).
The Scheduler application in the Insight and Commissioning Tool software is used to edit Schedule and Calendar objects in BACnet devices. This includes creating, copying, viewing, modifying, and deleting these objects in both native Siemens BACnet panels and third-party BACnet devices. The BACnet items are visible only if the Insight BACnet Option is present.
Starting with Insight Version 3.11, the Scheduler application has been enhanced as follows:
• Display of BACnet Schedules. The Scheduler application has been enhanced so that BACnet schedules now display in the calendar view. In addition, you can now modify a BACnet schedule by double-clicking its entry in the Scheduler application.
Insight Interoperability
Siemens Industry, Inc. 73
• Week Day Values Auto-populated. In the BACnet Schedule Properties, Calendar Entry Properties, and Exception Properties dialog boxes, when you specify values for the Day, Month, and Year fields, the Week Day field is automatically populated with the appropriate day of the week.
• Improved BACnet Exception Schedule Setup. In the Exception Properties dialog box, the system automatically populates all the fields with the values from the Effective Period’s Start date information. When defining a Week and Day exception type, the system automatically populates the Month and Week Day fields with the values from the Effective Period’s Start date information.
• New BACnet Schedule Properties Dialog Box. This new dialog box provides a more streamlined method of editing BACnet schedules, which allows you to focus on the most commonly-used features of BACnet schedules.
• Showing or Hiding BACnet Schedules in the View Menu. The View menu has been enhanced with a check box that enables you to show or hide BACnet schedules.
• Basic button added to the Advanced BACnet Schedule Properties dialog box. The Advanced BACnet Schedule Properties dialog box has been enhanced with a Basic button that allows you to go back to the BACnet Schedule Properties dialog box.
Chapter 3–BACnet Interoperability
74 Siemens Industry, Inc.
Command Object Editing
For third-party field panels, the Insight software allows you to select the Property ID and the Command Priority Array Index. The Command Priority Array Index is a list of 16 command priorities available for BACnet objects. The lowest array index is the highest command priority.
Insight Trending
The Insight BACnet Option supports configuring and uploading (manual or COV triggered) BACnet trend logs from APOGEE and third-party devices. However, you cannot use it to create trend definitions in third-party BACnet panels. But, you can establish Remote Trending with the following functionality:
• BACnet Trend logs can record historical data for points on another device. The storage location of trend log objects is not limited to the local panel.
• P1 FLN points are “owned” by the panel and appear as Locally trended points, whereas MS/TP FLN points are “owned” by their own MS/TP device and are trended Remotely.
Insight Device and Network Management
The Insight BACnet Option supports time synchronization, device communications control, scanning and diagnostics, and device initialization.
Insight Interoperability
Siemens Industry, Inc. 75
Field Panel Database Upload/Download
The Insight BACnet Option uses BACnet File objects and file transfer services to upload and download field panel databases, even if it has no understanding of the content of the file (database). It cannot download or upload incremental parts of a third-party field panel’s database. This requires the APOGEE-specific Confirmed Private Transfer function. It cannot create or edit third-party databases.
Foreign Device
An Insight workstation can act as a Foreign Device so it can join to a BACnet/IP network through a BBMD (BACnet Broadcast Management Device). For details about Foreign Devices and how to set up the Insight workstation as a Foreign Device, see Chapter 4–BACnet Communications.
Cloaking
A BACnet field panel can be Cloaked–removed from the Insight System Profile tree. This allows you to hide devices that you do not want displayed at the Insight workstation and to keep the device discovery feature from constantly re-adding the devices to an ALN. Only third-party devices can be cloaked.
BBMD
An Insight workstation can act as a BBMD on a BACnet network. For details about BBMDs and how to set up the Insight workstation as a BBMD, see Chapter 4–BACnet Communications.
Although the Insight software provides an option to synchronize all BBMD tables, all of the devices in the table must be APOGEE field panels or Insight workstations for the sync to work. All third-party BBMDs must be edited manually.
Database Transfer of Object Types
For third-party panels only, the Trend Log object and the Command object are uploaded and represented as points. The Trend log object is uploaded and represented as a virtual LDO point; the Command object as a LENUM point.
BACnet Field Panel Definition
Third-party BACnet field panels are included (along with PXC) as the types recognized by the Insight workstation in the BACnet Field Panel Definition dialog box.
Chapter 3–BACnet Interoperability
76 Siemens Industry, Inc.
Backup and Restore Password
A Backup/Restore Password section is in the BACnet Field Panel Definition dialog box for access to third-party panels for doing a backup or restore. Since passwords are optional, some devices may not require them. APOGEE field panels use their HIGH account password.
Field Level Network Devices
The Insight workstation provides Automation Level Network (ALN) interoperability between ALN-class components, both APOGEE and third-party. It does not cover integration of third-party Field Level Network (FLN) -class BACnet devices. That is the domain of the BACnet Field Panels and Integration Drivers.
Cross-Trunk
The Insight BACnet Client Option allows the Insight workstation and APOGEE P2/Ethernet field panels to read and command point-like objects in the BACnet devices (APOGEE 3.x field panels and third-party devices). Access in the other direction is not available. That is, the BACnet devices cannot access points in the APOGEE P2/Ethernet field panels (the Insight BACnet Server Option is required for this). Thus, a BACnet device cannot subscribe to COVs from a point in an APOGEE P2/Ethernet field panel.
Upload and Download
Allow BACnet clients (for example, workstations) to use the BACnet File object and file transfer services to upload and download the field panel’s database, even though the client has no understanding of the content of the file (database). This excludes downloads or uploads of incremental parts of the database, which requires the APOGEE-specific Confirmed Private Transfer function also supported by this field panel.
DesigoTM CC Released in July 2012, Desigo CC is a new management workstation that provides optimized monitoring and control of integrated building automation (including System ONE applications installed on PXC Modular or PXC Compact controllers) and fire safety systems, and incorporates real-time video for event verification. Some of the unique features of the Desigo CC management station are:
• Single management station for building automation, fire safety, and video cameras
• Access through web-browser, dedicated console, or Windows App provides the same capabilities and user interface from anywhere
DesigoTM CC
Siemens Industry, Inc. 77
• Workflow-driven user interface design that provides critical information in a single view for fast, accurate decision-making
• Standard and user-defined hierarchies for navigating the system according to a user’s point of view
• Vector-based graphics with AutoCAD import
• Time-shifted Trend views allows simultaneous comparison of trended values over multiple time ranges
Desigo CC uses a flexible full client-server architecture for Building Automation Control Systems and Fire Safety Systems, allowing configurations from small single-seat to large multi-user installations.
Desigo CC can also be installed on a single computer, where the server and the client share one hardware platform. This computer can also perform as server for additional clients.
Desigo CC is equipped with a flexible licensing mechanism that supports differentiated licensing based on the size of the different discipline systems and also on the number of clients anywhere from a single to unlimited clients.
Desigo CC workstation software provides a graphical approach to manage and control a facility from a
flexible, easy-to-use interface. DesigoTM
CC provides facility-wide efficiencies, cost effective information sharing, and event management.
The server, the front-end processor, and the dedicated installed clients run on Windows 7 64-bit or Windows Server 2008 R2. Web clients can use Microsoft Internet Explorer web-browser Version 8 on Windows XP, or Version 9 or later on Windows 7. The Windows desktop app can be downloaded to clients running Windows XP or Windows 7.
Desigo CC enhances the power of Siemens APOGEE Building Automation System. APOGEE, the most trusted brand in the market, has thousands of installations in facilities all over the world. Desigo CC brings a new dimension to APOGEE’s capabilities, giving you a more intelligent level of integration, performance and efficiency for your building’s core systems.
Desigo CC for APOGEE delivers centralized information and single control of building automation, fire and security systems, helping you drive better outcomes.
Compatibility
Desigo CC is compatible with the following subsystems (see release notes for details):
• APOGEE building automation system (BACnet only)
• XNET FireFinder XLS and MXL fire safety systems
Chapter 3–BACnet Interoperability
78 Siemens Industry, Inc.
• FCnet for Desigo Fire Safety systems
• Video surveillance through IP Cameras
• Third-Party Building Automation and Fire subsystems based on BACnet
• Third-Party subsystems through OPC (Open Platform Communication)
• Integration through SNMP (Simple Network Management Protocol), ONVIF (Open Network Video Interface Forum)
BACnet Firmware Compatibility with Desigo CC Software
This section outlines the APOGEE firmware revisions which are compatible with Desigo CC software, and the field panels that support those revisions. This information was derived from the Firmware Revision 3.2.4 Release Notes, posted on InfoLink (http://iknow.us009.siemens.net/infolink/automation/releasenotes/FW/5459753P24.pdf).
CAUTION:
The Power MEC in the following table is retired, but is still sold through the repair parts (Rparts) program until October 1, 2017. Refer to POA-001.
Table 22: BACnet Firmware Compatibility with Desigo CC Software.
Field Panel (Firmware Revision String) Model and Product Number
Desigo CC Market Package 1 (MP1)
PXC Modular Series (PXME) PXC00-E96.A, PXC100-E96.A 3.2.4
3.2.3a
3.2.2a
3.2a
3.1a
3.0.1a
PXC Compact Series (PXCE)
PXC36-E.A, PXC36-EF.A
3.2.4
3.2.3a
3.2.2a
3.2a
PXC Compact Series (PAAC)
PXC24.2-UCM.A
3.2.4
3.2.3a
3.2.2a
PXC Compact Series (PXCE)
PXC16.2-E.A, PXC16.2-ER.Ab
PXC24.2-E.A, PXC24.2-ER.A
PXC16.2-M.A, PXC16.2-MR.Ab
PXC24.2-M.A, PXC24.2-MR.A
3.2.4
3.2.3a
3.2.2a
3.2a
3.1a
DesigoTM CC
Siemens Industry, Inc. 79
Field Panel (Firmware Revision String) Model and Product Number
Desigo CC Market Package 1 (MP1)
PXC16.2-EF.A, PXC16.2-ERF.Ab
PXC24.2-EF.A, PXC24.2-ERF.A
PXC Compact Series (PXCE)
PXC16-E.Ab, PXC16-ER.Ab
PXC24-E.Ab, PXC24-ER.Ab
3.2.4
3.2.3a
3.2.2a
3.2a
3.1a
3.0a
Power Open Processor
BACnet/IP ALNb (562-040)
3.2a
3.1a
3.0a
Power MEC (MCNE)
1200EB (549-632)
1100EB/1110EBb (549-630, 549-631)
1210EBb (549-633)
3.2a
3.1a
3.0a
Power MEC (MEFE)
1200EFB (549-634)
1210EFBb (549-635)
3.2a
3.1a
3.0a
Power MEC
1200ELB (549-636)
1210ELBb (549-637)
3.1a
3.0a
a. Field panel Point Viewer/Editor, Program Viewer/Editor, Device Viewer/Editor, and Subpoint Viewer/Commander for Desigo CC are not available in firmware revisions 3.2.3 and lower. Desigo CC Trend Log Object creation is not supported in firmware revisions 3.2.3 and lower Field panel revisions 3.2.3 and lower should only be used with Desigo CC on networks with 5 or more field panel controllers.
b. This model is discontinued.
Desigo CC Scheduling
The Desigo CC scheduler allows you to schedule events for management stations and field panels at your facility. Scheduling is the process of creating and editing commands, calendars, schedules, and time triggers. An event is simply a scheduled system activity that involves equipment and spans a period of time, with a frequency of repetition applied to it.
Scheduler consists of the following schedule types:
• Management Station Calendars
• Management Station Schedules
• Management Station Time Triggers
• BACnet (Field Panel) Calendars
Chapter 3–BACnet Interoperability
80 Siemens Industry, Inc.
• BACnet (Field Panel) Schedules
• BACnet (Field Panel) Commands
BACnet scheduling allows you to automatically command points at prescribed time intervals. You can create daily or weekly schedules for BACnet field panels. Each BACnet panel stores its own calendar and schedule objects, and a BACnet panel can store and run multiple calendars or schedules at the same time. Because BACnet schedules reside in and are executed by field panels, they run even if the management station they are associated with is not running. BACnet schedules handle only BACnet objects.
BACnet calendars allow you to override a scheduled event. In this sense, you can consider them as exception schedules consisting of dates only, the same as management station calendars.
Commands allow you to control one or more BACnet objects related to your schedules. For example, you might want to create a command that turns lights on and maintains room temperature at 72°F (22.22°C) when the room is occupied. When the room is unoccupied, the command would turn lights off and maintain the room temperature at 65°F (18.33°C). In this scenario, you could create a command with an entry for Occupied/Unoccupied, save it, and then drag it from System Browser to a schedule of your choice. The schedule will determine what time the command executes, the start and end dates, and the frequency of repetition.
More information can be found in the DesigoTM CC Getting Started Version 1.1 Quick Start Guide, and the DesigoTM CC User Guide Version 1.1 Operation Manual posted on InfoLink at:
http://iknow.us009.siemens.net/infolink/automation/DesigoCC/DesigoCC%20MP11.htm.
Desigo CC Device and Network Management
The Desigo CC management station can support the following types of networks:
• BACnet, the field network supporting building automation (Desigo, APOGEE) and fire (FS20 SAFEDLINK) systems, is discussed in the following sections. General fire systems integration is treated in the FS20 Integration Guide (A6V10376188).
• The XNET, the field network supporting MLX and XLS fire control panels, is discussed in the XNET Integration Guide (A6V10376180).
• The OPC network, supporting the connection with third-party OPC servers, is discussed in the OPC Server Integration Guide (A6V10380501).
DesigoTM CC
Siemens Industry, Inc. 81
• SNMP (Simple Network Management Protocol), the system network related to the Desigo CC components, is discussed in the following sections.
More information can be found in the DesigoTM CC Engineering Manual Version 1.1 posted on InfoLink at:
http://iknow.us009.siemens.net/infolink/automation/DesigoCC/DesigoCC%20MP11.htm.
Open Architecture
Desigo CC for APOGEE was developed to keep pace with changing technology in modern facilities. APOGEE is an open system based around BACnet, and it’s flexible enough to work with many other protocols with the addition of Desigo CC. Its open architecture brings unrivaled control of critical building equipment and systems. It supports a variety of open system protocols and IT standards, including:
• Modbus
• XNET
• OnVIF
• SNMP (Simple Network Management Protocol)
• OPC (Open Platform Communications)
• SMTP (Simple Mail Transfer Protocol)
The system architecture showing all possible Desigo CC configurations is shown in Figure 19.
Chapter 3–BACnet Interoperability
82 Siemens Industry, Inc.
Figure 19: Desigo CC System Architecture Showing all Possible Configurations.
Examples of Third-Party Equipment Integration The following information can be found in the BACnet Solutions in Brief (127-0831) or BACnet MS/TP (127-1477) document posted on InfoLink. The Integration Availability List (126-974) has the most current information regarding Integrated solutions.
Since BACnet is a standard protocol used by many vendors, its application is frequent, yet tricky due to the many different ways for vendors to implement BACnet. It is important to understand the different APOGEE® solutions for BACnet and when to apply each solution.
Each vendor, including Siemens, will have a Protocol Implementation and Conformance Statement (PICS) that tells how they’ve implemented the BACnet protocol. Always use the PICS as a basis for understanding the functionality implemented by a particular BACnet device.
Typically, BACnet devices have a combination of BACnet client and BACnet server capabilities, with the focus on one or the other based on its role in the system. These capabilities are spelled out in the devices’ PICS. BACnet client capabilities (denoted as “A” in the BIBBs (BACnet Interoperability Building Blocks) of the PICS) enable the BACnet client device to initiate a request for information and action from a BACnet server device. BACnet server capabilities (denoted as “B” in the BIBB section of the PICS) enable the execution of requests from BACnet clients.
Examples of Third-Party Equipment Integration
Siemens Industry, Inc. 83
The APOGEE Automation System supports both BTL-listed and nonlisted BACnet products. BTL-listed products have a higher likelihood of interoperability and compatibility, but issues may still occur. Interoperability issues are often related to the timing of communication packets, content of communication packets, and variances in vendor implementation of the BACnet protocol; for example, alarm notification and acknowledgement can be implemented multiple ways and still comply with the BACnet standard.
APOGEE BACnet Product Positioning
The APOGEE Automation System provides multiple ways to integrate third-party systems or devices using the BACnet protocol:
• BACnet Option for Insight® Software — This is an MLN level solution. It was developed to provide workstation-to-workstation BACnet Ethernet or BACnet/IP integration, or integration to devices supporting BACnet Ethernet or BACnet/IP. The BACnet Client Option is used to monitor and command BACnet server devices, such as APOGEE BACnet/IP field panels or third-party BACnet devices. The BACnet Server Option is used to export proprietary APOGEE Automation System information to third-party BACnet client applications, such as a workstation software package.
• Trane Driver — This solution uses BACnet PTP (Point-to-Point), but is tailored specifically for Trane® equipment and cannot be used for integration with other BACnet systems or devices.
• BACnet Driver in MS/TP (Master Slave/Token Passing) Mode — This solution provides a general purpose BACnet MS/TP integration solution for HVAC, lighting control, and other equipment or devices supporting the BACnet MS/TP protocol. With the release of Firmware 3.1 and higher, the BACnet Driver in MS/TP Mode is most typically applied when the ALN is APOGEE proprietary protocol-based 2.x firmware.
• BACnet Driver in IP Mode — The BACnet Driver in IP Mode communicates through the Ethernet port with other BACnet/IP devices.
• BACnet PXC Modular, PXC Compact, and now retired MEC and Open Processor — The BACnet field panel supports BACnet as both a BACnet server and client, but the main role of the building controller in the system is to provide data to the workstation and other field panels; therefore, its primary role is as a BACnet server device.
BACnet Solutions
For a complete list of BACnet solutions, refer to the Availability List, which is at this location on InfoLink:
Chapter 3–BACnet Interoperability
84 Siemens Industry, Inc.
http://iknow.us009.siemens.net/infolink/integration/126974.xls. This worksheet lists the Vendors and Product Updates for drivers that support BACnet MS/TP or IP Integration and BACnet for Field Panels and BACnet for Insight.
There is a Field Tested Applications SharePoint Site. Click here to find additional applications that have been field tested. Table 23 provides a quick reference for deciding on the proper BACnet solution for APOGEE Automation System integration.
Table 23: Type of BACnet Solution for Different APOGEE Integration Requirements.
Integration Needs BACnet Solution
BACnet Ethernet or BACnet/IP integration for BACnet devices—either APOGEE BACnet/IP field panels, or third-party BACnet/IP or BACnet Ethernet devices.
BACnet Option for Insight Software
BACnet field panels—APOGEE BACnet field panels support BACnet/IP with Field Panel Firmware 3.0 and add BACnet MS/TP support with Field Panel Firmware 3.1, providing both BACnet client and BACnet server capabilities, though the primary mission is as a BACnet server.
BACnet Field Panels
Trane BCU integration into the APOGEE Automation System—using BACnet PTP serial RS-232 connection.
Trane Driver
BACnet MS/TP and BACnet/IP Integration of controllers or devices—serial RS-485 into the APOGEE Automation System. Support for BACnet MS/TP FLN is available using a BACnet MS/TP Driver on Field Panel Firmware 3.2, or a third-party-router.
With Field Panel Firmware 3.1, the field panels support configurable FLN for P1 or BACnet MS/TP directly.
BACnet Driver in MS/TP mode and BACnet/IP Driver
Or Field Panel with BACnet firmware.
Siemens Industry, Inc. 85
Chapter 4–BACnet Communications Chapter 4 describes BACnet communication theory in relation to the Insight application. It includes the following topics:
• BACnet Communication Theory
• Insight Communication with the BACnet Option
• Example BACnet Job (Internetwork)
BACnet Networking Technologies A BACnet system requires the appropriate network technology to interconnect all of the devices. The BACnet standard defines the datalink and physical communications portion of the protocol (see BACnet Protocol Model in this chapter) through six options. Table 24 defines these options and their support by APOGEE. Once the Insight workstation is connected to the network, it can successfully communicate with all other devices on the BACnet Internetwork, regardless of the networking technology used by the other devices.
Table 24. BACnet Protocol Datalink Communications Options.
Protocol Datalink Communications
Description Support by APOGEE System
BACnet over Ethernet BACnet over IEEE 8802-3 Ethernet
Supported by Insight 3.7 or later BACnet Option
BACnet/IP BACnet over Internet Protocol on Ethernet
Supported by Insight 3.7 or later BACnet Option and Field Panel Firmware Revision 3.0 or later.
Also supported by the Updated version of the BACnet Driver Firmware Revision 3.2 or 2.8.5.
MS/TP Master Slave/Token Passing over EIA-485 network
Supported by Insight 3.9.1 or later BACnet Option through Field Panel Firmware Revision 3.1 or later, and the BACnet Driver in MS/TP Mode on previous firmware revisions
PTP Point-to-Point over EIA-232
Supported through APOGEE Trane Driver and third-party BACnet routers
LonTalk BACnet over LonTalk Not supported in APOGEE system
ARCnet BACnet over ARCnet Supported through third-party BACnet routers only
Zigbee BACnet over Zigbee Not supported in APOGEE system
Chapter 4–BACnet Communications
86 Siemens Industry, Inc.
BACnet Over Ethernet
BACnet over Ethernet supports BACnet, but with limitations. The biggest is that IS/IT routers typically block Ethernet broadcasts over the network. BACnet over Ethernet cannot get around these blocks. With BACnet over Ethernet, only devices on the same subnet are able to detect each other, unless the IS/IT department modifies their routers to allow Ethernet broadcast distributions. Ethernet protocol by itself is considered a non-routable protocol because it works strictly with MAC addresses, and does not use IP addresses. BACnet over Ethernet uses the Ethernet MAC addresses in each of the network devices.
BACnet/IP
BACnet/IP was developed specifically for transporting BACnet messages between IP devices (over TCP/IP). It is the preferred networking technology for BACnet. BACnet/IP uses the IP address plus the UDP port address. BACnet/IP uses BACnet/IP Broadcast Management Devices (BBMDs) to get messages through IS/IT routers. For further details, see BACnet Broadcast Management Device (BBMD) in this chapter.
Figure 20 shows an example Ethernet BACnet/IP ALN configuration with two ALN controllers. FLN buses can either be P1 or MS/TP:
• P1 – Three FLNs, 31, 31, and 30 devices per FLN, respectively; 4800 baud only.
• MS/TP – One FLN only (on Port 1), 96 FLN devices max.; 9600, 19200, 38900, 56800, 76800 baud rates available.
Figure 20. Example Ethernet BACnet/IP ALN Configuration.
Master-Slave/Token-Passing
Master-Slave/Token-Passing (MS/TP) uses a token to control access to a bus network. A master node can initiate the transmission of data when it holds the token. Slave nodes may transmit data in response to requests from master nodes. In MS/TP systems with multiple masters, the token determines which master can initiate transmissions.
BACnet Networking Technologies
Siemens Industry, Inc. 87
APOGEE MS/TP slave nodes never hold the token. So, a means is provided to allow time for replies to be returned from slave devices. When a request that expects a reply is sent to a MS/TP slave node, the master waits for the reply to be returned before sending a request to another slave.
BACnet defines MS/TP for small networks with devices having lower speed requirements; 1 Mbps or less over twisted pair wiring. MS/TP over EIA-485 provides for small local networks that are up to 5,000 ft (1,524 m) long using shielded twisted pair wiring.
With Firmware Revision 3.1 or later, BACnet MS/TP devices can be integrated into an APOGEE Automation System directly. The driver communicates with Insight software, other APOGEE field panels, and the BACnet MS/TP devices. See the BACnet MS/TP section in this chapter.
For more information about the interaction and functionality between field panels and an MS/TP FLN devices, see Chapter 6–MS/TP Devices in the APOGEE BACnet ALN Field Panel User’s Manual (125-3020, January 2011).
LonTalk
LonTalk is the Echelon Corporation’s LAN technology. The Insight BACnet Option cannot directly connect to a BACnet on a LonTalk network, but it can communicate with such networks via BACnet third-party routers.
BACnet devices can utilize a LonTalk LAN to convey BACnet messages. This is identical to the way that BACnet messages are transported by Ethernet, ARCNET, and MS/TP. System designs, however, have steered away from BACnet messages on LonTalk. BACnet is optimized more for applications related to field panels and workstations. LonTalk, carrying proprietary LONMark messages, is the preferred method for unitary controller products, terminal unit controllers, and smart sensor/actuator applications.
CAUTION:
Although BACnet messages can be transported by LonTalk, this does not mean that native BACnet devices can automatically communicate with any other device on a LonTalk network. BACnet devices can only communicate with other BACnet devices. If a device on a LonTalk network uses Echelon’s proprietary technology, for example, it will not be able to understand BACnet messages, which are completely different.
As stated above, the Insight BACnet Option does not support direct connection to BACnet on a LonTalk network.
BACnet Protocol Model
The BACnet protocol is based on the seven-layer OSI model; however, BACnet is optimized by eliminating the transport, session and presentation layers (layers four, five and six) of the OSI model.
Chapter 4–BACnet Communications
88 Siemens Industry, Inc.
Table 25 shows the BACnet layers and the equivalent OSI model layers.
BACnet Networking Technologies
Siemens Industry, Inc. 89
Table 25. BACnet Protocol Architecture.
BACnet Layers Equivalent OSI Layers
BACnet Application Layer
Application
N/A Presentation
N/A Session
N/A Transport
BACnet Network Layer
Network
ISO 8802-2 (IEEE 802.2)
Type 1 Ethernet
MS/TP
PTP
Data Link
ISO 8802-3 (IEEE 802.3)
Ethernet
ARCNET
EIA-485
EIA-232
Lon Talk
Physical
For example, BACnet Master-Slave/Token-Passing (MS/TP) is a data link protocol. MS/TP provides services to the BACnet network layer similar to the way Ethernet’s (ISO 8802-2) Logical Link Control (part of the data link layer) does. MS/TP uses the services provided by the EIA-485 physical layer.
Some protocols, such as the Internet’s TCP/IP and BACnet’s BACnet/IP, are actually suites or stacks of protocols. They are layered sets of protocols which work together to provide a set of network functions. Each intermediate protocol layer uses the layer below it to provide a service to the layer above. The OSI model is an attempt to provide a standard framework within which to describe protocol stacks.
The Insight BACnet Option uses a BACnet protocol stack implementation called BACstac from Cimetrics, Inc. The BACstac protocol is required for computers running Insight or Commissioning Tool to communicate on a BACnet network. BACstac is shipped with the Insight application, but is installed separately. The version of BACstac must be compatible with the version of the Insight application. The protocol requires a one-time installation and setup on any Insight PC with an attached BBLN, or PCs acting as a BBMD, and on every Commissioning Tool PC to interact with BACnet devices. BACstac installation is easily accomplished after Commissioning Tool or Insight installation is completed. If Insight or CT is upgraded to a new version, BACstac needs to be uninstalled and reinstalled to match the new version.
Chapter 4–BACnet Communications
90 Siemens Industry, Inc.
On Insight versions prior to 3.11, the BACstac protocol was installed as a network protocol in network settings. Installing the protocol on Insight versions after 3.11, follow the path: C:\Insight\BACstac and then double-click the file bacstac.msi.
• A new folder will be created: C:\ProgramFiles\Cimetrics\bacstac v6.0g
• To make configuration changes to BACstac, double-click the file baccfg.bat located in the new folder. A port table opens as shown below.
For more information about the OSI model, see the Networking Essentials for APOGEE Application Guide (125-2011), posted on InfoLink.
In the application portions of the protocol, BACnet defines a typical device, objects and information within a device, properties of the objects, and protocol services. For detailed information on the BACnet protocol, refer to the BACnet Information Guide (Copyright 2005 Siemens Building Technologies, Inc., P/N 153-912p10) and the on-line BACnet training modules available through Education Services (ES Online).
BACnet Cimetrics BACstac
The Insight BACnet Option uses a BACnet protocol stack implementation called BACstac from Cimetrics, Inc. BACstac is shipped with the Insight application, but is installed separately. The version of BACstac must be compatible with the version of the Insight application. Table 26 outlines which Cimetrics BACstac versions are supported and shipped with the corresponding Insight revision. See InfoLink hyperlinks below corresponding to the Insight Version for more detail on a particular Insight version.
Only the current version of the Cimetrics BACstac is available on the Insight CD-ROM when shipped; no previous versions are included.
Table 26. Insight Software and Cimetrics BACstac Compatible Versions.
Insight Version Cimetrics BACstac Version
BACstac Release Date Insight Release Notes Reference Part
Number
3.12 6.0-g 03/25/2010 125-3160-312
3.11 6.0-g 03/25/2010 125-3160-311
3.10 5.0-i 03/30/2009 125-3160-310
3.9.1 4.3-m 10/01/2007 125-3160-391
BACnet Networking Technologies
Siemens Industry, Inc. 91
Basic BACnet Networking
This section describes how BACnet devices can be interfaced with other BACnet devices, non-native BACnet devices and BACnet devices on different networks. BACnet routers allow APOGEE BACnet/IP-based networks to interoperate with any other BACnet networks. The following examples can provide the basis for many combinations.
Native BACnet Devices on the Same LAN
Native BACnet means that the devices speak and understand BACnet. The devices may be interconnected using any of the approved BACnet LAN technologies. However, all devices must communicate using the same LAN type. Most communication is direct, device-to-device (Figure 21).
Figure 21. Native BACnet Devices Communicating Directly, All on the Same Network Type.
Native BACnet Devices with Different LAN Technologies
To interconnect native BACnet devices on multiple LAN technologies, such as an Ethernet LAN to a MS/TP LAN, the network layer protocol is used. A BACnet router is the physical device that passes the messages on the network level. The BACnet standard contains the specifications for the BACnet router. See the BACnet Router vs. IP Router section in this chapter for more details.
Figure 22 shows an example of how two BACnet routers allow native BACnet devices on different networks to communicate. Messages between the ARCNET and MS/TP LANs pass through both routers via the BACnet Ethernet. If the BACnet workstation is running the Insight software, then the BACnet MS/TP devices and the BACnet ARCNET devices will appear in System Profile as ALN devices.
Virtual points must be set up for an APOGEE BACnet field panel on Ethernet to communicate with a BACnet MS/TP or ARCNET devices to support alarms and trends.
Chapter 4–BACnet Communications
92 Siemens Industry, Inc.
Figure 22. BACnet Devices on ARCNET and MS/TP LANs Communicating via BACnet Routers.
Native BACnet to Non-Native BACnet Devices
To interconnect native BACnet devices to non-Native BACnet devices, the Application Layer protocol is used. As Figure 23 shows, a gateway is the physical device used to pass the Application layer.
Because the messages of BACnet devices are different from the messages of non-BACnet devices, gateways translate these messages. A gateway also handles the Network, Data Link, and Physical layers by packaging the message for transport on the networks involved. Gateways are more complicated devices than routers.
A gateway is required to interface native BACnet devices to the non-BACnet devices of an existing, proprietary DDC system–such as an APOGEE Automation System. Gateways of this type usually must come from the maker of the proprietary system because detailed knowledge of the system’s proprietary protocol is required.
The Insight BACnet Option can act as a gateway to allow communication between BACnet devices and Insight workstations with APOGEE P2/Ethernet field panels.
BACnet Networking Technologies
Siemens Industry, Inc. 93
Figure 23. Native BACnet and Non-Native BACnet Devices Communicating through a Gateway.
BACnet Communications
BACnet/IP
BACnet messages can travel over networks that use the Internet Protocol (IP) by using BACnet/IP. With BACnet/IP, the BACnet device is an IP device (IP node), complete with its own IP address and IP protocol stack.
BACnet/IP devices communicate using BACnet messages wrapped in IP messages. BACnet/IP messages can be unicast (point-to-point)–from one device specifically to another device, or broadcast–from one device to many devices. Due to the limitation of sending broadcast messages though IP routers, BBMDs (BACnet Broadcast Management Devices) are used to send broadcast messages around IP routers using a UNICAST message, which is a one-to-one IP message exchange.
A BACnet broadcast message can be:
• Local–on the same BACnet network as the source • Remote–on another BACnet network (but not its own) • Global–to all BACnet networks
Siemens Industry, Inc. has standardized on BACnet/IP for APOGEE Automation Systems. Most competitor's BACnet devices use BACnet/IP. APOGEE Firmware Revision 3.1 supports BACnet protocols:
Chapter 4–BACnet Communications
94 Siemens Industry, Inc.
• Field panels configured for BACnet protocols on both the ALN and FLN act as BACnet routers.
• All physical network segments need unique BACnet Network ID numbers.
• The logical group of devices in an ALN may span multiple physical network segments.
• The logical group of devices in an FLN may span multiple physical network segments.
If necessary, BACnet routers can be used to allow APOGEE BACnet/IP networks to interoperate with any other BACnet networks. The Insight BACnet Option and APOGEE BACnet 3.x field panels support using BBMDs, and each can provide the BBMD functionality.
BACnet Broadcast Management Device (BBMD)
Many IP routers prevent broadcast messages from being transmitted across a WAN. The BACnet protocol uses broadcast messages such as Who-Is, Who-Has, I-Am and I-Have to interrogate the network and determine what other BACnet devices exist. For these broadcast messages to be transmitted across IP routers that block such messages, one device on each subnet must be set up as a BACnet Broadcast Management Device (BBMD).
BBMDs are software applications that forward BACnet/IP broadcast messages across IP routers. A single BBMD must appear on each side of an IP router. Communication between BBMDs is via UNICAST messages. There are two methods available to the BBMD to broadcast a message on a remote network–the one-hop and the two-hop methods. A BBMD can send broadcasts to another subnet via another BBMD device using a UNICAST message. Sending a UNICAST to a subnet is called One-Hop Forwarding. Sending a UNICAST to another BBMD is called Two-Hop Forwarding.
The BBMD does not need to be a physically distinct device from a field panel or a workstation. It is a software or firmware application that can be integrated into a device that performs other operations, such as a field panel. For example, an Insight workstation with the BACnet Option or a BACnet field panel can also function as a BBMD.
CAUTION: More than one device set-up as a BBMD within a subnet will cause severe harm to the network, due to redundant broadcast messages in the same subnet.
Sending data unprotected across a network poses a risk to the integrity of the system. Messages can be hijacked via a ‘Man in the Middle Attack’ and data intercepted, copied or modified. If the application requires for data to be send across a Network the IT department responsible for the system shall be involved to assess the risk and put measures in place to minimize such risk. Siemens Industry Inc recommends the use of VLAN technology to protect data in transit. See Chapter 14 for further information on cyber security.
BACnet Networking Technologies
Siemens Industry, Inc. 95
The assumption with BACnet communications is that BACnet broadcast messages on any IP network (subnet) are used very infrequently, so their propagation should not cause any problems. So, care must be taken on all IP networks with BBMDs to prevent overwhelming the network with broadcast messages. Where broadcasts cannot be minimized, the use of another strategy, such as rearranging the subnets, should be examined.
Some other aspects of BBMD broadcasting are:
• An Insight workstation that acts as a BBMD for a subnet must have a fixed IP address.
• Every IP subnet with BACnet/IP devices must have a single BBMD so that broadcasts from the BACnet/IP devices on one subnet can reach the BACnet/IP devices on the other subnets.
Only 1 BBMD should be configured per IP subnet. If more than 1 BBMD is active on a subnet it will cause the BACnet network to fail. If there is an existing network that is being integrated into, ask the third-party technician, customer, or IT dept if a BBMD is already active on the network.
• Each BBMD has a Broadcast Distribution Table, which lists all the BBMDs, including itself, on the IP WAN. This table must be identical in all the BBMDs of a particular IP WAN. This table also tells which broadcast method, one-hop or two-hop, is to be used for each destination network.
• The BBMD is not involved with non-broadcast communications (such as file transfers or reading and writing data values) between BACnet/IP devices. These communications are conducted directly.
• There can be only one BBMD per IP subnet. Having more than one BBMD per IP subnet will cause messages to be repeated in a loop.
One-Hop
Figure 24 shows the one-hop or directed broadcast method. Device A on Network 1 initiates a broadcast message that is received by the other BACnet devices and the BBMD on Network 1. The BBMD sends the broadcast message to Network 2. The message has a destination address which causes the IP router for Network 2 to broadcast the message to all of the BACnet devices on that network.
Chapter 4–BACnet Communications
96 Siemens Industry, Inc.
Figure 24. BBMD One-Hop (Directed Broadcast) Example.
Two-Hop
If the IP routers will not perform directed broadcasts, the two-hop or directed unicast method, shown in Figure 25 must be used. Device A on Network 1 initiates a broadcast message that is received by the other BACnet devices and the BBMD on Network 1. The BBMD on Network 1 sends a directed unicast message to the BBMD on Network 2. The Network 2 BBMD then broadcasts the message on its network.
BACnet Networking Technologies
Siemens Industry, Inc. 97
Figure 25. BBMD Two-Hop (Directed Unicast) Example.
BACnet Foreign Devices
BACnet foreign device registration allows access to a BACnet network’s broadcast messages from any BACnet device (workstation or field panel) having an IP connection but not having a BBMD or a multicast router on its subnet. Figure 26 shows an example of a BACnet foreign device workstation accessing a BACnet network’s broadcast messages. The BACnet foreign device workstation registers with the network’s BBMD and, thus, becomes a member of the BACnet/IP network. Then, for a specified period (time to live time), the BACnet foreign device workstation will receive forwarded broadcast messages from the BBMD when they occur.
Chapter 4–BACnet Communications
98 Siemens Industry, Inc.
Figure 26. BACnet Foreign Device receiving a Broadcast Message from a BACnet Network.
In addition,
Figure 27 shows that the BACnet foreign device workstation can send messages to a BBMD with which it is registered, so they can be broadcasted.
Figure 27. BACnet Foreign Device Sending a Broadcast Message to a BACnet Network.
BACnet Router vs. IP Router
BACnet Routers are devices that interconnect two or more BACnet networks to form a BACnet Internetwork. BACnet routers communicate via a single path–that is, all of the packets of a message take the same route to get to their destination. The BACnet networks that a BACnet router interconnects usually have different networking technologies. For example, a BACnet router may connect a BACnet Ethernet network to a BACnet/IP network. Table 27 lists some examples of BACnet routers.
APOGEE Communication with BACnet
Siemens Industry, Inc. 99
Table 27. Examples of BACnet Routers.
Manufacturer Model Number
Description
Cimetrics BR2 BACnet/IP Router–connects BACnet to IT network; connects BACnet/IP to BACnet/Ethernet or BACnet MS/TP or BACnet/PTP or BACnet/ARCNET; can act as a BBMD; allows access to BACnet/IP network via modem.
Cimetrics B6000 BACnet/IP to MS/TP Router–connects BACnet/IP to MS/TP; DHCP5; no mapping required.
PolarSoft® FreeRange™ Router
BACnet Router v1.12–routing between Ethernet 8802-3, BACnet/IP, PTP or MS/TP LANs; rugged enclosure; setup using built-in Web server.
IP Routers or IS Department Routers are devices that interconnect IP subnetworks into a single WAN. An IP Router determines the best path for a packet through the network when there are multiple paths. The IP Router is usually set up by the IS department to block IP broadcast messages, which in effect, blocks BACnet Broadcast messages. BBMDs are then used to propagate BACnet broadcasts to all IP subnets.
APOGEE Communication with BACnet
CAUTION: Before setting up a BACnet network, cyber security aspects need to be assessed (see chapter 14 “System Cyber Security Risk Assessment”). If possible, the BACnet network should be completely separate to the end users corporate network or at minimum a VLAN should be created for the BACnet network. Under no circumstances shall the BACnet network be directly connected to the end user’s IT infrastructure without protection.
Also see Chapter 14 on Cyber Security.
BACnet Client and Server Options
The BACnet option for Insight has two components–the BACnet Client Option and the BACnet Server Option. The BACnet option is a software add-on to Insight Revision 3.2 or later that is designed to provide communication with BACnet networks. The option allows you to monitor and command BACnet points from Insight Graphics and Point Commander, or from a third-party BACnet workstation. BACnet alarms appear in the alarm application. BACnet points can be used in dynamic trends. BACnet device network status appears in the System Profile. The BACnet Option’s two parts, the client and the server, can exist on separate workstations, or the same workstation.
5 Dynamic Host Configuration Protocol (DHCP) is a network protocol that is used to configure devices which are connected to a
network (known as hosts) so that they can communicate on an IP (Internet Protocol) network. It involves clients and a server operating in a client-server model. The DHCP server maintains a database of available IP addresses and configuration information. When the server receives a request from a client, the DHCP server determines the network to which the DHCP client is connected, and then allocates an IP address or prefix that is appropriate for the client, and sends configuration information appropriate for that client. DHCP servers typically grant IP addresses to clients only for a limited time interval. DHCP clients are responsible for renewing their IP address before that interval has expired, and must stop using the address once the interval has expired, if they have not been able to renew it.
Chapter 4–BACnet Communications
100 Siemens Industry, Inc.
The BACnet Option supports communication with all BACnet devices regardless of networking technology. However, the Insight workstation with the BACnet Option must be physically connected to either a BACnet/IP network or a BACnet on Ethernet network.
BACnet Client
Figure 28 shows an Insight workstation with the BACnet Client Option connected to a BACnet internetwork. When the Insight with the BACnet Client Option is enabled, it allows viewing of third-party BACnet devices, and their points, on the BACnet internetwork. The BACnet Client Option allows adding these BACnet devices to BACnet ALNs connected to that particular Insight in System Profile. BACnet networks, devices, and points are all imported into the Insight database. The BACnet Client Option makes the BACnet network look like a ALN, and BACnet devices look like field panels in the Insight workstation. Without having the BACnet Client Option enabled, other Insight workstations can access these devices and points as if they were APOGEE Automation System devices and points. The BACnet Client license controls two things: reading BACnet points on a BACnet ALN, and commanding BACnet points on a BACnet ALN.
Figure 28. Insight with BACnet Client Connected to a BACnet Network.
BACnet Server
A BACnet Server is any Insight workstation connected to a P2/Ethernet ALN that has points exported to a BACnet virtual network. The virtual network has a unique network number that identifies the APOGEE and/or pre-APOGEE field panels to the entire BACnet Internetwork.
APOGEE Communication with BACnet
Siemens Industry, Inc. 101
Figure 29 shows an Insight workstation, with the BACnet Server Option, connected to an APOGEE P2 ALN. The BACnet Server software is implemented as a Windows service. It allows BACnet devices to read and command points residing in APOGEE and pre-APOGEE field panels. This is because points residing in APOGEE and pre-APOGEE field panels are represented as BACnet points in the BACnet virtual network, accessible on the entire BACnet Internetwork. Likewise, APOGEE and pre-APOGEE field panels are represented as BACnet devices on the BACnet virtual network.
An Insight workstation with the BACnet Server option can only export the data of its own APOGEE P2/Ethernet ALN (and ALN/P3) trunks. So, if there are multiple Insight systems, each with their own APOGEE P2/Ethernet ALN (ALN/P3) trunks, then each of those Insight systems must have the BACnet Server option enabled.
Figure 29. Insight with BACnet Server Connected to an APOGEE ALN.
BACnet MS/TP
Firmware 3.1 or later was designed to create an extremely BACnet-compliant field panel. Features include support for RS-485 MS/TP ALN and RS-485 MS/TP FLN. Additionally, with firmware 3.2 or later, the PXC Modular controller can act as a BACnet/IP ALN to BACnet MS/TP ALN router. This allows the customer to configure BACnet networks for Ethernet and serial EIA-485 networks as needed (see Figure 33).
CAUTION:
Upgrading to Firmware 3.1 or later: Changes to the database will occur when upgrading BACnet MS/TP devices that are currently integrated using the BACnet MS/TP Driver with Firmware Revision 3.0, due to point naming changes.
Chapter 4–BACnet Communications
102 Siemens Industry, Inc.
BACnet MS/TP Performance Guidelines
The information under this heading was derived from a Technical Support News article dated January 2013 titled BACnet MS/TP Guidelines. This article was released from the Area Technical Specialist (ATS) Group and vetted by Technical Support.
Addressing and Settings
• Setting devices on an MS/TP network as Master or Slave depends on the situation at the jobsite. All instance numbers and network numbers must be unique. Devices could be wired with existing TSP wires, or with 1.5TSP, but you will get better performance out of the latter. New Jobs should always use 1.5TSP wire.
• Always set the field panel "MAC Address" in the MS/TP settings to zero – note, the default is 127 in firmware versions prior to 3.2.5. Setting it to zero assures that the field panel will start the token if it needs to be restarted. The following shows an example of the HMI command string that should be used to set the MAC address for BACnet field panels.
APOGEE Communication with BACnet
Siemens Industry, Inc. 103
>Point, Application, Time, Message, Cancel, System, passWord, Bye? s
>Diagnostics, Users, dSt, Bacnet, Error_msgs, Hardware, Text, Quit? h
>Fieldpanels, Ethernet, nodeNametable, Disks, Reportprinter, Licensemanager, Quit? f
>Log, Display, Add, dElete, Modify, Config, Filesys, Quit? c
>Hmi, Aln, deVice, Names, Fln, nEttype, hoaMap, Defaultlanguage, db_fiLe, Quit?f
>fln1, fln2, fln3, Wireless, MS/TP, flnType, Quit? m
>Enable MS/TP FLN (Y/N) : Y
>Enter baud rate : 38400---
>Network Number : 14---
>MS/TP Device Mac Address : 0--
>Keep Alive Poll Rate : 60---
>Discovery Poll Rate : 60---
Figure 30: Example HMI Command String for Setting MAC Address to Zero on BACnet Field Panels for MS/TP Networks.
Set master devices at an address equal or lower than 127 and set slaves devices at an address higher than 127. Master devices should be addressed starting with 1 and number them sequentially without any gaps. This will make your network more efficient.
If you set a slave BACnet TEC at an address lower than or equal to 127, then the only way to change it back to a master is to go out to the device, connect with WCIS and change it (you have to go to the device) - if you do it by using the address only, then you can change it from the front end, by changing the address. Even though the BACnet specification allows lower number (0-127) devices to be slaves, that is not the best practice. Keep Masters addressed at 127 and below and Slaves at 128 and above.
The max master setting should be left at the default of 127 for all of the Masters devices except the last (highest numbered) Master on your FLN. (Some branches do the highest two Master devices in case one Master device fails.) The setting for max master should be one higher than the highest Master MAC address. This stops the MS/TP network from "polling for master devices" higher than the max master all the way up to 127 (which could affect performance).
Chapter 4–BACnet Communications
104 Siemens Industry, Inc.
If a customer's FLN network consists of only Siemens BACnet devices - we could set all of the Siemens TECs/PTECs as slaves to get better performance. Setting the devices as masters still has the advantage of making the TEC data available through the BACnet Object Browser, so if there are just a few devices setting them all as masters might still be preferable. Also, if all of the devices are slaves we should set the first or second as master devices with a max master setting of 2 or 3 so that polling for masters stops there and does not try to find each master up to 127. (This does improve performance).
Point Pickup Modules (PPMs) should be addressed as the first devices on the FLN.
Since the PPMs, when set up as MASTER, support COV subscription (unlike our TECs) they are quick to respond to changes and you can see them update on the graphics faster than anything else.
For MS/TP network-numbering we are allowed to use network numbers up to 65534. If a panel has an Instance number in that range then we suggest using the panel's instance number as the MS/TP network number for the connected FLN. Any network numbers in the range and not currently in use are allowed, but numbering by the panel's instance number lets you know immediately where the TEC is attached to if you are looking at any reports that show the network numbers. If there is another standard in place, then of course you should use that!
Wiring
When wiring an MS/TP network where P1 devices are being replaced by MS/TP devices, the two allowable choices are to use the TSP wiring that exists at the facility, or rewire using the three wire 1.5TSP. You will get much better performance and you will be able to support a larger number of MS/TP devices with 1.5TSP wiring. 1.5TSP is preferred.
When wiring with 1.5 TSP wiring, the plus and minus (White/Black typically) wiring connects to all devices, the third wire (typically yellow) connects to all devices that have a three wire input (some third-party devices have only plus and minus) at the S pin or ? (equipotential ground) and at the field panel the yellow wire and a 100 ohm PTC thermistor are attached to the S pin. The other side of the thermistor is connected to earth ground. For devices that do not have the third wire connection point the yellow wire should be wire nutted together so that the rest of the devices further down the MS/TP network still have the same reference potential.
The last step in the wiring is to attach a 120 ohm resistor (End-of-Line Resistors) at each end of the MS/TP network (both ends). They should be connected from plus to minus at the device. This resistor knocks down the amplitude of the "bounce back" signal to prevent it from interfering with the normal communication signal. These "end-of-line" (EOL) resistors are not optional.
APOGEE Communication with BACnet
Siemens Industry, Inc. 105
MS/TP uses an RS-485 wiring standard. In reality you will see performance issues if you put more than 50 or so devices on an MS/TP FLN. This is not an electrical limitation, it is a limitation of the amount of communication that occurs on an FLN network (how much the devices talk). The more information that each device has to communicate, the longer it takes. You can have up to 32 "unit loads" on an MS/TP (RS-485) network. For Siemens FLN devices, our current TECs are rated at ⅛ load. Older versions may be full load or ¼ load. According to the RS-485 standard, this means that in theory, our FLN could support an electrical load of 256 devices if they were all ⅛ load devices, but it would never work on a real job. Refer to Table 24 for the practical limitations of the maximum number of MS/TP Devices per FLN Field Panel.
If you are going to have more than 32 MS/TP devices on an FLN, you MUST use either a PXC36 or a PXC Modular controller, and you must verify that the MS/TP devices are NOT full load electrical devices. If the MS/TP devices are full load electrical devices, or you are not sure, then you must also plan for 485 repeaters on the FLN.
Third-Party Devices
If you are able to separate third-party devices on their own MS/TP FLN, then do so. The issues will then be isolated to their FLN, and will not affect our devices. (Cost may prohibit this option) A good example of this is ABB Drives. They do not support Read Property Multiple (RPM), which means they are slow at sending data and can slow down an MS/TP network. In reality it is unlikely that you will be able to do this because of the additional costs involved.
Most third-party devices can be master only. ABB and a few others are exceptions as they can be set as Master or Slave. All third-party devices should be set as masters so that we can see and interact with them easily.
On an MS/TP network with other third-party vendors that need access to our TEC data, all TECs should be set as masters.
If you have third-party devices that send out broadcasts frequently on the subnets where the master devices reside, take the necessary steps to isolate the device or stop it from constantly broadcasting.
If you put third-party devices on the same FLN as our master devices, make the third-party devices the first devices on that FLN - 1, 2, 3, 4, etc. There are two reasons for this setup:
• If the third-party devices have a max master setting of 127, we may not be able to change it (this happens often in the field). If you put our devices at a higher
Chapter 4–BACnet Communications
106 Siemens Industry, Inc.
address, and we use a lower max master setting, then it wouldn't matter if theirs was set to 127.
• It seems that the field panel is more tolerant when token passing to the third-party devices than when our TECs are talking to third-party devices. If you put the third-party devices first then our TEC doesn't have to talk to it. The reason is, the TECs have a very short timeout and will mark a device as failed if it does not respond within the 40ms window. Field Panels wait longer.
Master or Slave
If the network is properly set up, having all slave devices will be slightly faster, but probably not enough that it will make a significant difference to the end user. Always set all MS/TP devices up as master devices, because that is the standard with almost all of the third-party vendors. This would retain the ability to discover the devices with the BACnet Object Browser or any third-party software, or devices that are added to the network later. 50% of the field people use master devices, 50% use slave devices.
RS-485 MS/TP ALN
Firmware Revision 3.1 or later supports RS-485 MS/TP ALN (see Figure 31).
Figure 31. Simple RS-485 MS/TP ALN Network.
RS-485 MS/TP ALN provides the following features/functionality:
• The MS/TP ALN is a token passing network with functional similarities to APOGEE P2 ALN.
• The field panel node address on an RS-485 MS/TP ALN is selectable: 0 – 254
• The field panel requires a unique BACnet Network ID for the ALN: 0 – 65534
• Baud rates are selectable: 9600, 19200, 38400, 76800, or 115200
− 76800 maximum if using a mix of Siemens and non-Siemens devices
− 115200 can be used if all devices are Siemens
APOGEE Communication with BACnet
Siemens Industry, Inc. 107
Only PXC Modular and PXC Compact support 76800 baud rate. For more information, see Product Announcement 700 - BACnet Field Panels on Firmware Revision 3.1.
• The field panel ALN is a logical grouping of MS/TP nodes and IP nodes
• The IP nodes are accessed via a BACnet Router
BACnet MS/TP ALN Performance Considerations
Firmware Version 3.1 or later is required to support BACnet MS/TP ALN. The BACnet MS/TP ALN configuration is supported exclusively through the PXC Modular and select PXC Compact hardware (see PXC Modular and PXC Compact Series (Includes HOA) Configuration & Sizing Guidelines). The PXC Modular or PXC Compact 36 is required to support the BACnet MS/TP ALN, since the PXC Modular and PXC Compact 36 are the only APOGEE field panels that have simultaneous support for BACnet/IP ALN and BACnet MS/TP ALN. The PXC Modular and PXC Compact 36 therefore act as a router between BACnet/IP and BACnet MS/TP devices, objects, and properties, as specified by the BACnet standard.
The BACnet MS/TP ALN has the following performance considerations:
• In general, faster baud rates will increase performance on the network, so that 76.8Kbps will perform faster than 19.2Kbps, for example. However faster baud rates do increase sensitivity to RS-485 wiring guidelines. Every device on the network must support and be configured for the same baud rate.
• If devices on the BACnet MS/TP network are master devices, then set the MAX Master address equal to the highest address occupied with a physical device on the network, and do not skip addresses.
• Since Siemens devices resident on a BACnet MS/TP ALN are treated as field panels to be backed up and monitored by APOGEE Insight, network traffic between these devices and APOGEE Insight is heavy. This limits the number of devices that may productively reside on a single BACnet MS/TP ALN network to no more than 10 devices, depending on point counts and network activity. Network performance may drop significantly as Siemens field panels are added to the MS/TP ALN.
• Note that additional BACnet MS/TP ALN networks may be added without compromising network performance through an additional PXC Modular.
• Third party BACnet MS/TP devices may be added to a BACnet MS/TP ALN. Note that for best network performance, COV subscription should be supported and used by the third-party devices.
• Each additional device on a BACnet MS/TP network that is set-up as a master creates another device to pass the token, which takes time and decreases overall network response times.
Chapter 4–BACnet Communications
108 Siemens Industry, Inc.
All ALN devices must be MS/TP masters.
• There can only be a total of ten MS/TP ALN devices on an ALN, including the router.
In May 2011, a Technical Support News article titled BACnet MS/TP ALN Limitations stated that (BACnet) field panel firmware 3.1 and higher allows you to utilize BACnet MS/TP ALNs. When using a BACnet MS/TP ALN, there are three requirements:
1. PXC Modular or PXC Compact 36 are required to connect the BACnet/IP segment to the BACnet MS/TP segment.
2. A maximum of 10 Siemens field panels can be wired on a BACnet MS/TP segment.
3. A maximum of 10 Siemens field panels can be defined to a BACnet ALN.
For example, if you have two PXC Modular and two PXC Compact 36 field panels, and each has nine PXC compacts connected to the MS/TP ALN port, you would need to define four separate ALNs in your System Profile.
Consider every additional device on the MS/TP network as adding up to 1 second to the token pass response time. Token pass times may even exceed 1 second per node if COV is not supported by the device (such as BACnet TECs) and if the number of points in the device to be monitored is large (>100). Devices that are master devices and do not support COV, with a large point count will have the most negative impact on network performance and will limit the total number of devices on a single network.
There are adjustable parameters in BACnet MS/TP that can greatly influence the performance of the network. These parameters include the following:
• Max_Master, which is a parameter indicating the maximum master device object address that shall be passed the token. To maximize network performance, include only one address higher than the highest master device address in the token ring, and ensure sequential addresses. For instance, if there are 55 devices in a network, address the devices 0-54, with a max master address of 55.
• Max_Info_Frames, which is a parameter indicating the maximum number of information frames a node may pass before it must pass the token. In most cases for best performance, the proper setting is the field panel default setting of 20.
Advantages for products residing on BACnet MS/TP ALN • Maximum of 30 character point name support
• EIA-485 is inexpensive and easily managed
• Supports back-up and restore of database for Siemens field panel devices
• Supports third-party MS/TP devices
APOGEE Communication with BACnet
Siemens Industry, Inc. 109
Disadvantages for products residing on BACnet MS/TP ALN • Maximum of 10 Siemens field panel devices on MS/TP ALN. (This limitation is
only true for Siemens devices which are constantly updating the node table with synchronized data.) The 10 device limit does not apply to third-party BACnet MS/TP devices.
• All objects in device need updating, which creates additional network traffic vs. FLN
• Support for BACnet MS/TP FLN on a BACnet MS/TP ALN device is extremely limited and not recommended due to performance considerations.
• Supports Siemens BACnet TECs, but treated as MS/TP ALN level devices in system, which means certain FLN functions are not supported: initial values, global commands, drag and drop FLN reports.
A disadvantage for a TEC on an ALN is low performance due to more traffic. Better performance can be gotten on a FLN.
RS-485 MS/TP FLN
Firmware Revision 3.1 supports RS-485 MS/TP FLN and provides the following features/functionality:
• The MS/TP FLN is similar to the APOGEE P1 FLN but has other unique features
• Unlike P1, the field panel has a node address on the MS/TP FLN: 0 – 254 (128 – 254 are reserved for slave devices)
• The field panel requires a unique BACnet Network ID for the FLN: 0 – 65534
• Baud rates are selectable: 9600, 19200, 38400, 56800, 76800
Chapter 4–BACnet Communications
110 Siemens Industry, Inc.
Figure 32. Example Firmware 3.1 or Later MS/TP Architecture.
BACnet MS/TP FLN Performance Considerations
Firmware Version 3.1 or later is required to support BACnet MS/TP FLN configuration (not including the BACnet MS/TP Integration Driver discussed above). The BACnet MS/TP FLN configuration is supported through the PXC Modular with the FLN expansion module, PXC Compact with FLN port and FLN license, Power MEC with FLN, and Open Processor. With Firmware Version 3.1, the FLN may be configured in the field as either a BACnet MS/TP FLN or P1 FLN. When configured for BACnet MS/TP FLN, physical FLN 1 port is used for communication and all other FLN ports are deactivated.
CAUTION:
The Power MEC is now retired but is still sold on the repair parts (Rparts) program until October 1, 2017. Refer to POA-001.
The BACnet MS/TP FLN has the following performance considerations:
• In general, faster baud rates will increase performance on the BACnet MS/TP network, so that 76.8Kbps will perform faster than 19.2Kbps, for example. However faster baud rates do increase sensitivity to RS-485 wiring guidelines. Every device on the network must support and be configured for the same baud rate.
• BACnet MS/TP devices resident on a BACnet MS/TP FLN are treated as FLN devices with Point Teams automatically created in the field panel. The Point
APOGEE Communication with BACnet
Siemens Industry, Inc. 111
Teams created are intended to optimize operations with application specific devices, such as Siemens BACnet TECs.
• Siemens BACnet TECs are supported by the field panel and APOGEE Insight with initial values support, and drag and drop reports.
• Each additional device on a BACnet MS/TP network that is set-up as a master creates another device to pass the token, which takes time and decreases overall network response times. Consider every additional node on the MS/TP network as adding 1 second to the token pass response time. Token pass times may exceed 1 second per node depending on the support of COV and the number of points monitored. Loading a FLN with the maximum of 96 devices, response times due to token pass may be approximately 90 seconds.
In June 2012, a Technical Support News article written by Bryan Spegel titled Maximum Number of TECs per FLN per Field Panel contained practical limits on the number of TECs that can be put on a BACnet MS/TP FLN. This information is denoted in Tables 23 and 24 below.
Table 28: Maximum Number of MS/TP Devices per FLN Field Panel.
Field Panel Number of FLN Ports
Recommended Number of TECs
per FLN for Typical
Expected Performance
Recommended Number of
TECs per Field Panel for Typical
Expected Performance
Specified Maximum Number of
BACnet MS/TP TECs
per FLN
PXC 16 and PXC 24 1 32 32 32
All other BACnet Field Panels
1 50* 50* 96
* These numbers take into account the performance considerations in Table 25.
Table 29: BACnet MS/TP ALN Performance Considerations.
Performance Factor Criteria Impact to Performance
Master devices on MS/TP FLN All devices on MS/TP FLN are set-up as Master Devices
Master sets token passing which can influence performance if token ins delayed due to high point counts in devices, or inefficient network set-up. Token is passed from device to device based on MAC address, so the more devices, the longer the time necessary to pass token from first device to last device.
Max Master Setting if Master Devices on MS/TP FLN
Max Master Setting sets maximum address to be used in token pass
Set Max Master to address (MAC address) one more than highest
Chapter 4–BACnet Communications
112 Siemens Industry, Inc.
Performance Factor Criteria Impact to Performance network. address used on MS/TP FLN
network. Unused addresses (including unused high addresses, low addresses, or skipped addresses) in token pass networks waste bandwidth and creates inefficient performance. Avoid skipping addresses on MS/TP networks and set Max Master in field panel as described.
If MS/TP devices are set to slave devices, be sure to set Max master to “0”.
Slave Devices on MS/TP FLN Devices on MS/TP FLN are set-up as Slave Devices
Slave enables polling which sets master device as poll master and is always in charge of discussions to MS/TP devices. The higher the number of devices, the longer it takes to poll the entire network of devices.
Baud Rate on MS/TP Network The network speed is referred to as baud rate and must be consistent for every device on a single MS/TP network and consists of the following speeds, lowest speed to highest speed: 9.6Kbps, 19.2Kbps, 38.4Kbps, 76.8Kbps (115.2Kbps is supported by certain devices, including PXC controllers).
In general, faster baud rates perform faster token passing and/or polling rates. The recommended baud rate for good performance is 38.4Kbps. 19.2Kbps is universally supported by all BTL approved MS/TP devices. Note that 76.8Kbps baud rate must be wired per EIA-485 networking rules to be effective, including three wires for communication and proper device terminations.
Poll rate setting in PXC field panels Poll rate is the frequency the PXC field panel polls the MS/TP network.
Make changes for poll rate at Insight where possible to filter changes to the entire system.
Set the poll rate to as low as 10 seconds for field panels with 3.2.3 firmware and later. For previous versions of firmware (3.1, 3.2, and 3.2.2) set poll rate to as low as 20 seconds. The faster poll rate will speed performance; however, it increases risk of network problems if devices are inefficiently set-up, configured, or have other inefficiencies such as large numbers of points used in applications.
Number of MS/TP FLN network device points used in Insight and/or PXC field panel applications
Number of MS/TP points used in PPCL, trend, schedule, and event enrollment applications impacts due to points being read for used in applications.
The larger the number of points per device used in PPCL, trend, schedule, and event enrollment applications, the larger the time requirement for the network to
APOGEE Communication with BACnet
Siemens Industry, Inc. 113
Performance Factor Criteria Impact to Performance update information.
• Each additional device on a BACnet MS/TP network that is set-up as a slave creates another device to poll, which takes time and decreases overall network response times. Network performance is inversely related to the number of devices on the MS/TP network, especially if COV is not supported by the MS/TP devices (such as the case with current Siemens BACnet TECs). Consider every additional node on the MS/TP network as adding 1 second to the poll time which impacts overall response time. Response times may exceed 1 second per node depending on the number of points monitored. Loading a FLN with the maximum of 96 devices, response times due to polling may be approximately 90 seconds.
• In general, expect that BACnet MS/TP FLNs will perform slower than P1 FLNs due to:
− Increased communication requirements for BACnet MS/TP compared to P1
− Lack of COV support in many BACnet MS/TP devices (including current Siemens BACnet TECs)
− Token passing when MS/TP devices configured as masters require additional communication time
− High volume of devices on single physical network which adds to communication time.
Despite the significant increased speed of the BACnet MS/TP baud rate over the P1 baud rate, the actual communication response is slower due to the factors cited above.
There are adjustable parameters in BACnet MS/TP that can greatly influence the performance of the network. These parameters include the following:
• Max_Master, which is a parameter indicating the maximum master device object address that shall be passed the token. To maximize network performance, include only one address higher than the highest master device address in the token ring, and ensure sequential addresses. For instance, if there are 55 devices in a network, address the devices 0-54, with a max master address of 55.
• Max_Info_Frames, which is a parameter indicating the maximum number of information frames a node may pass before it must pass the token. The default setting is “20”; this is also the recommended setting. Advantages for Products Residing on BACnet MS/TP FLN
Chapter 4–BACnet Communications
114 Siemens Industry, Inc.
• BACnet TEC Network performance optimized through auto point team creation for each unique application
• Best performance when number of unique point team applications are minimized (many devices use same application)
• Initial values supported
• Global commanding supported
• Drag and drop reporting supported
• Max. of 99 devices on MS/TP FLN - based on 1/4 load SBT BACnet TEC devices
• EIA-485 is inexpensive and easily managed
• Supports third-party MS/TP devices
• One wire run
Disadvantages for Products Residing on BACnet MS/TP FLN • Maximum of 12 character point name support (same as P1 FLN)
• Alarms require virtual point residing in field panel, since BACnet TEC does not support Notification Class
• No back-up and restore of database to mass storage device (workstation)
• PXC Compact resident on BACnet MS/TP FLN will look like third-party device to Insight
• Only one port (#1)
• No ALN devices can be on it
BACnet MS/TP FLN Design Considerations • Actual number of devices will be negatively impacted with slow responding
third-party devices and higher load (½ load and higher) devices
• Proprietary objects and properties are not supported on BACnet MS/TP in 3.1 firmware, only supported in the BACnet MS/TP Driver
• Number of devices is limited by performance expectations, as the larger the number of devices, the slower the performance
• Number of devices is limited by performance expectations, as the larger the number of unique point team applications, the slower the performance
• BACnet MS/TP ALN devices are extremely limited in BACnet MS/TP FLN support; always use BACnet/IP for device managing BACnet MS/TP FLN as general rule.
APOGEE Communication with BACnet
Siemens Industry, Inc. 115
BACnet Driver for Firmware
The BACnet Driver provides communication between the APOGEE Automation System and BACnet MS/TP or BACnet/IP devices. The BACnet Driver is loaded into PXC Modular or PXC Compact (for proprietary 2.x firmware or standard firmware 3.1 or later). The driver communicates with the Insight software, other APOGEE field panels and controllers, and the BACnet MS/TP or BACnet/IP devices. See Figure 33, Figure 34, Figure 35, Figure 36, and Figure 36.
The BACnet Driver operates in two modes: BACnet MS/TP mode or BACnet/IP mode. Both modes are exclusive and cannot be used together at the same time.
• In BACnet MS/TP mode, the driver allows a physical connection to FLN 1 only.
− It can support up to 255 BACnet MS/TP devices, of which up to 126 of them can be masters.
− The actual number of BACnet MS/TP devices that the driver can support is dependent on the devices themselves, the number of points per device, and their electrical constraints.
• In BACnet/IP mode, the driver communicates through the Ethernet port with other BACnet/IP devices using FLN 6 as a virtual FLN. Theoretically, the driver can support up to 255 BACnet/IP devices; however, the actual number of BACnet/IP devices that he driver can support is dependent on the devices themselves, the number of points per device and the electrical constraints.
Chapter 4–BACnet Communications
116 Siemens Industry, Inc.
Figure 33. Typical BACnet Driver and APOGEE Automation System Integration with BACnet MS/TP Devices
(Firmware Revision 2.x).
Features and Benefits of the BACnet Driver The BACnet Driver can be loaded into PXC Modular or PXC-36 hardware. The driver is a microprocessor-based, multi-tasking platform designed for multi-system communication and control. The BACnet Driver communicates with Insight software or Desigo CC, other APOGEE field panels and controllers, and the BACnet system.
Through the Insight workstation, the BACnet points can be monitored and commanded. The BACnet points integrated into the APOGEE Automation System can be accessed by system applications, such as Powers Process Control Language (PPCL), scheduling, trending, and alarming.
APOGEE Communication with BACnet
Siemens Industry, Inc. 117
The BACnet Driver will not affect, in any way, the operating sequence or safeties as factory-programmed into the BACnet system.
Systems integration brings the powerful facility control capabilities of the APOGEE Automation System together with BACnet system. With the BACnet Driver, two unique features are available that are NOT available with standard APOGEE firmware 3.x: 1. Unique point names can be defined for BACnet points at the APOGEE Insight
workstation. 2. The APOGEE Insight workstation has ability to filter BACnet points used in
various Insight reports.
Integrating the BACnet points allows both systems to operate as a single system providing marked advantages in the following:
• Reduced operating and training costs.
• Increased employee productivity.
• Increased diagnostic capabilities to extend equipment life.
• Improved systems information and control.
• Maximized energy savings.
Chapter 4–BACnet Communications
118 Siemens Industry, Inc.
Figure 34: Typical BACnet Driver System Configuration with BACnet MS/TP Devices (Firmware Revision 3.x).
APOGEE Communication with BACnet
Siemens Industry, Inc. 119
Figure 35: Typical BACnet Driver System Configuration with BACnet/IP Devices (Firmware Revision 3.x).
Third-party BACnet devices and objects require that an application point map be programmed in the driver. Third-party devices must support BACnet MS/TP protocol as slave devices.
The major differences between the BACnet Driver and the 3.1 firmware with built-in BACnet MS/TP support are as follows:
• The Driver does not support auto point team creation, but rather relies on Application Builder, part of Commissioning Tool so that the user must manually create the applications. This allows the user to select and de-select points for monitoring which can have a positive impact on performance, and allows the user to change the point names to suit the user.
• The Driver operates best when all devices on the MS/TP network are slave devices, which allows the Driver to poll the devices fast and efficiently, and at the same time cache information in memory to serve Insight and other clients with the latest information about the devices quickly and efficiently.
• All information on the MS/TP network is visualized to third-party BACnet clients on the BACnet network as part of the Driver controller, not as individual devices. To Insight, however, the individual devices are preserved, and appear similar to TECs with the operations supported that are typical of TECs.
For more information about the BACnet MS/TP Driver see:
Hyperlinks are provided for the following product announcements based on their location on InfoLink.
Chapter 4–BACnet Communications
120 Siemens Industry, Inc.
• Product Announcement 638R2 – BACnet Field Panel Firmware Revision 3.0 and Insight Revision 3.7 or later BACnet Option Product Announcement 700 - BACnet Field Panels on Firmware Revision 3.1
• Product Announcement 697 - Integration Drivers Supporting Firmware 2.8.2 for PXC Modular
• BACnet MS/TP Driver Release/Upgrade Notes (126-983)
• BACnet MS/TP Driver Technical Specification Sheet (127-0954)
• BACnet MS/TP Driver Product Update (127-0157)
• BACnet MS/TP In Brief (127-1477)
BACnet TECs
The BACnet TEC communicates over the FLN trunk using the BACnet MS/TP protocol. BACnet TECs should be configured as slave devices to ensure optimal performance. For details on integrating BACnet TECs using the BACnet MS/TP Driver, see:
• BACnet MS/TP Driver Technical Reference (140-0428)
• Solution for the Siemens BACnet TEC Application Notes (140-0671).
Table 30 is a brief description of how the BACnet Field Panel revisions support FLN devices. For more detail, refer to the Release Notes on the various firmware revisions available from the hyperlinks on InfoLink for the various firmware revisions are given below.
Table 30. BACnet Field Panel Revisions and FLN Functionality.
APOGEE F/W Revision
Description
Rev. 2.6.2 (BACnet Early Edition)
Supports P1 FLN devices only (no BACnet TECs on the FLN)
Rev 3.0 Supports P1 FLN devices only (no BACnet TECs on the FLN) Rev 3.0 with MS/TP Driver Integrated solutions driver designed primarily for integration of third-party
BACnet products, but it also supports MS/TP FLN with BACnet TECs. All FLN devices (BTEC and third-party) are made to look like P1 TECs to the rest of the system such that the BACnet TEC subpoints have their database in the field panel to which they are attached.
Rev 3.1 Supports integration of third-party BACnet products and supports MS/TP FLN with BACnet TECs. Does not require MS/TP Driver.
APOGEE Communication with BACnet
Siemens Industry, Inc. 121
APOGEE F/W Revision
Description
Rev 3.2 Supports Algorithmic (Event Enrollment) Alarming for MS/TP FLN device points and other off-node devices that do not support the BACnet Event Enrollment object, such as certain third-party devices.
Supports PXC Compact 36, which can have up to 96 FLN devices on one RS-485 connection or split between two connections.
Per a Technical Support News article dated January 2013 titled BACnet MS/TP Guidelines, MS/TP uses an RS-485 wiring standard. In reality you will see performance issues if you put more than 50 or so devices on an MS/TP FLN. This is not an electrical limitation, it is a limitation of the amount of communication that occurs on an FLN network (how much the devices talk).
P1 FLN supports wireless field level network (WFLN) to allow use of wireless FLN TECs.
3.2.2 This firmware version featured the first release of the Field Panel Web Server. Other features and functionality enhancements included:
• PXM10T/S
• Unitary Equipment Controller (UEC) (for MS/TP only)
• MS/TP Point Pickup Module (PPM)
• USB Media Support
• New Panel Team Points
• Solutions to issues reported in the field
3.2.3 Firmware version 3.2.3 featured performance enhancements in the following areas:
• Field panel delays in processing COV’s from a MS/TP network
• UI ReadPropertyMultiple too big for third-party device
• Performance issues in MS/TP processing
• Need increased database discovery performance
Firmware version 3.2.3 also supported the following new features and functionality enhancements:
• Facility To Go
• SNMP (Simple Network Management Protocol)
• Remote Notification (Web Server)
• Current build identification
• Panel compatibility/synchronization status (Web Server)
• Solutions to issues noted in the field
Chapter 4–BACnet Communications
122 Siemens Industry, Inc.
APOGEE F/W Revision
Description
3.2.4 This firmware version was the first to be designed and tested and receive the BTL listing against the updated and more stringent ANSI/ASHRAE Standard 135-2008. When the APOGEE Field Panel Viewers and Editors files are uploaded into the panel, the following features and functionality are supported:
• Support for BACnet Create Trend Log service • Point Editor UI for Desigo CC • PPCL Editor UI for Desigo CC • TEC Editor UI for Desigo CC • TEC Subpoint Log, Commander, and Initial Values UI
for Desigo CC • Solutions to issues noted in the field
BACnet MS/TP Router
A third-party router can be used to provide communication between the BACnet/IP network and the BACnet MS/TP network. However, Firmware Release 3.1 replaces the need for such a router. See Figure 36. On the BACnet/IP network, there can be an Insight operator workstation and/or a third-party BACnet client (workstation or controller). BACnet MS/TP In Brief (127-1477) discusses the pros and cons of using a generic BACnet MS/TP router versus the APOGEE BACnet MS/TP driver. In general, the router provides more of a pure BACnet solution, but the driver integrates with the APOGEE Automation System more effectively.
BACnet TECs
When using a router, the BTEC looks like a third-party device, and all communications are purely BACnet. When using a router in an APOGEE Automation System, the BACnet MS/TP devices appear in System Profile as ALN/ALN third-party devices.
One of the downsides of using a router in an APOGEE Automation System is that virtual points must be created in the field panels to support alarms and trends. This is because with a router, the points on the BTEC are only in its own database and not in a field panel. The field panel only supports trend and alarms on points in its own database. The solution is to create virtual points in a field panel. The virtual points can then be trended and alarmed.
APOGEE Communication with BACnet
Siemens Industry, Inc. 123
Figure 36. BACnet Integration with BACnet MS/TP Router.
Physical Network Configurations
The BACnet Client and Server Option support BACnet communication over BACnet on Ethernet or BACnet/IP. Once properly connected, the Insight workstation can then communicate with BACnet devices on the entire BACnet Internetwork. Figure 37 through Figure 39 show three network configurations for the BACnet Client and Server Option.
Insight with Dedicated ALN on Separate MLN and BACnet Networks
The MLN and the BACnet ALN can be on separate networks connected to an Insight workstation with a dedicated ALN (Figure 37). Although using separate networks is optional, it can help when the system has heavy network traffic.
Chapter 4–BACnet Communications
124 Siemens Industry, Inc.
Figure 37. Insight with a Ethernet MLN, a Dedicated P2 ALN, and a BACnet ALN on Separate Networks.
One Insight workstation contains two network interface cards; one for connection with the BACnet ALN and the other for connection with the MLN. The BACnet Option must be configured as a BACnet Server for the third-party BACnet workstation to see the P2 devices and points. The BACnet Option must be configured as a BACnet Client for Insight to view the devices and points on the BACnet ALN.
Using 2 Network Interface Cards [NIC] can separate the ALN from the customers’ network if separate Ethernet infrastructure is deployed. This will add a considerable level of security for the end users network and should be recommended.
Insight with Dedicated ALN on a Common MLN/BACnet Network
An Insight workstation with a dedicated ALN can be connected to one Ethernet network supporting both the MLN and a BACnet ALN (Figure 38).
APOGEE Communication with BACnet
Siemens Industry, Inc. 125
Figure 38. Insight with a Dedicated ALN and a BACnet ALN.
One Insight workstation contains one network interface card for connection with the Ethernet LAN. The BACnet Option must be configured as a BACnet Server for the third-party BACnet workstation to see the P2 devices and points. The BACnet Option must also be configured as a BACnet Client for Insight to view the devices and points on the BACnet ALN.
Connecting the BAS network directly to the corporate network of the end user poses significant security risks is not recommended. If the network infrastructure hardware needs to be shared a separate VLAN needs to be set up for the BAS.
Chapter 4–BACnet Communications
126 Siemens Industry, Inc.
Insight with a Remote AEM ALN on a Common MLN/BACnet ALN
Figure 39 shows an APOGEE Ethernet Microserver (AEM) connecting a remote P2 ALN to the Ethernet. The AEM can be assigned to either the Insight workstation. The BACnet ALN is assigned to one of the Insight workstations with the BACnet option. The MLN and BACnet ALN share the Ethernet network. The remote ALN can also be an Ethernet ALN with Ethernet PXCs.
Connecting the BAS network directly to the corporate network of the end user poses significant security risks is not recommended. If the network infrastructure hardware needs to be shared a separate VLAN needs to be set up for the BAS.
Figure 39. Insight with a Remote AEM ALN and a BACnet ALN.
One Insight workstation contains one network interface card for connection with the Ethernet LAN. The BACnet Option must be configured as a BACnet Server for the third-party BACnet workstation to see the P2 devices and points. The BACnet Option must be configured as a BACnet Client for Insight to view the devices and points on the BACnet ALN.
APOGEE Communication with BACnet
Siemens Industry, Inc. 127
Insight with APOGEE BACnet Field Panels on a Common MLN/BACnet ALN
Figure 40 shows two Insight workstations with the BACnet Option connected to APOGEE BACnet field panels and third-party BACnet field panels, all on a Common Network. Communications between the Insight workstations with BACnet Option and the APOGEE BACnet field panels is via BACnet/IP. The APOGEE BACnet field panels and the third-party BACnet field panels can communicate with each other. The network also supports MLN communications between the two Insight workstations.
Connecting the BAS network directly to the corporate network of the end user poses significant security risks is not recommended. If the network infrastructure hardware needs to be shared a separate VLAN needs to be set up for the BAS.
Figure 40. Insight with APOGEE and Third-party BACnet Field Panels on Common Network.
Chapter 4–BACnet Communications
128 Siemens Industry, Inc.
One Insight workstation contains one network interface card for connection with the Ethernet LAN. The BACnet Option must be configured as a BACnet Client for Insight to view the APOGEE and BACnet third-party devices and points on the BACnet network.
APOGEE Communication with BACnet
Siemens Industry, Inc. 129
Insight with Routers Using BBMDs and Foreign Devices
Figure 41 shows an Insight Database Server, a PXC Compact and a third-party BACnet device acting as BACnet Broadcast Management Devices (BBMD), while an Insight workstation and a Siemens BACnet field panel are acting as BACnet foreign devices. This setup is an example in which there are IS department routers (IP routers) between the foreign devices and the subnets with the BACnet BBMDs. With this setup, BACnet/IP must be used.
Each Insight workstation that acts as a BBMD for a subnet requires a fixed IP address. BBMDs will work only with fixed IP addresses.
Figure 41. Insight with Routers Using BACnet Broadcast Management and Foreign Devices.
The Insight Database Server acting as a BBMD must have the BACnet Option. Its Broadcast Distribution Table must contain the IP address of all of the BBMDs in the BACnet network segment. The Foreign Device, Insight, and field panel are on subnets without BBMDs, so each of these foreign devices must register with a BBMD to receive broadcasts from the devices on all of the other subnets.
Chapter 4–BACnet Communications
130 Siemens Industry, Inc.
BACnet Network Communication Features
BACnet Broadcast Management Device Functionality
BBMD functionality can be implemented in an Insight workstation with the BACnet Option or in an APOGEE BACnet field panel. An Insight workstation is set up as a BBMD using the Cimetrics BACstac Routing Edition v4.x Properties dialog box.
Use the following steps to set up the workstation as a BBMD:
1. From the Start menu, click Settings, Network Connections. The Network Connections window displays.
2. Double-click Local Area Connection. The Local Area Connection Status dialog box displays.
3. On the General tab, click Properties. The Local Area Connection Properties dialog box displays.
4. Select Cimetrics BACstac(TM) Routing Edition v4.x Protocol in the scroll box and click Properties. (Select the Properties of the appropriate network interface card (NIC), if the computer has more than one.)
5. To complete the BBMD setup, see Setting Up Insight on a BACnet/IP Network in the Insight Getting Started Help.
A BACnet field panel is set up as a BBMD from the BACnet Field Panel Definition dialog box and the BBMD Table dialog box (Figure 42).
APOGEE Communication with BACnet
Siemens Industry, Inc. 131
Figure 42. Example BBMD Table for BBMD in IP Subnet 1.
The APOGEE Automation System supports both one hop BBMDs and two hop BBMDs simultaneously as follows:
• If the entry in the BBMD table has a 32 bit mask (255.255.255.255) then that specific entry in the table is two hop. The APOGEE Automation System forwards messages to a two-hop BBMD, and expects that two-hop BBMD to rebroadcast the message on its local subnet.
• If the entry in the BBMD table has less than a 32-bit mask (255.255.0.0), then that entry in the table is a one hop. The APOGEE Automation System sends a directed broadcast directly to the one-hop BBMDs subnet, and expects the one-hop BBMD to do nothing (no rebroadcast by the one-hop BBMD).
Two methods exist for a BBMD to distribute broadcast messages to remote IP subnets. The first method is to use IP directed broadcasts, which are also called one-hop message distribution. This method sends the message using a BACnet/IP address where the network portion of the address contains the subnet of the destination IP subnet, and the host portion of the address contains all 1's. While this method of distribution is efficient, it requires that the IP router serving the destination subnet be configured to support the passage of directed broadcasts.
Chapter 4–BACnet Communications
132 Siemens Industry, Inc.
Since not all IP routers are configured to pass directed broadcasts, a BBMD may be configured to send a directed message (UNICAST) to the BBMD on the remote subnet, called two-hop distribution. This method then transmits the message using the BACnet/IP broadcast address. The two hop method is the preferred method and most universally applied.
Foreign Device
An APOGEE field panel can be defined as a Foreign Device by selecting the Foreign Device button in the BACnet Field Panel Definition dialog box (brought up by clicking on the desired field panel in the Insight System Profile application). The Foreign Device Settings dialog box (Figure 43) allows activating the Foreign Device feature, entering the BBMD port and address to which the field panel is registered, and the time to live before re-registration is required.
Figure 43. Foreign Device Settings Dialog Box.
An Insight workstation can be defined as a foreign device. Setup is done in the BACnet/IP Port Properties dialog box. Access this dialog box by doing the following:
1. From the Start menu, click Settings, Network Connections. The Network Connections window displays.
2. Double-click Local Area Connection. The Local Area Connection Status dialog box displays.
3. On the General tab, click Properties. The Local Area Connection Properties dialog box displays.
4. Select Cimetrics BACstac(TM) Routing Edition v4.x Protocol in the scroll box and click Properties.
5. Select the Foreign Device tab for access to the Foreign Device Settings dialog box.
If more than one foreign device is needed on a segment, consider adding a BBMD instead. BBMDs give more functionality and expandability. For two or more devices on a segment, communications through a BBMD uses less bandwidth than if the devices were foreign devices. Additionally, new devices are easier to add to a segment with a BBMD.
APOGEE Communication with BACnet
Siemens Industry, Inc. 133
Cross-Trunk Communications
The Insight BACnet Client Option allows Insight and APOGEE P2/Ethernet field panels to read and command point-like objects in the BACnet devices (APOGEE 3.x field panels and third-party devices). Access in the other direction is not available. That is, the BACnet devices cannot access points in the APOGEE P2/Ethernet field panels without using the Insight BACnet Server Option. Thus, a BACnet device cannot subscribe to have COVs sent from a point in an APOGEE P2/Ethernet field panel.
Normally the Insight BACnet Server Option, which supports subscribing to COVs, is required if third-party BACnet network devices must access points on the APOGEE P2/Ethernet networks.
However, since APOGEE P2/Ethernet field panels can initiate actions in BACnet devices, sending COVs from an APOGEE P2/Ethernet point can be duplicated by commanding a BACnet point-like object to the value of the APOGEE P2/Ethernet point. For example, assume it is desired to send the value of the physical outside air temperature point, OAT, from an APOGEE P2/Ethernet PXC to a BACnet third-party device (Figure 44). An Analog Value Object, VIRTUAL_LAO, is created in an APOGEE BACnet 3.x PXC. A line of PPCL code in the APOGEE P2/Ethernet PXC sets the value of VIRTUAL_LAO equal to the OAT value. Then, the APOGEE P2 Ethernet PXC sends the point’s value to the BACnet device using conventional cross-trunk point command mechanisms. (The value of VIRTUAL_LAO is ultimately determined by its Command Priority Array.) To send this value to other devices on the BACnet network, COV subscription is used between BACnet panels. (For more information, see BACnet Network COVs section in this chapter.)
Figure 44. BACnet Receiving COVs from the APOGEE Automation System.
Chapter 4–BACnet Communications
134 Siemens Industry, Inc.
Figure 45 shows an example of how to command a BACnet point from the Insight Scheduling Application. The name of a BACnet Analog Value Object point, VIRTUAL_LAO, is entered into the Zone’s Command Table. When this point is commanded, the Insight cross-trunk service sends the command to this point in the BACnet 3.x PXC. PPCL code in the BACnet 3.x PXC sets a BACnet Command Object Present Value equal to the value of VIRTUAL_LAO. The Command Object will then execute its commands based on its new Present_Value.
CAUTION:
Watch for APOGEE Zone Command Table values of 0 (zero). The BACnet Command Object will not accept 0 (zero) for its Preset_Value. The BACnet Command Object will not accept 0 for it Present_Value. You may have to add 1 to the Virtual_LAO value in the BACnet panel PPCL code (Figure 45).
Figure 45. BACnet Receiving a Command from APOGEE.
See the SSTO section in Chapter 7–BACnet Scheduling for an example of how to use the APOGEE Zone mode sub-point to command mode PPCL in the BACnet 3.x PXC.
BACnet Network COVs
BACnet has a service called SubscribeCOV (see section 13.14 of the ANSI/ASHRAE Standard 135-2012) to send notifications of changes of value (COV) that may occur in a property of an object. The Unsolicited COV Subscription feature of APOGEE BACnet field panels sends COVs to a BACnet device even when the device does not ask for (subscribe to) COVs. This feature can be used for the following reasons:
• To send a COV to a third-party BACnet device that lacks the SubscribeCOV mechanisms
APOGEE Communication with BACnet
Siemens Industry, Inc. 135
• To send a COV notification message for an important system point, such as outside air temperature, that is likely to be wanted by all devices.
This feature is available only in SBT 3.x BACnet field panels. The Unsolicited COV Subscription List dialog box (Figure 46) is accessed in the Insight workstation from the Field Panel Definition dialog box by selecting the Unsolicited COV button. The button is grayed out for third-party field panels. Communication is limited to BACnet networks with the Insight BACnet Client Option. Use cross-trunk communication (see the Cross-Trunk Communications section in this chapter) to send an APOGEE P2/Ethernet device’s COVs to a BACnet network device. With the Insight BACnet Server Option, use BACnet Network Device registration for COVs.
Figure 46. Unsolicited COV Subscription List Dialog Box.
COV recipients can be selected by name or Instance Number, in which case the COV notification goes specifically to that recipient. Alternatively, a Global Broadcast can be chosen in which case it will be sent to all BACnet devices on the network. If Global Broadcast is chosen and there are IP routers on the network, the global broadcast messages will go through the BBMDs to traverse the IP routers.
Network Bandwidth Usage
APOGEE components do not add significant overhead to a TCP/IP network. Network usage is variable since it depends on the number of components on the network, network speed and architecture, and the activity occurring at the moment.
Chapter 4–BACnet Communications
136 Siemens Industry, Inc.
Trend collection tests conducted in the 2006 time frame at network data rates from 56K to 100 megabits per second have shown added network traffic to be less than 1% for all collections. Database downloads, database uploads, graphic updates, and multiple alarm displays on graphics and in alarm windows have given similar results. Thus, it is reasonable to expect that no burst traffic from an APOGEE BACnet system will generate significant network traffic.
Average network traffic (normal steady state conditions) will be significantly less than burst traffic.
Insight BACnet Option Security
The Insight BACnet Client and Server Option protects the APOGEE Automation System by disallowing file transfer (BACnet File Access Services), accepting only BACnet commands that are supported by the APOGEE Automation System, and allowing the user to select which APOGEE Automation points are available to BACnet devices.
For additional security we recommend that the customer’s IT department physically separates all network components of the BAS from the corporate network. At minimum a VLAN shall be setup for the BAS network. A VLAN uses encryption and other security mechanisms to ensure that only authorized users can access the BAS network and that the data cannot be intercepted on the ALN.
Network security in BACnet is optional. Clause 24 of the BACnet specification ANSI/ASHRAE Standard 135-2012 defines an optional security architecture for BACnet that provides peer identity, data origin, and operator authentication, as well as data confidentiality and integrity. Other aspects of communications security, such as authorization policies, access control lists, and non-repudiation, are not defined by this standard. Systems that require these functions may add them to BACnet by using the proprietary extensibility features provided for by this architecture, or by some other proprietary means. For more information on the network security features of BACnet, refer to clause 24 of the ANSI/ASHRAE Standard 135-2012.
Device Discovery
Discovery is a BACnet process that enables a device to find new devices on the network. The discovery process involves broadcasting Who-Is messages and listening to resulting I-Am messages (as well as other I-Ams from other processes and applications). For example, an APOGEE BACnet field panel broadcasts an I-Am message at startup (warm or cold) and anytime DHCP changes the IP address.
One way that the Insight workstation uses the device discovery is to enable it to populate the ALNs in the System Profile. Insight’s device discovery puts devices on specific ALNs based on criteria (filtering) established by entries in the BACnet Connection Settings dialog box (Figure 47). The devices that are found can be from a third-party or from Siemens.
APOGEE Communication with BACnet
Siemens Industry, Inc. 137
Figure 47. BACnet Connection Settings Dialog Box.
Device discovery is a manually triggered process. BACnet Enable Device Discovery (System Profile, Tools) must first be enabled (Figure 48). It is defaulted as disabled. Then, BACnet Global Broadcast Who-Is is selected. The System Profile tree then populates as devices respond with I-Am messages resulting from the broadcast Who-Is.
After the System Profile tree is built, known devices are automatically monitored in the background for problems. If a problem occurs with a specific device, it will be targeted with attempts to restore communication with it. This occurs with or without BACnet Enable Device Discovery being checked.
Chapter 4–BACnet Communications
138 Siemens Industry, Inc.
Figure 48. BACnet Enable Device Discovery Dialog Box.
Enable Device Discovery is defaulted to the disabled state because filter setups should be done first before device discovery. The recommended workflow is as follows:
1. Set up ALN filters using the Network Connection Settings dialog box. Filtering means defining which BACnet devices are on each ALN. For example, devices may be filtered by manufacturer–each ALN will contain devices from one particular manufacturer–or devices may be filtered by BACnet network number.
In engineering a BACnet system, a document should be created defining in which ALN each device (field panel) resides. This can be a simple table or Excel spreadsheet.
2. Enable Device Discovery and then Global Broadcast Who-Is. Insight’s Global Table Services then starts processing I-Am responses and putting devices in the proper ALN in the System Profile.
3. Use “Cloaking” to remove those field panels that shouldn’t be seen in the System Profile. Cloaking prevents discovery from re-adding the panels to System Profile.
Device Discovery may not put some BACnet devices anywhere due to peculiarities (or errors) in the filtering scheme. It is recommended to set up a catch-all ALN for these orphan devices. This will help avoid having lost devices and bring to light any filtering issues.
The catch-all ALN should have no restrictions (filtering) at all in the BACnet Connection Settings. The Device Discovery process searches the ALNs with the most restrictive filtering criteria first when attempting to put a newly discovered device onto a ALN. Then ALNs with fewer restrictions are considered. If the new device does not fit in any ALN with restrictions, it will be placed in the catch-all ALN.
APOGEE Communication with BACnet
Siemens Industry, Inc. 139
Some third-party field panels may not respond to the Who-Is messages sent out during device discovery. These devices can be added manually using the traditional System Profile methods for adding a device to a ALN. Such devices will often need to be added to APOGEE BACnet field panel address tables. Address tables are accessed through the BACnet Address Table dialog box. To display the BACnet Address Table dialog box, select BACnet Address Table on the System Menu.
Time Synchronization
The Insight software offers the option to synchronize the time of BACnet devices on a ALN. Some low-capability BACnet devices need to be told the time on a periodic basis. Also, if doing extensive trending, time synchronization is important when comparing the trend results of one field panel to those of another field panel.
Time synchronization for BACnet is not broadcasted. It is sent specifically to those devices on the ALN that have subscribed. The subscription list is called the Recipient List, and time synchronization is sent to each device on the Recipient List. APOGEE 3.x field panels are subscribed by default.
Time synchronization occurs once a day at 2:00 A.M. (configurable) or can be forced manually by clicking the Set Time button in the Building-Level Network Definition dialog box (Figure 49).
The synchronization time comes from the clock of the Insight workstation to which the ALN is assigned in the System Profile. In a system with multiple Insight workstations, each with their own ALNs, Windows time synchronization mechanisms must be used to synchronize all of the workstations and, thus, the whole system. For example, the workstations can be synchronized to an atomic clock or to one Windows server.
Chapter 4–BACnet Communications
140 Siemens Industry, Inc.
Figure 49. Building Level Network Definition Dialog box–Time Synchronization.
Time synchronization is set up for devices on an ALN through the Building Level Network Definition Dialog box from System Profile. The Recipients button opens the Time Synchronization Recipient List dialog box (Figure 50) in which three choices are given for each device:
• Do not Sync
• sync to Local Time
• sync to UTC Time
APOGEE Communication with BACnet
Siemens Industry, Inc. 141
Figure 50. Time Synchronization Recipient List Dialog Box.
Chapter 4–BACnet Communications
142 Siemens Industry, Inc.
Example BACnet Job (Internetwork)
Figure 51 shows an example of a BACnet Job (Internetwork). BACnet is communicating on four segments–each with a different networking technology: MS/TP, BACnet/IP, ARCNET and Ethernet. BACnet routers interconnect the different technologies. An Insight with the BACnet Option is functioning as both a BACnet Client and Server.
Figure 51. Example BACnet Internetwork (Job).
System Configuration
Each physical segment is identified with a unique BACnet Network Number, 1 through 4. These are arbitrary numbers, unique job-wide, assigned by the person configuring the BACnet routers.
Each BACnet device is user-assigned a BACnet Device ID (Device Instance Number) that is unique job-wide. The BACnet Device Number can be 0 through 4,194,303 (222 – 1).
Although a BACnet device does not know its own network number, each BACnet device is uniquely located by its BACnet Address:
BACnet Address = BACnet Network Number + MAC Address
APOGEE Communication with BACnet
Siemens Industry, Inc. 143
The MAC Address is programmed into the network interface of each BACnet device. Depending on the network technology, the MAC address may be user-configurable or may be permanently set at the factory. The structure of the MAC address varies based on the networking technology:
• For MS/TP, the MAC address is a single byte (0 through 7).
• For BACnet/IP, the MAC address is the IP address + 2 bytes for the UDP port (usually 47808). These 2 bytes equal 186.192 in decimal or BA.C0 in hexadecimal. Therefore, the MAC address for a device in Subnet 3 can be represented in decimal as 136.157.38.29.186.192, or in hexadecimal as 88.9D.26.1D.BA.C0. For a BACnet Field Panel, the BACnet MAC address is displayed in the BACnet Field Panel Definition dialog box either in Decimal (Figure 52) or Hexadecimal (Figure 53).
• For ARCNET, the MAC address is 4 bytes.
• For Ethernet, the MAC address is 6 bytes.
Figure 52. BACnet Field Panel Definition Dialog Box with Decimal MAC Address.
Chapter 4–BACnet Communications
144 Siemens Industry, Inc.
Figure 53. BACnet Field Panel Definition Dialog Box with Hexadecimal MAC Address.
There are three BBMDs on the BACnet/IP network–one on each IP subnet. On this job the BACnet/IP segments have subnet masks of 255.255.255.0.
The BBMDs move BACnet broadcast messages through the IS department routers. BBMDs are only used on BACnet/IP networks. The domain of the BBMD is a single BACnet/IP network (network number). Therefore, hypothetically, if (in Figure 51) BACnet Network No. 4 were BACnet/IP instead of Ethernet, its BBMDs would not be in the BBMD table of Network No. 2 and vice versa.
BBMDs provide more functionality and expandability than multiple foreign devices on a segment. Foreign devices each use bandwidth, so the more foreign devices, the more bandwidth that is used. BBMDs are more efficient: One BBMD message occurs instead of multiple foreign device messages. Also, additional devices hookup easily (no foreign device setup).
Running the LocalNET Configuration Utility
To implement both the Insight BACnet Client and Server required in this example, the LocalNet Configuration Utility must be run. This is more than a utility–it is an essential step in setting up the Insight BACnet Client and/or Server options.
APOGEE Communication with BACnet
Siemens Industry, Inc. 145
The LocalNet Configuration Utility is located under Insight in the Windows Programs menu (Figure 54). Full details of its use are covered in the Getting Started documentation. After installing Insight software and rebooting, select both or either of the BACnet Client and/or the BACnet Server.
Figure 54. Running the LocalNET Configuration Utility.
Setting Up Insight with a Virtual BACnet Network
For cyber security reasons Siemens recommends thatthe BAS network is completely separate and isolated from the corporate network. If this cannot be done on a hardware basis, it is strongly recommended to install the BAS on a VLAN.
Chapter 4–BACnet Communications
146 Siemens Industry, Inc.
The BACnet Server Option must be set up to export P2 (ALN) points to a BACnet virtual network. The process to set up the virtual network is documented in the Getting Started documentation. It is similar to choosing the network interface card (NIC) on the computer through Windows Start, Settings, and Network Connections. Working down from the Local Area Connection Status dialog box (Figure 55) through the Local Area Connection Properties (Figure 56), the virtual network is added to the Port Table in the Cimetrics BACstac™ Routing Edition v4.x Protocol Properties (Figure 57 and Figure 58). Unlike a physical network, a virtual network is not related to a NIC. See the entry for Port ID 2 in Figure 57.
Figure 55. Local Area Connection Status Dialog Box.
APOGEE Communication with BACnet
Siemens Industry, Inc. 147
Figure 56. Local Area Connection Properties Dialog Box.
Figure 57. Cimetrics BACstac™ Routing Edition v4.x Protocol Properties.
Figure 58. Virtual Port Properties Dialog Box.
Chapter 4–BACnet Communications
148 Siemens Industry, Inc.
When selecting a Network Number for the Virtual Network, make sure to use a number NOT used by any other BACnet Network on the job.
The Insight workstation must be rebooted to make the virtual network settings take effect.
When a BACnet device starts up, it typically does a global Who-Is broadcast to discover the other devices on the network. A Who-Is expects to receive an I-Am response (Device Instance Number + BACnet Address) from other devices. A BACnet device also may do an I-Am on startup, to advertise its presence on the network. After the global broadcasts, device communication is usually just device-to-device.
APOGEE BACnet Field Panel
Siemens Industry, Inc. 149
Chapter 5–BACnet Field Panel Chapter 5 describes the features and functions of the APOGEE BACnet field panel as well as the firmware used to operate it. The APOGEE BACnet field panel is a combination of the hardware platform and the firmware that supports BACnet features. This chapter includes the following topics:
• APOGEE BACnet Field Panel – how it differs from traditional non-BACnet (Protocol 1 or 2) field panel communication and data handling
• Firmware – revisions of firmware required to support various levels of BACnet functionality
• HMI
APOGEE BACnet Field Panel The APOGEE BACnet field panel is based on the APOGEE Ethernet field panel platform. The APOGEE BACnet field panel uses a combination of standard BACnet objects and services and proprietary functions to implement functions not covered by the BACnet standard.
APOGEE P2 and BACnet Comparison APOGEE field panel firmware was configured to support the BACnet protocol when:
• Both the BACnet and APOGEE protocols have a function, the BACnet function (or version of the function) is implemented.
• APOGEE provides a function that the BACnet protocol does not support, the APOGEE function is retained as long as it does not interfere with BACnet functionality.
This approach to BACnet implementation retains much of the APOGEE feature set while providing 100% compatibility with the BACnet protocol.
Table 31 below provides a comparison of the point and application differences between APOGEE P2 and BACnet field panels.
Table 31: Comparison of the Point and Application Differences Between APOGEE P2 and BACnet Field Panels.
System Function
APOGEE P2 (RS-485 or Ethernet)
APOGEE BACnet
Names • 30-character limit and unique point names system-wide
• 30-character limit
• Unique point names within devices are required.
• Unique point names system-wide is not technically required. (Insight DOES require uniqueness)
Chapter 5–BACnet Field Panel
150 Siemens Industry, Inc.
System Function
APOGEE P2 (RS-485 or Ethernet)
APOGEE BACnet
Integrated BACnet Device Names
• Not supported • 30-character point name limit OR a combination of Device/Object ID (Encoded Name)
Alarming • Standard Alarming
• Enhanced Alarming
• BACnet Alarming
• Notification Classes
• Event Enrollment (3.2 or higher panel firmware)
• No Enhanced Alarm functions with alarm prioritization or escalation
• Time delay and Deadband alarm characteristics are standard features
Trending
• Trend by time interval and/or COV
• Trend start/stop by trigger point condition (0,1, or 2)
• Automatic Trend Collection
• Trend by time interval and/or COV
• Configuration, creation, and deletion of BACnet trend log objects from Insight
• Remote trending
• Automatic Trend Collection
Equipment Scheduling
• Scheduling accomplished through zones and events coordinated with PPCL.
• Zone command table for individual point commanding.
• Scheduling accomplished through a mode point coordinated with PPCL
• Command Objects for individual point control
• Creation, deletion, configuration and editing of Schedules, Calendars, and Command Objects from Insight
• Schedule objects are created inside of each Panel
Field Panel Database Upload/Download
• Field panel upload/download
• Field panel upload/download
• Backup and restore third-party field panel devices
Field Panel Hardware
All APOGEE field panels that have the Ethernet hardware can be upgraded to BACnet firmware. The BACnet firmware supports the same physical point IO and FLN devices as the non-BACnet Ethernet field panel.
APOGEE BACnet Field Panel
Siemens Industry, Inc. 151
In addition, BACnet Programmable TEC’s (PTEC’s) have been introduced since this guide was last published (in 2007). BACnet Programmable Terminal Equipment Controllers (PTEC) are application-specific equipment controllers designed to provide stand-alone Direct Digital Control (DDC) for various types of HVAC terminal units. Table 32 lists the PTEC controllers orderable at the time of this writing. For more information, refer to the BACnet Programmable TEC (PTEC) User Manual, the BACnet Programmable TEC (PTEC) Technical Reference or the BACnet Programmable TEC (PTEC) Configuration and Sizing Guidelines documents hyperlinks to these documents posted on InfoLink.
Chapter 5–BACnet Field Panel
152 Siemens Industry, Inc.
Table 32: BACnet PTEC Controllers Orderable at this Writing.
Controller Type Product No. Application Type Application No. 6 Firmware Revision
BACnet PTEC Terminal Box/VAV Controller
550-495P VAV pressure independent
6520, 6521, 6522, 6523, 6524, 6525, 6526, 6527 (6587)
BV40 Rev 2.0.0.19
BACnet PTEC VAV with Series Fan and 3-Stage Electric Heat Controller
550-492P VAV pressure independent
6557 (6599) BH40 Rev 2.0.0.21
BACnet PTEC Unit Conditioner (Fan Coil) Controller
550-496P VAV pressure dependent Fan
Coil Unit
6540, 6541, 6550, 6551, 6552, 6553, 6554 (6591)
BF40 Rev 2.0.0.19
BACnet PTEC Unit Vent Controller
550-493P Unit Ventilator 6575, 6576, 6577, 6578, 6579 (6595)
BE40 Rev 2.0.0.20
BACnet PTEC Heat Pump Controller
550-490P Multi-Stage Compressor
6583, 6584 (6590)
BK40 Rev 2.0.0.20
BACnet PTEC Extended I/O Controller
550-491P I/O Expansion Module
6596
BI40 Rev 2.0.0.17
BACnet PTEC Dual Duct Controller
550-497P Two Air Velocity Sensors
6565, 6566, 6567, 6568, 6569
BD40 Rev 2.0.0.1
BACnet PTEC Constant
550-498P Electronic Output
6560, 6562, 6563 BC40
Volume Controllers
Rev 2.0.0.20
The following table from a draft copy of the BACnet Network and Troubleshooting Manual 7 provides a quick reference for hardware supported by BACnet Firmware and the ALN and FLN options supported by each type of hardware.
6 Application numbers in parentheses are slave mode applications.
APOGEE BACnet Field Panel
Siemens Industry, Inc. 153
Table 33: Quick Reference for Hardware Supported by BACnet Firmware and the ALN and FLN Options. Field Panel ALN FLN
PXC Compact 24 PXC Compact 16
BACnet/IP Optional depending on model – requires FLN license
P1 or BACnet MS/TP (Configurable FLN: controller supports either one P1 FLN or one BACnet MS/TP FLN).
Supports up to 32 BACnet or P1 TECs on single FLN network.
BACnet MS/TP BACnet MS/TP FLN or P1 FLN not supported in combination with BACnet MS/TP ALN on PXC Compact.
PXC Compact 36 BACnet/IP Optional FLN – requires license for PXC 36 BASE, or included with PXC 36 with FLN and TX I/O support.
P1 or BACnet MS/TP (Configurable FLN: controller supports either two P1 FLNs or one BACnet MS/TP FLN).
Supports up to 96 BACnet TECs on single FLN network, or up to 96 P1 TECs among two FLN networks (i.e., up to 48 on each of two FLN networks). Always match electrical and performance requirements to number of devices on FLN.
When FLN is configured for BACnet MS/TP, then it also supports BACnet MS/TP ALN.
BACnet MS/TP Optional FLN – requires license for PXC 36 BASE, or included with PXC 36 with FLN and TX I/O support.
P1 or BACnet MS/TP (Configurable FLN: controller supports one P1 FLN or one BACnet MS/TP FLN).
PXC Modular BACnet/IP and/or BACnet MS/TP
Three P1 FLNs or one BACnet MS/TP FLN (Configurable).
Power Open Processor BACnet/IP Three P1 FLNs or one BACnet MS/TP FLN (Configurable)
Power MEC BACnet/IP Optional depending on model: Three P1 FLNs or one BACnet MS/TP FLN (Configurable)
BACnet/IP Lon-Talk
CAUTION:
The Power MEC is now retired but is still sold on the repair parts (Rparts) program until October 1, 2017. Refer to POA-001.
7 At the time of this writing, this manual is not yet published or posted anywhere on the Siemens Intranet.
Chapter 5–BACnet Field Panel
154 Siemens Industry, Inc.
The PXC Compact 36 includes (2) RS-485 connections which are marked “B” and “A”.
ALN Connection
“B” “A”
BACnet/IP MS/TP ALN MS/TP FLN
BACnet/IP P1 FLN (FLN2)
P1 FLN (FLN1)
BACnet MS/TP
ALN FLN
HMI prompt? S, H, F, C, A, M, M (System, Hardware, Fieldpanels, Config, Aln, MS/TP, Modify)
Some of the BACnet controllers can reside on BACnet IP ALN, BACnet MS/TP ALN or BACnet MS/TP FLN.
PXC-24 Unitary Equipment Controller PXC Compact 16 PXC Compact 24
Maximum Number of MS/TP Devices per Network
The maximum number of MS/TP devices allowed per network is listed in Table 34.
Table 34: Maximum Number of MS/TP Devices per Network. Field Panel Number of
MS/TP FLN Ports
Max Number of MS/TP device
per FLN
Number of MS/TP ALN
ports
Max Number of MS/TP ALN Devices per
ALN
PXC Modular 1 96 1 10
PXC Compact 36 1 96 1 10
PXC Compact 16/24 1 32
Power MBC/Power MEC
1 96
CAUTION:
The Power MBC and Power MEC is now both retired but both are still sold on the repair parts (Rparts) program until October 1, 2015 (for the MBC) October 1, 2017 (for the MEC). Refer to PA-669R and POA-001, respectively.
All Programmable TEC and BACnet TEC (Rev Bx20 series) are 1/8 load.
Siemens Industry, Inc. 155
Field Panel Features
APOGEE BACnet field panels retain much of the functionality of APOGEE non-BACnet field panels. Some of these functions include:
• User Accounts and Access Control
• Global Data Replication
• Point Teams
• PPCL Programming Language
• Database upload and download
• Support of P1 FLN devices
• HMI menus and prompts
Where APOGEE and BACnet are incompatible, such as in network management and scheduling, new generic BACnet applications replace their non-BACnet counterparts.
APOGEE BACnet Firmware Compatibility with Insight
Table 35 shows the BACnet firmware revisions that are compatible with various versions of Insight or Commissioning Tool. This information is taken from the Firmware Revision 3.2.4 Release Notes, posted on InfoLink.
Footnote c at the bottom of Table 35 indicates that an XML file or registry update is needed to provide the capability for some earlier Insight® revisions to communicate with the field panel and to back up and restore the database.
Table 35: APOGEE BACnet Firmware Revision Compatibility with Insight or Commissioning
Tool Versions.
Insight/Commissioning Tool Revision
3.12 3.11c 3.11 3.10 3.10b,c 3.9.1c 3.9c 3.8.1 3.8 3.7
BACnet Field Panel Model and Product Number
APOGEE Firmware Revision
PXC Modular Series (PXME8) PXC00-E96.A, PXC100-E96.A
3.2.4
3.2.3
3.2.2
3.2
3.1
3.0.1
3.2.4
3.2.3
3.2.2
3.2
3.1
3.0.1
3.2.2
3.2
3.1
3.0.1
3.2.4
3.2.3
3.2.2
3.2
3.1
3.0.1
3.2
3.1
3.0.1
3.2.4
3.2.3
3.2.2b
3.2d
3.1 3.0.1
3.2.4
3.2.3
3.2.2b
3.2d
3.1
3.0.1
3.0.1 — —
8 PXME is the hardware platform for the PXC Modular.
Chapter 5–BACnet Field Panel
156 Siemens Industry, Inc.
Insight/Commissioning Tool Revision
3.12 3.11c 3.11 3.10 3.10b,c 3.9.1c 3.9c 3.8.1 3.8 3.7
BACnet Field Panel Model and Product Number
APOGEE Firmware Revision
PXC Compact Series (PXCE9) PXC36-E.A, PXC36-EF.A
3.2.4
3.2.3
3.2.2
3.2
3.2.4
3.2.3
3.2.2
3.2
3.2.2
3.2
3.2.4
3.2.3
3.2.2
3.2
3.2 3.2.4
3.2.3
3.2.2
3.2d
3.2.4
3.2.3
3.2.2
3.2d
— — —
PXC Compact Series (PAAC) PXC24.2-UCM.A
3.2.4
3.2.3
3.2.2
3.2.4
3.2.3
3.2.2
3.2.2 3.2.4
3.2.3
3.2.2
— 3.2.4
3.2.3
3.2.2
3.2.4
3.2.3
3.2.2
— — —
PXC Compact Series (PXCE) PXC16.2-E.A, PXC16.2-ER.Aa, PXC24.2-E.A, PXC24.2-ER.A PXC16.2-M.A, PXC16.2-MR.Aa, PXC24.2-M.A, PXC24.2-MR.A PXC16.2-EF.A, PXC16.2-ERF.Aa, PXC24.2-EF.A, PXC24.2-ERF.A
3.2.4
3.2.3
3.2.2
3.2
3.1
3.2.4
3.2.3
3.2.2
3.2
3.1
3.2.2
3.2
3.2
3.2.4
3.2.3
3.2.2
3.2
3.1
3.2
3.1
3.2.4
3.2.3
3.2.2
3.2 d
3.1
3.2.4
3.2.3
3.2.2
3.2 d
3.1
— — —
PXC Compact Series (PXCE)
PXC16-E.Aa, PXC16-ER.Aa PXC24-E.Aa, PXC24-ER.Aa
3.2.4
3.2.3
3.2.2
3.2
3.1
3.0
3.2.4
3.2.3
3.2.2
3.2
3.1
3.0
3.0 3.2
3.1
3.0
3.2.4
3.2.3
3.2.2
3.2d
3.1
3.0
3.2.4
3.2.3
3.2.2
3.2d
3.1
3.0
3.0 3.0 3.0
MBC Power Open Processor ARCnet/IP ALNa (562-040)
3.2
3.1
3.0
3.2
3.1
3.0
3.2
3.1
3.0
3.2
3.1
3.0
3.2
3.1
3.0
3.2d
3.1 3.0
3.2d
3.1
3.0
3.0 3.0 3.0
9 PXCE is the hardware platform for the PXC Compact.
APOGEE BACnet Field Panel
Siemens Industry, Inc. 157
Insight/Commissioning Tool Revision
3.12 3.11c 3.11 3.10 3.10b,c 3.9.1c 3.9c 3.8.1 3.8 3.7
BACnet Field Panel Model and Product Number
APOGEE Firmware Revision
Power MEC
Models:
(MCNE) 1100EB/1110EBa (549-630, 549-631)
1210EBa (549-633)
3.2d
3.1 3.0
3.2d
3.1
3.0
3.0 3.0 3.0
Power MEC (MEFE) 1200EFB (549-634), 1210EFBa (549-635)
3.2
3.1
3.0
3.2
3.1
3.0
3.2
3.1
3.0
3.2
3.1
3.0
3.2
3.1
3.0
3.2d
3.1
3.0
3.2d
3.1
3.0
Power MEC 1200ELB (549-636), 1210ELBa (549-637)
3.1
3.0
3.1
3.0
3.1
3.0
3.1 3.1 3.1 3.1 — — —
a. This model is discontinued.
b. Insight and Commissioning Tool Revision 3.10 and earlier do not recognize the PMXT/S, UEC (in FLN mode) or MS/TP PPM.
c. With latest firmware.rev.xml.
d. Insight and Commissioning Tool Revisions 3.9.1 and earlier do not recognize the HOA Upgrade Kit or algorithmic alarming.
CAUTION:
The Power MEC is now retired but is still sold on the repair parts (Rparts) program until October 1, 2017. Refer to POA-001.
Chapter 5–BACnet Field Panel
158 Siemens Industry, Inc.
Firmware Compatibility Chart The following table from a draft copy of the BACnet Network and Troubleshooting Manual 10 provides a quick reference to the compatible features offered for each revision. The left column represents the various features of the firmware, and the top row represents the different firmware revisions. For example, Firmware Revision 3.1 supports MS/TP Routing, Remote Trending, P1BIM, DB Restore from Flash, USB, Adapt and Wireless FLN.
Table 36: Compatible Features Offered for Each Firmware Revision. Compatible Functionalities Each Firmware Revision Supports.
Firmware Rev. 3.2.4 3.2.3 a) 3.2.2 b) 3.2 3.1 3.0.1 3
Desigo CC support ■
Remote Notification ■ ■
SNMP ■ ■
Facility To Go ■ ■
Web Server ■ ■ ■
PXM 10T/S ■ ■ ■
File System/Auto-Save
■ ■ ■
Event Enrollment ■ ■ ■ ■
Hand-Off-Auto (HOA) c)
■ ■ ■ ■
MS/TP Routing ■ ■ ■ ■ ■
Remote Trending ■ ■ ■ ■ ■
P1BIM ■ ■ ■ ■ ■
DB Restore from Flash
■ ■ ■ ■ ■
USB Support ■ ■ ■ ■ ■ ■
Adapt ■ ■ ■ ■ ■ ■ ■
Wireless FLN ■ ■ ■ ■ ■ ■ ■
a) Firmware is designed for PXC Series controllers, the features attached to this firmware are for these specific controllers only.
b) Firmware is designed for PXC Series controllers, the features attached to this firmware are for these specific controllers only.
c) For PXC Compact Series controllers only.
10 At the time of this writing, this manual is not yet published or posted anywhere on the Siemens Intranet.
APOGEE BACnet Field Panel
Siemens Industry, Inc. 159
PXC Modular Series for BACnet Networks The PXC Modular Series for BACnet networks is a high-performance modular Direct Digital Control (DDC) supervisory equipment controller, which is an integral part of the APOGEE Automation System. It is classified as a BACnet Building Controller (B-BC) and supports BACnet/IP and BACnet MS/TP protocols. It is BACnet Testing Laboratories (BTL) certified and classified as a BACnet Building Controller (B-BC).
Figure 59: PXC Modular Series Controller.
PXC Compact Series for BACnet Networks The PXC Compact Series (Programmable Control cerified and classified as a BACnet Building Controller (B-BC), which is an integral part of the APOGEE Automation System. The controllers are classified as either a BACnet Building Controller (B-BC) with support for BACnet/IP or BACnet MS/TP protocols. The PXC Compact is available with 16, 24, or 36 point terminations.
Chapter 5–BACnet Field Panel
160 Siemens Industry, Inc.
Figure 60: PXC Compact Series Controllers (PXC-24 and PXC-36 Shown).
Power MEC for BACnet The Power Modular Equipment Controller (MEC) for BACnet® Networks is an integral part of the APOGEE® Automation System. The controller is a part of a family of high performance, modular Direct Digital Control (DDC) supervisory equipment controllers. It is classified as a BACnet Building Controller (B-BC) and supports BACnet/IP and BACnet MS/TP protocols.
APOGEE BACnet Field Panel
Siemens Industry, Inc. 161
Figure 61: Power Modular Equipment Controller.
CAUTION:
The Power MEC is now retired but is still sold on the repair parts (Rparts) program until October 1, 2017. Refer to POA-001.
BTL Certification
The APOGEE BACnet field panels are BACnet Testing Laboratories (BTL) certified and listed BACnet Building Controllers. They carry the BTL certification mark and can meet specifications calling for native BACnet field panels. They provide interoperability with third-party BACnet workstations.
Chapter 5–BACnet Field Panel
162 Siemens Industry, Inc.
Firmware
Object Basics
BACnet is based on Objects and Services. As an analogy, BACnet’s Objects with their properties can be compared to APOGEE’s logical points and their point attributes. For more details about BACnet objects, see Chapter 2–BACnet Objects and Services.
Object Support Summary
The APOGEE BACnet field panel supports a sub-set of all of the 50 standard objects in the BACnet standard ANSI/ASHRAE Standard 135-2012. Table 37 shows a list of all of the standard BACnet objects and those supported by APOGEE BACnet Field Panels. Also shown is the APOGEE non-BACnet equivalent to the BACnet object.
Table 37. BACnet Objects Supported by the APOGEE BACnet Field Panel.
BACnet Object
Supported APOGEE Non-BACnet Equivalent
Notes
1 Accumulator No --
2 Analog Input Yes Physical LAI, LPACI Physical points.
3 Analog Output Yes Physical LAO Physical points.
4 Analog Value Yes Virtual LAI, LAO, LPACI and $LOC
Virtual points.
5 Averaging No -- APOGEE does support averaging in PPCL, but this table is referring to the equivalency of a BACnet object.
6 Binary Input Yes Physical LDI Physical points.
7 Binary Output Yes Physical LDO, L2SL, L2SP
Physical points.
8 Binary Value Yes Virtual LDI, LDO, L2SL, L2SP
Virtual points.
9 Calendar Yes Replaces Global Data: Calendar.
10 Command Yes Replaces Equipment Scheduler Command Table.
11 Device Yes Replaces ALN node.
12 Event Enrollment
Yes --
13 File Yes -- Used for file up/downloads to/from workstations, including third-party workstations that do not understand the content of the file.
14 Group No -- APOGEE Insight supports point grouping, but this table is referring to the equivalency of a BACnet object.
15 Life Safety Point No --
Firmware
Siemens Industry, Inc. 163
BACnet Object
Supported APOGEE Non-BACnet Equivalent
Notes
16 Life Safety Zone No --
17 Loop No -- APOGEE Insight PPCL supports LOOP statements, but this table is referring to the equivalency of a BACnet object.
18 Multistate Input No --
19 Multistate Output
Yes LFSSL, LFSSP, LOOAL, LOOAP
Physical and Virtual points.
20 Multistate Value Yes LENUM Physical and Virtual points.
21 Notification Class
Yes Replaces Global Data: Destinations.
22 Program No --
23 Pulse Converter No --
24 Schedule Yes Replaces Equipment Scheduler Mode Schedules.
25 Trend Log Yes Allows both internal and external trending of BACnet object properties by time and/or COV on any device on the BACnet network including BACnet TECs and third-party BACnet MS/TP devices.
26 Access Door No
27 Event Log No
28 Load Control No
29 Structured View No
30 Trend Log Multiple
No Monitors one or more properties of one or more referenced objects, either in the same device or in an external device.
31 Access Point No
32 Access Zone No
33 Access User No Defines a standardized object whose properties represent the externally visible characteristics associated with a user of a physical access control system.
34 Access Rights No Defines a standardized object whose properties represent the externally visible characteristics associated with access rights for physical access control.
35 Access Credential
No Defines a standardized object whose properties represent the externally visible characteristics of a credential that is used for authentication and authorization when requesting access.
36 Credential Data No Defines a standardized object whose properties represent the externally visible characteristics of a process that provides authentication factors read by a physical device.
Chapter 5–BACnet Field Panel
164 Siemens Industry, Inc.
BACnet Object
Supported APOGEE Non-BACnet Equivalent
Notes
37 CharacterString Value
No Defines a standardized object whose properties represent the externally visible characteristics of a named data value in a BACnet device.
38 DateTime Value No Defines a standardized object whose properties represent the externally visible characteristics of a named data value accessible to other BACnet devices.
39 Large Analog Value
No Defines a standardized object whose properties represent the externally visible characteristics of a named data value in a BACnet device. A BACnet device can use a Large Analog Value object to make any kind of double-precision data value accessible to other BACnet devices.
40 BitString Value No Defines a standardized object whose properties represent the externally visible characteristics of a named data value in a BACnet device. A BACnet device can use a BitString Value object to make any kind of bitstring data value accessible to other BACnet devices.
41 OctetString Value
No Defines a standardized object whose properties represent the externally visible characteristics of a named data value in a BACnet device. A BACnet device can use a OctetString Value object to make any kind of OctetString data value accessible to other BACnet devices.
42 Time Value Yes CRTIME A Time Value object is used to represent a single moment in time.
43 Integer Value No
44 Positive Integer Value
No
45 Date Value Yes Panel-resident points: MONTH and DAYOFM
46 DateTime Pattern
No
47 Time Pattern Value
No
48 Date Pattern Value
No
49 Network Security
No Defines a standardized object whose properties represent the externally visible network security settings and status of a BACnet device. Secure BACnet devices shall contain exactly one Network Security object and they shall have an instance of 1.
50 Global Group Object
No
Firmware
Siemens Industry, Inc. 165
Object Names and Instance Numbers
Each object must have a unique name within its BACnet Device. Local object names within the BACnet field panel database are limited to 30 characters and are case insensitive. However, the BACnet Field panel applications preserve case sensitive object name references to support remote object names in third-party panels that are case sensitive.
Each object within a BACnet Device must also have a unique identifier consisting of its Object_Type and its Instance Number. The Device Object (field panel) has the additional constraint that its Instance Number must be unique network wide.
Encoded Object Names
APOGEE BACnet field panels allow the user to reference an object with an encoded textual representation of the BACnet Device Object Instance Number and the BACnet Object Identifier. The general format is:
BAC_<device instance>_<object type>_<object instance>
The BAC_characterstring format is reserved for encoded names, and BAC characters cannot be used at the beginning of non-encoded object names. The device instance and object Instance Numbers must be in decimal format. The object type may be specified in decimal format, or with a two-character abbreviation as shown in Table 38.
Table 38. Object Type Formats.
Abbreviation11 Object Type Enumeration
AC Accumulator Object 23
AI Analog Input Object 00
AO Analog Output Object 01
AV Analog Value Object 02
AG Averaging Object 18
BI Binary Input Object 03
BO Binary Output Object 04
BV Binary Value Object 05
CA Calendar Object 06
CO Command Object 07
EE Event Enrollment Object 09
FI File Object 10
11 Object types in bold letters are supported in the APOGEE system.
Chapter 5–BACnet Field Panel
166 Siemens Industry, Inc.
Abbreviation11 Object Type Enumeration
GR Group Object 11
LP Life Safety Point 21
LZ Life Safety Zone 22
LO Loop Object 12
MI Multistate Input Object 13
MO Multistate Output Object 14
MV Multistate Value Object 19
NC Notification Class Object 15
PR Program Object 16
SC Schedule Object 17
TL Trend Log Object 20
Note that the Device Object Type, 08, cannot be specified in a fully encoded name.
The encoded name allows you to reference points that have name(s) greater than 30 characters, such as the device name and/or the object name could be longer than 30 characters.
For example, suppose you want to reference a point defined as:
Device Name: AdministrationBuildingChiller1 (this name has 31 characters)
Device Instance: 0004
Point Name: ReturnWaterTemperature (this name has 22 characters)
Point Type : Analog Input
Point Instance: 26
The encoded name would be: BAC_4_AI_26
Note the following about this example:
1. You cannot reference the point by its device name, because it is 31 characters.
2. You cannot reference the point by its 22 character point name because BACnet names are not unique network wide. You need to know the specific device name to ask for this specific point, and you cannot specify the device name because it is too long.
3. This point must exist on a third-party device, since APOGEE BACnet only supports 30 character device names for APOGEE field panels.
4. In this example, you can only use the encoded name to reference the point.
Firmware
Siemens Industry, Inc. 167
Device Specific Names
Since BACnet object names are not unique network wide, this option allows you to reference a point on a specific device.
The general format is [DeviceName] PointName:SubpointName
For example, suppose you want to reference a point defined as:
Device Name: AdministrationBuilding1 (note this name has 24 characters)
Device Instance: 0004
Point Name: ReturnWaterTemperature (note this name has 22 characters)
Point Type : Analog Input
Point Instance: 26
The device specific name would be:
[AdministrationBuilding1] ReturnWaterTemperature
Note the following about this example:
1. You can reference the point by its device name because it is only 24 characters.
2. You can also reference the point by its encoded name.
3. The point could reside in either an APOGEE node or a third-party node.
4. The encoded name would be: BAC_4_AI_26
Instance Number Allocation
Although Instance Numbers are automatically allocated, you can still manually select them. Within the field panel, Instance Numbers are allocated to each of the following types of objects:
• Physical and virtual point-like objects
• Application-related objects (schedule object, trend object, etc.)
• Field panel local and resident points (PPCL-generated, $LOC, SECNDS, etc.)
• FLN devices and points (auto unbundled and manually characterized)
Auto unbundled points use the same Instance Number every time, in every panel, such that encoded name references, like BAC_4_AI_26, can be used consistently.
Point-Like Objects
BACnet Implementation of APOGEE Logical Points
A number of BACnet objects function as point objects in the APOGEE BACnet system. Table 39 shows a list of the APOGEE logical points and their similar BACnet objects.
Chapter 5–BACnet Field Panel
168 Siemens Industry, Inc.
Table 39. BACnet Implementation of APOGEE Logical Points.
APOGEE BACnet (Physical) BACnet (Virtual)
LAO Analog Output Analog Value
LAI Analog Input Analog Value
LDO Binary Output Binary Value
LDI Binary Input Binary Value
LPACI Analog Input Analog Value
L2SL/L2SP Binary Output Binary Value
LFSSL/LFSSP Multistate Output Multistate Output
LOOAL/LOOAP Multistate Output Multistate Output
LENUM Multistate Value Multistate Value
• Analog and Digital points are mapped to BACnet Analog and Binary, Input and Output objects if the points are physical.
• Analog and Digital points are mapped to BACnet Value objects if the primary (or only) point are virtual, that is, the second pulsed points or the “proof” points are ignored.
• The Multistate points with “proofs” are mapped to Multistate Output objects regardless of whether they are physical or virtual.
• The Multistate points for LENUM are mapped to Multistate Value objects regardless of whether they are physical or virtual.
The Command Priority Array
BACnet supports an application-oriented prioritization mechanism, referred to as the Command Priority Array, for controlling the Present_Value property of some objects. Not all standard objects have a Present_Value, and some that do have it may not have an associated priority array.
You can view and modify the Command Priority Table from the Insight workstation, Desigo CC, Field Panel Web, or the HMI. However, you cannot command with priorities higher than the OPER slot (slot 8) in the table. That is, slots 1 – 7 are reserved for use by authorized persons during critical situations.
For more details about the Command Priority Array, see the Command Priority Properties section in Chapter 2–BACnet Objects and Services.
TEC Subpoints
Bundled TEC subpoints have Command Priority Array support, just like a regular point.
Firmware
Siemens Industry, Inc. 169
Browsing
When a bundled point that has not yet been commanded is browsed with the HMI or the Insight BACnet Browser, the “initial” priority array property is empty. The Relinquish Default property contains the current Present_Value of the point.
Commanding
A bundled EEPROM-only TEC subpoint is commandable via the OPER slot of the priority array only.
When a bundled point is commanded, the point will be unbundled, and the correct priority array slot will be filled in with the commanded value. The system determines if the point is one that changes only the EEPROM in the TEC. This EEPROM only point command will fill the command priority slot requested. If the priority slot is OPER or above (priority level 1 – 8), the command will burn the EEPROM. If the slot is below OPER (priority level 9 – 16), then the point and priority array will be FAILed. Any time the priority array is failed, the Relinquish Default will contain the actual value. The Present_Value will be set to the highest priority slot, like any other point.
The above operation prevents applications, like PPCL or Scheduling, from constantly changing the EEPROM value and exceeding the 10,000 re-burn limit on EEPROM. Only OPERATOR commands can change the EEPROM value.
When a manually unbundled EEPROM only point is commanded, the priority array is already present, so the correct slot is filled with the commanded value. From this point, the operation is the same as commanding a bundled point, shown above.
Releasing
When a point that can be bundled is released, the following actions are possible:
• If the point is not an EEPROM-only point, then the point is released.
• If the point is an EEPROM-only point, it is not released, such that the Initial Value remains in the device.
• If the Command Priority Array is empty, then the point is re-bundled.
• If the Command Priority Array is not empty, the highest priority slot is used to command the point.
Chapter 5–BACnet Field Panel
170 Siemens Industry, Inc.
FLN Commands
HAND-OFF-AUTO Switches
The HAND-OFF-AUTO (H-O-A) switches on a MEC correspond to FLN 0, Drop 0. (The backplane of the panel is considered FLN 0, Drop 0. Therefore, the HOA switches only correspond to those fixed points on the backplane.) The status of H-O-A is mapped to the OVERRIDDEN flag of the Status property of the related point-like object.
The HAND mode of a point overrides the BACnet Command Priority Array. The slots in the array may still be commanded, but will not have an effect until the HAND condition is removed.
If the H-O-A switch is in the HAND position, OVERRIDDEN is set to TRUE and subsequent FLN data COVs will be saved in Present Value only (no priority array update). The priority array is considered to be out of sync with the state of the point. This is acceptable because the BACnet field panel no longer has control of the point–the switch controls the point.
TEC Tool–Override Commands
In non-BACnet APOGEE, PPCL can compete with the TEC tool (CIS or Voyager) for control of a point. PPCL executes at a repeatable cycle and keeps re-commanding a TEC point. Other applications, like Scheduling, command only once.
In BACnet APOGEE, if the Command Priority Array slot to which the TEC tool commands (slot 16 by default) already has a value, the field panel remembers which application commanded it (PPCL, Scheduling, etc.). Tool commands may be accepted momentarily, but will be over-written by the field panel with the previous value. Beyond this, if a higher Command Priority Array slot for the point has a value, then the point will be recommended to that value from the tool-entered value. To eliminate this conflict, you can temporarily disconnect the TEC from the FLN – recognizing that any changes will be over-written when the TEC is reconnected to the FLN. To make the tool’s change permanent, the Command Priority Array for that point has to be cleared before reconnecting the FLN.
Firmware
Siemens Industry, Inc. 171
TEC Tool–Releasing
Releasing a bundled point at the TEC with a TEC tool releases slot 16 of the associated Command Priority Array. If a higher slot for the point has a value, then the point will be recommended to that value from the tool-entered value. To eliminate this conflict, you can temporarily disconnect the TEC from the FLN–recognizing that any changes will be over-written when the TEC is reconnected to the FLN. To make the tool’s change permanent, the Command Priority Array for that point has to be cleared before reconnecting the FLN.
Relinquish Default
Downloads from the Insight workstation only contain the Relinquish Default, that is the Command Priority Array is always empty. So, if you upload the field panel’s database and then download it back to the field panel, the Command Priority Array is lost–only the Relinquish Default is saved.
The Relinquish Default is honored for all point object types except BO (Binary Output) and MSO (Multi-State Output). (These correspond to LDO, L2Sx, LFSSx and LOOAx.) For these exceptions, the Relinquish Default corresponds to the physical OFF state, that is if the point is inverted, then the Relinquish Default will be ON.
When the Relinquish Default is not honored, it is over-written with the actual value, such that the Present Value and Priority Array are said to be in sync.
For P1 TEC’s, the Relinquish Default is not persistent for any TEC subpoint, because the Relinquish Default is used to store changes in value from the TEC device. The Set Initial Value prompt must be used to accomplish the Relinquish Default functionality within the TEC. To set the TEC initial value, use the menu path: Application, Fln, Tec, Initval, Command, Set. On start-up, this TEC initial value is read from EEPROM and written to RAM.
The above paragraph is NOT true for BACnet MS/TP TEC’s.
The Out-Of-Service Property
The BACnet Out_Of_Service property is used to disconnect the Present_Value and Reliability properties of a BACnet Object from its physical I/O. This differs from the Insight Out-Of-Service function, which suspends COV and alarm notifications from a logical point.
Chapter 5–BACnet Field Panel
172 Siemens Industry, Inc.
Another difference is that input points can only 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. An input point must be out-of-service to be commanded.
TEC subpoints shall use Out_Of_Service to allow input points to be commanded. You must first command the input point Out_Of_Service before commanding the Present_Value.
When the point is put back into service, the point is re-characterized, such that the Present_Value (and Control Status) reflects the device value. This operation behaves just like the value was just received from the physical I/O, such as update Trend, update the Alarm state, and report a COV over the ALN if necessary.
Engineering Units
BACnet Engineering Units are pre-configured using the BACnet Engineering Units enumeration. Free form user-entered text is not allowed.
A predefined BACnet text string is associated with each value of the BACnet Engineering Units enumeration. The BACnet text strings are used for display in all reports that display the free form engineering unit strings in the non-BACnet field panels. The maximum length for this string is eight characters.
State Text
The APOGEE State Text table is used when configuring BACnet Point Objects. BACnet default state text tables exist for APOGEE points that map to the BACnet MultiStateOutput (MO) and MultiStateValue (MV) object types. You can only command a point with state text values; if the state text values map to an APOGEE State Text table.
Totalization
Totalization is available for the active state of LDIs, LDOs, L2SLs, and L2SPs. These points map to BACnet Objects with elapsed time. All other totalization which is supported in APOGEE non-BACnet field panels is not supported in the APOGEE BACnet; that is, there is no totalization for analog points.
The two properties, Elapsed_Active_Time and Time_Of_Active_Time_Reset are only available in point object's that have been configured as able to be totalized.
Totalization will be available in seconds only. Hours and minutes are not available.
Firmware
Siemens Industry, Inc. 173
Pulse Accumulator
The APOGEE BACnet LPACI point is represented as an Analog Input (AI) object for physical LPACI points, and Analog Value (AV), for virtual LPACI points.
In order to change the value of a physical LPACI, the associated BACnet object must be placed out of service, which by definition disconnects the point from the physical I/O. When the point is placed back into service, the counter will begin at the Present_Value. So, LPACI points ignore counts received during Out-Of-Service and restart at the current Present_Value.
In order to change the value of a virtual LPACI, the associated BACnet object can be simply commanded.
Network Management
The BACnet protocol specifies one Device object in each BACnet Device. A Device object is referenced by its Object_Identifier property, its Object_Name and its Instance Number. Each of these must be unique throughout the BACnet internetwork. This uniqueness allows identifying all of the devices on the BACnet network.
Within an APOGEE BACnet system, a device on the network is identified by its BACnet Device Instance Number, which also must be unique network wide. The Instance Number relates to the Object_Identifier as follows:
Object_Identifier = Object_Type + Instance Number
When specifying a field panel name in Field Panel Application Programs, you can use either the Device Instance ID (such as 9001) or the Device Specific Name (such as Building1_Panel1).
BBMD Routing Tables
An APOGEE BACnet field panel can act as a BACnet/IP Broadcast Management Device (BBMD). Therefore, every field panel has its own BBMD routing table. The routing table contains a list of BACnet addresses of all of the BBMDs on the network–this includes IP address or Device Object name and UDP port. The presence of a panel’s own address in a BBMD table enables the BBMD functionality in the panel. The routing table length is only limited to the capacity of the field panel memory. All field panels acting as BBMDs must have identical routing tables, that is, the same list of addresses. This is the responsibility of the user/installer.
Chapter 5–BACnet Field Panel
174 Siemens Industry, Inc.
Foreign Device Support
The field panel can register with a single BBMD as a foreign device. The BBMD MAC address, UDP port, subnet mask and Time-to-live parameters are configurable parameters from the HMI.
Field panels acting as BBMDs must have a fixed IP address.
A field panel that is already acting as a BBMD cannot register as a foreign device with another BBMD.
DHCP and DNS Support
The field panel supports DHCP to get its own IP address assignment. When acting as a Foreign Device to a BBMD, the field panel can have a DHCP assigned address, but the BBMD must have a fixed IP address.
For more details about APOGEE BACnet Network Management, see Chapter 4–BACnet Communications.
Trending
In BACnet trending, all of the trend information resides in the Trend Log object. This differs from APOGEE trending in which the trend information resides with the point being trended. In BACnet trending:
• The Trend Log object contains the ID of the point being trended, an array of all of the data collected, Notification Class information about notifying a computer to upload the data when the trend buffer fills, and much more.
• The Notification Class object contains a list of devices (computers) to be notified when the trend buffer is nearly full.
APOGEE GO can collect trend data from a BACnet field panel.
Firmware Revision 3.1 or later supports external trending. Users may trend properties of objects in any device on the BACnet network, including devices that do not support the BACnet trend object, such as BACnet TECs and certain third-party devices. Trending of BACnet object properties can be done by time and/or COV on any device on the BACnet network including BACnet TECs and third-party BACnet MS/TP devices.
For details about the BACnet Trending application, see Chapter 9–BACnet Trending.
Firmware
Siemens Industry, Inc. 175
Alarm and Event Applications
Alarms
The BACnet field panel supports BACnet Intrinsic alarms and Algorithmic Alarming (Event Enrollment).
Alarming is based on two BACnet objects:
• The BACnet point-like object in which the alarming information resides.
• The BACnet Notification Class object, which directs the alarm to specific destinations, such as workstations. The Notification Class object contains the priority of the alarm.
For details about the BACnet Alarming application, see Chapter 8–BACnet Alarming.
Events–System Messages
APOGEE BACnet field panels can generate system messages as a result of some system event, such as PPCL errors, logins and logouts. These messages are made available to third-party devices via the ConfirmedTextMessage service and the UnconfirmedTextMessage service. If the third-party device supports these services, it will be able to receive APOGEE Automation System messages. Since the APOGEE BACnet field panel supports these services, messages from third-party devices can be displayed at the HMI.
APOGEE BACnet field panels send system messages to the Notification Class Objects associated with each message. You can configure each system message to associate it with a Notification Class Instance Number between 0 and 255. The global database for system messages is limited to Notification Class values between 1 and 250, in accordance with the APOGEE limitation.
The standard APOGEE error messages can be displayed in the HMI (Figure 62). The default Notification Class Instance Number of zero is assigned until the user assigns another Instance Number. The YES and NO in the second column is for enabling dial-out. Messages 1 and 2 can only be displayed locally (within the field panel from which the messages originate).
Chapter 5–BACnet Field Panel
176 Siemens Industry, Inc.
>Point, Application, Time, Message, Cancel, System, passWord, Bye? s >Diagnostics, Users, dSt, Bacnet, Error_msgs, Hardware, Text, Quit? e >Display, Replace, Quit? d >Here, Printer : H 01/01/2002 TUE ERROR MESSAGE REPORT 00:00 ------------------------------------------------------------------------------- Notification ID Message 1 0 (YES) Field panel FAILURE 2 0 (YES) Field panel RETURN from failure 3 0 (YES) DEVICE FAILURE in field panel 4 0 (YES) DEVICE RETURN from failure in field panel 5 0 (NO) PPCL statement FAILURE 6 0 (NO) PPCL statement RETURN from failure 7 0 (NO) User login at field panel 8 0 (NO) User logout at field panel 9 0 (NO) Unsuccessful login attempt at field panel 10 0 (NO) Predicted demand above 90% for meter area 11 0 (NO) Predicted demand below 90% for meter area 12 0 (NO) Predicted demand above 100% for meter area 13 0 (NO) Predicted demand below 100% for meter area 14 0 (NO) Loop Tuning finished 15 0 (NO) Tuning failed; could not reach steady state 16 0 (NO) Auto tuning failed, check results 17 0 (NO) Tuning failed; check available memory, try again 18 0 (NO) Tuning failed; constant process variable 19 0 (NO) Tuning failed; retry disturbance 20 0 (NO) Tuning failed; constant control variable 21 0 (NO) Loop Tuning started
Figure 62. Standard APOGEE Error Messages displayed on HMI.
Scheduling
The Insight Scheduling application is replaced by BACnet objects as follows:
• The BACnet Schedule object replaces the APOGEE Zone, Mode Schedule, and Override Schedule.
• The BACnet Command object replaces the APOGEE Command Table within the Zone.
• The BACnet Calendar object replaces the APOGEE calendar that is shared as global data on the ALN.
APOGEE GO can edit BACnet schedules in BACnet field panels.
For details about the BACnet Scheduling application, see Chapter 9–BACnet Scheduling.
Firmware
Siemens Industry, Inc. 177
PPCL
PPCL in an APOGEE BACnet field panel has its own configurable priority that is used for point commands and releases issued from the PPCL statements. You can specify a command priority value or use the default PPCL value of 16.
The command priority value relates to the slots in the BACnet Command Priority Array. For a full explanation, see the Command Priority Properties section of Chapter 2– BACnet Objects and Services.
The priority is entered as the Priority for Writing through the field panel HMI (Figure 63). In the Insight Program Editor, the priority is entered as the PPCL Command Priority. For details, see the Program Editor section of Chapter 8–Insight BACnet Option.
For compatibility with the APOGEE Automation System, the field panel PPCL application supports automatic conversion from APOGEE priority levels entered in PPCL code to default BACnet Command priority array slots (Table 40).
Table 40. BACnet Command Priority Array Slots.
APOGEE Priority Default BACnet Command Priority
OPER 08
SMOKE 10
EMER 12
PDL 14
PPCL, NONE 16
The field panel allows you to change the Default BACnet Command Priorities for PPCL through SMOKE. For OPER, the value in the table should be used as the highest priority slot available for commanding. That is, you can command at this priority and lower.
A BACnet Command Priority value of 16 is used by PPCL as the default priority for writing, if this attribute is not specified by the user at configuration time.
Points commanded from PPCL use the priority for writing value unless there is a @priority indicator in the PPCL line of code. The @priority indicator maps to a slot in the global Command Priority Table when commanding the point.
Command Priority Example 1: 10 ON(@OPER, FAN)
20 ON(LIGHTS)
For line 10, the Command Priority Table will be used to automatically map OPER to a BACnet command priority number.
Chapter 5–BACnet Field Panel
178 Siemens Industry, Inc.
For line 20, the Priority_For_Writing will be used.
Command Priority Example 2:
The Priority for Writing slot is also used whenever the NONE keyword is used. For example:
10 ON(@NONE, FAN)
20 IF(FAN.EQ.@NONE) THEN GOTO 100
If the Priority for Writing was set to 11, then:
• Line 10 would set the FAN point’s priority array slot 11 = ON, and
• Line 20 would be TRUE if:
− The highest slot in the FAN point’s priority array is 11, or
− The FAN point’s priority array is empty.
The APOGEE BACnet field panel can discover other BACnet devices based on the Device Name used in PPCL statements. Therefore, PPCL statements in APOGEE BACnet field panels can use point names from other BACnet devices on the Internetwork.
Alarming can be enabled and disabled via PPCL in BACnet field panels. The ENALM and DISALM statements are used for these functions.
PPCL in BACnet field panels supports monitoring and commanding of Present_Value, Status, and Priority of points defined locally, over the ALN to other BACnet field panels, and over the ALN to third-party devices.
>Point, Application, Time, Message, Cancel, System, passWord, Bye? a >Ppcl, flNdevice, Bacnet, Quit? p >Log, Display, unReslv, Edit, Find, eNable, dIsable, Trace, Pdl, tUne, Quit? e >Program name : ahu1-------------------------- >Field panel : ------- >Priority For Writing : -- >Add, Modify, Copy, Delete, Look, Quit? a >Line ? 10 on(SFAN)-------------------------------------------------------- PPCL Line Added Program name: ahu1 >Add, Modify, Copy, Delete, Look, Quit? l >First line number : -------- >Last line number : -------- 08/14/2005 SUN PPCL LOOK REPORT 23:25 ------------------------------------------------------------------------------- Search for <ahu1> Line numbers <1 to 32767> PPCL program <ahu1> Field panel name <9033> Priority For Writing <16> Instance Number Block Start <30150> Instance Number Block Size <200> State Line Statement ------------------------------------------------------------------------------- D 10 ON(SFAN)
Firmware
Siemens Industry, Inc. 179
End of report
Figure 63. HMI Display for PPCL in an APOGEE BACnet Field Panel.
Resident Points
Each PPCL program has 26 resident points (e.g. SECNDS,SECND1,…,SECND7, $LOC1,…,$LOC15) that are capable of being displayed by the HMI. Figure 64 shows the 26 resident points that were created when the PPCL program myProgram was created. Each of these subpoints is automatically assigned a BACnet Instance Number. >Point, Application, Time, Message, Cancel, System, passWord, Bye? a >Ppcl, flNdevice, Quit? p >Log, Display, unReslv, Edit, Find, eNable, dIsable, Trace, Pdl, tUne, Quit? e >Program name : myProgram--------------------- >Field panel : ------- >Priority For Writing : 16 >Add, Modify, Copy, Delete, Look, Quit? a >Line ? c test------------------------------------------------------------- Compiler syntax error >Add, Modify, Copy, Delete, Look, Quit? - >Point, Application, Time, Message, Cancel, System, passWord, Bye? p >Log, Display, Command, Edit, Operation, Monitor, Alarm, Trend, Quit? l >Point name : myProgram:*-------------------------------- 03/28/2006 TUE POINT LOG REPORT 15:22 ------------------------------------------------------------------------------- Search for <myProgram:*> Point name :Suffix (Description) Value/State Status Priority ------------------------------------------------------------------------------- myProgram :PPCL Address 9033 -N- NONE :SECNDS 0 -N- NONE :SECND1 0 -N- NONE :SECND2 0 -N- NONE :SECND3 0 -N- NONE :SECND4 0 -N- NONE :SECND5 0 -N- NONE :SECND6 0 -N- NONE :SECND7 0 -N- NONE :LOC1 0.0 -N- NONE :LOC2 0.0 -N- NONE :LOC3 0.0 -N- NONE :LOC4 0.0 -N- NONE :LOC5 0.0 -N- NONE :LOC6 0.0 -N- NONE :LOC7 0.0 -N- NONE :LOC8 0.0 -N- NONE :LOC9 0.0 -N- NONE :LOC10 0.0 -N- NONE :LOC11 0.0 -N- NONE :LOC12 0.0 -N- NONE :LOC13 0.0 -N- NONE :LOC14 0.0 -N- NONE
Chapter 5–BACnet Field Panel
180 Siemens Industry, Inc.
:LOC15 0.0 -N- NONE :PDL 0.0 -N- NONE :TOTKW 0.0 -N- NONE End of report
Figure 64. HMI Display of Resident Points created by PPCL Program.
Each PPCL program has an Instance Number range of 200. But, because there are already 26 fixed resident points using Instance Numbers, you are limited to 174 user-defined local points (available for LOCAL statements). If you need more than that, then you have to create a new PPCL program that gives you a new set of 200. That is, 26 fixed and 174 user-defined local points.
You can display the Instance Number Block Start and Instance Number Block Size (200) of a PPCL program (Figure 63). For example, the program ahu1 has the Instance Number range from 30176 to 30350 available for user-entered local points created using the DEFINE statement. Instance Numbers 30150 through 30175 are used by the fixed resident points.
You can also display the Instance Number of a specific resident point. The resident point is named as an APOGEE subpoint in the following colon-separated format:
PPCL Program Name: Resident Point Name
Figure 65 shows an example of displaying the Instance Number (and other data) of the PDL resident point. In this case, the Instance Number Block Start for this program is 50500, of which the 24th is the PDL resident point. So, the Instance Number of the PDL is 50524.
>Point, Application, Time, Message, Cancel, System, passWord, Bye? p >Log, Display, Command, Edit, Operation, Monitor, Alarm, Trend, Quit? e >Add, Modify, Copy, Delete, Look, Quit? l >Point name : myProgram:pdl------------------------------ 03/28/2006 TUE POINT LOOK REPORT 15:23 ------------------------------------------------------------------------------- Search for <myProgram:pdl> Field Value ------------------------------------------------------------------------------- Point system name : myProgram:PDL Instance Number : 50524 (BAC_9033_AV_50524) Point name : myProgram:PDL Point type : LAO Descriptor : Value : 0.0 Condition : -N- Priority : NONE Analog representation : Float Number of decimal places : 4 Engineering units : Access group(s) : <all> Alarmable : NO Device Instance Number : 9033 Point address : --- Virtual --- COV limit : 0.0 Relinquish Default : 0.0
APOGEE BACnet Field Panel Firmware Revision 3.2.4
Siemens Industry, Inc. 181
End of report
Figure 65. Display of PDL Resident Point Instance Number.
A PPCL local point is not guaranteed to have the same Instance Number from program to program, and should not be referenced using the encoded name. That is, BAC_9000_AV_150.
APOGEE BACnet Field Panel Firmware Revision 3.2.4 APOGEE BACnet Field Panel Firmware Revision 3.2.4 is compatible with DesigoTM CC. DesigoTM CC is a new management workstation released in July 2012 that provides optimized monitoring and control of integrated building automation and fire safety systems, and incorporates real-time video for event verification.
APOGEE BACnet Field Panel Firmware Revision 3.2.4, released in August 2012, is compatible with DesigoTM CC and supports BACnet standard trend log object Add, Delete, and Modify using standard BACnet services, which promotes enhanced usability and interoperability. It also supports PXC controller web-services-based database editing and user-interface enhancements. Firmware Revision 3.2.4, along with Insight 3.12 and DesigoTM CC positions the APOGEE Automation System for comprehensive BACnet support throughout, in order to meet current and future customer requirements. Important new features include:
• Supports and enhances DesigoTM CC by adding an embedded user interface for point editing, PPCL editing, TEC editing, subpoint logs, commanding, and initial values.
• Supports a BACnet trend editing function which allows the use of standard BACnet services to Add, Modify and Delete PXC-based trend log objects on the network.
• Is BACnet protocol listed for ANSI/ASHRAE Standard 135-2008. • Provides database editing support of PXC controllers directly with the
DesigoTM CC workstation using web services, in addition to increasing our comprehensive BACnet compliant and BTL (BACnet Testing Labs) listed functionality.
Firmware 3.2.4 also represents the introduction of a cross platform graphical user interface, allowing for near identical interfaces between the BACnet Field Panel Web Server, and the field panel editors that are utilized in Desigo CC. The reuse of these graphical user interfaces provides continuity throughout Siemens systems and reduces the potential learning curve associated with the introduction of our exciting new next generation workstation – DesigoTM CC.
Chapter 5–BACnet Field Panel
182 Siemens Industry, Inc.
Certifications
The following certifications have been obtained with APOGEE BACnet Field Panel Firmware Revision 3.2.4:
• All PXC Compact and PXC Modular Controllers loaded with 3.x firmware are BTL Listed as B-BC devices
• BACnet PXC 24 UEC (part # PXC24.2-UCM.A) is BTL listed as a B-AAC device • UL/CUL 916 PAZX/PAZX7 (Enclosed Energy Management) • UL864 UUKL for Smoke Control Equipment (except PXC 24 UEC) • C-Tick • CE Mark • WEEE Compliant • RoHS Compliant
APOGEE Firmware Revision 3.2.3 APOGEE Firmware Revision 3.2.3 supports the following features and functionality:
• Performance Enhancements – provides solutions to following performance issues:
o Field Panel delays processing COV from MS/TP network o UI ReadPropertyMultiple too big for third-party device o Performance issues in MS/TP processing o Need increased database discovery performance
• Supports the following features and functionality enhancements: o Facility To Go o Simple Network Management Protocol (SNMP)
The Simple Network Management Protocol (SNMP) Agent is a firmware feature that has been added to BACnet Firmware Revision 3.2.3 and later. The SNMP Agent allows points in the field panel to communicate with an SNMP manager over Ethernet. SNMP is an application layer protocol that facilitates the exchange of management information between network devices. It is part of the Transmission Control Protocol/Internet Protocol (TCP/IP) suite. SNMP enables network administrators to manage network performance, find and solve network problems, and plan for network growth.
o Remote Notification
If you are using Insight in addition to the Field Panel Web Server, you must use the Insight Remote Notification application rather than the Web Server application. If you migrate from a Web Server solution to a solution using Insight, you must reconfigure Remote Notification to use the Insight application.
o Current build identification o Panel compatibility/ synchronization status (Web Server) o Solutions to issues noted in the field
APOGEE Firmware Revision 3.2.2
Siemens Industry, Inc. 183
APOGEE Firmware Revision 3.2.2 Introduced BACnet Field Panel Web Server. (Refer to tools that came with F/W release.)
HMI This section describes new functionality for the APOGEE BACnet Field Panel HMI, which can be accessed through the serial port or by Telnet. The following subsections contain summaries of changes to the text displays in the HMI. For detailed instructions, see the latest revision of the APOGEE Field Panel User’s Manual (125-3000).
Application Summary
The following are summaries of the changes to the Application menu item.
Display Deletions
Application, A Ppcl, flnDevice, Schedule, Quit? Log, Display, Edit, Ssto, Override, eNable, dIsable, Quit?
Removed non-BACnet Equipment scheduler
System Summary
The following are summaries of the changes to the System menu item.
Display Deletions
System, S Diagnostics, Users, dAtes, deStination, Error_msgs, Hardware, Text, Quit? Priorities, Addresses, Quit? -
Removed old Alarm Destination prompting
Display Additions
System, S Diagnostics, Users, dAtes, Bacnet, Error_msgs, Hardware, Text, Quit? Priorities, Addresses, Quit? -
Added new BACnet prompting
Priorities, Display, Modify, Quit?
Command Priority Table mapping
Addresses Display, Add, dElete, Quit? M
Address Helper Table mapping
Chapter 5–BACnet Field Panel
184 Siemens Industry, Inc.
Point Command Priority
In addition to the point name and point value, the HMI user is prompted for the Command Priority Array slot number when commanding or releasing points. The user may specify an exact slot, or use the default OPER. The APOGEE priority levels displayed as OPER, SMOK, EMER, PDL and OVRD, are replaced with the BACnet slot levels, BN01, BN02, etc. The APOGEE priority NONE is displayed when the Priority Array is empty or not present.
A Priority Array Report can be run to allow you to view the entire Priority Array for a point. Access the report (Figure 66).
Point, Application, Time, Message, Cancel, System, passWord, Bye? p Log, Display, Command, Edit, Operation, Monitor, Alarm, Trend, Quit? d Value, Total, Definition, Priority, Unresolved, Quit? P Point name : FAN--------------------------------------------- 01/14/2002 MON POINT PRIORITY REPORT 07:43 --------------------------------------------------------------------------------- Search for <FAN> Point name :Suffix (Description) Value/State Status Priority --------------------------------------------------------------------------------- fan (supply fan) OFF -N- BN08 1. Manual Life Safety --- 2. Automatic Life Safety --- 3. BN03 --- 4. BN04 --- 5. Critical Equipment Control --- 6. Minimum On/Off --- 7. BN03 --- 8. Manual Operator (oper) OFF 9. BN09 --- 10. BN10 (smoke) ON 11. BN11 --- 12. BN12 (emer) --- 13. BN13 --- 14. BN14 (pdl) --- 15. BN15 --- 16. BN16 (sched & ppcl) ON Relinquish Default OFF End of report
Figure 66. Example Priority Array Report.
Siemens Industry, Inc. 185
Chapter 6–BACnet FLN Devices Chapter 6 describes the basic features and functions of the Siemens BACnet TEC and Programmable TEC (PTEC) product lines.
BACnet Programmable TEC (PTEC) In August 2010, Siemens Building Technologies released a new line of BACnet Programmable Terminal Equipment Controllers (PTECs), which for the first time allowed a subset of PPCL programming capabilities within a TEC device. PTECs are application-specific controllers designed to provide either networked or stand-alone Direct Digital Control (DDC) for various types of HVAC terminal units. All PTECs are listed with the BACnet Testing Labs (BTL) as BACnet Application-Specific Controllers (B-ASC) and communicate using BACnet MS/TP.
A key feature of the PTEC product line is the introduction of custom PPCL programming capabilities into a BACnet TEC.12 This capability allows you to create your own custom application and is used to add, remove, modify, backup and restore BACnet programmable TECs. Standard BACnet TEC applications reside in the PTEC and can run alongside the custom PPCL. It is important to note that BACnet TEC applications command points at BACnet priority 15. Because of this programming capability PTEC controllers can perform complex HVAC control, monitoring and energy management functions. PTEC controllers are designed to reside on any BACnet control system network.
There are two hardware platforms for BACnet PTEC controllers – a long-board platform with eight digital outputs (8 DOs) and a short-board platform with six digital outputs (6 DOs). Figure 66 shows the long-board platform of the PTEC controller.
12 The PPCL supported by the PTEC is a subset of the PPCL supported in the ALN field panel. For more information on the PPCL
rules and limitations on supported functions, refer to the BACnet Programmable TEC (PTEC) Tool User Manual.
Chapter 6–BACnet FLN Devices
186 Siemens Industry, Inc.
Figure 67: BACnet PTEC Controller (Long-Board Platform).
Systems Integration Benefits
The PTEC offers these features and benefits:
• Increased programming flexibility • Reduced operating and training costs • Increased employee productivity • Increased diagnostic capabilities to extend equipment life • Improved systems information and control • Potential for maximized energy savings through increased programming
flexibility Field Panel Requirements
PTEC controllers require field panel Firmware Revision 3.1 or later.
Required Components
Software
• Cimetrics BACstac 5.0 • PTEC Tool (Stand-alone, Insight and Commissioning Tool are not required) • Windows XP
Hardware
• BACnet/IP or MS/TP Router – for example, Cimetrics of field panel.
BACnet Programmable TEC (PTEC)
Siemens Industry, Inc. 187
• Eithernet cable o Crossover cable required for direct connection to field panels.
PTEC Controller Applications, Product Numbers, and Firmware Revisions
Controller Type
Product No. Application Type
Application No.13
Firmware Revision
BACnet PTEC Terminal Box/VAV Controller
550-495P VAV pressure independent
6520, 6521,6522, 6523, 6524, 6525, 6526, 6527 (6587)
BV40
Rev 2.0.0.19
BACnet PTEC VAV with Series Fan and 3-Stage Electric Heat Controller
550-492P VAV pressure independent
6557 (6599) BH40 Rev 2.0.0.21
BACnet PTEC Unit Conditioner (Fan Coil) Controller
550-496P VAV pressure dependant
Fan Coil Unit
6540, 6541 6550, 6551, 6552, 6553, 6554 (6591)
BF40 Rev 2.0.0.19
BACnet PTEC Unit Vent Controller
550-493P
Unit ventilator 6575, 6576, 6577, 6578, 6579 (6595)
BE40 Rev 2.0.0.25
BACnet PTEC Heat Pump Controller
550-490P
Multi-Stage Compressor
6583, 6584 (6590)
BK40 Rev 2.0.0.20
BACnet PTEC Extended I/O Controller
550-491P
I/O Expansion Module
6596
BI40 Rev 2.0.0.17
13 Application numbers in parentheses are slave mode applications.
Chapter 6–BACnet FLN Devices
188 Siemens Industry, Inc.
Controller Type
Product No. Application Type
Application No.13
Firmware Revision
BACnet PTEC Dual Duct Controller
550-497P
Two Air Velocity Sensors
6565, 6566, 6567, 6568, 6569
BD40 Rev 2.0.0.1
BACnet PTEC Constant Volume Controllers
550-498P Electronic Output
6560, 6562, 6563
BC40 Rev 2.0.0.20
BACnet Programmable VAV with Chilled Beam, CO2-Based Demand Control Ventilation, Floating or Analog Output
550-494P Floating or Analog Output
6658 (6692) BB50 Rev 2.0.5.6
BACnet Standardized Device Profiles and Interoperabiltiy Building Blocks (BIBBs) for PTECs
BACnet PTEC Terminal Box VAV Controller
BACnet Standardized Device Profile Product Device Profile BTL Tested
BACnet PTEC Terminal Box (VAV) Controller
BACnet Application-Specific Controller (B-ASC) •
Supported BACnet Interoperability Building Block (BIBBs) Product BIBB Name BTL
Tested PTEC Terminal Box (VAV) Controller
DS-RP-B Data Sharing-ReadProperty-B •
BACnet Programmable TEC (PTEC)
Siemens Industry, Inc. 189
DS-RPM-B Data Sharing-ReadPropertyMultiple-B •
DS-WP-B Data Sharing-Write Property-B •
DM-DDB-B Device Management-Dynamic Device Binding-B •
DM-DOB-B Device Management-Dynamic Object Binding-B •
DM-DDC-B Device Management-DeviceCommunicationControl-B •
DM-RD-B Device Management-ReinitializeDevice-B •
DM-BR-B Device Management-Backup and Restore-B •
DM-OCD-B Device Management-Object Creation and Deletion-B •
BACnet PTEC VAV with Series Fan and 3-Stage Electric Heat Controller
BACnet Standardized Device Profile Product Device Profile BTL Tested
BACnet PTEC VAV with Series Fan and 3-Stage Electric Heat Controller
BACnet Application-Specific Controller (B-ASC) •
Supported BACnet Interoperability Building Block (BIBBs) Product BIBB Name BTL
Tested BACnet PTEC VAV with Series Fan and 3-Stage Electric Heat Controller
DS-RP-B Data Sharing-ReadProperty-B •
DS-RPM-B Data Sharing-ReadPropertyMultiple-B •
DS-WP-B Data Sharing-Write Property-B •
DM-DDB-B Device Management-Dynamic Device Binding-B •
Chapter 6–BACnet FLN Devices
190 Siemens Industry, Inc.
Product BIBB Name BTL Tested
DM-DOB-B Device Management-Dynamic Object Binding-B •
DM-DDC-B Device Management-DeviceCommunicationControl-B •
BACnet PTEC Unit Conditioner (Fan Coil) Controller
BACnet Standardized Device Profile Product Device Profile BTL Tested
BACnet PTEC Unit Conditioner (Fan Coil) Controller
BACnet Application-Specific Controller (B-ASC) •
Supported BACnet Interoperability Building Block (BIBBs) Product BIBB Name BTL
Tested BACnet PTEC Unit Conditioner (Fan Coil) Controller
DS-RP-B Data Sharing-ReadProperty-B •
DS-RPM-B Data Sharing-ReadPropertyMultiple-B •
DS-WP-B Data Sharing-Write Property-B •
DM-DDB-B Device Management-Dynamic Device Binding-B •
DM-DOB-B Device Management-Dynamic Object Binding-B •
DM-DDC-B Device Management-DeviceCommunicationControl-B •
DM-RD-B Device Management-ReinitializeDevice-B •
DM-BR-B Device Management-Backup and Restore-B •
DM-OCD-B Device Management-Object Creation and Deletion-B •
BACnet Programmable TEC (PTEC)
Siemens Industry, Inc. 191
BACnet PTEC Unit Vent Controller
BACnet Standardized Device Profile Product Device Profile BTL Tested
BACnet PTEC Unit Vent Controller
BACnet Application-Specific Controller (B-ASC) •
Supported BACnet Interoperability Building Block (BIBBs) Product BIBB Name BTL
Tested BACnet PTEC Unit Vent Controller
DS-RP-B Data Sharing-ReadProperty-B •
DS-RPM-B Data Sharing-ReadPropertyMultiple-B •
DS-WP-B Data Sharing-Write Property-B •
DM-DDB-B Device Management-Dynamic Device Binding-B •
DM-DOB-B Device Management-Dynamic Object Binding-B •
DM-DDC-B Device Management-DeviceCommunicationControl-B •
BACnet PTEC Heat Pump Controller
BACnet Standardized Device Profile Product Device Profile BTL Tested
BACnet PTEC Heat Pump Controller
BACnet Application-Specific Controller (B-ASC) •
Supported BACnet Interoperability Building Block (BIBBs) Product BIBB Name BTL
Tested BACnet PTEC Heat Pump Controller
DS-RP-B Data Sharing-ReadProperty-B •
DS-RPM-B Data Sharing-ReadPropertyMultiple-B •
DS-WP-B Data Sharing-Write Property-B •
Chapter 6–BACnet FLN Devices
192 Siemens Industry, Inc.
Product BIBB Name BTL Tested
DM-DDB-B Device Management-Dynamic Device Binding-B •
DM-DOB-B Device Management-Dynamic Object Binding-B •
DM-DDC-B Device Management-DeviceCommunicationControl-B •
BACnet PTEC Extended I/O Controller
BACnet Standardized Device Profile Product Device Profile BTL Tested
BACnet PTEC Extended I/O Controller
BACnet Application-Specific Controller (B-ASC) •
Supported BACnet Interoperability Building Block (BIBBs) Product BIBB Name BTL
Tested BACnet PTEC Extended I/O Controller
DS-RP-B Data Sharing-ReadProperty-B •
DS-RPM-B Data Sharing-ReadPropertyMultiple-B •
DS-WP-B Data Sharing-Write Property-B •
DM-DDB-B Device Management-Dynamic Device Binding-B •
DM-DOB-B Device Management-Dynamic Object Binding-B •
DM-DDC-B Device Management-DeviceCommunicationControl-B •
DM-RD-B Device Management-ReinitializeDevice-B •
DM-BR-B Device Management-Backup and Restore-B •
DM-OCD-B Device Management-Object Creation and Deletion-B •
BACnet Programmable TEC (PTEC)
Siemens Industry, Inc. 193
BACnet PTEC Dual Duct Controller
BACnet Standardized Device Profile Product Device Profile BTL Tested
BACnet PTEC Dual Duct Controller
BACnet Application-Specific Controller (B-ASC) •
Supported BACnet Interoperability Building Block (BIBBs) Product BIBB Name BTL
Tested BACnet PTEC Dual Duct Controller
DS-RP-B Data Sharing-ReadProperty-B •
DS-RPM-B Data Sharing-ReadPropertyMultiple-B •
DS-WP-B Data Sharing-Write Property-B •
DM-DDB-B Device Management-Dynamic Device Binding-B •
DM-DOB-B Device Management-Dynamic Object Binding-B •
DM-DDC-B Device Management-DeviceCommunicationControl-B •
DM-RD-B Device Management-ReinitializeDevice-B •
DM-BR-B Device Management-Backup and Restore-B •
DM-OCD-B Device Management-Object Creation and Deletion-B •
BACnet PTEC Constant Volume Controllers
BACnet Standardized Device Profile Product Device Profile BTL Tested
BACnet PTEC Constant Volume Controllers
BACnet Application-Specific Controller (B-ASC) •
Supported BACnet Interoperability Building Block (BIBBs) Product BIBB Name BTL
Tested BACnet PTEC Constant Volume
DS-RP-B Data Sharing-ReadProperty-B •
Chapter 6–BACnet FLN Devices
194 Siemens Industry, Inc.
Product BIBB Name BTL Tested
Controllers DS-RPM-B Data Sharing-ReadPropertyMultiple-B •
DS-WP-B Data Sharing-Write Property-B •
DM-DDB-B Device Management-Dynamic Device Binding-B •
DM-DOB-B Device Management-Dynamic Object Binding-B •
DM-DDC-B Device Management-DeviceCommunicationControl-B •
DM-RD-B Device Management-ReinitializeDevice-B •
DM-BR-B Device Management-Backup and Restore-B •
DM-OCD-B Device Management-Object Creation and Deletion-B •
BACnet Programmable VAV with Chilled Beam, CO2-Based Demand Control Ventilation, Floating or Analog Output
BACnet Standardized Device Profile Product Device Profile BTL Tested
BACnet Programmable VAV with Chilled Beam, CO2-Based Demand Control Ventilation, Floating or Analog Output
BACnet Application-Specific Controller (B-ASC) •
BACnet Programmable TEC (PTEC)
Siemens Industry, Inc. 195
Supported BACnet Interoperability Building Block (BIBBs) Product BIBB Name BTL
Tested BACnet Programmable VAV with Chilled Beam, CO2-Based Demand Control Ventilation, Floating or Analog Output
DS-RP-B Data Sharing-ReadProperty-B •
DS-RPM-B Data Sharing-ReadPropertyMultiple-B •
DS-WP-B Data Sharing-Write Property-B •
DM-DDB-B Device Management-Dynamic Device Binding-B •
DM-DOB-B Device Management-Dynamic Object Binding-B •
DM-DDC-B Device Management-DeviceCommunicationControl-B •
DM-RD-B Device Management-ReinitializeDevice-B •
DM-BR-B Device Management-Backup and Restore-B •
DM-OCD-B Device Management-Object Creation and Deletion-B •
For more information on the PTEC product line, refer to the following PTEC documents, which are posted on InfoLink:
• BACnet Programmable TEC (PTEC) Technical Reference manual • BACnet Programmable TEC (PTEC) Tool User Manual • BACnet Programmable TEC (PTEC) Configuration and Sizing Guidelines • Chilled Beam Controller • Constant Volume Controller • Dual Duct Controller • Extended I/O Controller • Heat Pump Controller • Terminal Box (VAV) Controller • Unit Conditioner (Fan Coil) Controller • Unit Vent Controller • VAV with Series Fan and 3-Stage Electric Heat Controller
Chapter 6–BACnet FLN Devices
196 Siemens Industry, Inc.
Basic Product Description
Siemens Industry, Inc. 197
Chapter 7–BACnet Field Panel Web Server Chapter 7 addresses the BACnet Field Panel Web Server. The Field Panel Web Server provides a Web-based Graphical User Interface compatible with BACnet® networks that is hosted directly from APOGEE BACnet Field Panels. The Web server allows remote access through an intuitive Web-based user interface to monitor, control, command and configure the Siemens building automation system. This chapter includes the following topics:
• Basic Product Description
• Web Server Communication
• Network Bandwidth Effect
• Web Server Limitations
• Web Server Access and Security
• Remote Access to Building Automation System
Basic Product Description The Field Panel Web Server (a browser-based user interface (UI)) and the Siemens Launch Pad (an Adobe AIR-based client application), once launched, appear the same and perform the same functions. In this chapter, they are jointly refered to as the Web Server.
The Web Server provides command and control access to the building automation system. It allows users to interact with Siemens Ethernet BACnet Field Panels equipped with Web Services, and provides a more intuitive user interface for database interaction in comparison to line-by-line command prompts. The Web Server supplies a web-based graphical user interface for use in configuring BACnet networks and creating/editing Points, Trends, Schedules, PPCL, Event Enrollments, Notification Classes, Remote Recipient Lists, and SMTP Configuration (for sending out e-mails). The web server is designed as a small system UI and will function with any BACnet/IP-enabled PXC controller with Firmware Revision 3.2.3 or later. Figure 68 shows the architecture of a BACnet network where the Field Panel Web Server could be used.
Field panels include PXC Modular controllers, PXC Compact 36 controllers, and PXC Compact 16 and 24 controllers. The field panels operate stand-alone or networked to perform complex control, monitoring, and energy management functions without relying on higher-level processors.
Chapter 7–BACnet Field Panel Web Server
198 Siemens Industry, Inc.
The Web Server will automatically connect and display data from any BACnet/IP PXC Modular or PXC Compact controller on the network that has the Web Services enabled. In order to observe Graphics and Changes of Value (COV’s) from a given PXC panel requires a license to be purchased. As of firmware revision 3.2.5, the license is only needed to receive COV data from the panel (needed for graphics). All other features of the Web Server are available by default. Web pages are populated via HTTP data services, with data from each controller and asocated BACnet MS/TP or P1 Field Level Network (FLN) devices. The use of web services for communication ensures that any web browser with ADOBE Flash is able to access the Field Panel Web Server, and any smart phone loaded with the Facility-to-Go mobile application is able to access and display near-real-time system values along with affording convenient command/override capabilities via always-available smart phone access.
A Field Panel Web server can accommodate an unlimited number of user accounts and simultaneous users. Each user account can be defined with customized levels of privileges and access to the system.
The field panel Web Server User Interface software must be installed on at least one PXC-36 or PXC Modular controller on each network. Any new client device (web browser) accessing the system makes an initial connection to the controller where the UI software files are installed, and can then access data from all controllers that have the web services enabled.
The Launch Pad application is installed on the hard drive of a computer that is connected to a BACnet network.
Web Server Communication
Siemens Industry, Inc. 199
Figure 68: Architecture of Field Panel Web server.
The information in following sections is taken from the Field Panel Web Server Technical White Paper published in November 2011. Additional information on the Field Panel Web Server can also be found in the Technical Specification Sheet and User Guide.
Web Server Communication All versions of field panels can co-exist on an Ethernet network; however, only BACnet field panels with Web Services enabled can participate in a BACnet system with Web access.
Web Server user interface communications (Web client to field panels with Web Services enabled) uses HTTP-based TCP/IP communication through Web Services in the BACnet field panels.
Network Bandwidth Effect Siemens BACnet components do not add significant overhead to a TCP/IP network. Network bandwidth utilization is variable and dependent upon the number of panels, network speed, and network architecture.
Chapter 7–BACnet Field Panel Web Server
200 Siemens Industry, Inc.
On a 100-base T or faster network, typical network usage will be less than 2%.
Short burst of traffic is possible, triggered by system events like alarms. These messages can be configured as local broadcasts, global broadcasts, or directed with confirmation. In addition to these event-triggered communications, periodic system heartbeat messages between the BACnet devices (called e-ping) are relatively small and do not contribute much to the occupied bandwidth.
Siemens BACnet Web Server communication begins with an initial connection to one panel to upload the client application (approximately a 2 MB file). The client application is then executed inside a Web browser as a Flash® application. The client application will then establish a connection to each Web Services-enabled BACnet field panel to learn the configuration of the system. As a minimum, Change-Of-Value (COV) subscriptions for system status points are created to every Web Services-enabled field panel in the system and checked every 15 seconds as long as a user is logged in. If the user opens a graphic with dynamic linked points, these points will be added to the COV table in the controller where the points reside and also updated every 15 seconds. If a user closes the graphic, the COV subscription for the points in the graphic will be removed. If the user logs off or gets logged off then all COV updates will stop.
Web Server Limitations There is no hard limit on how many users can log into a system simultaneously. However, the available resources in the controller will have to be shared among these users, and a lack of system resources will lead to a system slow-down. The most resource-intensive tasks are running point logs, and if more than two users run a point log from the same controller at the same time, a temporary degradation of control performance can be expected. As soon the reports are finished, the system performance will return to normal.
There is also no hard limit on how many BACnet field panels can be part of a Web-based control system. There is a recommended limit of 10 controllers, which was used as guideline for our system tests and performance tests. As the number of panels on the system increases, so will the login and caching refresh times.
Web Server Access and Security • BBMDs are only for BACnet UDP broadcast traffic and not required for Web
Server HTTP traffic. • BACnet Web Services rely on an encrypted user ID/password combination to
restrict access. A unique session ID cookie is created after a successful log-in from a Web client and used throughout a session as authentication for every
Web Server Access and Security
Siemens Industry, Inc. 201
HTTP request sent to the panel. Without a valid session ID cookie, the panel will discard incoming requests and not respond.
• Only port 80 is required for accessing Web Services on field panels. Port 80 for access is fixed and cannot be changed.
• Communication is though HTTP “GET” and “POST” messages. Most communication between client and server is accomplished with POST messages with XML data in the requests and responses.
• FTP (port 21) and Telnet (port 23) can be used for configuration and upgrading of field panels but is not required for operation and can be disabled if required.
• The Field Panel Web Server can be configured with a Public (Internet) IP address which has the potential to allow unauthorized access. Siemens Industry Inc recommends to use Private IP addresses only. If a Public (Internet) IP address has to be used the IT department responsible for the site has to be involved.
• User accounts are customizable with varying privileges and levels of access. It is strongly recommended to follow the least rights strategy and only assign the users the necessary rights they need to perform their duties. There are three default account IDs: “LOW”, “MED”, and “HIGH” with respective default passwords “LOW”, “MED”, and “HIGH”. The default accounts cannot be deleted. As these default logins are known, the default passwords need to be changed during commissioning to avoid unauthorized access.
• User IDs and passwords are not case sensitive and do not have a requirement of different character types. User account names can be between 1 and 40 characters, user IDs can be between 1 and 4 characters and passwords can be between 3 and 15 characters. All letters A through Z, and numbers 0 through 9 can be used. Do not use #, ?, or *. Only the user ID and password is used for authentication.
• User accounts need to be managed and kept current. If the access needs of a user changes (move to a different position, leaving the organization) then the change needs to be made immediately.
• It is strongly advised that each user gets a separate user account (not one username and password for all managers or site electricians).
• BACnet field panels do not support SSL. • Cookies are used to store the users’ consent in the EULA. If cookies are not
enabled, the user has to acknowledge the EULA at every browser start and log-in.
• Login is accomplished by indicating the following for the Hostname, Username, and Password:
o Hostname – (Launch Pad only) enter the Name or IP address of the PXC that is connected to the BACnet network
Chapter 7–BACnet Field Panel Web Server
202 Siemens Industry, Inc.
o Username – enter the username of a valid user account with appropriate access priviledges
o Password – enter the password of a valid user account with appropriate access priviledges
Figure 69: Web Server Logon Window.
Figure 70: Launch Pad Logon Window.
Remote Access to Building Automation System
Siemens Industry, Inc. 203
Remote Access to Building Automation System To access a building automation system from a public network (like the Internet), Siemens Industry, Inc. recommends using ISA 62443.03.03 Level 2 compliant hardware and software as a minimum. By using ISA 62443.03.03 Level 2 compliant hardware and software configured to the network’s settings, you can connect to the private network from any location with Internet access with a minimal level of security.
There are many types of remote access, and it is up to the local IT department to select the appropriate solution for them. If asked for support, Siemens should always use caution and suggest a minimum of ISA 62443.03.03 Level 2 compliant remote access system.
Be sure to contact the highest level in the IT department associated with the site to select the securest remote access system.
If no IT department exists, Siemens Industry, Inc. recommends using a router with a built-in VPN server that is to be managed by the customer or Siemens Industry, Inc. Siemens Building Technologies has tested the EtherGuard secure hardware VPN router with APOGEE products. This device can be used to allow secure data exchange in both directions between an outside location and the BAS. Please contact Udo Drafz ([email protected]) for more information. Use the example image as shown in Figure 71 and information given in the Field Panel Web Server White Paper as a guide.
Chapter 7–BACnet Field Panel Web Server
204 Siemens Industry, Inc.
Figure 71: Example of a VPN Solution with a Cisco RV0xx Series 10/100 VPN Router.
Field Panel Web Server and Lauch Pad look nearly identical once the user is logged in.
Once logged in, the user has access to all information from all PXC panels that have the web server application enabled and access rights, and a screen with a node table will appear in the left window pane with the main menu window (see Figure 73). Figure 74 – Figure 78 show the various windows used for creating and editing Points, Trends, Schedules, Notification Classes, and configuring panels, ALN’s and FLN’s, and setting up e-mail recipients, users and user passwords.
Remote Access to Building Automation System
Siemens Industry, Inc. 205
Chapter 7–BACnet Field Panel Web Server
206 Siemens Industry, Inc.
Figure 72: Launch Pad Main Menu Display.
Figure 73: Field Panel Web Server Main Menu Display.
Remote Access to Building Automation System
Siemens Industry, Inc. 207
Figure 74: Grouping for Creating/Editing Schedule, Command Calendar.
Figure 75: Grouping for Creating/Editing Notification Class, Remote Recipient List, SMTP Configuration.
Chapter 7–BACnet Field Panel Web Server
208 Siemens Industry, Inc.
Figure 76: Grouping for Creating/Editing Panel Configuration, ALN Node Table, and Panel Time.
Remote Access to Building Automation System
Siemens Industry, Inc. 209
Figure 77: Grouping for Creating/Editing FLN and TEC Initialization.
Figure 78: Grouping for Creating/Editing Users and Changes to User Password.
Siemens Industry, Inc. 211
Chapter 8–Insight BACnet Option Chapter 8 describes the Insight BACnet Option and the changes to the Insight software since Revision 3.2. It discusses the following topics:
• Insight BACnet Option
• Insight Changes for BACnet
Insight BACnet Option The BACnet Client Option provides communication with both the APOGEE Automation System and third-party BACnet devices and systems, enabling functionality that:
• Monitors and commands BACnet objects
• Establishes BACnet schedules and calendars
• Backs up databases in BACnet devices
• Receives and acknowledges BACnet alarms
• Establishes and reads BACnet trend logs
The BACnet Server Option can export proprietary protocol APOGEE point information as BACnet objects, so that a third-party BACnet client system may monitor and command APOGEE points, and monitor and acknowledge alarms within APOGEE proprietary networks and field panels.
For details on how each of these options interface with a BACnet network, see APOGEE Communication with BACnet in Chapter 4–BACnet Communications. Also see, the Insight 3.x Release Notes and Getting Started in the APOGEE Insight 3.x Help.
Native BACnet and B-OWS
The Insight Revision 3.7 or later software with the BACnet Option can be considered a native BACnet workstation because it conforms to the BACnet Operator Workstation (B-OWS) specification.
Chapter 8–Insight BACnet Option
212 Siemens Industry, Inc.
Backward Compatibility
The addition of the BACnet option does not compromise APOGEE Automation System functionality or backward compatibility. All applications relating to APOGEE P2 ALN field panels, such as enhanced alarming, trending, point teams, scheduling, SSTO, PPCL, backup/restore, etc. are supported. Other Insight options such as OPC support, InfoCenter, specials, Fire/Security Workstation, RENO, and APOGEE GO are also supported.
Insight Features for BACnet This section lists the features in Insight for BACnet. The emphasis is on the Insight software user interface (look and feel) because the details for using the dialog boxes are in the APOGEE Insight 3.x Help and other chapters of this application guide.
Alarms
This section covers how the Insight software supports BACnet from a user's standpoint. For more detail about the operation of BACnet alarming, see Chapter 10–BACnet Alarming.
Point Priority
The Point Priority column in the BACnet Command Priority Array Dialog Box displays the BACnet point priority for BACnet points.
Initials
The BACnet client option always displays BAC as the initials when an alarm is acknowledged. The correct user initials are displayed for alarms that are acknowledged by the Insight workstation, but alarms that are acknowledged by a foreign BACnet system display BAC. The initials SYS are displayed for alarms that do not require acknowledgements (similar to previous revisions of Insight software).
Alarm Acks
In BACnet, an object keeps an ack required flag for each state separately. The three states are To-OffNormal, To-Fault, and To-Normal. Each one of these states can require a separate acknowledgement. If the user acknowledges an item in the Insight alarm window, up to three acknowledgements are sent to the BACnet device (the BACstac keeps track of how many need to be sent). There is no means to acknowledge a single state. Conversely, if a third-party workstation acknowledges only one state when three states require acknowledgement, the Insight workstation will not display the alarm as acknowledged until all three states have been acknowledged.
Insight Features for BACnet
Siemens Industry, Inc. 213
Event Information and Alarm Summary
The Insight software supports the BACnet Get Event Information service (labeled getinformation). This service allows a BACnet field panel to be periodically interrogated for all of its alarms. If the BACnet field panel supports these services, the Insight workstation will learn and display any alarms for that device. It does this when it starts up and after a field panel returns from failure. This feature is optional on a field panel, so not all field panels will do this. APOGEE BACnet field panels support this service. The Event Information service replaces Alarm Summary. The Insight software still supports the Alarm Summary for compatibility with BACnet non-APOGEE field panels.
In addition to the above, the Insight workstation looks though its existing list of alarms and makes sure the alarms are current. For example, if Point A is in alarm and needs to be acknowledged, then the field panel that contains Point A fails and comes back later with Point A not in alarm and not needing to be acknowledged, then the Insight alarm window will update with this new information. It will show the point's new status and show the point as acknowledged.
Unknown BACnet alarms
If an alarm displays for a point that is not known or has been deleted, then the name of the point will be the encoded name, such as BAC_1234_AO_3 (BACnet device Instance Number 1234, Analog Output Instance 3).
A registry key has been added to allow alarms for object types that are not supported by Insight as points to be displayed. The key is called ShowAlarmsForAllObjects and is under the client key.
• If the key is set to 1, then the Insight workstation will display alarms for Life Safety Points, Life Safety Zones, Loops, etc.
• If the key is 0 (the default), the Insight workstation will only show alarms for the standard point types Binary Input, Binary Output, Binary Value, Analog Output, Analog Input, Analog Value, Multistate Input, Multistate Output, Multistate Value, Event Enrollment (BI, BO, BV, AO, AI, AV, MI, MO, MV, EE).
BACnet Text Messages
In BACnet, confirmed/unconfirmed text messages can be sent to a device. If the Insight workstation receives any messages, they will be displayed in the ALN messages pane of the alarm window. The messages will also be logged in the system activity log.
Chapter 8–Insight BACnet Option
214 Siemens Industry, Inc.
Alarm Priority
The alarm priority found in a point's Notification Class object has a value from 0 to 255. This alarm priority is mapped to the six APOGEE alarm levels (Table 41).
Table 41. BACnet Alarm Priority mapping to APOGEE.
BACnet Notification Class Alarm Priority APOGEE Alarm Level Mapping
1 – 31 A1 (life safety)
32 – 63 A2 (property safety)
64 – 95 A3 (supervisory)
96 – 127 A4 (trouble)
128 – 191 A5 (high priority alarms)
192 – 255 A6 (low priority alarms)
Alarms A1 through A6 display for BACnet points in all applications that display priority. Table 42 shows example alarm displays.
Table 42. BACnet Alarm Displays.
BACnet alarm level Displayed as *A6*, for example. (Similar to APOGEE enhanced alarms.)
BACnet normal state Displayed as -N- regardless of the TO-NORMAL priority.
BACnet fault state Displayed as *F* regardless of the TO-FAULT priority.
Alarm Messages
BACnet supports sending an unlimited-sized text message with an alarm. The Insight workstation truncates the message to 200 characters. These messages are numbered and defined in the BACnet Field Panel Definition. Then, a message number can be entered in a point definition. (These are the same messages that are used for APOGEE enhanced alarms).
If the BACnet Field Panel Definition does not have any messages defined (only a message #0), one can be defined for the point in the Point Editor (Alarm Type, Alarm Properties), and the Insight alarm window will use that one. The message #0 triggers the Insight workstation to look in its message database.
APOGEE GO
All applications that display point priority will display BACnet priority for BACnet points.
Insight Features for BACnet
Siemens Industry, Inc. 215
Attribute Duplicator
The following BACnet properties (attributes) can be copied by the Attribute Duplicator if the source and destination point are APOGEE BACnet points:
• Notification Class
• Standard Alarm Message number
• Event Enable Bits
• Relinquish Default
In Insight Revision 3.9.1, Deadband and Time Delay properties have been added to the Properties to Copy section of the Attribute Duplicator screen for the selected source BACnet point. See Figure 79.
If a BACnet point which supports intrinsic reporting is selected as the source point, the Time Delay field can be copied to the relevant BACnet destination point, if selected in the list of properties.
If an analog input or output BACnet point which supports intrinsic reporting is selected as the source point, the Deadband field can be copied to the relevant BACnet destination point, if selected in the list of properties.
Figure 79. Attribute Duplicator Dialog Box.
Chapter 8–Insight BACnet Option
216 Siemens Industry, Inc.
BACnet Export Map Entries Tool
From the Tools menu, select the BACnet submenu, and select View BACnet Export Map Entries. The View BACnet Export Map Entries dialog box displays (Figure 80) all of the APOGEE proprietary points that you are exporting to the BACnet virtual network through the BACnet Server Option.
Figure 80. View BACnet Export Map Entries Dialog Box.
BACnet Communication Diagnostic
From the Tools menu, select the BACnet submenu and then select BACnet Communication Diagnostic to display the BACnet Communication Diagnostic dialog box (Figure 81). You can use this tool to decide the best time for the APDU timeout. It can also be used to see how slow some devices are communicating on the BACnet network. For more details, see Chapter 12-BACnet Tools.
Insight Features for BACnet
Siemens Industry, Inc. 217
Figure 81. BACnet Communication Diagnostic Dialog Box.
With this tool you can:
• Run the test on a single device or select all BACnet devices.
• Enter up to a 3-digit timeout period. The default of 30 seconds should be sufficient for most networks.
• Enter up to a 2-digit number of attempts.
• Send a read property when you press Begin and the Insight application will display the number of seconds it took for that device to respond and a recommended time for the APDU timeout. If it takes longer than the BACnet APDU timeout entered, The request timed out message displays for that device.
• Press the Stop button to cancel a test in progress.
• Press the Clear button to empty the Results list.
• View the setting that the Insight workstation has for each device in the Current APDU Timeout column.
• Set the ADPU timeout for a device in any row you select to the Suggested APDU Timeout by pressing Set APDU Timeouts. If you select any rows that had an error, they will be skipped and the APDU timeout will not be changed for that device.
Chapter 8–Insight BACnet Option
218 Siemens Industry, Inc.
BACNET Object Browser
The BACnet Object Browser is an Insight application that allows you to view and write to the BACnet objects and their properties using generic windows and dialog boxes. This application is accessed from the BACnet submenu of the Tools menu in the System Profile application when you select either a ALN or a field panel in the tree.
Figure 82 shows an example of viewing the properties of a device object using the Object Browser. A navigation pane on the left side shows the hierarchy of the BACnet network and the device the user is currently viewing. The right panel displays data about whatever item is selected in the tree. In Figure 82, a BACnet device object has been selected in the tree to display a device property view on the right. Selecting a point object in the tree displays an object property view on the right. Error messages may display at the bottom of the screen, if applicable. Various filtering actions are also available within these screens.
Figure 82. Viewing Device Object Properties with the Object Browser.
Insight Features for BACnet
Siemens Industry, Inc. 219
To use this application, you must have either Read-level access (which allows viewing and browsing to any available devices and objects) or Configure-level access (which allows writing properties, importing points, reinitializing devices, or using device communication controls as needed) to the BACnet Object Browser. User access level settings are configured through the User Accounts application.
BACnet Browser Features
Other features of the BACnet Browser include:
• A View Options dialog box that lets you select what properties you want displayed by default (set in registry upon exiting).
• A Tools menu that provides dialog boxes to:
− Send Who-Is messages
− Send Who-Has messages
− Write properties of objects
− Perform device communication control (as described in Chapter 12-BACnet Tools)
− Re-Initialize a device
− Import Points
• There are 20 different view types. Each view can be printed and/or saved as a .csv file. These views appear in the View box at the top of the screen based on what is selected in the tree control and list control. For example, View Device Properties is displayed in the View box (Figure 82).
• Most of the simple data types as well as the complex data types can be edited. The simple data types include strings, numbers, Boolean values, Bit strings, times, and date ranges. The complex data types include Weekly Schedules, Exception Schedules, Recipient Lists, Object Reference Lists, Action Lists and Calendars. (You must have configure access to the Browser to use Write Property.)
• The browser has its own functional access level that can be set per user in the User Accounts application. There are two levels:
− Read access–This lets you read/browse everything, but you cannot do write properties, import points, reinitialize a device or use device communication control commands.
− Configure access–This lets you do everything.
• Display and edit proprietary properties. (Only the simple data types can be edited–unsigned, float, Boolean, string, and signed.)
Chapter 8–Insight BACnet Option
220 Siemens Industry, Inc.
• Display proprietary objects in their own folder. (The write property cannot be used.)
BACnet Browser Limitations
Limitations of the browser include:
• The ability to only edit existing objects. You cannot create new objects or delete objects from the browser.
• Some data types cannot be edited. The write property button will remain gray if you are on a property that cannot be written by the browser.
Commander
When a BACnet point is selected from the object selector or typed in, the point Commander dialog box changes slightly. Instead of the non-BACnet priority buttons, you will see Set, Relinquish, and Advanced buttons and a drop-down list for BACnet priority (Figure 83).
Insight Features for BACnet
Siemens Industry, Inc. 221
Figure 83. Point Commander Dialog Box.
• The drop-down list only contains priorities that the user has authorization to command (based on their user account setup).
• The Advanced button displays the current Command Priority Array. It is enabled only for point types that can have a Command Priority Array. (AO, BO, MO, AV, BV, MV). Also, the Relinquish button is enabled only for points with Command Priority Arrays.
• To command a point the user must select Set or Relinquish. If the point has a Command Priority Array, then the priority slot displayed will be commanded or relinquished. If the point does not have a Command Priority Array, the present value of the point will be written.
• Out of Service will be enabled for third-party BACnet points and APOGEE input points only.
Chapter 8–Insight BACnet Option
222 Siemens Industry, Inc.
• The command priority defaults to Manual Operator (the priority defined in Syspro as operator). If the user doesn’t have access to this level (defined in user accounts), it will default to the next lower priority (higher in number) that the user has access to. If the user does not have access to a lower priority, then the next higher one will be the default.
• Reset Totalization is supported in BACnet. Only binary points can be totalized.
• Alarm by command and ODSB are not supported in BACnet and will be grayed out.
• Clicking on the Advanced button displays the BACnet Command Priority Array (Figure 84).
Figure 84. BACnet Command Priority Array.
• The current values for all the Command Priority Array slots are displayed.
• Users can relinquish any priority level that they have access to (from user account setup). Levels that the user does not have access to are grayed.
• The actual relinquish happens after the point command (not when clicking OK to this Command Priority Array dialog box).
Insight Features for BACnet
Siemens Industry, Inc. 223
Database Transfer
Progress Tab
In the Database Transfer dialog box, new BACnet databases have been added to the Progress tab. To make room, the four SSTO databases have been combined into one counter, and the TIU counter has been removed (there is only one TIU and only on pre-APOGEE panels). The four counters at the bottom have been added for BACnet (Figure 85).
With Insight 3.9.1 or later, the Database Transfer application has been enhanced to upload and download BACnet FLN device information to a field panel that resides on the BACnet/IP or BACnet MS/TP ALN.
Beginning with Insight 3.10, the Database Transfer application supports the individual upload and download of Event Enrollment Objects for Siemens BACnet panels. For third-party panels, Event Enrollment Objects can only be uploaded and downloaded through Atomic Backup and Restore.
Chapter 8–Insight BACnet Option
224 Siemens Industry, Inc.
Figure 85. Database Transfer Dialog Box.
Log Tab
Support has been added to display information as BACnet databases are uploaded and downloaded.
Upload Selected Dialog
New BACnet databases have been added to the upload selected database dialog box. You can selectively upload BACnet Schedules, Commands, Calendars, and Notification Classes.
Insight Features for BACnet
Siemens Industry, Inc. 225
Object Types
Two new object types will be uploaded and represented as points. The Trend log object will now get uploaded and represented as a virtual LDO. The Command object will be uploaded as a LENUM point. This is for third-party panels only.
Backup and Restore
Some BACnet devices will support a backup and restore of their database. Two buttons have been added to the toolbar (and menus) to perform these operations (Figure 86).
On a backup, the Insight workstation will store a single copy of the device database in the ATOM database. Any subsequent backups will overwrite the previous one. On a restore, Insight workstation will reinitialize the device and send down the last backup. The status of the backup and restore operation will be displayed in the log panel of the Database Transfer application. Users need configure access to database transfer to do a backup or a restore.
Some field panels, including those of Siemens, require a password. The user must enter this password in the BACnet Field Panel Definition dialog box in System Profile. For Siemens field panels, the password is the high account password.
Figure 86. Database Transfer Dialog Box for Backup/Restore.
Cloaked Panels will not display in the panel list.
Chapter 8–Insight BACnet Option
226 Siemens Industry, Inc.
Dynamic Plotter
Dynamic Plotter supports BACnet points. With Insight Revision 3.9.1 and later, the Dynamic Plotter supports plotting BACnet Trend Log Object data from multiple devices.
Error Messages
The Message Destination Assignments selection on the System menu allows users to display error message text. The Message Destination Assignments dialog box (Figure 87), has five entries for BACnet. You can control which alarm windows display these messages in the ALN message pane of the alarm window. The BACnet message types default to destination zero (0).
Figure 87. Message Destination Assignements Dialog Box.
BACnet ALN Sorting Options
The BACnet ALN Sorting Options selection on the View menu allows you to determine how to sort devices in the tree.
Insight Features for BACnet
Siemens Industry, Inc. 227
Figure 88. BACnet ALN Sorting Options Dialog Box.
The BACnet ALN Sorting Options dialog box (Figure 88) provides three choices for sort order. For each choice, you can also optionally display other fields. This setting is saved per user in the Insight user’s account.
BACnet Multiple Device Editing
The BACnet Multiple Device Configuration selection on the Tools menu displays the BACnet Multiple Device Configuration dialog box (Figure 89) that allows you to set some device properties across a list of selected devices.
Chapter 8–Insight BACnet Option
228 Siemens Industry, Inc.
Figure 89. BACnet Multiple Device Configuration Dialog Box.
This feature allows the following functions:
• The list cannot be empty and removes duplicates automatically.
• The Add Devices button displays the Object Selector, which shows cloaked devices so you can uncloak them, if desired.
• You must select at least one checkbox.
• The same limits are enforced as in the Advanced Settings dialog box, which is accessed from the Field Panel Definition dialog box via the Advanced Settings button.
• A summary of errors is provided after the operation completes.
Insight Features for BACnet
Siemens Industry, Inc. 229
Other System Profile BACnet Features
Other System Profile BACnet features include:
• Insight systems can be added under BACnet ALNs.
• BACnet menu items are hidden if the Insight system does not have a BACnet license.
• BACnet Enable Device Discovery, under the Tools menu item, turns on and off the automatic discovery of BACnet panels. A toolbar button also turns on and off the automatic discovery of BACnet panels. See Chapter 4-BACnet Communications for more details about device discovery.
• Global Broadcast Who-Is, under the Tools menu item, is enabled for an Insight system with a BACnet ALN or a BACnet ALN selected. Selecting this item sends a Who-Is on the network. This feature works with device discovery to help discover BACnet panels. There is also a toolbar button for this. See Chapter 4-BACnet Communications for more details about device discovery.
• BACnet Object Browser, under Tools menu item, is enabled when a BACnet panel or ALN is selected that launches the BACnet Object Browser application. If a specific panel is selected, only that panel is opened in the browser. If a ALN is selected, then all panels are opened in the browser. (It takes longer to load all panels.)
• PX Compact is supported. The new panel type is called COMPACT and can be added to any P2/P3, dialup, Ethernet, or BACnet ALN. The new panel cannot have FLNs. There is a new icon for it.
Event Builder
Command Object
The Event Builder Application allows you to create, edit, and delete BACnet Command Objects (Figure 90). This capability is limited to Command objects in Siemens field panels. Editing a Command object is very similar to editing an APOGEE Zone. See Chapter 9-BACnet Scheduling for details about the Command object.
Chapter 8–Insight BACnet Option
230 Siemens Industry, Inc.
Figure 90. Event Builder BACnet Command Object Dialog Box.
When using the Command Object dialog box in Event Builder:
• The Instance Number defaults to –1 when creating a new command, which means the device will assign the Instance Number.
• An object name entry must be unique on that field panel.
• Create action text entries. You must provide action text (it doesn’t need to be unique and it can be blank). It is the index that is the key.
• Action text indexes cannot have gaps. You can only delete the last one in the list. If you attempt to delete one in the middle of the list, only the commands for that action index are deleted.
• When selecting an action text item, you can add actions in the lower list control. These actions are the commands to be executed when the Command object is commanded to the value of the index in the action text list. For example, if a user writes the Present Value property of the command object to 1, then all commands in the Action List for the Warm Up action will be executed.
• You can add modify, remove, move up, and move down actions.
• Selecting Add at the bottom of the Event Builder BACnet Command Object dialog box (Figure 90) displays the Edit Action dialog box (Figure 91) to enter a command line in the Action List.
Insight Features for BACnet
Siemens Industry, Inc. 231
Figure 91. Edit Action Dialog Box.
• Selecting a BACnet point from the Object Selector will automatically fill in most of the dialog box. If a point is selected, only the property ID, value, priority, delay, and quit on failure setting must be filled in.
• If you select a point that uses a state text table, its values are inserted into the value drop-down list.
• If a command is created for an APOGEE panel, the Property ID is set to Present_Value and disabled. For a third-party, the property can be selected (same for Array Index).
• Actions can be selected to perform copy/cut/paste operations.
• If you select more than one action and click Remove, an “Are you sure” message displays.
• If a single item is selected, it can be moved up or down in the list. This affects the order in which commands are executed.
• For a list of the most recently used items, select Command Objects from the Definition menu.
Chapter 8–Insight BACnet Option
232 Siemens Industry, Inc.
Event Printer
BACnet loader messages and BACnet Text messages are printed at the event printer.
Global Commander
Global commanding of BACnet points is not supported. In the Logical point tab, if a BACnet point is entered, an error message displays.
In Insight 3.9.1 or later, the Global Commander can support BACnet FLN devices on a field panel residing on a BACnet/IP or BACnet MS/TP ALN. The following operations are supported:
• Update initial values of a group of BACnet FLN devices
• Set the value of a group of BACnet FLN device subpoints
• Release a group of BACnet FLN device subpoints
• Initialize BACnet FLN devices
Graphics
The following enhancements are implemented for Insight graphics:
• All controls and tool tips that display point priority will display the BACnet priority for BACnet points.
• Commanding points using analog bars will use the default operator priority defined via System Profile.
Object Selector
Cloaked Panels
The Object Selector will not show cloaked panels. In Insight Revision 3.9.1 or later, the Object Selector application is enhanced to include BACnet FLN devices.
PXC Compact
An icon was added for PXC Compact.
PXC Compact Support
The PXC Compact field panel is similar to a MEC except that it cannot have FLNs. Anything you can do with MEC points, you can also do with PXC Compact points. They can be in Cross Trunk, and exported to BACnet. There is a limit to the number of points and PPCL lines that a PXC Compact can hold. Attempts to add more than the limits will not be acknowledged by the panel and this error will be displayed by the Insight workstation.
Insight Features for BACnet
Siemens Industry, Inc. 233
Point Details
Point Details displays the BACnet priority of a BACnet point. Also displayed are Object ID, Notification class, Reliability, and the Event Enable flags. Finally, a button in the dialog box allows you to quickly read another point.
Point Editor
Engineering Units
In BACnet, engineering units is an enumeration. This means users cannot type anything they want. Users must select units from a list of defined units in the Select Engineering Units dialog box (Figure 92).
Figure 92. Select Engineering Units Dialog Box.
There are three choices for units:
• Standard Unit–These units are grouped by category. The first drop-down box has a list of categories (length, mass, volume, etc.). When you select a Category of Units, the Units list on the right displays all the Units in that category.
• Proprietary Unit– You must enter an enumerated value. If you do not type in a specified enumerated unit, an error message displays.
• No Units–The unit’s string will be blank.
Chapter 8–Insight BACnet Option
234 Siemens Industry, Inc.
If you do not type in a specified enumerated unit, an error message displays.
BACnet Data
The point dialog boxes in Point Editor contain Object Instance number, Notification Class, Alarm Values, Relinquish Default, and the Event Enable flags, and Alarm Message number (Figure 93). The Event Enable flags are only for Alarmable points.
• The Point Editor dialog boxes include the following features and changes:
• Event enable flags are only valid for alarmable points.
• The BACnet object type is displayed in parenthesis in the title of each subordinate dialog box.
• You cannot change the Instance number once a point has been saved. If –1 is selected, the panel will assign a number and it will upload that information to the Insight workstation. The Instance Number will display the next time the point is opened.
• Totalization is only supported on binary input and binary value points in BACnet (LDI, LDO, L2SL, L2SP). The units are always seconds.
• Dynamic COV and Enhanced Alarms are not supported in BACnet.
• The Alarm Message # is the number of the enhanced alarm message number that was defined in the Field Panel Definition dialog box in System Profile. Use 0 to indicate to use the alarm message as defined locally in the point editor. See Chapter 10-BACnet Alarming for more details about the Alarm Message #.
BACnet FLN Device Points
Insight Revision 3.9.1 or later allows you to edit point attributes (descriptor, graphic, classification, informational text, analog output format, and access groups) in BACnet FLN devices. Changes made to these point attributes are used at the workstation but not saved to the field panel.
Support for Deadband, Time Delay, Minimum On Time, and Minimum Off Time BACnet Properties
Insight Revision 3.9.1 or later, four property fields are available for points created on a BACnet field panel that is supporting intrinsic reporting:
• The Deadband property–included for LAI and LAO points
• Time Delay–for all points
• Minimum ON Time and Minimum OFF Time properties–included for Binary Value and Binary Output object types only.
Insight Features for BACnet
Siemens Industry, Inc. 235
These properties are included in the Alarm Characteristics section in the Point window screen (Figure 93). These properties are viewable and can be edited on third-party field panels as well as Siemens panels.
Figure 93. Point Editor LAI (analog input) Dialog Box.
RENO Notification
In order to send RENO notification when a BACnet point goes into alarm, the notification class must have checked “Acknowledgement required” for TO-OFFNORMAL and/or TO-NORMAL. BACnet points can have notifications on ALARM_PRIORITY 1 through 6.
PXC Compact Slope/Intercept
The PXC Compact field panel type was added to the slope intercept calculator. The same values as the MEC are used. In addition to the sensors that a MEC supports, the PXC Compact supports the following sensors: Nickel 1K RTD, Platinum 1K RTD 385, and Thermistor.
CAUTION:
The Power MEC is now retired but is still sold on the repair parts (Rparts) program until October 1, 2017. Refer to POA-001.
Chapter 8–Insight BACnet Option
236 Siemens Industry, Inc.
Program Editor
PPCL is supported in APOGEE BACnet field panels. The Save As dialog box has additional fields for BACnet (Figure 94).
Figure 94. Program Editor Save As Dialog Box.
If a BACnet field panel is selected, the fields in the BACnet Settings section become enabled. PPCL Command Priority is the priority at which the PPCL program commands points. The PPCL Command Priority defaults to the value defined through System Profile.
Report Builder/Reports
Display BACnet Priority
All reports that display point priority display the BACnet priority (BN01 through BN16). If no priority is present, NONE is displayed.
Reports
Application Log Report
In Insight Revision 3.9.1 or later, the Application Log can display BACnet MS/TP FLN devices.
Panel Configuration Report
The Panel Configuration Report displays additional BACnet configuration data for APOGEE BACnet panels only. In Insight Revision 3.9.1 or later, the Panel Configuration Report can display BACnet MS/TP ALN/ALN and FLN information. See Figure 95 for an example.
Insight Features for BACnet
Siemens Industry, Inc. 237
Figure 95. Panel Configuration Report.
Panel Display Report
The Panel Display report displays panel status information for BACnet ALNs. PXC Compact is also supported.
Panel Point Definition Report
The Panel Point Definition report displays the Object ID, Notification Class, Relinquish Default, and Event Enable Flags, and priority array for BACnet points.
Panel Trend Data Detail Report
In Insight Revision 3.9.1 and later, the Panel Trend Data Detail Report includes filtering options for local and remote trending. The Definition Filter provides the option to filter by All, Local Trends, or Remote Trends.
Remote Trends only apply to BACnet points.
Chapter 8–Insight BACnet Option
238 Siemens Industry, Inc.
Panel Trend Definition Report
The Panel Trend Definition report shows the properties of a BACnet trend log object. Insight Revision 3.9.1 and later supports local and remote trending.
Point Definition Report
The Point Definition report displays the Object ID, Notification Class, Relinquish Default, and Event Enable Flags for BACnet points.
System Profile Report
The System Profile report displays information for BACnet ALNs and Panels. PXC Compact is supported.
Totalization Log Report
The Totalization Log report shows elapsed active runtime for BACnet binary points. It also shows the last reset time.
Trend Collection Report
With Insight Revision 3.9.1 and later, the Trend Collection Report supports local and remote trending.
Trend Definition Report
The Trend Definition report shows the properties of a BACnet Trend Log object. Insight Revision 3.9.1 and later supports local and remote trending.
Trend Data Detail Report
The Trend Data Detail report shows data for BACnet Trend Log objects that have been collected. There are trend status markers for BACnet in addition to the data loss marker already available for the APOGEE Automation System. The following entries are available:
• Log Enabled–indicates the beginning of data collection.
• Log Disabled–indicates the ceasing of data collection.
• Log Purged–indicates a user purged all the data at the device by writing a 0 to the record count property.
• Error–provides a BACnet error number. It indicates the device has problems collecting the data.
• Time Changed–indicates the local time of the device was changed. It is the offset in seconds by which that the time changed.
Insight Features for BACnet
Siemens Industry, Inc. 239
In Insight Revision 3.9.1 and later, the Trend Data Detail Report includes filtering options for local and remote trending. The Definition Filter provides the option to filter by All, Local Trends, or Remote Trends.
Remote Trends only apply to BACnet points.
Figure 96. Trend Data Detail Report Filtering Options.
Trend Interval Report
With Insight Revision 3.9.1 and later, the Trend Interval Report supports local and remote trending.
Trend Sample Report
With Insight Revision 3.9.1 and later, the Trend Sample Report supports local and remote trending.
Trend Summary Report
With Insight Revision 3.9.1 and later, the Trend Summary Report supports local and remote trending.
User Account Report
The User Account report displays a users functional access rights to the BACnet Browser. The users Command Priority Array access level is displayed.
Chapter 8–Insight BACnet Option
240 Siemens Industry, Inc.
Scheduler
See Chapter 9-BACnet Scheduling for details.
Event Log
BACnet loader messages and BACnet Text messages are logged in the System Activity log.
System Profile
BACnet MS/TP ALN Configuration
The Insight Revision 3.9.1 or later supports the ability to configure BACnet MS/TP ALN devices from the BACnet Field Panel Definition dialog box. APOGEE BACnet field panels, with Firmware Revision 3.1 or later, can reside on BACnet/IP or MS/TP networks.
Figure 97. Example of BACnet/IP and MS/TP Networks.
BACnet MS/TP FLN Configuration
Insight Revision 3.9.1 or later supports the ability to configure BACnet MS/TP FLNs, giving you a total of three FLN options, P1, LON (LonWorks technology), and MS/TP.
A BACnet MS/TP FLN is configured from the BACnet Field Panel Definition (Figure 108) and MS/TP FLN Settings (Figure 98) dialog boxes.
Insight Features for BACnet
Siemens Industry, Inc. 241
Only BACnet field panels with Firmware Revision 3.1 or later support this feature.
Figure 98. MS/TP FLN Settings Dialog Box.
Logical Grouping of BACnet FLN Devices
Insight Revision 3.9.1 or later supports adding BACnet FLN devices to BACnet field panels that contain Firmware Revision 3.1 or later.
BACnet FLN devices are logically or physically grouped on a BACnet MS/TP FLN. Groups of BACnet FLN devices can be a mix of either Siemens devices and/or third-party devices in a logical or physical grouping. This solution allows for existing networks with third-party devices to communicate with the BACnet FLN network.
Chapter 8–Insight BACnet Option
242 Siemens Industry, Inc.
Figure 99. Example: Logical Grouping of BACnet FLN Devices.
BACnet FLN Device Definition Dialog Box
BACnet FLN devices reside on a BACnet MS/TP network. When you define a BACnet MS/TP FLN device, several of its properties must be configured: Device Instance, Network Number, BACnet MAC Address, and the MS/TP Node type as either a Master or a Slave. You can also determine how initial values are established.
Insight Features for BACnet
Siemens Industry, Inc. 243
Figure 100. BACnet FLN Device Definition Dialog Box.
Once the BACnet FLN device is defined in the network, most fields in the dialog box can be modified. The System Name field or the Application field, however, cannot be edited. All other fields are editable. Since modifying fields does not change the attributes in the device itself, these fields should be used only to correct errors in defining the device.
If the device is no longer needed in the network, it can be deleted.
Application Initial Values
In Insight Revision 3.9.1 or later, the Application Initial Values dialog box (Figure 101) lists all of the points for the Application selected in the BACnet FLN Device Definition. This dialog box displays currently defined initial values and allows you to Set a new initial value for a point, Release a point’s initial value, or Update the initial values table.
The Application Initial Values dialog box is accessed by clicking the Initial Values button in the BACnet FLN Device Definition dialog box.
Chapter 8–Insight BACnet Option
244 Siemens Industry, Inc.
Figure 101. Application Initial Values Dialog Box.
Command Priority Array Strings
The BACnet Command Priority Array on the System menu displays the BACnet Command Priority Array dialog box (Figure 102). This dialog box allows you to edit the long and short versions of the strings that are displayed for the different BACnet Command Priority levels. The short strings are used throughout most of the system. The long strings are available in the Point Commander. You can also select the default priorities for Insight applications.
Figure 102. BACnet Command Priority Array Dialog Box in System Profile.
The operational features of the BACnet Command Priority Array dialog box include:
• The Edit button displays a dialog box that allows you to change the long and/or short version of the strings and select default priorities.
• Changes to Text take effect next time the Insight application starts since they are cached by applications.
Insight Features for BACnet
Siemens Industry, Inc. 245
• Default priorities are global data and should be replicated automatically to all panels. The Insight applications that use them will read them the next time they are started. (for example, Program Editor uses the PPCL priority).
BACnet Address Table
The BACnet Address Table selection on the System menu displays the BACnet Address Table dialog box (Figure 103). This dialog box allows you to assign addresses to devices (for example, MS/TP devices) and objects that do not report their addresses when asked. This table is used by the field panel to resolve devices or objects that might appear in PPCL.
Figure 103. BACnet Address Table Dialog Box in System Profile.
The operational features of the BACnet Address Table dialog box include:
• The list rejects duplicates. A duplicate is defined as having the same Device ID and Object ID.
• To erase an item in the list, select the item’s line and click Remove.
• The Modify button displays the BACnet Address Table dialog box (Figure 104) and allows you to modify some of the properties. You cannot modify the device ID or Object ID settings. To modify these, you must delete the line and add a new one.
• This address table is a new database type in the field panel. Entries added/removed will be sent to the field panel using replication.
• When changes have been made and the Cancel button clicked, a prompt to save the changes is displayed.
Chapter 8–Insight BACnet Option
246 Siemens Industry, Inc.
• When Add is clicked, the BACnet Address Table Entry dialog box displays (Figure 104).
Figure 104. BACnet Address Table Entry Dialog Box.
When using the BACnet Address Table Entry dialog box, note the following:
• The Device Instance number must be entered (at a minimum).
• The button displays the object selector. When a panel is selected in the object selector, the name and address fields will be filled automatically.
• When the Object ID checkbox is selected, it enables the fields to the right and allows you to enter the object type and instance.
• The address can be entered in either hex or decimal.
ALN Definition
The Building Level Network Definition dialog box for a BACnet ALN has changed slightly (Figure 105). You can now specify the Instance Number for the Insight workstation, whereas, in previous revisions this could be done only in the registry.
Insight Features for BACnet
Siemens Industry, Inc. 247
Figure 105. Building Level Network Definition Dialog Box with a BACnet ALN.
The operational features of the Building Level Network Definition dialog box include:
• A change to the Instance Number that affects all ALNs on that Insight workstation. You are issued a warning when making a change.
• When Set Time is clicked, only the time for the panels in the recipients list are set (synchronized). Any panels for which the Set Time operation fails will be reported in a message box.
• The Recipients button displays the Time Synchronization Recipient List dialog box (Figure 106) that allows users to pick which panels will have their time synchronized automatically every day or when the Set Time button is clicked. In that dialog box, users can choose to send local time or UTC. The Change button cycles between do not Sync, local time, and UTC time. You can multi-select so you can change many at a time. See Time Synchronization in Chapter 4–BACnet Communications for more information.
Chapter 8–Insight BACnet Option
248 Siemens Industry, Inc.
Figure 106. Time Synchronization Recipient List Dialog Box.
• If the Building Level Network Definition dialog box is closed when creating a new ALN, a warning message box displays if any BACnet filters were not set up. Click Yes to save the ALN anyway. Filtering is done in the BACnet Connection Settings dialog box (Figure 107) that you can access by clicking the Settings button. For more information, see Device Discovery in Chapter 4-BACnet Communications.
Insight Features for BACnet
Siemens Industry, Inc. 249
Figure 107. BACnet Connection Settings Dialog Box.
The operational features of the BACnet Connection Settings dialog box include:
• I-Am processing–This section handles how device discovery adds devices to the ALN. Users can setup rules or filters on what devices should be added automatically to this specific ALN. Users can specify a Device ID range, a vendor ID, and/or a network number.
• Process ID Registration–This section allows users to add a list of Process IDs (up to 16) that the Insight application will register on the BACnet network.
− Duplicate Process IDs are rejected.
− The defaults are 0 and 600.
− The Remove button removes the highlighted process ID from the list.
− Changes to Process IDs take effect after the next reboot (the Async service must restart).
• Replication Settings–The replication settings are the same settings as for Ethernet ALNs. They are replicated in the same way on a BACnet ALN. The BACnet Network number, instead of site name, determines intersite and
Chapter 8–Insight BACnet Option
250 Siemens Industry, Inc.
intrasite. For details about the BACnet network number, see Chapter 4-BACnet Communications.
• BBMD Settings–The BBMD Table button displays the BBMD edit dialog box, which allows you to edit the Insight BBMD table. The dialog box is shown in the Panel Definition section. You can only edit BBMD entries if the BBMD was enabled in the Cimetrics network configuration application. For details, see Chapter 4-BACnet Communications.
Panel Definition
The Field Panel Definition dialog box has been updated for BACnet field panels (Figure 108).
Figure 108. BACnet Field Panel Definition Dialog Box.
Insight Features for BACnet
Siemens Industry, Inc. 251
The operational features of the BACnet Field Panel Definition dialog box include:
• Panel type can now be MBC, MEC, Compact, Modular, and BACnet (other). Other is for all third-party BACnet devices.
• A Network # field has been added. Panels on multiple network numbers can reside on the same ALN.
• The Object name was added. This is an optional field that displays the BACnet object name property as it appears in the device object. (This is not the configured name that the Insight application uses when creating a device).
• Several fields are read-only and will be filled in by device discovery. These include: Vendor ID, Application SW Rev., Model Name, Vendor Name, Firmware Rev, and Location.
• The Site Name field was added. This is an optional field that allows you to define which site the panel belongs to. The site name affects which discovery and replication timers are used (intrasite or intersite).
• The Status section contains a Cloaked check box. This feature is used to hide panels on the BACnet network that a user does not wish to see through the Insight workstation.
• The Supports LON checkbox is only enabled for the MEC. The LON Settings button displays the same LON settings as Version 3 MECs use.
• A Backup/Restore Password section has been added for access to third-party panels for doing a backup or restore. Passwords are optional, so some devices may not require them. For APOGEE field panels, enter the HIGH account password.
• If this is an APOGEE field panel and the ALN name configured at the panel is different than the ALN name in the Insight workstation, a warning message displays when there is a mismatch.
• The Alarm Messages button displays the standard dialog box for editing enhanced alarm messages. These messages are used in BACnet for standard point alarms. For more details, see Chapter 10-BACnet Alarming.
Chapter 8–Insight BACnet Option
252 Siemens Industry, Inc.
Advanced Settings Dialog Box
The Advanced Settings button displays the Advanced Settings dialog box (Figure 109) for setting some advanced timers.
Figure 109. Advanced Settings Dialog Box.
The operational features of the Advanced Settings dialog box include:
• Base Instance for FLN devices–Only enabled for PXC’s. This is the Instance Number from which the APOGEE field panel will start creating points on FLN devices. This value must be at least 10000.
• COV Resubscribe and COV Poll Rate–Valid for all panel types. The first is how often to reregister for COVs. The second is how often to poll devices that don’t support COVs.
• APDU Timeout and APDU Retries–BACstac settings to control how long the Insight workstation will wait for a command to this field panel to be completed before timing out and how many times to retry the command. Insight enforces a minimum of 1 retry and 5-second timeout. APDU timeouts are also discussed in Chapter 4–BACnet Communications.
• Backup Preparation Time and Restore Preparation Time–Determine the amount of time Insight will wait before starting the backup and restore procedures after it tells this field panel that the operation is coming. Many devices need some time to prepare their configuration files.
Insight Features for BACnet
Siemens Industry, Inc. 253
Unsolicited COV Subscription List Dialog Box
The Unsolicited COV button on the BACnet Field Panel Definition dialog box displays the Unsolicited COV Subscription List dialog box (Figure 110). This is used for entering a table of points that are to send COVs to devices that are not capable of asking for COVs.
Figure 110. Unsolicited COV Subscription List Dialog Box.
The operational features of the Unsolicited COV Subscription List dialog box include:
• Allowing COV Recipients to be a BACnet point, a device, or a Process ID. The device can be used as a wildcard to indicate a broadcast to all devices.
• The ability to reject duplicate entries from the Unsolicited COV Subscription List.
• A button that displays the object selector and allows you to pick points or panels.
• A Remove button that is enabled after selecting an item in the list. When Remove is clicked, the item is removed from the list.
• A database that is also kept in the field panel. Changes made here should match the list in the field panel.
Chapter 8–Insight BACnet Option
254 Siemens Industry, Inc.
• A prompt to save changes when changes have been made and the Cancel button is clicked.
BBMD Table Dialog Box
The BBMD Table button displays the BBMD Table dialog box (Figure 111) that lets you define which devices are BBMD devices. It is only available on PXC’s (not third-party field panels). See Chapter 4-BACnet Communications for details about BBMDs and how to set up the Insight workstation as a BBMD, if required.
Figure 111. BBMD Table Dialog Box.
The operational features of the BBMD Table dialog box include:
• The IP Address, UDP Port, and Broadcast Distribution Mask fields, which are used for each BBMD device.
• A button to the right of the IP address field that allows you to select a field panel and have its IP address entered automatically.
Insight Features for BACnet
Siemens Industry, Inc. 255
• A Remove button that deletes the selected item
• A prompt to save changes when changes have been made and the Cancel button is clicked.
• The list prevents you from adding duplicates.
• This table is sent to the field panel and should match what is in its database.
• An OK button that provides an option to sync all BBMD tables. If Sync All is selected, the Insight software will try to send the table to all devices in the table. All devices in the table must be APOGEE panels or Insight workstations for the sync to work. All third-party BBMDs must be edited manually.
BACnet Point Names Dialog Box
The Point Names button in the BACnet Field Panel Definition dialog box displays the BACnet Point Names dialog box (Figure 112) that allows users to pick how points are named when uploaded for this panel. It is only available on third-party panels. The default setting is Encoded Names.
Figure 112. BACnet Point Names Dialog Box.
Chapter 8–Insight BACnet Option
256 Siemens Industry, Inc.
Foreign Device Settings Dialog Box
The Foreign Devices button in the BACnet Field Panel Definition dialog box displays the Foreign Device Settings dialog box (Figure 113) that allows you to select whether the field panel is acting as a foreign device. It is only available on PXC’s (not third-party field panels). See Chapter 4-BACnet Communications for details about Foreign Devices and how to set up the Insight workstation as a Foreign device, if required.
Figure 113. Foreign Device Settings Dialog Box.
• If Act as Foreign Device is checked, all controls are enabled.
• A Time to Live value of 0 means it never expires, otherwise it must re-register each time the Time to Live expires.
Notification Class Dialog Box
The Notification Class button in the BACnet Field Panel Definition dialog box displays the Notification Class dialog box (Figure 114) where you can edit Notification Classes for the device. See Chapter 10-BACnet Alarming for details about notification classes.
Insight Features for BACnet
Siemens Industry, Inc. 257
Figure 114. Notification Class Dialog Box.
• You can create/add/modify/remove Notification Classes in third-party panels and APOGEE BACnet panels.
• The Copy To button allows you to copy the selected notification class to other devices. It copies by Instance Number. If that device already has a notification class with that Instance Number, it will be deleted and replaced with this one. If a notification class is copied that doesn’t have an Instance Number, then it can end up with different Instance Numbers in the devices to which it was copied. Users can copy it to APOGEE field panels or third-party devices. Any errors received during the copy operation will be displayed.
CAUTION:
Be careful using the Copy To feature. Instances of the same number in the destination device can be overwritten. Verify what the Copy To operation is doing each time it is used.
BACnet Notification Class Dialog Box
Adding a Notification Class displays the BACnet Notification Class dialog box (Figure 115) that prompts for the properties of a Notification Class.
Chapter 8–Insight BACnet Option
258 Siemens Industry, Inc.
Figure 115. BACnet Notification Class Dialog Box.
• The Instance Number must be unique within the device for Notification Classes. If –1 is entered, the device will assign the Instance Number.
• The Object name must be unique within the device.
• The Descriptor is optional.
• The Priorities can be 0 to 255.
• You can select which transitions should require acknowledgements.
It is suggested that ALL of the “Ack required…” check boxes be checked when RENO notification is required. For more details on RENO Notification, see Chapter 10–BACnet Alarming.
• Modifying a notification class also displays the BACnet Notification Class dialog box. The Instance Number cannot be changed when modifying a notification class.
• With a notification class selected, users can add, modify or remove a recipient.
BACnet Destination Dialog Box
Adding a recipient displays the BACnet Destination dialog box (Figure 116).
Insight Features for BACnet
Siemens Industry, Inc. 259
Figure 116. BACnet Destination Dialog Box.
• The recipient can be a Device Instance, Address, or Broadcast.
• The Process ID should be a positive integer.
• You can select:
− Which transitions to tell the recipient about.
− Which days to send a notification.
− Which hours within a day to send a notification.
− Confirmed or unconfirmed notification.
See Chapter 10-BACnet Alarming for details about Notification class entries.
Cloaking
The concept of cloaking has been added for BACnet panels. Clicking the Cloaked button in Status section of the BACnet Field Panel Definition dialog box, the panel is removed from the system profile tree. This allows you to hide devices that you do not want to appear at the Insight workstation and to keep device discovery from constantly re-adding the devices to a ALN.
Chapter 8–Insight BACnet Option
260 Siemens Industry, Inc.
Only third-party devices can be cloaked.
Selecting the Show Cloaked Panels item on the View menu in System Profile (Figure 117). displays the cloaked panels in the System Profile tree. This allows access to the definition dialog box where you can uncloak the panels, if desired. In this view, cloaked panels appear as an outline of a panel.
Figure 117. Show Cloaked Panels Item in System Profile.
FLN Devices
Device Instance range edit dialog boxes have been added to the TEC, LTEC, and UC definition dialog boxes. Figure 118 shows the TEC Definition dialog box.
Insight Features for BACnet
Siemens Industry, Inc. 261
Figure 118. TEC Definition Dialog Box.
• The instance range fields are only enabled for BACnet field panels. These are the Instance Numbers that points on this FLN device will use.
• Once the number of subpoints is saved, it cannot be changed. The TEC has to be deleted and re-added to change it.
• The default base is displayed as –1. As soon as the field panel assigns a value, it will be uploaded to the Insight workstation and displayed. This cannot be set manually. Only the number of subpoints can be set when creating a device. The default and minimum value is 100.
Device Re-Initialization
If a BACnet device is selected in the tree and Coldstart/Re-Initialize on the Tools menu is selected, the BACnet Re-Initialize Device dialog box (Figure 119) displays to allow a warmstart or coldstart of the device.
Chapter 8–Insight BACnet Option
262 Siemens Industry, Inc.
Figure 119. BACnet Re-Initialize Device Dialog Box.
• An Are you sure message box displays before the command is sent.
• Some devices require a password. An error displays if left blank and the device requires a password. For APOGEE BACnet field panels, use the high account password.
• Configure access to System Profile is required to issue this command.
Device Communication Control
If a BACnet device is selected in the tree and BACnet/Device Communication Control on the Tools menu is selected, the BACnet Device Communication Control dialog box (Figure 120) displays to allow users to send communication control commands to the panel. There are three commands: Enable, Disable, and Disable Initiation Only. The disable commands allow you to stop a device from communicating on the network for a period of time. For more details see Chapter 12-BACnet Tools.
Insight Features for BACnet
Siemens Industry, Inc. 263
Figure 120. BACnet Device Communication Control Dialog Box.
The operational features of the BACnet Device Communication Control dialog box include:
• Disable or Disable Initiation Only enable the Disable Duration Edit window. Users can enter the number of minutes the device is to be disabled.
• Some devices require a password. An error displays if it is left blank and the device requires a password. For APOGEE panels, use the high account password.
• Users must have Configure access to System Profile to issue this command.
• The Add Devices button displays the Object Selector so that users can generate a list of panels. This makes this function useful for power fail tests. The list automatically removes duplicates. At least one panel must be in the list.
Who-Is Diagnostic Tool
Clicking BACnet Custom Send Who-Is on the Tools menu displays the Who-Is Diagnostic Tool dialog box. This is a tool that allows you to send out Who-Is messages and view the I-am messages as they arrive. For more details, see Chapter 12-BACnet Tools.
Chapter 8–Insight BACnet Option
264 Siemens Industry, Inc.
Application Initial Values Dialog Box
Access the Application Initial Values dialog box by clicking the Initial Values button on the BACnet FLN Device Definition dialog box. This dialog box lists all the points for the selected BACnet FLN device application. This dialog box displays currently defined initial values and allows you to Set a new initial value for a point, Release a point’s initial value, or Update the initial values table.
Figure 121. Application Initial Values Dialog Box.
Time-of-Day Scheduling
APOGEE BACnet field panels support the PPCL-based Time-of-Day scheduling.
Trend Editor
Trend Definitions
Insight Revision 3.9.1 or later supports the ability to trend BACnet points in other devices. In previous revisions of the Insight software, points could only be trended in the field panels where they resided. With Insight Revision 3.9.1, you can trend BACnet points with any BACnet device that supports trend definitions (Trend Log Objects), regardless of where the BACnet points reside.
Trend Definition Editor
BACnet Add Trend Definition Dialog Box
With Insight Revision 3.9.1 or later, the Add Trend Definition Figure 169dialog box can display all devices in which Trend Log Objects reside for a particular BACnet point.
Insight Features for BACnet
Siemens Industry, Inc. 265
Figure 122. Add Trend Definition Dialog Box.
Add COV and Add Interval Definition Dialog Boxes
To support Trend Log Objects in other devices, the Insight Revision 3.9.1 or later Add COV Definition Figure 170and Add Interval Definition Figure 171dialog boxes have a Device Name field. By default, the Device Name field displays the device name in which the Trend Log Object resides. The user has the option of choosing a different device in which to store the Trend Log Object.
Figure 123. Add COV Definition Dialog Box.
Chapter 8–Insight BACnet Option
266 Siemens Industry, Inc.
Figure 124. Add Interval Definition Dialog Box.
• When a BACnet point is selected, the BACnet Settings section is enabled; otherwise it is disabled.
• For BACnet points, the Conditional Trending and Enable Buffer full controls are disabled.
• Users provide an Object Name for a BACnet trend definition. The Object Name must be unique within a panel.
• The Description is optional.
• The Instance Number must be unique within a device. Leave it set to –1 to have the panel assign the instance automatically.
• The Notification Class is the instance of the notification class that is to be notified when the buffer reaches the Notification Threshold.
• The Notification Threshold is the number of samples at which the device will notify recipients that the buffer is getting full and needs to be collected. This value should be less than the maximum samples at the device.
• Stop when full is a flag that indicates whether the device will stop collecting data when the buffer is full. It defaults to unchecked.
• The start and stop date/time can be specified to only collect data for certain dates or hours during the day. If any of the fields are wild carded in the start date/time, then trending will start immediately, if any are wild carded in the stop date/time, then trended will continue forever. There are buttons to display a dialog box that edits the dates/times.
• For custom interval definitions, the units are hundredths of seconds.
• When modifying a BACnet trend definition, you cannot change the Instance Number.
Insight Features for BACnet
Siemens Industry, Inc. 267
Trending Wizard - Select BACnet Device(s) Dialog Box
With Insight 3.9.1 and later, the Trending Wizard Select BACnet Device(s) dialog box allows you to select the device in which the BACnet points will be trended. You can create trends in the device where each point resides, or create trends in other devices.
Figure 125. Select BACnet Device(s) Dialog Box.
You can create trend definitions for points only in APOGEE BACnet panels. The COV and Interval dialog boxes have a BACnet section that lists the properties of a Trend Log object.
User Accounts Siemens Industry Inc. strongly recommends that User Accounts are setup in a secure way and are managed regularly and continuously throughout the BAS life. There are several simple aspects to be considered when setting up User Accounts that increase the security of the system, but not impede the access and usage of the system:
• There shall only be one or maximum two users with full Administrator rights
• Each User shall have a separate account. Group accounts should not be used (that is, one username and password for all electrical technicians).
• Each User Account shall be setup with the least privileges required for the user to perform the duties that are required of her/his position.
• User Accounts shall be constantly managed and updated (privileges added and removed as requirement changes, users added and removed as employees responsibilities change they join or leave)
See also Chapter 14-User Accounts.
Chapter 8–Insight BACnet Option
268 Siemens Industry, Inc.
Command Priority
In the Edit Insight Account dialog box (Figure 126), there are sections for BACnet Command Priority, Command Settings, and non-BACnet Command Priority defaults.
Figure 126. Edit Insight Account Dialog Box.
The Command Settings button displays the BACnet Command Priority Array dialog box (Figure 127).
Insight Features for BACnet
Siemens Industry, Inc. 269
Figure 127. BACnet Command Priority Array Dialog Box.
This allows selection of the BACnet priorities that the user is allowed to command or relinquish. These settings are used by the Point Commander to allow/disallow commanding and relinquishing certain priority levels.
Changes to these settings take effect next time the Insight workstation starts up. (Technically, the changes take effect the next time the Point Commander starts. However, once Point Commander is run, it really doesn’t shutdown until the Insight workstation is shutdown).
The non-BACnet Command Priority section allows you to set the default priority of any non-BACnet point that is commanded.
Insight Account Tab
The currently logged-in user account is selected by default. This is not specifically a BACnet related change, but is part of the Insight Release 3.7 application.
Chapter 8–Insight BACnet Option
270 Siemens Industry, Inc.
ALN Account TAB
BACnet ALNs appear in the ALN User Accounts tab. This allows assigning users to BACnet ALNs.
Figure 128. ALN User Accounts Dialog Box.
BACnet Export
BACnet Export, accessed from the Account menu, is a feature of the Insight BACnet server that enables populating the BACnet virtual network with non-BACnet APOGEE points in the Insight database server. The BACnet export dialog box displays a warning if you attempt to export points with COV limits twice the slope or smaller. These points display in an Export Results dialog box (Figure 129) and can be copied to the clipboard. This feature was added for Anthem support, which may lead to users exporting thousands of points. Too much COV traffic can be detrimental to a P2 (RS-485) ALN.
Insight Features for BACnet
Siemens Industry, Inc. 271
Figure 129. Export Results Dialog Box.
The Export Results dialog box also warns users when they forget to make the BACnet account or if no points are exported.
BIBBs Specifications for BACnet Scheduling
Siemens Industry, Inc. 273
Chapter 9–BACnet Scheduling Chapter 9 describes BACnet scheduling theory as it relates to scheduling in the APOGEE Building Automation System. It discusses the following topics:
• BIBBs for BACnet Scheduling BACnet and Insight Scheduling
• Setting Up BACnet Schedules
• BACnet Scheduling Examples
Much of the information in this chapter is taken from the Siemens Industry, Inc. training course: BAU-6005, APOGEE Automation System with BACnet.
BIBBs Specifications for BACnet Scheduling Scheduling is specified for the various BACnet Interoperable Building Blocks (BIBBs) equipment profiles in the following tables elsewhere in this document:
• BACnet Building Controller (B-BC): Table 18, page 61.
• BACnet Advanced Application Controller (B-AAC): Table 19, page 62.
• BACnet Operator Workstation (B-OWS): Table 20, page 63.
• BACnet Advanced Workstation (B-AWS): Table 21, page 64.
Overview of BACnet Scheduling BACnet scheduling involves three Insight database object types:
• Calendars
• Commands
• Schedules
The interaction of the Schedule object, Calendar object and either Command objects or database objects are what make a BACnet schedule function.
Comparison to APOGEE
The table below illustrates the scheduling differences between standard APOGEE and the APOGEE with BACnet system:
Table 43: Comparison of Scheduling Differences Between APOGEE and APOGEE with BACnet. APOGEE APOGEE with BACnet
Weekly schedule, monthly calendar Weekly schedule, monthly calendar
Zone mode schedule Command Object with mode point
Overrides Exceptions
Zones and Events Command Objects, Point Objects
Chapter 9–BACnet Scheduling
274 Siemens Industry, Inc.
APOGEE APOGEE with BACnet
Command Table (within a Zone) Command Object
Replacement Days Calendars and Exceptions
Start Stop Time Optimization (SSTO) configured in zones.
SSTO accomplished through PPCL.
Insight software supports viewing, creating, deleting and editing Schedules, Zones, and Events.
Insight software supports viewing, creating, deleting, and editing of Schedules, Calendars, and Command Objects.
APOGEE Go supports scheduling Zones, Events, and Reports that already exist in Insight.
APOGEE Go supports viewing, creating, deleting and editing of Schedules and Calendars that already exist in Insight.
BACnet Object Browser supports viewing and editing Schedules, Calendars and Command Objects.
Scheduling Theory In BACnet systems, LENUM points must start at 1. This is different than a proprietary LENUM point which would normally start at 0.
• The BACnet Scheduler will not recognize a state of 0 for LENUM points.
• For example, a BACnet State Text Table would look like this:
− 1 – VAC
− 2 – OCC
• This can be an issue because the PPCL programs we use are written to use the proprietary State Text format:
− 0 – VAC
− 1 – OCC To get around this disparity, the Command Object can be used to command a mode point to a value recognized by the PPCL program. PPCL programs are written to monitor the status of a zone’s mode point. Because BACnet Systems do not use zones, a virtual LAO (AV) point is created in its place.
• The virtual LAO is substituted in the program for the zone mode point. The Command Object containing the mode point is scheduled using a BACnet compliant state text table. For example:
• 07:00 – 19:30: a Command Object’s value is 2 or OCC In the Command Objects Action List, when the Command Object is in OCC, the virtual mode point’s value is commanded to 1.
• The virtual mode point is monitored by the PPCL program. When its value changes to 1, the program initiates occupied programming.
Setup DBCS for Scheduling Through Insight/Commissioning Tool
Siemens Industry, Inc. 275
At 19:30, the Scheduler will change the Command Object to 1 or VAC. When the Command Object is in VAC, the virtual mode point’s value is commanded to 0. The virtual mode point monitored by the PPCL program changes to 0, and the program initiates unoccupied programming.
Setup DBCS for Scheduling Through Insight/Commissioning Tool Before creating Schedules and Calendars, the DBCS Server Service must be configured. The steps for this process are documented below.
Step 1 Navigate to the DCOM Config Security Screen.
a) Follow the menu path Start Run. b) Type DCOMCNFG and press Enter. c) Expand the navigation tree:
Component Services Computers My Computer DCOM Config. d) Click Yes for any CLSID warnings. e) In the right window, find Insight DBCSServer. Right-click the icon and then select Properties f) Click the Security tab.
Do not attempt to change any settings in the Configuration Permissions section of the Security tab.
Step 2 Configure the Launch and Activation and Access Permissions.
a) In the Launch and Activations Permissions section, select the Customize radio button and click the Edit button.
b) In the Group or Usernames section, click the Add button. Click Advanced, and then click Find now.
c) Make sure Administrators, Administrator, System, and any Insight Users or Insight Group all have access, and “Everyone” does not. Add to the group as necessary.
d) In the Permissions section of the Change Configuration Permission dialog box, check the check boxes to allow access to both levels of access for allowed users.
e) Click OK.
f) Repeat these steps for Access permissions.
Step 3 Close DCOM Config.
a) Click OK. b) Close the Component Service window.
It is not necessary to reboot the computer.
Chapter 9–BACnet Scheduling
276 Siemens Industry, Inc.
Step 4 Start or Cycle the DBCS Server Service.
a) Open the services. (services.msc on the run line) b) Scroll to the Insight DBCS Server service. c) Put it in Automatic, and start it. d) If it is already running, restart it. e) Verify that the Windows service (Insight BACnetClientSvc) is started. f) Close the services window.
Step 5 Verify that Field Panel Communications are Ready.
a) Open System Profile and expand the tree. b) Open the field panel properties and verify that the panel is ready.
Step 6 Use the Database Transfer Application to Upload the Panel Database to Insight.
a) Open the properties box of the field panel in System Profile and verify that the panel is ready.
b) Open the Database Transfer utility and perform an Upload All from the field panel to Insight.
BACnet Calendars The BACnet Calendar Object is a list of date entries from which action can be initiated. The Calendar Object’s Present Value is evaluated as TRUE on any date that is in its Date List. On other dates the Calendar Object’s Present Value is FALSE.
In an APOGEE BACnet field panel, the instances where the Present Value of the Calendar Object is checked includes:
• After 00:00 each day (midnight).
• Whenever the device resets.
• Whenever properties that can affect the results are changed.
• Whenever the time in the device changes by an amount that may have an effect on the calculation result.
At other times, as required, to maintain the correct value of the calendar through the normal passage of time.
BACnet Calendars
Siemens Industry, Inc. 277
BACnet Time Setup BACnet panels have an additional feature for time synchronization that is critical for scheduling accuracy. There is a button in the BACnet BLN dialog box called Recipients. It is located below the Set Time button. BACnet panels have four options for time synchronization:
• Local Time: Synchronizes the selected device(s) on the BLN to your local time.
• UTC: Synchronizes the selected device(s) on the BLN to the Universal Time Coordinated (UTC). (UTC is also referred to as Greenwich Mean Time (GMT).)
• Both: Allows you to send the Local Time and UTC to the selected device(s). This is the default setting for devices added from the BACnet network.
• Do not Sync: Does not synchronize the selected device(s). This is the default setting for devices added from the System Profile application.
In most installations the Local Time option is selected.
Creating a BACnet Calendar Each time a BACnet device’s date changes, all internal calendars are evaluated as True or False.
• If the current date is included in the calendar’s list of effective date, the calendar is evaluated as “true.”
• Calendars themselves do not command objects.
• Calendars are created and viewed in the Scheduler application.
• Follow the path: BACnet > New > Calendar
• The BACnet Calendar Object Properties dialog box opens.
Chapter 9–BACnet Scheduling
278 Siemens Industry, Inc.
Figure 130: Creating a BACnet Calendar in APOGEE.
BACnet Calendar Properties Dialog Box The BACnet Calendar Properties dialog box contains the following fields:
Device Name: The panel that will contain the calendar.
Device Instance: Auto-populates with the instance number of the device.
Calendar Name: Unique name for the calendar, e.g. “National Holidays.”
Calendar Instance: Auto-assigned by default.
Description: Optional field, up to 256 characters.
Present value: Read-only field that displays the current status of the calendar.
BACnet Calendars
Siemens Industry, Inc. 279
Calendar Properties Date List The Date List area of the Calendar Properties dialog box allows the user to set up Dates, Date Ranges and/or Week and Day entries in the Calendar.
When the Add button is clicked, the Calendar Entry Properties dialog box appears. The entries are described below:
Date: Specifies an exact date in the calendar. It is active on one day each year.
Date Range: Specifies a range of dates.
Week and Day: Specifies a month, week, and/or day, such as the last Thursday of November (Thanksgiving). Wildcards are allowed.
Chapter 9–BACnet Scheduling
280 Siemens Industry, Inc.
BACnet Object Commands BACnet Command Objects, created in the Event Builder application, allow a user to control a single point or groups of different types of points based upon the state of a state text table.
The Command object can command a mix of data types (Analog and Binary). A Schedule object can only command single object types.
Creating Command Objects Access the BACnet Command dialog box from the Event Builder application.
Follow the : Definition > New > BACnet Command Object
BACnet Command Dialog Box Below is a description of the fields in the BACnet Command dialog box:
Object Name: Unique for the field panel.
Descriptor: Usually left the same as the Object Name.
Field Panel: Enter the field panel name or use the Object Selector to browse for the appropriate field panel.
Instance Number: Normally auto-assigned by the panel (left at -1).
Action Text: The state text table used by the Command Object can be imported or created in this section.
• The Action Text group starts with an index value of 1.
• Gaps are not allowed in index values. They must be contiguous.
• Copy and paste functionality can be used to copy command information from one action text object group to another. For example: copying the points from the VACANT Action List and pasting them into the OCCUPIED Action List.
BACnet Schedules
Siemens Industry, Inc. 281
The Import button can be used to populate the Action Text section with pre-defined state text tables.
Action List: This section is used to add objects to individual Action Text states. Objects are added by highlighting the Action Text state and then clicking the Add button on the bottom of the dialog box. Objects are added to the state by selecting them in the Edit Action dialog box. Most information auto-populates when an object is selected from the database. The following information requires manual entry:
• Value Type: The value the object will be commanded to in this state.
• Priority: The priority the object will be have when commanded in this state.
• Delay: A time delay in seconds that will take place when the Command Object changes state. If there are several items in the Action List, the time delay applies to each individually, in order, from top to bottom.
Quit on Failure: Check this box if commands to the remaining objects should not be initiated if this line's command fails.
If an object displays an instance number value of 4,194,303; it is not recognized by Insight. This is often an indication that the object has not been downloaded to the field panel and lacks an instance number.
BACnet Schedules BACnet schedules are used to command objects at prescribed time intervals. Each BACnet field panel holds its own calendar and schedule objects. A device can store and run multiple calendars and schedules at the same time.
The BACnet schedule object contains a periodic schedule that can occur over a range of dates. The dates are set up to change the value of one or more objects being controlled by the schedule. The BACnet schedule object:
• Normally controls with a regular (Weekly) schedule.
• Has an exception schedule list for holidays, special events etc. A BACnet Exception has the same effect on the schedule as an APOGEE Replacement Day. It removes and replaces all schedules for the day on which it is used.
• Integrates with the Calendar Object to ease programming of exception schedules that affect large numbers of schedule objects.
• Schedules are divided into days, of which there are two types: normal days within a week and exception days.
• Both types of days can specify scheduling events for either the full day or portions of a day.
• A priority mechanism defines which scheduled event is in control at any given time.
The current state of the Schedule object is represented by the value of its Present Value property, which is normally calculated using the time/value pairs from the Weekly Schedule and Exception Schedule properties. A default value is used when no schedules are in effect.
Chapter 9–BACnet Scheduling
282 Siemens Industry, Inc.
Scheduling Point Objects BACnet schedules allow the direct scheduling of point objects; however, all points commanded by a schedule must be of the same type. When commanding points in a schedule:
• Every point will be commanded at the same time.
• Every point will be commanded to the same value.
If it is necessary to command a mixed group of object types, a Command Objects allows much more flexibility.
Insight Rules The BACnet Field Panel executes the schedule(s). Insight accesses the calendars and schedules stored in the panel in order to permit editing.
• If defined as the Mass Storage Device, Insight will store a copy of the calendars and schedules for its devices (panels).
• All points in a single BACnet schedule must be of the same type as the schedule itself (either analog AO or binary BO points).
• When a schedule directly executes a command, all points are commanded to the same value.
Creating BACnet Schedules Through Insight/Commissioning Tool Schedules may be created that run every single day of the year, or they may be seasonal schedules that run within specific times of the year.
To create a schedule, open the Scheduler application and from the main menu select: BACnet > New > Schedule. The BACnet Schedule Properties dialog box displays.
BACnet Schedules
Siemens Industry, Inc. 283
Figure 131: BACnet Schedule Properties Dialog Box.
The BACnet Schedule Properties dialog box allows the user to configure a BACnet Schedule. The dialog box has six main parts:
• Schedule Identity: This section allows a user to name the schedule, provide an optional description of its use, and identify the field panel that will support the schedule.
• Schedule Objects: This section allows a user to add and/or remove objects. Objects are listed by Device Number, Object Name, Object ID, and Property. The fields may be configured in ascending or descending order.
− The Add button allows the user to utilize the Object Selector to add an existing BACnet Object to the schedule.
− The Remove button deletes a selected item from the schedule.
• Schedule Default: This section allows a user to enter a default value for the schedule and select its command priority.
− The Default Value will be used if no weekly schedule is in effect.
− Checking the Null Value box disables the Default Value field. Objects in the Schedule Objects field will use their own default values if not scheduled.
− The Priority for Writing drop-down list allows the user to select the command priority level. This is the priority that the system will use when writing object properties during schedule processing.
• Effective Period: This section allows a user to set a time period for the specific schedule to be active.
− The button resets all fields to the default value of <Any>.
Chapter 9–BACnet Scheduling
284 Siemens Industry, Inc.
− The button updates all fields with the current date.
− The button displays a calendar for date selection.
• Schedule Output: This section allows a user to define a weekly BACnet schedule for selected days of the week.
− The Add button displays the Schedule Entry dialog box. This allows a user to add start and end times and a value to the selected BACnet weekday schedule.
− The Modify button allows a user to modify the time and value entries for the selected BACnet weekday schedule.
− The Copy button allows a user to modify existing schedule entries and add them as new schedule items.
− The Remove button deletes one or more existing schedule output entries.
− The Combine Days checkbox allows the user to combine schedules that have the same Start Time, End Time, and Value, into a single line display.
• Exceptions: This section allows a user to view scheduled exceptions with details such as exception definition, start time, value, end time, and priority.
− Exception schedules can be modified by double-clicking the schedule entry or selecting it and clicking the Edit button.
Advanced BACnet Schedule Properties
Clicking the Advanced button will open the Advanced BACnet Schedule Properties dialog box. There are four tabs in the dialog box:
General Tab: This tab displays schedule property information and allows changes to be made to the following:
• Description
• Default Value
• Effective Period
The Current State section displays information useful for determining the status of the schedule:
• Status: Auto-populates with either OK or Failed.
• Reliability: Additional status information indicating whether the schedule is properly configured in the device.
• Present Value: Auto-populates with the value of the existing schedule. If the Out of Service box is checked, the field is active and a value may be selected.
BACnet Schedules
Siemens Industry, Inc. 285
Weekly Tab: This tab allows a user to define, modify or remove a weekly schedule for a selected day of the week.
• The Schedule section display is sorted in ascending order by time value. For example, a time of 08:00 is the first line item in the list, then 17:00, and so forth.
Chapter 9–BACnet Scheduling
286 Siemens Industry, Inc.
Exception Tab: This tab allows a user to add, modify, or remove exception schedules from the weekly BACnet schedule. It is divided into two separate panes of information:
• Upper Section: Exception definitions and priority levels.
• Lower Section: Times and values for each exception schedule listing.
BACnet Schedules
Siemens Industry, Inc. 287
Exceptions are used to modify an existing schedule. There are a number of reasons a user may want to do this:
• Apply a calendar to the schedule. The calendar must be in the panel’s database.
• Create an exception particular to this schedule. The same options used when creating a calendar:
− Date
− Date Range
− Week and Day
• Override a schedule to modify the time it is active.
Using a value of Null in an exception schedule tells the system to return to the “normal” schedule. So if the exception was to schedule a half day from 8 to noon, and you go Null at noon, the system will stay on for the remaining “normal” hours.
Items Tab: This tab displays the objects controlled by the schedule. All functions in this tab are the same as in the Schedule Objects section of the BACnet Schedule Properties dialog box.
Chapter 9–BACnet Scheduling
288 Siemens Industry, Inc.
Creating BACnet Schedules/Commands/Calendars Through the Field Panel Web Server
The information in this section was derived from the Field Panel Web Server User Guide posted on InfoLink. This section discusses the following topics:
• Schedule/Command/Calendar Object Editors Overview
− User Interface Description for the Schedule/Command/Calendar Object Editors
− Tips for Using the Schedule/Command/Calendar Object Editors
• Schedule/Command/Calendar Object Editors Step-by-Step Instructions
− Schedule Objects
− Command Objects
− Calendar Objects
Schedule/Command/Calendar Object Editors Overview
The Field Panel Web Server Schedule/Command/Calendar Object Editors allow the user to create, modify, view, and delete schedule objects, calendar objects, and command objects. The user can also view the properties of an object or override a schedule on a selected date.
The Object Editors are accessible via the Create/Edit bar on the navigation pane on the left side of the Web Server screen.
BACnet Schedules
Siemens Industry, Inc. 289
Existing Schedules can also be viewed through the Scheduler Application, accessible via the Scheduling bar on the navigation pane on the left side of the Web Server screen. Choose the desired panel to view any existing schedules. Schedules cannot be created, modified, or deleted via this view.
The following attributes of an existing schedule can be modified through the Schedule editor:
• Description
• Effective time period
• Weekly schedule
• Exception schedule
• Schedule default values
• List of objects/property reference
• Write priority
• Out of service status
The user can also create Calendar Objects to be used with the Schedule editor. The calendar object created will be referenced by the Schedule Object. The user can also view, delete, and modify existing Calendar Objects.
The following attributes of an existing Calendar Object can be modified through the Calendar Editor:
• Description
• Date List
Chapter 9–BACnet Scheduling
290 Siemens Industry, Inc.
The user can also create Command Objects to be used with the Schedule editor. The Command Object created will be referenced by the Schedule Object. The user can also view, delete, and modify existing Command Objects.
The following attributes of an existing Command Object can be modified through the Command Editor:
• Description
• Action
• Action Text
For details on the description of the User Interface for Schedule/Command/Calendar Object Editors, refer to the Field Panel Web Server User Guide.
1. Existing schedule details can also be viewed via the Scheduler bar in the
navigation pane on the left side of the Web Server screen. Schedule details can be viewed using Today, Day, Work Week, Week, or Month views. Use the buttons at the top of the Schedule window to choose among the available views or to advance to the next Schedule segment (day, work week, week, or month).
2. The Schedule Object Editor allows the user to enable or disable an existing schedule on a specific date, which adds or removes an override on that specific date.
3. Additional overrides can be made for a specific date to change the starting time, ending time, and day span values of a schedule entry. The actual schedule definition does not change; only the control values used by the schedule for the specific date are changed.
4. The Object Name and Object Identifier of an existing Schedule, Calendar, or Command Object cannot be changed.
5. When creating a weekly schedule, use the Add Multiple button to add a weekly schedule to multiple days of the week.
Using the Schedule/Command/Calendar Object Editors
Schedule Object
Creating a Schedule Object 1. Click the Schedule icon from the Create/Edit bar. The Object Editor window displays. 2. Click Select a Panel at the top of the left pane of the Object Editor window to display
available panels. 3. Select the desired panel by clicking the panel name in the left pane of the Object Editor
window. 4. Click the + button at the bottom left of the Object Editor window. The Schedule Editor
window displays a new schedule object. 5. Enter the new schedule object information (Object Name, Object Identifier, Description,
Effective Start and Stop dates/times, Write Priority, Default Value). 6. Click the Weekly Schedule, Exception Schedule, or Command Point Objects buttons to
access those windows. 7. Click Save. The Save button will be grayed out once the modifications are complete.
BACnet Schedules
Siemens Industry, Inc. 291
Creating a Weekly Schedule 1. From within the Object Editor window, click the Weekly Schedule button to open the Edit
Weekly Schedule window. 2. Choose the day of the week by clicking the tabs at the top of the window. 3. Click the + sign at the bottom left of the window to add rows to the Time/Values table. 4. Click the – sign at the bottom left of the window to delete rows from the Time/Values
table. 5. Double click the entry in the Time column to change the start and stop times. 6. Double click the entries in the Value column to change the desired values.
To add a schedule to multiple days of the week, click the Add Multiple button.
Chapter 9–BACnet Scheduling
292 Siemens Industry, Inc.
For more information on creating a schedule exception, creating command objects, creating calendar objects, or modifying/deleting schedule, command or calendar objects, refer to the Field Panel Web Server User Guide.
Creating a Schedule Exception 1. From within the Object Editor window, click the Exception Schedule button to open the
Edit Exception Calendar window.
2. Click the + sign at the bottom left of the window to add an Exception Schedule.
BACnet Schedules
Siemens Industry, Inc. 293
• Choose Date, Date Range, Week’n’Day, or Reference (to reference an existing Calendar Object)
• Enter schedule details.
1. Click the Edit Time Values button to add time values to the Exception Schedule.
• Click the + sign at the bottom of the Edit Time Values window to add rows to the Time/Values table.
Chapter 9–BACnet Scheduling
294 Siemens Industry, Inc.
1. Click the value under the Priority column to change the exception priority. The Exception priority is the priority in which exception schedules are executed. If there are more than one exception schedules for the same time, the exception schedule with the higher priority will be executed.
2. Click the – sign at the bottom left of the window to delete an Exception Schedule.
Command Point Objects
1. From within the Object Editor window, click the Command Point Objects button to open the Edit Command Objects window.
2. Click the + sign at the bottom left of the window to add a Command Object to the Schedule Object.
• Click the Object drop down to choose a reference objects or a Command Object.
• Enter a property identifier in the Property ID field.
Viewing a Schedule Object
1. Click the Schedule icon from the Create/Edit bar.
• The Object Editor window displays.
2. Click Select a Panel at the top of the left pane of the Object Editor window to display available panels.
3. Select the desired panel and the desired schedule object by clicking the panel name and then the schedule object name.
• The Schedule Editor window displays the schedule object details.
BACnet Schedules
Siemens Industry, Inc. 295
BACnet Schedules
Siemens Industry, Inc. 297
Command Objects
Creating a Command Object
1. Click the Command icon from the Create/Edit bar (hover over the Schedule icon to view it).
• The Object Editor window displays.
2. Click Select a Panel at the top of the left pane of the Object Editor window to display available panels.
3. Select the desired panel by clicking the panel name in the left pane of the Object Editor window.
4. Click the + button at the bottom left of the Object Editor window.
• The Command Object Editor window displays a new command object.
5. Enter the new command object information (Object Name, Object Identifier, Description).
6. Click the + button at the bottom left of the Command Object Editor window to add an action to the command object.
7. Click the new action to add a title in the Action Title field, and to add point information.
8. Click the + button to add rows to the Action table.
9. Click each cell in the new row to add Point, Value, Priority, and Quit on Failure information.
10. Click Save.
• The Save button will be grayed out once the modifications are complete.
Siemens Industry, Inc. 299
Calendar Objects
Creating a Calendar Object
1. Click the Calendar icon from the Create/Edit bar (hover over the Schedule icon to view it).
• The Object Editor window displays.
2. Click Select a Panel at the top of the left pane of the Object Editor window to display available panels.
3. Select the desired panel by clicking the panel name in the left pane of the Object Editor window.
4. Click the + button at the bottom left of the Object Editor window.
Chapter 9–BACnet Scheduling
300 Siemens Industry, Inc.
• The Calendar Object Editor window displays a new calendar object.
5. Enter the new calendar object information (Object Name, Object Identifier, Description).
6. Click the + button at the bottom left of the Calendar Object Editor window to enter Date, Range, or Week’n’Day information.
7. Click Save.
• The Save button will be grayed out once the modifications are complete.
Event Scheduling
BACnet objects cannot be included within an Insight Event. The closest method for duplicating an Event with BACnet is to include the object IDs in the Action List of a BACnet Command Object. The object IDs can be Command objects themselves and can be considered similar to APOGEE zones.
BACnet Schedules
Siemens Industry, Inc. 301
Start Stop Time Optimization (SSTO) Implementation in PPCL
The following example is applicable for Insight versions 3.12 or lower and APOGEE Firmware 3.2.5 and lower. Starting with Insight version 3.13 and APOGEE Firmware version 3.3, the SSTO application for BACnet will be built into the software and firmware.
Insight Soft Controller APOGEE SSTO
APOGEE SSTO operating from within the Insight Soft Controller option can be used to command BACnet objects. There are several ways to implement this. The easiest is to use the Zone’s MODE subpoint in IF-THEN logic to define which section of the PPCL program will be implemented. For example, the Mode state of the Zone point in an Air Handler program determines whether the air handler PPCL implements occupied operation, warmup, cooldown, stop heating, stop cooling, night heating, night cooling, etc. Since MODE is the default subpoint of a Zone’s name, only the Zone name need be used in the IF-THEN statements. The PPCL code will have the following pattern:
2010IF (ZONE1.EQ.1) THEN GOTO 6000 2020IF (ZONE1.EQ.2) THEN GOTO 5000 2030IF (ZONE1.EQ.6) THEN GOTO 3000 2040IF (ZONE1.EQ.7) THEN GOTO 4000 . . . 3000Warmup PPCL code 4000Cooldown PPCLcode 5000Occupied mode PPCL code 6000Vacancy mode PPCL code
CAUTION:
BACnet does not support LENUM values less than 1. Therefore, the default State Text Table ZONE_MODE for the zone names (e.g. ZONE1 in the above example) will need to be changed to a custom LENUM so that all LENUM values are greater than 0.
Chapter 9–BACnet Scheduling
302 Siemens Industry, Inc.
The PPCL code shown above uses the modes of a LENUM point (point ZONE1) with a custom State Text Table whose modes have the following values:
Mode State Name Value
VAC 0
OCC1 1
OCC2 2
OCC3 3
OCC4 4
OCC5 5
WARMUP 6
COOLDOWN 7
NIGHT_HTG 8
NIGHT_CLG 9
STOP_HTG 10
STOP_CLG 12
Mode State Name Value
VAC 1
OCC1 2
OCC2 3
OCC3 4
OCC4 5
OCC5 6
WARMUP 7
COOLDOWN 8
NIGHT_HTG 9
NIGHT_CLG 10
STOP_HTG 11
STOP_CLG 12
BACnet Schedules
Siemens Industry, Inc. 303
Figure 132 shows how to implement APOGEE Zone Mode control of BACnet Mode PPCL. The mode sub-point value is written to a BACnet Analog Value Object point, VIRTUAL_LAO, using PPCL within the APOGEE PXC or Insight Soft Controller. When VIRTUAL_LAO is commanded, the Insight cross-trunk service sends the command to this point in the BACnet device. The appropriate section of PPCL code in the BACnet device is implemented based on the value of VIRTUAL_LAO.
Figure 132. APOGEE Zone Mode control of BACnet Mode PPCL.
Another way to use SSTO from the Soft Controller is to have the Zone’s Command Table write to the Present Value of one or more BACnet Command Objects. The Command Objects can then command those objects necessary to implement the desired control strategy. For example, a Command Object can be set up for each of the following Modes: OCC, WARMUP. COOLDOWN. See the Command Object section for more details. For more details, see the Cross-Trunk Communications section in Chapter 4–BACnet Communications.
For more details as to how to bring APOGEE point commands over to BACnet devices, see the Cross-Trunk Communications section in Chapter 4–BACnet Communications.
BACnet Device Database Storage
Schedule and Calendar objects for Siemens BACnet panels are stored in the Insight database. So, these objects can be edited even if the Insight workstation is not communicating with the panel (editing may be performed online or offline).
Chapter 9–BACnet Scheduling
304 Siemens Industry, Inc.
Schedule and Calendar objects for third-party BACnet devices are stored in the third-party devices only. Therefore, these objects can be edited only when the Insight workstation is communicating with the device (editing must be performed online only).
Schedule Object Properties that Can be Commanded
Although the BACnet Schedule specification supports commanding object properties of any type, the Siemens BACnet field panel implementation is limited to:
• Unsigned–intended for commanding the value of a Command Object.
• Real–intended for Analog Output points.
• Enumerated–intended for commanding Binary Output points.
• Boolean–intended for enabling/disabling Trend Log objects.
In most cases, the property written is limited to the Present_Value property.
1. Object properties that are Arrays of the above simple data types (unsigned, real, enumerated
and Boolean) are not supported by Siemens BACnet field panels.
2. The capability to write to remote devices is not required by the BACnet specification, but the Siemens BACnet field panel supports commanding to outside devices. All BACnet devices, regardless of vendor, will accept commands from a Siemens BACnet field panel.
CAUTION:
Siemens BACnet Field Panels Wildcard Limitations
NOTE: Even though the BACnet Field Panel accepts an illogical or incomputable wildcard combination entry, the field panel may not execute it at all or may not execute it in the way the user intended.
Wildcarding an individual field (such as, Month) requires that the field be wild carded both in the Start date and the End date.
If Month and Day are not <any>, then <any> for the year has to be in both the Start and End dates. Thus, both dates with the year wild carded will provide the same date range every year.
When wildcarding an individual field, the Year field must be wild carded first before wildcarding the Month; the Month must be wild carded before the Day can be wild carded.
If a specific year number is entered into the Year field, <any> cannot be put in the Month field. An entry of <any> must go in the Year field if <any> is to be entered into the Month field. Therefore, with <any> entered for both Month and Year, the Calendar object will be TRUE over the same range of days for every month in every year.
A wildcard combination must have an obvious start date and stop date. In the following example, it is clear that all dates from September 2, 2005 through June 7, 2006 are within the Start period.
Start September 2 2005 <any>
Stop June 7 2006 <any>
However, if the years are changed to <any>, then both years can theoretically be the same (for example, 2005), which would not make any sense. Therefore, this use of wildcarding violates the rule of having an obvious start date and stop date.
BACnet Schedules
Siemens Industry, Inc. 305
Using BACnet Calendar Days in an APOGEE BACnet Field Panel
The BACnet calendar object’s value is either a Boolean TRUE or FALSE. The BACnet calendar object can be used in two ways; in PPCL or in a Schedule.
In PPCL
To use the BACnet calendar object in PPCL, simply inset the BACnet calendar object name in the lines of PPCL code as if it were a point name. For example, you could use the following line of code if you wanted to turn off the washroom exhaust fans on the holidays listed in BACnet Calendar Instance 7 of Device Instance 15000: IF (BAC_15000_CA_7) THEN OFF(BAC_4_BO_6)
In a Schedule
To use a BACnet calendar in a schedule, you list the calendar name as an Exception Property for a schedule and then the Exception Schedule will be implemented on the dates listed in the BACnet Calendar Properties. A BACnet Calendar should be used for exception schedules that affect multiple Schedules, for example, a national holiday. In this way, if the date must be modified, it only has to be modified in one place; in the BACnet Calendar.
To list the Calendar name as an exception property:
1. From the BACnet Schedule Properties dialog box, choose the Exception tab.
2. Click the Add Exception button to display the Calendar Reference dialog box.
Chapter 9–BACnet Scheduling
306 Siemens Industry, Inc.
3. Select Calendar Reference as the Type of Exception in the Exception Properties dialog box.
4. Use the drop-down list box in the Calendar Reference dialog box to select the desired calendar name. The example above displays the name “Holiday Calendar” in the Calendar Reference section when the dialog box opens. The following example shows “Holiday-C96” after the Calendar Reference has been changed.
If the calendar object has not yet been created, only the Instance Number must be entered to act as a placeholder for the future calendar object.
Accessing a Calendar Object with the BACnet Object Browser
The Calendar object can be accessed with the BACnet Object Browser, which is available in Insight software and Commissioning Tool in the System Profile application under the Tools menu. The Calendar object names appear under Calendar in the navigation pane (Figure 133). The properties for the chosen Calendar name can be viewed by double-clicking the appropriate name. The Date List property must then be double-clicked to view the dates.
BACnet Scheduling Examples
Siemens Industry, Inc. 307
Figure 133. Viewing Calendars with the Object Browser.
BACnet Scheduling Examples The following examples illustrate how Scheduling works in an APOGEE field panel implementing the BACnet 2004 specification.
BACnet Scheduling Example 1
Figure 134 is an example of a BACnet schedule. This simple example shows the basic elements of BACnet scheduling.
The Schedule object name is season-based because it relates to its Effective Period property. The Description is geographic so a user does not have to drill down to each of the Object Property References to determine what zones are controlled by this Schedule object. If every building on the campus had a different Weekly Schedule, then it would probably be appropriate to include the building name in the Schedule Name for quicker access by the user.
Chapter 9–BACnet Scheduling
308 Siemens Industry, Inc.
Figure 134. BACnet Scheduling Example.
The Weekly Schedule (Figure 135) starts at 00:00:00 and causes the Night Cooling Action to occur, otherwise the Schedule Default (0) will take over at midnight and no action will occur until 6:00:00, when Cool down begins. The Occupied (cooling) action occurs at 8:00:00 and ends at 18:00:00 when Night Cooling reinstates.
BACnet Scheduling Examples
Siemens Industry, Inc. 309
Figure 135. Example 1 Weekly Schedule for Night Cooling.
The Exception Schedule comes from the Calendar object named Holiday Calendar. This requires that the user update only this one Calendar object each year with the new holiday dates. The Date List shows that fixed dates are entered for most of the holidays while Date Ranges are entered for the Thanksgiving and Christmas holidays.
The List of Object Property References shows the three Command objects being commanded by the Schedule object. Each Command object represents a building. The Name and Description are use to detail how the Command object is programmed and save the user some time viewing each. The Action List of each Command object includes the supply fan object. Obviously, there is no Start Stop Time Optimization implemented. If there was SSTO, the supply fan would be controlled by SSTO PPCL as explained elsewhere in this section.
BACnet Scheduling Example 2
The weekly schedule is: 8:00=OCC and 17:00=UNOCC
It is desired to have a week in which everyone leaves early at 15:00.
To do this, set up an exception schedule that defines the week (for example, 24 December 2005, 02 January 2006) and has one time entry (15:00=UNOCC).
Chapter 9–BACnet Scheduling
310 Siemens Industry, Inc.
BACnet Scheduling Example 3
The weekly schedule is: 8:00=OCC and 17:00=UNOCC
It is desired to have a week in which everyone arrives later (9:00) and leaves early (15:00).
To do this, set up an exception schedule that defines the week (for example, 24 December 2005, 02 January 2006) and has three entries (UNOCC with any time between 00:00:00 and 7:59:59, and 9:00=OCC, and 15:00=UNOCC).
BACnet Scheduling Example 4
The weekly schedule is: 8:00=OCC and 17:00=UNOCC
It is desired to have a week in which everyone arrives early (7:00), but leaves at the time in the weekly schedule (leaving time may vary slightly from day-to-day).
To do this, set up an exception schedule with two entries (7:00=OCC, and NULL with any time value between 8:00:01 and earliest possible UNOCC time in the weekly schedule).
BACnet Scheduling Examples
Siemens Industry, Inc. 311
BACnet Scheduling Example 5 On a university campus, BACnet scheduling can be used to ring the bells on each hour and 50 minutes after each hour, 24 hours a day. The bells should ring for four seconds. To do this, create a BACnet Schedule object and BACnet Command Objects as follows: Schedule Object Schedule Name:
Campus Bells Description:
Class Bells – All Buildings Effective Period:
Start: August <last><any>Monday End: May <last><any>Friday
Weekly Schedule: *:00:00 2 *:00:04 1 *:50:00 2 *:50:04 1
Schedule Default: 1
List of Object Property References: Lecture Hall 1 Bells Lecture Hall 2 Bells Lecture Hall 3 Bells Lecture Hall 4 Bells Classroom Hall 1 Classroom Hall 2 Classroom Hall 3 Classroom Hall 4 Outdoor Annunciator
Command Object (one of many) Name:
Lecture Hall 1 Bells Description:
Class Bells – All Floors Action Index:
1Bells OFF 2Bells ON
Action List (Bells OFF): First Floor BellsOFF Second Floor BellsOFF
Action List (Bells ON): First Floor BellsON Second Floor BellsON
If 24 hour operation is not desired, a separate entry for each hour can be entered in the Weekly Schedule. For example:
08:00:002 08:00:041 08:50:002 08:50:041 09:00:002 09:00:041 09:50:002
Chapter 9–BACnet Scheduling
312 Siemens Industry, Inc.
09:50:041 Etc.
Siemens Industry, Inc. 313
Chapter 10–BACnet Alarming Chapter 10 describes the three separate areas of the database that are affected by BACnet alarming: Points, Notification Classes, and Alarm Messages, how it relates to the APOGEE Building Automation System, and how to set up alarming in APOGEE. It discusses the following topics:
• BACnet and APOGEE
• Setting Up BACnet Algorithmic Alarming
• Setting Up BACnet Intrinsic Alarming
• BACnet Intrinsic Alarming Example
Much of the information in this chapter is taken from the Siemens Industry, Inc. training course: BAU-6005, APOGEE Automation System with BACnet.
BACnet Alarming Overview BACnet Alarming utilizes three separate areas of the Insight database: Points, Notification Classes, and Alarm Messages. Alarming characteristics are added when creating or modifying a point.
Point objects: will reference or contain the following:
• Transitional notifications
• High and low values
• Notification Classes
• Message IDs
Notification Classes: are defined in the panel. When assigned to an alarmable point they add the following:
• The recipient of the alarm
• How the alarm is sent (broadcast)
• Whether acknowledgement is required
• Transitions allowed
• The priority of the alarm
• When the notifications are active, based upon days of the week and time
Chapter 10–BACnet Alarming
314 Siemens Industry, Inc.
Alarm Messages: are defined in the panel. Specifically:
• Up to 250 different messages may be defined.
• Default message “This point is in alarm” displays if a specific message is not selected.
Transitional States BACnet systems allow the selection of three specific alarm reporting events for a point. They are referred to as Transitional States. Specifically:
To-OffNormal: The BACnet object has transitioned from its normal state to an alarm state.
To-Fault: The BACnet object has transitioned from its normal state to any state other than alarm.
• Failed and Out of Service states would be included in this category.
To-Normal: The BACnet object has transitioned from any other state back to normal.
A user may require acknowledgement of these events when they are set up in Point Editor. Selecting all three events to be active for an alarm will cause it to function similar to standard APOGEE alarming
BACnet and APOGEE Alarming Siemens BACnet field panels support BACnet Intrinsic Alarming and Algorithmic Alarming (with Firmware Revision 3.2 or later) on points, replacing the Insight’s standard alarm and enhanced alarm applications. BACnet alarms, although closely resembling APOGEE standard alarms, include Notification Class Objects, which are similar to the APOGEE model for alarm destinations (also known as categories). For APOGEE BACnet field panels, an alarm message number can also be defined in the point definition for intrinsic alarming and in the Event Enrollment Object for Algorithmic Alarming. Figure 136 shows an example of the APOGEE implementation of BACnet Intrinsic Alarming from the perspective of a system point (BACnet Analog Input object–AI4).
BACnet and APOGEE Alarming
Siemens Industry, Inc. 315
Figure 136. APOGEE Implementation of BACnet Intrinsic Alarming.
Figure 137 shows an example of the APOGEE implementation of BACnet Algorithmic Alarming from the perspective of an Event Enrollment Object. Note that Alarm Message Number assignment is in the Event Enrollment Object.
Figure 137. APOGEE Implementation of BACnet Algorithmic Alarming.
Chapter 10–BACnet Alarming
316 Siemens Industry, Inc.
Table 44 shows a quick comparison of BACnet Alarming and APOGEE Alarming.
Table 44. Comparison of BACnet and APOGEE Alarming.
APOGEE Standard Alarms BACnet Standard Alarms
• Four standard destinations, each may contain multiple recipients.
• Up to 64,000 Notification Classes, each may contain multiple recipients.
• Globally shared Alarm Destination database • Notification Class stored internally in the panel.
• If a valid destination is not specified, the Mass Storage Device receives the alarm notification.
• Only devices specifying a Notification Class will receive an alarm notification.
• The Mass Storage Device must be included in a Notification Class to receive alarms.
• Message created as a part of a specific point.
Globally shared Alarm message database.
• Up to 250 messages available.
• Can use Message wildcards.
• Generic alarm message.
Alarm Messages
BACnet alarm messages are created in System Profile in the BACnet Field Panel dialog box, by clicking the Alarm Messages button.
BACnet and APOGEE Alarming
Siemens Industry, Inc. 317
Up to 250 messages may be created in a single panel. Specifically:
• Four lines of text per message, 50 characters per line.
• POPUP message designator may be used.
• Tokens may be used.
• Similar in set up to Enhanced Alarm messages.
Once the necessary messages have been created and saved to the panel, they can be selected in the Alarm Characteristics section of the Point Editor application.
Chapter 10–BACnet Alarming
318 Siemens Industry, Inc.
Token Messages Token Messages are text strings, inserted in alarm messages, that generate a piece of information to be included as part of the message.
If the correct strings are not used, the alarm message may print a partial message or no message at all.
The table below displays a list of valid tokens:
Message Token Example
In the example below, message tokens are used to create a generic message that might be used with a variety of alarmable points.
BACnet and APOGEE Alarming
Siemens Industry, Inc. 319
Notification Classes Notification Classes are used in many BACnet applications including, Alarming, Trending, and Event Enrollment. They contain a list of BACnet devices that receive alarms, alarm acknowledgements and notifications when a point enters a specified condition. Specifically:
• Notification Classes must be created, there is no default.
• If a Notification Class is not assigned, only system messages are sent directly to the mass storage device.
• Each field panel maintains its own set of Notification Classes.
• You can copy existing Notification Classes to other BACnet field panels using the Copy To… button.
− Always copy in order from top to bottom.
Chapter 10–BACnet Alarming
320 Siemens Industry, Inc.
The Notification Classes dialog box has two configuration areas:
• List of Notification Classes in this Device: The upper section is used to name and describe the Notification Class.
− Priorities and acknowledgement requirements are specified here.
• Recipient List of selected Notification Class: The lower section is used to identify recipients and set when the Notification Class is valid.
− Transitions and confirmations are specified here.
Upper Section Configuration Clicking the Add button in the upper section of the Notification Classes dialog box opens the BACnet Notification Class dialog box. The configuration details are provided below:
Instance Number. Normally auto-assigned.
Object Name. A unique name for the Notification Class within the device.
Descriptor: Optional field; a description of the Notification Class.
To Off-Normal Priority. Enter a priority level from 0 through 255.
To-Fault Priority. Enter a priority level from 0 through 255.
To Normal Priority. Enter a priority level from 0 through 255.
BACnet and APOGEE Alarming
Siemens Industry, Inc. 321
Ack required for To Normal transitions. Check this box to require an acknowledgement for return to normal transitions.
Ack required for To Off-Normal transitions. Check this box to require an acknowledgement for a transition from normal into alarm.
Ack required for To Fault transitions. Check this box to require an acknowledgement for a transition from normal into a state other alarm.
In BACnet systems, alarms have an available priority range of 0 through 255.
Insight maps the BACnet priorities to the six Insight alarm priority levels, A1 through A6. Table 45 below identifies the specific ranges:
Table 45: Network Alarm Priorities in BACnet Versus Insight. BACnet Alarm
Priority Range
Insight Alarm
Priority
Network Priority
Description
0 – 31 A1 Life Safety Message
Notifications related to an immediate threat to life, safety, or health.
For example, fire detection or medical emergency.
32 – 63 A2 Life Safety Message
Notifications related to an immediate threat to property.
For example, a forced entry or unlocked doors.
64 – 95 A3 Critical Equipment
Notifications related to improper operation, monitoring failure particular to Life Safety or Property Safety monitoring, or monetary loss.
Chapter 10–BACnet Alarming
322 Siemens Industry, Inc.
BACnet Alarm
Priority Range
Insight Alarm
Priority
Network Priority
Description
Message
For example, fire sprinkler valve shut off, communication failure and excessive energy use.
96 – 127 A4 Critical Equipment Message
Notifications related to communication failure particular to Life Safety or Property Safety equipment.
128 – 191 A5 Urgent Message
Higher-level notifications related to occupant discomfort, normal operation, normal monitoring, or return to normal.
For example, normal event logging or room temperature above setpoint.
192 – 255 A6 Normal Message
Lower-level notifications related to occupant discomfort, normal operation, normal monitoring, or return to normal.
For example, normal event logging or room temperature above setpoint.
An easy way to remember a value to associate with a priority level is to count up in increments of thirty. This works for all but the last level.
Priority 1 = 30Priority 3 = 90Priority 5 = 150
Priority 2 = 60Priority 4 = 120Priority 6 = 250 (The only exception.)
Lower Section Configuration
Clicking the Add button in the lower section of the Notification Classes dialog box opens the BACnet Destination dialog box. The configuration details by section are provided below.
Recipient Section The Recipient section allows the user to choose which specific device or devices will receive the notification. Selections include:
Device Instance. Specify a single device by instance number.
Address. Specify a single device by MAC Address and Network Number.
Broadcast. Specify a receiving subnet or all subnets:
• Local. Broadcast to all devices on the local subnet.
• Remote. Broadcast to all devices on a remote subnet.
BACnet and APOGEE Alarming
Siemens Industry, Inc. 323
• Global. Broadcast to all devices on all subnets.
Recipient Process Section This field contains the Process ID number of the BACnet recipient. Siemens devices are all process ID 600. A Process ID may need to be obtained from a vendor for integration.
Transitions Section A user can check or uncheck the boxes in this section to activate or deactivate Transitional States for this notification class. If the site is using RENO, these boxes must be checked.
Valid Days Section
Allows a user to select which days of the week notifications will be sent.
Period Section Allows a user to select which hours within a day to send notifications to a device. All fields must be populated (no Any indicators) or the period will default to 24/7.
Notifications Section When checked, configures a device to issue confirmed alarm notifications. This means that the device sending the alarm requires a response from the device receiving the alarm.
Chapter 10–BACnet Alarming
324 Siemens Industry, Inc.
• Can only be used when a single recipient is selected, similar to TCP/IP.
Event Enrollment
Event Enrollment is a BACnet application that allows a user to add alarm and event reporting features to an object. It utilizes three separate areas of the database: Points, Notification Classes, and Event Enrollment.
Event Enrollment Object Types
Event Enrollment allows a user to choose or specify multiple conditions to meet different scenarios. Table 46 lists the types of Event Enrollment Objects that are supported in our APOGEE BACnet panels.
Table 46: Types of Event Enrollment Objects Supported in APOGEE BACnet Panels.
Event Types
Supported Point Types
CHANGE OF STATE
BI, BV, MV
• Time Delay
• Property State Type
• Value
COMMAND FAILURE
BO, MO
• Time Delay
• Feedback Property Reference
FLOATING LIMIT
AI, AO, AV
• Time Delay
• Low Diff Limit
• High Diff Limit
• Deadband
• Setpoint Reference
OUT OF RANGE
AI, AO, AV
• Time Delay
• Low Limit
• High Limit
• Deadband
Event Enrollment Objects supported in other non-Siemens BACnet devices include:
• Change of Value
• Change of Bitstring
• Buffer Ready
• Unsigned Range
• Change of Life Safety
BACnet and APOGEE Alarming
Siemens Industry, Inc. 325
Event Enrollment Creation Event Enrollment Objects can be created in the Point Editor and System Profile applications.
Point Editor: A selected point may be configured for Event Enrollment by clicking the Event Enrollment button in the Related BACnet Objects section of the point definition dialog box.
System Profile: Clicking the Event Enrollment button in the BACnet Field Panel Definition dialog box opens the Event Enrollment Objects dialog box.
From either location a user can add, view, modify, copy or delete Event Enrollment objects.
Clicking the Event Enrollment button opens the Event Enrollment Objects dialog box. All existing Event Enrollment objects will be displayed.
To add a new Event Enrollment object, click the Add button. The BACnet Event Enrollment Properties dialog box opens. The following fields must be configured:
• Device Name: The panel where the Event Enrollment Object will reside.
• Instance Number: Normally auto-assigned.
• Name: A unique name for the Event Enrollment Object within the device.
• Description: Optional field; a description of the Event Enrollment Object.
• Notification Class Instance #: The instance number of the Notification Class to be used by the Event Enrollment object.
− The Notification Class must reside in the same device as the Event Enrollment Object being created in order for recipients to receive the event notification.
• Notify Type: A user can select Alarm or Event. Both options provide the same configuration characteristics.
• Alarm: Select for points normally considered alarmable, such as safeties or control sensors.
− To generate alarms that can be displayed in the Alarm Status application, the object must have a special type of LENUM point associated with it, which is used locally at the workstation and is never downloaded to the panel.
Chapter 10–BACnet Alarming
326 Siemens Industry, Inc.
− Creation and deletion of the LENUM point is automatically managed by the workstation.
− Limited editing of the LENUM point can be done in the Point Editor application.
Event: Select for points normally considered non-alarmable, such as sensors like the Outdoor Air Temperature.
• Can be used to notify the system if an important non-alarmable point fails or is placed out of service.
• To generate notifications that can be received by the Notification Class recipient, the object must have a special type of LENUM point associated with it.
− The same characteristics as the Alarm LENUM.
Event Enable: A user can check or uncheck the boxes in this section to activate or deactivate Transitional States for this Event Enrollment Object.
• If the site is using RENO, these boxes must be checked.
BACnet and APOGEE Alarming
Siemens Industry, Inc. 327
Object Property Reference: This section contains information on the reference point used by the Event Enrollment Object. Clicking the Select Object button allows a user to select the reference object.
• Once a reference point is selected, the fields in this section auto-populate with the objects information.
• The fields in this section may also be manually populated. This is not recommended.
Event Type and Parameters: This section allows the user to select the type of Event Enrollment to configure. The specific parameters will vary based upon the type of Event Enrollment selected.
Event Enrollment is the only way to make unbundled PTEC subpoints alarmable. It is also a substitute for some Enhanced Alarming features.
Alarm Enable/Disable
Operator-initiated and PPCL-initiated alarm enable/disable are not available for BACnet.
Floating Alarm Limits
Floating Alarms (in which the alarm setpoint moves with the value of another point) are available with the APOGEE BACnet solution using the event enrollment object in Field Panel Firmware Revision 3.2 or later.
In Field Panels before Firmware Revision 3.2, use PPCL to create floating alarms. See the Creating Multiple Alarm Levels For Analog Points section of BACnet Modular Building Controller Power Open Processor Start-up Procedures (145-024) and BACnet Modular Equipment Controller (MEC) and Point Expansion Module (PXM) Start-up Procedures (145-025).
System Messages
Some examples of APOGEE Automation System events are PPCL run-time errors and Logon/Logoff messages. The APOGEE Automation System messages are available to third-party devices delivered using unconfirmed text message service.
Initials
When alarms are acknowledged by an Insight operator, the correct user initials will be displayed. Alarms that are acknowledged by a third-party system will display BAC at the Insight workstation. The initials SYS will be displayed at the Insight workstation for alarms that do not require acknowledgements.
Chapter 10–BACnet Alarming
328 Siemens Industry, Inc.
Alarm Acknowledgements
In BACnet, each one of the three state transitions (To-OffNormal, To-Fault, and To-Normal) can require a separate acknowledgement. If an operator acknowledges an item in the alarm window from the Insight workstation, it will send up to three acknowledgements to the BACnet device (software keeps track of how many acknowledgements to send).
A means to acknowledge a single transition is not provided.
Conversely, if a third-party workstation acknowledges only one state, when three states require acknowledgement, the Insight application will not display the alarm as acknowledged until all three states have been acknowledged.
Get Event Information vs. Alarm Summary
The BACnet Get Event Information service (labeled geteventinformation) allows a BACnet device (field panel) to be periodically asked for all of its alarms. The Insight BACnet option supports this service. If a BACnet device also supports this service, the Insight application will learn this and display any alarms for the device. Insight asks for the alarms when the Insight application starts up and after a device returns from failure or being unconnected. This is a feature of APOGEE field panels, but not all third-party devices do this.
Additionally, the Insight workstation checks its existing list of alarms and makes sure they are up to date. For example, suppose Point A is in alarm and needs to be acknowledged. Then, the device that contains Point A fails but comes back later with Point A not in alarm and not needing to be acknowledged. The Insight alarm window will update with this new information. It will show the point’s new status and show the point as acknowledged.
APOGEE BACnet field panels support the get event information service as a replacement for the Alarm Summary function. The Insight BACnet Option still supports the Alarm Summary for devices that support only Get Alarm Summary function (for example, old BACnet field panels).
Unknown BACnet Alarms
If an alarm comes in for a point that is not known or has been deleted, then the name of the point will be the encoded name, such as, BAC_1234_AO_3 (BACnet device Instance Number 1234, Analog Output Instance 3).
Life Safety Alarms
Only alarms for the following standard point types are displayed:
BACnet and APOGEE Alarming
Siemens Industry, Inc. 329
• Binary Input
• Binary Output
• Binary Virtual
• Analog Output
• Analog Input
• Analog Virtual
• Multi-state Input
• Multi-state Output
• Multi-state Virtual
A registry key has been added to allow alarms for object types that are not supported by the Insight application as points to be displayed. The key is called ShowAlarmsForAllObjects and is under the client key.
• If the key is set to 1, then the Insight application displays alarms for Life Safety Points, Life Safety Zones, Loops, etc.
• If the key is 0 (the default), the Insight application only shows alarms for the standard point types (BI, BO, BV, AO, AI, AV, MI, MO, MV, EE).
BACnet Text Messages
In BACnet, confirmed/unconfirmed text messages can be sent to a device. If the Insight application receives any messages, they will be displayed in the ALN messages pane of the alarm window. The messages will also be logged in the system activity log.
Alarm Priority
The alarm priority found in a point’s Notification Class object has a value from 0 to 255. This alarm priority is mapped to the six APOGEE alarm levels (Table 47).
Table 47. BACnet Alarm Priority mapping to APOGEE.
BACnet Notification Class Alarm Priority APOGEE Alarm Level mapping
1 - 31 A1 (life safety)
32 - 63 A2 (property safety)
64 - 95 A3 (supervisory)
96 - 127 A4 (trouble)
128 - 191 A5 (high priority alarms)
192 - 255 A6 (low priority alarms)
Chapter 10–BACnet Alarming
330 Siemens Industry, Inc.
The A1-A6 alarm levels display for BACnet points in all applications that display priority. Table 48 lists alarm display examples.
Table 48. BACnet Alarm Displays.
BACnet alarm level Displayed as *A6*, for example. (Similar to APOGEE enhanced alarms)
BACnet normal state Displayed as –N– regardless of the TO-NORMAL priority
BACnet fault state Displayed as *F* regardless of the TO-FAULT priority.
Alarm Messages
Although BACnet supports sending an unlimited-sized text message with an alarm, Insight truncates the message to 200 characters. These messages are numbered and defined in the BACnet Field Panel Definition.
• With Intrinsic Alarming, a message number can be entered in the alarmed point definition. (These are the same messages that are used for APOGEE enhanced alarms).
• With Algorithmic Alarming, a message number must be entered in the Event Enrollment Object.
Insight 3.10 and earlier does not support entering a message number in the Event Enrollment dialog box. If a message number is desired, use the field panel HMI to both create the Event Enrollment object and enter the associated field panel message number.
If the BACnet Field Panel Definition does not have any messages defined (only a message #0), one can be defined for the point in the Point Editor (Alarm Type, Alarm Properties), and the Insight alarm window will use that one. The message #0 triggers Insight to look in its message database.
BACnet Browser
Point Objects
When viewing point objects with the BACnet Browser, each point type has properties associated with intrinsic alarming. If the point is configured for alarms, the properties are readable as a group. If the point is NOT alarmable, the properties do not appear.
The Event_Enable property displays a point’s ability to send alarms as follows:
• All three bits are TRUE if the point is alarmable AND alarms are enabled.
• All three bits are FALSE if the point is alarmable AND alarms are disabled.
• There may be a mix of TRUE and FALSE.
RENO Notification
Siemens Industry, Inc. 331
The Event_Enable property may be written for:
• Alarm enable–all flags set to TRUE.
• Alarm disable–all flags set to FALSE.
• Point Add–mix and match of TRUE and FALSE.
• Point Modify–mix and match of TRUE and FALSE.
The Event_Enable property may be edited within the BACnet Browser. Any change to the Event_Enable bits will refresh the Browser display and will trigger a point upload, but will not cause an annunciation.
RENO Notification RENO notifications can be sent from BACnet points. BACnet points can have RENO notifications on Alarm Priorities 1 through 6. To send a RENO notification when a BACnet point goes into alarm, the appropriate Ack required choice for the desired transition must be checked in the BACnet Notification Class dialog box.
RENO notification examples:
• For a RENO notification of a TO-OFFNORMAL transition, Ack required for To Off-Normal transitions must be checked.
• For a RENO notification of a TO-FAULT transition, Ack required for To Fault transitions must be checked.
It is suggested that ALL of the “Ack required…” check boxes be checked when RENO notification is required.
APOGEE GO APOGEE GO can display BACnet alarms like any other APOGEE alarms. However, it does not provide any capability for setting up alarm functionality. For example, Notification Class and Alarm Message dialog boxes are not accessible.
Setting Up BACnet Algorithmic Alarming
Point Editor Event Enrollment
The Insight Point Editor application is used to enable the BACnet algorithmic alarming (event enrollment) functions for a BACnet point. The Event Enrollment button in the Point Editor is displayed on all dialog boxes for all APOGEE point types that map to BACnet point types (Table 49).
Chapter 10–BACnet Alarming
332 Siemens Industry, Inc.
Table 49. Point Type Mapping in APOGEE.
APOGEE Point Type
Physical or Virtual APOGEE Point
BACnet Point Type
LPACI Physical Analog Input
Virtual Analog Value
LENUM N/A Multistate Value
LDO, L2SP, L2SL Physical Binary Output
Virtual Binary Value
LOOAP, LOOAL, LFSSP, LFSSL N/A Multistate Output
LDI Physical Binary Input
Virtual Binary Value
LAO Physical Analog Output
Virtual Analog Value
LAI Physical Analog Input
Virtual Analog Value
Figure 138, Figure 139, and Figure 140 show Point Editor dialog boxes for points respectively on a Siemens BACnet panel, a third-party BACnet panel, and a BTEC team member point. The Related BACnet Objects group box contains the Event Enrollment button to set up BACnet Event Enrollment Objects.
The Related BACnet Objects group does not display in the Point Editor dialog box for APOGEE points (non-BACnet Points).
Setting Up BACnet Algorithmic Alarming
Siemens Industry, Inc. 333
Figure 138. Example Siemens BACnet Panel Point Editor Dialog Box.
Chapter 10–BACnet Alarming
334 Siemens Industry, Inc.
Figure 139. Example Third-Party BACnet Panel Point Editor Dialog Box.
Setting Up BACnet Algorithmic Alarming
Siemens Industry, Inc. 335
Figure 140. Example BTEC Team Member Point Editor Dialog Box.
The Event Enrollment button opens the Event Enrollment Objects (EEO) dialog box (Figure 141), which contains a list of all EEOs monitoring the point. The point being monitored is listed in the Referenced Object column.
All the lines display the same Referenced Object – the point being monitored.
Figure 141. Event Enrollment Objects (EEO) Dialog Box.
Chapter 10–BACnet Alarming
336 Siemens Industry, Inc.
Although all listed event enrollment objects refer to the same referenced object, they may reside at different devices (all ALN devices that can be selected from the Object Selector). For example, in Figure 141, Event Enrollment Objects (EEOs) in devices C1BACALNCAB24_2124 and C1MS/TPALN100_2130, both reference point C2124LAO (the Referenced Object). Although these two EEOs both use the out-of-range Event Type, it is not necessary that they do so. Thus, different Event Types can apply to the same referenced object.
Clicking the Add, View/Modify, or Copy buttons launches the BACnet Event Enrollment Properties dialog box. (The user must have Configure/Edit access to either the Point Editor or System Profile to do this.)
Adding, modifying, or removing a Change of Life Safety EEO is not allowed in the Insight Version 3.10 software.
Event Enrollment Object Creating and Editing
The Event Enrollment Objects (EEO) dialog box provides a means to add a new EEOs, or modify or copy the properties of a selected EEO. Choosing the Add, View/Modify or Copy buttons, opens the BACnet Event Enrollment Object Properties dialog box (Figure 142).
With Insight 3.10 and earlier, if a field panel numbered message is required to appear in the Alarm Status box when an EEO alarm occurs, the EEO must be created using the field panel HMI, not the BACnet Event Enrollment Object Properties dialog box. See Event Enrollment Object Alarm Messages in this chapter.
• The Add button opens a new, blank EEO editing dialog box where the Referenced Object field is populated with the point’s name and is disabled.
• The Modify button opens the same dialog box , which is populated with the property values of the select EEO.
• The Copy button opens the same dialog box and allows you to create a copy of the selected EEO. The Instance # (number) of the copy will be blank or sent to -1, and it’s Name and Description fields will be blank. The value of all other fields or properties will be identical to the original EEO.
Setting Up BACnet Algorithmic Alarming
Siemens Industry, Inc. 337
Figure 142. Example Event Enrollment Object Properties Dialog Box.
The BACnet EEO Properties dialog defaults to the most meaningful choices for the event type chosen. For a specified referenced object, the dialog box will default to Present_Value for the referenced property.
The system will not verify that the notification class is defined, but an invalid Instance Number will generate an error message. For example, a negative invalid Instance Number is invalid.
The Change of Life Safety Event Type is always disabled. The Insight application will display EEOs with Change of Life Safety Event Type, but you can only view the EEO. However, you are not allowed to create, modify, or delete it.
The BACnet Event Enrollment Object Properties dialog box will not restrict meaningless choices.
Event Enrollment Object Alarm Messages
With Insight 3.10, to make a controller's alarm message appear in the alarm status box when an Event Enrollment Object goes into alarm, requires a special procedure. The EEO is not created using the Insight EEO dialog boxes.
Chapter 10–BACnet Alarming
338 Siemens Industry, Inc.
Before creating the EEO, you must know about EEO shadow points. When you create an Event Enrollment object, Insight automatically creates a LENUM shadow point with a name in the format BAC_<PANEL ID>_EE_<ID#. The shadow point exists only in the Insight database, not in the field panel. However, the shadow point appears in the object selector and can be brought up in the Point Editor (Figure 143). When editing the EEO in the Point Editor, the Object field in the Reference Object and Property group box will be disabled and preset to the point’s system name.
Figure 143. Object Selector displaying EEO Shadow Points
Use the procedure for associating controller alarm messages with EEOs:
1. Call up the Object Selector from the Point Editor. Make note of the last shadow point name. For example, in Figure 143 it is BAC_2124_EE_6.
2. Create an Event Enrollment object using the field panel HMI rather than using Insight. (You cannot configure or view the alarm message number associated with an EEO at Insight.) The HMI prompts will include a prompt for an Alarm Message number. This is where you enter the number of the alarm message you want to appear in the Alarm Status box.
Setting Up BACnet Algorithmic Alarming
Siemens Industry, Inc. 339
3. Again, call up the Object Selector from the Point Editor. Make note of the new last shadow point name. For this example it should now be BAC_2124_EE_7. This is the shadow point associated with the Event Enrollment Object.
4. Go into the Point Editor and make the shadow point BAC_2124_EE_7 alarmable. (It does not matter what alarm message number is selected for the EEO. The important thing is to make the shadow point alarmable.)
The alarm message that appears at Alarm Status is the one whose number was entered when creating the EEO at the panel HMI.
Alarm Messages
Alarm messages are created by clicking the Alarm Messages button in the BACnet Field Panel Definitions dialog box (Figure 14) and then creating/editing a message in the Alarm Message Definition dialog box (Figure 15 and supporting text).
Alarm Notification Classes
Alarm Notification Class Instance Numbers are created by clicking the Notification Class button in the BACnet Field Panel Definitions dialog box (Figure 14) and then adding/modifying a Notification Class in the BACnet Notification Class dialog box (Table 10, Figure 16, Figure 19 and supporting text).
Recipient List
Create a Recent List for the selected Notification Class using the BACnet Destinations dialog box (Figure 17 and Figure 18 and supporting text).
Alarm Priority Colors
As necessary, customize alarm priority colors using the Insight Definition dialog box (Figure 154 and supporting text).
Table 50. BACnet EEO Properties.
Field User Configurable BACnet EEO Property
Displayed Value
EEO List Device Not a BACnet EEO property System Name
EEO List Instance #
Part of Object_Identifier Integer
EEO List, Name Object_Name See Notification Classes
EEO List, Description
Description See Notification Classes
Device Name Not a BACnet EEO property System Name
Instance # Part of Object_Identifier Integer
Chapter 10–BACnet Alarming
340 Siemens Industry, Inc.
Field User Configurable BACnet EEO Property
Displayed Value
Name Object_Name See Notification Classes
Description Description See Notification Classes
Referenced Object
Part of Object_Property_Reference
Point’s System Name (edit field is disabled)
Referenced Property
Part of Object_Property_Reference
Name of a property of the current BACnet point object. For wexample, present-value, status-flags, etc. (Edit field is disabled, use Configure button to change value.)
Event Type
Notify Type
Event Enable
Notification Class Notification_Class Instance number of a local notification class
Event Parameters tabbed control
Event_Parameters See BACnet Standard section 12.12.7
The Configure Event Parameters dialog box (Figure 144) in the BACnet browser for editing event parameters in shows how tabbed control is used to set up event parameters based on a selected event type.
Figure 144. Example Configure Event Parameters Dialog Box.
The system will not verify that the notification class is defined, but an invalid Instance Number will generate an error message. For example, a negative invalid Instance Number.
The Change of Life Safety Event Type is always disabled. The Insight application will display EEOs with Change of Life Safety Event Type, but you can only view the EEO. However, you are not allowed to create, modify, or delete it.
Setting Up BACnet Intrinsic Alarming
Insight
To enable alarms from a BACnet TEC or third-party device, you must set up a virtual point in the supervisory panel.
Point Alarm Setup
Insight’s Point Editor application (see Figure 145, Figure 146, and Figure 147) is used to enable the BACnet alarming functions of a BACnet point by doing the following:
• In the Alarm Type section, choose Standard Alarms.
Setting Up BACnet Intrinsic Alarming
Siemens Industry, Inc. 341
• In BACnet settings, enter a Notification Class number. Creating Notification Classes is explained in the Notification Classes section. For LENUM (BACnet Multistate) points, enter the Alarm Values that the Present_Value should equal to generate an alarm.
• In Alarm Characteristics:
− Enter the high and low alarm limit values (analog points only).
− Select which types of transitions are to annunciate an alarm (TO NORMAL, TO OFF-NORMAL, TO FAULT).
− Enter the Alarm Message Number to be sent when an alarm occurs. Use 0 to indicate you want to use the alarm message defined locally in the Point Editor.
Dynamic COV and Enhanced Alarms are not supported in BACnet.
Figure 145. Point Editor LDO Point Fields Related to Alarming.
Chapter 10–BACnet Alarming
342 Siemens Industry, Inc.
Figure 146. Point Editor LAO Window Showing Notification Class Field.
Figure 147. Point Editor LENUM Window Showing Alarm Values Setting.
Setting Up BACnet Intrinsic Alarming
Siemens Industry, Inc. 343
Alarm Notification Classes and Messages
Alarm Notification Classes and Messages are created for a Siemens Field Panel using the System Profile application. Open the BACnet Field Panel Definition Window for the desired field panel by double-clicking on the field panel symbol (Figure 148). The Notification Classes and Alarm Messages buttons are used to open their respective dialog boxes.
Figure 148. BACnet Field Panel Definition Window.
Chapter 10–BACnet Alarming
344 Siemens Industry, Inc.
Alarm Messages
The Alarm Messages button displays the Alarm Message Definition dialog box. Clicking the New button allows you to create a new message with a new ID number (Figure 149). You can create up to 250 messages, and each message can have up to 200 characters (4 lines of 50 characters each).
Figure 149. Alarm Message Definition Dialog Box.
Notification Classes
The Notification Classes button displays the Notification Classes dialog box. You can create new Notification Class Instances by clicking the Add button, which displays the BACnet Notification Class dialog box (Figure 150).
The name and descriptor of the Notification Class object can describe the group of recipients of the alarms or the type of alarms that should use this Notification Class.
Alarm priorities in a point’s Notification Class object can each be assigned values from 0 to 255. Table 51 shows how this alarm priority is mapped to the six APOGEE alarm levels.
Table 51. BACnet Notification Class Alarm Priority Mapping.
BACnet Notification Class Alarm Priority APOGEE Alarm Level Mapping
1 - 31 A1 (life safety)
32 - 63 A2 (property safety)
64 - 95 A3 (supervisory)
96 - 127 A4 (trouble)
128 - 191 A5 (high priority alarms)
192 - 255 A6 (low priority alarms)
Setting Up BACnet Intrinsic Alarming
Siemens Industry, Inc. 345
The BACnet Notification Class dialog box (Figure 150) also allows you to define whether a certain alarm transition must be acknowledged. Check boxes are provided for each transition type.
To send a RENO notification when a BACnet point goes into alarm, the appropriate Ack required choice for the desired transition must be checked. For example, for a RENO notification of a TO-OFFNORMAL transition, Ack required for To Off-Normal transitions must be checked.
Figure 150. BACnet Notification Class Dialog Box.
Recipient List
Create a Recipient List for the selected Notification Class. In the Notification Class dialog box, click the lower Add button to open the BACnet Destination dialog box (Figure 151).
Chapter 10–BACnet Alarming
346 Siemens Industry, Inc.
Figure 151. Recipient Creation using the BACnet Destinations Dialog Box.
The BACnet Destination dialog box has the following sections:
• Recipient–The easiest way to identify a recipient is by Device Instance number. To determine an Insight workstation’s Instance Number, open the System Profile and double-click on the ALN serving the device originating the alarm. The Building Level Network Definition dialog box opens and displays and the Instance Number of the Insight assigned to the ALN displays (Figure 152).
If the recipient is receiving its IP addresses via DHCP, you MUST identify it using its Device Instance number.
• Recipient Process–This number is obtained from the manufacturer of the field panel originating the alarm.
• Transitions–Check the transitions that must be sent to this recipient.
For a specific event transition (TO-OFFNORMAL, TO-FAULT, or TO-NORMAL) to reach a recipient, that transition choice has to be selected BOTH in the source object (Point) AND in the destination (recipient) record.
• Valid Days and Period–Use these sections to coordinate the alarm destinations based on day and time. For example, critical HVAC alarms can be programmed to go to the HVAC workstation during regular business hours, and to the Security workstation after hours and on weekends.
• Notifications–Confirmed Notifications should be chosen for high priority alarms.
Setting Up BACnet Intrinsic Alarming
Siemens Industry, Inc. 347
Figure 152. Viewing an Insight’s Instance number from System Profile.
Additional Notification Classes and Recipient Lists
Create additional Notification Classes and Recipient Lists as required using the Add button (Figure 153).
Figure 153. Additional Notification Classes in Dialog Box.
After setting up your notification classes, you should upload the field panel again. This will allow graphics to show the correct alarm priority.
Chapter 10–BACnet Alarming
348 Siemens Industry, Inc.
Alarm Priority Colors
Each alarm priority level has a color associated with it for use in the Insight alarm band and graphics. The colors can be customized from the default assignments in the Insight Definition dialog box (Figure 154). This is accessed by double-clicking the desired Insight workstation icon in the System Profile application.
Figure 154. BACnet Alarm Color Selections on the Insight Definitions Dialog Box.
BACnet Intrinsic Alarming Example Figure 155 shows an example of applying BACnet Intrinsic Alarming to a VAV air handling system. The AHU has the following components:
• Mixed air dampers
• Cooling coil
• Low temperature detector switch (LTD)
• Differential pressure flow-proofing switch (DI for L2SL)
• Fan with relay requiring a latched contact (DO for L2SL)
BACnet Intrinsic Alarming Example
Siemens Industry, Inc. 349
• Supply air temperature sensor (SAT)
• Supply static pressure sensor (SSP)
Figure 155. Example Air Handling Unit for BACnet.
The requirement is to apply alarms to the L2SL, LTD, SAT, and SSP points.
L2SL Point
A supply fan alarm must occur if the differential pressure proofing switch does not close 60 seconds after the fan has been commanded to the ON state. In the Point Editor, a L2SL point is created (Figure 156). BACnet-specific entries are made as follows:
• Addresses–The address of the digital output controlling the fan relay (0.0.25), the address of the digital input proofing switch (0.0.1), and the value of 60 for the Proof Delay seconds are entered.
• BACnet Settings–A -1 is entered for auto assignment of the point’s Instance Number and 1 is entered for Notification Class. For details, see Figure 163.
• Relinquish Default is set to OFF.
• Alarm Type–Standard Alarms is selected. The Alarm Properties button does not need to be clicked because there are no entries to be made in this point’s Standard Alarm Setup dialog box.
• Alarm Characteristics–This fan system’s operation is important, so alarms are to annunciate on all three types of transitions. Alarm Message #2 is to appear in the alarm banner. For details, see Figure 163.
Chapter 10–BACnet Alarming
350 Siemens Industry, Inc.
Figure 156. Example Supply Fan L2SL Point.
LTD Point
A low temperature alarm must occur if the low temperature detector switch (“freeze stat”) trips. In the Point Editor, a LDI point is created as shown in Figure 157. BACnet-specific entries are made as follows:
• Address–The address of the physical digital input (0.0.2), is entered.
• BACnet Settings–A -1 is entered for auto assignment of the point’s Instance Number and 1 is entered for Notification Class. For details, see Figure 162.
• Relinquish Default is set to OFF
• Alarm Type–Standard Alarms is selected. The Alarm Properties button does not need to be clicked because there are no entries to be made in this point’s Standard Alarm Setup dialog box.
• Alarm Characteristics–The low temperature device has to be manually reset at the device, so it is decided that it is not necessary to annunciate transitions to
BACnet Intrinsic Alarming Example
Siemens Industry, Inc. 351
Normal. Alarm Message #3 is to appear in the alarm banner. For details, see Figure 163.
Figure 157. Example Low Temperature Device Digital Input Point.
SAT Point
An alarm must occur if the supply air temperature is too low or too high. In the Point Editor, a LAI point is created (Figure 158). BACnet-specific entries are made as follows:
• Address–The address of the physical analog input (0.0.17) of the BACnet device, is entered.
• BACnet Settings–A -1 is entered for auto assignment of the point’s Instance Number and 1 is entered for Notification Class. For details, see Figure 162.
• Relinquish Default–Is set to 55°F.
Chapter 10–BACnet Alarming
352 Siemens Industry, Inc.
• Alarm Type–Standard Alarms is selected. The Alarm Properties button is clicked because there is to be a private message entered in this point’s Standard Alarm Setup dialog box (Figure 159).
• Alarm Characteristics–High and Low Alarm Limits are set to 65 and 45°F, respectively (10 degrees above and below the setpoint of 55°F). This temperature is to be monitored closely, so alarms are to annunciate on all three types of transitions. Alarm Message is set to #0 so that a Private Message, entered in the Standard Alarm Setup dialog box (Figure 159), will be available from the Insight alarm banner. Right click on the banner and select View Alarm Message (Figure 160).
Figure 158. Example Supply Air Temperature Analog Input Point.
BACnet Intrinsic Alarming Example
Siemens Industry, Inc. 353
Figure 159. Example Standard Alarm Setup Dialog Box for SAT Point.
Figure 160. Example Alarm Banner and Message Box with Private Message Text.
Chapter 10–BACnet Alarming
354 Siemens Industry, Inc.
SSP Point
An alarm must occur if the supply static pressure is too low or too high. In the Point Editor, a LAI point is created as shown in Figure 161. BACnet-specific entries are made as follows:
• Address–The address of the physical analog input (0.0.18) of the BACnet device, is entered.
• BACnet Settings–A -1 is entered for auto assignment of the point’s Instance Number and 1 is entered for Notification Class. For details, see Figure 162.
• Relinquish Default –Is set to 0 inches of H2O.
• Alarm Type–Standard Alarms is selected. The Alarm Properties button does not need to be clicked because there are no entries to be made in this point’s Standard Alarm Setup dialog box.
• Alarm Characteristics–The fan static pressure is important, so alarms are to annunciate on all three types of transitions. Alarm Message #4 is to appear in the alarm banner. For details, see Figure 163.
BACnet Intrinsic Alarming Example
Siemens Industry, Inc. 355
Figure 161. Example Supply Air Static Pressure Analog Input Point.
Notification Class
The BACnet points in this air handling unit all use Notification Class Instance #1. The Notification Class is set up in the Notification Classes dialog box (Figure 162). Notification Class 1, named HVAC Maintenance, has the following priorities:
• To Off-Normal–160
• To Fault–130
• To Normal–200
To Fault has the highest priority because it has the lowest number. An acknowledgement is required for all transitions that are annunciated.
Chapter 10–BACnet Alarming
356 Siemens Industry, Inc.
The Recipient List for Notification Class #1 is set up such that Insight workstation Device 15001, the HVAC Maintenance workstation, is the recipient of all transitions during regular working hours (Monday through Friday from 6 A.M. to 6 P.M.). At other times, the Security Guard workstation is the recipient of all transitions. This is accomplished by the first three line entries in the Recipient List.
Figure 162. Example Notification Class Dialog Box.
Alarm Message Definition
Three points on the air handling unit have Alarm Message Numbers assigned:
• Supply Air Fan (SAF)–Alarm Msg #2
• Low Temperature Detector (LTD)–Alarm Meg#3
• Supply Static Pressure (SSP)–Alarm Msg#4
These messages are defined in the Alarm Message Definition dialog box (Figure 163) this dialog box is accessed by clicking the Alarm Messages button on the BACnet Field Panel dialog box in the System Profile application.
BACnet Intrinsic Alarming Example
Siemens Industry, Inc. 357
Figure 163. Example Alarm Message Definition Dialog Box.
New messages are added by clicking the New button which opens the New Alarm Message dialog box (Figure 164).
Figure 164. Example New Alarm Message Dialog Box.
Chapter 10–BACnet Alarming
358 Siemens Industry, Inc.
Figure 165 and Figure 166 show examples of messages.
Figure 165. Example Alarm Message #3 Definition Dialog Box.
Figure 166. Example Alarm Message #4 Definition Dialog Box.
Siemens Industry, Inc. 359
Chapter 11–BACnet Trending Chapter 11 describes BACnet trending theory and trending in an APOGEE Building Automation System. It discusses the following topics:
• BACnet Trending Theory
• BACnet Trending in APOGEE
BACnet Trending Theory The Trend Log object, the heart of BACnet trending, monitors a property of an object. In APOGEE BACnet, this property is the Present_Value of the point-like object specified in the Log_DeviceObjectPropery (Figure 167). When predefined conditions are met, the Trend Log object writes the following to its Log_Buffer property for subsequent retrieval: the Present_Value, a time stamp, and certain status flags. Errors that prevent the acquisition of the data, as well as changes in the status or operation of the logging process are also recorded. The data may be logged at regular intervals (specified in hundredths of seconds in the Log_Interval property), or upon a change of value (COV). The COV value comes from either the Trend_Log’s Client_COV_Increment property when using Trend COV, or the trended point’s COV_Increment property when using the Point COV option (Client_COV_Increment will be NULL). Each time-stamped buffer entry is called a trend log record. The Buffer_Size property specifies the maximum number of records the buffer can hold.
Figure 167. BACnet Trending Concept Drawing.
Chapter 11–BACnet Trending
360 Siemens Industry, Inc.
In an APOGEE BACnet field panel, the trended object (point) must reside in the same field panel as the Trend Log object.
Each Trend Log object maintains an internal buffer that fills, or grows, as log records are added. If the buffer becomes full, there are two options: the oldest record is overwritten when a new record is added, or collection may be set to stop (Stop_When_Full property set to TRUE). If logging stops when full, the Log_Enable property will be set to FALSE (off). The buffer may be cleared by writing a zero to the Record_Count property. Each record in the buffer has an implied SequenceNumber which is equal to the value that the Total_Record_Count property has immediately after the record is added. If the Total_Record_Count is incremented past 232 -1, then it shall reset to 1.
Logging may be enabled and disabled (Log_Enable property) and at dates and times specified (Start_Time and Stop_Time properties). Disabling the log overrides timed operation. Trend Log enabling and disabling is recorded in the log buffer.
Notification is available to initiate automatic uploading of log records from the field panel to the mass storage device (computer). If a computer or server is set as the storage device for trends the security of the data needs to be discussed with the customer and their IT staff. The data stored should be encrypted and the access to it limited. Additionally a RAID system for recovery purposes should also be considered. For security Siemens Industry Inc. strongly suggests to follow the security layed out in ISA 62443.03.03 Level 2 for the protection of data in transit and data at rest to prevent unauthorized access, theft or modification of trend data. See also Chapter 14. BACnet supports two ways to accomplish this: algorithmic or intrinsic notification. APOGEE BACnet supports intrinsic reporting, which sends a new notification to the computer when the Records_Since_Notification, the number of records collected since the last notification (or startup), equals the Notification_Threshold property value. The sequence number of the record that triggered the notification is recorded in the Last_Notify_Record property. In response to a notification, the subscriber (computer) initiates an upload of the new records using a service called ReadRange. There is also a methodology for a subscriber to detect a missed notification by analyzing parameters of the previous and the current notification.
One of the properties of the Trend Log object is the identity (Instance Number) of a Notification Class object. This object contains a Recipient List property that identifies the devices (Insight workstations) that upload the trend data. Also identified are the days and time range in which that device will upload the trend data. The Notification Class object is in the same field panel as its related Trend Log object.
BACnet Trending Theory
Siemens Industry, Inc. 361
The acquisition of log records by remote devices has no effect upon the state of the Trend Log object itself. This allows completely independent, but properly sequential, access to its log records by all remote devices. Any remote device can independently update its records at any time.
Table 52 shows the properties of the Trend Log Object as documented in the ANSI/ASHRAE Standard 135-2004.
Table 52. Properties of the Trend Log Object Type.
Property Identifier Property Data Type Conformance Code
Object_Identifier BACnetObjectIdentifier R
Object_Name CharacterString R
Object_Type BACnetObjectType R
Description CharacterString O
Log_Enable BOOLEAN W
Start_Time BACnetDateTime O1,2
Stop_Time BACnetDateTime O1,2
Log_DeviceObjectProperty BACnetDeviceObjectPropertyReference O1
Log_Interval Unsigned O1,2
COV_Resubscription_Interval Unsigned O
Client_COV_Increment BACnetClientCOV O
Stop_When_Full BOOLEAN R
Buffer_Size Unsigned32 R
Log_Buffer List of BACnetLogRecord R
Record_Count Unsigned32 W
Total_Record_Count Unsigned32 R
Notification_Threshold Unsigned32 O3
Records_Since_Notification Unsigned32 O3
Last_Notify_Record Unsigned32 O3
Event_State BACnetEventState R
Notification_Class Unsigned O3
Event_Enable BACnetEventTransitionBits O3
Acked_Transitions BACnetEventTransitionBits O3
Notify_Type BACnetNotifyType O3
Event_Time_Stamps BACnetARRAY[3] of BACnetTimeStamp O3
Profile_Name CharacterString O 1 These properties are required to be present if the monitored property is a BACnet property.
Chapter 11–BACnet Trending
362 Siemens Industry, Inc.
Property Identifier Property Data Type Conformance Code 2 If present, these properties are required to be writable. 3 These properties are required to be present if the object supports intrinsic reporting.
For more information about APOGEE trending and how to use trend data after it is captured, see the APOGEE Trending Application Guide (125-1899).
BACnet Trending in APOGEE Firmware Revision 3.1 or later supports external trending. Users may trend properties of objects in any device on the BACnet network, including devices that do not support the BACnet trend object, such as BACnet TECs and certain third-party devices. Trending of BACnet object properties can be done by time and/or COV on any device on the BACnet network including BACnet TECs and third-party BACnet MS/TP devices.
Although BACnet trending differs from non-BACnet APOGEE trending, the APOGEE user interfaces can make the two appear to be very similar. This section explains some of the differences and how to setup an APOGEE BACnet trend.
APOGEE Trending: Non-BACnet vs. BACnet
Table 53 shows some of the differences between APOGEE non-BACnet and BACnet trending.
Table 53. Comparison of APOGEE Trending–non-BACnet vs. BACnet.
APOGEE Non-BACnet APOGEE BACnet
Trend info is in the point record Trend info (including point info) is in Trend_Log object
Optional trend trigger No trend trigger
COV and/or interval trending (can have up to 1 COV and 4 interval per point)
COV and/or interval trending (can have up to 1 COV and 4 interval per point)
Circular file only (writes over oldest data when buffer is full)
Circular file or stop-when-full feature
Data cleared when trend is disabled Can be disabled without data loss
Support for Trend Log Objects in Other Devices
Insight Revision 3.9.1 or later supports the ability to trend BACnet points in other devices. In previous revisions of the Insight software, points could only be trended in the field panels where they resided. With Insight Revision 3.9.1, you can trend BACnet points with any BACnet device that supports trend definitions (Trend Log Objects), regardless of where the BACnet points reside.
BACnet Trending in APOGEE
Siemens Industry, Inc. 363
For any particular APOGEE BACnet field panel, you can have up to five Trend Log Objects for any specific BACnet point, wherever that point may reside. As part of this, you can now create Trend Log Objects for a single point with the same sample interval as long as those Trend Log Objects reside on multiple devices.
For example, panel A can have up to five Trend Log Objects for a BACnet point, and panel B can also have up to five Trend Log Objects for that same point.
If you delete a BACnet point that has Trend Log Objects in other devices, those Trend Log Objects are not deleted. Also, if you delete a device that has Trend Log Objects for points in other devices, those points are not deleted—the points will continue to exist in the devices in which they reside.
The following applications have been updated to support Trend Log Objects in other devices.
Dynamic Plotter
The Dynamic Plotter application has been updated to support plotting of BACnet Trend Log Object data from multiple devices.
Report Builder/Viewer
The Panel Trend Data Detail and Trend Data Detail reports have been updated to include filtering options for local and remote trending (Figure 168). In the Definition Filter section, you can now specify if you want to filter by All, Local Trends, or Remote Trends.
Remote Trends only apply to BACnet points.
Chapter 11–BACnet Trending
364 Siemens Industry, Inc.
Figure 168. Trend Data Detail Report Filtering Options.
In addition to the Panel Trend Data Detail and Trend Data Detail reports, the following reports have been updated to support local and remote trending:
• Panel Trend Definition
• Trend Collection
• Trend Definition
• Trend Interval
• Trend Sample
• Trend Summary
Trend Definition Editor
Enhanced Add Trend Definition Dialog Box
The Add Trend Definition (Figure 169) dialog box has been enhanced to display all devices in which Trend Log Objects reside for a particular BACnet point.
BACnet Trending in APOGEE
Siemens Industry, Inc. 365
Figure 169. Add Trend Definition Dialog Box.
Enhanced Add COV and Add Interval Definition Dialog Boxes
To support Trend Log Objects in other devices, the Add COV Definition (Figure 170) and Add Interval Definition (Figure 171) dialog boxes have been enhanced with a Device Name field. By default, the Device Name field displays the device name in which the Trend Log Object resides. To specify a different device in which to store
the Trend Log Object, click and then select the device you want to use.
Figure 170. Add COV Definition Dialog Box.
The linked image cannot be displayed. The file may have been moved, renamed, or deleted. Verify that the link points to the correct file and location.
Chapter 11–BACnet Trending
366 Siemens Industry, Inc.
Figure 171. Add Interval Definition Dialog Box.
New Select BACnet Device(s) Dialog Box
The Trending Wizard has been enhanced with a new Select BACnet Device(s) dialog box (Figure 172), from which you can select where you want to trend BACnet points.
Figure 172. Select BACnet Device(s) Dialog Box.
When selecting BACnet points to trend, you can create trends in the device where each point resides, or create trends in other devices.
Scheduling Trends
Although the Trend_Log object has its own Start/Stop Date/Time, it can still be scheduled by the Scheduling application in the field panel. Using the Scheduling application offers more flexibility than just using the Trend_Log times. For example, Scheduling a trend allows programming different start and stop times for weekends, holidays, etc. The Trend_Log’s Start/Stop times are unchanging day after day.
BACnet Trending in APOGEE
Siemens Industry, Inc. 367
To use the BACnet Scheduler to schedule when data will be trended, you must schedule the log-enable property of an existing trend log object. To do this, follow these steps:
1. From the Tools menu in System Profile, click BACnet Object Browser.
2. In the left pane choose the field panel and open the Trend Logs folder (Figure 173).
3. Choose the trend log to schedule. Note its Instance Number (the number in parenthesis preceding the object name, for example (5) 00800003_TrendLog_6000). Double-clicking the desired object name will display its properties in the right pane. The object-identifier property contains the words trend-log- followed by the Instance Number (for example, trend-log-5).
Figure 173. Trend Logs viewed with BACnet Object Browser.
4. Open the Scheduler. From the BACnet menu, click New, and then Schedule. In the General tab (Figure 174), choose the device in which the schedule will exist. Usually this the same device that has the trend log.
Schedule Name should describe details about the trend log being scheduled.
Data Type is BOOLEAN.
Default Value is the state in which the trend log’s Log_Enable property will be set if no command is given to it. False disables the trend log.
For the Effective Period, you usually enter the period in which you want the trend log enabled, although sometimes you may want this to be the time in which the trend log is disabled.
Chapter 11–BACnet Trending
368 Siemens Industry, Inc.
Figure 174. Scheduling a Trend Log–General Tab.
5. In the Items tab (Figure 175), click Add to display the Item Properties dialog box. DO NOT click Select Point.
Object Type–Select trend-log from the drop down selections. The object-type number is automatically entered.
Object Instance–Enter the Instance Number of the trend log you selected while in the object browser.
Property ID–Select log-enable from the drop-down selections; the property ID number is automatically entered.
Do not check the Array Index box. The output of this schedule is simple BOOLEAN, not an array.
6. Click OK to close the Item Properties dialog box.
CAUTION:
If you want this schedule to command other items, their properties to be commanded must also be a data type of BOOLEAN. For one BACnet schedule to command multiple properties with mixed data types, a Command Object must be used. Put the one Command Object in the items list and put the assorted data-type properties in the Command Object.
BACnet Trending in APOGEE
Siemens Industry, Inc. 369
Figure 175. Scheduling a Trend Log–Items Tab.
Note that in the BACnet Schedule Properties dialog box (Figure 176), the trend log’s Object Name does not appear. Its object name exists in the field panel, but is not displayed.
Figure 176. BACnet Schedule Properties dialog box.
To verify that the correct object name is scheduled, use the BACnet Object Browser. Open the schedule named for the desired trend log. Double-click on the property called list-of-object-property-references. The Object ID format will have the Instance Number following the text TLOG and then the trend log name in parenthesis, for example TLOG-5 (00800003_TrendLog_6000) (Figure 177).
Chapter 11–BACnet Trending
370 Siemens Industry, Inc.
Figure 177. BACnet Object Browser to Correlate Name of Scheduled Trend Log.
Scheduling Trend Collections
Trend data can be collected (uploaded) to the storage device (computer) periodically based on a trend collection schedule. This can be in addition to the automatic notification and uploading that occurs through the Notification_Class and Notification_Threshold properties in the Trend Log object. When points are trended by the interval method, the trend buffer fill at a predictable rate, so the collection of trend data can be easily scheduled.
Schedule a BACnet trend log object using the conventional non-BACnet Insight scheduling. From either the Daily or Monthly tab, select a starting day for the trend collection on the Monthly calendar in the right hand corner of the Schedule window. Next, from the Schedule menu, select New, and then Trend Collection. When the object selector displays, select the BACnet trend log object. Click OK and complete the process by completing the fields in the Trend Collection Schedule dialog box.
The Trend Wizard automatically sets up a trend collection schedule. Trend data is collected every two hours throughout the day. Figure 178 shows a trend collection schedule established by the trend wizard.
BACnet Trending in APOGEE
Siemens Industry, Inc. 371
Figure 178. Trend Collection Schedule automatically set up by Trend Wizard.
Setup Steps
Even though BACnet trending is based around the Trend_Log object, the Insight Trending user interface for BACnet bases the trend on the point being trended. This is the same as regular APOGEE trending. Therefore, when creating, modifying or deleting a trend, you start by selecting the point being trended.
BACnet trends are setup like any APOGEE trend–through the Trend Definition Editor (Figure 179) in the Insight software or Commissioning Tool.
Figure 179. Trend Definition Editor Window.
New trends can be created or existing trends can be opened (for viewing or modification) or deleted by using the corresponding commands on the Trend menu in the Trend Definition Editor window (Figure 180).
Chapter 11–BACnet Trending
372 Siemens Industry, Inc.
Figure 180. Trend Definition Editor–Trend Menu.
The Object Selector dialog box is used to select points for new trends or points that are currently being trended (Figure 181 and Figure 182).
Figure 181. Object Selector Dialog Box Showing a Trended Points Group.
BACnet Trending in APOGEE
Siemens Industry, Inc. 373
Figure 182. Object Selector Dialog Box Showing Points in a Trend Group.
Once a point is selected, the Trend Type is chosen for new point trends or is displayed for existing point trends. See Figure 183 for Trend Type dialog box. A BACnet point in an APOGEE field panel can have one COV and up to four interval trend types. The trend wizard can be employed to set up a trend in an APOGEE BACnet field panel.
Figure 183. Trend Type Dialog Box.
After a trend type is chosen the COV (Figure 184) or the Interval (Figure 185) Definition dialog box opens. Assuming a BACnet point was chosen for the trend, the BACnet Settings section is enabled, but the Conditional Trending section and the Enable “Buffer Full” Notification option are disabled. Trigger points are not supported and the Trend_Log object has its own Notification Threshold for BACnet trends in APOGEE BACnet field panels.
Chapter 11–BACnet Trending
374 Siemens Industry, Inc.
Figure 184. Add COV Definition Dialog Box.
Figure 185. Add Interval Definition Dialog Box.
For a BACnet trend definition, you must provide an Object Name. The Object Name must be unique within a panel.
• If you are entering the Object Name manually, consider using a naming format that includes information about the trend and the point trended. The reason is that the BACnet Object Browser only displays the trend log object name, type, Instance Number, present value and status. Encoding trend details in the name will make the object browser more convenient. For example, for the trend described in Figure 185 use AHU1_SAT_I15m. I15m means interval, 15 minutes. For the trend described in Figure 184 use AHU1_SAT_C1F. C1F means COV, 1°F.
• If the Trend Wizard is used, a configured object name is automatically entered. The format of the name generated by the wizard is:
BACnet Trending in APOGEE
Siemens Industry, Inc. 375
Trended Object Type + Instance number + ”_trendlog_” + Interval Where: Interval is in hundredths of seconds (6000 = 1 minute). 0 means COV trend Trended Object Type number relates to the trendable object types as follows: OBJECT_ANALOG_INPUT = 0 OBJECT_ANALOG_OUTPUT = 4 OBJECT_ANALOG_VALUE = 8 OBJECT_BINARY_INPUT = 12 OBJECT_BINARY_OUTPUT = 16 OBJECT_BINARY_VALUE = 20 OBJECT_MULTISTATE_INPUT = 52 OBJECT_MULTISTATE_OUTPUT = 56 OBJECT_MULTISTATE_VALUE = 76
For example: 00800003_TrendLog_0 is the wizard-created name of a COV trend of an Analog Value object of Instance Number 3.
The Description is optional. The wizard does not enter a Description.
The Instance Number must be unique within a device. Leave it set to –1 to have the panel assign the instance automatically. (The Object Identifier property is made up of the Object Type (Trend_Log) and the Instance Number.) When modifying a BACnet trend definition, you cannot change the Instance Number.
The Notification Class is the Instance Number of the Notification Class object that is to be notified when the buffer reaches the Notification Threshold. The Notification Class object has the recipient list that includes the identity of the computer that will upload the trend data, see Notification Class section in this chapter.
The Notification Threshold is the number of samples at which the device will notify the Notification Class object that the buffer is getting full and needs to be collected. This value should be less than the maximum samples at the device.
Stop when full is a flag that indicates whether the device will stop collecting data when the buffer is full (instead of overwriting the oldest data). It defaults to unchecked.
The start and stop date/time can be specified to only collect data for certain dates or hours during the day. If any of the fields are wild carded in the start date/time, then trending will start immediately, if any are wild carded in the stop date/time, then trended will continue forever. There are buttons to bring up a dialog box that edits the dates/times.
Clicking the button displays the Enter Date/Time dialog box (Figure 186)
CAUTION:
You cannot create trend definitions in third-party BACnet panels.
Chapter 11–BACnet Trending
376 Siemens Industry, Inc.
Figure 186. Enter Date/Time Dialog Box.
Notification Class
The Notification Class object contains a list of what devices (Insight workstations) are notified to upload a trend log buffer when it reaches its notification threshold. A Notification Class is created for a Siemens field panel through the System Profile application. Double-clicking on the desired field panel symbol opens the BACnet Field Panel Definition window. See Figure 187 and note the Notification Classes button.
BACnet Trending in APOGEE
Siemens Industry, Inc. 377
Figure 187. BACnet Field Panel Definition Window.
The Notification Classes button displays the Notification Classes dialog box. New Notification Class Instances can be created by clicking Add, which displays the BACnet Notification Class dialog box (Figure 188).
The name and descriptor of the Notification Class object can be written to encode the name of the group of recipients of the trend data or the type of trend data that uses this Notification Class.
The Priority values relate to the BACnet events (transitions) that are generated by the Trend_Log object. For APOGEE BACnet field panels, only the To Normal Priority is used for trending. This transition occurs when a notification is triggered–the value of the Records_Since_Notification property becomes equal to or greater than the value of the Notification_Threshold property. This number can be high (192 through 255) for trend data of low importance and lower (128 through 191) for important trend data.
The Trend Log TO-FAULT transition is intended for failed COV subscription attempts, but since APOGEE requires the Trended point, Trend Log and Notification Class to be in the same panel, COV subscription is not used. The To Off-Normal Priority and the Ack field are in the Notification Class object for when it is used for alarming (Notify_Type property is Alarm) and can be ignored for trend notification.
As explained in Chapter 10–BACnet Alarming, the alarm priorities in a Notification Class object can each be assigned values from 0 to 255. This alarm priority is mapped to the following six APOGEE alarm levels:
Chapter 11–BACnet Trending
378 Siemens Industry, Inc.
0-31 is A1 (life safety)
32-63 is A2 (property safety)
64-95 is A3 (supervisory)
96-127 is A4 (trouble)
128-191 is A5 (high priority alarms)
192-255 is A6 (low priority alarms)
None of the Ack (acknowledge) check boxes need be selected.
Figure 188. BACnet Notification Class Dialog Box.
Recipient List
The Recipient List defines what device (Insight workstation) is notified to upload a trend log buffer when it reaches its notification threshold. Create a Recipient List for the selected Notification Class by clicking the lower Add button in the Notification Class dialog box to open the BACnet Destination dialog box (Figure 189).
BACnet Trending in APOGEE
Siemens Industry, Inc. 379
Figure 189. Recipient Creation using the BACnet Destinations Dialog Box.
The BACnet Destination dialog box has the following sections:
• Recipient–The easiest way to identify a recipient is by Device Instance number. To determine an Insight workstation’s Instance Number, Open the System Profile and double-click on the ALN serving the device originating the alarm. The Building Level Network Definition dialog box will display the Instance Number of the Insight workstation assigned to the ALN will appear (Figure 190).
Chapter 11–BACnet Trending
380 Siemens Industry, Inc.
Figure 190. Viewing an Insight’s Instance number from System Profile.
• Recipient Process–This number is obtained from the manufacturer of the field panel originating the alarm. The APOGEE Automation System enters 600 by default.
• Transitions–Check only the TO NORMAL box.
• Valid Days and Period–To ensure unimpeded collection of trend data check all days and select the <any> wildcard entry for the dates.
• Notifications–Confirmed Notifications should be chosen for high priority trend data.
Create additional Notification Classes and Recipient Lists as required using the Add button.
BACnet Trending in APOGEE
Siemens Industry, Inc. 381
Siemens Industry, Inc. 383
Chapter 12–BACnet Tools Chapter 12 describes tools for analyzing BACnet communications in an APOGEE Building Automation System. It discusses the following topics:
• BAS-o-matic Protocol Analyzer
• Commissioning Tool Support for APOGEE BACnet Field Panels
• Insight BACnet Communications Tools
BAS-o-matic Protocol Analyzer Cimetrics™ BAS-o-matic is a tool for analyzing communication packets on a network–a type of Packet Sniffer. To debug communication problems, the user captures packets and then sends them to the manufacturer of the device that generated the packets so they can be analyzed. In the case of Siemens, the packets are sent to field support.
BAS-o-matic can be run on the Insight competitor on other computers (notebooks) when desired. This allows flexibility in where and when the tool is used. Using the Insight workstation is usually easier, and BAS-o-matic does not in any way interfere with Insight operations. BAS-o-matic will work on Ethernet, BACnet/Ethernet, BACnet/IP, BACnet MS/TP, and Modbus.
BAS-o-matic enables the network card's promiscuous mode and can capture network traffic on the local segment of the LAN. Thus, it normally captures and analyzes packets addressed to all of the computers on the segment, not only to the one where the program is running. There are certain limitations for Wireless Ethernet adapters (you can monitor only inbound/outbound traffic) and switched networks.
Obtaining BAS-o-matic
BAS-o-matic is a product of Cimetrics, Inc. A free version of the installation program (demo version - no license or dongle required) is included with Insight Revision 3.7. It is located on CD#3 as a zip file in a folder named BAS-o-matic. Alternatively, all versions—including the demo version—can also be downloaded from www.Cimetrics.com. From the Cimetrics’ home page, use the following path to download the installation program:
BACnet > Support Docs & Downloads > BACnet Installation Tools > B5020 - BAS-o-matic v5.0 Protocol Analyzer (10 Files) > BAS-o-matic – Demo Version
Click the Download button
Chapter 12–BACnet Tools
384 Siemens Industry, Inc.
The demonstration version has many features relative to capturing packets but, unlike the fully featured versions, does not provide for interpretation and analysis of the packets.
Connecting to a Network
When using a separate computer to run BAS-o-matic, a dumb hub or a switch that supports “port mirroring” is needed to interface the BAS-o-matic computer to the network. When using the Insight computer to run BAS-o-matic, no special network hookup is required.
A hub is needed to interface a separate BAS-o-matic computer to the network. This needs to be a truly dumb Ethernet hub–one that will show all packets at every port all the time. For example, the NETGEAR Model EN104 and model EN108. Switches (and certain hubs that act like switches) read the addresses of incoming data and allow only certain data to pass. Thus, the BAS-o-matic will only capture packets sent to and from the computer on which it is running.
BAS-o-matic will also work with switches that support port mirroring. This feature redirects the traffic of some or all ports to a designated monitoring port on the switch. Monitoring the entire LAN segment then becomes possible.
Most modern switches support port mirroring. A switch’s specifications and documentation will disclose if the switch has port mirroring. Be aware that various manufacturers name this feature differently. Table 54 is a short list of switches by three major manufacturers.
Table 54. Partial List of Switches that Support Port Mirroring.
Manufacturer Name Used for the Port Mirroring Feature
Models of Switches with Port Mirroring Support
Cisco Switched Port Analyzer (SPAN) Cisco Catalyst 1900 Series Switches
Cisco Catalyst 4500 Family Switches
Cisco Catalyst 6000 Family Switches
3COM Roving analysis port (RAP) 3Com SuperStack 3 Switch 4400
Intel Port mirroring Intel Express 460T
Intel Express 480T
Connecting a Separate BAS-o-matic Computer
To connect a separate BAS-o-matic computer to the network:
1. Acquire three regular Ethernet patch cables.
2. Disconnect the Insight workstation from the main network and plug it into the hub.
BAS-o-matic Protocol Analyzer
Siemens Industry, Inc. 385
3. Plug the BAS-o-matic computer into the hub. Connect the hub’s uplink port to the main network using the jack that the Insight computer was connected to.
4. Make sure the network card in the BAS-o-matic computer is properly installed in the operating system.
Using the Insight Workstation for BAS-o-matic
No hub or special connection to the network is needed. The Insight workstation stays plugged into the network.
Installing BAS-o-matic v5.0
Use the following steps to install BAS-o-matic:
1. Uninstall any previous versions of BAS-o-matic. In some versions of BAS-o-matic, an Uninstall option is present in the BAS-o-matic Start Menu group. If present, use this to uninstall BAS-o-matic. Otherwise, use the Add/Remove Programs applet in the Control Panel. See the caution in the Uninstalling BAS-o-matic section.
CAUTION:
Uninstalling BAS-o-matic-Copy protection–BAS-o-matic uses the same SentinelLM service as the Insight application. If both are running on the same computer, be careful when deleting either application. Deleting either application usually removes the SentinelLM service, which then disables copy protection for the software that is left. To avoid this, reinstall the remaining application to restore the SentinelLM service.
2. Unzip the compressed installation file to the computer’s drive.
3. Follow the Insight documentation or instructions downloaded from the Cimetrics Web site for installation of the dongle (not required for demonstration version) and run BAS-o-matic_v50b.exe.
4. When installing, follow the on-screen prompts. You will be instructed to close all other applications.
5. Make sure the hardware key is connected to the appropriate computer port; parallel port for a parallel port key or USB port for a USB port key. Then, select the appropriate key type in the setup dialog box during installation (Figure 191). If you do not have a key, the software will run in Demonstration mode, which will still allow you to capture the packets and send them in to Field Support for analysis.
Chapter 12–BACnet Tools
386 Siemens Industry, Inc.
Figure 191. BAS-o-matic Setup Dialog Box.
6. Run BAS-o-matic (the installation should have put an icon on the Windows Desktop). Verify operation and network connection. Fully featured (non-demo) versions should check for the hardware key, then startup. If a fully featured version comes up in “Demo Mode”, then check the dongle and the license file for problems.
7. Make sure the network interface card (NIC) is set as desired from the choices in the drop-down list box in the opening window. This should default to the network adapter of the computer in which BAS-o-matic is installed. In Figure 192, Intel® PRO/1000 MT Network Connection - Packet Scheduler Miniport is chosen.
Figure 192. Selecting Network Adapter.
Using BAS-o-matic on BACnet/IP
To begin capturing packets on a BACnet/IP network:
1. From the Help menu, click Contents & Index.
BAS-o-matic Protocol Analyzer
Siemens Industry, Inc. 387
The online help window displays.
2. In the Contents tab, expand the BACnet folder and click BACnet - Email a Capture File.
3. From the BAS-o-matic menu, click Settings, Options.
The Options dialog box displays.
4. From the Automation Protocols tab, select the BACnet/IP & B/E Plug-in in the Plug-Ins list and click the Configure.
The BACnet preferences dialog box displays.
Figure 193. BACnet Preferences Dialog Box for BACnet/IP Networks.
5. Select the Display Invoke ID checkbox so that on displays. If you know that UDP ports other than 47808 are being used for BACnet/IP on the network, enter them as comma separated values in the Listen to Ports field. Click OK twice to close the dialog boxes.
6. From the Rules tab (Figure 194), select Protocols & Direction in the left sidebar under the Simple Rules heading. Clear the Enable Ethernet protocol rules box if checked. Clear the Enable direction rules box if checked. Check the Enable IP protocol rules box. In the Enable IP protocol rules section, select UDP in the Description list. Verify that all other protocols are not selected. In the Action group, click Capture.
Chapter 12–BACnet Tools
388 Siemens Industry, Inc.
Figure 194. Rules Tab–Selecting Protocols and Direction (for BACnet/IP).
Port Rules–If capturing a specific UDP port is desired, select Ports in the navigation frame under Simple Rules.
Important:
If you are using port rules, BAS-o-matic will be unable to automatically reconstruct segmented BACnet/IP messages; therefore, port rules should not be used unless necessary.
To use port rules, select the Enable port rules box. In the Action section, select Capture. In the Add Record section, select Both, type 47808 in the field, and click Add Port. Other UDP ports can be added as well.
7. Select the Packets tab. It should be empty.
8. From the File menu, select Start Capture. If BACnet traffic exists, the window in the Packets tab should start filling with lines of information on each packet detected.
9. Perform actions on the APOGEE and/or foreign systems to investigate the problem under scrutiny.
10. After capturing data, select Stop Capture from the File menu.
11. From the File menu, select Save Packet Log As...
12. Save the log with a meaningful name and type: BAS-o-matic 5.0 Capture Files (*.ncf).
BAS-o-matic should display a message box describing how many packets were saved and to what file.
BAS-o-matic Protocol Analyzer
Siemens Industry, Inc. 389
13. If more data needs to be captured, or it only occurs after a long time, check Auto Saving on the Logging tab. Designate a directory where the log file should be stored with Save logs to:. When you start your capture, data will be sent to a default file in your designated directory each time 500 packets have been received. After a capture, click Concatenate logs… to make them into one large file. Use a compression software application (such as WinZIP®) to shrink the file for distribution via e-mail.
14. Send the saved file(s) via e-mail to the Field Support group of the manufacturer whose equipment is causing the problem.
Using BAS-o-matic for BACnet on Ethernet
Use the following steps to begin capturing packets for BACnet on Ethernet networks:
1. From the Help menu, click Contents & Index.
The online help window displays.
2. In the Contents tab, expand the BACnet folder and click BACnet - Email a Capture File.
3. From the BAS-o-matic menu, click Settings, Options.
The Options dialog box displays.
4. From the Automation Protocols tab, select the BACnet/IP & B/E Plug-in in the Plug-Ins list and click Configure.
The BACnet preferences dialog box displays.
Figure 195. BACnet Preferences Dialog Box for Ethernet Networks.
Chapter 12–BACnet Tools
390 Siemens Industry, Inc.
5. Select the Display Invoke ID checkbox so that on displays. Click OK twice to close the dialog boxes.
6. From the Rules tab, select Protocols & Direction in the left sidebar under the Simple Rules heading. Select the Enable Ethernet protocol rules box.
7. Check IEEE802.3 in the Description list. In the Action group, click Capture.
This filter will capture all the BACnet/Ethernet packets and will filter away most of the unwanted packets. This can be used in combination with other filtering options to further enhance the capability.
8. Select the Packets tab. It should be empty.
9. From the File menu, select Start Capture. If BACnet on Ethernet traffic exists, the window in the Packets tab should start filling with lines of information on each packet detected.
10. Perform actions on the APOGEE and/or foreign systems to investigate the problem under scrutiny.
11. After capturing data, select Stop Capture from the File menu.
12. From the File menu, select Save Packet Log As...
13. Save the log with a meaningful name and type BAS-o-matic 5.0 Capture Files (*.ncf).
BAS-o-matic will display a message box describing how many packets were saved and to what file.
14. If more data needs to be captured, or it only occurs after a long time, do the following: check Auto Saving on the Logging tab. Designate a directory where the log file should be stored with Save logs to:. When you start your capture, data will be sent to a default file in your designated directory each time 500 packets have been received. After a capture, click Concatenate logs… to make them into one large file. Use a compression software application (such as WinZIP®) to shrink the file for distribution via e-mail.
15. Send the saved file(s) via e-mail to the Field Support group of the manufacturer whose equipment is causing the problem.
Commissioning Tool Support for APOGEE BACnet Field Panels There are no special Commissioning Tool (CT) applications for BACnet, but all of the applications support BACnet. However, the level of support varies, as explained in the following sections.
Commissioning Tool support is limited to APOGEE BACnet devices only. Third-party BACnet devices are NOT supported.
Commissioning Tool Support for APOGEE BACnet Field Panels
Siemens Industry, Inc. 391
For the Custom Solution BACnet MEC, Commissioning Tool allows import of point information on a Microsoft Excel spreadsheet into the Point Editor. However, importing spreadsheets is not available for use with third-party field panels.
The following sections explain the levels to which the Commissioning Tool applications support APOGEE BACnet field panels.
Firmware Loading Tool
The Firmware Loading Tool (FLT) application allows you to load new firmware into a field panel's flash memory and change configuration data. FLT also provides the capability to identify and flash BACnet field panels.
HMI Database Transfer
The HMI Database Transfer (HMIXfer) application supports BACnet field panels. This involves connecting to the panel’s HMI port, building the system profile, performing backup/restore operations for ALN/FLN devices (including APOGEE BACnet devices), and communicating in terminal mode.
Build System Profile
The HMI Database Transfer application includes a Build System Profile command for BACnet field panels.
Backup/Restore
HMI Transfer application provides capability to backup/restore APOGEE BACnet field panels to the Commissioning Tool (job) database. This includes support for the following BACnet-specific objects:
• Calendar
• Command
• Notification Class
• Schedule
Terminal Emulation
Terminal Emulation is available for operator interface with a field panel. A COM port or a modem can be used for communication between a computer and a field panel.
Chapter 12–BACnet Tools
392 Siemens Industry, Inc.
Copy Field Panel
The Copy Field Panel application is used to duplicate all (or selected parts) of an existing field panel’s data (except PPCL) into a newly created field panel. The application supports BACnet by being able to duplicate an APOGEE BACnet field panel’s data to create a new BACnet field panel. Data components that must be unique in each panel, such as Instance Number and System Name, are not copied.
The Copy Field Panel application also allows duplication of an APOGEE BACnet field panel to an APOGEE Ethernet, P2, and Remote Building Level Network (ALN). The copied field panel becomes an Ethernet field panel or P2 field panel, depending on the ALN to which it is copied.
Copy Field Panel also provides functionality to duplicate an Ethernet or P2 Field Panel to a BACnet ALN. The copied field panel becomes a BACnet field panel.
Point Transfer
The Point Transfer (XPoint) application allows points to be transferred from the Job database into a Microsoft® Excel spreadsheet or from an Excel spreadsheet into the Job database. In Excel, new points can be added or existing points can be modified, and then the changes can be imported to the Job database.
Point Transfer provides limited support for APOGEE BACnet field panels. Only APOGEE non-BACnet data is transferred to or from the Excel spreadsheet.
• When transferring BACnet point data to Excel, you lose the BACnet-specific parts of the point data (Instance Number, Notification Class, Annunciate flags, etc.).
• When transferring Excel point data to a BACnet panel in the Job database, default values are inserted where possible. For example, Instance Numbers are set to -1, and Notification Class is set to 0.
Therefore, it is necessary for the user to manually fill-in the missing BACnet-specific data.
Non-Field Panel Data Transfer
The Non-Field Panel Data Transfer (NFData) application (formerly known as CT/Insight Transfer) is used for importing or exporting non-field panel data (events, graphics, reports, etc.). The application functions by transferring the data between a job database and an XML file. The Non-Field Panel Data Transfer application is included with Insight Revision 3.7 (it must be installed separately for earlier revisions).
Commissioning Tool Support for APOGEE BACnet Field Panels
Siemens Industry, Inc. 393
The Non-Field Panel Data Transfer application supports APOGEE BACnet field panels but not third-party devices.
Point Summary Report
The Point Summary Report application allows you to create a printed document that contains information about the points in field panels and devices. The information can also be exported to a Microsoft® Excel (or other) spreadsheet application. In Excel, the report can be modified, saved as an Excel worksheet, and printed.
Although the Point Summary Report application works with APOGEE BACnet field panels, reports will not contain any BACnet-specific information such as Notification Classes, Instance Numbers, etc.
Point Checkout Data
The Point Checkout Data application allows users to view a point report in Microsoft® Notepad as a comma-separated text file. The application supports APOGEE BACnet field panels, but the report does not display any BACnet-specific point data like Instance Number and Notification Class. The report displays the following information:
• Point name
• Point descriptor
• Point type
• Point address
• Alarmable
• Controller
Commissioning Report Generator
The Commissioning Report Generator (CRG) application is a tool that allows a user to create, print, and save report forms that can be used for submitting a proposed job database for review, as well as document the results of start-up and commissioning of field panels and FLN devices (for example, MBCs, TECs, Unitary Controllers).
The CRG supports the BACnet Field Panel Point Report; however, only APOGEE point-like objects appear in the report. For APOGEE BACnet field panels, the report displays the following:
• Point Address
• Present_Value
The IP address of the APOGEE BACnet panel is not displayed.
Chapter 12–BACnet Tools
394 Siemens Industry, Inc.
Insight BACnet Communications Tools Several software tools are available in the Insight System Profile application Tools menu to assist in troubleshooting BACnet communications problems.
Multiple Device Configuration
The Multiple Device Configuration Tool enables the user to set some device properties across a list of selected devices. The Multiple Device Configuration Tool (Figure 196) is accessed by clicking BACnet Multiple Device Configuration from the Tools menu in the System Profile application.
Figure 196. Multiple Device Configuration Dialog Box.
Some notes about the operation of the Multiple Device Configuration tool are:
• The list cannot be empty and will remove duplicates automatically.
• The object selector will show cloaked devices so the user can uncloak them.
• At least one checkbox must be selected.
• The same limits are enforced as in the Advanced Settings dialog box (accessed through the BACnet Field Panel Definition dialog box).
• A summary of errors (if any) appears after the operation completes.
Insight BACnet Communications Tools
Siemens Industry, Inc. 395
Global Broadcast Who-Is
Clicking this menu item broadcasts a Who-Is message to all devices on the network. This tool is intended to be used with the discovery process. For information, see Device Discovery in Chapter 4–BACnet Communications.
Custom Send Who-Is Diagnostic Tool
The Who-Is Diagnostic Tool enables a user to send out a Who-Is message and view I-Am responses from devices on the network. The Who-Is message can be directed at a specific range of device numbers on a specific network or can be global (the default).
This tool can be used to locate devices that, for some reason, the device discovery process did not locate. If a response is gotten by this tool but the device is not on a ALN, then the BACnet Device Connection Settings (filtering) may be wrong or the device may be cloaked (see Glossary and Chapter 4–BACnet Communications).
The Who-Is Diagnostic Tool (Figure 197) is accessed by clicking BACnet Custom Send Who-Is from the Tools menu in the System Profile application.
Figure 197. Who-Is Diagnostic Tool Dialog Box.
I-Ams are added to the dialog box as they are received. The columns sort when the heading is clicked. A Total Count box lists the total number of I-Ams received.
Enable Device Discovery
Clicking the Enable Device Discovery menu item starts the discovery process for all devices on the network. See the Device Discovery section in Chapter 4–BACnet Communications.
Chapter 12–BACnet Tools
396 Siemens Industry, Inc.
BACnet Device Communication Control
BACnet Device Communication Control allows the user to control the communication of a BACnet device (field panel). The following device communication control is available to the user:
• Enable–Allows the device to respond to commands
• Disable–Stops a device from initiating or responding to commands. (The device will only respond to Device Communication Control and Reinitialization messages.)
• Disable Initiation Only–Stops a device from initiating commands but allows it to respond to commands. (It will respond to a Who-Is with one I-Am.)
This feature is useful when running tests on other devices on the network and a certain device or devices may interfere with those tests. For example, if certain devices are communicating a lot, the network may be too noisy to test the communication of other devices. This tool allows the user to quiet the noisy devices for the time the tests have to be run.
The Insight Help message gives another example. A user can disable the communications of a field panel on which a power fail test is to be run so that alarms are not sent to Alarm Status.
When the testing is completed, the field panel communication can be manually enabled or communications will automatically enable after the Disable duration time has elapsed. Setting the time to 0 disables the timer and keeps the field panel disabled until it is manually enabled.
CAUTION:
Use caution when disabling (entering a value of 0) the Disable duration timer. Device communication will not be able to resume until manually enabled.
There is no global enable command. Devices to be enabled must be specifically selected–either individually or more than one. If the selected devices require passwords, they MUST be enabled individually.
Unauthorized disabling of communication is restricted because the field panel password (if the panel was so configured) must be entered for this function to operate. For third-party BACnet devices, contact the manufacturer for the device password. For Siemens field panels, use the high account password.
Some third-party BACnet devices may not support Device Communication Control. For more information, see the manufacturer’s user documentation and/or Protocol Implementation and Conformance Statement (PICS).
Insight BACnet Communications Tools
Siemens Industry, Inc. 397
The BACnet Device Communication Control dialog box (Figure 198) is accessed from the Tools menu in the System Profile application.
Figure 198. BACnet Device Communication Control Dialog Box.
BACnet Communication Diagnostic
The BACnet Communication Diagnostic tool is used to configure the Insight BACnet communication wait time based on the analysis of APDU response times from field panels. An APDU (Application Protocol Data Unit) is a message that originates in an application program of one BACnet device and is sent to the application program of another BACnet device(s). For example, an APDU can be a point command and the response is the confirmation that the command was successful. When an APDU is sent, a response from the other BACnet device(s) is expected. The issue is how long to wait (timeout) for a response before trying again, and how many attempts or retries should be made before quitting.
This tool helps do the following:
• Give a suggestion for the best time to use the APDU timeout. The Suggested APDU Timeout is calculated by adding four seconds to the largest Response Time for a test ADPU issued by the Insight application.
• Help test for APDU turnaround time, and show how slow some devices are communicating on the BACnet network. This can be done by running multiple tests, each with a reduced BACnet APDU timeout value. When a panel does not respond (request timed out), the Current BACnet APDU Timeout value is less than the turnaround time. Adjusting the BACnet APDU Timeout allows zeroing in on the turnaround time.
• Assist in response tuning. If a panel’s turnaround time is inconsistent, a decision can be made for the best compromise timeout value.
Chapter 12–BACnet Tools
398 Siemens Industry, Inc.
The BACnet Communication Diagnostic tool allows you to test a single device or select all BACnet panels in the database. Operation is as follows:
• Press Begin. The device(s) are sent a request for the value of a read property.
• The Responses Received columns fill in accordingly:
− The number of seconds it takes for each device to respond is displayed in the Response Times [in Seconds] column. If it takes longer than the BACnet APDU timeout value entered at the top of the dialog box, The request timed out message displays.
− The APDU times that Insight is using for each device is displayed in the Current APDU Timeout column. The initial default value is 5 seconds.
− The APDU timeout recommended for each device is displayed in the Suggested APDU Timeout column.
− After Test Complete appears, clicking Begin again does not clear the columns. Instead, another set of response times, separated by commas, are written in the columns.
• If the Response Time and the Current APDU Timeout differ for a field panel, the suggested timeout can replace the current timeout by highlighting the field panel row and clicking the Set APDU Timeouts button. Multiple rows can be highlighted and set with one click of the set button, but if a row with errors is selected, it will be skipped and the APDU timeout will not be changed for that device.
APDU Timeout and Retries are BACstac settings to control how long a command has to complete before timing out and how many times to retry the command. The Insight software enforces a minimum of 1 retry and 5 second timeout. These values are set in the Advanced Settings of the BACnet Field Panel Definition. In the Insight software, this dialog box appears in System Profile.
CAUTION:
Some third-party devices may have default timeout values that are way too long. For example, anything over 30 seconds is too long and should not be required. If a panel’s turnaround time is slow and a long timeout is required, it will slow the operation of the Insight application. Long turnaround time issues for a panel must be resolved with the manufacturer.
The BACnet Communication Diagnostic dialog box (Figure 199) is accessed from the Tools menu in the System Profile application.
Insight BACnet Communications Tools
Siemens Industry, Inc. 399
Figure 199. BACnet Communication Diagnostic Dialog Box.
CAUTION:
The timeouts in this tool are for Insight software only. A field panel has its own, single timeout value and retry value that it uses when it requests data from other devices. These two values are read only and can be accessed through the Object Browser by viewing the ADPU_Timeout and Number_of_ADPU_Retries properties of the Device Object of the field panel. The APOGEE BACnet field panel firmware sets these values to three seconds for timeouts and three retries
Chapter 12–BACnet Tools
400 Siemens Industry, Inc.
Siemens Industry, Inc. 401
Chapter 13–BACnet Network Setup, Troubleshooting, and its Impact on IT
Chapter 13 presents information on Insight and firewall ports, BACnet network setup, troubleshooting, and the impact BACnet networks have on Information Technologies (IT). BACnet/IP networks typically impact IT in three areas:
• Port usage so that IT can configure firewalls.
• BBMD’s.
• Typical bandwidth usage for BACnet/IP networks.
This chapter will discuss each of these issues and provide recommendations for each.
Port Usage IT folks typically need to know BACnet/IP port usage so they can configure their firewalls. The User Datagram Protocol (UPD) is set to 47808 by default but is configurable. The Field Panel User’s Manual will tell you how to change the port from 47808 to another port.
The customer‘s IT department may not want to use a common default port for security reasons. However, will have to change every device on the network if 47808 is changed.
CAUTION:
The modification of network settings has an impact on the cyber security of the network. It is necessary to discuss these modifications and their implications with the customer/end user to ensure they understand the risks so that they are aware of the risks and can manage them.
Insight Firewall Ports
The following information has been reprinted from a Technical Support News (TSN) article written in June 2011 on Insight and Firewall Ports. This document can be found on the KnowlixFrontline knowledge management software package by searching for document # SMY-R22-YSW.
Chapter 13–BACnet Network Setup, Troubleshooting, and its Impact on IT
402 Siemens Industry, Inc.
“Some installations have a firewall to prevent unauthorized access to their Ethernet. These must be programmed to allow certain communications through and block out other, undesired access. For the APOGEE Automation System to function properly, the ports shown in Table 55 should be enabled. Note that these ports must be enabled only when there is a firewall between the APOGEE Insight computers and/or Field Panels. Also, note that not all of these ports need to be open for APOGEE to function properly. For example, there is no need for ports 67 and 68 to be open if DHCP is not used in your specific configuration. The same is true for ports 2050 and 2051 when running Insight APOGEE revision 3.9. Since 2050 and 2051 are only required for Insight revision 3.2 and below, there is no need to open these ports.”
Enable the ports listed in Table 55 when there is a firewall between the APOGEE Insight computers and/or Field Panels.
Table 55: Ports Required to be Enabled for APOGEE.
Port Protocol Used By Comments
7 TCP Ping/ICMP Used for Insight Server to Insight Client communication and verification.
23 TCP Telnet Used to communicate to AEMs, AEM 100s, EMBCs, and EMECs. Used for troubleshooting & maintenance purposes only. Not secure.
25 TCP SMTP Required for RENO.
53 TCP/DNS All APOGEE PC’s/Ethernet Field Panels
Many APOGEE configurations depend on DNS to provide naming resolution. You can also create a ‘Hosts’ file if you do not want to use DNS. However, note that whenever a new computer or field panel is added to the configuration, the ‘Hosts’ file must be updated with the new information. On the customer sites, consult with IT to determine if the IP address for DNS will be automatically assigned by DHCP or if it will be manually entered in the TCP/IP properties.
67/68 UDP BootP/DHCP Processes DHCP requests.
69 UDP TFTPD Used to flash firmware in AEMs and AEM 100s. Recommended to keep port open for future firmware upgrade.
80 TCP Internet Explorer Required for APOGEE GO®.
100 Internal Siemens R&D diagnostic’s logger output for remote troubleshooting.
135 TCP RPC RPC Endpoint Mapper.
137 UDP NETBIOS Datagram Service
Used by NetBIOS.
138 UDP NETBIOS Datagram Service
Used by NetBIOS.
Port Usage
Siemens Industry, Inc. 403
Port Protocol Used By Comments
139 TCP NETBIOS Session Service
Used by NetBIOS.
161 UDP SNMP Used by various APOGEE products using SNMP (Firmware 3.2, OPC/SNMP Agent).
162 UDP SNMP Used by various APOGEE products using SNMP (Firmware 3.2, OPC/SNMP Agent).
502 TCP/UDP Modbus TCP Used by Modbus Driver.
1200 through 5000
BCS/RPC event notification
This range can be limited through the Registry. To change this, see Note 1 below.
DCOM ports
TCP/UDP Insight DBCS Service when using Object Selector optimization, APOGEE GOTM
To determine ports to be allocated for DCOM, see Note 2 below. Note that this only needs to be done at the computer where te DBCS service is running.
2050 and 2051
UDP Rainbow Used by clients to find Sentinel in 3.2 and earlier.
3001 TCP/UDP Async Service Used to maintain connection between the Insight workstation and the field panel through AEM Serial Port 1.
3002 TCP/UDP Telnet Used to communicate to the field panel MMI port through an AEM200.
3389 TCP Terminal Services Terminal Services.
5033 TCP Ethernet Field Panels
Ethernet Field Panel communication occurs through 5033.
5093 UDP Rainbow Used by Sentinel LM in 3.3 and later.
5099 TCP/UDP Rainbow Used by Sentinel LM in 3.3 and later.
5441 TCP LSNIFF Sniffer for APOGEE Ethernet.
5442 TCP IPSNIFF, BACnet stack
IP sniffer, currently used by APOGEE BACnet stack. Async is dependent on the port being open.
6775 through 6778
TCP Objectivity/DB 5.0 and 5.1 Objectivity (Insight 3.1 and earlier).
6779 and 6780
TCP Objectivity 5.2, 6.x, 7.x, 8.x, and 9.x (Insight 3.2 and later).
47808 TCP/UDP BACnet Building Automation and Control Networks.
9999 TCP Telnet For the configuration port of an AEM200.
Chapter 13–BACnet Network Setup, Troubleshooting, and its Impact on IT
404 Siemens Industry, Inc.
Port Protocol Used By Comments
12001 12002 12003 12004 12005
TCP Dialogic Board Used by Dialogic Board. Must be open when using RENO with the TestTalk/Scansoft (Text-to-Speech) option.
47808 UDP BACnet For BACnet communication.
Desigo CC Firewall Ports
The list of required ports for Desigo CC is listed in the Desigo CCTM Installation Manual and is reproduced in Table 56. You should add the following ports to Windows 7 Firewall on the Server computer and any firewalls between the Desigo CC server and clients to allow access between the Server and all its clients.
Table 56: Desigo CC Firewall Port Settings on the Server Computer.
Firewall Settings
Port Type Notes
161 UDP (SNMP default) PVSS00snmp.exe
162 UDP (SNMP default) PVSS00snmp.exe
1977 TCP XNET driver port
4897 TCP PVSS00data.exe
4998 TCP PVSS00event.exe
4999 TCP TCP default port. PVSS00pmon.exe
7774 TCP HDB access used for sending trend data to the client for display
7775 ARCHIVE_DEFAULT_PORT
From GMS_PLATFORM_APPL\HDB\Examples\BCM\ Communication\GMSClient\GmsClientResources.hxx
47808 UDP UDP default port
You should add the ports as shown in Table 57 to Windows 7 Firewall on the Web Server computer to allow access between the Web Server and its clients.
Table 57: Additional Desigo CC Firewall Port Settings on the Web Server Computer.
Firewall Settings
Port Type Notes
80 TCP Standard HTTP port for all web clients, and the number assigned to the default web site when IIS is installed. If this port is already in use, you must specify a different port number.
443 TCP (SSL port) the web application.
BACnet Network Setup13F
Siemens Industry, Inc. 405
Firewall Settings
Port Type Notes
8000 TCP Windows Communication Foundation. The Desigo CC installation program defaults to this port.
BACnet Network Setup14
BACnet/IP ALN
BACnet/IP networks are a collection of one or more IP sub networks (IP domains) to which a single, unique BACnet network number is assigned. You can set up the software to function as one of the following:
• A Standard BACnet/IP or MS/TP device
• A BACnet Broadcast Management Device (BBMD)
• A Foreign Device
Use the following guidelines to determine the appropriate setup for your installation.
• UDP/IP on port 47808 (0xBAC0)
• MAC address is IP Address, Port Number
• Unicast, Broadcast
• BACnet/IP and BACnet Ethernet Share Wire
Standard BACnet/IP Networks
Set up a workstation to function as a Standard BACnet/IP device if the BACnet/IP network does not span IP routers. A Standard BACnet/IP network consists of BACnet devices on a single IP subnet.
14 The information in this section is taken from a draft of the Network Setup and Troubleshooting Manual. At the time of this writing,
this manual is not yet published or posted anywhere on the Siemens Intranet.
Chapter 13–BACnet Network Setup, Troubleshooting, and its Impact on IT
406 Siemens Industry, Inc.
BBMDs
Many IP routers prevent broadcast messages from being transmitted across a Wide Area Network (WAN). The BACnet protocol uses broadcast messages called Who-Is and I-Am to interrogate the network and determine what other BACnet devices exist on the BACnet Internetwork. For these broadcast messages to be transmitted across IP routers that block such messages, one device on each IP subnet must be set up as a BBMD.
Each BBMD shall possess a table called a Broadcast Distribution Table (BDT) which shall be the same in every BBMD in a given BACnet/IP network. If the BBMD has also been designated to register foreign devices as described below, it shall also possess a Foreign Device Table (FDT).
Set up only one BBMD for each IP subnet, and set up the Broadcast Distribution Table with the IP addresses of all other BBMDs that you want the workstation to work with. The Broadcast Distribution Tables must match the list of BACnet devices. If this is already an operational BACnet network, BBMDs may have been set up by the Network Administrator/Coordinator. Always consult with your Network Administrator/Coordinator when setting up BBMDs. There must be only one BBMD per IP subnet. This BBMD may be a workstation, Siemens field panel or a third-party panel.
• BBMDs can only be configured on BACnet/IP networks.
• Each workstation that acts as a BBMD for a subnet requires a fixed IP address.
• All Broadcast Distribution Tables on all BBMDs on a particular BACnet/IP network must be identical.
There are two ways that a BBMD may distribute broadcast messages to remote IP subnets.
BACnet Network Setup13F
Siemens Industry, Inc. 407
1. Sending directed broadcasts to an IP subnet (also called "one-hop" distribution). This involves sending the message using a BACnet/IP address in which the network portion of the address contains the subnet of the destination IP subnet and the host portion of the address contains all 1's. While this method of distribution is efficient, it requires that the IP router serving the destination subnet be configured to support the passage of such directed broadcasts.
2. Sending directed unicasts to another BBMD (also called "two-hop" distribution). It transmits the message using the BACnet/IP broadcast address. Since the use of one-hop distribution requires an IP router configured to pass directed broadcasts and the two-hop method is always available, two-hop distribution is strongly recommended.
Chapter 13–BACnet Network Setup, Troubleshooting, and its Impact on IT
408 Siemens Industry, Inc.
Figure notes:
1. A field panel in IP Subnet 1 (10.0.0.x) initiates a broadcast message (such as WHO-IS) that is received by the other BACnet device and the BBMD on the same subnet.
2. The BBMD on IP Subnet 1 see the broadcast and sends a directed unicast message through the IP routers to the BBMD on IP Subnet 2 (20.0.0.x) and IP Subnet 3 (30.0.0.x)
3. The BBMDs of IP Subnet 2 and 3 then re-broadcast the message on its respective network.
If a new BBMD joins the network, the Insight workstation must be rebooted if it’s defined as BBMD.
Figure 200: Illustration of a Two-Hop BBMD Network.
BACnet Network Setup13F
Siemens Industry, Inc. 409
Foreign Device
BACnet devices can be configured as a foreign device if you do not allow the Siemens field panel to be a BBMD on their network or if a third-party device is on a different subnet and does not support the BBMD function but can be set up as a foreign device.
• May or may not support the BBMD service.
• Every foreign device must be subscribed to a single BBMD on another subnet.
• Communicate broadcasted message ONLY with the BBMD to which they are individually subscribed.
• Do not re-broadcast message received from their subscribed BBMD to their local network.
Setting or Modifying the Field Panel IP Configuration
The field panel coldstarts during this procedure.
HMI S, H, E, S, M (System, Hardware, Ethernet, ipSettings, Modify)
Prompt/Field Option/Entry Description
Node name Alpha-numeric field Object name of the panel, must be unique on the entire system.
Site name Alpha-numeric field BACnet panels and Insight software on same IP subnet should have the same site name. The site name affects which discovery and replication times are used.
BLN name Alpha-numeric field This must be identical to the System Name of the BACnet ALN in System Profile.
DNS suffix ENTER = continue without entering data BACnet field panels do not use naming resolution.
DHCP Y DHCP is enabled DHCP server is to assign the field panels IP addresses.
N DHCP is disabled If using fixed IP addresses.
Chapter 13–BACnet Network Setup, Troubleshooting, and its Impact on IT
410 Siemens Industry, Inc.
Prompt/Field Option/Entry Description
IP address Numeric field If DHCP = N, you are prompted for an IP setting. Enter the IP setting. If DHCP = Y, you are not prompted for the IP setting.
Netmask Numeric field
Gateway address IP address for the assigned gateway If there is no IP gateway, enter 0.0.0.0.
DNS 1 Enter the address of the DNS server.
This can be obtained from the site’s IT department. If you do not need to specify DNS addresses, enter 0.0.0.0 for each of these.
DNS 2
DNS 3
DNS 4
Telnet Enabled Y Telnet is enabled To allow remote HMI sessions via Telnet and to enable FTP
N Telnet is disabled Remote HMI and FTP are blocked.
Configure BACnet Y BACnet configuration options are displayed.
N Exit configuration and save or discard changes.
Configure BACnet device Y Configure BACnet Device.
Device Instance Number Numeric field. Valid values are 0 through 4,194, 302, must be unique on the entire BACnet site. Recommended values: 7000 to 7999 for Siemens panels.
Device Location Alpha-numeric field Specify a descriptive location so the customer or other Siemens employee can locate the device.
Device Description ENTER = accept existing value Enter a device description.
Device Reserved Instance Base ENTER = accept the default 10,000 Enter the instance number where the field panel starts creating BACnet points for FLN devices; this must be at least 10000.
BACnet Network Setup13F
Siemens Industry, Inc. 411
Prompt/Field Option/Entry Description
COV Resubscribe Period (min) ENTER = accepts default, 30 Enter a number that identifies how often the field panel and the system will re-register for COVs.
COV Poll Rate (sec) ENTER = accepts default, 60 Enter a number, in seconds (10 to 3600) that identifies how often the field panel and the system will poll devices that do not support the Subscribe COV BACnet service.
N ENTER = default value (10000)
Enable BACnet IP ALN Y Configure the IP ALN
BACnet IP Network Number Specify a network, valid values are 1 through 65534. This network must be unique for the entire BACnet site. No other BACnet MS/TP ALN or BACnet MS/TP FLN or third-party network number may be the same.
UDP Port Accept the default BACnet UDP port, 47808. Other port may be used if required.
N No IP ALN.
Act as a Foreign Device Y A foreign device is A BACnet device (workstation or field panel) that has an IP connection but does not have a BBMD or multicast router on its subnet to allow it access to BACnet broadcast messages. A foreign device enables itself to send and receive both directed and broadcast messages.
Foreign devices are only used when a BACnet device is joining a network that spans multiple IP subnets and it is only going to be on that network for a short time.
N If the BACnet network does not span multiple Networks, enter N.
Enable MS/TP ALN Y If MS/TP ALN is used, enter Y and configure the next 3 parameters.
MS/TP ALN Baud Rate Enter the desired baud rate. 38400 is recommended.
MS/TP ALN Network Number Specify a network. Valid values are 1 through 65534. This network must be unique for the entire BACnet site. No other BACnet/IP
Chapter 13–BACnet Network Setup, Troubleshooting, and its Impact on IT
412 Siemens Industry, Inc.
Prompt/Field Option/Entry Description ALN, BACnet MS/TP ALN or BACnet MS/TP FLN or third-party network number may be the same.
MS/TP ALN Node Address Enter a MAC address. Valid values are 0 through 127. Address 0 is recommended .
This address with be the MAC address of the BACnet/IP to BACnet MS/TP ALN router. No other device on the BACnet MS/TP ALN may have the same MAC address. Other MS/TP FLNs or MS/TP ALNs may use this address.
N Enter N unless MS/TP ALN is being used.
P1, MS/TP P Select P for p1.
FLN1 Baud Rate A typical baud rate is 4800 for TECs and VFDs. If you are using P1 BIM, PXC on P1, PXMs, you can specify another baud rate.
On a PXC Modular, you will be prompted for the baud rates of all three FLNs.
FLN2 Baud Rate
FLN3 Baud Rate
Wireless Enabled (Y/N) If the FLN will be Wireless, specify Y. Otherwise, specify No.
M Select M for MS/TP FLN.
Enable MS/TP FLN (Y/N) Select Y to enable the MS/TP FLN.
MS/TP FLN Baud Rate Enter the desired baud rate. 38.4k is recommended
MS/TP FLN Network Number Specify a network. Valid values are 1 through 65534. This network must be unique for the entire BACnet site.
No other BACnet/IP ALN, BACnet MS/TP ALN or BACnet MS/TP FLN or third-party network number may be the same.
MS/TP FLN Node Address Enter a BACnet Media Access Control (MAC) address. Valid values are 0 through 127. Address 0 is recommended. This address with be the MAC address of the BACnet/IP to BACnet MS/TP FLN router. No other device on the BACnet MS/TP FLN may have the same MAC address. Other MS/TP FLNs or MS/TP ALNs may
BACnet Network Setup13F
Siemens Industry, Inc. 413
Prompt/Field Option/Entry Description use this address.
MS/TP Keep Alive Poll Rate Enter desired time between live node scans (10 to 300 seconds) if different than default setting.
Accept the default of 60.
MS/TP FLN Discovery Poll Rate Enter the desired time between dead node scans (10 to 300 seconds) if different than default setting. Accept the default of 60.
OK to coldstart (Y/N) Y Coldstart the field panel and save the configuration.
N Do not coldstart, discard any changes.
LocalNet Config Utility
Local Net Config must be set up to support the BACnet installation at the site. Specifically:
• BACnet networks must have the “Configure for BACnet Client” checkbox selected as shown in Figure 201 below..
• The “Configure for BACnet Server” checkbox is only used if you are exporting P1/P2 points as BACnet points to 3rd-party devices.
Technicians must be careful with this setting on their laptops.
• Selecting the BACnet Client option puts BACstac service dependencies in place.
• These dependencies can prevent ASYNC, Loader, and other services from starting if the laptop is used at a non-BACnet site.
• Unchecking the option when leaving the BACnet site will prevent any conflicts.
Chapter 13–BACnet Network Setup, Troubleshooting, and its Impact on IT
414 Siemens Industry, Inc.
Figure 201: LocalNet Configuration Setting for BACnet Clients.
BACnet MS/TP ALN
Firmware Revision 3.1 or later supports BACnet MS/TP ALN. The BACnet MS/TP ALN configuration is supported exclusively through the PXC Modular and select PXC Compact hardware (see PXC Modular Configuration & Sizing Guidelines (145-045) and PXC Compact Configuration & Sizing Guidelines (145-171)). The PXC Modular and PXC Compact 36 are the only APOGEE field panel that has simultaneous support for BACnet/IP ALN and BACnet MS/TP ALN. Therefore, they act as a router between BACnet/IP and BACnet MS/TP devices, objects, and properties, as specified by the BACnet standard.
The BACnet MS/TP ALN has the following performance considerations:
• In general, faster baud rates will increase performance on the network, so that 76.8Kbps will perform faster than 19.2Kbps, for example. However faster baud rates do increase sensitivity to outside interference on RS-485 wiring. Every device on the network must support and be configured for the same baud rate.
• Since Siemens devices that reside on a BACnet MS/TP ALN are treated as field panels to be backed up and monitored by the Insight workstation, network traffic between these devices and the Insight workstation is heavy. This limits the number of devices that may productively reside on a single BACnet MS/TP ALN network to approximately 10 devices, depending on point counts and network activity. Network performance may drop significantly if more than 10 Siemens field panels are added to the MS/TP ALN.
• Additional BACnet MS/TP ALN networks, with different ALN Name, may be added without compromising network performance through an additional PXC Modular/PXC Compact 36.
BACnet Network Setup13F
Siemens Industry, Inc. 415
• Third-party BACnet MS/TP devices may be added to a BACnet MS/TP ALN without the consequence of excess traffic.
• Each additional device on a BACnet MS/TP network that is set up as a master (ALN devices must be MS/TP masters) creates another device to pass the token, which takes time and decreases overall response times. Consider every additional node on the MS/TP network as adding 1 second to the token pass response time. Token pass times may exceed 1 second per node depending on the support of COV and the number of points monitored.
Rules for BACnet MS/TP ALN’s • Only PXC Modular with Firmware Revision 3.1 and later and PXC Compact 36
BACnet field panel support the BACnet/IP ALN to BACnet MS/TP ALN router functions.
• Integration drivers are not supported as BACnet ALN routers.
• Only one BACnet/IP to BACnet MS/TP router is allowed per ALN.
• All BACnet MS/TP ALN devices on an ALN must be on the same physical MS/TP segment.
• A maximum of 10 Siemens field panels, including the Router, can be wired on a single BACnet MS/TP ALN.
For example, you have two PXC Modular and two PXC Compact 36 field panels on a BACnet IP network. Each of those supervisory controllers has nine PXC Compact 16/24 connected to the MS/TP ALN port . In this case, you would need to define four separate ALNs in System Profile.
Adding a BACnet Field Panel as a MS/TP ALN Node
Configuring BACnet MS/TP Network Type HMI S, H, F, C, E, M (System, Hardware, Fieldpanels, Config, nEttype, Modify)
Prompt/Field Option/Entry Description
Alnnode, Flnnode A Type A for Alnnode and then press Enter.
F Type F for Flnnode and then press Enter
Ok to coldstart (Y/N) Y Type Y to coldstart the device and save the configuration changes.
N Type N to cancel, all configuration changes will be lost.
Chapter 13–BACnet Network Setup, Troubleshooting, and its Impact on IT
416 Siemens Industry, Inc.
Modifying BACnet Device Settings
CAUTION:
If the Device Instance Number or Device Reserved Instance Base are changed, the field panel coldstarts at the end of this procedure.
To accept the existing value and advance to the next entry field at any step of BACnet configuration, press ENTER.
To modify BACnet device settings, type the following letters in sequence and proceed with the steps:
HMI S, H, F, C, V, M (System, Hardware, Fieldpanels, Config, deVice, Modify)
Steps
Prompt/Field Option/Entry Description
Device Instance Number enter the device instance number
(0 – 4,194,302)
Recommended values are between 7000 and 7999; must be unique throughout the BACnet network.
Device Location enter the device location
Device Description enter the device description
Device Reserved Instance Base enter the starting reserved instance number
For more information on this parameter, see Device Reserved Instance Base in this section
COV Resubscribe Period (min) enter the COV resubscribe period in minutes
COV Poll Rate (sec) enter the COV poll rate in seconds
OK to coldstart (Y/N) This prompt only displays if you change the Instance Number or Device Reserved Instance Base.
Y Coldstart the device and save your configuration changes
N Cancel the configuration
BACnet Network Setup13F
Siemens Industry, Inc. 417
Example >Point, Application, Time, Message, Cancel, System, passWord, Bye? s
>Diagnostics, Users, dSt, Bacnet, Error_msgs, Hardware, Text, Quit? h
>Fieldpanels, Ethernet, nodeNametable, Disks, Reportprinter, Licensemanager, Quit? f
>Log, Display, Add, dElete, Modify, Config, Quit? c
>Hmi, Aln, deVice, db_fiLe, Fln, Names, Defaultlanguage, Quit? v
>Display, Modify, Quit? m
>Device Instance Number : 13933--
>Device Location : BIERMAN SUB BASEMENT---------
>Device Description : ABSORPTION CHILLER-----------
>Device Reserved Instance Base : 10000--
>COV Resubscribe Period (min) : 30--
>COV Poll Rate (sec) : 60--
Command successful
>Display, Modify, Quit? -
Modifying MS/TP ALN Settings
The field panel coldstarts during this procedure.
To modify MS/TP ALN settings, complete the following steps:
HMI S, H, F, C, A, M, M (System, Hardware, Field Panel, Config, Aln, MS/TP, Modify)
If the MS/TP ALN is already enabled, and the BACnet/IP ALN port is either disabled or not present on this device, the following prompt is not displayed. Under these conditions, continue this procedure with the following step (MS/TP ALN Baud Rate prompt).
Chapter 13–BACnet Network Setup, Troubleshooting, and its Impact on IT
418 Siemens Industry, Inc.
Prompt/Field Option/Entry Description
Enable MS/TP ALN (Y/N) Y To enable the MS/TP ALN port
N To disable the MS/TP ALN port
MS/TP ALN Baud Rate Enter the Baud rate for this port
MS/TP ALN Network Number Enter the network number for this port, or ENTER to accept the current value, if other than 65535
The network number must be changed from the system default of 65535
MS/TP ALN Node Address Enter the node address for this port
If you made any changes from existing values during this procedure, OK to coldstart (Y/N) is displayed. Do one of the following:
Y To coldstart the device and save your configuration changes
N To cancel the configuration
Example >MSTP ALN Network Number : 55---
>MSTP ALN Node Address : 127
>MSTP ALN Baud Rate : 9600----
>OK to coldstart (Y/N) : y
BACnet MS/TP FLN
Firmware Revision 3.1 or later supports BACnet MS/TP FLN configuration (not including the BACnet MS/TP Integration Driver discussed above). The BACnet MS/TP FLN configuration is supported through the PXC Modular with the FLN expansion module and PXC Compact with FLN port and FLN license. With Firmware Revision 3.1 or later, the FLN may be configured in the field as either a BACnet MS/TP FLN or P1 FLN. When configured for BACnet MS/TP FLN, physical FLN 1 port is used for communication and all other FLN ports are deactivated.
The BACnet MS/TP FLN has the following performance considerations:
• In general, faster baud rates will increase performance on the BACnet MS/TP network, so that 76.8Kbps will perform faster than 19.2Kbps, for example. However faster baud rates do increase sensitivity to RS-485 wiring guidelines. Also a number of microprocessor UARTS of MS/TP device cannot accurately produce 76800 baud signals. Devices using these microprocessors might list 76800 as supported but you may have network issue. 38.4KKbps is strongly recommended for MS/TP network communication.
• BACnet MS/TP devices resident on a BACnet MS/TP FLN are treated as FLN devices with point teams automatically created in the field panel. Point teams
BACnet Network Setup13F
Siemens Industry, Inc. 419
created are intended to optimize communication with application specific devices, such as Siemens BACnet TECs.
• Siemens BACnet TECs are supported by the field panel and Insight workstation with initial values support, and drag and drop reports.
• Each additional device on a BACnet MS/TP network that is set up as a master creates another device to pass the token, which takes time and decreases overall network response times. Consider every additional node on the MS/TP network as adding 1 second to the token pass response time. Token pass times may exceed 1 second per node depending on the support of COV and the number of points monitored. Loading a FLN with the maximum of 96 devices, response times due to token pass may be approximately 90 seconds.
• Each additional device on a BACnet MS/TP network that is set-up as a slave creates another device to poll, which takes time and decreases overall network response times. Consider every additional node on the MS/TP network as adding 1 second to the poll time which impacts overall response time. Response times may exceed 1 second per node depending on the number of points monitored. Loading a FLN with the maximum of 96 devices, response times due to polling may be approximately 90 seconds. Generally, with Siemens-only devices and low monitoring requirements, all devices configured as slaves on the MS/TP network perform faster than all devices configured as masters.
• In general, expect that BACnet MS/TP FLNs will perform slower than P1 FLNs due to the following: increased communication requirements for BACnet MS/TP compared to P1, lack of COV support in many BACnet MS/TP devices (including BACnet TECs), token passing when MS/TP devices configured as masters require additional communication time, and high volume of devices on single physical network which adds to communication time. So despite the significant increased speed of the BACnet MS/TP baud rate over the P1 baud rate, the actual communication response is slower due to the factors cited above.
• Based on field experience with MS/TP devices connected to a BACnet router, data transfer speed is decreased as the number of MS/TP devices is increased. When the number of devices exceeds 50, the data transfer speed becomes unacceptably slow for most customers. The system may experience slow updates of points (COVs, Alarms, etc.), and/or frequent device failures and return from failures. Therefore, it is recommended not to connect more than 50 BACnet MS/TP devices on a single BACnet network.
Chapter 13–BACnet Network Setup, Troubleshooting, and its Impact on IT
420 Siemens Industry, Inc.
MS/TP FLN versus MS/TP ALN
Benefits • You can more than 10 Siemens field panels reside on a MS/TP FLN whereas you
are limited to only10 Siemens field panels on a MS/TP ALN.
• You want to replace a third-party controller that is on the FLN with a Siemens BACnet field panel and use the same wiring.
• With a MS/TP driver you can add a Siemens BACnet field panel on that FLN.
Disadvantages • You cannot edit the field panel’s database from the Insight workstation.
• The field panel cannot be restored from the workstation if it coldstarts. However, it can restore its own database using the flash memory Auto Restore feature.
• If the System Name for points in the child field panel is longer than 12 characters, then the parent panel will use the ObjectName_InstanceNumber as the name.
Adding a BACnet MS/TP PXC Compact 16/24 or UEC to a MS/TP FLN Network
BACnet MS/TP PXC-16/24 controller is configured as an ALN node out of factory, opposed to UEC is configured as a FLN node out of factory.
Configuring BACnet MS/TP Network Type HMI S, H, F, C, E, M (System, Hardware, Fieldpanels, Config, nEttype, Modify)
Prompt/Field Option/Entry Description
Alnnode, Flnnode A Type A for Alnnode and then press Enter.
F Type F for Flnnode and then press Enter
Ok to coldstart (Y/N) Y Type Y to coldstart the device and save the configuration changes.
N Type N to cancel, all configuration changes will be lost.
BACnet Network Setup13F
Siemens Industry, Inc. 421
Configuring a Field Panel as a MS/TP Device
Although the UEC has a functional Ethernet port, it does not support BACnet IP ALN. The IP connection can be used for Telnet, FTP, etc. but needs to be configured only if these options are used. (See Steps 3 through 6.)
HMI S, H, E, S, M (System, Hardware, Ethernet, ipSettings, Modify)
Prompt/Field Option/Entry Description
Node name Alpha-numeric field Object name of the panel, must be unique on the entire system.
Site name Alpha-numeric field BACnet panels and Insight software on same IP subnet should have the same site name. The site name affects which discovery and replication times are used.
BLN name Alpha-numeric field This must be identical to the System Name of the BACnet ALN in System Profile.
DNS suffix ENTER = continue without entering data BACnet field panels do not use naming resolution.
DHCP Y DHCP is enabled DHCP server is to assign the field panels IP addresses.
N DHCP is disabled If using fixed IP addresses.
IP address Numeric field If DHCP = N, you are prompted for an IP setting. Enter the IP setting. If DHCP = Y, you are not prompted for the IP setting.
Telnet Enabled Y Telnet is enabled To allow remote HMI sessions via Telnet and to enable FTP
N Telnet is disabled Remote HMI and FTP are blocked.
Configure BACnet Y BACnet configuration options are displayed.
Chapter 13–BACnet Network Setup, Troubleshooting, and its Impact on IT
422 Siemens Industry, Inc.
Prompt/Field Option/Entry Description
N Exit configuration and save or discard changes.
Configure BACnet device Y Configure BACnet Device.
Device Instance Number Numeric field. Valid values are 0 through 4,194, 302, must be unique on the entire BACnet site. Recommended values: 7000 to 7999 for Siemens panels.
Device Location Alpha-numeric field Specify a descriptive location so the customer or other Siemens employee can locate the device.
Device Description ENTER = accept existing value Enter a device description.
Device Reserved Instance Base ENTER = accept the default 10,000 Enter the instance number where the field panel starts creating BACnet points for FLN devices; this must be at least 10000.
COV Resubscribe Period (min) ENTER = accepts default, 30 Enter a number that identifies how often the field panel and the system will re-register for COVs.
COV Poll Rate (sec) ENTER = accepts default, 60 Enter a number, in seconds (10 to 3600) that identifies how often the field panel and the system will poll devices that do not support the Subscribe COV BACnet service.
N ENTER = default value (10000)
Enable MS/TP ALN Y If MS/TP ALN is used, enter Y and configure the next 3 parameters.
MS/TP ALN Baud Rate Enter the desired baud rate. 38400 is recommended.
MS/TP ALN Network Number Specify a network. Valid values are 1 through 65534. This network must be unique for the entire BACnet site. No other BACnet/IP ALN, BACnet MS/TP ALN or BACnet MS/TP FLN or third-party network number may be the same.
MS/TP ALN Node Address Enter a MAC address. Valid values are 0 through 127. Address 0 is recommended.
This address with be the MAC address
BACnet Network Setup13F
Siemens Industry, Inc. 423
Prompt/Field Option/Entry Description of the BACnet/IP to BACnet MS/TP ALN router. No other device on the BACnet MS/TP ALN may have the same MAC address. Other MS/TP FLNs or MS/TP ALNs may use this address.
N Enter N unless MS/TP ALN is being used.
OK to coldstart (Y/N) Y Coldstart the field panel and save the configuration.
N Do not coldstart, discard any changes.
It is strongly recommended that you enable the Auto-Save and Auto-Restore features since the field panel is now configured as a MS/TP FLN device and can no longer perform a database transfer with the Insight workstation.
Adding a BACnet TEC or a Third-party MS/TP Device to a BACnet Field Panel
The following procedure explains how to add a BACnet MS/TP device on the FLN of a BACnet/IP field panel with Firmware Revision 3.1 and later. It can be performed from the Insight workstation or from the field panel’s HMI prompt.
Gathering Information from the BACnet MS/TP Device
The following information is required from each BACnet MS/TP device:
• MAC Address – For BACnet TECs (BTECs), the MAC address is also the value of CTLR ADDRESS (Point 1).
• MS/TP Device Instance Number – See the ID field in the BACnet Properties dialog box in WCIS.
• Baud Rate – See the Baud Rate drop-down list in the BACnet Properties dialog box in WCIS.
• MS/TP Node Type (slave or master) – See the MS/TP Slave check box in the BACnet Properties dialog box in WCIS.
Figure Figure 202 is an example of the BTEC information displayed in the WCIS BACnet Properties dialog box:
• MAC Address = 50 (from the value of CTLR ADDRESS (Point 1))
• MS/TP Device Instance Number = 250205 (from the ID field)
• Baud Rate = 38400 bps
• MS/TP Node Type = Slave (MS/TP Slave option is checked)
Chapter 13–BACnet Network Setup, Troubleshooting, and its Impact on IT
424 Siemens Industry, Inc.
Figure 202: BACnet Properties Dialog Box.
Configuring the FLN for MS/TP
From the Insight Workstation
1. In System Profile, double-click BACnet/IP field panel.
2. Go to the FLN Configuration section. From the Type menu, select MS/TP.
3. Click the FLN Settings button.
The MS/TP FLN Settings dialog box displays.
4. Check Enable MS/TP FLN Port.
5. In the Baud Rate drop-down list, select the rate that matches the baud rate of the BACnet MS/TP device. For more information, see the section Gathering Information from the BACnet MS/TP Device.
BACnet Network Setup13F
Siemens Industry, Inc. 425
6. In the Network Number field specify a unique number.
Valid values are 0 through 65534. This number should not be the same as the BACnet/IP Network Number or any other network number on the site, including third-party network numbers. The Virtual BACnet network in the Cimetrics properties has a default network number of 2. The network number cannot match any network number used for the MS/TP FLN.
7. Leave the rest of the fields as default in the MS/TP FLN Settings dialog box and click OK.
8. When the BACnet Field Panel Definition dialog box displays, click OK.
9. Click Yes when prompted with the following message: The changes made to the panel definition will cause the field panel to coldstart. Do you wish to proceed?
Figure 203: FLN Settings Dialog Box.
Chapter 13–BACnet Network Setup, Troubleshooting, and its Impact on IT
426 Siemens Industry, Inc.
From the Field Panel’s HMI Port Point, Application, Time, Message, Cancel, System, passWord, Bye? s Diagnostics, Users, dSt, Bacnet, Error_msgs, Hardware, Text, Quit? h Fieldpanels, Ethernet, nodeNametable, Disks, Reportprinter, Licensemanager, Quit? f Log, Display, Add, dElete, Modify, Config, Quit? c Hmi, Aln, deVice, db_fiLe, Fln, mBus, Names, Defaultlanguage, Quit? f fln1, fln2, fln3, Wireless, MS/TP, flnType, Quit? m Enable MS/TP FLN (Y/N) : Y
Enter baud rate : 38400--- NOTE: Must be identical to the MS/TP device baud rate. See the Baud Rate drop-down list in the BACnet Properties dialog box in WCIS.
Network Number : 21--- NOTE: Must be a unique number. Valid values are 1 through 65534. This number cannot be the same as the BACnet/IP Network Number or any other Network Number on the site, including third-party network numbers.
MS/TP Device Mac Address : 127
NOTE: Field panel's MAC address. Leave it as 127, unless another device on the network has a MAC address of 127.
Keep Alive Poll Rate : 60--- NOTE: Leave it as the default.
Discovery Poll Rate : 60--- NOTE: Leave it as the default.
Command successful
BACnet Network Setup13F
Siemens Industry, Inc. 427
Adding the MS/TP Device
From the Insight Workstation:
1. In System Profile, drag and drop a BACnet TEC icon to FLN 1 of the BACnet/IP field panel.
2. Enter the parameters for the following:
- System Name and Name: Enter a descriptive name without any special characters. It does not have to match the Name defined in Device Properties in WCIS.
- Descriptor: (Optional) Enter a description without any special characters.
- Graphic Name: (Optional)
- Application: Select 65535 for a BTEC; otherwise, enter a number from 10000 through 11999.
- Device Instance: MS/TP Device Instance Number. For BTECs this is the value from the ID field in WCIS.
- Network Number: Enter the MS/TP Device Network Number. This number must be identical to the Network Number defined in the MS/TP FLN Settings dialog box in the procedure Configuring the FLN for MS/TP. Valid values are 1 through 65534. This number must not be same as the BACnet/IP Network Number.
- BACnet MAC Address: Enter the value for the Controller Address point obtained from WCIS in the procedure Gathering Information from the BACnet MS/TP Device. Enter the value as a decimal value.
- MS/TP Node Type: Select the same MS/TP node type as you obtained from WCIS in the procedure Gathering Information from the BACnet MS/TP Device.
- Initial Value Priority: Select 16 – Available 16.
- Save Relinquish Defaults: Select this check box for a BTEC. Clear this check box for third-party devices.
- Password: Enter HIGH
Chapter 13–BACnet Network Setup, Troubleshooting, and its Impact on IT
428 Siemens Industry, Inc.
Figure 204: FLN Device Definition Dialog Box.
From the Field Panel’s HMI Port Point, Application, Time, Message, Cancel, System, passWord, Bye? a Ppcl, flNdevice, Quit? n MS/TP, Tec, Uc, Quit? m Log, Display, Edit, Initvalues, Quit? e Add, Modify, Copy, Delete, Look, Quit? a FieldValue --------------------------------------------------------------------------- MS/TP Device system name: ASB54A MS/TP Device name: ASB54A
MS/TP Device Instance Number: 70011 NOTE: This is the number from the ID field in the BACnet Properties dialog box in WCIS.
Application number: XXXXX NOTE: Leave this field blank for BACnet TECs (BTECs). For third-party devices, valid values are 10000 to 11999
Descriptor: NOTE: You can enter any type of descriptor.
Access group(s): <all>
Field panel name: 70011 NOTE: Device Instance Number of the field panel.
Master, Slave: Slave NOTE: Can be either Slave or Master.
MS/TP Device Network Number: 11 NOTE: Enter a unique number. Valid values are 1 through 65534. It cannot be the same as the BACnet/IP Network Number or any other Network Number on the site, including third-party network numbers.
BACnet Network Setup13F
Siemens Industry, Inc. 429
MS/TP Device Mac Address: 1 NOTE: For BTECs, the MAC address is also the value of CTLR ADDRESS (Point 1).
Initial Value Priority: 16 NOTE: For third-party devices, leave this field at 16.
Save Relinquish Defaults: YES NOTE: For BTECs, set this field to YES. For third-party devices, set this field to NO.
Device Init Password: HIGH
The field panel must be made ready for communications to occur.
Cimetrics MS/TP Router Set Up for Communication with BACnet TECs
The Cimetrics B6000 Router allows the BACnet MS/TP TEC and third-party MS/TP devices to communicate with an Insight BACnet Client by converting BACnet/IP to BACnet MS/TP. This following procedure covers the entire setup procedure for the Cimetrics B6000 Router, the BACnet TEC configuration, and the Insight® workstation configuration. The MS/TP Router specifically refers to the Cimetrics B6000 BACnet MS/TP router, whereas router refers to generic BACnet routers.
The following procedures are for configuring the MS/TP Router:
• Gathering Necessary Information
• Wiring and Network Electrical Considerations
• Setting the MS/TP Router Terminations
• Connecting to the MS/TP Router with a Computer for Configuring
• Configuring the MS/TP Router BACnet/IP Settings
• Configuring the MS/TP Router MS/TP Settings
• Confirming the MS/TP Router Settings
• Configuring the BACnet TECs
• Establishing Communication with the Insight workstation
The Configuring the BACnet TECs procedure may be performed before Setting the MS/TP Router Terminations through Configuring the MS/TP Router Settings (in the case that the BACnet TECs are available before the MS/TP Router).
Gathering Necessary Information
Physical Network (DNET) Setting Numbers, UDP Port Number, BTEC Object Names and Object IDs.
Before going to the job site, be sure to obtain the BACnet TEC startup document(s) for your application(s). Those documents are available at:
Chapter 13–BACnet Network Setup, Troubleshooting, and its Impact on IT
430 Siemens Industry, Inc.
• http://iknow.us.abatos.com/customsolutions/HVAC_main.asp
• Beacon: https://inet.sbt.siemens.com/customsolutions/HVAC_main.asp
• To configure the MS/TP Router, it is necessary to assign it two physical network numbers, one for each of the following:
• The BACnet/IP network
• The MS/TP network
Cimetrics refers to the physical network numbers as DNET numbers. These DNET numbers must be configured properly or communication cannot be established.
In addition, it is also necessary to know the UDP port number that is being used, since this must be configured at both the router and at the Insight BACnet workstation. This process assumes the Cimetrics router will be used in conjunction with an Insight workstation. If it is used with another third-party system, you must find the physical network number(s) the third-party system uses.
Physical Network (DNET) Setting Numbers and UDP Port Number
To determine which network numbers and which UDP port number to use, if there are no third-party BACnet vendors present, do the following at the Insight workstation: This procedure assumes you have already followed the Setting Up BACnet in the Insight Online Documentation under Getting Started.
1. Click Start, Settings, Control Panel, and then double-click Network Connections.
2. Right-click the connection that represents the Network Interface Card that is bound to the BACstac Protocol, and then click Properties.
3. Select Cimetrics BACstac(TM) Routing Edition v4.2 Protocol, and then click Properties.
4. Make a note of the following:
• Physical Network number for the BACnet/IP network to which you intend to connect the router. This is located in the Network Num column. This number will be used as the Router’s BACnet/IP DNET number.
• The UPD Port number. This number will be used in the BACnet/IP configuration of the B6000 Router. It is usually set to 47808.
• The network numbers of any other networks in the Cimetrics BACstac(TM) Routing Edition v4.2 Protocol. When you configure the MS/TP Router’s MS/TP settings, make sure neither the BACnet/IP DNET number nor the MS/TP DNET number is the same value as any of the physical network or virtual numbers defined for the Insight workstation.
BACnet Network Setup13F
Siemens Industry, Inc. 431
To determine which physical network numbers and which UDP port number to use, if the third-party BACnet vendors are present, then ask the following questions:
• Which physical network numbers are being used for the BACnet/IP network?
• Use this network number for both of the following:
• The Router’s BACnet/IP DNET number.
• The Insight BACnet workstation’s BACnet/IP network number.
• Which physical network and virtual numbers they are using for other networks?
Do not use these network numbers in the router’s configuration or for the Insight BACnet workstation’s Cimetrics Setting.
• Which UDP port they are using? The UPD port 47808 is the default, but sometimes, other ports may be used.
BTEC Object Names and Object IDs
Be sure to consult with the customer or third-party vendor to determine the best naming convention for the BTEC Object Names and Object IDs on the MS/TP network. The names are determined in the same way as standard APOGEE Automation System names. The Object IDs are usually in a range reserved for this type of device. If the job is small, the Object IDs can be in any range. However, if there are several BACnet devices on the network, an organizational spreadsheet should be used to keep an ID from being accidentally reused.
Wiring and Network Electrical Considerations • All BACnet TECs must be daisy chained. No T-Taps are allowed.
• The end of every segment must be terminated. The end of a segment is any FLN connector with only one set of wires connected to it. The following are different ways to terminate segment ends:
– The MS/TP Router is terminated by placing the termination jumpers (see Setting the Router Termination).
– The recommended wiring is our standard ALN/FLN wiring, 24 gauge, Cat 5, twisted, shielded pair, low capacitance (12.5 pF/ft.), available from Anixter. See the Field Purchasing Guide for more information.
– Terminate the last TEC with an ALN Trunk Terminator (Part Number 538-664).
Chapter 13–BACnet Network Setup, Troubleshooting, and its Impact on IT
432 Siemens Industry, Inc.
– Terminate all FLN connectors that connect to an HSTIE by setting the Trunk Termination Switch (inside the HSTIE enclosure) for that FLN connector to an End of Line (EOL). Do not add an ALN Trunk Terminator. If there are two sets of wires in one FLN connector, the Trunk Termination Switch should be set to Normal (NRML).
• HSTIEs are required if more than 31 of the older BACnet TECs are used. For BACnet TECs sold after November 2005, a maximum of 50 TECs can be placed on a single router without any HSTIE. Additional TECs can actually be used, but over 50 is not recommended because change of values (COVs) will update slowly.
To determine if the BACnet TECs are the type that allows more than 31 on a segment, locate the chip labeled U16 on the board, which is about 1-inch above terminations 7 and 8. If the TEC is the newer type, the marking MAX3085 is printed on the chip. The older types of TECs have a series of numbers printed on them, but not "MAX3085".
• The E terminal of the power connector for all BACnet TECs must be connected to earth ground. If the E terminal is not connected to earth ground, the BACnet TECs could potentially lock up and stop communicating.
• Connect the shield wire to every BACnet TEC and to the MS/TP Router.
Setting the Router Termination
Only perform this procedure if the router is at the end of a segment (which means, the router’s MS/TP connector has only one set of FLN wires connected to it).
1. Unplug all connections to the router, including power.
2. With a small Phillips screwdriver, remove the four screws on the sides of the router.
3. Remove the top cover.
4. Move the three jumpers near the green MS/TP connector on J5 from Spare to Terminated.
BACnet Network Setup13F
Siemens Industry, Inc. 433
Figure 205: Termination Jumper Placement inside the Cimetrics B6000 Router.
5. Place the cover back and tighten the four screws.
6. Reconnect the power supply. Leave the Ethernet and MS/TP connectors disconnected.
Connecting to the Router with a Computer for Configuring
1. Obtain an Ethernet Crossover cable or an Ethernet hub and two Ethernet patch cables.
Chapter 13–BACnet Network Setup, Troubleshooting, and its Impact on IT
434 Siemens Industry, Inc.
2. Configure your laptop computer or another computer to have a fixed IP address of 192.168.88.90 with a subnet mask of 255.255.255.0. To do so, perform the following steps (these steps assume you have Windows XP):
- Click Start, Settings, Control Panel, and then double-click Network Connections.
- Right-click on the Connection that represents your Network Interface Card, and then click Properties.
- Select Internet Protocol (TCP/IP), and then click the Properties button.
- Select Use the Following IP Address.
- Type the following:
IP address 192.168.88.90
Subnet Mask 255.255.255.0
- Click OK in the Internet Protocol (TCI/IP) Properties dialog box.
- Click OK in the Local Area Connection Properties dialog box.
- Close the Network Connections window.
3. Disable the ISA Firewall Client by right-clicking on the ISA Firewall Client icon in the system tray in the lower right corner of the screen and selecting Disable.
Figure 206: ISA Firewall Client Icon.
4. Open Internet Explorer. Type http:// 192.168.88.89 in the Address box and press ENTER.
5. The MS/TP Router prompts you for a User Name and Password. Type admin for both the username and password.
Configuring the Router MS/TP Settings
1. Click MS/TP Settings.
2. Configure the baud rate. The recommended baud rate is 38400 bps. A baud rate of 76800 bps does not work with HSTIEs.
BACnet Network Setup13F
Siemens Industry, Inc. 435
- Set the value of This Station (MAC), to a value from 1 through 127, that is not equal to any of the ADDRESS (1) subpoints of any BACnet TECs. The MS/TP Router is actually a node on the MS/TP network, similar to TECs. If the MAC address of the MS/TP Router were the same as one of the BACnet TECs, the network would not communicate properly and the BACnet TECs would fail.
- Set Max Info Frames to a value of 1.
- Set Max Master to 127. This sets the highest MAC address the MS/TP Router can poll. As a general rule, this should be at least the value of the highest TEC address on the network if it is not, the TECs cannot communicate.
- Set Reply Timeout to 255 mS.
- Set Usage Timeout to 20 mS.
- Set DNET to a unique value. This value must be different from the following:
The DNET parameter on the BACnet/IP settings.
The Insight workstation's Cimetrics Network numbers (physical and virtual).
The networks for any other router or Insight workstation.
- Click Save.
Confirming the Router Settings
1. Click Activate Configuration.
2. Click Confirm.
A message displays: “Confirmation saved. Now rebooting the device.”
3. Close Internet Explorer.
4. Disconnect the Ethernet cable that was used for configuring and connect the cable that will be used to connect the MS/TP Router to the Insight workstation.
5. From the Insight workstation, click Start, Run, type CMD and then press ENTER.
6. Verify that the Insight workstation has Ethernet connectivity to the MS/TP Router. Type PING [IP address of MS/TP Router] and then press ENTER.
7. If you need to verify settings from the Insight workstation, open Internet Explorer and type http://[IP address of MS/TP router]in the address box and then press ENTER.
Chapter 13–BACnet Network Setup, Troubleshooting, and its Impact on IT
436 Siemens Industry, Inc.
The MS/TP Router configuration Web page can still be contacted from a computer whose IP address is 192.168.88.90 by typing http://192.168.88.89 in the address box of Internet Explorer. This method works even if the MS/TP router has been configured with a different IP address. This is useful if the IP address of the MS/TP Router is unknown.
Configuring BACnet TECs Perform the following procedure at all BACnet TECs. 1. Connect to the BACnet TEC with WCIS 2.1.4 or later through the TECs HMI port.
- WCIS 2.1.4 is available on the Field Support Web site: http://iknow.us009.siemens.net/fieldsupport/WindowsCIS.asp
- From Beacon: https://inet.sbt.siemens.com/fieldsupport/WindowsCIS.asp
2. Set the communications baud rate to 1200 bps. 3. Click Device, and then Connect. 4. Set the MAC address of the BACnet TEC by overriding the point ADDRESS (1),
to the desired value.
Do not leave more than one BACnet TEC that has not been addressed connected to the network. The default address of 99 is a valid BACnet address. Therefore, if you leave more than one BACnet TEC connected with an address of 99, you will have duplicate addresses, and you will be unable to establish communication.
1. Set APPLICATION (2) to the desired application.
2. Follow the remaining procedures in the Startup Documents with the exception of Configuring BACnet Parameters section:
- http://iknow.us.abatos.com/customsolutions/HVAC_main.asp
- From Beacon: https://inet.sbt.siemens.com/customsolutions/HVAC_main.asp
3. Save TEC initial values using the backup feature in WCIS 2.1.4. Neither the MS/TP Router nor the BACnet MS/TP Driver has the ability to back up or restore initial values.
4. Click the Device drop-down menu. The WCIS software pauses and the mouse pointer may change to an hour glass.
5. Click on Device Properties. Again, there may be a pause.
6. Set Object Name to a unique name (12-character limit).
7. Set the Object ID to a unique value from 0 to 4194303.
Object ID is not the MAC address; it is a higher-level address within the BACnet MS/TP protocol (device instance number).
BACnet Network Setup13F
Siemens Industry, Inc. 437
1. Type a Description for the controller (60-character limit). (Optional) 2. Type a Location describing the physical location of controller (60-character limit).
(Optional) 3. Set CIS/MMI Command Property to a value 8. 4. If the TEC is connected to an MS/TP Router and metric units are desired, select
the Metric Units check box. 5. Set the baud rate to match Baud Rate of the MS/TP Router. The options for baud
rate are; 9600, 19200, 38400 or 76800. The default is 19200.
HSTIEs cannot be configured for 76800 bps. It is recommended to configure the BACnet TECs to a baud rate of 38400 bps.
1. Configure the controller for MS/TP Master or Slave. To determine which to use, consider the following:
- Use Master if you will be referencing several of the BACnet TEC points in PPCL. If you select Master, you can use the BACnet TEC point names in PPCL, such as [ObjectName]Room Temp.
- Use Slave if you are concerned with performance, specifically the rate at which the BACnet TECs update. To use the BACnet TEC point names, such as [ObjectName]Room Temp in PPCL, you must manually type the name in the BACnet address table from System Profile or the field panel HMI, or use a fully qualified BACnet object name, such as 70001_AI_4.
- If the customer requests Metric Units, select the Metric Units check box.
- Click the Write button.
- Initialize the TEC, or cycle power to it.
2. Follow the procedures in the BACnet TEC startup document(s) for your application. Those documents are available at. http://iknow.us.abatos.com/customsolutions/HVAC_main.asp.
Establishing Communication with an Insight Workstation
1. If the BACnet TECs are configured for MS/TP Slave, change the value of the registry key PingByReadPropertyFrequency to a value of 4. To do this:
- Click Start, Run, and type regedt32 and press ENTER.
- Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\LANDIS & GYR\Insight\CurrentVersion\BACnet\Client\.
- Double-click PingByReadPropertyFrequency, and change the value from 0 (default) to 4. Click OK.
- Exit Regedt32.
Chapter 13–BACnet Network Setup, Troubleshooting, and its Impact on IT
438 Siemens Industry, Inc.
2. Once all the BACnet TECs have been configured, connect the MS/TP connector to the MS/TP Router.
3. Open System Profile at the Insight workstation.
4. If there is not already one present, create a BACnet ALN.
5. Do one of the following:
- If the TECs are configured for MS/TP master, click Enable BACnet Discovery in System Profile, and then click Send Who Is.
- If the TECs are configured for MS/TP Slave or you want to specify the System Name of the TECs, manually add the BACnet TEC. To do this, drag-and-drop a field panel on the ALN for each TEC.
6. Set the Device Instance Number equal to the TEC device instance number (Object ID) in Configuring BACnet TEC, Step 11.
7. Assign a unique System Name and Name.
8. If you are not using BACnet Discovery, manually add a TEC. To do this, drag-and-drop a field panel on the ALN for each TEC.
- Set the Device Instance Number equal to the TEC device instance number (Object ID) in Configuring BACnet TEC, Step 11.
- Assign a unique System Name and Name.
9. Using Database Transfer, upload each BACnet TEC.
10. Run a Point Log report to verify that all of the BACnet TECs are communicating.
Troubleshooting the BACnet Network Using Wireshark
Overview
Wireshark is an open source network analyzer. This is a software application that can be used to capture, view, and save network traffic for the purpose of troubleshooting network communication problems including BACnet (BACnet/IP, BACnet Ethernet, and BACnet MS/TP).
Installation
Wireshark can be installed on most Microsoft operating systems running Windows XP, Windows Server 2003, Windows Vista, Windows 2008, Windows 7, and Windows 2008 R2.
You can download a copy of the latest Wireshark application from http://www.wireshark.org/.
BACnet Network Setup13F
Siemens Industry, Inc. 439
During the Wireshark installation, two components are installed:
• Wireshark – Application for configuring the capture filters, setting capture parameters, displaying frames, decoding frames, producing graphs, tables, and statistics.
• Winpcap – Drivers used to capture packets off the NDIS interface.
Setting Up Wireshark Capture Software Install Wireshark on a computer running BACnet software, for example an APOGEE Insight workstation.
1. Capture all IP network packets on an Insight workstation.
2. Capture all IP network packets on a specific field panel using an Ethernet Hub. Install Wireshark on laptop computer and connect to the Ethernet network using a true hub so that the laptop computer will get all packets received and delivered from the perspective of the field panel. See Figure Switched Media (with Hub).
Unlike switches, when routing data, hubs broadcast the data to all of their ports knowing that the correct recipient will receive it.
Chapter 13–BACnet Network Setup, Troubleshooting, and its Impact on IT
440 Siemens Industry, Inc.
True hub models that are known to work:
• Netgear DS104
• Netgear DS108
• Netgear GS108NA
• Netgear GS105?
Benefit - Cheap and easy to install.
Disadvantage - Reduces link to half duplex and is not practical on servers or switch uplink.
Capture all IP network packets on a specific field panel using a switch with port mirror.
Install Wireshark on laptop computer and connect to the Ethernet network using a switch with port mirroring capabilities. Using the switch management, you can select both the monitoring port and assign a specific port you wish to monitor. Actual procedures vary between switch models and you may need to use a terminal emulator, specialized SNMP client software or (more recently) a Web browser.
BACnet Network Setup13F
Siemens Industry, Inc. 441
Switch model that is known to work: Netgear GS108E
Benefit – Does not require link to be dropped and great for one-time link monitoring.
Disadvantage – Requires switch access and configuration.
Capture all MS/TP network packets using a Serial to RS-485 adaptor.
Install Wireshark on laptop computer and connect to the RS-485 network using a Serial to RS-485 adapter.
Starting Wireshark Click Start, Programs, Wireshark. The main window displays.
Chapter 13–BACnet Network Setup, Troubleshooting, and its Impact on IT
442 Siemens Industry, Inc.
The two main drop-down menus you will use are: • File. The File drop-down menu allows you to open, save, and export capture
files.
• Capture. The Capture drop-down menu allows you to start and stop a capture, as well as select a network interface where you want capture data to reside on.
Starting and Stopping Wireshark Capture for an IP Network
1. To start a capture, select Interfaces from the Capture drop-down menu.
The Capture Interfaces dialog box displays.
2. Select the network card you want to capture data from by using the radio buttons on the left side and then click the Start button.
3. The data packets will display in the main window.
BACnet Network Setup13F
Siemens Industry, Inc. 443
4. Select Stop from the Capture drop-down menu, to stop capture.
Starting and Stopping Wireshark Capture for MS/TP Network Using MS/TPCAP
1. From Command Prompt, type the following:
MS/TPCAP <COM> <BAUD> <WindowsPipe>
where <COM> syntax is COMx where x is port, for example COM2 or COM12.
where <BAUD> syntax number equal to baud (19200, 38400, etc) where <WindowsPipe> is \\.\pipe\wireshark
2. MS/TPCAP creates capture files in the following format:
MS/TP_YYYYMMDDHHMMSS.cap (YearMonthDayHourMinuteSeconds)
There is a packet counter that increments every 100 packets. If counter stays at 0, check ComPort and Baud.
1. After running MS/TPCAP with a WindowsPipe, start Wireshark.
2. Select Options from Capture drop-down menu.
3. Type WindowPipe; use the MS/TPCAP command line, from the Interface section.
Chapter 13–BACnet Network Setup, Troubleshooting, and its Impact on IT
444 Siemens Industry, Inc.
4. Click the Start button. 5. The data packets will display in the main window. 6. Select Stop from the Capture drop-down menu to stop capture.
After stopping Wireshark capture, you must also stop MS/TPCAP by using CTRL-C in Command Prompt.
Saving Wireshark Capture
You can only save a capture that is not actively running.
1. To save the data packets, select Save-As from the File drop-down menu. The Wireshark Save file as dialog box displays.
BACnet Network Setup13F
Siemens Industry, Inc. 445
2. To save all the packets, select the All packets and Captured radio buttons in
the Packet Range section. 3. Navigate to the folder location where you want to save the captures, type in a
filename, and then click the Save button.
Display Filters
Display Filters are used to view only the packets that you want to see and hide the packets you don’t want to see. You do this by building a filter expression in the filter toolbar.
Chapter 13–BACnet Network Setup, Troubleshooting, and its Impact on IT
446 Siemens Industry, Inc.
To build a filter expression, you will use a combination of Comparison operators, Logical operators, common keywords, and values. The following tables are the most commonly used operators, keywords, and values used to build expressions.
Comparison Operators
Description Wireshark syntax English syntax
Equal == eq
Not equal != ne
Greater than > gt
Less than < lt
Greater than or equal to >= ge
Less than or equal to <= le
Logical Operators
Description Wireshark syntax English syntax
And && and
Or ‖ or
Not ! not
Common keywords – MAC address
Description Wireshark syntax
IP Address ip.addr
Source IP Address ip.src
Destination IP Address ip.dst
MS/TP Source MAC MS/TP.src
MS/TP Destination MAC MS/TP.dst
Common keywords – BACnet
Description Wireshark syntax
Only BACnet Packets bacnet
BACnet Object Type bacapp.objectType
BACnet Object Instance bacapp.instance_number
BACnet Confirmed Service bacapp.confirmed_service
BACnet Unconfirmed Service bacapp.unconfirmed_service
BACnet Network Setup13F
Siemens Industry, Inc. 447
BACnet Object Type – Values
Object Type Value
Analog Input 0
Analog Output 1
Analog Value 2
Binary Input 3
Binary Output 4
Binary Value 5
Calendar 6
Command 7
Device 8
EventEnrollment 9
MultiState Input 13
MultiState Output 14
MultiState Value 19
BACnet Confirmed Service – Values
Object Type Value
confirmedCOVNotification 1
confirmedEventEnrollment 2
SubscribeCOV 5
ReadProperty 12
ReadPropertyMultiple 14
Write Property 15
WritePropertyMultiple 16
ConfirmedPrivateTransfer 18
Chapter 13–BACnet Network Setup, Troubleshooting, and its Impact on IT
448 Siemens Industry, Inc.
BACnet Unconfirmed Service – Values
Object Type Value
I-Am 26
I-Have 27
unconfirmedCOVNotification 28
unconfirmedEventNotification 29
Who-Has 33
Who-Is 34
Building Filters
Building Display Filter Expression You build a Display Filter by using the Filter Expression dialog box.
1. Select the Expression on the toolbar.
The Filter Expression – Profile: Default dialog box displays.
2. Select Field name, Relation, and Value to build the expression.
For BACnet, the following Field name sections are useful:
BACapp - Building Automation and Control Networks APDU
BACnet - Building Automation and Control Networks NPDU
BACnet MS/TP – BACnet MS/TP
Building Display Filter Packet Details Pane
1. Right-click Packet Detail pane.
2. Select a packet in the Packet List pane you would like to filter on.
3. Right-click on the part of the packet you want to filter on and select Apply as Filter.
4. Select the appropriate Logical Operator syntax.
The result is a Display Filter of bacapp.confirmed_service == 15, which results in only displaying Write Property packets.
Example
Packet 167 was highlight from the Packet List, the Service Choice: Write Property (15) in the Packet Detail pane, and then the Logical Operator syntax Selected.
BACnet Network Setup13F
Siemens Industry, Inc. 449
Displaying Statistics
This procedure allows you to display the statistics on all the packets you have captured and statistics for any packets that meet the Display Filter criteria you have defined.
To display the summary, select Summary from the Statistics drop-down menu.
Summary dialog box displays.
Chapter 13–BACnet Network Setup, Troubleshooting, and its Impact on IT
450 Siemens Industry, Inc.
Using Filter Expressions to Display COV Traffic • To define a filter to display all the COV traffic:
− Filter expression: bacapp.confirmed_service == 1 && !(bacapp.type == 2)
BACnet Network Setup13F
Siemens Industry, Inc. 451
The Summary dialog box displays statistics of a total of 4.978 COVs per second being sent.
• To filter on only show packets from a source IP address of 192.168.1.125:
− Filter expression: bacapp.confirmed_service == 1 && !(bacapp.type == 2) && (ip.src == 192.168.1.125)
− The Summary dialog box displays statistics of 4.444 COVs per second from IP address 192.168.125.
• To filter on only packets from Binary Value, 123:
Chapter 13–BACnet Network Setup, Troubleshooting, and its Impact on IT
452 Siemens Industry, Inc.
− Filter expression: bacapp.confirmed_service == 1 && !(bacapp.type == 2) && (ip.src == 192.168.1.125)&& (bacapp.objectType == 5) && (bacapp.instance_number == 123)
The Summary dialog box displays statistics of 4.089 COVs per second from Binary Value 123.
Using Filter Expressions to Display Alarms • To define a filter to display all the alarms:
Filter expression: bacapp.confirmed_service == 2 && !(bacapp.type == 2) The Summary dialog box displays statistics of a total of 2.703 alarms per second being sent.
• To filter to only display alarms from a source IP address of 192.168.1.125:
Filter expression: bacapp.confirmed_service == 2 && !(bacapp.type == 2) && (ip.src == 192.168.1.125) The Summary dialog box displays statistics of a total of 2.339 alarms per second from IP address 192.168.1.125.
• To filter to only display alarms from a Binary Value, 444:
Filter expression: bacapp.confirmed_service == 2 && !(bacapp.type == 2) && (ip.src == 192.168.1.125)&& (bacapp.objectType == 5) && (bacapp.instance_number == 444) The Summary dialog box displays statistics of 1.967 alarms per second from Binary Value 444.
Using Filter Expressions to Find Duplicate BBMD/Broadcast Storms • To define a display filter to display broadcasts generated by BBMD’s:
Filter expression: bvlc.function == 0x04 && ip.dst == 10.0.0.255
Both 10.0.0.19 and 10.0.0.54 are configured as BBMD’s on the same subnet.
The Summary dialog box displays statistics of 191.567 broadcasts per second occurring on this subnet.
Typical Bandwidth Usage
Siemens Industry, Inc. 453
Typical Bandwidth Usage As mentioned in the Network Bandwidth Effect section on page 199, Siemens BACnet components do not add significant overhead to a TCP/IP network. However, network bandwidth utilization is variable and dependent upon the number of panels, network speed, and network architecture. However, a short burst of traffic is possible, triggered by system events like alarms.
Siemens Industry, Inc. 455
Chapter 14–System Cyber Security Chapter 14 addresses best practices to ensure System Cyber security. Discussed in this chapter are the following topics:
• The importance of Cyber Security
• Best practices to ensure System Cyber security
• Cyber Security Assessment
The Importance of Cyber Security Cyber security is the concern of Siemens Industry Inc. and the Building Technologies Division of Siemens Industry, Inc. It is essential for us to secure Siemens Building Automation Systems against cyber threats to protect the information, assets and reputation of the customer and of Siemens. Siemens Industry Inc. recommends the cyber security level of the cyber security standard ISA 62443.03.03 Level 2. As employees of Siemens Building Technologies, we must position ourselves as the experts on cyber security and have to assume the end-user is not an expert of cyber security. This means we must inform and train ourselves and our customers on a continuing basis. Convenience is a short-lived event compared to the long term effects that a hacking event can pose to our customers and us.
If one of our systems is compromised the damage to the customer and to the Siemens reputation can be extensive.
Best Practices to Enhance Network Security
User Names and Passwords for Network Access
One of the most obvious best practices for software access is immediate removal and re-definition of default user names and/or passwords. The end user/owner should be made aware of the passwords and their usage in our system. They should be given a recommendation as to how to specify and use this password access. The Siemens standard should be adopted if the customer does not have his own system. If we are giving out passwords to end users, we must ensure that the end user does not use the same password on different systems, even if it is the same customer.
User accounts should be given to personnel only on a need-to-have and least rights basis (a user should only be given the rights she or he needs to perform their duties) and they should be maintained regularly and continuously.
Chapter 14–System Cyber Security
456 Siemens Industry, Inc.
Passwords should not be shared with others. Ideally, passwords and usernames should be immediately removed from the system if the user does not need access anymore. At minimum, passwords need to be changed regularly so that users who have changed job functions or have left the customer’s organization cannot continue to access to the system software.
Our customers need to be educated and advised to create their own IT policy if they do not have one. A Siemens minimum standard should be suggested if the customer, for whatever reason, does not want to create their own IT policy. Password policies must include certain standards, such as minimum complexity rules, and changing passwords at fixed time intervals.
Usernames should be assigned to individual users so that they can be monitored and/or held responsible for their action. Group identification should only be permitted when it is absolutely necessary for the work to be performed.
Customers should be given the option to choose the level of security they would like. Siemens recommends thatusers create the strongest practical password for their personal access. However, if the user chooses to create a weaker password, then his/her decision should be recorded. Some examples of procedures to create weak, strong, and strongest passwords are:
User Accounts • Allow the creation of a single username/password to be used by all employees
(weak).
• Create a specific user account for each individual employee and provide that info to the user (stronger).
• Create a new and unique username and password and provide it only if and when needed by the employee performing the work (strongest practical, and recommended).
Passwords • Less than 8 characters = weak.
• Only letters = weak
• Same as user name = weak
• Mixture of numbers and letters = stronger
• Words with numbers (john1966) = stronger
• Mixture of numbers, letters and special characters (john@1966, j@hn1966) = stronger
• Mixture of numbers, letters, capital letters and special characters longer than 8 characters (Chic@goCu&s@1908) = strongest.
APOGEE BAS Network Security Features
Siemens Industry, Inc. 457
Avoid the Use of Internet Access to the APOGEE BAS Network
The connection of the Insight server or any other part of the ALN to network with the Internet poses a great risk and is NOT recommended. It is the portal for hackers. The Insight server should not be used for anything other than the control and monitoring of the BAS. However, users are allowed to set up the APOGEE BAS for Internet access in any of the following ways:
• The Insight server is connected directly to the internet (weak security not recommended).
• The insight server is connected to the internet but the connection is controlled and exclusively used for remote support (will be turned OFF or timed) (stronger security).
• The insight server and its BLN is not connected to the Internet (strongest security).
Because Siemens Building Technologies personnel are the experts with our systems, we know the problems and benefits better than most of our customers. It is our responsibility to use that knowledge to protect our customer’s equipment and operations from cyber attacks. In the role of a subject matter expert, field personnel are in the position to advise customers in regard to the cyber security aspects of the Siemens BAS (Building Automation System). A recommendation based on the customer’s application should be made and a decision regarding the adoption of this recommendation should clearly be documented for future reference.
Remember, if a customer’s information is compromised by the use of the Siemens building control system the damage to the customer and our reputation, as well as financial loss, can be immense.
APOGEE BAS Network Security Features Cyber attacks the APOGEE Automation System can damage the customer’s building control equipment, interrupt the proper operation of his building control system, and result in the loss of valuable building control data. The Building Technologies Division of Siemens Industry, Inc. (SBT) takes the issue network security very seriously, and SBT has implemented up-to-date network security measures on the APOGEE Building Automation System15. Since network security also involves components and procedures beyond the APOGEE network, it should be recognized that network security is a joint effort between SBT and our customer’s IT personnel.
15 Information in this section is taken from the white paper titled APOGEE® Network Security, Rev.1, July 2004, which is posted on
InfoLink (http://iknow.us009.siemens.net/infolink/InfoLink.aspx?page=/infolink/Default.htm). This section just highlights the main security features of APOGEE BAS networks, as discussed in detail in this publication.
Chapter 14–System Cyber Security
458 Siemens Industry, Inc.
Insight Network Security Features
The Insight product uses built-in, encrypted Windows logon security. To log on to an Insight workstation, a user must have a valid Windows user account on the network domain. The User Accounts application allows authorized personnel to configure user access, including:
• Limiting how much access the user has to Insight applications.
• Controlling access to objects in the Insight database using Access Groups.
The Management Level Network (MLN) level user accounts and passwords are not contained in the Insight database, and the BLN level passwords are encrypted. Communications to the database is over a proprietary protocol through a single TCP/IP port. For an attacker to do anything more than corrupt or delete the database would require in-depth knowledge of the database’s proprietary structure.
To protect against data loss, the Insight Backup Utility allows authorized personnel to schedule regular Insight backups. To further secure the backup, the Backup Utility allows authorized personnel to direct the backup to be stored on another computer on the enterprise network.
With the Insight Life Safety option, only UL Listed Insight Fire Workstations are permitted to control the Fire Alarm System. These workstations are installed on a dedicated IP subnet and broadcast domain – isolated from the enterprise network. The communication protocol for the fire panels is proprietary and does not support transfers of executable files such as those that can contain viruses.
APOGEE GO for Insight employs the communication security and user
authentication of Microsoft®
Internet Information Services (IIS) software. Three authentication methods are supported: Anonymous, Basic, and Challenge/Response (IIS 4) or Integrated Windows (IIS 5). For additional security, all client-to-server Internet and intranet communications can be secured with Secure Sockets Layer (SSL). Communication between the APOGEE GO web server and the Insight database server is protected by Microsoft DCOM securities and a Siemens Building Technologies proprietary site key.
The Insight BACnet Client and Server option protects the customer’s APOGEE Automation System by disallowing file transfer (BACnet File Access Services), accepting only BACnet commands that are supported by the APOGEE Automated System, and allowing authorized personnel to select which APOGEE Automation points are available to BACnet devices.
The Insight Terminal Services option provides the customer with remote access to his Insight software using Windows Terminal Services. Access to the Insight database server is controlled by the Windows domain user account. Communication can be encrypted using Secure Socket Layers (SSL).
APOGEE BAS Network Security Features
Siemens Industry, Inc. 459
The RENO option allows the customer to configure an Insight workstation to send email, phone, pager, and simple message service (SMS) notifications about Insight alarms, failures and events. RENO does not allow personnel to make changes to the Insight database other than stopping alarm notifications. A RENO user must enter a valid Insight user ID and password to gain access to the system. The password is encrypted and stored in the Insight database.
The Insight OPC Server option enables your OPC (OLE for Process Control) applications to access your Insight database, using Microsoft DCOM security. DCOM provides security for program access, program launch, user identity and connection policies.
APOGEE Automation Field Panel Security Features
APOGEE Automation field panels include several built-in security features. All APOGEE field panels are secured with lock and key. Users must enter a user ID and an encrypted password to access the Man Machine Interface (MMI) of any APOGEE field panel. In addition, the field panels can be configured to lock out a user trying to access the MMI prompt after three failed password attempts (requires Firmware Revisions 2.6 or later).
The field panel database structure and its communication protocol with the Insight workstation are proprietary to Siemens Building Technologies, making it difficult for attackers to access the system. DOS files, which can contain malicious executables, are not supported. Denial of service attacks are mitigated since the field panel database is battery backed up and does not depend on the BLN, MLN, or Insight database to execute building control. A BLN directly connected to an Insight workstation with a Trunk Interface II makes intrusion very difficult because physical access to the trunk is also required.
APOGEE Ethernet field panels and APOGEE Ethernet Micro Servers (AEMs) allow the customer to use an Ethernet network for communication between field panels and Insight workstations. Ethernet field panels and AEMs include the following security features:
• The AEM Ethernet port and the APOGEE Ethernet field panel port are in constant use by the Insight workstation. Should an attacker disable that port, a message box in the System Profile application would announce the BLN failure.
• The AEM is physically located in the field panel enclosure requiring key access.
• Users must enter a password to configure an AEM.
• APOGEE Ethernet field panels and the AEM200 allow users to access the MMI using Telnet16, but a valid user name and password is required.
16 Telnet is a network protocol used on the Internet or local area network to provide bidirectional interactive text-oriented
communication capability using a virtual terminal connection.
Chapter 14–System Cyber Security
460 Siemens Industry, Inc.
• An open MMI session will automatically close after a timeout period if there is no activity from the connected terminal. This decreases the window of opportunity for an unauthorized user to take over an unattended terminal or, if Telnet, connect from another computer into a field panel with an open session.
• Since only one Telnet session can be open at a time this prevents an attacker from opening a session while a legitimate user is in a session.
• The Telnet feature for MMI sessions can be enabled or disabled individually per APOGEE Ethernet field panel. To enable Telnet requires that the user have privileges to use the Insight workstation. The APOGEE Ethernet field panel preserves the Telnet enable /disable state even if it should cold boot.
Modems allow phone line communication between field panels and Insight workstation or access to the field panel MMI. Modems include the following security features:
• The Modem port is limited to the Insight Autodial application or MMI dial-in, and the MMI port is limited to dial-in MMI only; a valid user name and password is required.
• An open MMI session will automatically close after a timeout period if there is no activity from the connected terminal. This decreases the window of opportunity for an unauthorized user to take over an unattended remote terminal.
• To configure a modem it must be physically disconnected from the field panel. The modem connection is secured in the field panel enclosure and requires key access.
APOGEE Network Security Best Practices
Siemens Building Technologies recommends that customers implement the following security best practices to make your APOGEE Automation network even more secure.
Limit Physical Access to your APOGEE Automation System by:
• Keeping areas with Insight workstations under lock and key
• Changing passwords and reviewing access privileges frequently.
• Limiting shares to logical drives on network computers
• Prohibiting the use of modems, except for Auto-Dial and RENO modems.
• Prohibiting the use of the APOGEE Automation server for applications other than the Building Automation System (i.e. word processing, emailing, etc.)
• Keeping field panels locked and key distribution limited
• Replacing any field panel batteries that do not report an OK status.
System Cyber Security Risk Assessment
Siemens Industry, Inc. 461
Run virus scanner and keep your virus scanner software up-to-date. The Insight software will coexist with any reputable anti-virus software. To preserve the performance of the Insight software, which is constantly accessing its database, Siemens Building Technologies recommends scanning a copy or backup of the database rather than the active database. Most anti-virus software can be setup to exclude certain directories, such as the database directory.
Back up your system regularly – especially critical data files. This allows you to quickly recover any data damaged by viruses or other malicious programs.
Always keep your computers up-to-date with the latest operating system security patches and service packs. If a technician is not available to regularly install security patches and service packs, configure Windows Update service to automatically download and install the latest Microsoft updates.
Use firewalls to protect your APOGEE Automation network. Hardware or software firewalls protect your network by limiting access to your network. Also, use personal
firewall software on your Insight workstations. BlackICETM
Firewall Software is the recommended personal firewall software for these connections. BlackICE protects a computer from unknown applications and from applications connecting to a network such as the Internet.
IT departments often install firewalls between different buildings in a facility. If Insight Database Server and Insight Database Clients must communicate across a firewall, specific ports must be open in the firewall to allow Insight to function properly. If issues arise concerning the open ports, solutions exist to resolve these issues. For example, an Access Control List (ACL) can be created. An ACL is a rule that can determine the source and type of traffic allowed through the firewall. An ACL can be created in the firewall to only allow control messages (ICMP), such as ping, from APOGEE IP addresses at the site.
Always consider putting a critical sub-system on a Virtual Local Area (VLAN). Multiple VLANs can be implemented on the same physical LAN. Thus, an APOGEE Automation System on its own VLAN can be isolated from the rest of the network.
System Cyber Security Risk Assessment Our building control systems can be installed into different types of buildings with different types of occupants. Depending on the building design and the occupant the security requirement will vary. As a base line Siemens Industry Inc has adopted the cyber security standard ISA 62443.03.03 level 2 (2013).
A risk assessment should be performed with the building owner and or the IT department responsible for the BAS network. If possible this assessment should happen during the systems specification phase, pre-sale. The following security aspects should be addressed as a minimum:
Chapter 14–System Cyber Security
462 Siemens Industry, Inc.
• Does the responsible IT department have a cyber security standard and can that be applied to the BAS and is that compliant with ISA 62443.03.03?
− No – The customer shall be advised on how they can adopt a standard policy or how their policy can be hardened to be compliant with ISA 62443.03.03 Level 2.
− Yes – Their policy can be adopted for the BAS
• Is the network hardware access limited to authorized personal (lock and Key) or is easily accessible?
− No – The customer shall be advised on how to secure the network hardware against tempering by putting them into secure locations or by mounting them in a lockable enclosure.
− Yes – The access should be managed carefully to allow access when needed.
• Is the Insight server in a server room with access limited to authorized personal only?
− No – It is recommended to keep access to the server limited. The customer should be advised on lockable server enclosures, disabling of USB and other ports for memory devices to prevent the introduction of malware.
− Yes – The access should be managed carefully to allow access when needed.
• Does the BAS need to send data across a public or corporate network (i.e. for energy monitoring)
− No – No immediate action required but the requirement needs to be monitored.
− Yes – Data should not be send across a public or corporate network without protection. For a corporate network we recommend at minimum the setup of a VLAN for the BAS to send data. For sending information across a public network a secure and managed VPN access system is recommended.
• Does the BAS need to be accessed through a public network (remote access, remote monitoring)?
− No – No immediate action required but the requirement needs to be monitored.
− Yes – Access shall be provided via a managed VPN system. If possible the connection should be turned off at the BAS side and only turned ON if the connection is required for the amount of time required.
• What is the potential damage if the system is tampered with?
System Cyber Security Risk Assessment
Siemens Industry, Inc. 463
− Has the collected historical trend data any value (FDA, Quality Assurance, etc.).
− Is the network connected to computers or servers that hold private information?
− Is there potential damage if the BAS is not operated within defined parameters (i.e. high air pressure for a clean room, specific temperature and humidity for a laboratory, etc.).
• Is there any reason why data for the BAS needs to be transferred to and from a memory device (i.e. USB stick)?
− No – all memory device ports on the insight server and clients should be disabled to prevent introduction of malware.
− Yes – The memory device must be closely monitored. Purchase a device specifically for this purpose Label the device clearly for identification purposes Secure all data on it via an encryption/Vault program Format the device after every use and frequent Run frequent virus checks on it to ensure it is clean. Store the device security on the premises and do not allow it to be used for any other purpose.
• Is the BAS connected to a network that can connect to a server with Intellectual Property [IP] information or personal information on it?
− No: No immediate action required but the requirement needs to be monitored.
− Yes: Any BAS network activity should be run on a secure VLAN. The BAS should not be connected to a server system with IP on it without strong security measures. Using a VLAN to separate the network traffic has to be an absolute minimum.
A minimum of the ISA 62443.03.03 level 2 standard should be adopted.
Siemens Industry, Inc. 465
Glossary This glossary describes various terms and acronyms used in this application guide. For a comprehensive listing of building control terminology, see the Technical Glossary of Building Controls Terminology and Acronyms (125-2185).
ASHRAE
American Society of Heating, Refrigerating and Air-Conditioning Engineers. An HVAC industry organization for advancing the arts and sciences of heating, refrigeration, air conditioning, and ventilation for the benefit of the public.
ALN
Automation Level Network. An RS-485 network for use by the APOGEE building level controllers.
Communication trunk connecting Insight computers and field panels in a building control system. You must have a ALN Account in order to access and perform operations at a field panel on a specific ALN.
ANSI
American National Standards Institute.
Application Protocol Data Unit (APDU)
A unit of data specified in an application protocol and consisting of application-protocol-control-information and possibly application-user-data (ISO 9545).
ARCNET
Attached Resource Computer Network. Type of LAN that works like a token-ring network, except that the connections between computers do not need to be in the shape of a ring. ARCNET networks usually use Ethernet hardware.
B-BC
See BACnet Building Controller Profile.
B-OWS
See BACnet Operator Workstation Profile.
Glossary
466 Siemens Industry, Inc.
BACnet
Data communication protocol for Building Automation and Control networks, based on specifications detailed in ANSI/ASHRAE Standard 135. The first version of this standard was published in 1995 as ANSI/ASHRAE Standard 135-1995. The latest published version of this standard (published in 2012) is ANSI/ASHRAE Standard 135-2012. BACnet allows devices from multiple manufacturers to communicate and work together.
BACnet Building Controller Profile (B-BC)
BACnet defines a B-BC as a general-purpose, field-programmable device capable of carrying out a variety of building automation and control tasks.
BACnet Device A BACnet device is a microprocessor-based unit that uses the BACnet protocol for interoperable communication.
BACnet Device ID
A number, between 0 and 222, assigned to a BACnet device by the person configuring a BACnet network. This number must be unique per job (internetwork). Also called Device Instance Number.
BACnet Foreign Device
A BACnet device (workstation or field panel) that has an IP connection but does not have a BBMD or multicast router on its subnet to allow it access to BACnet broadcast messages.
BACnet Interest Group (BIG)
Associations formed by BACnet users for the benefit of BACnet users. BIGs enable individuals to exchange information and share experiences about the implementation and application of BACnet. Many BACnet Interest Groups have formed around the world to support BACnet users. There is BIG-NA, North America (www.big-na.org); BIG-EU, Europe (www.big-eu.org), and BIG-AA, AustralAsia (www.big-aa.org).
BACnet Internetwork
Two or more BACnet networks interconnected by routers.
The job (the whole BACnet network on a job). This includes all BACnet segments regardless of media or protocol or networking technology (ARCNET, MS/TP, etc.).
Glossary
Siemens Industry, Inc. 467
BACnet Interoperability Building Block (BIBB)
Collections of one or more BACnet services that function to define the inter-operational capabilities of a BACnet device. Certain BIBBs may also be predicated on the support of certain, otherwise optional, BACnet objects or properties. BIBBs may also constrain allowable values of specific properties or service parameters.
BACnet Router
A device that interconnects two or more BACnet networks to form a BACnet internetwork. BACnet routers make use of BACnet network layer protocol messages to maintain their routing tables. A router may, or may not, provide BACnet application layer functionality.
BACnet/IP Broadcast Management Device (BBMD)
An application that forwards BACnet/IP broadcast messages across IP routers. One BBMD must appear on either side of an IP router, and communicate using unicast messages.
BACnet Object
In a BACnet system a BACnet Object is a collection of information within a device described by its properties. An object might represent information about a physical input or output, or it may represent a logical grouping of points that perform some function, such as a setpoint. Every object has an identifier (such as AI-1) that allows the BACnet system to identify it. An object is similar to a data point, although it contains additional information other than present value. It is only through its properties that an object is monitored and controlled.
BACnet Operator Workstation Profile (B-OWS)
BACnet defines a B-OWS as ‘the operator’s window into a BACnet system. Primarily used for on-line operations.
BACnet Network A BACnet network is a set of devices that can communicate using the BACnet protocol.
BACnet Testing Laboratories™ (BTL)
Laboratories formed by the BACnet Manufacturers Association (currently known as BACnet International) to test building automation products and certify them as BACnet compliant.
Glossary
468 Siemens Industry, Inc.
BBMD
See BACnet/IP Broadcast Management Device.
BIBB
See BACnet Interoperability Building Block.
BTL
See BACnet Testing Laboratories™.
Building Level Network (BLN)
Former name for Automation Level Network (ALN). See definition for ALN above.
change-of-value (COV)
Method of sampling (trending) point values at a field panel. A COV is recorded when the change in a point value is greater than the user-defined COV limit (analog points) or when there is a change of state for a digital point.
Cloaking A process which removes BACnet devices from ALNs in System Profile and prevents the Insight device discovery process from re-adding the devices. In Insight, accessed through a check box in the BACnet Field Panel Definition dialog box.
Datagram A term used to describe data that is put into packets for network transport.
Device Instance Number
See BACnet Device ID.
Domain Name System (DNS) Domain Name Server (DNS)
An Internet service that translates domain names into IP addresses.
Alphabetical domain names (www.example.com) are easier to remember for humans, but the Internet is based on IP addresses. So a DNS server does the translation into the corresponding IP address. If one DNS server can’t translate a particular domain name, it asks another one in the DNS network, and so on, until the correct IP address is returned.
Glossary
Siemens Industry, Inc. 469
Default method of name resolution for Windows 2000. The domain naming service (DNS) allows computers on a domain to determine the Computer Name assigned to an IP address or the IP address assigned to a computer name. Windows 2000 uses Dynamic DNS where the name table for the domain is automatically updated as computers join the network or become unavailable.
Electronic Protocol Implementation Conformance Statement (EPICS)
A self-documentation file that lists all of the objects, properties and services supported by a device.
EPICS
See Electronic Protocol Implementation Conformance Statement.
Ethernet
Type of protocol developed by the IEEE (802.3) that maps to the Physical layer in local area networks.
A combination wiring and signaling standard for networking. The IEEE standard 802.3 that defines the functions of the Logical Link Control sub-layer of the Data Link layer in the OSI model. Also defined are the network operations of the Physical and Data Link layers. Ethernet is the most popular form of local area network.
A high-speed LAN which runs on a variety of media-STP, coaxial cable, or fiber optics.
Field Level Network (FLN)
Network consisting of Terminal Equipment Controller (TEC), Unitary Controllers (UC), fume hoods, etc.
An FLN allows application specific controllers to communicate with field panels. This allows for the controllers to be manipulated from central points in the field panels.
Foreign Device
See BACnet Foreign Device.
Group Object
The Group object type defines a standardized object whose properties represent a collection of other objects and one or more of their properties. A group object is used to simplify the exchange of information between BACnet Devices by providing a shorthand way to specify all members of the group at once. A group may be formed using any combination of object types
Glossary
470 Siemens Industry, Inc.
Half-Router
In BACnet, a device that can participate as one partner in a point-to-point (PTP) connection. Two half-routers form an active PTP connection and act as a single router.
Instance Number
In BACnet, a number that uniquely identifies an object within a device or a device on an internetwork. Device Objects are required to have an Instance Number that is unique internetwork-wide. Instance numbers may range from 0 to 4194303. For devices, see BACnet Device ID.
Integrated Systems Architecture (ISA)
A Siemens initiative to standardize BACnet usage across Siemens business units.
Internetwork
See BACnet Internetwork.
Interoperability Area (IA)
BACnet defines functionality in terms of "Interoperability areas" (IAs). The five IAs are data sharing, alarm and event management, scheduling, trending, and device and network management.
Internet Protocol (IP)
Acronym for Internet Protocol. IP handles the breaking up of data messages into packets (also called datagrams), the routing of the packets from their origin to the destination network and node, and the reassembling of the packets into the data message at the destination. IP operates at the internetwork layer of the TCP/IP model, which is equivalent to the network layer of the ISO/OSI reference model.
IP Address
Address that is assigned to every computer and all Ethernet ALN and BACnet controllers. An IP address uniquely identifies a node on the network.
The 32-bit address used to identify a computer on a network using the IP protocol. A 4-octet number like 128.253.245.74. An IP address is separated into the network address portion and the host portion.
Glossary
Siemens Industry, Inc. 471
IPsec (IP security) (Internet Protocol security)
A standard for securing Internet Protocol communications by encrypting and/or authenticating all IP packets. IPsec provides security at the network layer.
Local Area Network (LAN)
Network of computers and other devices that is confined to an office, a building, or a company.
LonTalk
Echelon Corporation’s LAN technology. It is a specification for the Physical and Data Link layers of their protocol architecture.
Media Access Control (MAC)
The part of a network that handles access to the physical network (media). In BACnet, each device has a unique MAC Address/Network Number combination that identifies it on the BACnet internetwork.
MS/TP
MS/TP (Master-Slave/Token-Passing) is an Electronics Industry Alliance (EIA) standard for multipoint communications–contrary to just point-to-point communications like RS-232. MS/TP is also known as RS-485 or EIA-485.
National Institute of Standards and Technology (NIST)
An agency of the U.S. Department of Commerce's Technology Administration. The NIST charter is to strengthen the U.S. economy and improve the quality of life by working with industry to develop and apply technology, measurements, and standards. NIST has played an integral role in the development of BACnet.
Operates a lab where manufacturers can test their products for BACnet conformance.
"Native" BACnet
A phase that implies that whatever is being described only speaks and understands BACnet.
Glossary
472 Siemens Industry, Inc.
Network
Collection of Insight workstations, field panels, printers, and equipment controllers that are electronically and physically connected to communicate with each other for sharing building control data.
ONVIF (Wikipedia definition): The Open Network Video Interface Forum (ONVIF) is a global and open industry forum with the goal to facilitate the development and use of a global open standard for the interface of physical IP-based security products. Or in other words, to create a standard for how IP products within video surveillance and other physical security areas can communicate with each other. ONVIF is an organization started in 2008 by Axis Communications, Bosch Security Systems and Sony.
OPC
Open Platform Communications. OPC is a standard for industrial communications that enables universal connectivity and interoperability. OPC technology is based on Client/Server architecture and provides standards-based communication that allows users to employ a "best of breed" solution for their projects. In essence, OPC is the Modbus of the new century.
Point-to-Point (PTP)
Point-to-Point Protocol – a protocol provided by an Internet Service Provider (ISP) for connection to the Internet via a dial-up connection. PTP is faster, more reliable and supports more functions than the comparable SLIP protocol. PTP also applies to RS-232 (EIA-232) connections
Properties
The means by which objects are monitored and controlled. BACnet specifies 123 properties of objects. Three properties-Object-identifier, Object-name, and Object-type-must be present in every object. BACnet also requires that certain objects support specific additional properties. The type of object and the type of device in which that object resides determine which properties are present. Some properties can accept writes, and others can only be read.
Protocol for Data Communications
A set of rules governing the exchange of data over a computer network.
Glossary
Siemens Industry, Inc. 473
Protocol Implementation Conformance Statement (PICS)
A document that details the particular BACnet objects, services and capabilities supported by a type of BACnet device. Every BACnet-compliant device has an associated PICS published by the manufacturer.
Available from building automation control vendors, a PICS documents such things as supported conformance class, functional groups, standard application services, standard object types, data link layer options, character sets, and any special functionality built into the protocol.
Router
Device used to connect networks using different architectures and protocols. Routers determine the best path for sending data, and filter broadcast traffic to the local segment.
A device that connects two LANs. Routers are similar to bridges, but provide additional functions, such as message filtering and forwarding based on various criteria. A router is a physical device that is used to pass messages on the network level (network layer of the OSI model).
PXC Compact
The PXC Compact is a series of high-performance, Direct Digital Control (DDC), programmable controllers. The controllers operate stand-alone or networked to perform complex control, monitoring, and energy management functions without relying on a higher-level processor. The Compact series communicates with an Insight® workstation and other APOGEE® and pre-APOGEE field panels on a peer-to-peer Automation Level Network (ALN).
PXC Modular
The PXC Modular is the newest ALN controller offering for the APOGEE Automation System and is a global hardware platform. It has installation flexibility, a capability for large point counts, and supports FLN devices. The Modular series communicates with an Insight® workstation and other APOGEE® and pre-APOGEE field panels on a peer-to-peer Automation Level Network (ALN), and with TX-I/O modules directly through the TX-I/O self-forming bus.
Serial Line Internet Protocol (SLIP)
A protocol provided by an Internet Service Provider (ISP) for connection to the Internet via a dial-up connection. SLIP can be used on RS-232 serial ports and supports asynchronous links. SLIP is not as common as PPP.
Glossary
474 Siemens Industry, Inc.
Services
How one BACnet device gets information from another device, commands a device to perform certain actions (through its objects and properties, of course), or lets other devices know that something has happened. The only service that is required to be supported by all devices is the Read-property service. There are a total of 32 standard services.
SMTP (Wikipedia definition): Simple Mail Transfer Protocol (SMTP) is an Internet standard for electronic mail (e-mail) transmission across Internet Protocol (IP) networks. SMTP was first defined by RFC 821 (1982, eventually declared STD 10), and last updated by RFC 5321 (2008) which includes the Extended SMTP (ESMTP) additions, and is the protocol in widespread use today.
SNMP
Simple Network Management Protocol. SNMP is an application layer protocol that facilitates the exchange of management information between network devices. It is part of the Transmission Control Protocol/Internet Protocol (TCP/IP) suite. SNMP enables network administrators to manage network performance, find and solve network problems, and plan for network growth.
Subnet
See Network.
Target Target Reference
In BACnet scheduling, the BACnet Object Property Reference. That which is written to by the BACnet schedule.
Third-party BACnet Device
A non-APOGEE /non-Siemens BACnet device. A BACnet device from another manufacturer. Not to be confused with a BACnet Foreign Device.
Third-party BACnet Workstation
A non-Insight workstation that is on or reachable through BACnet/IP. The level of interoperability that may be achieved is limited by many factors.
Glossary
Siemens Industry, Inc. 475
TCP/IP
Transmission Control Protocol/Internet Protocol. TCP/IP is the de facto protocol standard used by the Internet. Whereas IP deals only with packet transmission, TCP enables two hosts to establish a connection and exchange streams of data. TCP handles delivery and order of data streams.
User Datagram Protocol (UPD)
Used for internetworking, UDP is a connectionless transport protocol that facilitates transport of the IP.
User Datagram Protocol is an alternative transport service to Transmission Control Protocol (TCP). Most internet messages are encapsulated in a TCP frame. TCP is a “reliable”, connection-oriented transport service. That is, it guarantees that the message reaches its destination. Since the BACnet protocol itself guarantees delivery, TCP is not required. Thus, BACnet can use UDP instead. UDP is a connectionless transport layer protocol that exchanges datagrams (packetized data) without acknowledgments or guaranteed delivery
UTC
(Wikipedia definition): Coordinated Universal Time (UTC) is the primary time standard by which the world regulates clocks and time. It is one of several closely related successors to Greenwich Mean Time (GMT).
Virtual network
The representation of P2 ALN devices and points as BACnet objects to the rest of the BACnet internetwork. This is achieved by the Insight BACnet Server. Virtual network is a BACstac term.
WAN (Wide Area Network)
A connection that ties together computers or LANs in locations across a city, country or even overseas.
Index
476 Siemens Industry, Inc.
Index Add COV and Add Interval Definition Dialog
Boxes, 265 Additional Notification Classes and
Recipient Lists, 347 Advanced Settings Dialog Box, 252 Advantages for products residing on BACnet
MS/TP ALN, 108 Advantages for Products Residing on
BACnet MS/TP FLN, 113 Alarm Acknowledgements, 72, 328 Alarm Acks, 212 Alarm and Event Applications, 175 Alarm and Event Management, 58, 67 Alarm Enable/Disable, 327 Alarm Message Definition, 356 Alarm Messages, 214, 330, 339, 344 Alarm Notification Classes, 339 Alarm Notification Classes and Messages,
343 Alarm Priority, 214, 329 Alarm Priority Colors, 339, 348 Alarms, 212 Alarms, 175 Analog Input Object, 32 Analog Output Object, 33 Analog Value Object, 35 APOGEE BACnet Field Panel, 149
Using BACnet Calendar Days, 305 APOGEE BACnet Field Panel
Interoperability, 64 APOGEE GO, 214, 331 APOGEE Trending: Non-BACnet vs. BACnet,
362 Application Initial Values, 243 Application Initial Values Dialog Box, 264 Application Summary, 183 Attribute Duplicator, 215
Backup and Restore, 225 Backup and Restore Password, 69, 76 Backup/Restore, 391 Backward Compatibility, 212 BACnet Add Trend Definition Dialog Box,
264 BACnet Address Table, 245 BACnet and APOGEE, 314 BACnet BLN Sorting Options, 226 BACnet Broadcast Management Device
(BBMD), 94 BACnet Broadcast Management Device
Functionality, 130 BACnet Browser, 330 BACnet Browser Features, 219 BACnet Browser Limitations, 220 BACnet Building Controller (B-BC) Profile, 61 BACnet Cimetrics BACstac, 90 BACnet Client, 100 BACnet Client and Server Options, 70, 99 BACnet Communication Diagnostic, 216,
397 BACnet Communications, 93 BACnet Data, 234 BACnet Destination Dialog Box, 258 BACnet Device, 29 BACnet Device Communication Control, 396 BACnet Device Database Storage, 303 BACnet Device Profiles, 59 BACnet Export, 270 BACnet Export Map Entries Tool, 216 BACnet Field Panel Definition, 75 BACnet FLN Device Definition Dialog Box,
242 BACnet FLN Device Points, 234 BACnet Foreign Devices, 97
Index
Siemens Industry, Inc. 477
BACnet Implementation of APOGEE Logical Points, 167
BACnet Implementation within APOGEE, 7 BACnet Interoperable Building Blocks, 55 BACnet Intrinsic Alarming Example, 348 BACnet MS/TP, 101 BACnet MS/TP ALN Performance
Considerations, 107 BACnet MS/TP BLN Configuration, 240 BACnet MS/TP Driver for Firmware Revision
3.0 Only, 115 BACnet MS/TP FLN Configuration, 240 BACnet MS/TP FLN Design Considerations,
114 BACnet MS/TP FLN Performance
Considerations, 110 BACnet MS/TP Router, 122 BACnet Multiple Device Editing, 227 BACnet Network Communication Features,
130 BACnet Network COVs, 134 BACnet Networking Technologies, 85 BACnet Notification Class Dialog Box, 257 BACnet Object Browser, 71
Accessing a Calendar Object, 306 BACNET Object Browser, 218 BACnet Operator Workstation (B-OWS)
Profile, 62, 63 BACnet Over Ethernet, 86 BACnet Point Names Dialog Box, 255 BACnet Protocol Model, 87 BACnet Router vs. IP Router, 98 BACnet Scheduling Example 1, 307 BACnet Scheduling Example 2, 309 BACnet Scheduling Example 3, 310 BACnet Scheduling Example 4, 310 BACnet Scheduling Example 5, 311 BACnet Scheduling Examples, 307 BACnet Server, 100 BACnet TECs, 120, 122 BACnet Text Messages, 213, 329
BACnet Trending in APOGEE, 362 BACnet Trending Theory, 359 BACnet/IP, 86, 93 Basic BACnet Networking, 91 BAS-o-matic Protocol Analyzer, 383 BBMD, 69, 75 BBMD Routing Tables, 173 BBMD Table Dialog Box, 254 Binary Input Object, 36 Binary Output Object, 37 Binary Value Object, 39 BLN Account TAB, 270 BLN Definition, 246 Browsing, 169 BTL Certification, 161 Build System Profile, 391 Building Controller Profile (B-BC) and
Operator Workstation Profile (B-OWS), 60 Calendar Object, 43 Certification, 52 Cloaked Panels, 232 Cloaking, 75, 259 Command Object, 43, 68, 229 Command Object Editing, 74 Command Priority, 268 Command Priority Array Strings, 244 Command Priority Array vs. APOGEE, 24 Command Priority Properties, 22 Commander, 220 Commanding, 169 Commissioning Report Generator, 393 Commissioning Tool Support for APOGEE
BACnet Field Panels, 390 Connecting a Separate BAS-o-matic
Computer, 384 Connecting to a Network, 384 Copy Field Panel, 392 COVs, 67 Cross-Trunk, 76 Cross-Trunk Communications, 133 Data Sharing, 57, 65
Index
478 Siemens Industry, Inc.
Database Transfer, 223 Database Transfer of Object Types, 75 Device And Network Management, 68 Device Communication Control, 262 Device Discovery, 136 Device Management, 58 Device Re-Initialization, 261 Device Specific Names, 167 DHCP and DNS Support, 174 Dialout, 68 Disadvantages for products residing on
BACnet MS/TP ALN, 109 Disadvantages for Products Residing on
BACnet MS/TP FLN, 114 Display BACnet Priority, 236 Dynamic Plotter, 226, 363 Enable Device Discovery, 395 Encoded Object Names, 165 Engineering Units, 172, 233 Error Messages, 226 Event Builder, 229 Event Enrollment Object Alarm Messages,
337 Event Enrollment Object Creating and
Editing, 336 Event Information and Alarm Summary, 213 Event Log, 240 Event Printer, 232 Event Scheduling, 300 Events–System Messages, 175 Example BACnet Job (Internetwork), 142 Example System, 142 Field Level Network Devices, 76 Field Panel Database Upload/Download, 75 Field Panel Features, 155 Field Panel Hardware, 150 Field Panel Tools, 69 File Object, 44 Firmware, 162 Firmware Loading Tool, 391 FLN Devices, 260
Floating Alarm Limits, 327 Foreign Device, 69, 75, 132 Foreign Device Settings Dialog Box, 256 Foreign Device Support, 174 Get Event Information vs. Alarm Summary,
328 Getting Help, IV Global Broadcast Who-Is, 395 Global Commander, 232 Graphics, 232 HAND-OFF-AUTO Switches, 170 Impact to MMI, 27 Impact to PPCL, 28 Impact to TEC Subpoints, 29 Initials, 71, 212, 327 Insight Account Tab, 269 Insight Alarm and Event Management, 71 Insight BACnet Communications Tools, 394 Insight BACnet Option, 211 Insight BACnet Option Security, 136 Insight Data Sharing, 70 Insight Device and Network Management,
74 Insight Features for BACnet, 212 Insight Interoperability, 69 Insight Scheduling, 72 Insight Soft Controller APOGEE SSTO, 301 Insight Trending, 74 Insight with a Remote AEM BLN on a
Common MLN/BACnet BLN, 126 Insight with APOGEE BACnet Field Panels on
a Common MLN/BACnet BLN, 127 Insight with Dedicated BLN on a Common
MLN/BACnet Network, 124 Insight with Dedicated BLN on Separate
MLN and BACnet Networks, 123 Insight with Routers Using BBMDs and
Foreign Devices, 129 Installing BAS-o-matic v5.0, 385 Instance Number Allocation, 167 Interoperability, 51
Index
Siemens Industry, Inc. 479
L2SL Point, 349 Life Safety Alarms, 328 Log Tab, 224 Logical Grouping of BACnet FLN Devices,
241 LonTalk, 87 LTD Point, 350 Master-Slave/Token-Passing, 86 MMI, 183 MMI Database Transfer, 391 Modifying the Priority Array, 25 MS/TP Device
adding, 427 Multiple Device Configuration, 394 Multi-state Input Object, 40 Multi-state Output Object, 41 Multi-state Value Object, 42 Native BACnet and B-OWS, 211 Native BACnet Devices On The Same LAN,
91 Native BACnet Devices with Different LAN
Technologies, 91 Native BACnet to Non-Native BACnet
Devices, 92 Network Bandwidth Usage, 135 Network Management, 57, 173 Non-Field Panel Data Transfer, 392 Notification Class, 72, 355, 376 Notification Class Dialog Box, 256 Notification Class Object, 44 Notification Classes, 344 Object Basics, 162 Object Names and Instance Numbers, 65,
165 Object Selector, 232 Object Support Summary, 162 Object Types, 225 Objects Supported, 66 Objects Theory, 19 Obtaining BAS-o-matic, 383 One-Hop, 95
Operation, 27 Organization of Guide, II Other Objects Supported by APOGEE
BACnet Field Panels, 43 Other System Profile BACnet Features, 229 Panel Configuration Report, 236 Panel Definition, 250 Panel Display Report, 237 Panel Point Definition Report, 237 Panel Trend Data Detail Report, 237 Panel Trend Definition Report, 238 Physical Network Configurations, 123 Point Alarm Setup, 340 Point Checkout Data, 393 Point Command Priority, 184 Point Commanding, 67, 71 Point Definition Report, 238 Point Details, 233 Point Editor, 233 Point Editor Event Enrollment, 331 Point Names, 70 Point Objects, 330 Point Priority, 212 Point Summary Report, 393 Point Transfer, 392 Point-Like Objects, 31, 70, 167 PPCL, 66, 177 Program Editor, 236 Progress Tab, 223 Properties of Objects, 20 Proprietary Applications, 68 Protocol Implementation and Conformance
Statement, 53 Pulse Accumulator, 173 Purpose of this Guide, II PXC Compact, 232 PXC Compact Slope/Intercept, 235 PXC Compact Support, 232 Recipient List, 339, 378 Reference Materials, III Releasing, 169
Index
480 Siemens Industry, Inc.
Relinquish Default, 171 RENO Notification, 235, 331 Report Builder/Reports, 236 Report Builder/Viewer, 363 Reports, 236 Resident Points, 179 RS-485 MS/TP ALN, 106 RS-485 MS/TP FLN, 109 Running the LocalNET Configuration Utility,
144 SAT Point, 351 Schedule Object, 44 Schedule Object Properties that Can be
Commanded, 304 Scheduler, 240 Scheduling, 57, 68, 176 Scheduling Trend Collections, 370 Scheduling Trends, 366 Send Comments, IV Services Not Supported, 49 Services Supported, 48, 66 Services Theory, 46 Services to Support the BACnet Browser, 66 Setting Up BACnet Algorithmic Alarming,
331 Setting Up BACnet Intrinsic Alarming, 340 Setup Steps, 371 Specifying BACnet, 53 SSP Point, 354 Start Stop Time Optimization (SSTO), 301 State Text, 172 Support for Deadband, 234 Support for Trend Log Objects in Other
Devices, 362 Symbols, III System Configuration, 142 System Messages, 67, 327 System Profile, 240 System Profile Report, 238 System Summary, 183 TEC Subpoints, 66, 168
TEC Tool–Override Commands, 170 TEC Tool–Releasing, 171 Terminal Emulation, 391 The OBJECT_TYPE Property, 21 The Out-Of-Service Property, 171 Third-Party Proprietary Objects, 71 Time Synchronization, 139 Time-of-Day Scheduling, 264 Totalization, 172 Totalization Log Report, 238 Trend Collection Report, 238 Trend Data Detail Report, 238 Trend Definition Editor, 264, 364 Trend Definition Report, 238 Trend Definitions, 264 Trend Editor, 264 Trend Interval Report, 239 Trend Log Object, 44 Trend Sample Report, 239 Trend Summary Report, 239 Trending, 57, 68, 174 Trending Wizard - Select BACnet Device(s)
Dialog Box, 267 Two-Hop, 96 Unknown BACnet alarms, 213 Unknown BACnet Alarms, 328 Unsolicited COV Subscription List Dialog
Box, 253 Upload and Download, 68, 76 Upload Selected Dialog, 224 User Account Report, 239 User Accounts, 267 Using BAS-o-matic for BACnet on Ethernet,
389 Using BAS-o-matic on BACnet/IP, 386 Using the Insight Workstation for BAS-o-
matic, 385 Viewing with the BACnet Browser, 44 Who-Is Diagnostic Tool, 263
Custom Send, 395
Siemens Industry, Inc. 481
www.sbt.siemens.com
Siemens Industry, Inc.Building Technologies Division1000 Deerfield ParkwayBuffalo Grove, IL. 60089-4513USA1-847-215-1000
Part No. 125-1984Copyright © 2013 Siemens Industry, Inc.
