9MA10271 - User Guide BACNET AAC Application Notes - en - 11.05.16

FREE Studio
BACnet Objects
BACnet Application Notes
05/2016
Application
Notes
9MA10252.00
www.eliwell.com
The information provided in this documentation contains general descriptions and/or technical
characteristics of the performance of the products contained herein. This documentation is not intended
as a substitute for and is not to be used for determining suitability or reliability of these products for
specific user applications. It is the duty of any such user or integrator to perform the appropriate and
complete risk analysis, evaluation and testing of the products with respect to the relevant specific
application or use thereof. Neither Eliwell nor any of its affiliates or subsidiaries shall be responsible or
liable for misuse of the information contained herein.
If you have any suggestions for improvements or amendments or have found errors in this publication,
please notify us.
No part of this document may be reproduced in any form or by any means, electronic or mechanical,
including photocopying, without express written permission of Eliwell.
All pertinent state, regional, and local safety regulations must be observed when installing and using this
product. For reasons of safety and to help ensure compliance with documented system data, only the
manufacturer should perform repairs to components.
When devices are used for applications with technical safety requirements, the relevant instructions must
be followed.
Failure to use Eliwell software or approved software with our hardware products may result in injury,
harm, or improper operating results.
Failure to observe this information can result in injury or equipment damage.
© 2015 Eliwell Controls s.r.l. All rights reserved.
2 9MA10271 05/2016
TABLE OF CONTENTS
CHAPTER 1. Introduction........................................................................ 9
1.1. Definitions........................................................................................ 9
1.2. Requirements ................................................................................. 10
1.3. Website........................................................................................... 10
1.4. BACnet/IP and BACnet MS/TP....................................................... 10
1.4.1. BACnet/IP profile............................................................................................ 11
1.5. Network examples........................................................................... 13
CHAPTER 2. BACnet Objects................................................................ 14
2.1. First Start-up................................................................................... 14
2.2. BACnet objects............................................................................... 15
2.2.1. DEVICE object............................................................................................... 22
2.2.2. ANALOG VALUE object................................................................................. 23
2.2.3. BINARY VALUE object................................................................................... 26
2.2.4. MULTI STATE VALUE object.......................................................................... 27
2.2.5. CALENDAR object......................................................................................... 28
2.2.6. SCHEDULE object......................................................................................... 30
2.2.7. NOTICATION CLASS object.......................................................................... 34
2.3. FREE Studio Device ...................................................................... 37
2.3.1. EDE file.......................................................................................................... 43
2.3.2. Management of pre-existing projects............................................................. 44
CHAPTER 3. Libraries 46
3.1. BACnet_IEC.................................................................................... 46
3.2. Functions......................................................................................... 46
3.3. Enumerations ................................................................................. 47
3.3.1. BACnet_IEC vars........................................................................................... 48
CHAPTER 4. APPENDIX - B-AAC PROFILE.......................................... 49

CHAPTER 5. BACnet Interoperability Building Blocks Support......... 51
5.3.1. Data Sharing.................................................................................................. 51
5.3.2. Alarms and Events......................................................................................... 52
5.3.3. Schedules....................................................................................................... 52
5.3.4. Trends............................................................................................................ 53
3 9MA10271 05/2016
5.3.5. Device Management...................................................................................... 53
5.3.6. Network Management.................................................................................... 54
5.3.7. Supported BACnet Object Types .................................................................. 55
5.3.8. Device Object - FREE Studio......................................................................... 57
5.3.9. Controller Data Types..................................................................................... 59
5.3.10. Analog Input Object - FREE Studio.............................................................. 60
5.3.11. Analog Output Object - FREE Studio........................................................... 61
5.3.12. Analog Value Object - FREE Studio............................................................. 62
5.3.13. Binary Value Object - FREE Studio.............................................................. 63
5.3.14. Multi-State Input Object - FREE Studio........................................................ 63
5.3.15. Multi-State Value Object - FREE Studio....................................................... 65
5.3.16. Schedule Object - FREE Studio .................................................................. 66
5.3.17. Notification Class Object - FREE Studio...................................................... 67
5.3.18. Calendar Object - FREE Studio................................................................... 67
4 9MA10271 05/2016
SAFETY INFORMATION
Important Information
Read these instructions carefully, and look at the equipment to become familiar with the device before trying to install,
operate, service, or maintain it. The following special messages may appear throughout this documentation or on
the equipment to inform of potential hazards or to call attention to information that clarifies or simplifies a procedure.
The addition of this symbol to a Danger safety label indicates that an electrical hazard exists, which will result
in personal injury if the instructions are not followed.
This is the safety alert symbol. It is used to alert you to potential personal injury hazards.
Obey all safety messages that follow this symbol to avoid possible injury or death.
DANGER
DANGER indicates a hazardous situation which, if not avoided, will result in death or serious injury.
WARNING
WARNING indicates a hazardous situation which, if not avoided, could result in death or serious injury.
CAUTION
CAUTION indicates a hazardous situation which, if not avoided, could result in minor or moderate injury.
NOTICE
NOTICE is used to address practices not related to physical injury.
PLEASE NOTE
Electrical equipment should be installed, operated, serviced, and maintained only by qualified personnel.
No responsibility is assumed by Eliwell for any consequences arising out of the use of this material.
A qualified person is one who has skills and knowledge related to the construction and operation of electrical
equipment and its installation, and has received safety training to recognize and avoid the hazards involved.
BEFORE YOU BEGIN

Do not use this product on machinery lacking effective point-of-operation guarding. Lack of effective point-of-operation
guarding on a machine can result in serious injury to the operator of that machine.
WARNING
UNGUARDED EQUIPMENT
• Do not use this software and related automation equipment on equipment which does not have point-of-operation
protection.
• Do not reach into machinery during operation.
Failure to follow these instructions can result in death, serious injury, or equipment damage.
5 9MA10271 05/2016
This automation equipment and related software is used to control a variety of industrial processes. The type
or model of automation equipment suitable for each application will vary depending on factors such as the
control function required, degree of protection required, production methods, unusual conditions, government
regulations, etc. In some applications, more than one processor may be required, as when backup redundancy
is needed.
Only you, the user, machine builder or system integrator can be aware of all the conditions and factors present
during setup, operation, and maintenance of the machine and, therefore, can determine the automation
equipment and the related safeties and interlocks which can be properly used. When selecting automation
and control equipment and related software for a particular application, you should refer to the applicable local
and national standards and regulations. The National Safety Council’s Accident Prevention Manual (nationally
recognized in the United States of America) also provides much useful information.
In some applications, such as packaging machinery, additional operator protection such as point-of-operation
guarding must be provided. This is necessary if the operator’s hands and other parts of the body are free to
enter the pinch points or other hazardous areas and serious injury can occur. Software products alone cannot
protect an operator from injury. For this reason the software cannot be substituted for or take the place of point-
of-operation protection.
Ensure that appropriate safeties and mechanical/electrical interlocks related to point-of-operation protection
have been installed and are operational before placing the equipment into service. All interlocks and safeties
related to point-of-operation protection must be coordinated with the related automation equipment and software
programming.
NOTE: Coordination of safeties and mechanical/electrical interlocks for point-of-operation protection is outside
the scope of the Function Block Library, System User Guide, or other implementation referenced in this
documentation.
START-UP AND TEST

Before using electrical control and automation equipment for regular operation after installation, the system should
be given a start-up test by qualified personnel to verify correct operation of the equipment. It is important that
arrangements for such a check be made and that enough time is allowed to perform complete and satisfactory
testing.
CAUTION
EQUIPMENT OPERATION HAZARD
• Verify that all installation and set up procedures have been completed.
• Before operational tests are performed, remove all blocks or other temporary holding means used for shipment from
all component devices.
• Remove tools, meters, and debris from equipment.
Failure to follow these instructions can result in injury or equipment damage.
Follow all start-up tests recommended in the equipment documentation. Store all equipment documentation for
future references.
Software testing must be done in both simulated and real environments.
Verify that the completed system is free from all short circuits and temporary grounds that are not installed
according to local regulations (according to the National Electrical Code in the U.S.A, for instance). If high-
potential voltage testing is necessary, follow recommendations in equipment documentation to prevent accidental
equipment damage.
Before energizing equipment:
• Remove tools, meters, and debris from equipment.
• Close the equipment enclosure door.
• Remove all temporary grounds from incoming power lines.
• Perform all start-up tests recommended by the manufacturer.
6 9MA10271 05/2016
OPERATION AND ADJUSTMENTS
The following precautions are from the NEMA Standards Publication ICS 7.1-1995 (English version prevails):
• Regardless of the care exercised in the design and manufacture of equipment or in the selection and ratings
of components, there are hazards that can be encountered if such equipment is improperly operated.
• It is sometimes possible to misadjust the equipment and thus produce unsatisfactory or unsafe operation.
Always use the manufacturer’s instructions as a guide for functional adjustments. Personnel who have
access to these adjustments should be familiar with the equipment manufacturer’s instructions and the
machinery used with the electrical equipment.
• Only those operational adjustments actually required by the operator should be accessible to the operator.
Access to other controls should be restricted to prevent unauthorized changes in operating characteristics.
Product Related Information
WARNING
LOSS OF CONTROL
• The designer of any control scheme must consider the potential failure modes of control paths and, for certain critical
control functions, provide a means to achieve a safe state during and after a path failure. Examples of critical control
functions are emergency stop and overtravel stop, power outage and restart.
• Separate or redundant control paths must be provided for critical control functions.
• System control paths may include communication links. Consideration must be given to the implications of unantici-
pated transmission delays or failures of the link.
• Observe all accident prevention regulations and local safety guidelines.(1)
• Each implementation of this equipment must be individually and thoroughly tested for proper operation before being
placed into service.
(1) For additional information, refer to NEMA ICS 1.1 (latest edition), “Safety Guidelines for the Application, Installation, and
Maintenance of Solid State Control” and to NEMA ICS 7.1 (latest edition), “Safety Standards for Construction and Guide
for Selection, Installation and Operation of Adjustable-Speed Drive Systems” or their equivalent governing your particular
location.
WARNING
UNINTENDED EQUIPMENT OPERATION
• Only use software approved by Eliwell for use with this equipment.
• Update your application program every time you change the physical hardware configuration.
7 9MA10271 05/2016
ABOUT THE BOOK
Document Scope
This document is aimed at designers and developers and requires a knowledge of one or more IEC61131-3 stan-
dard programming languages and is designed to provide a first-level overview of the installation, functions and use
of FREE Studio.
Validity Note
This document is valid for FREE Studio (v.3.5 or greater).
The technical characteristics of the devices described in this manual also appear online.
The characteristics that are presented in this manual should be the same as those characteristics that appear online.
In line with our policy of constant improvement, we may revise content over time to improve clarity and accuracy. If
you see a difference between the manual and online information, use the online information as your reference.
Related Documents
Title of Documentation Reference Document Code
9MA10252 (EN)
FREE Advance Logic Controllers, Hardware User Manual
9MA00252 (IT)
9MA10252 (EN)
FREE Evolution - FREE Panel Logic Controllers, Hardware User Manual
9MA00252 (IT)
9MA10255 (EN)
FREE Studio software, Quick Start
9MA00255 (IT)
FREE Studio software, Programming Guide 9MA10256 (EN)
You can download these technical publications and other technical information from our website at:
www.eliwell.com
8 9MA10271 05/2016
CHAPTER 1
Introduction
1.1. Definitions
• AVD/AVC: FREE Advance

• EVD/EVC: FREE Evolution
• EVP: FREE Panel Flush mounting
• EVS ETH: ETHERNET Communication Module
• target: AVD/AVC - EVD/EVC controller
• IEC/PLC: IEC/PLC application present in the target that implements the physical resources
defined by the Analog Value, Binary Value and MultiState Value (AV/BV/MSV) objects
• SCADA: generic supervisor that communicates with the PLC via the BACNet protocol
• BIOS the part of the target firmware where the management of the BACNet protocol is
implemented.
• BACnet communications protocol (ASHRAE, ANSI, and ISO standard) for building automation
and control networks. The acronym is for Building Automation Control networks
BACnet was designed to allow building automation and control system communications in a range
of applications including HVAC, lighting control, detection systems, etc.
BACnet® is an 'open' – i.e. non-proprietary – data exchange protocol.
The BACnet® protocol provides services for computerized building automation devices to
exchange information.
BACnet is a registered trade mark of the American Society of Heating,

Refrigerating and Air-Conditioning Engineers (ASHRAE).
9 9MA10271 05/2016
1.2. Requirements
The BACnet functionalityis available in the FREE Studio workspace after version 3.5.
The development environment:
 for the programming, where the BACnet objects are available, is Application
 for the setting of the BIOS parameters is Device
The targets that support the BACnet functionality are:

• EVD (1) (with display) updated to version FW 423.22 or later
• EVC (2) (without display) updated to version FW 477.22 or later
• EVP (2) updated to version FW 489.15 or later
• AVD/AVC (1) updated to version FW 596.1 or later
(1) AVD/AVC, EVP have onboard EVS ETHERNET.
(2) need plug-in EVS ETHERNET.
1.3. Website
This document and other Application Notes are available for registered users only in the
Technical Support area of the Eliwell site @
Home > Technical Support > Programmable Controllers Area > FREE Studio > FREE Application Notes
Log in and type: http://www.eliwell.it/content.aspx?id=26663
This document and other Application Notes are available in the Eliwell site.
Available also is an example of a project created in Application.
BACnet_project_demo that includes BACnet objects.
1.4. BACnet/IP and BACnet MS/TP

The BACnet protocol guarantees full interoperability between control devices for BMS by
defining a set of simple, unambiguous rules for communication between devices made by different
manufacturers on a common platform.
The BACnet protocol defines a certain number of objects and a series of services used for BMS
communication, in which FREE Studio implements the BACnet / IP & MS/TP protocol in the
FREE Studio Application and Device work environment. The former through IP address-based
Ethernet connection (the BACnet frames will thus be the UDP/IP type); the latter trough RS485
connection.
NOTE. BACnet /IP can coexist with other AVD/AVC - EVD/EVC services / functionalities such as
WebServer TCP or binding between EVD/EVC - EVP controllers.
The profile implemented is the BACnet B-AAC, in which AVD/AVC - EVD/EVC appears as an
Application Advanced Controller (AAC).
10 9MA10271 05/2016
1.4.1. BACnet/IP profile
See also the tables below, which illustrate the profile and options implemented:
Highest conforming profile selected

Device Profile Support
from each group
Controller Profile
BACnet Building Controller (B-BC) -
BACnet Advanced Application Controller (B-AAC) X
BACnet Application Specific Controller (B-ASC) X
BACnet Smart Actuator (B-SA) X
BACnet Smart Sensor (B-SS) X
Operator Profile
BACnet Advanced Operator Workstation (B-AWS) -
BACnet Operator Workstation (B-OWS) -
BACnet Operator Display (B-OD) -
Highest conforming profile selected

Device Profile Support
from each group
Segmentation Capability
Segmentation Supported Window Size

Able to transmit segmented messages X 1476 byte/seg
Able to receive segmented messages - -
Data Link and routing Options
Router for
Data Link Supported Data Rates
Data Link
EVS ETH
BACnet/IP
EVS ETH/RS485
10/100 MBPS -
Ethernet - ISO 8802_3 - - -
MS/TP master - - -
9600, 19200,
EVS BACnet
MS/TP slave 38400, 76800 -
EVS ETH/RS485
BPS
Zigbee - - -
ARCnet - ANSI/ATA 878.1 - - -
RS-485 – ANSI/ATA 878.1 - - -
LonTalk TP/FT-10 - - -
LonTalk/IP - - -
Point-to-Point – EIA 232 - - -
Point-to-Point – modem - - -
11 9MA10271 05/2016
Other Networking Options
Networking Option Supported

Static Device Binding Supported -
Annex H, BACnet Tunneling Router over IP -
BACnet Broadcast Management Device (BBMD) -
BBMD supports registration by foreign device -
Device support registration as a foreign device X
Character Sets Supported
Character Sets Supported

ANSI X3.4 X
ISO 8859-1 X
ISO 10646 (USC-2) -
ISO 10646 (UCS-4) -
IBM / Microsoft DBCS -
JIS C 6626 -
12 9MA10271 05/2016
1.5. Network examples
AVD/AVC and EVD/EVC - BACNET IP example
CAN GS
CAN H
TM171DGRP CAN L
Power IN
GS H L
CAN POWER
Switch/Router
Ethernet
Ethernet Ethernet
Power
y 10 m
CAN GS
z 24 V CAN H
CAN L
Power IN
TM171AETH Power OUT
AI2 AI3 G + – GS GS H L
Ethernet
Analogue
inputs
RS485 CAN POWER
USB USB
NTC Sensor RH Sensor

Built-in Built-in
AI1 AI4
OK
mini mini
USB USB
BAcnet Supervisor TM172PDG42p TM171PFE03 / TM171PFE03HR TM172PDM27p TM171EP27pp

z 24 V z 24 V
48 V 48 V
AVD/AVC and EVD/EVC - BACNET MS/TP example
VALVE DRIVER
z 24 V
TM172PDG42p
OK
RS485-1 RS485-1 485GS

485 –
485 +
CAN GS
CAN H
CAN L
GS H L
CAN POWER RS485-2
INVERTER FAN DRIVER

TM171DGRP
BACnet Node
RS485-2 RS485-2
485GS
485 –
485 +
TM172PDM27p
USB
mini
USB
BACnet Supervisor BACnet Node BACnet Node BACnet Node
z 24 V
48 V
13 9MA10271 05/2016
CHAPTER 2
BACnet Objects
2.1. First Start-up
1. Click the Launch FREE Studio icon located on the Desktop

2. Click the FREE Studio Application icon.
The program appears as in the figure (for example after clicking on New Project):
You can now:You can now:

• Create a new project 'New Project ...'
• in this case choose a AVD1 target
• the numbers at the side indicate the firmware version (mask) (for example 423)
• Open an existing project 'Open project …'
• Open recent projects 'Open an existing project ...' by selecting them from a list.
The projects keep the .ppjs extension, as in the previous EVD/EVC projects2
By default, the BACnet Objects will be listed in the Resources panel, as shown in the figure:
1 the operation for AVC / EVD / EVC / EVP is completely analogous

2 for existing projects see corresponding section
14 9MA10271 05/2016
2.2. BACnet objects
BACnet defines a standard set of objects, each with a standard set of properties or attributes,
which describe the status to other devices on the BACnet network.
Via the properties, the objects can be controlled by other BACnet devices.
For example, amongst the objects there are Analog Value (analog inputs such as temperature
sensors or setpoints), Binary Value (such as relays) and Calendar for scheduling dates,
weekends and holidays.
List of default Objects in FREE Studio listed in table:
BACnet Objects table
number of
Object Description Notes / example
instances
Object that describes the properties and services
1 single instance
Device supported by the device (for example property name, 1 (1)
(1 child / leaf)
firmware version, etc.)
analog I/O, temperature
Analog Value Representation of the characteristics of an analog value
value, setpoint, etc.
Analog analog Input, temperature 0...256 (2)
Representation of the characteristics of an analog input
Input value, setpoint, etc.
Analog analog Output, temperature
Representation of the characteristics of an analog output
Output value, setpoint, etc.
Representation of a binary value, which can be only two ON/OFF relay, digital I/O,
Binary Value 0...256
distinct values TRUE/FALSE, etc.
Multistate Status of a process, day of

Representation of a vector or enumerated value, which can
the week, operating mode of
Value be an infinite number of distinct values
a device, etc.
0...32 (2)
Multi- Status of a process, day of
state Representation of a vector or enumerated input, which can
the week, operating mode of
be an infinite number of distinct values
Input a device, etc.
Assumes a Boolean value corresponding to a set or list Working days in the year,
Calendar of dates (defined as properties of the object); assumes a national and weekday 0...4
complementary value if not within these dates holidays, etc.
Assimilable with the definition of time bands: within a set of lessons schedule for a class,
Schedule dates it can assume different values on certain days of the programming of a room 0...16
week and in certain instances thermostat, etc.
Notification
Notifications to be sent to devices in the network Alarm messages to be sent 0...16
Class
(1) Number of instances There may be no instances, and therefore no 'leaf' in the object 'node'.
For the Device object, on the other hand, it is obligatory to create at least one instance, which
MUST be unique.
(2) Number of instances Analog Value+Input+Output Total ; MultistatValue+Input Total.
For the Calendar object, for example, either no instances, one instance, or a maximum of 4
different calendar instances can be defined.
15 9MA10271 05/2016
BACnet Objects are generally very complex and can also be represented by nested data
structures. Each object is managed via properties, which are also called Attributes, such as
Present_Value, Out_Of_Service_Relinquish_Default (see also the references to these and
other properties in the descriptions of the individual objects).
The Objects fields can be edited via SCADA, PLC, user interface or, more rarely, via third party
protocols.
Some of the properties of the Objects can be set as retentive (linked to the initial configuration) so
that they are held in non-volatile memory and will not be reset when the controller is switched off
(for example counters, timers).
In the Application area, complex data structures can be used to declare and allocate BACnet
Objects as well as native enumerations.
Before adding an object it is necessary to connect to the BACnet_IEC.pll library.
If the library has not been downloaded yet, the following message will appear (LH dialogue box):
select Add. To add the Library manually browse at:
<C:\Programs>\Eliwell\SoMachineHVAC\Catalog\FreeEvolution\PLC
Add Object message Add Object PLC Library
For each object it is possible to:

• Add Object add an object
• Paste Object copy3-paste an existing object
• Export all to File export an existing object
• Import from File import an existing object from file
One the library has been downloaded you can, for example, add an object (for example Calendar
object):
3 'copy' is possible when the instance has been created with Add - see below
16 9MA10271 05/2016
For each downloaded object it is possible to:
• Rename an existing object
• Delete an existing object
• Copy an existing object
• Export to File export an existing object to an XML file
Object actions Export to File Object Successfully exported
As mentioned previously, attributes can be associated to each object. Click on the object and the
properties of the object to be saved in EEPROM and/or made available via Modbus will appear in
the workspace on the right.
17 9MA10271 05/2016
BACnet Objects Object Attributes
By default, the following two attributes are always present4:

Object Attribute Description
Object_Identifier Generated automatically. 32-bit identifier linked to data / address type
Text string used in the searches broadcast by the BACnet devices
Object_Name
(used as Alias)
These properties are used to uniquely identify the object in the network.
Other properties can be set by clicking on Add.
The Filter allows you to narrow down your search with the available properties.
In the BACnet_IEC library (see Appendix), all the object properties can be viewed by clicking on
the structure name (these are easily identifiable because they are defined as Type = Structure with
all letters in UPPER CASE).
4 the BACnet protocol actually provides for 3. the third Object_Type is described below
18 9MA10271 05/2016
The image shows the attributes of the DEVICE object with the Object_Identifier attribute
highlighted:
The elements of the structure indicated in the Type column can be enumerations (arrays of
indexed values) or, in turn, structures (nested structures concept).
The Description field gives a brief description of the attribute.
For this, see either the Appendix or the BACnet_IEC libraries available in Application.
19 9MA10271 05/2016
Depending on how it is defined by the ASHRAE standard on BACnet, each object can have scores
of more or less complex attributes that can be characterised in the PLC application.
Each property has a series of fields, as described below:
field Description
Publish = True
 publishable at Modbus / CANopen level
Publish*  Address field has an automatic address
If Publish = False, the Address field will be empty and the attribute will not be
usable
Address* ModBUS address. Assigned automatically if Publish = True
Retentive property: available in RAM or saved permanently.
EEPROM = False  fixed value
= True  available space 16KBytes
Type of data used in IEC code (UINT, BOOL, etc.)
Application
Can also be an enumeration available in the BACnet_IEC library, whose de-
Type
fault value is settable in the drop-down menu
Default value
Initial value and minimum/maximum values
Min/Max
Format Display format for Default/Min/Max values
Unit Unit of Measurement
The individual properties have their read/write characteristics.
The Read only field refers to the Modbus/CANOpen side
Read only*
 = True read only
 = False read/write
*NOTE. The BACnet object elements configured as public (Publish = True) are displayed in FREE
Studio Device; they will have their own Modbus Address and will be R/W, according to the Read
Only field.
They are also displayed in the project's .parx (to be used in FREE Studio UI), in the same way as
Status Variables and EEPROM Parameters. These elements are thus viewable on the graphic
display of the base or on a terminal.
Also, the public elements of a project can be used in the same BACnet object as correlated Min
and Max values of other elements, attributes of the same object (for example Low_Limit, High_
Limit).
The range of Modbus/CANOpen addresses in the event of the publishing of a BACnet element is
the set of available Status Variables + EEPROM Parameters addresses.
20 9MA10271 05/2016
Example of object where the Publish/Address, EEPROM and Default Value fields are highlighted
If Publish = False, the Address field will be empty and the attribute will not be usable as public.
The defined BACnet objects are allocated to the related vectors of structures defined for each type
of object. The vectors are available in the BACnet_vars library.
An object can be used in the IEC code via the name of the object:
SETPOINT.Present_Value
or else via the related vector:
sysBACnet_AV[i].Present_Value
The vector addressing index i is a function of the order the objects are defined in:
• i = 0 for SETPOINT
• i = 1 for Temperature
21 9MA10271 05/2016
2.2.1. DEVICE object
The Device object is the only object that MUST always be present in a BACnet project
If it is not present, there will be a compilation error.
By default, as described previously, the following two attributes are always present:
Object_Identifier, Object_Name
For this object only, editable fields are available:

Subnet, Node Number: using these values the Default Value column in Object_Identifier will
uniquely identify the DEVICE object in the network of devices.
Other properties can be either set by clicking on Add or removed with Remove.
Example: as well as the two default properties, it is presumed that Vendor_Name and/or Vendor_
Identifier will be added5. If not specified, the Vendor_Identifier value is 10.
In this case, the name will be a string, with a fixed, non-visible/available value for reading via
Modbus. A more complete example can be seen in the Analog Value object described below.
5 Vendor_Name and Vendor_Identifier are released by bacnet.org: Eliwell has the number 10 (FREE
Studio default)
22 9MA10271 05/2016
2.2.2. ANALOG VALUE object
The Analog Value object is generally a RAM variable and can be an example of an analog value
such as a temperature and/or Setpoint. In addition to the two (highlighted) default properties,
always present and not removable, other attributes can be added using the Add key, as described
previously.
In the Type drop-down menu Analog Value object can be defined either as an Analog Input,
Analog Output o Analog Value-type in the BACnet or PLC environment.
This distinction corresponds to different ways of managing the data structure by the EVD/EVC
BIOS: if the object is the Input type, the Present_Value is writeable as an IEC code, whereas in
the other two cases it is calculated on the basis of the Relinquish_Default and Priority_Array
properties.
Analog Input example: Temperature.Present_Value := TO_REAL(AI1)/10;

Analog Value example: SETPOINT.Relinquish_Default := overridden_value;
23 9MA10271 05/2016
The updating of the Present_Value occurs via the function call sysBACnet_AV_PresentValue:
realRet := sysBACnet_AV_PresentValue(ADR(SETPOINT));
Management of alarm states and conditions

The BACnet objects Analog Value, Binary Value and Multi State Value contain the following
properties implemented on the target for managing the alarm states and conditions:
• Out Of Service
• Reliability
• Event State
• Status Flags
NOTE. The resources events management is always active, independently of whether any
Notification Objects have been defined; therefore, variations in the status of each object can be
managed dynamically at one-second intervals.
Also, the management of the states leads to the different management of the data structure by the
EVD/EVC BIOS if the Analog Value object is defined as an Input, Output value or a Value type.
Management of Overridden Status

The Overridden flag of the Status Flags property is controlled by the PLC.
If set to TRUE, the behaviour is similar to the Out Of Service=TRUE situation.
The only difference is that notifications, if any, are not inhibited.
24 9MA10271 05/2016
Analog Input
Reliability Attribute
The property assumes the following set values in the following conditions:
• NO_SENSOR: if the Present Value property assumes the value

-32768 | 3276.8 | 327.686 (generic probe error).
• UNRELIABLE_OTHER: if the Present Value property assumes the value
-32767...-32760 | -3276.7...-3276.0 | -327.67...327.607 (communication error with an I/O
expansion).
• NO_FAULT_DETECTED in all other cases.
A value other than NO_FAULT_DETECTED automatically implies that FAULT flag setting in the
Status Flag property is TRUE.
Analog Output
The value of this property is set by the PLC.
Events management (always active) does not modify the value of this property.
The events management system has the task of updating the value of the Status Flags property –
the FAULT flag only – depending on the value of the Reliability property.
6 See Controller Data Types

7 Idem. See Note 6 above
25 9MA10271 05/2016
2.2.3. BINARY VALUE object
The Binary Value object is normally used for RAM variables representing Boolean values such as
relay ON/OFF states.
In addition to the two default properties Object_Identifier / Object_Name, always present and not
removable, other attributes can be added using the Add key, as described previously.
In the Type drop-down menu Binary Value object can be defined in PLC environment, as an
Binary Input, Binary Output or Value-type. In the BACnet environment they are set as Binary
Value.
Binary Output case with relinquish default calculation
IF Temperature.Present_Value > SETPOINT.Present_Value THEN

Relay.Relinquish_Default := BINARY_ACTIVE;
ELSE
Relay.Relinquish_Default := BINARY_INACTIVE;
END_IF;
As with Analog Value, the Present_Value will be updated via the sysBACnet_BV_PresentValue
function call:
BinaryPVRet := sysBACnet_BV_PresentValue(ADR(Relay));
The relay output update will be given by
DO1 := TO_BOOL(Relay.Present_Value);
Event State Attribute

See Analog Input.
26 9MA10271 05/2016
2.2.4. MULTI STATE VALUE object
The Multi State Value object can vary within a finite number of distinct values, for example a
process status or a day of the week.
It is normally used for enumeration-type variables representing multiple states such as HEAT/
COOL/OFF8, defrost cycles (request, start, duration, dripping, etc.)
In addition to the two default properties Object_Identifier / Object_Name, always present and not
removable, other attributes can be added using the Add key, as described previously.
In the Type drop-down menu Multi State Value object can be defined in BACnet and PLC
environment a Multistate Input o Value-type object. Difference between Multistate Value and
Multistate Output is valid in PLC environment only.
Example:
In the example the multiple state = 2

The property that defines the number is Number_Of_States
The properties that define the values are:
State_Text[1].text
State_Text[2].text
At IEC livello:
Machine_State.Relinquish_Default:=2;(*Chiller ON*)
Machine_State.State_Text[0].text := 'Chiller OFF';
Machine_State.State_Text[1].text:= 'Chiller ON';
where Machine_State is the name of the object.
Event State Attribute

See Analog Input.
8 example: multiple state =3; the multiple state can also be binary, i.e. = 2
27 9MA10271 05/2016
2.2.5. CALENDAR object
The Calendar object, as implied by the name, defines a set of dates.

The following can actually be defined:
• a single date (a day)
• an interval of consecutive dates/days (a week, a month, ...)
• days that repeat in a cycle (first Monday of the month, every Saturday, every weekend, ...)
The Calendar is normally a static object.

Its present value has the Boolean value TRUE if the current date (determined by the device's RTC
settings) is within the set of dates defined in the object itself; otherwise the present value is FALSE.
In the example, a Holiday calendar is created.
NOTE. A maximum of 4 (instances of) different calendars can be created.
The Calendar object attributes can be nested structures:
Example. The DateList Type is BACnetCalendarEntry:
28 9MA10271 05/2016
BACnetCalendarEntry, in turn, is made up structures: BACnetDate, BACnetDateRange,
BACnetWeekNDay (date, dates interval, week of the month):
The structures, in turn, contain the following elements:

BACnetDate is the date, made up of the year, month, day and day of the week.
BACnetDateRange is the dates interval:
Finally, BACnetWeekNDay is the week of the month, made up of the month, week of the month
and day of the week.
29 9MA10271 05/2016
2.2.6. SCHEDULE object
The Schedule Objects (Sc) define the planning of the actions to be carried out in a certain dates
interval, with a possible weekly recurrence and with possible exceptions, which can be defined
either with single dates or via a Calendar.
Depending on the current date and time, the present value of the Schedule can assume variable
values as defined in the properties of the object itself.
BACNET_SCHEDULE is a complex nested structure:

The image shows the attributes of the Sc object with the Object_Identifier attribute highlighted
In the example a scheduler has been created that uses the most complex attributes available: the
Weekly_Schedule attribute is a nested array (vector size 7, for the days of the week) containing
enumerations (hours, minutes, seconds)
Amongst these there are the properties Effective and Exceptions.

The exceptions are managed by the scheduler and not the calendar; for example the definition of
the events that are inactive at weekends (Saturday/Sunday) is set in the Scheduler and not by the
Calendar.
NOTE. The Schedule object doesn't necessarily use a Calendar in order to function.
It is merely an option, for defining the Exception_Schedule field.
30 9MA10271 05/2016
In fact, the scheduler is recursive, i.e. not a static structure.
Effective_Period property
The Schedule Objects in the example is valid for the whole of the year 2013, i.e. from 01/01/13 to
31/12/13
The SC1 BACnet Schedule object is linked to ScState, a Binary Value Object with object-identifier
20971521. It can assume the two Boolean values:
1=Active (BINARY_ACTIVE) and 0 = Inactive (BINARY_INACTIVE).
Weekly_Schedule defines the days of the week: the working days are Monday (Weekly_
Schedule[0]), Tuesday (Weekly_Schedule[1]),..., Friday (Weekly_Schedule[4]).
Binary Value Object  Present _Value = BINARY_INACTIVE
SC1 BACnet Schedule Object  Present _Value = BINARY_INACTIVE
The Present-value (85) with priority 16 of the Binary_Value object indicated will be set to Active
from 8 in the morning to 5 in the afternoon, and inactive – both outside the indicated schedule and
for the weekend – for all of the Saturday (Weekly_Schedule[5]) and all of the Sunday (Weekly_
Schedule[6]).
31 9MA10271 05/2016
Exception_Schedule property
The exceptions, with reference to what was defined previously, are managed with the Exception_
Schedule attribute (Exception_Schedule[0]); the calendar period is taken (Exception_Schedule[0].
period.calendarReference) which has object-identifier 25165824 and for all the days of the year
(from 00:00 every single day) the binary variable (object-identifier 20971521) will be set to inactive.
Binary Value  ObjectIdentifier = 20971521
Calendar  ObjectIdentifier = 25165824
Schedule  attributes summary
32 9MA10271 05/2016
The screenshot shows the Effective properties that determine the beginning and end of the
scheduler associated to the calendar and Weekly_Schedule, i.e. the days of the week
For example, to enter the Effective_Period click on Add; the BACnet object attributes window
opens (on the left below); select Effective_Period.
The window shown on the right opens: press All to enter all the items that make up the startDate
in the table:
The single items will be valorized in the Default valuecolumn.

Next, see the setting example for the month of January (Jan):
Effective_Period.startDate.month  1 = Jan
33 9MA10271 05/2016
2.2.7. NOTICATION CLASS object
The Notification Class (NC) object contains a list of devices to which notifications of messages
and/or alarms are sent on the basis of certain events defined in the Analog Value, Binary Value,
and Multi State Value objects.
The intrinsic reporting characterises this object like the previous ones: in this case, each event is
associated to an action, and the notification class describes where and how the chosen message
will be sent.
NOTE. Different EVD/EVC in the network do not exchange messages, or rather the notifications
are sent to SCADA devices which can then send messages to Evolution.
BACNET_NOTIFICATION, like those described previously, is a complex nested structure

The image shows the attributes of the NC object with the Recipient_List attribute that contains the
list of devices highlighted:
Recipient_List is of the complex BACnetDestination type which, in turn, as shown in the figure,
is a complex nested structure
BACnetDestination : STRUCT
validDays : BACnetDaysOfWeek;
fromTime : BACnetTime;
toTime : BACnetTime;
recipient : BACnetRecipient;
processIdentifier : UDINT;
issueConfirmedNotifications : BOOL;
(*transitions : BACnetEventTransitionBits;*)
transitions : ARRAY[0..2] OF BOOL; { DE:"position 0 for to_offnormal,
position 1 for to_fault, position 2 for to_normal" } END_STRUCT;
34 9MA10271 05/2016
NOTE. The 'notification' is generated by objects such as Analog Value, Binary Value, etc. and not
by the correlated Notification Class object.
In fact, the indicated objects contain properties that activate the notification, such as
• Limit_Enable[0], Limit_Enable[1]
• Event_Enable[0],Event_Enable[1],Event_Enable[2],
• Notification_Class
In the examples, an Analog Value (Temperature) object instance has been created
The indicated attributes have been added to the object
• Limit_Enable[0]
• Limit_Enable[1]
• Event_Enable[0]
• Event_Enable[1]
• Event_Enable[2]
• Notification_Class
35 9MA10271 05/2016
The Notification Class (NC) object, as mentioned previously, will contain the list of devices to
which notifications will be sent in a specific interval.
In the example, the valid days of the week

validDays : BACnetDaysOfWeek
are all 7 (1111111 binary = 7 decimal)
The period of validity

fromTime : BACnetTime;
toTime : BACnetTime;
goes from 0 to 23 hours
fromTime.hour
from 0 to 59 minutes
fromTime.min
and from 0 to 59 seconds
fromTime.sec
(i.e. all day)

36 9MA10271 05/2016
2.3. FREE Studio Device
As well as the Application environment, the Device working environment is used, where
the parameters of the PLC application will be present and, amongst the BIOS parameters,
a dedicated BACnet file.
Menus
On the Application Resources panel, menus can be created that will count the attributes defined
via the objects with PUBLISH = True.
The attributes are added to the menu with the Add key, selecting them from a drop-down list.
The example shows the created menus (AV, Analog Value; BV, Binary Value, etc.) and the AV
menu attributes where the various attributes are added.
In FREE Studio Device the attributes will be displayed and will include the Modbus address
(Address column). Attributes set as read only (in grey) will not be editable:
37 9MA10271 05/2016
BACnet FREE Studio Device Parameters
As well as the Application environment, the Device working environment is used, where a
BACnet file will be present amongst the BIOS parameters.
The file will contain two parameters:
BACnet Description
With the next startup, load the default values for the BACnet
Load_BACnet_E2_Defaults
parameters in EEPROM
BACnet/IP port number: default 47808
Port_BACnet_IP
(0 equals 47808)
The BACnet file is displayed as the last of the BIOS parameters:
Combined use of the parameter Load_BACnet_E2_Defaults BACNET.DAT file
The Load_BACnet_E2_Defaults parameter makes it possible to establish whether, when the

instrument resets, the retentive BACnet elements (declared as EEPROM=True) have to be
reinitialised to the project default value or read by EEPROM at the values they were when saved
before the reset and loaded into RAM (to be used by the PLC).
Load_BACnet_E2_Defaults = True  all the retentive elements will be rewritten in EEPROM with
the default values and subsequently loaded into RAM.
Load_BACnet_E2_Defaults = False  the retentive elements will be loaded into RAM by
EEPROM, keeping the value they had before the reset.
The Load_BACnet_E2_Defaults parameter is automatically reset to False after being used,

so that the resetting to the default values needs to be done only once.
38 9MA10271 05/2016
Also, in a project file, the application automatically generates the BACNET.DAT file which contains
the reference and default value for all the configured BACnet elements in text format.
The file can then be edited and may contain just one limited set of elements, whose default value is
to be managed. This allows a EVD/EVC/EVD/EVC Flush user or installer to edit the default value
declared in the Application project, without having to edit and recompile the project.
• The BACNET.DAT file must be loaded beforehand in the EVD/EVC/EVD/EVC Flush flash
memory.
• All the BACnet elements listed in the file, regardless of whether or not they are retentive, will be
rewritten in RAM at the value indicated in the file at every switching on or at every unloading of the
PLC after a "rebuild-all" command.
Below is a table summarising the functioning in a reset due to the combined action of the
parameter and the file.
When the device Load_BACnet_E2_Default Load_BACnet_E2_Default

is reset... FALSE TRUE
to perform independentely on
Load_BACnet_E2_Default = TRUE/FALSE
Step 1
Initializes BACnet structure objects
where present Out_Of_Service field is set to TRUE
… the default values of the
non‑retentive BACnet elements … the default values of the
are loaded into RAM retentive & non‑retentive BACnet
(EEPROM=FALSE) elements are loaded into RAM
Step 2 … the default values of the as defined in the project.
retentive BACnet The retentive elements in
elements are loaded into RAM EEPROM are rewritten at the
(EEPROM=TRUE) project default values.
The initial values specified in the

BACNET.DAT file are loaded
Step 3
The initial values specified into RAM.
in the BACNET.DAT file are
to perform only if overwritten in RAM, if and only if Also, the initial values specified
they are non-retentive. in the BACNET.DAT file are
(EEPROM=FALSE) overwritten in EEPROM if and
BACNET.DAT file present
only if they are retentive.
(EEPROM=TRUE)
Load_BACnet_E2_Default
Step 4 ---
is set to FALSE
39 9MA10271 05/2016
; SETPOINT.Object_Name
4="AV1"
; SETPOINT.Description
44="SETPOINT"
; SETPOINT.High_Limit
304=210.0
; SETPOINT.Low_Limit
308=-100.0
; SETPOINT.Units
92=62
Port_BACnet_IP
The value of the port for the BACnet + service is editable from the second parameter of the
BACnet file Port_BACnet_IP
If Port_BACnet_IP = 0 the value used for the port is the default BACnet corresponding to 47808
(0xBAC0 hex).
PASSIVE ETHERNET PLUGIN – BACNET/IP

The BACnet/IP network can have a device that has the function of a Gateway or BACnet/router to
be configured for EVD/EVC/EVD/EVC Flush (known IP address, see example).
ETHERNET – BACNET/IP
ETHERNET plugin passive – BACNET/IP
40 9MA10271 05/2016
The ETHERNET passive plug-in configuration parameters provide for the configuration of the
Modbus TCP/IP communication port (for example 502), the IP address, the gateway and the
subnet mask
The 'Default Gateway' and 'Net mask' parameters are of no significance in the local point-to-point
network.
For connections via a router the 'Default Gateway' parameters must match the IP address, as in
the following example:
AVD/AVC settings EVD/EVC settings

DefGtwy_1_ETH_PI Default Gateway (part 1) 10 192
RS485 PLUGIN PASSIVE – BACNET MS/TP

BACnet/IP is enabled as default standard as decribed above.
NOTE: BACNET IP and BACnet MS/TP cannot be performed concurrently.
AVD/AVC
If the application performed in AVD/AVC allows Bacnet objects, MS/TP is enabled only if:
• parameter Proto_RS485_OB1 is set to 4=BACnet MS/TP
or
• parameter Proto_RS485_OB is set to 4=BACnet MS/TP
or
• plugin EVS BACnet is available and
• parameter Proto_RS485_PI is set to 4=BACnet MS/TP
NOTE: BACnet MS/TP can be enabled on one 485 port only. For multiple ports enabling by
parameter foloowing priority shall be considered: RS485-1, RS485-2, RS485 Plugin Passive.
41 9MA10271 05/2016
BACnet MS/TP as Slave
parameter value notes

if Addr_RS485_OB1 >127
Proto_RS485_OB1 Default Modbus/RTU 4=BACnet MS/TP
as Slave
if Addr_RS485_OB >127
Proto_RS485_OB Default Modbus/RTU 4=BACnet MS/TP
as Slave
if Addr_RS485_PI >127
Proto_RS485_PI Default Modbus/RTU 4=BACnet MS/TP
as Slave
BACnet MS/TP as Master
Device Object property fixed value notes

64 max-master 1 read only
63 max-info-frames 127 read only
EVD/EVC
BACnet/IP is enabled as default standard as decribed above.
If the application performed in AVD/AVC allows Bacnet objects, MS/TP is enabled only if:
• one plugin choosen from EVS Bacnet / EVS ETH/RS485 is available
• parameter Proto_RS485_PI is set to 4=BACnet MS/TP
value
Proto_RS485_PI Default Modbus/RTU 4=BACnet MS/TP
• related 485 serial line is not set as Master from Connection environment
42 9MA10271 05/2016
2.3.1. EDE file
In order to make the configured objects available to the SCADA BACnet supervisor, it will be
necessary to generate the EDE (Engineering Data Exchange) file in .CSV format
The EDE file is not generated automatically but has to be created using the drop-down menu
Developer > Generate EDE files > and saved in the PC project directory.
43 9MA10271 05/2016
2.3.2. Management of pre-existing projects
All projects created with previous versions of FREE Studio 3.5 can be upgraded to the latest
available target to allow the creation of BACnet objects.
To make the existing BACNet project compatible with a minimum number of changes, proceed as
follows:
• create the requested BACnet objects
• keep the pre-existing variable parameter or status aligned with the corresponding EEPROM
resource
Below is an example of the management (alignment) of an EEPROM parameter (EE_Setpoint) and a

variable status (StatusVar), both whole and with format XXX.Y.
Given an existing project, two new Analog Value objects have to be created from the Resources
panel.
Analog Value BACnet Object Type Note

AV_EQ_EE_Setpoint Analog Value aligned with EE_Setpoint
AV_EQ_StatusVariable Analog Input aligned with StatusVar
The properties that need to be defined – other than the default ones – for the two objects are as
follows
Properties AV_EQ_EE_Setpoint AV_EQ_StatusVariable Note

Relinquish_Default - x
Present_Value x x
default TRUE,
Out_Of_Service x x
set to FALSE
by default, Out_Of_Service is set to TRUE: simply instruct the SCADA to take on the value to be
written in the object. Set to FALSE to use the PLC value.
In the example defined by the project, available on the Web:
Program AlignEE keeps the relinquish_default and the pre-existing parameter aligned.
Program AlignSV copies the value of the variable status into the object's Present_Value.
In the example defined by the project, available on the Web:
44 9MA10271 05/2016
Program AlignEE keeps the relinquish_default and the pre-existing parameter aligned
Program AlignSV copies the value of the variable status into the object's Present_Value
45 9MA10271 05/2016
CHAPTER 3
Libraries
Indicated below are the BACnet functions available in the Library > Target blocks sec-
tion of FREE Studio Application as described in FREE Studio.
3.1. BACnet_IEC
The BACnet_IEC library contains functions, enumerations and structures.
3.2. Functions
The functions return the Present Value of the object instance, as defined in the table:
Function Object Input Return Value

sysBACnet_AV_ Analog
ADR of Analog Value Object instance REAL
PresentValue Value
BACnetBinaryPV:
sysBACnet_BV_ 0=BINARY_
Binary Value ADR of Binary Value Object instance
PresentValue INACTIVE
1=BINARY_ACTIVE
sysBACnet_Ca_
Calendar ADR of Calendar Object instance BOOL
PresentValue
sysBACnet_MV_ Multi State
ADR of MultiState Object instance UDINT
PresentValue Value
Any BACnet ADR of BACnet field stored into
field EEPROM
sysBACnet_WriteE2Par USINT
stored into ADR of variable containing the new
EEPROM value to be written
The function sysBACnet_BBMD set-up Foreing Devices Handling, as defined in the table:
Function to set-up Foreing Devices Handling.
Return value: BOOL. Return always TRUE.
Function Input Type Description

ip_1 USINT 1 st part of Ip address of the BBMD
ip_2 USINT 2 nd part of Ip address of the BBMD
ip_3 USINT 3 rd part of Ip address of the BBMD
sysBACnet_BBMD
ip_4 USINT 4 th part of Ip address of the BBMD
port UINT Port of the BBMD
tmo UINT Underflow timeout in seconds [0...65535]
46 9MA10271 05/2016
3.3. Enumerations
The enumerations are arrays of values (for example BACnetBinaryPV).
Structures
The structures are associated to the Objects and easily identifiable because they are defined as
Type = Structure in all UPPER CASE letters (for example BACNET_DEVICE)
Click on the individual structure to view the properties of the object.
Example: BACNET_CALENDAR (all UPPER CASE):
The object type too can be a structure, for example BACnetCalendarEntry
The structure can be nested, i.e. it can contain elements formed by other structures, for
example BACnetDate
47 9MA10271 05/2016
3.3.1. BACnet_IEC vars
The BACnet_IEC vars library contains:
1) the BACnet objects

The size of the vectors is given between square brackets.
The maximum number of available instances is described in the BACnet Objects Table.
Function Type Object

sysBACnet_AV ARRAY[0..255] OF BACNET_ANALOG_VALUE Analog Value Object
sysBACnet_BV ARRAY[0..255] OF BACNET_ANALOG_VALUE Digital Value Object
sysBACnet_Ca ARRAY[0..3] OF BACNET_CALENDAR Calendar Object
sysBACnet_De BACNET_DEVICE Device Object
sysBACnet_ ARRAY[0..31] OF BACNET_MULTI_STATE_
Multi State Value Object
MV VALUE
ARRAY[0..15] OF BACNET_NOTIFICATION_
sysBACnet_NC Notification Class Object
CLASS
sysBACnet_SC ARRAY[0..15] OF BACNET_ANALOG_VALUE Schedule Object
2) the two Device variables described previously:
sysLoadBACnetE2Defaults Enable flag to write default values in EEPROM

Port_BACnet_IP BACnet/IP Port number (default 47808, 0 equals to 47808)
3) the whole variable on the status of the operation on the BACnet file:
Status of operation on BACnet file

0 = command completed
1 = at least one element has its address not in DataBase
sysBACnetFileStatus
2 = at least one element has not be written (write fail)
3 = at least one element has its type not handled
255 = file not present
4) the whole variable on the device reinit:
it is set 1 or 2 by DM-RD-B command and must be set to 0

by PLC application
sysBACnet_ReinitDevice 0 = Idle
1 = WARMSTART
2 = COLDSTART
NOTE: sysBACnet_ReinitDevice is a reinit request; implementation is defined by the application
developer.
48 9MA10271 05/2016
CHAPTER 4
APPENDIX - B-AAC PROFILE
Described below are the functions available with the B-AAC (Application Advanced Controller)
profile implemented in FREE Studio.
Interoperability
Building Block
mandatory for B-AAC
DS-RP-B x
Data Sharing (object access functions) BIBBs
DS-WP-B x
AE-N-I-B x
Alarm & Event Management BIBBs AE-ACK-B x
AE_INFO-B x
Scheduling BIBBs SCHED-I-B x
DM-DDB-B x
DM-DOB-B x
Device and Network Management BIBBs
DM-DCC-B x
DM-TS-B -
Trends - -
ReadProperty (DS-RP-B)
This function enables a client to ask for a property of an object from the server.
BACnet Service Initiate Execute

ReadProperty (DS-RP-B) x
ReadPropertyMultiple
This function is identical to the ReadProperty function, but the properties of several objects can be
read with a demand (in Schneider porting restriction is applied to APDU maximum size provided by
Ethernet, approx. 1500 bytes).
WriteProperty (DS-WP-B)
This function enables a client to write values into the properties of an object.

WriteProperty (DS-WP-B) x
WritePropertyMultiple
This function is identical to the WriteProperty function, but the properties of several objects can be
written with a demand.
49 9MA10271 05/2016
Alarm & Event Management BIBBs
(AE-N-I-B) Device B generates notifications about alarms and other events.
(AE-ACK-B) Device B processes acknowledgments of previously transmitted alarm/event
notifications.

Alarm & Event Management BIBBs (AE-N-I-B) x
Alarm & Event Management BIBBs (AE-ACK-B) x
Scheduling-Internal-B (SCHED-I-B)
The B device provides date and time scheduling of the values of specific properties of specific
objects within the device. In addition to supporting the DS-RP-B and DS-WP-B BIBBs, each device
claiming conformance to SCHED-I-B shall also possess at least one Calendar and one Schedule
object. Devices claiming conformance to SCHED-I-B shall also support DM-TS-B.
Device Management-Dynamic Device Binding-B (DM-DDB-B)

The B device provides information about its device attributes and responds to requests to identify
itself.

Who-Is x
I-Am x
Device Management-Dynamic Object Binding-B (DM-DOB-B)

The B device provides address information about its objects upon request.

Who-Has x
I-Have x
Device Management-DeviceCommunicationControl-B (DM-DCC-B)

The B device responds to communication control exercised by the A device. Support for requests
of a limited duration is required, and support for requests of an indefinite duration is optional.
Device Management-TimeSynchronization-B (DM-TS-B)

The B device interprets time synchronization messages from the A device.

TimeSynchronization x
50 9MA10271 05/2016
CHAPTER 5
BACnet Interoperability Building Blocks Support
BACnet Interoperability Building Blocks (BIBBS) Support
5.3.1. Data Sharing
BACnet standard
Eliwell
B-OWS
B-AWS
B-AAC
B-ASC
B-OD
B-BC
B-SA
BIBBS description
B-SS
DS-RP-A ReadProperty-A X X X X
DS-RP-B ReadProperty-B X X X X X X X X X
DS-RPM-A ReadPropertyMultiple-A X X X
DS-RPM-B ReadPropertyMultiple-B X X X
DS-RPC-A ReadPropertyConditional-A
DS-RPC-B ReadPropertyConditional-B
DS-WP-A WriteProperty-A X X X X
DS-WP-B WriteProperty-B X X X X X
DS-WPM-A WritePropertyMultiple-A X X
DS-WPM-B WritePropertyMultiple-B X X X
DS-COV-A COV-A
DS-COV-B COV-B X
DS-COVP-A COVP-A
DS-COVP-B COVP-B
DS-COVU-A COV-Unsolicited-A X
DS-COVU-B COV-Unsolicited-B X
DS-V-A View-A X X
DS-M-A Modify-A X X
DS-AV-A Advanced View-A X
DS-AM-A Advanced Modify-A X
51 9MA10271 05/2016
5.3.2. Alarms and Events
BACnet standard
Eliwell
B-OWS
B-AWS
B-AAC
B-ASC
BIBBS description
B-OD
B-BC
B-SA
B-SS
AE-N-A Notification-A X X
AE-N-I-B Notification Internal X X X
AE-N-E-B Notification External-B
AE-ACK-A ACK-A X X
AE-ACK-B ACK-B X X X
AE-ASUM-A Summary-A
AE-ASUM-B Alarm Summary-B
AE-ESUM-A Enrollment Summary-A
AE-ESUM-B Enrollment Summary-B X X
AE-INFO-A Information-A X
AE-INFO-B Information-B X X
AE-LS-A LifeSafety-A
AE-LS-B LifeSafety-B
AE-AS-A Alarm Summary-A
AE-VN-A View Notification-A X X
AE-VM-A View Modify-A X
AE-AVM-A Advanced View Modify-A X
Advanced View
AE-AVN-A X X
Notifications-A
AE-ELVM-A - 1
1 Not required for devices conformance to a Protocol Revision less than 7
5.3.3. Schedules
BACnet standard
Eliwell
B-OWS
B-AWS
B-AAC
B-ASC
BIBBS description
B-OD
B-BC
B-SA
B-SS
SCHED-A Scheduling - A
SCHED-B
SCHED-I-B Scheduling - Internal-B X X
SCHED-E-B Scheduling - External-B X
SCH-VM-A Scheduling - View Modify X
Scheduling - Advanced
SCH-AVM-A X
View Modify
Scheduling - Weekly
SCH-WS-A
Schedule-A
Scheduling - Weekly
SCH-WS-I-B
Schedule Internal-B
SCH-R-B Scheduling - Readable-B
52 9MA10271 05/2016
5.3.4. Trends
BACnet standard
Eliwell
B-OWS
B-AWS
B-AAC
B-ASC
BIBBS description
B-OD
B-BC
B-SA
B-SS
Viewing and Modifying
T-VMT-A
Trends-A
T-VMT-I-B X
Trends Internal-B
T-VMT-E-B
Trends External-B
Automated Trend
T-ATR-A
Retrieval-A
Automated Trend
T-ATR-B X
Retrieval- B
T-V-A View-A X
T-A-A Archiving-A
T-AVM-A - X
5.3.5. Device Management
BACnet standard
Eliwell
B-OWS
B-AWS
B-AAC
B-ASC
BIBBS description
B-OD
B-BC
B-SA
B-SS
DM-DDB-A Dynamic Device Binding - A X X X X
DM-DDB-B Dynamic Device Binding - B X X X X X X 2 2 X
DM-DOB-A Dynamic Object Binding - A X
DM-DOB-B Dynamic Object Binding - B X X X X X X 2 2 X
DM-DCC-A DeviceCommunicationControl-A X
DM-DCC-B DeviceCommunicationControl-B X
DM-PT-A Private Transfer-A
DM-PT-B Private Transfer-B
DM-TM-A Text Message-A
DM-TM-B Text Message-B
DM-TS-A TimeSynchronization-A
DM-TS-B(*) TimeSynchronization-B X X X(*)
DM-UTC-A UTCTimeSynchronization-A
DM-UTC-B(*) UTCTimeSynchronization-B X X (*)
DM-RD-A ReinitializeDevice-A X
DM-RD-B ReinitializeDevice-B X X X
DM-BR-A Backup and Restore-A X
DM-BR-B Backup and Restore-B X
DM-R-A Restart-A
DM-R-B Restart-B
53 9MA10271 05/2016
BACnet standard
Eliwell
B-OWS
B-AWS
B-AAC
B-ASC
BIBBS description
B-OD
B-BC
B-SA
B-SS
DM-LM-A List Manipulation-A
DM-LM-B List Manipulation-B
Object Creation and
DM-OCD-A X X
Deletion-A
Object Creation and
DM-OCD-B
Deletion-B
DM-VT-A Virtual Terminal-A
DM-VT-B Virtual Terminal-B
DM-ANM-A - X
DM-ADM-A - X
DM-MTS-A - X X
2 Not required if the device is a BACnet MS/TP Slave
(*) for B-AAC profile only one is required
5.3.6. Network Management
BACnet standard
Eliwell
B-OWS
B-AWS
B-AAC
B-ASC
BIBBS description
B-OD
B-BC
B-SA
B-SS
NM-CE-A Connection Establishment- A X X
NM-CE-B Connection Establishment- B
NM-RC-A Router Configuration-A
NM-RC-B Router Configuration-B
54 9MA10271 05/2016
5.3.7. Supported BACnet Object Types
Summary
Protocol
BACnet standard Eliwell
Revisions
Protocol Rev
Introduced
Createable
Deletable
Supported
Updated
B-AWS
ID description
B-OWS
B-AAC
B-ASC
B-OD
B-BC
B-SA
B-SS
23 Accumulator 4 X
0 Analog Input 0 X Y Y
1 Analog Output 0 X Y Y
2 Analog Value 0 1 X Y Y
18 Averaging 1 X
3 Binary Input 0 1 X
4 Binary Output 0 X
5 Binary Value 1 X Y Y
6 Calendar 0 X X Y Y
7 Command 0 X
8 Device 0 1 X X X X X X X X Y Y
9 Event Enrollment 0 4 X X X X
10 File 0 1, 9 X
11 Group 0 X
21 Life Safety Point 2 4, 5 X
22 Life Safety Zone 2 4, 5 X
12 Loop 0 7 X
13 Multi-state Input 0 1 X Y Y
14 Multi-state Output 0 X
19 Multi-state Value 1 1 X Y Y
15 Notification Class 0 1, 4 X X X X Y Y
16 Program 0 X
24 Pulse Converter 4 X
17 Schedule 0 1, 4 X X X X Y Y
20 Trend Log 1 7 X X X
30 Access Door 6 X
25 Event Log 7 X
28 Load Control 6 X
29 Structured View 5 X
27 Trend Log Multiple 7 X
Lighting Output2 9i
Access Credential 9 X
Access Point 9 X
Access Rights 9 X
Access User 9 X
Access Zone 9 X
55 9MA10271 05/2016
Supported BACnet Object Types (Summary continued)
Protocol
BACnet standard Eliwell
Revisions
Protocol Rev
Introduced
Supported
Createable
Deletable
Updated
ID description
B-OWS
B-AWS
B-AAC
B-ASC
B-OD
B-BC
B-SA
B-SS
37 Credential Data Input 9 X
38 Global Group2 9p
39 CharacterString Value2 9w
40 DateTime Value2 9w
41 Double Value2 9w
42 BitString Value2 9w
43 OctetString Value2 9w
44 Time Value2 9w
45 Singed Value2 9w
46 Unsigned Value2 9w
47 Date Value2 9w
1
Implied requirements of Device Profile are in respect to the protocol revision support by the device.
If the object type did not exist in the BACnet standard for the revision supported by the device it is not required.
2
Object types proposed for ASHRAE standard by SSPC 135 committee but not currently approved
56 9MA10271 05/2016
5.3.8. Device Object - FREE Studio
BACnet Standard – Device Eliwell PLC
Readable
Optional
Required
Required
Writable
Readble
Writable
WRITE
READ
ID BACnet property name Notes
75 object-identifier R R W y no
77 object-name R R W y y
79 object-type R R y no
112 system-status R R W y y
121 vendor-name R R W y y
120 vendor-identifier R R W y y
70 model-name R R y y
44 firmware-revision R R y y
application-software-
12 R R y y
version
58 location O - -
28 description O - -
98 protocol-version R R y no
139 protocol-revision R R y no
protocol-services-
97 R R no no
supported
protocol_object-types-
96 R R no no
supported
76 object-list R R no no
209 structured-object-list O - -
62 max-apdu-length-accepted R R y no
107 segmentation-supported R R y no
122 vt-classes-supported O2 - -
5 active-vt-sessions O2 - -
O3
57 local-time R W - -
O4
O3
56 local-date R W - -
O4
119 utc-offset O4 R - -
24 daylight-savings-status O4 - -
10 apdu-segment-timeout O1 R W - -
11 apdu-timeout R R y no
73 number-of-apdu-retries R R y no
55 list-of-session-keys O - -
time-synchronization-
116 O5 - -
recipients
64 max-master O 6
- -
63 max-info-frames O6 - -
30 device-address-binding R R no no
155 database-revision R R y no
154 configuration-files O7 - -
157 last-restore-time O7 - -
153 backup-failure-timeout O8 - -
152 active-cov-subscriptions O R - -
167 max-segments-accepted O1 R W - -
172 slave-proxy-enable O10 - -
57 9MA10271 05/2016
BACnet Standard – Device Eliwell PLC
Readable
Optional
Required
Required
Writable
Readble
Writable
WRITE
READ
169 auto-slave-discovery O11 - -

171 slave-address-binding O12 - -
Manual-slave-address-
170 O10 - -
binding
168 profile-name O - -
196 last-restart-session - -
203 time-of-device-restart O13 - -
restart-notification-
202 O13 - -
recipients
utc-time-synchronization-
206 O5 - -
recipients
time-synchronization-
204 O14 - -
interval
193 align-intervals O 14
- -
195 interval-offset O14 - -
1
Required if segmentation of any kind is supported.
2
If one of the properties VT_Classes_Supported or Active_VT_Sessions is present, then both of these properties shall
be present. Both properties are required if support for VT Services is indicated in the PICS.
3
If the device supports the execution of the TimeSynchronization service, then these properties shall be present.
4
If the device supports the execution of the UTCTimeSynchronization service, then these properties shall be present.
5
If this property is present, then Time_Synchronization_Interval, Align_Intervals and Interval_Offset shall be present. If
present, this property shall be writable.
6
These properties are required if the device is an MS/TP master node.
7
These properties are required if the device supports the backup and restore procedures.
8
This property must be present and writable if the device supports the backup and restore procedures.
9
This property is required if the device supports execution of either the SubscribeCOV or SubscribeCOVProperty
service.
10
This property shall be present and writable if the device is capable of being a Slave-Proxy device.
11
This property shall be present if the device is capable of being a Slave-Proxy device that implements automatic
discovery of slaves.
12
This property shall be present if the device is capable of being a Slave-Proxy device.
13
These properties are required if the device supports the restart procedure as described in Clause 19.3.
14
If either Time_Synchronization_Recipients or UTC_Time_Synchronization_Recipients is present, then this property
shall be present and writable.
• None of the writable values will be stored non volatile, so will be lost after power cycle of the device (except
DeviceInstance).
• All strings are restricted to 31 characters.
• number-of-apdu-retries is fixed at 3
• apdu-timeout is fixed at 3000
• apdu-segment-timeout have 2000msec as default value from reset. Max value 65535ms.
• max-segments-accepted have 127 as default value from reset (this value should not be exceed)
58 9MA10271 05/2016
5.3.9. Controller Data Types
Corresponding
Data Type Controller Precision Maximum Range Minimum Range
Data Type
0 32767 -32768
1 3276.7 -3276.8
Signed 16 INT
2 327.67 -327.68
3 32.767 -32.768
0 65535 0
1 6553.5 0
Unsigned16 UINT
2 655.35 0
3 65.535 0
0 2147483647 -2147483648
1 214748364.7 -214748364.8
Signed 32 DINT
2 21474836.47 -21474836.48
2147483.647 -2147483.648
0 4294967295 0
DWORD 1 429496729.5 0
Unsigned32
UDINT 2 42949672.95 0
3 4294967.295 0
0 127 -128
1 12.7 -12.8
Signed 8 SINT
2 1.27 -1.28
3 0.127 -0.128
0 255 0
BYTE
1 25.5 0
Unsigned 8 USINT
2 2.55 0
3 0.255 0
59 9MA10271 05/2016
5.3.10. Analog Input Object - FREE Studio
BACnet Standard – Analog Value Eliwell PLC
Readable
Required
Required
Optional
Writable
Writable
Readble
WRITE
BACnet
READ
ID
property name
75 object-identifier R R y no
call
85 present-value R4 R W y
func
28 description O R W y y
111 status-flags R R y no
36 event-state R R y no
103 reliability O R y *
81 out-of-service R R W y y
117 units R R W y y
104 relinquish-default 1
22 cov-increment O2 R W y y
113 Time-delay O3 R W y y
17 notification-class O3 R W y y
45 High-limit O3 R W y y
59 low-limit O3 R W y y
25 deadband O3 R W y y
52 Limit-enable O3 R W y y
35 event-enable O3 R W y y
0 acked-transitions O3 R y no
72 notify-type O3 R W y y
130 event-time-stamps O3 R y no
1
priority-array and relinquish-default unmanaged
2
This property is required if the object supports COV reporting.
3
These properties are required if the object supports intrinsic reporting.
4
If present-value is commandable, then it is required to be writable. This property is required to be writable when out-of- service is TRUE.
• None of the writable values will be stored non volatile, so will be lost after power cycle of the device
• If the precision of the value written to present_value is greater than the precision of the variable in the application, the controller will truncate the value to the controller precision,
please refer the Controller DataTypes Table for range of values
60 9MA10271 05/2016
5.3.11. Analog Output Object - FREE Studio
Readable
Required
Required
Optional
Writable
Writable
Readble
WRITE
BACnet
READ
ID
property name
call
85 present-value R4 R W no
func
117 units R R W y y
87 priority-array O1 R y no
104 relinquish-default O1 R W y y
1
If present-value is commandable, then both of these properties shall be present.
2
3
4
If present-value is commandable, then it is required to be writable. This property is required to be writable when out-of-
service is TRUE.
• If the precision of the value written to present_value is greater than the precision of the variable in the application,
the controller will truncate the value to the controller precision, please refer the Controller DataTypes Table for range of
values
61 9MA10271 05/2016
5.3.12. Analog Value Object - FREE Studio
Readable
Required
Required
Optional
Writable
Writable
Readble
WRITE
BACnet
READ
ID
property name
call
func
117 units R R W y y
1
2
3
4
If present-value is commandable, then it is required to be writable. This property is required to be writable when out-of-
service is TRUE.
• If the precision of the value written to present_value is greater than the precision of the variable in the application,
the controller will truncate the value to the controller precision, please refer the Controller DataTypes Table for range of
values.
62 9MA10271 05/2016
5.3.13. Binary Value Object - FREE Studio
Readable
Required
Required
Optional
Writable
Writable
Readble
WRITE
READ
call
func
103 reliability O R y y
46 inactive-text O 2
R W y y
4 active-text O2 R W y y
16 change-of-state-time O3
15 change-of-state-count O3
115 time-of-state-count-reset O3
33 elapsed-active-time O4
114 time-of-active-time-reset O4
66 minimum-off-time O
67 minimum-on-time O
113 time-delay O6 R W y y
6 alarm-value O6 R W y y
1
If present-value is commandable, 1 If present-value is commandable, then it is required to be writable. This property is
required to be writable when out-of-service is TRUE.
2
If one of the optional properties inactive-text or active-text is present, then both of these properties shall be present. 3 If one
of the optional properties change-of-state-time, change-of-state-count, or time-of-state-count-reset is present, then all of
these properties shall be present.
4
If one of the optional properties elapsed-active-time or time-of-active-time-reset is present, then both of these properties
shall be present.
5
6
63 9MA10271 05/2016
5.3.14. Multi-State Input Object - FREE Studio
BACnet Standard – Multi-State Value Eliwell PLC
Readable
Required
Required
Optional
Writable
Writable
Readble
WRITE
READ
call
85 present-value R1 R W y
func
103 reliability O2 R y y
74 number-of-states R R y y
110 state-text O R y y
87 priority-array 3
104 relinquish-default 3
113 time-delay O 4
R W y y
7 alarm-values O4 R W y y
39 fault-values O4 R W y y
1
If present-value is commandable, then it is required to also be writable. This property is required to be writable when out-of-
service is TRUE.
2
This property shall be required if fault-values is present.
3
priority-array and relinquish-default unmanaged
4
• None of the writable values will be stored non volatile, so will be lost after power cycle of the
• Number_Of_State il limited to 5, there are max. 5 State_Text string.
64 9MA10271 05/2016
5.3.15. Multi-State Value Object - FREE Studio
BACnet Standard – Multi-State Value Eliwell PLC
Readable
Required
Required
Optional
Writable
Writable
Readble
WRITE
READ
call
func
103 reliability O2 R y y
74 number-of-states R R y y
110 state-text O R y y
113 time-delay O4 R W y y
7 alarm-values O4 R W y y
39 fault-values O4 R W y y
1
If present-value is commandable, then it is required to also be writable. This property is required to be writable when out-of-
service is TRUE.
2
This property shall be required if fault-values is present.
3
4
• Number_Of_State il limited to 5, there are max. 5 State_Text string.
65 9MA10271 05/2016
5.3.16. Schedule Object - FREE Studio
BACnet Standard – Calendar Eliwell PLC
Readable
Required
Required
Optional
Writable
Writable
Readble
WRITE
READ
85 present-value R R y y
32 effective-period R R W y y
123 weekly-schedule O1 R W y y
174 schedule-default O1 R W y y
38 exception-schedule R R W y y
list-of-object-property-
54 R R W y y
references
88 priority-for-writing R R W y y
103 reliability R R y y
1
At least one of these properties is required.
66 9MA10271 05/2016
5.3.17. Notification Class Object - FREE Studio
BACnet Standard – Notifcation Class Eliwell PLC
Readable
Required
Required
Optional
Writable
Writable
Readble
WRITE
READ
17 notification-class R R no no
86 priority R R W y y
1 ack-required R R W y y
102 recipient-list R R W y y
• Recipient_List is limited to 4 recipients.
5.3.18. Calendar Object - FREE Studio
BACnet Standard – Calendar Eliwell PLC

Readable
Required
Required
Optional
Writable
Writable
Readble
WRITE
READ
call
85 present-value R R no
func
23 date-list R R W y y
• Date-list is limited to 16 BACnetCalendarEntry.
67 9MA10271 05/2016

9MA10271 - User Guide BACNET AAC Application Notes - en - 11.05.16

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

9MA10271 - User Guide BACNET AAC Application Notes - en - 11.05.16

Hochgeladen von

Copyright:

Verfügbare Formate

FREE Studio

BACnet Application Notes

Failure to observe this information can result in injury or equipment damage.

© 2015 Eliwell Controls s.r.l. All rights reserved.

CHAPTER 4. APPENDIX - B-AAC PROFILE.......................................... 49

BEFORE YOU BEGIN

START-UP AND TEST

Software testing must be done in both simulated and real environments.

Product Related Information

FREE Studio software, Programming Guide 9MA10256 (EN)

• AVD/AVC: FREE Advance

BACnet is a registered trade mark of the American Society of Heating,

The targets that support the BACnet functionality are:

1.4. BACnet/IP and BACnet MS/TP

Highest conforming profile selected

Highest conforming profile selected

Segmentation Supported Window Size

Data Link and routing Options

Networking Option Supported

Character Sets Supported

Character Sets Supported

AVD/AVC and EVD/EVC - BACNET IP example

NTC Sensor RH Sensor

BAcnet Supervisor TM172PDG42p TM171PFE03 / TM171PFE03HR TM172PDM27p TM171EP27pp

AVD/AVC and EVD/EVC - BACNET MS/TP example

RS485-1 RS485-1 485GS

CAN POWER RS485-2

INVERTER FAN DRIVER

BACnet Supervisor BACnet Node BACnet Node BACnet Node

2.1. First Start-up

1. Click the Launch FREE Studio icon located on the Desktop

You can now:You can now:

1 the operation for AVC / EVD / EVC / EVP is completely analogous

BACnet Objects table

Multistate Status of a process, day of

Before adding an object it is necessary to connect to the BACnet_IEC.pll library.

Add Object message Add Object PLC Library

For each object it is possible to:

Object actions Export to File Object Successfully exported

By default, the following two attributes are always present4:

For this object only, editable fields are available:

Analog Input example: Temperature.Present_Value := TO_REAL(AI1)/10;

Management of alarm states and conditions

Management of Overridden Status

• NO_SENSOR: if the Present Value property assumes the value

6 See Controller Data Types

Binary Output case with relinquish default calculation

IF Temperature.Present_Value > SETPOINT.Present_Value THEN

The relay output update will be given by

Event State Attribute

In the example the multiple state = 2

where Machine_State is the name of the object.

Event State Attribute

The Calendar object, as implied by the name, defines a set of dates.

The Calendar is normally a static object.

In the example, a Holiday calendar is created.

NOTE. A maximum of 4 (instances of) different calendars can be created.

The Calendar object attributes can be nested structures:

Example. The DateList Type is BACnetCalendarEntry:

The structures, in turn, contain the following elements:

BACnetDateRange is the dates interval:

BACNET_SCHEDULE is a complex nested structure:

Amongst these there are the properties Effective and Exceptions.