BACnet AS - sauter-controls.com sauter-controls.com

BACnet AS 


User's Manual 

7001007003 S10 

7001007003 S10 Sauter Systems 1


2 7001007003 S10 Sauter Systems


Table of contents 

0 

1 BACnet basics ....................................................................................................... 11 

1.1 Bibliography.................................................................................................... 11 

1.1.1 BACnet Standard .................................................................................... 11 

1.1.2 BACnet engineering ................................................................................ 12 

1.2 Interoperability in building automation............................................................. 13 

1.3 BACnet as an open protocol for building automation ...................................... 13 

1.4 BACnet Data Link Layers................................................................................ 14 

1.5 Network topology............................................................................................ 15 

1.6 Router............................................................................................................. 15 

1.7 Virtual devices ................................................................................................ 15 

1.8 Client/server model......................................................................................... 15 

1.9 Data objects in the BACnet............................................................................. 16 

1.9.1 The Standard BACnet objects ................................................................. 16 

1.10 Access functions to BACnet devices and objects (services) ........................... 16 

1.10.1 Object access functions........................................................................... 17 

1.10.1.1 AddListElement ............................................................................ 17 

1.10.1.2 RemoveListElement ..................................................................... 17 

1.10.1.3 CreateObject ................................................................................ 17 

1.10.1.4 DeleteObject................................................................................. 17 

1.10.1.5 ReadProperty ............................................................................... 17 

1.10.1.6 ReadPropertyConditional.............................................................. 17 

1.10.1.7 ReadPropertyMultiple ................................................................... 17 

1.10.1.8 WriteProperty ............................................................................... 17 

1.10.1.9 WritePropertyMultiple ................................................................... 17 

1.10.1.10 ReadRange .................................................................................. 17 

1.10.2 File access functions ............................................................................... 18 

1.10.2.1 AtomicReadFile ............................................................................ 18 

1.10.2.2 AtomicWriteFile ............................................................................ 18 

1.10.3 Alarm and event functions ....................................................................... 18 

1.10.3.1 AcknowledgeAlarm....................................................................... 18 

1.10.3.2 ConfirmedCOVNotification............................................................ 18 

1.10.3.3 ConfirmedEventNotification .......................................................... 18 

1.10.3.4 GetAlarmSummary ....................................................................... 18 

1.10.3.5 GetEnrollmentSummary ............................................................... 18 

1.10.3.6 SubscribeCOV (UnsubscribeCOV) ............................................... 19 

1.10.3.7 UnconfirmedCOVNotification........................................................ 19 

1.10.3.8 UnconfirmedEventNotification....................................................... 19 

1.10.3.9 GetEventInformation Service........................................................ 19 

1.10.3.10 SubscribeCOVProperty Service.................................................... 19 

1.10.3.11 LifeSafety Service......................................................................... 19 

1.10.4 Remote device management functions.................................................... 20 

1.10.4.1 DeviceCommunicationControl ...................................................... 20 


0 



1.10.4.2 ConfirmedPrivateTransfer .............................................................20 

1.10.4.3 UnconfirmedPrivateTransfer..........................................................20 

1.10.4.4 ReinitializeDevice..........................................................................20 

1.10.4.5 ConfirmedTextMessage ................................................................20 

1.10.4.6 UnconfirmedTextMessage.............................................................20 

1.10.4.7 TimeSynchronization.....................................................................20 

1.10.4.8 Who-Has .......................................................................................21 

1.10.4.9 I-Have ...........................................................................................21 

1.10.4.10 Who-Is...........................................................................................21 

1.10.4.11 I-Am ..............................................................................................21 

1.10.4.12 UTCTimeSynchronization..............................................................21 

1.10.5 Virtual Terminal functions.........................................................................21 

1.10.5.1 VT-Open .......................................................................................21 

1.10.5.2 VT-Close .......................................................................................21 

1.10.5.3 VT-Data.........................................................................................21 

1.10.6 Network security functions .......................................................................22 

1.10.6.1 Request Key..................................................................................22 

1.10.6.2 Authenticate ..................................................................................22 

1.11 Conformance and interoperability ....................................................................22 

1.11.1 Conformance codes .................................................................................22 

1.11.2 Conformance classes...............................................................................22 

1.11.3 Client/server behaviour ............................................................................22 

1.11.4 Functional groups.....................................................................................23 

1.12 PICS (Protocol Implementation Conformance Statement) ...............................23 

1.13 BIBBs (BACnet Interoperable Building Blocks) ................................................24 

1.14 BACnet procedures and mechanisms .............................................................24 

1.14.1 Initiating a connection with BACnet ..........................................................24 

1.14.2 Referencing with BACnet .........................................................................25 

1.14.3 Change-Of-Value reporting ......................................................................25 

1.14.4 Intrinsic reporting......................................................................................26 

1.14.5 Prioritising commands..............................................................................26 

1.14.5.1 The priority array ...........................................................................26 

1.14.5.2 Writing a value with a priority indication.........................................27 

1.14.5.3 Deleting the priority .......................................................................27 

2 BACnet with Sauter EY3600...................................................................................29 

2.1 BACnet automation stations ............................................................................29 

2.2 BACnet server.................................................................................................30 

2.3 BACnet objects................................................................................................32 

2.3.1 Structure of a BACnet object ....................................................................32 

2.3.2 Portrayal of MFA to BACnet objects.........................................................32 

2.3.3 Link between BACnet object and input/output module..............................33 




0 

2.3.4 Link between BACnet object properties and input/output module 

parameters .............................................................................................. 35 

2.3.4.1 Analog input ................................................................................. 35 

2.3.4.2 Analog output ............................................................................... 36 

2.3.4.3 Analog value................................................................................. 37 

2.3.4.4 Binary input .................................................................................. 38 

2.3.4.5 Binary output ................................................................................ 39 

2.3.4.6 Binary value.................................................................................. 40 

2.3.4.7 Multistate input ............................................................................. 41 

2.3.4.8 Multistate output ........................................................................... 42 

2.3.4.9 Multistate value ............................................................................ 43 

2.3.4.10 Loop ............................................................................................. 44 

2.3.5 Relationship of BACnet unit code to module parameter ‘unit of 

measurement’.......................................................................................... 46 

3 BACnet hardware (EYK) ........................................................................................ 51 

3.1 Hardware platform .......................................................................................... 51 

3.2 Wiring diagram ............................................................................................... 51 

3.3 BACnet configuration...................................................................................... 51 

3.4 LED display for Ethernet interface .................................................................. 52 

4 BACnet in the network (topologies) ..................................................................... 53 

4.1 EYK as a native BACnet station...................................................................... 53 

4.2 EYK as a native BACnet head station............................................................. 54 

4.3 EYK as a native BACnet and novaNet station................................................. 55 

4.4 EYK as a BACnet station with bus-compatible devices (external protocols).... 56 

5 BACnet server configurator .................................................................................. 57 

5.1 Serial COM connection................................................................................... 57 

5.2 Installing the BACnet server configurator........................................................ 58 

5.3 Description of the configurator ........................................................................ 61 

5.3.1 Description of tabs................................................................................... 63 

5.3.1.1 Register „Device“.......................................................................... 63 

5.3.1.2 "Objects" Register ........................................................................ 64 

5.3.1.3 "Network" Register ....................................................................... 65 

5.3.1.4 The ‘EY3600’ tab.......................................................................... 66 

5.3.1.5 "Settings" Register........................................................................ 67 

5.3.1.6 "BBMD" Register .......................................................................... 68 

5.3.2 Description of menu items ....................................................................... 69 

6 BACnet system objects......................................................................................... 73 

6.1 Create device object ....................................................................................... 73 

6.1.1.1 Device Object ............................................................................... 74 

6.1.2 'Reinitialize Device' for BACnet device .................................................... 75 


0 



6.1.3 Time synchronisation for the BACnet device ............................................76 

6.2 The 'Project engineering' object.......................................................................76 

6.3 The 'AS status' object......................................................................................77 

6.4 The 'Restart-Indicator' object ...........................................................................77 

7 Parameterising the AS with CASE FBD ................................................................79 

7.1 Visualisation and operating..............................................................................79 

7.1.1 AI parameters ..........................................................................................79 

7.1.2 AI_Soft parameters ..................................................................................79 

7.1.3 CI parameters ..........................................................................................80 

7.1.4 CIF_Soft parameters................................................................................80 

7.1.5 CIV_Soft parameters................................................................................80 

7.1.6 Example...................................................................................................81 

7.1.7 Hours-run counter ....................................................................................82 

7.1.8 Example...................................................................................................82 

7.2 Analog output object........................................................................................83 

7.2.1 AO parameters.........................................................................................83 

7.3 Analog value object .........................................................................................83 

7.3.1 AI_Soft parameters ..................................................................................83 

7.3.2 AIA_Soft parameters................................................................................83 

7.3.3 CFB_Soft parameters...............................................................................84 

7.3.4 Example...................................................................................................84 

7.4 Binary input object...........................................................................................85 

7.4.1 BI parameters ..........................................................................................85 

7.4.2 BI_Soft parameters ..................................................................................85 

7.4.3 DI parameters ..........................................................................................85 

7.4.4 DI_Soft parameters ..................................................................................85 

7.4.5 Example...................................................................................................86 

7.5 Binary output object.........................................................................................86 

7.5.1 DO parameters.........................................................................................86 

7.5.2 Example...................................................................................................87 

7.6 Binary value object ..........................................................................................88 

7.6.1 DIA_Soft parameters................................................................................88 


7.6.3 CFB_Soft parameters...............................................................................88 

7.7 Multistate input object......................................................................................89 

7.7.1 DI parameters ..........................................................................................89 


7.8 Multistate output object....................................................................................89 

7.8.1 DO parameters.........................................................................................89 

7.8.2 Example...................................................................................................90 

7.9 Multistate value object .....................................................................................91 

7.9.1 DIA_Soft parameters................................................................................91 




0 

7.9.2 DI_Soft parameters ................................................................................. 91 

7.9.3 CFB_Soft parameters.............................................................................. 91 

7.10 Loop object..................................................................................................... 92 

7.10.1 Loop parameters ..................................................................................... 92 

8 Historical data recording with BACnet................................................................. 93 

8.1 Create a Trend Log object .............................................................................. 93 

8.2 Trend Log Object............................................................................................ 95 

8.3 How a Trend Log works.................................................................................. 96 

8.4 Engineering examples .................................................................................... 97 

8.4.1 Analogue input of Present-Value with time raster .................................... 97 

8.4.2 Analogue input of Present-Value with COV ............................................. 98 

8.4.3 External multistate output of Present-Value with COV ............................. 98 

8.4.4 Non-COV-supported property with time raster ......................................... 99 

8.5 Read log buffer with ReadRange .................................................................... 99 

8.6 Trend Log engineering notes ........................................................................ 101 

8.6.1 Background information......................................................................... 101 

8.6.2 Behaviour in case of power failure or reset of the BACnet server .......... 101 

9 Alarms and events............................................................................................... 103 

9.1 Change-Of-Value reporting........................................................................... 103 

9.2 Intrinsic-Reporting......................................................................................... 103 

9.3 Alarms with Notification Class objects........................................................... 105 

9.4 Notification Class Object............................................................................... 107 

9.4.1 Notification class 1 (OOR alarming notification)..................................... 108 

9.4.2 Notification class 2 (COS alarming notification) ..................................... 109 

9.4.3 Notification Class 3 (system events)...................................................... 110 

9.4.4 Notification class 4 (TrendLog buffer limit)............................................. 111 

9.4.5 Notification class 5 (floating limit notification)......................................... 112 

9.5 Alarm-Quittierung.......................................................................................... 113 

10 Time profiles ........................................................................................................ 115 

10.1 Create schedule object ................................................................................. 115 

10.1.1 Schedule object..................................................................................... 116 

10.1.2 Example ................................................................................................ 116 

10.2 Create calendar object.................................................................................. 117 

10.2.1 Calendar object ..................................................................................... 118 

10.2.2 Example ................................................................................................ 118 

11 EYK 300 parameterising for peer-to-peer data transmission ........................... 119 

11.1 Client ‘data sink’ functionality........................................................................ 119 

11.2 Client ‘data source’ functionality.................................................................... 119 

11.3 Engineering the data links............................................................................. 120 

11.4 Downloading the link file ............................................................................... 121 


0 



11.5 Example: .......................................................................................................122 

11.5.1 Topology: ...............................................................................................122 

11.5.2 Transfer list bnsclt1.xls...........................................................................123 

11.5.3 Description of operation .........................................................................123 

11.5.3.1 Data sink .....................................................................................123 

11.5.3.2 Data source.................................................................................124 

12 EDE (Engineering Data Exchange)......................................................................125 

13 Data exchange with EYK (FTP)............................................................................127 

14 Annexe A: BACnet FAQ .......................................................................................129 

15 Annexe B: Troubleshooting the EYK ..................................................................131 

15.1 Error log file for the BACnet server................................................................131 

15.2 Communication tests.....................................................................................133 

15.2.1 Ping........................................................................................................133 

15.2.2 Telnet server ..........................................................................................134 

15.2.3 Hyperterminal.........................................................................................135 

16 Annexe C: System limits......................................................................................137 

16.1 System ..........................................................................................................137 

16.2 Objects..........................................................................................................137 

17 Annexe D: BACnet data types .............................................................................139 

18 Annexe E: BACnet client tool ..............................................................................141 

19 Annexe F: 'Inside' BACnet EYK...........................................................................143 

19.1 Hardware architecture ...................................................................................143 

19.2 The baseboard ..............................................................................................143 

19.3 The processor board .....................................................................................144 

20 Annexe G: BACnet server application update....................................................145 

21 Annexe H: BACnet on the Internet ......................................................................147 




0 

Trademarks 

Registered trademarks and product designations of various companies and 

manufacturers are not specifically shown in this manual, but a summary of them is given 

here. 

Microsoft, Windows, MS-DOS 

Windows CE 

Microsoft Office 

Microsoft Excel 

Microsoft Access 

Microsoft Word 

Acrobat Reader 

BACstac 

OPC 

BACnet, ASHRAE 

LonTalk 

Ethernet 

ARCnet 

Intel, Pentium 

Trademark of Microsoft Corporation 






Adobe Systems Incorporated 

Trademark of Cimetrics, Inc. 

Trademark of the OPC Foundation 

Trademark of the American Society of Heating, 

Refrigerating and Air-Conditioning Engineers, Inc. 

Trademark of Echelon, Inc. 

Trademark of the Xerox Corporation 

Trademark of the Datapoint Corporation 

Trademark of the Intel Corporation 

All other brand or product names mentioned in the manual are trademarks and/or 

registered trademarks of the owners of the respective rights. 


0 





BACnet basics 

1 

1 BACnet basics 

BACnet is an open data communication protocol for building automation and control 

networks (Building Automation and Control networks). 

BACnet was developed by the North-American ASHRAE (American Society of Heating, 

Refrigerating and Air-conditioning Engineers), adopted by the American National 

Standards Institute (ANSI) and is regularly revised by the International Standards 

Organisation (ISO). 

BACnet is suitable for both the management level and the automation level. 

Milestones in the history of BACnet: 

• 1987 ASHRAE establishes the Standard Project Committee, SSPC 135 

• 1995 Publication of ASHRAE 135-1995, adopted as ASHRAE/ANSI Standard 135- 

1995 

• 1999 With Addendum 135a, BACnet/IP becomes part of the standard 

• 2002 ASHRAE publishes ASHRAE/ANSI 135-2001 

• 2003 BACnet becomes the international standard (ISO 16484-5) and the 

European standard (EN ISO 16484-5) 

• 2004 ASHRAE publishes ASHRAE/ANSI 135-2004 

Milestones for Sauter: 

• 2003 First Sauter BACnet product on the market, based on BACnet/IP 

• 2004 Sauter passes the BACnet conformance test with the BACnet Automation 

Station (EYK 300) and obtains the BTL logo. 

1.1 Bibliography 

1.1.1 BACnet Standard 

[1a] 

ANSI/ASHRAE Standard 135-1995 BACnet A Data Communication Protocol for 

Building Automation and Control Networks:- 

This is the erste official ASHRAE standard on the subject of BACnet and covers the 

complete ASHRAE Standard 135-1995 (BACnet). There are a number of extensions 

and annexes to this work which can be downloaded from the BACnet web site 

(www.bacnet.org). The more recent versions are: 

[1b] ANSI/ASHRAE Standard 135-2001: BACnet, A Data Communication Protocol for 

Building Automation and Control Networks 

[1c] ISO 16484-5:2003: Building Automation and Control Systems -- Part 5: Data 

Communication Protocol 


1 



[1d] ANSI/ASHRAE Standard 135-2004: BACnet, A Data Communication Protocol for 

Building Automation and Control Networks 

This standard can be obtained from the following online bookshops: 

• ASHRAE: www.ashrae.org Bookstore 

• International Organisation for Standardization: www.iso.org ISO Store 

• Beuth Verlag: www.beuth.de 

• Promotor Verlag: www.cci-promotor.de 

• Swiss Standards Association: www.snv.ch 

• Austrian Standards Institute: www.on-norm.at 

• Italian HVAC Organisation (Associazione Italiana Condizionamento dell'Aria 

Riscaldamento Refrigerazione): www.aicarr.it 

Of course, there are other country-specific standardisation institutes from which you can 

also obtain global standard ISO 16484-5 (BACnet Protocol). 

1.1.2 BACnet engineering 

[2] B.I.G.-EU, VDI-TGA: Leitfaden zur Ausschreibung interoperabler 

Gebäudeautomation auf Basis von DIN EN ISO 16484-5, Systeme der 

Gebäudeautomation - Datenkommunikationsprotokoll (BACnet) 

[B.I.G.-EU, VDI-TGA: [GSA] Guide to Specifying Interoperable Building Automation 

and Control Systems based on DIN EN ISO 16484-5, Building Automation Systems 

- Data Communication Protocol (BACnet)] 

This is an extensive guideline that offers important advice on implementing BACnet 

projects. It is the German translation of [3] and is available from www.big-eu.org 

Downloads. 

[3] NIST: GSA Guide to Specifying Interoperable Building Automation and Control 

Systems Using ANSI/ASHRAE Standard 135-1995, BACnet; NISTIR 6392 

This is the American guideline for BACnet projects, available from www.nist.gov 

Search NIST webspace Keyword: NISTIR 6392. 

[4] B.I.G.-EU, VDI-TGA: Begriffe und Definitionen für den Leitfaden zur Ausschreibung 

interoperabler Gebäudeautomation auf Basis von DIN EN ISO 16484-5 

[B.I.G.-EU, VDI-TGA: Terms and Definitions for the Guide to Specifying 

Interoperable Building Automation based on DIN EN ISO 16484-5] 

This is an additional document for [2] and is helpful for 'Anglo-Saxon' terms and their 

meanings that are not always translated into the other language in this field. You can 

also obtain it from www.big-eu.org Downloads. 




1 

[5] Hans R. Kranz: BACnet Gebäude-Automation [BACnet Building Automation] 1.4, 

Promotor-Verlag Karlsruhe, ISBN 3-922420-02-8, 1st edition, 2005 

This is a very comprehensive book on BACnet basics, project engineering advice and 

specifications. 

1.2 Interoperability in building automation 

The main the problem is that many manufacturers use their own (proprietary) 

communication protocols. 

Efforts to find a ‘common language’ for building automation systems have been made 

regularly in the past; some of these communication protocols are still in use today. 

Here are some examples:- 

• FND 

• Profibus profile building automation 

• MODBUS 

• EIB 

• LONtalk 

Not all of the above-mentioned communication protocols are/were successful. 

The reasons for this are, amongst other things: (a) the lack of acceptance of all those 

involved in the planning, realisation and running of building automation systems; and (b) 

the reluctance of manufacturers to make their systems compatible with the systems of 

other manufacturers. 

1.3 BACnet as an open protocol for 

building automation 

The following chapters concentrate on the BACnet communication protocol. 

BACnet was designed as an interoperable communication protocol for the automation 

and management levels of building automation systems. In Europe, BACnet has already 

achieved the status of a European standard. 

Therefore, interoperability has a decisive role for the use and acceptance of BACnet 

products. 

In 2004, Sauter passed the European BACnet conformance test at the 

WSPLab testing institution with the BACnet Automation Station, giving it 

the BTL (BACnet Testing Laboratories) logo. 


1 



1.4 BACnet Data Link Layers 

For data communication in the BACnet, numerous ‘data link layers’ were laid down. The 

following table shows the defined layers with their location in the ISO/OSI layer model:- 

Layers in the 

ISO/OSI 

reference model 

BACnet Application Layer 

Application 

BACnet/IP 

UDP/IP 

BACnet Network Layer 

Switching 

BVLL 

ISO 8802-2 

Type 1 

MS/TP PTP LonTalk Data backup 

Media access 

ISO 8802-3 

'Ethernet' 

ARCNET RS 485 RS 232 Bit transmission 

The following data link layers have been included in the European standard:- 

For the management level (ENV 1805-1):- 

• Ethernet (ISO 8802-3) 

• TCP/IP 

• PTP (point to point) mainly for dial-up connections 

For the automation level (ENV 13321-1):- 

• Ethernet (ISO 8802-3) 

• TCP/IP 

• PTP (point to point) mainly for dial-up connections 

• LONTalk 




1 

1.5 Network topology 

BACnet devices use one of four LAN media or an asynchronous serial connection 

(possibly with dial-up connection) as a physical medium. The type of specified media 

chosen was common, standardised network media, in order to be able to realise 

inexpensive networks with standard components. 

1.6 Router 

A big advantage of BACnet lies in the number of ready-defined data link layers and in 

the ability to ‘tunnel’ data. For instance, with the aid of routers, practically any media can 

be used, if the relevant routers convert the data on the one side into either another standard 

protocol or a proprietary protocol, which is forwarded again as a BACnet data 

package on the other side. This mechanism is of interest mainly for remote properties if, 

for example, TCP/IP (i.e. the ‘internet’ protocol) is to be used. For the BACnet devices in 

the network, this mechanism is fully transparent. 

1.7 Virtual devices 

If the application demands it, devices can be represented in BACnet virtually by a physical 

device. This is useful if all the devices of part of a building need to be addressed singly, 

but there is only one physical connection. The device that manages the physical connection 

then works as a router for one or more virtual networks. 

1.8 Client/server model 

BACnet is structured along the lines of a client/server model. The server is the device 

that provides data for other applications/devices (clients). Routers have both client and 

server functionality. Clients can log onto one or more servers and read or write the 

values of objects. Furthermore, there are mechanisms for event-orientated data communication, 

i.e. clients are automatically notified of any changes in value in the server. 


1 



1.9 Data objects in the BACnet 

Every BACnet device (the term ‘device’ also refers in this case to a superior management 

software or similar) manages so-called objects. At least the ‘device’ object, which 

the inscribes the device itself must be available. Objects are comprised of ‘properties’. 

1.9.1 The Standard BACnet objects 

Analog Input Command Multistate Input 

Analog Output Device Multistate Output 

Analog Value Event Enrollment Multistate Value 

Binary Input Notification Class Calendar 

Binary Output File Loop 

Binary Value Group Program 

Averaging Trend Log Schedule 

Accumulator 

Life Safety Point 

Pulse Converter 

Life Safety Zone 

The BACnet protocol is being expanded all the time, and new functions and objects for 

other applications, e.g. for fire-alarm systems, counter values etc. are being added. 

1.10 Access functions to BACnet devices 

and objects (services) 

To be able to access BACnet objects and their properties, numerous functions have been 

defined. These include functions to establish a connection to a device, to read/write 

properties and, for instance, to log COV services on. 

BACnet services are divided into various categories such as: 

• object access functions 

• file access functions 

• alarm and event functions 

• remote device management functions 

• virtual terminal functions 

• network security functions 




1 

1.10.1 Object access functions 

1.10.1.1 AddListElement 

This function enables a client to attach an entry to a property which represents a list. 

1.10.1.2 RemoveListElement 

This function enables the client to remove an entry from a list. 

1.10.1.3 CreateObject 

This function enables a client to create a new instance of an object within a server. 

1.10.1.4 DeleteObject 

This function enables a client to remove an instance of an object from the server again. 

1.10.1.5 ReadProperty 

This function enables a client to ask for a property of an object from the server. 

1.10.1.6 ReadPropertyConditional 

This function is identical to the ReadProperty function, but restrictions can be stipulated, 

e.g. read all PresentValues that are less than 10. 

1.10.1.7 ReadPropertyMultiple 

This function is identical to the ReadProperty function, but the properties of several 

objects can be read with a demand. 

1.10.1.8 WriteProperty 

This function enables a client to write values into the properties of an object. 

1.10.1.9 WritePropertyMultiple 

This function is identical to the WriteProperty function, but the properties of several 

objects can be written with a demand. 

1.10.1.10 ReadRange 

This function enables a client to read a range of data. This function is used for trend 

objects, lists or arrays. 


1 



1.10.2 File access functions 

1.10.2.1 AtomicReadFile 

This function enables a file to be read from a device. 

1.10.2.2 AtomicWriteFile 

This function enables a file to be sent to a device. 

The purpose of use and the content of the files are not laid down. Applications can, for 

instance, be parameter definitions that can be loaded into devices with the aid of files. 

1.10.3 Alarm and event functions 

1.10.3.1 AcknowledgeAlarm 

This function enables a client to confirm an alarm from the server (usually in conjunction 

with a user acknowledgement in the user surface). 

1.10.3.2 ConfirmedCOVNotification 

This function enables a server to inform a client of the change in either a current value 

or the status flags. It ensures that the client has received the message. This does not 

mean, however, that a possible operator has been informed of the status. 

1.10.3.3 ConfirmedEventNotification 

This function enables a server to inform a client of an alarm or an event. Again, it 

ensures that the client has received the message. Similarly, the message means merely 

that the message has been sent, not that a user has acknowledged it. 

1.10.3.4 GetAlarmSummary 

This function enables a client to request a list of waiting alarms. This is done usually 

when the client starts the program. 

1.10.3.5 GetEnrollmentSummary 

This function enables a client to request a list of those objects that can trigger an alarm 

can. Again, this is done usually when the client starts the program. 




1 

1.10.3.6 SubscribeCOV (UnsubscribeCOV) 

This function enables a client to subscribe as the recipient for the automatic server 

notification service when the current value or the status flag changes. 

UnsubscribeCOV: this function is used by a client to withdraw again from the automatic 

notification service. This is not an independent service, but a variant of SubscribeCOV. 

1.10.3.7 UnconfirmedCOVNotification 

This function is used by a server to notify a client of a change to the current value or 

status flags. This is an unconfirmed service, i.e. it cannot be ensured that the client 

really has been informed. 

1.10.3.8 UnconfirmedEventNotification 

This function is used by a server to notify a client of an alarm or an event. This is also an 

unconfirmed service, i.e. it cannot be ensured that the client really has been informed. 

1.10.3.9 GetEventInformation Service 

This function is used by a client to obtain an overview of all active event statuses. 

1.10.3.10 SubscribeCOVProperty Service 

This function is the same as SubscribeCOV, except that other properties than the 

current value and status flags can be notified to the server notification service for value 

changes. 

1.10.3.11 LifeSafety Service 

This function is used for fire and security systems to perform relevant tasks. 


1 



1.10.4 Remote device management functions 

1.10.4.1 DeviceCommunicationControl 

This function enables a device to be blocked for any network traffic (except DevicecommunicationControl 

and ReinitializeDevice) either for a limited period or for an 

indefinite period. 

1.10.4.2 ConfirmedPrivateTransfer 

This message enables functions pertaining to a particular manufacturer to be carried out 

with a confirmation. The purpose of use and the content are subject to details pertaining 

to a particular manufacturer. 

1.10.4.3 UnconfirmedPrivateTransfer 

This message enables functions pertaining to a particular manufacturer to be carried out 

without a confirmation. The purpose of use and the content are subject to details 

pertaining to a particular manufacturer. 

1.10.4.4 ReinitializeDevice 

This function enables a device to be re-started. This can be either a reboot or a warm 

start (defined starting at a certain point). 

1.10.4.5 ConfirmedTextMessage 

This function enables confirmed text transfer to a device. 

Text messages can be prioritised and can also be given a message category. Again, the 

sending of the message is guaranteed, but there is no certainty that the operator actually 

reads it. This message should not be sent as a broadcast or a multicast. 

1.10.4.6 UnconfirmedTextMessage 

This function is similar to the ConfirmedTextMessage, but without confirmation that the 

message has been received; however, there is the option of sending it as either a 

broadcast or a multicast. 

1.10.4.7 TimeSynchronization 

This function enables the user to synchronise devices that should, on receipt of the 

message, set their internal clock accordingly. 




1 

1.10.4.8 Who-Has 

This function is used to determine which DeviceObject and which network address of the 

device has the desired object. To do so, either the clear ObjectIdentifier (i.e. ObjectType 

and ObjectInstance) or the object name is used. This command can and should be sent 

as a broadcast command. 

1.10.4.9 I-Have 

With this function, a device announces that it has a certain object. This message can be 

sent as a response to a Who-Has message or as a broadcast on starting the device. 

1.10.4.10 Who-Is 

This function is used to determine the network address and/or the DeviceObjectidentifier 

of devices in the network. 

1.10.4.11 I-Am 

With this function, a device announces its network address and its DeviceObjectIdentifier. 

This message can be sent as a response to a Who-Is message or as a broadcast 

on starting the device. 

1.10.4.12 UTCTimeSynchronization 

This function is used to synchronise the time with the aid of time zones. Devices should 

set their internal clock accordingly on receiving this message. 

1.10.5 Virtual Terminal functions 

These Virtual Terminal functions are no longer used frequently with BACnet/IP and the 

new network technologies. 

1.10.5.1 VT-Open 

This function opens a virtual terminal of a device. 

1.10.5.2 VT-Close 

This function closes a virtual terminal. 

1.10.5.3 VT-Data 

This function is used to transfer data to a virtual terminal. 


1 



1.10.6 Network security functions 

These functions for network security are very rarely used, as other technologies are 

used for network security in most cases. 

1.10.6.1 Request Key 

This function is used by the BACnet client to obtain a Session Key with its Private Key, 

allowing communication with another BACnet device. 

1.10.6.2 Authenticate 

This function is used to confirm access rights for communication. 

1.11 Conformance and interoperability 

As already mentioned, interoperability is of great importance in the BACnet whenever 

systems of various manufacturers are to communicate with one another. To safeguard 

this, numerous rules have been laid down in the BACnet specification with regard to the 

relevant objects and their properties. 

1.11.1 Conformance codes 

There are three possible conformance codes for the properties of objects:- 

• R This property must be both present and readable. 

• W This property must be present, readable and writeable. 

• O This property is optional. 

1.11.2 Conformance classes 

BACnet specification 135-1995 divided BACnet functions into so-called 'Conformance 

Classes'. Each of these classes (1-6) contains a defined scope of functions that have to 

be supported. The classes are structured incrementally, i.e. a device that supports 

conformance class 3 must also support the functions of Classes 1 and 2. 

1.11.3 Client/server behaviour 

As already mentioned, BACnet uses the client/server model for data communication. 

The terms ‘initiate’ and ‘execute’ are used to determine which device requests a service 

(‘initiate’) and which one carries out the service (‘execute’). These terms are often used 

in BACnet specification 135-1995 in connection with BACnet functions. 




1 

1.11.4 Functional groups 

In addition to the Conformance Classes, BACnet specification 135-1995 also defined 

Functional Groups to allow the classification of devices. This is explained below using 

the examples ‘COV Event Initiation’ and ‘COV Event Response’. 

COV Event Initiation Functional Group (server functionality) 

Application Service Init Exec 

SubscribeCOV 

X 

ConfirmedCOVNotification X 

COV Event Response Functional Group (client functionality) 

Application Service Init Exec 

SubscribeCOV 

X 

ConfirmedCOVNotification 

X 

The letter ‘X’ in the ‘Init’ column denotes that the device (acting as a client) is capable of 

requesting or triggering the service. The letter ‘X’ in the ‘Exec’ column denotes that the 

device (acting as a server) is capable of carrying out the requested service. 

1.12 PICS (Protocol Implementation 

Conformance Statement) 

A PICS is a document that describes the scope of a device in terms of functions and 

objects. Among other aspects, it may also describe the supported Conformance 

Classes, the supported DataLinkLayers and the Functional Groups. Since BACnet 

specification 135-2001, BACnet profiles, supported BIBBs and objects are also 

indicated. 

The official template for a PICS is defined in Annexe A of the AHSRAE Standard, which 

makes it part of that standard. 

For two devices to be able to interact properly, it is important that the PICS be compared 

to one another. To achieve interoperability of both devices, you can, of course, only use 

functions, objects and DataLinkLayers that are supported by both devices. Another point 

to note here is which protocol revision is supported. 


1 



1.13 BIBBs (BACnet Interoperable Building 

Blocks) 

The system of 'Conformance Classes' and 'Functional Groups' has not proven to be 

ideal in practice, so BACnet specification 135-2001 included a definition of the BIBBs 

(BACnet Interoperable Building Blocks) as Annexe K. This annexe to the BACnet 

Standard specifies functions in categories 'A' and 'B'. 

Category A lays down the user of the data (normally a client device). Category B lays 

down the provider of the data (normally a server device). 

As regards structure, the BIBBs can be compared with the functional groups, but there is 

no strict classification in the conformance classes. 

With the BIBBs, the functions of devices can, therefore, be presented in much greater 

detail. 

1.14 BACnet procedures and mechanisms 

Client / server behaviour - how functions (services) are used and which ones - is 

described in various BACnet procedures and mechanisms. Some examples are cited 

below. 

1.14.1 Initiating a connection with BACnet 

The device object makes the properties of a BACnet subscriber available to other 

subscribers in the BACnet as a standard object. 

Clients can use the ‘Who-Is’ service to ask which servers have logged on to the BACnet 

network. Servers can use the ‘I-Am’ service to inform the clients in the BACnet network 

that they have logged on to the network. 

With the ‘Who-Has’ service, clients ask which servers in the BACnet have a particular 

object. With the ‘I-Have’ service, servers inform the BACnet clients that they have the 

object in question. 

These services are mostly sent as broadcast messages to all the connected subscribers 

in the BACnet network. 




1 

1.14.2 Referencing with BACnet 

In networks with a lot of subscribers, the unique referencing of devices and objects is 

necessary. The referencing of objects, and of device objects, is effected in the BACnet 

via the object type and an instance number, which together form the unique BACnet 

Object Identifier. 

The instance number of the device object must be unique in the entire network. 

The objects supported in the device must be unique within the object. 

Alternatively, addressing via the object name is possible. Here, too, it must be possible 

to reference the device object in the entire network uniquely and to reference every 

object in the device within the device. 

1.14.3 Change-Of-Value reporting 

In order to keep traffic in the network low, especially when there is a lot of data, the 

event-dependent notification of clients informs about changes to the present value or 

changes to the status flags (COV=‘Change of Value’) in the BACnet. 

To use this service, the client uses the ‘SubscribeCOV’ service to subscribe to the 

notification service for required objects after the link has been established. 

The server adds this information to an internal notification list and notifies the client e.g. 

about changes to the present value or changes to the status flags. 

The client can state whether this notification is to be confirmed or unconfirmed. It is also 

possible for the client to restrict the lifetime of the notification service (‘Lifetime’). 


1 



1.14.4 Intrinsic reporting 

Intrinsic reporting represents one of two ways of notifying clients of events or alarms. 

With intrinsic reporting, the Notification Class Object is used to lay down the type of 

event or alarm. 

This represents any number of event-triggering objects and determines the type of 

alarm, e.g. the priority and whether an acknowledge is necessary. 

Clients can enter themselves in the list of recipients. This entry is made using the 

BACnetDestination data structure. 

This includes the client’s network address and details of the valid period and the type of 

notification (confirmed/unconfirmed). 

1.14.5 Prioritising commands 

The BACnet standard describes certain properties as ‘commandable’ e.g. the 

Present_Value of an analog-output object. To enable prioritising of commands, these 

objects support the properties ‘Priority_Array’ and ‘Relinquish_Default’. The support for 

these properties is, in some cases, even stipulated (e.g. for analog output). 

1.14.5.1 The priority array 

The Priority_Array, which is readable only, supports 16 priority levels (1=highest priority, 

16=lowest priority), which processes the issuing of commands by different clients. In this 

array, either the last written value in each case or the word ‘NULL’ (there is no command 

for this priority level) is saved for each priority level. 

The use of the 16 priority levels is not standardised and it may vary from one plant to 

another. To guarantee interoperability, however, all the devices in a plant must conform 

to the same priority level scheme. The standard lists the Standard Command Priorities 

and their applications in a table. 

Priority Application 

Priority Application 

level 

level 

1 Manual Life Safety 9 Freely available 

2 Automatic Life Safety 10 Freely available 

3 Freely available 11 Freely available 


5 Critical Equipment Control 13 Freely available 

6 Minimum On/Off 14 Freely available 


8 Manual Operator 16 Freely available 




1 

1.14.5.2 Writing a value with a priority indication 

If a client writes a ‘Commandable property’ with the ‘WriteProperty’ or 

‘WritePropertyMultiple’ Service, he transfers (in addition to the value) the priority level in the 

range 1-16. If no priority is given, priority 16 is taken as standard. If a value with a higher 

priority has already been written (perhaps by another client), only the new value is added to 

the Priority_Array; the value of the commandable property is not changed. 

If the priority of the value in question exceeds the highest present priority in the 

Priority_Array, then the new value is added to the Commandable Property, even if the 

priority levels are the same. The written value is also saved in the Priority_Array in the 

relevant priority level. The previous value for the corresponding priority level becomes 

invalid due to the writing operation and is overwritten without notification. BACnet does 

not stipulate that the information as to which process has carried out a write command 

has to be saved, but this can be implemented according to the manufacturer. 

1.14.5.3 Deleting the priority 

To remove an entry from the Priority_Array, a client writes the Commandable Property 

using either the ‘WriteProperty’ or ‘WritePropertyMultiple’ Service with the word ‘NULL’, 

stating the priority level. In this case, the relevant entry is removed from the 

Priority_Array and the value of the next lowest priority becomes applicable, i.e. the 

Commandable Property is set with this value. 

If all 16 elements in the Priority_Array have value 'NULL' ['ZERO'], the 

Commandable_Property should take the Relinquish_Default property of the object. 


1 





BACnet with Sauter EY3600 

2 

2 BACnet with Sauter EY3600 

2.1 BACnet automation stations 

Sauter offers a BACnet communication card (EYK 300) for modular automation stations 

(nova106 and novaCom) and two compact BACnet automation stations (nova220 and 

nova230). 

EYK 300 F001 EYK 220 F001 EYK 230 F… 

BACnet nova220 with integrated nova230 with integrated 

COMMUNICATION CARD BACNET FUNCTION BACNET FUNCTION 

• The EYK 300 F001 is used to integrate the modular nova106 EY3600 automation 

stations and novaCom with the standardised 'BACnet / IP based on Ethernet' 

communication protocol in accordance with ISO 16484-5 (ENV 13321-1). It is 

assembled in rack EYU 108 or 109 in card position A and is operated together with a 

nova106 or with novaCom. 

• The EYK 220 F001 is the compact nova220 unit in the EY3600 system family, 

equipped with an integrated BACnet communication card. 

The EYK 230 F… is a compact universal nova230 unit in the EY3600 system family, 

also equipped with an integrated BACnet communication card. As well as the normal 

hardware volume structure for the HVAC applications, other devices with specific field 

bus protocols (e.g. Modbus, M-Bus, etc.) can also be integrated via RS232. 


2 



2.2 BACnet server 

As the BACnet server, this BACnet communication card provides all the 'BACnet objects' 

that are needed for the HVAC applications as well as the associated 'Properties' with the 

required 'Services' (or functions). Typical users (BACnet clients) of this information are 

open management systems, bus-wide control units/user panels, etc. 

In its function as a BACnet client (which is also integrated), the communication card 

supports peer-to-peer transmission for a maximum of 100 datapoints with other BACnetcompatible 

automation stations. 

The connection between communication processor EYK 300 and the automation station 

processor (EYL 106, EYL 2…) is made via 'novaNet'. Within the focal point of the 

installation, up to 100 intelligent novaFlex I/O controllers, subordinate EY3600 automation 

stations, novaCom and ecos can also be connected to it. 

Each EYK 300 F001, EYK 220 F001 or EYK 230 F… can manage up to a maximum of 

1000 BACnet objects. 

The following local objects are defined statically (s) or dynamically (d) for this purpose: 

• 1 device object (s) 

• 1 binary input object for Project Engineering status (s) 

• 1 binary input object for Restart-Indicator status (s) 

• 1 multistate input object per assigned automation station for AS status (s) 

• 5 predefined Notification Class objects (s) or 

13 or 14 freely available Notification Class objects and 2 predefined Notification 

Class objects (s) 

• 0 ... 100 Schedule objects (s/d) 

• 0 ... 40 Calendar objects (s/d) 

• 0 … 50 Trend Log objects (d) 

Every valid EY3600 AS data point and its corresponding parameters are automatically 

converted into a BACnet object and its corresponding properties. 

The updating of the properties is also done automatically. The following objects are 

supported and are generated automatically: Analogue Input, Analogue Output, Analogue 

Value, Binary Input, Binary Output, Binary Value, Multistate Input, Multistate Output, 

Mulitstate Value, Loop and Notification Class. 




2 

Using the similarly implemented Scheduler (day and week calendar) and the associated 

‘Schedule and Calendar BACnet objects’, it is possible to process local BACnet time 

programs and also, therefore, to control process variables of the connected AS in accordance 

with a time programme. It is also possible to control objects from other BACnet 

devices. 

The Trend Log objects have to be created dynamically by a BACnet client in order to 

obtain historical data records with BACnet. A BACnet client can perform the 

configuration of the Trend Log object and, accordingly, read the stored data from local or 

external BACnet objects with the ReadRange function. 

The AS data points (BACnet objects) can be transmitted either by BACnet clients via 

cyclical polling or by the COV (Change Of Value) subscription mechanism on the 

BACnet communication card. 

Other BACnet specifications can be consulted according to the separate BACnet PICS 

(Protocol Implementation Conformance Statement), and the 'Sauter-Server-EY3600- 

PICS.pdf' document. 

The Annexe (section 16) contains more information about the system limit. 

. 


2 



2.3 BACnet objects 

2.3.1 Structure of a BACnet object 

A BACnet object comprises a collection of parameters (properties), which are either 

obligatory, optional or Author-specific. The following properties are obligatory and can 

be found in every BACnet object:- 

• Object_Identifier 

• Object_Name 

• Object_Type 

These properties must be unambiguous in a BACnet system. 

2.3.2 Portrayal of MFA to BACnet objects 

An MFA of an AS is always portrayed to exactly one instance of the corresponding 

BACnet object type. The instance number of such a BACnet object is worked out from 

the AS novaNet address (1...4194) and the MFA number as follows:- 

Object instance = AS address * 1000 + MFA number 

Important note: 

The calculation of these object instance numbers (AS address * 1000 + MFA number) yields 

a maximum permissible AS number of 4194. 

The BACnet communication card or a BACnet AS cannot generate a BACnet object for an 

AS with a novaNet AS address which is higher than 4194 or equal to 0. 

The object name of a BACnet object is composed of the house address and the protocol 

zone of a specified MFA and a freely definable constant text. The composition is specified 

by a formatting string that can be engineered in the configurator (see section 5). 

The object type of a BACnet object is automatically determined using the parameterised 

input/output modules. 




2 

2.3.3 Link between BACnet object and input/output 

module 

The link to the EY3600 input/output modules is shown in the BACnet object-type table 

below:- 

BACnet Object-Type Code EY3600 input/output modules Function 

Analog Input 0 AI, CI, AI_Soft, CIF_Soft, CIV_Soft Measure / counter 

Analog Output 1 AO Positioning 

Analog Value 2 AI_Soft, AIA_Soft, CFB_Soft 

(AI_Soft) 

Setpoint 

Binary Input 3 BI, BI_Soft, DI, DI_Soft Alarm / State / BFB 0-I 

Binary Output 4 DO command 0-I 

Binary Value 5 DI_Soft, DIA_Soft, CFB_Soft 

(DI_Soft) 

command 0-I 

Loop 12 Loop + PID PID controller 

Multistate Input 13 DI, DI_Soft BFB 0-I-II-... 

Multistate Output 14 DO command 0-I-II-... 

Multistate Value 19 DI_Soft, DIA_Soft, CFB_Soft 

(DI_Soft) 

command 0-I-II-... 

This table is structured in accordance with the following rule:- 

To find out the BACnet object type for a particular MFA, the user should use its card 

code (DW 22), the HBG parameter (DW 33) and perhaps the number of projected BFB 

texts (DW 56 ff.) to find out the ‘multistateness’. 

A binary object is easier to use than a multistate object. Therefore, single-state and 

multistate commands or BFBs are differentiated and sorted out. 

If a soft address can be written by the management level, (setpoint/positioning value or 

switching command) it is implemented as an value object. 

If a soft address can only be read by the management level, (measured value, alarm, 

status or BFB), it is implemented as an input object. 


2 



Note on 'commandable' objects (Relinquish-Default): 

The mechanism for sending values as commands (Command with WriteProperty 

Service) to the BACnet server is described in section 1.14.5. The behaviour of the 

BACnet server with 'Relinquish Commands' (withdrawn command; empty priority array) 

is mentioned here as a note. 

Relinquish-Default property: there is a Relinquish-Default property for the output and 

value objects. This value in the Relinquish-Default property is written to the Present- 

Value if it has no values in it in the priority array (all NULL/ZERO) . 

As the EY3600 cannot specify a default value for modules in addition to the X input, the 

Relinquish-Default value corresponds to the Automatic value (DDC value). However, the 

Relinquish-Default value is only updated by the Automatic value if there is no value in 

the priority array and if a novaNet telegram is triggered by a value change or a Round 

Robin refresh telegram. 

If value objects are implemented without an Automatic value (without an X-connection; 

as setpoints with AIA_Soft or switching commands with DIA_Soft), the Relinquish- 

Default value will automatically match the last written value of a BACnet client (Present- 

Value). 

Output objects without an Automatic value always have value 0 for AO or FALSE for BO 

and 1 for MO. To obtain a Relinquish-Default on the EYK in the form of a constant as 

specified by BACnet, you can link the relevant modules (AO, DO, AIA_Soft, DIA_Soft) 

with soft addresses (AI_Soft, DI_Soft) parameterised as constants. 




2 

2.3.4 Link between BACnet object properties and 

input/output module parameters 

2.3.4.1 Analog input 

Property Datatype EYK AS 

Required properties 

Object-Identifier BACnetObjectIdentifier R MFA 

Object-Name CharacterString R HA 

Object-Type BACnetObjectType R KC 

Present-Value Real R 

Status-Flags BACnetStatusFlags R 

Event-State BACnetEventState R 

Out-Of-Service Boolean W 

Units BACnetEngineeringUnits R DIMY 

Optional properties 

Description CharacterString R Atxt 

Device-Type CharacterString R FC2 

Reliability BACnetReliability R 

Update-Interval Unsigned R 

Min-Pres-Value Real X 

Max-Pres-Value Real X 

Resolution Real R 

Profile-Name CharacterString X 

Optional properties conditional 

COV reporting supported 

COV-Increment Real W TRW 

Intrinsic reporting supported Out-Of-Range 

Time-Delay Unsigned R 

Notification-Class Unsigned R 

High-Limit Real W Lt 

Low-Limit Real W Lb 

Deadband Real R TRW 

Limit-Enable BACnetLimitEnable R 

Event-Enable BACnetEventTransitionBits R 

Acked-Transitions BACnetEventTransitionBits R 

Notify-Type BACnetNotifyType R 

Event-Time-Stamps BACnetArray[3] of BACnetTimeStamp R 

EYK : R = Read ; W = Write ; X = not supported 


2 



2.3.4.2 Analog output 






Present-Value Real W 





Priority-Array BACnetPriorityArray R 

Relinquish-Default Real R 



Device-Type CharacterString R FC2 


Min-Pres-Value Real R b 

Max-Pres-Value Real R a+b 

Resolution Real R 




















2 

2.3.4.3 Analog value 






Present-Value Real W 



























2 



2.3.4.4 Binary input 






Present-Value BACnetBinaryPV R 




Polarity BACnetPolarity R fBi 



Device-Type CharacterString R 




Texts 

Inactive-Text CharacterString R Txt0 

Active-Text CharacterString R Txt1 

Change-Of-State 

Change-Of-State-Time BACnetDateTime R 

Change-Of-State-Count Unsigned W 

Time-Of-State-Count-Reset BACnetDateTime R 

Active-Time 

Elapsed-Active-Time Unsigned32 X 

Elapsed-Active-Time-Reset BACnetDateTime X 

Intrinsic reporting supported Change-Of-State 



Alarm-Value BACnetBinaryPV R 









2 

2.3.4.5 Binary output 






Present-Value BACnetBinaryPV W 












Minimum-Off-Time Unsigned32 X 

Minimum-On-Time Unsigned32 X 


Texts 







Active-Time 



Intrinsic reporting supported Command-Failure 

Time-Delay Unsigned X 

Notification-Class Unsigned X 

Feedback-Value BACnetBinaryPV X 

Event-Enable BACnetEventTransitionBits X 

Acked-Transitions BACnetEventTransitionBits X 

Notify-Type BACnetNotifyType X 

Event-Time-Stamps BACnetArray[3] of BACnetTimeStamp X 



2 



2.3.4.6 Binary value 

















Minimum-Off-Time Unsigned32 X 

Minimum-On-Time Unsigned32 X 


Texts 







Active-Time 






Alarm-Value BACnetBinaryPV X 









2 

2.3.4.7 Multistate input 






Present-Value BACnetBinaryPV R 




Number-Of-States Unsigned R Txt 


Description CharacterString R 



State-Text BACnetArray[N] of CharacterString R Txt 






Alarm-Values List of Unsigned X 

Fault-Values List of Unsigned X 







2 



2.3.4.8 Multistate output 




















Intrinsic reporting supported Command-Failure 



Feedback-Value BACNetBinaryPV X 









2 

2.3.4.9 Multistate value 






















Alarm-Values List of Unsigned X 

Fault-Values List of Unsigned X 







2 



2.3.4.10 Loop 






Present-Value Real R 




Output-Units BACnetEngineeringUnits R DIMY 

Manipulated-Variable-Reference BACnetObjectPropertyReference R 

Controlled-Variable-Reference BACnetObjectPropertyReference R 

Controlled-Variable-Value Real R 

Controlled-Variable-Units BACnetEngineeringUnits R 

Setpoint-Reference BACnetSetpointReference R 

Setpoint Real R 

Action BACnetAction R fSLi 

Priority-For-Writing Unsigned R 




Update-Interval Unsigned R 

Bias Real R 

Maximum-Output Real R a+b 

Minimal-Output Real R b 





2 



Proportional 

Proportional-Constant Real W XP 

Proportional-Constant-Units BACnetEngineeringUnits R 

Integral 

Integral-Constant Real W TN 

Integral-Constant-Units BACnetEngineeringUnits R 

Derivative 

Derivative-Constant Real W TV 

Derivative-Constant-Units BACnetEngineeringUnits R 



Intrinsic reporting supported Floating-Limit 

Time-Delay Unsigned W Tdly 


Error-Limit Real W LtErr 







2 



2.3.5 Relationship of BACnet unit code to module 

parameter ‘unit of measurement’ 

So that the unit of an analogue value can be converted into the right BACnet unit code, 

the 4 characters of the module parameter DIM or DIMY have to be entered as follows:- 

Range Unit of measurement BACnet Abbreviation *) 

code 1 2 

Area square-metres 0 m2 m 2 

square-centimetres 116 cm2 cm 2 

square-feet 1 sqft ft2 

square-inches 115 sqin in2 

Currency currency1 105 CHF 

currency2 106 £ 

currency3 107 $ 

currency4 108 Euro 

currency5 109 cur5 






Electrical milliamperes 2 mA 

amperes 3 A 

ohms 4 Ohm 

kilohms 122 kOhm 

megohms 123 mOhm 

volts 5 V 

millivolts 124 mV 

kilovolts 6 kV 

Megavolts 7 MeV 

volt-amperes 8 VA 

kilovolt-amperes 9 kVA 

megavolt-amperes 10 MeVA 

volt-amperes-reactive 11 VAR 

kilovolt-amperes-reactive 12 kVAR 

megavolt-amperes-reactive 13 MVAR 

degrees-phase 14 °Ph 

power-factor 15 PF 

*) Upper/lower case is irrelevant. 




2 


code 1 2 3 

Energy joules 16 J 

kilojoules 17 kJ 

kilojoules-per-kilogram 125 kJKg 

megajoules 126 MJ 

watt-hours 18 Wh WStd 

kilowatt-hours 19 kWh 

btus 20 Btu 

therms 21 ther 

ton-hours 22 Th tStd 

Enthalpy joules-per-kilogram-dry-air 23 J/kg 

btus-per-pound-dry-air 24 b/lb 

btus-per-pound 117 btlb 

Entropy joules-per-degree-Kelvin 127 J/°K J°K 

joules-per-kilogram-degree- 128 Jk°K 

Kelvin 

Frequency cycles-per-hour 25 1/h 

cycles-per-minute 26 1/m 

hertz 27 Hz 

kilohertz 129 kHz 

megahertz 130 MHz 

per-hour 131 /Std /h 

Humidity 

grams-of-water-per-kilogramdry-air 

28 x gH2O 

percent-relative-humidity 29 %rF %rh %hr 

Length millimetres 30 mm 

centimetres 118 cm 

metres 31 m 

inches 32 in 

feet 33 ft 

Light watts-per-square-foot 34 W/f2 Wft2 

watts-per-square-metre 35 W/m2 

Lumens 36 lm 

Luxes 37 Lux Lx 

foot-candles 38 ftcd 

Mass kilograms 39 kg 

pounds-mass 40 lb lbs 

tons 41 t 



2 




code 1 2 3 4 

Mass Flow kilograms-per-second 42 kg/s 

kilograms-per-minute 43 kg/m 

kilograms-per-hour 44 kg/h 

pounds-mass-per-second 119 lb/s 

pounds-mass-per-minute 45 lb/m 

pounds-mass-per-hour 46 lb/h 

Power milliwatts 132 mW 

watts 47 W Watt 

kilowatts 48 kW 

megawatts 49 MeW 

btus-per-hour 50 bt/h 

horsepower 51 PS HP 

tons-refrigeration 52 tref 

Pressure pascals 53 Pa 

hectopascals 133 hPa 

kilopascals 54 kPa 

millibars 134 mbar 

bars 55 Bar 

pounds-force-per-square-inch 56 lbi2 

centimetres-of-water 57 cmWs 

inches-of-water 58 inH2 inwa 

millimetres-of-mercury 59 mmHg 

Centimetres-of-mercury 60 cmHg 

inches-of-mercury 61 inHg 

Temperature degrees-Celsius 62 °C degC 

degrees-Kelvin 63 °K degK 

degrees-Fahrenheit 64 °F degF 

degree-days-Celsius 65 °TC °dC °jC 

degree-days-Fahrenheit 66 °TF °dF °jF 

delta-degrees-Fahrenheit 120 d°F 

delta-degrees-Kelvin 121 d°K 

Time years 67 Y Year Jahr 

months 68 Mon Mois 

weeks 69 Week Woch Sem 

days 70 days Tag Jour 

hours 71 hour Std Std. heur 

minutes 72 min min. 

seconds 73 s sek. sec. 





2 


code 1 2 3 

Velocity metres-per-second 74 m/s 

kilometres-per-hour 75 km/h 

feet-per-second 76 ft/s 

feet-per-minute 77 ft/m 

miles-per-hour 78 mph m/h 

Volume cubic-feet 79 cuft ft3 

cubic-metres 80 m3 qm cum 

imperial-gallons 81 Igal 

litres 82 l 

us-gallons 83 Ugal 

Volumetric cubic-feet-per-second 142 ft3s 

Flow cubic-feet-per-minute 84 ft3m 

cubic-metres-per-second 85 m3/s 

cubic-metres-per-hour 135 m3/h 

imperial-gallons-per-minute 86 Igam 

litres-per-second 87 l/s 

litres-per-minute 88 l/m 

litres-per-hour 136 l/h 

us-gallons-per-minute 89 Ugam 

Other degrees-angular 90 °ang 

degrees-Celsius-per-hour 91 °C/h 

degrees-Celsius-per-minute 92 °C/m 

degrees-Fahrenheit-per-hour 93 °F/h 

degrees-Fahrenheit-per-minute 94 °F/m 

kilowatt-hours-per-square-metre 137 kWhm 

kilowatt-hours-per-square-foot 138 kWhf 

megajoules-per-square-metre 139 MJm2 

megajoules-per-square-foot 140 MJf2 

no-units 95 

parts-per-million 96 ppm 

parts-per-billion 97 ppb 

percent 98 % 

percent-obscuration-per-foot 143 %Oft 

percent-obscuration-per-metre 144 %O/m 

percent-per-second 99 %/s 

per-minute 100 /min 

per-second 101 /s /sek /sec 

psi-per-degree-Fahrenheit 102 psiF 

radians 103 rad 

revolutions-per-minute 104 rpm n/m 

Watts/square-metre-d-kelvin 141 wm2K 



2 





BACnet hardware (EYK) 

3 

3 BACnet hardware (EYK) 

3.1 Hardware platform 

The hardware platform for the BACnet communication card uses the Windows CE Version 

3.0 operating system. The interfaces that are supported are an RJ45 Ethernet connection 

for the BACnet/IP protocol on the one hand and, on the other, a novaNet290-compatible 

RJ11-novaNet interface for EY3600 datapoint access and a DB9 COM interface for 

configuration. 

3.2 Wiring diagram 

EYK 300 F001 

novaNet 

RJ-11 

a 

2 

b 

5 

Ethernet 

BACnet 

RJ-45 

Tx+ Tx- Rx+ Rx- 

1 2 3 4 5 6 7 8 

75 75 

Speed 

LI 

ACT 

1 DCD (IN) 

2 RD (IN) 

3 TD (OUT) 

4 DTR (OUT) 

5 GND 

6 DSR (IN) 

7 RTS (OUT) 

8 CTS (IN) 

9 RIN (IN) 

COM 1 

9 Pol. 

SUB-D 

1 2 3 4 5 

6 7 8 9 

DB9 Stecker 

RS 232 C Schnittstelle (DTE) 

A09734 

3.3 BACnet configuration 

The EYK 300 F001, EYK 220 F001 and EYK 230 F... require a one-off configuration as 

BACnet/IP server devices:- 

• ‘Device Instance’ number and name 

• Number of calendar and schedule objects 

• Time synchronisation 

• IP address, subnet mask, BACnet router functionality (BBMD, Foreign Device) 

• novaNet PC address 

• Assigned automation stations 

This is parameterised using the Sauter software tool ‘BACnet Server Configurator’. 

(see chapter configuration). 


3 


BACnet hardware (EYK) 

3.4 LED display for Ethernet interface 

Speed yellow 

Data transmission speed; is recognised automatically:- 

LED off: 10 Mbits/s 

LED on: 100 Mbits/s 

LI yellow Physical link established (Link) 

ACT yellow Transmission of BACnet protocol (Activity) 


UPS 

Power 

Receive 

Send 

a 

b 

a 

b 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 


BACnet in the network (topologies) 

4 

4 BACnet in the network 

(topologies) 

Below, you will find several examples of network topologies with BACnet automation 

stations and possible subordinate EY3600 automation stations with novaNet or other 

BACnet devices based on BACnet/IP. 

4.1 EYK as a native BACnet station 

The topology shows nova106 or nova220 as a native BACnet station:- 

The communication network on the automation level and on the management level is 

Ethernet with the BACnet/IP protocol. 

BACnet Client 


Ethernet 

nova106 mit 

EYK 300 F001 

nova220 

EYK 220 F001 

novaNet 

BACnet Server 

X 


Y 


Z 


UPS 

Power 

Receive 

Send 

a 

b 

a 

b 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

4 



4.2 EYK as a native BACnet head station 

The topology shows nova106 or nova220 as a native BACnet head station with 

subordinate novaNet stations. 

The communication network on the automation level with other BACnet-capable DDCs, 

or on the management level, is Ethernet with the BACnet/IP protocol. 

The main communication network with other EY3600 AS on the automation level 

remains the proprietary EY3600 novaNet system bus. For example, a BACnet head 

station can be installed inside the focal point of an installation. 



Ethernet 

nova106 mit 

EYK 300 F001 

nova220 

EYK 220 F001 

novaNet 


X 


Y 


Z 

novaNet 

novaNet 

Note: 

From BACnet server version 2.4 onwards, up to 100 subordinate automation stations 

can be connected to one novaNet. Even so, however, the BACnet head station cannot 

manage more than 1000 objects. The first readout of a large novaNet network and the 

automatic generation of the BACnet objects can take quite a long time (~ 2-3 minutes 

per automation station). 


UP S 

Power 

Receive 

Send 

a 

b 

a 

b 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 



4 

4.3 EYK as a native BACnet and novaNet 

station 

The topology shows nova106 and nova220 as native BACnet and novaNet stations: 

if the number of novaNet datapoints that are to be converted into BACnet objects is 

more than 1000, and if the bus may only be one novaNet segment for data exchange 

between all subordinate automation stations (e.g. due to a shared 'Common'), the 

following topology applies:- 



Ethernet 

nova106 mit 

EYK 300 F001 

nova220 

EYK 220 F001 


X 


Y 


Z 

novaNet 

novaNet 

Note: 

You can assign which AS belongs to which BACnet head station in the BACnet server 

configurator with 'Integrate AS addresses'. In addition, you can individually assign each 

module with the parameter system number to the corresponding BACnet AS with the 

same BACnet system number. 


Power 

Re ce ive 

UPS 

a 

b 

a 

b 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

1 

2 

3 

4 

Send 

Send 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

1 

2 

3 

4 

5 

6 

7 

8 

Send 

Send 

9 

10 

11 

12 

13 

14 

15 

16 

ESC 

4 



4.4 EYK as a BACnet station with buscompatible 

devices (external 

protocols) 

The topology shows novaCom and nova230 as native BACnet stations, but they do not 

have the additional ability to integrate BACnet-compatible, bus-compatible 

('communicative') devices into the BACnet automation station. 

Shown here: novaCom for Modbus consisting of EYU 108 F001, EYK 300 F001, 

EYI 103 F001, EYI 280 F020 and EYI 288 F001, and nova230 for M-Bus 

(EYK 230 F010) 



Ethernet 

novaCom mit 

EYK 300 F001 

nova230 

EYK 230 F010 

novaNet 


X 


Y 


Z 

novaNet 

Modbus (RS485) 

M-Bus 



BACnet server configurator 

5 

5 BACnet server configurator 

BACnet communication card EYK 300 F001 and/or BACnet automation stations EYK 

220 F001 and EYK 230 F… have to be configured. 

The parameterisation is carried out with Sauter's 'BACnet server configurator' software 

tool. 

The configuration is transmitted via the serial COM interface (DB9 plug) or via the 

Ethernet/IP interface, and is stored there in a flash memory so that it is safe against 

network outages. Data transfer via IP is handled via TCP port 51966, which is 

permanently set. 

Notes: 

• After switching on, the card needs at least 20 seconds until it is able to accept the 

configuration. 

• BACnet servers (nk.lzh) with version status prior to 2.4 must be engineered via the 

serial interface, for reasons of compatibility. 

5.1 Serial COM connection 

The cable used is identical to the novaNet291 router cable (MZ. 368301.001). 

The communication parameters between the PC and the BACnet communication card 

must be set to the standard settings (9600 Bd, 8 bits, without parity, 1 stop bit, without 

handshake). 

EYK 300 

novaNet 

DB9 - DB9 

PC 

(DTE) 

1 

2 

DCD 

RD 

DCD 

RD 

1 

2 

EYK 300 

(DTE) 

3 

TD 

TD 

3 

DB9 

Male 

4 

5 

6 

DTR 

GND 

DSR 

DTR 

GND 

DSR 

4 

5 

6 

DB9 

Male 

7 

RTS 

RTS 

7 

8 

CTS 

CTS 

8 

9 

RI 

RI 

9 

B09828 

The cable used is identical to the novaNet291 router cable (0368301 001). 


5 



5.2 Installing the BACnet server 

configurator 

The program is installed using the installation program supplied. 

To install the BACnet server 

configurator, start the ‘Setup’ 

program via ‘Start | Run’ in the 

relevant installation folder or on 

the CD. 

The setup program then shows 

its start window. Press ‘Next >‘ to 

continue the installation. 




5 

The setup program installs the 

software in the folder stated. Use 

the ‘Browse...’ button if you want 

to change the folder. Press 

‘Next >‘ to continue the installation. 

The setup program now states 

the name of the program group. 

This can also be changed if you 

so wish. Press ‘Next >‘ to 

continue the installation. 

The proposed (or changed) 

settings are all displayed 

together for verification before 

the actual installation takes 

place. Press ‘Next >‘ to start 

installing the program 

components. 


5 



When the installation has been 

concluded, a message to this 

effect appears on screen. 

The computer should then be restarted. 

Press ‘Finish’ to carry 

out the option of your choice. 

Note: 

The Setup programme installs files BnsCfg.exe, BnsEncr.dll and tExeDlg.dll from the 

\Program directory into the selected programme directory, and files MFC42.dll and 

MSVCRT.dll into the Windows system directory. 

If the standard programme directory is not used, it may happen that the installed 

programme links have to be adjusted manually. 




5 

5.3 Description of the configurator 

After you call up the BACnet Server configurator (BnsCfg.exe) you 

are offered a choice of six tabs: "Device, Objects, Network, EY3600, 

Settings" and "BBMD". 


5 






5 

5.3.1 Description of tabs 

5.3.1.1 Register „Device“ 

The EYK 'Device object' is a local object that is generated using the EYK Device tab. 

After starting up, the basic rule is that the BACnet server is not time-synchronised. 

Synchronisation can be implemented both by reading the time from an AS and also by 

using the BACnet time synchronisation of a BACnet time master. Synchronisation using 

a BACnet time master takes precedence here. 

Entry Description Input range 

Device 

Instance number 

BACnet instance number of the AS 3600-BACnet 

server 

1...2097151 

Name Name of BACnet server (Device object) max. 15 1) 

Description Description of the AS 3600-BACnet server max. 48 

Time 

synchronisation 

Disabled 

Allow from every 

time master 

Only allow from 

time master with 

specified MAC 

address 

MAC address 

This can be used to disable the time 

synchronisation for the server. 

With this option, every BACnet client (time master) 

can trigger a time synchronisation. 

If this option is used, a time synchronisation can 

only be triggered by a BACnet client with a specified 

MAC address (the network card address). 

With Ethernet, the MAC address is entered as 

6 hexadecimal digits separated by commas. 

1) 

Remark: BACnet systems from other manufacturers sometimes have a limit on the 

length of the name here, i.e. the name should generally be kept as short as possible. 

The picture shows the 

permitted characters. This 

message appears if you make 

an incorrect entry. 


5 



5.3.1.2 "Objects" Register 

All valid novaNet datapoints are converted into a BACnet object in which the "object 

name" property corresponds to the novaNet datapoint house address by default (%A). 

So as not to limit the "object name property" to 24 characters, it is possible to extend it 

with extra text and the novaNet datapoint protocol zone. 

Entry 

Description 

Format for object 

name 

Object name 

Characters 

Code to generate the object names. House address (%A) 

can be extended with freely definable text and protocol 

zone (%Z) - default: %A 

If this option is enabled, a minus sign in the object name is 

automatically replaced by an underscore. 

Assignment of 

Notification Class 

Static assignment 

Assignment via 

protocol category 

Automatic assignment defined via object type in five 

Notification Classes 

Assignment of instance number from the protocol category 

(0..14) for the respective MFA plus offset 10 

Hours-run meters 

Create objects 

Name extension 

An additional BACnet analogue input object is created for 

all hours-run meters enabled in the AS 

AS house address house address extension for the 

associated hours-run meter object (Default: -HRC) 




5 

5.3.1.3 "Network" Register 

An Ethernet network interface is used for communication with other BACnet devices. 

Communication is handled via the BACnet/IP transport protocol. The EYK 300 F001 

and/or the EYK 220 F001 require an IP address (mandatory). 

The EYK integrates an access-protected FTP server. The user name and the password 

can be modified on this tab. 


Address 

IP address 

Subnet mask 

Standard gateway 

IP address of the BACnet server 

Subnet mask of the BACnet server 

IP address of a gateway (if one is needed) 

Port 

Port ID 

Network number 

UDP port 

Access via FTP 

User name 

Change password 

Allow access via 

Telnet 

Number of the port that is used for 

transmission. 

Number of the network that is used for 

transmission. 

Number of the UDP port that is used for 

transmission. 

The default user name for the integrated FTP 

server is "Sauter". Upper/lower case is 

ignored. 

The default password for the integrated FTP 

server is "12345". Upper/lower case is taken 

into account. 

If this option is enabled, access to EYK is 

possible via Telnet. 

1 ... 255 

1 ... 65 534 

BAC0 ... BACF 

(Hex) 

Max.32 char. 

unlimited 


5 



5.3.1.4 The ‘EY3600’ tab 

The connection to the automation station is made via the novaNet using an EYS290- 

compatible interface that is integrated on the card. 

The EYK 300 F001 must have a novaNet PC address (31744 ... 31999). 


EY3600 parameters: 

novaNet address 

BACnet system no. 

Allow novaNet 

commands 

Integrate AS address: 

[Text field] 

Read stored MFA 

data in again at 

startup *) 

BACnet server novaNet PC address 

Default = 31999 

System number for assigning the MFA to 

BACnet, default = 0 

This option must be enabled if AS outputs are 

also to be changed via a manual user panel or 

other possible means of control. 

Engineering of the EY3600 AS to be entered for 

BACnet; if the input field is empty, all connected 

EY3600 AS are entered for BACnet (default). 

Example: 4,6,10-15 means that AS 4, 6 and 10 

to 15 are entered for BACnet. 

This option must be enabled to force a 

complete scan of the MFA data at every new 

startup. If this option is not enabled, MFAs will 

only be newly read in if their time stamp has 

changed since the last save. 

31744 ... 31999 

0 ... 3 

max. 500 

characters 

*) 

Technical note: 

The BACnet server has been revised and optimised from Version 2.4 onwards so that multiple stations (up 

to 100) can also be managed. 

This allows problem-free use of a BACnet station as the 'head station' of a fairly large EY3600 novaNet 

network with several 'substations' with EY3600 ecos room controllers, for example. (See also section 4.2.) 

Nevertheless, reading in the EY3600 stations (AS, ecos, novaFlex) for the first time still always takes about 

2-3 minutes per station. If a network of this kind has been read into the BACnet server, you can 

parameterise the EYK with the BACnet server configurator so as to eliminate the entire read-in when the 

EYK is switched on, if necessary. 

Changes to the novaNet, e.g. stations added, are still recognised and the BACnet server will automatically 

update the changes. 




5 

5.3.1.5 "Settings" Register 


File generation 

[Text field] 

After a change to the engineering data, for 

example after newly scanning the MFAs or 

after describing a Schedule object, it is 

necessary to save the data on the flash 

disk. After a change of this kind, there is a 

waiting period lasting the time indicated in 

seconds, without any new modifications 

taking place, before the data are written. 

- Delayed saving for the persistent data. 

10..86400 

seconds 

[Text field] Delayed saving for EDE data 10..86400 

seconds 

Enable error recording 

If this option is enabled, errors occurring at 

runtime are recorded in two alternating files 

and are stored on the flash disk so that they 

are safe against network outages. The 

maximum size of a file is about 500kByte in 

each case, and the file is saved with 

\flashfx\bnsErrA.txt or bnsErrB.txt as the 

filename. In addition, start information and 

errors are saved in \flashfx\bnsStart.txt. 

These files can be downloaded via FTP for 

system analysis. 

.. 

Create schedule and calendar objects 

Number of schedule 

objects 

Number of calendar 

objects 

Number of BACnet schedule objects 

created in the server 

Number of BACnet calendar objects created 

in the server 

0...100 

0...40 


5 



Notification of engineering 

change 

Automatic reset after: 

You can make an entry in minutes for the 

delayed automatic reset of 'Engineering 

Changed' Present-Values in the Project 

Engineering object and the 'Restart' 

Present-Values in the Restart-Indicator 

object. 

2..60 

minutes 

5.3.1.6 "BBMD" Register 

This tab can be used to enable the BBMD (BACnet Broadcast Management Device) 

function or the FD (Foreign Device) function. The BBMD function can only be enabled 

once per network. 


BBMD 

Enable BACnet 

Broadcast 

Management Device 

function 

Broadcast Distribution 

Table (BDT) 

If this option is set, the BBMD functionality is 

enabled and entries can be made in the 

Broadcast Distribution table. 

All BBMDs with which the BACnet server 

should communicate must be engineered in the 

BDT. Use the 'Add' button to add another 

BBMD to the BDT. The 'Edit' button allows you 

to change a previously marked BBMD entry and 

the 'Remove' button deletes it (Caution: the 

entry is deleted without an enquiry.) 




5 


Use direct 

broadcasting in own 

subnetwork (One 

Hop) 

You should enable this option if the connected 

router transports so-called 'Directed 

Broadcasts'. Ask the responsible network 

administrator about this setting. 

Foreign Device table 

Enable 

Number of FDT 

entries 

Allows Foreign Devices to log onto the BBMD; if 

it is enabled, the 'Number of FDT entries' input 

box is activated. 

Maximum number of Foreign Devices that can 

log onto the BBMD. 

max. 16 

5.3.2 Description of menu items 

File - New 

Ctrl+N 

Enables you to create a new configuration file. 

File – Open... 

Ctrl+O 

Enables you to open an existing configuration file. 

File – Save 

Ctrl+S 

Enables you to save the configuration file that is currently open. If the file is one that has 

just been newly created, the ‘File-Save’ dialog box appears, allowing you to enter the 

folder and the file name. In the case of an existing file, it is saved directly. 

File – Save as... 

Enables a newly created or an existing configuration file to be saved under a folder and 

file name of your choice. 

File – Send configuration 


5 



1. Transmission with serial interface: 

Enables the present configuration to be sent via the chosen interface to the AS 3600- 

BACnet server. Before sending, you are asked to 

confirm. On pressing the ‘Yes’ button, the sending 

operation is started and the window shown here on 

the right appears on the screen. Press ‘No’ if you want 

to abort the operation. On pressing the ‘Yes’ button, 

the ‘Execute’ dialog appears, showing the progress of 

the sending operation. Use the ‘Details’ button to get 

more information on the sending operation. The 

activated option ‘Automatically close the dialog box 

after successful completion’ closes the dialog box if 

everything was sent OK. 

2. Transmission with Ethernet interface (TCP/IP): 

After acknowledging the security enquiry 

positively (as for a serial connection), the 

network is searched for BACnet servers. The 

devices that are found are 

shown for selection. After you 

mark them and press the OK 

button, the data are 

transmitted and the Send 

operation is displayed as for a 

serial interface. 




5 

File – Read configuration 

Enables the present configuration to be read via the chosen interface by the AS 3600- 

BACnet server. 

File – Settings... 

Enables you to choose the serial interface 

or the Ethernet interface (TCP/IP 

connection) via which the configuration 

data are to be read or sent. 

Furthermore, you can use the ‘Reset after 

download’ option to decide whether the 

EYK 300 F001 should be reset after the 

sending operation has finished. 

The ‘Program start | Load last configuration’ option enables the configuration file that 

was edited most recently to be loaded automatically. 


5 



File – Last file 

This menu item is inscribed with ‘Last file’ as long as no file has been 

opened or saved. This section shows the last four files to be edited, so 

that you can access them more easily. 

In the example shown here on the right (marked with a red bar), the file 

AS3600_02 was the last one to be used; preceded by the file 

AS3600_01. The extension ‘INI’ is set by default. 

File - Close 

This menu item closes the EYK 300 configurator. If you have made changes but have 

not saved them, you are asked whether you want to save the changes before closing. 

View – Symbol bar 

This menu item lets you hide or show the symbol bar. 

View – Status bar 

This shows or hides the status 

bar at the bottom of the window. 

Column 1 of the status line shows either the ‘Ready’ status or a description of the 

chosen menu item. Column 2 shows the currently-set interface via which the 

configuration can be read or sent. Other columns show the status of the ‘Caps Lock’, 

‘Num Lock’ and the ‘Scroll’ button. 



BACnet system objects 

6 

6 BACnet system objects 

The BACnet server on the BACnet communication card manages three system objects 

and (as already mentioned), an AS status object for each subordinate EY3600 

automation station, ecos or novaFlex. 

6.1 Create device object 

The EYK Device object is a local object that is parameterised with the help of the 

'Device' tab in the BACnet server configurator. 


6 



As soon as the configuration of the BACnet card is downloaded with the BACnet server 

configurator and the BACnet server has completed a full read-in (scan) of an automation 

station, the Device object can be created in the BACnet server. 

6.1.1.1 Device Object 

Property Datatype EYK 


Object-Identifier BACnetObjectIdentifier R 

Object-Name CharacterString R 

Object-Type BACnetObjectType R 

System-Status BACnetDeviceStatus R 

Vendor-Name CharacterString R 

Vendor-Identifier Unsigned16 R 

Model-Name CharacterString R 

Firmware-Revision CharacterString R 

Application-Software-Version CharacterString R 

Protocol-Version Unsigned R 

Protocol-Revision Unsigned R 

Protocol-Services-Supported BACnetServicesSupported R 

Protocol-Object-Types-Supported BACnetObjectTypesSupported R 

Object-List 

BACnetArray[N] of 

R 

BACnetObjectIdentifier 

Max-APDU-Length-Accepted Unsigned R 

Segmentation-Supported BACnetSegmentation R 

APDU-Timeout Unsigned R 

Number-of-APDU-Retries Unsigned R 

Device-Adress-Binding List of BACnetAdressBinding R 

Database-Revision Unsigned R 


Location CharacterString R 


List-of-Session-Keys List Of BACnetSessionKey X 





6 



Segmentation supported 

Max-Segments-Accepted Unsigned R 

APDU-Segment-Timeout Unsigned R 

Virtual Terminal Supported 

VT-Classes-Supported List of BACnetVTClass X 

Active-VT-Sessions List of BACnetVTSession X 

Service "TimeSynchronization Execute" is supported 

Local-Time Time R 

Local-Date Date R 

Service "UTCTimeSynchronization Execute" is supported 

UTC-Offset Integer R 

Daylight-Savings-Status Boolean R 

Required if device is a TimeMaster 

Time-Synchronization-Recipients List of BACnetRecipient 

X 

Required if device is a MS/TP master node 

Max-Master Unsigned (1..127) X 

Max-Info-Frames Unsigned X 

Backup and Restore Procedures supported 

Configuration-Files 

BACnetArray[N] of 

X 

BACnetObjectIdentifier 

Last-Restore-Time BACnetDateTime X 

Backup-Failure-Timeout Unsigned16 X 

"SubscribeCOV Execute" or "SubscribeCOVProperty Execute" supported 

Active-COV-Subscritpions List of BACnetCOVSubscriptions R 


6.1.2 'Reinitialize Device' for BACnet device 

BACnet supports a variety of device management functions that can be triggered using 

the Device object. The BACnet server supports the ReinitializeDevice service. This 

function makes it possible to restart the BACnet server. Values Coldstart and Warmstart 

are accepted as BACnet service parameters. Other parameters are not supported and 

they will all be rejected. 

Coldstart: 

Warmstart: 

This triggers a reset of the EYK. The system is rebooted. 

This triggers a completely new read-in of the MFA engineering data for all 

connected EY3600 stations. 


6 



6.1.3 Time synchronisation for the BACnet device 

The BACnet server supports the BACnet TimeSynchronisation and 

UTCTimeSynchronisation services. The BACnet server is the performing service (i.e. 

not BACnet time-master but time-slave). The possibility of time synchronisation via 

BACnet can be set with the BACnet server configurator. 

Note on implementing the service: 

The EYK platform realtime clock is not battery-buffered. It follows that the system time 

and date for a cold start (after a network failure) are always set to the corresponding 

initialisation value of the system BIOS. This means that the system is basically not timesynchronised 

after startup. Synchronisation can be performed both by reading the time 

from an EY3600 AS and also by using the BACnet time synchronisation from a BACnet 

time-master. Synchronisation via a BACnet time-master takes precedence here. If no 

time synchronisation has taken place via BACnet, the time stamp for the first AS that is 

recorded will be used for this purpose. After the first time synchronisation via BACnet, 

the time stamp of the AS is permanently ignored. Moreover, all EY3600 AS are 

synchronised with the time communicated by BACnet via novaNet broadcasting. 

6.2 The 'Project engineering' object 

When commissioning takes place, there is often a need to make changes in relation to 

the engineering that was originally drafted on paper; this means that a BACnet object list 

that was once valid is changed again, and the logged-on BACnet clients can no longer 

access the original data, or can only do so to a limited extent. 

A separate object (Binary Input; object name Engineering-Change; instance number 1) 

makes it possible to identify changes to the engineering and to notify them automatically 

via COV or Event Notification. 

The current engineering status is stored in the Database-Revision property, in the 

Device object, as a consecutive number. If the value of this property changes, the 

Present-Value of Engineering-Change is set from Inactive to Active. Clients that are 

logged on via COV subscription or via Intrinsic-Reporting by means of the Notification 

Class 3 System Events object are then automatically notified of this event (Notify 

type=1). 

Present-Value = 0 Project Engineering - No Changes 

Present-Value = 1 Project Engineering - Engineering Changed 

The Active status can be reset via the BACnet Acknowledge Alarm service on the client 

side; as an alternative, a timeout that can be configured with the BACnet server 

configurator is also implemented, and after it has expired, the status of the Present- 

Value is automatically set to Inactive. 




6 

6.3 The 'AS status' object 

For every EY3600 automation station that is recorded on the BACnet communication 

card, an additional object (type: Multistate input) is generated, reflecting the status of the 

relevant AS. The object name takes the object from the house address of the 

automation station. If no house address is assigned, the default object name is 'AS'+AS 

address. Two statuses have initially been implemented for the object: 

Present-Value = 1 AS Status - Offline (AS switched off) 

Present-Value = 2 AS Status - Online (AS switched on) 

The object instance number is calculated as follows: 

'AS Status' object instance = AS address * 1000 + 256 

As well as the usual method of notifying their value changes (COV), the 'AS Status' 

objects are also able to notify them as alarms via Intrinsic-Reporting using the 

Notification Class 3 System Events object (Notify type=0). In this case, 'Online' status is 

treated as normal and 'Offline' is treated as off-normal. To generate an alarm for the 

'Offline' status, it is entered as an element in the list of alarm values. 

6.4 The 'Restart-Indicator' object 

From BACnet server version 2.4 onwards, a 'Restart-Indicator' object (type: Binary input) 

is created automatically in every BACnet AS; this indicates a BACnet server restart 

triggered by a power failure or a ReinitializeDevice. This system object offers a generally 

valid possibility for client-side recognition and acknowledgement of a cold start by the 

BACnet server. 

After a BACnet server power failure, all previously logged-on COV subscriptions are 

lost. This phenomenon is usually counteracted by a limited lifetime for logons of this 

type, and by having the connected BACnet clients log on again cyclically. Firstly, 

however, the logon of a correspondingly high number of subscriptions leads to a high 

load on the network and secondly, a long subscription lifetime entails the uncertainty of 

having to live without updated values after a brief server outage. This object allows 

optimization of renewed BACnet client-side logon. 

The 'Restart-Indicator' object is implemented as a binary input object; after startup, its 

Present-Value changes to Restart, which also corresponds to the alarm value for this 

object. 

Present-Value = 0 Device Restart-Indicator - Operational (device is running) 

Present-Value = 1 Device Restart-Indicator - Restart (device was restarted) 

In addition to the usual method of notifying the value change (COV), the transition to 

Restart status can be sent as an Event (Notify type=1) to all BACnet clients entered in 


6 



the Recipient List of the Notification Class 3 System Event via Intrinsic-Reporting. 

According to choice, the status can be reset to Operational either by acknowledging the 

event or after the time interval that is also entered for the 'Engineering-Change' 

notification after the server starts up. 



Parameterising the AS with CASE FBD 

7 

7 Parameterising the AS with CASE FBD 

To create an MFA in an adequate BACnet object, you need a projected house address 

and the successful conversion of the card code, manual-operating unit code and the 

number of projected BFB texts, in a valid BACnet object type. 

Incorporation of MFA’s with a projected house address into the BACnet object list is also 

controlled by the BACnet System ID. If this ID does not match the BACnet System ID 

(0... 3) configured for the EYK 300 F001 in question, the corresponding MFA will not be 

processed. 

For an individual assignment of alarms to Event Notification Classes (Notification Class 

objects), the protocol category (PC) must be set in the modules from 0..13 (or 14) (see 

section 9). 

So that an AS-MFA is implemented as a ‘BACnet Object’, the following parameters 

should be set using the relevant CASE FBD input/output module. 

7.1 Visualisation and operating 

The BACnet Analogue Input object can only be visualised by a BACnet client 

(management level) and should be used for visualising measured values or counter 

readings. 

7.1.1 AI parameters 

HA Identification 

Atxt Address text 

DIMY Dimension (unit of measurement) 

TRW Threshold width 

SNr System number System 0 

7.1.2 AI_Soft parameters 



DIMY Dimension 

fSP Input value from control panel No 




7 



7.1.3 CI parameters 

WT Impulse divider 



DIM Dimension 



7.1.4 CIF_Soft parameters 

WT Impulse divider 



DIM Dimension 



7.1.5 CIV_Soft parameters 



DIM Dimension 






7 

7.1.6 Example 

CASE FBD: In the AS (novaNet address 01), MFA 00 has been parameterised with an 

AI module for visualising measured values. 

EYK: This AI module is then implemented as an analog input with instance number 1000, 

as a BACnet object. 


7 



7.1.7 Hours-run counter 

If the hours-run counter for a datapoint is enabled and object generation is also enabled, 

an additional BACnet Analogue Input object is also implemented with the same instance 

number, address text and house address, with the extension that was entered in the 

BACnet server configurator (see the following example). 

7.1.8 Example 

CASE FBD: in the AS (novaNet address 01), MFA 72 was parameterised with a BI_Soft 

module for a status with hours-run counter visualisation. 

EYK: for this BI_Soft module, two BACnet objects - one binary input and one analogue 

input - are then implemented with instance number 1072. 




7 

7.2 Analog output object 

The BACnet Analogue Output Object can be visualised and operated by the BACnet 

client (management level), and should be used for manual positioning values, 

specification to a hardware datapoint. 

7.2.1 AO parameters 






7.3 Analog value object 

The BACnet Analogue Value object can be visualised and operated by a BACnet client 

(management level), and should be used for manually specifying setpoints on a software 

datapoint. 

7.3.1 AI_Soft parameters 




fSP Input value from control panel Yes 



7.3.2 AIA_Soft parameters 







7 



7.3.3 CFB_Soft parameters 

The CFB output must be connected with a CFB input (instruction). 






7.3.4 Example 

CASE FBD: In the AS (novaNet address 01), MFA 65 has been parameterised with an 

AI_Soft module for a setpoint setting. 

EYK: This AI_Soft module is then implemented as an analog value with instance 

number 1065, as a BACnet object. 

Enter setpoint: Enter 20.0 at the ‘Property Present value’. 

The value 20.0 equates to a temperature setpoint of 20.0 °C. 




7 

7.4 Binary input object 

The BACnet binary input object can be visualised only by the BACnet client 

(management level). It should be used for alarm, status or single-state binary feedback. 

7.4.1 BI parameters 

Visualisation applies only to output fC8 (Bit 31). 



CPB1 CP release Alarm or Status 

Txt0 Text Alarm On/Status Off 

Txt1 Text Alarm Off/Status On 


7.4.2 BI_Soft parameters 

fALSt Alarm/Status flag Alarm or Status 



CPB1 CP release Alarm or Status 

Txt0 Text Alarm On/Status Off 

Txt1 Text Alarm Off/Status On 


7.4.3 DI parameters 



CPB2 CP release Yes 

Txt0 BFB text stage 0 



7.4.4 DI_Soft parameters 



CPB2 CP release BFB 

CTxt0 BFB text stage 0 




7 



7.4.5 Example 

CASE FBD: In the AS (novaNet address 01), MFA 68 was parameterised with a BI_Soft 

module for alarm visualisation. 

EYK: This BI_Soft module is then implemented as a binary input with instance number 

1068, as a BACnet object. 

7.5 Binary output object 

The BACnet binary output object can be visualised and operated by the BACnet client 

(management level). It should be used for manual single-state switching command to 

hardware data point. 

7.5.1 DO parameters 



CTxt0 Command text stage 0 


fCP0 Command release stage 0 






7 

7.5.2 Example 

CASE FBD: In the AS (novaNet address 01), MFA 32 was parameterised with a DO 

module for a single-state switching command. 

EYK: This DO module is then implemented as a binary output with instance number 1032, 

as a BACnet object. 

Enter switching command: enter 0,1 or NULL for the ‘Property Present Value’. 

• Value 0 equates to a switching command with Stage 0 

• Value 1 equates to a switching command with Stage 1 

• The value NULL denotes that there is no switching command and positions the 

relevant MFA to ‘Automatic’. 


7 



7.6 Binary value object 

The BACnet Binary Value Object can be visualised and operated by the BACnet client 

(management level) and should be used for a manual single-stage switching command 

on a software datapoint. 

7.6.1 DIA_Soft parameters 











CPB2 CP release Command 







Output cCFB must be connected with a cCFB output (instruction). 











7 

7.7 Multistate input object 

The BACnet Multistate Input object can only be visualised by the BACnet client 

(management level) and should be used for multi-stage binary feedback. 

7.7.1 DI parameters 

HA 

Identification 

Atxt 

Address text 



Txt1-6 BFB text stage 1-6 



HA 


Atxt 

Address text 



CTxt1-6 BFB text stage 1-6 


7.8 Multistate output object 

The BACnet multistate output object can be visualised and operated by the BACnet 

client (management level). It should be used for manual multi-state switching command 

to hardware data point. 

7.8.1 DO parameters 

HA 


Atxt 

Address text 


CTxt1-6 Command text stage 1-6 


fCP1-6 Command release stage 1-6 



7 



7.8.2 Example 

CASE FBD: In the AS (novaNet address 02), MFA 37 was parameterised with a DO 

module for a multi-state switching command. 

EYK: This DO module is then implemented as a multistate output, with instance 

number 2037, as a BACnet object. 

Enter switching command: enter 1 to 8 or NULL for the ‘Property Present Value’. 

• A value of 1 equates to a switching command with Stage 0 



• ... 


• The value NULL denotes that there is no switching command and positions the 

relevant MFA to ‘Automatic’. 




7 

7.9 Multistate value object 

The BACnet multistate value object can be visualised and operated by the BACnet client 

(management level). It should be used for manual multi-state switching command to 

software data point. 

7.9.1 DIA_Soft parameters 

HA 


Atxt 

Address text 







HA 


Atxt 

Address text 

CPB2 CP release Command 







Output cCFB must be connected with a cCFB input (instruction). 

HA 


Atxt 

Address text 







7 



7.10 Loop object 

The BACnet loop object maps a PID controller loop. The three constants – Proportional, 

Integral and Derivative - can be visualised and changed by the BACnet client 

(management level). 

Note: 

So that the loop object is implemented by the EYK 300, the PID controller has to be 

connected to the loop module as follows. In addition, the AI (Controlled_Variable), 

AI_Soft (Setpoint) and AO (Manipulated_Variable) must also be converted into BACnet 

objects. 

Hinweis: 

Ab CASE FBD Version 5.1 SR2+ kann auch ein AIA_Soft (oder AI_Soft) als 

Manipulated_Variable verwendet werden. Ein AI_Soft ist jedoch nicht zu empfehlen, da 

das fSP-Flag freigeschaltet werden müsste, damit es ein Analog Value (AV) Objekt gibt; 

doch somit könnte auch eine andere novaNet Bedienung dieses AV Objekt verstellen. 

7.10.1 Loop parameters 

HA 

House address 

Atxt 

Address text 

DIMXP 

Proportional_Constant_Units 

TRW 

Half raster width 


XP 

Proportional_Constant 

TN 

Integral_Constant 

TV 

Derivative_Constant 

LtErr 

Error_Limit 

Tdly 

Time_Delay 



Historical data recording with BACnet 

8 

8 Historical data recording with BACnet 

BACnet uses Trend Log objects to implement the storage of historical data. The Trend 

Log objects are local EYK objects that are created or deleted dynamically with the help 

of a BACnet client. The Trend Log object can record a property from an internal or an 

external BACnet object. The stored data are read by a BACnet client using the 

'ReadRange' service. The EYK can manage up to 50 Trend Log objects dynamically. A 

maximum of up to 10,000 historical data entries can be stored on the EYK. 

8.1 Create a Trend Log object 

The Trend Log object has to be created with a BACnet client which supports the 'Create 

Object' service. For example, you can use the novaPro Open BACnet Configuration 

Console (BCC) or the BACnet client tool. 

Notes: 

• as BACnet client-Tool (BACtool.exe) ist ein kleiner BACnet client basierend auf dem 

Cimetrics BACstac 4.x und wird mit dem BACnet-Server Konfigurator mitgeliefert. 

Das BACnet client-Tool unterstützt die Services "Create Object" und "Delete Object", 

damit dynamisch erzeugbare Objekte in einem BACnet Server erstellt werden 

können. Die Objekte werden mit Default Properties vorgegeben und können 

anschliessend von einem BACnet client angepasst werden. Es ist nicht möglich eine 

Liste von Initialwerten (List of Initial Values) zu übergeben. 

Da der BACnet OPC Server von Cimetrics/MBS das dynamische Anlagen von 

Objekten nicht unterstützt, ist dieses BACnet-Client Tool als Ergänzung zu diesem 

BACnet OPC Server gedacht. Weitere Hinweise zum BACnet-Client Tool können 

dem Anhang im Kapitel 18 entnommen werden. 

• Dynamic creation of BACnet objects with a specified list of initial values is possible 

with novaPro Open BCC from version 2.1 onwards. 

• The Trend Log object in version 2.4 is implemented according to BACnet Protocol 

Revision 1.2. 

The relevant 'Object Properties' for a Trend Log object have to be configured correctly 

and can also be changed by a BACnet client during operation: 

• Log-Device-Object property: 

This property defines which property is recorded, by which object and from which 

device. 

• Log-Enable: 

This property turns recording on or off. 


8 



• Start-Time, Stop-Time: 

These properties define when the recording is turned on or off respectively. If 

wildcards (*) are included in a time or date field in these properties, turning on or off 

is ignored. 

• Buffer-Size: 

Buffer-Size specifies the number of data records that can be stored in this Trend Log 

object. The default value is 100. 

• Notification-Threshold: 

Notification-Threshold defines when an Intrinsic-Reporting Buffer-Ready is triggered. 

• Stop-When-Full: 

If Stop-When-Full is set, no more values will be stored and Log-Enable is switched 

off. If Stop-When-Full is not set, the oldest value from the buffer disappears and the 

new value is added (FIFO). 

• Log-Interval specifies the periodic interval in 1/100ths of a second at which the 

referenced property is recorded. If the value is 0, recording will be performed with 

COV Reporting using a COV subscription for the referenced property. In most cases, 

this is the Present-Value with which the 'Change-Of-State' (COS) of a status flag is 

also recorded. 

• COV-Resubscription-Interval: 

If a COV property is recorded by an external device (Remote Device) with the Trend 

Log object, the interval for logging back on must be indicated in seconds. 




8 

8.2 Trend Log Object 

Property Data type EYK 



Object-Name CharacterString W 


Log-Enable Boolean W 

Stop-When-Full Boolean W 

Buffer-Size Unsigned32 W 

Log-Buffer List of BACnetLogRecord R 

Record-Count Unsigned32 W 

Total-Record-Count Unsigned32 R 



Description CharacterString W 

COV-Resubscription-Interval Unsigned W 

Client-COV-Increment BACnetClientCOV R 



Required when monitored property is a BACnet property 

Start-Time BACnetDateTime W 

Stop-Time BACnetDateTime W 

Log DeviceObjectProperty BACnetDeviceObjectPropertyReference W 

Log-Interval Unsigned W 

Intrinsic-Reporting supported Buffer-Ready 

Notfication-Threshold Unsigned32 R 

Records-Since-Notification Unsigned32 R 

Previous-Notify-Time BACnetDateTime R 

Current-Notify-Time BACnetDateTime R 







8 



8.3 How a Trend Log works 

A Trend Log object records a property of a referenced object if predefined conditions 

materialise, and it stores (or 'logs') the values for this property with a time stamp in an 

internal buffer. 

The referenced object may be located either on the same device (Device) or on an 

external device. 

There are two ways of recording the data. They can be recorded at periodic intervals, or 

when a status/value changes (COV). In addition, errors and changes to the status and 

function of the Trend Log object are recorded. Every entry in the Trend Log buffer ('Log 

Buffer') is known as a 'Record'. If a referenced object supports status flags ('Status 

Flags') with COV Reporting, an entry will also be made when the status of a flag 

changes. The status of the status flags is also recorded in a Record. 

The buffer size of a Trend Log object is defined in the 'Buffer-Size' property, and it can 

be changed manually by a BACnet client. (The buffer can be enlarged during recording; 

if the buffer is set lower than 'Record Count', the entire 'Log Buffer' is deleted). 

If the 'Stop-When-Full' property is set, recording is stopped automatically when the 

buffer is full. If this property is not set, recording continues and the oldest value 

disappears from the buffer. 

You can use 'Log-Enable' to enable ('True') or disable ('False') recording manually. This 

also tells you the current status of the Trend Log object. You can use the dates and 

times defined in the 'Start-Time' and 'Stop-Time' properties to specify recording for 

limited times. Setting 'Log-Enable' to 'False' takes precedence over a 'Start/Stop-Time' 

specification. 

If the number of records in the buffer reaches the number specified in the 'Notification- 

Threshold' property, a 'Buffer-Ready' notification is sent with Notification Class object 4 

('Trendlog Buffer-Limit Notification'). The Notification Threshold should be about half or 

3/4 of the buffer size so that sufficient time is available to read out and archive the data 

in the Trend Log object. 

The 'Record-Count' property represents the current number of records in the Log Buffer. 

If this property is given value 0, the Log Buffer is deleted. 




8 

8.4 Engineering examples 

This section provides some examples of the various parameterisations for Trend Log 

objects. Parameterisation can be performed with the BACnet OPC server, for example. 

Notes on parameterisation with the Cimetrics/MBS BACnet OPC server: 

• The BACnet OPC Server represents wildcards for properties with data type 

BACnetDateTime for 'Start-Time' or 'Stop-Time' (*.*.*, *:*:*) as '01.01.1970, 

00:00:00.00' (for example). 

• The syntax in the BACnet OPC server for the 'Log-device-object-property' property 

should be entered as follows, for example: 

 

 

for a local BACnet object: {{(analogue-input,1083),present-value}} with 

{(analogue-input,1083,present-value} - i.e. without outer curved brackets 

for an external BACnet object: {{(device,200),(analogue-input,2083),presentvalue}} 

with {(analogue-input,2083),present-value,?,(device,200)}. 

8.4.1 Analogue input of Present-Value with time 

raster 

Recording of the 'Device-internal' analogue input object 4111001 Present-Value with a 

time raster of 10 seconds. 

The properties could be parameterised as follows: 

'Log-device-object-property' = {{(analogue-input,4111001),present-value}} 

'Log-enable' = T (Trend Log is active (True)) 

'COV-resubscription-interval' = 3600 (only relevant for COV Reporting of external 

objects; in seconds) 

'Log-interval' = 1000 (gives a time raster of 10 seconds; in 1/100ths of a second) 

'Start-time' = 31.07.2005, 00:00:00.00 (optional) 

'Stop-time' = 31.08.2005, 00:00:00.00 (optional) 


8 



8.4.2 Analogue input of Present-Value with COV 

Recording of the 'Device-internal' analogue input object 4111000 Present-Value after a 

'Raster Threshold Violation' (COV Reporting) 


'Log-device-object-property' = {{(analogue-input,4111000),present-value}} 


'COV-resubscription-interval' = 3600 (not relevant) 

'Log-interval' = 0 (for COV Reporting, this value must be 0!) 

'Start-time' = 31.07.2005, 00:00:00.00 (optional) 

'Stop-time' = 31.08.2005, 00:00:00.00 (optional) 

8.4.3 External multistate output of Present-Value with 

COV 

Recording of the 'Device-external' multistate output object 4112037 Present-Value after 

a 'Raster Threshold Violation' (COV Reporting) 


'Log-device-object-property' = {{(device,4112),(analogue-input,4112037),presentvalue}} 


'COV-resubscription-interval' = 3600 (log on again every hour; in seconds; this value 

must not be equal to 0!) 

'Log-interval' = 0 (for COV Reporting, this value must be 0!) 

'Start-time' = 01.01.1970, 00:00:00.00 (corresponds to *.*.*, *:*:* and is always active) 

'Stop-time' = 01.01.1970, 00:00:00.00 (corresponds to *.*.*, *:*:* and is always active) 




8 

8.4.4 Non-COV-supported property with time raster 

If possible, recording of non-COV-supported properties should only be used if there is 

an urgent need (to minimise the load on the bus due to unnecessary polling). 

Recording of 'Device-internal' loop object 4111109 proportional-constant with a time 

raster of 1 hour. 


'Log-device-object-property' = {{((loop,4111109),proportional-constant}} 


'COV-resubscription-interval' = 3600 (not relevant) 

'Log-interval' = 360000 (gives a time raster of 1 hour; in 1/100ths of a second) 

'Start-time' = 01.01.1970, 00:00:00.00 (corresponds to *.*.*, *:*:* and is always active) 

'Stop-time' = 01.01.1970, 00:00:00.00 (corresponds to *.*.*, *:*:* and is always active) 

Recording of a non-COV-supported property can also be performed with an external 

object. 

8.5 Read log buffer with ReadRange 

A BACnet client is told via the 'Buffer-Ready' intrinsic reporting mechanism (using 

Notification Class object 4) that the size of the log buffer has reached the threshold limit 

and that it should be read out. 

The readout can be performed manually (T-VMT-B: Trending-Viewing and Modifying 

Trends) with the ReadRange service or automatically (T-ATR-B: Trending-Automated 

Trend Retrieval), which is supported by the intrinsic reporting 'Buffer-Ready'. 

Manual readout, for example with the BACnet OPC server from Cimetrics/MBS, is 

shown here: 

Double-click on the 

Trend Log object to open a 

dialogue window where the 

Trend Log range can be 

read out and saved. 

The result of a log buffer 

read-out may appear in a file 

as follows: 


8 



# Date Value type Value Status flags 

1 30.08.2005 14:22:014.00 real 22.26 (FFFF) () 

2 30.08.2005 14:22:010.00 real 15.73 (FFFF) () 

3 30.08.2005 14:22:002.00 real 17.73 (FFFF) () 

4 30.08.2005 14:21:049.00 real 10.19 (FFFT) (out-of-service) 

5 30.08.2005 14:21:038.00 real 10.19 (FFFF) () 

6 30.08.2005 14:21:035.00 real 12.39 (FFFF) () 

7 30.08.2005 14:21:031.00 real 15.93 (FFFF) () 

8 30.08.2005 14:21:028.00 real 21.15 (FFFF) () 

9 30.08.2005 14:21:024.00 real 18.1 (FFFF) () 

10 30.08.2005 14:21:021.00 real 12.67 (FFFF) () 

11 30.08.2005 14:21:017.00 real 12.3 (FFFF) () 

12 30.08.2005 14:21:013.00 real 15.79 (FFFF) () 

13 30.08.2005 14:21:006.00 real 18.5 (FFFF) () 

14 30.08.2005 14:21:003.00 real 25.35 (FFFF) () 

15 30.08.2005 14:20:059.00 real 33.31 (FFFF) () 

16 30.08.2005 14:20:056.00 real 53.52 (FFFF) () 

17 30.08.2005 14:20:052.00 real 64.51 (FFFF) () 

18 30.08.2005 14:20:028.00 log-status (FT) ---- 

The ReadRange service (according to Revision 1.2 of the protocol) supports various 

mechanisms for data readout: 

• Read all (the optional Range parameter in the service is not used) 

• With position (in this case, the number of data records to be read out is defined 

starting from a specified position) 

• With time (in this case, the start time and number of data records to be read out is 

specified) – this is not supported with the BACnet OPC server.ß 

• With time range (in this case, the start and end times are specified). 

Note: the mechanisms such as 'With sequence number' or 'With time and number with 

returned start sequence number' are not (yet) supported (this will only be possible after 

implementation as per Revision 1.3 of the protocol). 

With novaPro Open BACnet Driver 2.1, automatic Trend-Log Retrieval is supported. 




8 

8.6 Trend Log engineering notes 

8.6.1 Background information 

Prior to BACnet server Version 2.4, attempts were made to use the Historical Database 

(HDB) of the EY3600 automation station with BACnet. For each datapoint that was 

HDB-compatible, a BACnet Trend Log object was created (if the BACnet server 

configurator had set this option). However, due to aggravated compatibility reasons, it 

was decided that historical data storage with the Trend Log objects would no longer be 

linked with the HDB of the EY3600 system. As a result, the HDB of an AS has no 

relationship with a BACnet Trend Log object. 

8.6.2 Behaviour in case of power failure or reset of 

the BACnet server 

Battery buffering is not provided on the BACnet communication card. There must not be 

too many write cycles on the available flash disk and for this reason, the recorded data 

('Log buffers') of the Trend Log objects are only kept in the normal working memory of 

the EYK. Unfortunately, this means that the data for the 'Log buffer' property are lost 

every time the server is restarted due to a power failure, the ReinitializeDevice Service 

or also after engineering via the BACnet server configurator. 

Measures have to be taken to minimise or totally eliminate the data loss. Here are some 

suggestions that may be used: 

a) Keep the buffer size of the individual Trend Log objects and especially the Threshold 

limits as small as possible, so that the data are read out frequently via the Intrinsic- 

Reporting 'Buffer-Ready' using a BACnet client with ReadRange, meaning that they 

can be archived at management level. In this way, a BACnet client can save the data 

persistently over long periods in a database or a file. A low Threshold limit therefore 

keeps data loss from the Log buffer at a low level. 

b) Before a ReinitializeDevice service is carried out by a BACnet client or an 

engineering change is made via the BACnet server configurator, all 'Log buffers' 

should be read out. 

c) To prevent data loss completely in case of a power failure, the BACnet AS or the 

modular BACnet station (nova106 or novaCom) must be supported with an external 

UPS device (Uninterruptible Power Supply, 230V). 

d) An alternative would be to use the Sauter EY3600-USP (EYZ101F001) for the 

BACnet AS or, for the modular BACnet station (EYK 300 F001), to use the 

nova108/nova109 assembly variant with the novaCom supply and UPS card 

(EYI 103 F001) at plug position B. 

It should be remembered that the BACnet communication card consumes a 

maximum of 0.4 A of extra power during operation. 


8 





Alarms and events 

9 

9 Alarms and events 

BACnet allows various mechanisms for transmitting data (process variables), alarm 

notifications (alarms) or special status changes (events). Detailed descriptions of these 

services are available in the BACnet Standard [1] or the Guide [2]. 'Change-Of-Value' 

reporting for data exchange is supported with the BACnet communication card. Alarm 

notifications are supported with the Intrinsic-Reporting mechanism and the Notification 

Class objects. 

9.1 Change-Of-Value reporting 

The Change-Of-Value reporting function is completely dynamic, i.e. the number of 

logons (COV subscriptions) is only limited by the memory and performance of the EYK. 

In view of this, however, no more than 3000 COV subscriptions should be used. This 

means that with a maximum number of objects, at most 3 clients can log on to all object 

instances at the same time. The COV subscriptions are not persistent so they are no 

longer available after a power failure. 

Logged-on clients should release the COV subscriptions correctly (using 

'UnsubscribeCOV'), so that there is no unnecessary accumulation of unused memory. 

The BACnet server automatically releases all COV subscriptions for the relevant 

recipient after a COV Notification Request has been cancelled with a timeout. In 

addition, a cyclical Resubscribe should be carried out to counteract the loss of COV 

subscriptions which may have occurred due to communication failures or other faults 

(including a server network outage). 

9.2 Intrinsic-Reporting 

A BACnet object receives the properties for Intrinsic-Reporting via the BACnet AS 

precisely when a special status (alarm) can be recorded by means of an appropriate 

algorithm. 

This is always the case for all analogue variables (AI, AO and AV), because the 

corresponding limit values are defined in an AS. The Out-Of-Range (OOR) algorithm is 

used in this case. However, the relevant limit value monitoring is only performed if the 

limits are enabled. The validity of the respective limit value is mapped in the Enable bits 

of the 'Limits_Enable' property. The half raster width is used as the hysteresis 

('Deadband' property). 


9 



For binary digital variables BI, BO and BV, the properties for Intrinsic-Reporting are only 

created if the HBG parameter Code involves an alarm. In this case, a change of status is 

notified by the Change-Of-State (COS) event type. 

For the Loop object, a Floating-Limit Intrinsic-Reporting alarm is triggered if the absolute 

difference between 'Setpoint' and 'Controlled-Variable-Value' exceeds the 'Error-Limit' 

value for longer than 'Time-Delay'. 

For the Trend Log object, a Buffer-Ready Intrinsic-Reporting alarm is triggered if the 

'Records-Since-Notification' and 'Notification-Threshold' properties are the same. 

The 'Project Engineering' and 'Restart-Indicator' system objects have a Change-Of-State 

algorithm implemented as an event, and they refer to the System Events Notification 

Class object intended for this purpose. 




9 

9.3 Alarms with Notification Class objects 

Notification of events to one or more BACnet clients requires a knowledge of the 

recipient(s) and the time-related release conditions, among other things. With Intrinsic- 

Reporting this is implemented solely by reference to a corresponding Notification Class 

object ('event notification class') which contains the necessary information. For example, 

the list of recipients ('Recipient_List' property) is stored in a non-volatile manner in this 

object after each client entry, so that the list is available again after restarting. This 

allows you to set the behaviour for event notifications on a group-by-group basis. 

Event notifications for standard BACnet objects are always sent with Notify_Type = 0 

(alarm). 

From BACnet server Version 2.4 onwards, there are two possible ways of assigning the 

event notifications to corresponding Notification Class objects. You can specify the type 

of assignment in the BACnet server configurator. 

1. Static assignment via object type 

In the BACnet AS, there is a Notification Class object for every type of event 


9 



notification. The BACnet objects with properties for Intrinsic-Reporting automatically 

receive the relevant reference to the appropriate Notification Class object 

('Notification_Class' property). The following five Notification Class objects are 

created in the BACnet server. 

Instance 

no. 

Name 

Description 

1 OOR Alarming Notification Class Out Of Range Alarming – class 1 

2 COS Alarming Notification Class Change-Of-State Alarming – class 2 

3 System Events System Events - class 3 

4 Trend Log Buffer-Limit Notification Trend Log Buffer-Limit Notification - class 4 

5 Floating Limit Notification Floating Limit Notification - class 5 

2. Assignment via protocol category 

If 'Assignment via protocol category' is selected, 13 or 14 Notification Class objects 

are automatically created in the BACnet AS. These 13 or 14 Notification Class 

objects are used for individual grouping of the event/alarm notifications, and the 

protocol category is parameterised in the engineering with CASE FBD for the 

individual I/O modules. In this case, an Intrinsic-Reporting Out-Of-Range, Change- 

Of-State, Floating-Limit alarm algorithm for the I/O modules is assigned to the 

relevant Notification Class objects using the protocol category (PC) . 

Instance 

no. 

Name 

Description 

10 Protocol-Category 0 Protocol-Category 0 – class 10 


… … … 


Optional if the 'Use protocol category 14' flag is enabled: 

Instance 

no. 

Name 

Description 


Note: 

This enabled status should only be used if 14 freely usable Notification Class 

objects really have to be used. Protocol category 14 should remain reserved for any 

new BACnet server functions. 

If this flag is not enabled and an I/O module nevertheless has protocol category 14 

parameterised, the Intrinsic-Reporting functionality will be disabled on the 

corresponding BACnet object. 




9 

The Notification Class objects for the System events and the Trend Log Buffer Limit 

notifications are retained. 

Instance 

no. 

Name 

Description 

3 System Events System Events - class 3 

4 Trend Log Buffer-Limit Notification Trend Log Buffer-Limit Notification - class 4 

9.4 Notification Class Object 

Property Data type EYK 






Priority BACnetArray[3] of Unsigned W 

Ack-Required BACnetEventTransitionBits R 

Recipient-List List of BACnetDestinations W 





Note: 

From Version 2.4 onwards, the 'Object name' and 'Description' properties can be filled 

in. 

The default priority value for the Notification Class object is 1. This value can be filled in, 

and it should be parameterised by a BACnet client for correct classification (Alarm/Event 

Class Priority). The BACnet Standard makes the following informative suggestion 

(Annexe M): 

Notification 

group 

Priority Network priority Description 

Safety of persons 

(Life Safety) 

Building security 

(Property Safety) 

Monitoring 

(Supervisory) 

Problem case 

(Trouble) 

00 – 31 Life-saving 

notification 

32 – 63 Life-saving 

notification 

64 – 95 Equipmentcritical 

notification 

96 – 127 Equipmentcritical 

Notification of acute danger to life, safety and 

health such as a fire alarm, armed robbery 

Notification of acute danger to buildings, such as 

forcible intrusion 

Notification of incorrect execution, monitoring 

failure (especially for safety of people and 

buildings) or if money is lost (EMAX) 

Notification of communication failure (especially 

for safety of people and buildings) 


9 




of higher priority 


of lower priority 

notification 

128 – 191 Important 

notification 

192 – 255 Normal 

notification 

Notifications in higher categories regarding 

discomfort for persons present, normal operation, 

normal monitoring or return to normal status. 

Notifications in lower categories regarding 

discomfort, normal operation, normal monitoring or 

return to normal status. 

9.4.1 Notification class 1 (OOR alarming notification) 

All analogue objects (analogue input, analogue output and analogue value objects) that 

have corresponding limit values (parameters Lt and Lb) defined in an AS will support 

intrinsic reporting with the Out Of Range algorithms. These objects are assigned to 

notification class 1. 

Acknowledgement of alarms is possible only for incoming alarm messages. In the 

‘Property Ack_Required’ in object notification class 1, only the related enabling bit is set 

for TO-OFFNORMAL. 




9 

9.4.2 Notification class 2 (COS alarming notification) 

In the case of binary digital variables (object binary input), the properties for intrinsic 

reporting are created only if the parameter CPB1 (HBG enable) stands at Alarm on the 

BI or BI_Soft module. 

In so doing, a status change is reported by the event type Change-Of-State (COS). 

These objects are assigned to notification class 2. 

Acknowledgement of alarms is possible only for incoming alarm messages. In the 

‘Property Ack_Required’ in object notification class 2, only the related enabling bit is set 

for TO-OFFNORMAL. 


9 



9.4.3 Notification Class 3 (system events) 

This event notification class is reserved for general system events. At present, the 

automatically generated system objects are used with this Notification Class object. 

These are the 'Project Engineering' object, the 'AS Status' objects and the 'Restart- 

Indicator' object (see section 6). 

Acknowledgement of alarms is only possible for incoming alarm notifications. For this 

purpose, only the associated Enable bit for TO-OFFNORMAL is set in 'Property 

Ack_Required' in the Notification Class 3 object. 




9 

9.4.4 Notification class 4 (TrendLog buffer limit) 

All trend log objects support intrinsic reporting with the buffer-ready algorithms. These 

objects are assigned to notification class 4. 

Alarm acknowledgement is not possible. 


9 



9.4.5 Notification class 5 (floating limit notification) 

All loop objects which have the corresponding Tdly and LtErr parameters defined in an 

AS will support intrinsic reporting with the floating limit algorithms. These objects are 

assigned to notification class 5. 

Alarm acknowledgement is not possible. 




9 

9.5 Alarm-Quittierung 

In general, AS-side acknowledgement of alarms is only possible for incoming alarm 

notifications. Accordingly, when an event notification (Event Notifications) is due to be 

sent, a user acknowledgement is only requested by BACnet if the event status in 

question is a transition to the TO-OFFNORMAL status. For this purpose, only the 

associated Enable bit is set to TO-OFFNORMAL in the Ack_Required property of the 

respective object instances of the Notification Class type. 

Notes on functioning: 

An Acknowledge-Alarm Request initiated by a BACnet client with a correspondingly 

acknowledgeable event status is forwarded directly to the automation station. The 

identity specified (Id=255) is used to identify the originator. 

In this case, it should be noted that with analogue variables, the various monitoring 

mechanisms may bring about different alarm statuses in the automation station and in 

the BACnet server. If this happens, a user acknowledgement by BACnet may 

temporarily seem implausible from the viewpoint of the automation station under certain 

circumstances. 


9 





Time profiles 

10 

10 Time profiles 

10.1 Create schedule object 

The schedule objects are local EYK objects and they are created, either dynamically with 

the use of a BACnet-Client (e.g. with novaPro Open, see manual novaPro Open) or 

statically within the BACnet-Server Configurator (BnsCfg) in the "Settings" tab. Up to 100 

schedule objects can be created. 

The 4 relevant "object properties"- "Effective Period", "Exception Schedule", "List of Object 

Property References" and "Weekly Schedule" - are empty and still have to be 

parameterised from the management level. 


10 


Time profiles 

10.1.1 Schedule object 






Present-Value Any R 

Effective-Period BACnetDateRange W 

List-Of-Object-Property-References List of 

W 

BACnetDeviceObjectPropertyReference 

Priority-For-Writing Unsigned (1..16) R 





Weekly-Schedule BACnetArray[7] of BACnetDailySchedule W 

Exception-Schedule BACnetArray[N] of BACnetSpecialEvent W 


10.1.2 Example 

ISP06_SH00 (Schedule (0)) is active (present value = 1) every Tuesday from 8:00 

onwards and is inactive (present value = 0) every Tuesday from 16:00 onwards. 

Binary output 1033 is written with this value, with write priority 16. 



Time profiles 

10 

10.2 Create calendar object 

The calendar objects are local EYK objects and they are created , either dynamically 

with the use of a BACnet-Client (e.g. with novaPro Open, see manual novaPro Open) or 

statically within the BACnet-Server Configurator (BnsCfg) in the "Settings" tab. Up to 40 

calendar objects can be created. 

The relevant "object property" - "Datelist" - is empty and still has to be parameterised 

from the management level. 


10 


Time profiles 

10.2.1 Calendar object 






Present-Value Boolean R 

Date-List List of BACnetCalendarEntry W 





10.2.2 Example 

ISP06_CA00 (Calendar (0)) is active (present value = true) on Tuesday 5 February 

2004 and Friday 19 March 2004. 



EYK 300 parameterising for peer-to-peer data transmission 

11 

11EYK 300 parameterising for peerto-peer 

data transmission 

Using the integrated client functionality, the data exchange of present values with 

external BACnet devices is possible as both a data sink and a data source. 

11.1 Client ‘data sink’ functionality 

Present values of an external BACnet servers are recorded and written with a pre-set 

write priority to the present value of a local object. 

Data acquisition is possible either event-controlled per COV reporting (COV=Change- 

Of-Value) or via cyclical polling (Read-Property). 

Local objects can only be selected as data targets if they have the Priority-Array 

property (all Output and Value object types) so that they are 'commandable'. 

If a data source fails, a value of ‘NULLs written on the present value of the linked local 

object. This causes the value of the associated write-priority level to become invalid, so 

the value of the lower priority level comes into effect. If there is no valid value left, 

automatic mode is enforced. 

Communication is not started until the object belonging to such a link has been created. 

11.2 Client ‘data source’ functionality 

This function enables a local present value to be written directly to the present value of 

an external BACnet device. The writing operation is triggered when a value changes 

outside a projectable hysteresis (similar to COV increment). 

Objects can only be selected as external data targets if they have the Priority- 

Array property (all Output and Value object types) so that they are 'commandable'. 


11 



11.3 Engineering the data links 

Up to 100 external data links can be projected. This is done using an Excel table that is 

saved as a CSV file bnsclt*.csv (*=Device instance number of EYK 300F001). 

Note: It can happen that the EYK is delivered with an example file: bnsclt.xls. However, 

it is mandatory to save this file as a CSV file (.csv) in order to enable the client 

functionality of the EYK. 

Link description 

Remote object type 

Remote object 

instance 

Local object instance 

Write priority 

Function code 

(0=Polling 1=COV 

2=Write) 

Lifetime/poll time-out 

[sec] 

COV 

increment/threshold 

Test analogue-value polling 45 AI 45000 220020 15 0 30 

Test analogue-value COV 45 AI 45001 220021 15 1 600 0,1 

Test analogue-value write 45 AO 45022 220002 15 2 0,1 

Remote deviceinstance 

The links are configured line by line. The values of each column should be entered as 

follows:- 

Column Explanation Range 


Description of the external dataobject 

for engineering aid. This 

Any text (except 

separators) 

column is ignored by Bns36. 

Remote device instance Device-instance number of the 1..4194303 


Remote object instance 


Local write priority 

external server. 

Symbol for the object type of the 

remoteseitgen data-object:- 

AI=Analogue Input 

AO=Analogue Output 

AV=Analogue Value 

BI=Binary Input 

BO=Binary Output 

BV=Binary Value 

MSI=Multistate Input 

MSO=Multistate Output 

MSV=Multistate Value 

Instance number of the remoteside 

data object 

Instance number of the local data 

object 

Priority level for the writing 

operation (1=highest, 15=lowest 

priority) 

AI,AO,AV,BI,BO,BV,M 

SI,MSO 

(upper/lower case 

permitted) 

1..4194303 

1..4194303 

1..15 




11 

Function code 

Lifetime/poll time-out [sec] 

COV increment/threshold 

Method of data transmission 

0=Cyclical polling 

1=COV reporting 

2=Write 

Lifetime of the COV subscription or 

poll time-out 

(N.B.: Lifetime for COV = 0 

denotes unlimited lifetime) 

This entry is ignored when function 

code=2. 

COV increment when data 

acquisition via COV reporting. 

Hysteresis for writing function; if 

field is empty, 0.0 is taken. The 

hysteresis works only for analogue 

variables. 

0,1,2 

0..4294967295 

Floating decimal point 

11.4 Downloading the link file 

The EYK integrates an access-protected FTP server. The user name and password 

(default: Sauter 12345) can be modified by means of the BACnet configurator. 

Using an FTP client (e.g. Internet Explorer), the file bnsclt*.csv (*=device instance 

number of EYK 300F001) should be downloaded to the EYK 300 or EYK 220 into the 

FlashFx folder direct via TCP/IP. After the download, the EYK 300 has to be re-started. 


11 



11.5 Example: 

11.5.1 Topology: 

Client functionality of the BACnet server/client device-instance no. 1:- 

Data sink (read/receive) 

Data source (write) 


Ethernet 

Device-Instance No.: 1 

EYK 300 F001 

Device-Instance No.: 2 

EYK 300 F001 

novaNet 1 

novaNet 2 

AS-novaNet No.: 1 

EYL 106 F001 

BACnet Server/Client 1 

AS-novaNet No.: 2 

EYL 220 F001 

BACnet Server/Client 2 




11 

11.5.2 Transfer list bnsclt1.xls 


Remote deviceinstance 


Remote object 

instance 


Write priority 

Function code 

(0=polling 1=COV 

2=write) 

Life-time/poll-timeout 

[sec] 

COV 

increment/threshold 

AI 2010 --> AO 1020 2 AI 2010 1020 16 1 600 0.05 

MSI 2052 --> MSO 1036 2 MSI 2052 1036 16 1 600 

BI 2064 --> BO 1032 2 BI 2064 1032 16 1 600 

AV 1066 --> AO 2020 2 AO 2020 1066 16 2 0.05 

MSV 1073 --> MSO 2039 2 MSO 2039 1073 16 2 

AI 1000 --> AV 2065 2 AV 2065 1000 16 2 0.05 

MSI 1052 --> MSO 2038 2 MSO 2038 1052 16 2 

11.5.3 Description of operation 

11.5.3.1 Data sink 

Present values of the external BACnet server (device-instance no. 2) are recorded and 

are written with a pre-set writing priority onto the present value of the local object 

(BACnet client device-instance no. 1). 

Line 1 

The present value of the external analogue input object (object instance 2010) is written 

onto the present value of the local analogue output object (object instance 1020). 

Line 2 

The present value of the external multistate input object (object instance 2052) is written 

onto the present value of the local multistate output object (object instance 1036). 

Line 3 

The present value of the external binary input object (object instance 2064) is written 

onto the present value of the local binary output object (object instance 1032). 


11 



11.5.3.2 Data source 

This function enables the local present value (BACnet client device-instance no. 1) to be 

written directly onto the present value of the external BACnet server (device-instance No. 2). 

Line 4 

The present value of the local analog value object (object instance 1066) is written onto 

the present value of the external analog output object (object instance 2020). 

Line 5 

The present value of the local multistate value object (object instance 1073) is written 

onto the present value of the external multistate output object (object instance 2039). 

Line 6 

The present value of the local analog input object (object instance 1000) is written onto 

the present value of the external analog value object (object instance 2065). 

Line 7 

The present value of the local multistate input object (object instance 1052) is written 

onto the present value of the external multistate output object (object instance 2038). 



EDE (Engineering Data Exchange) 

12 

12 EDE (Engineering Data Exchange) 

With regard to the acquisition of object data from alien BACnet sub-systems, it is often 

not possible to download them online via the internet, since the engineering work for it 

cannot usually be done on site. For this reason, a format was developed by the Working 

Group Technic of the B.I.G. (BACnet Interest Group) Europe for exchanging this 

engineering data (Description of EDE SpreadSheet.doc). 

Roughly speaking, these data comprise four separate tables that are saved as CSV 

(Comma Separated Value) files. These are namely: object data, state-text references, 

unit-text references and coding of object types. Since the EYK 300 F001 of BACnet 

uses pre-defined unit-of-measurement texts and object types, these tables are constant 

and are not created by EYK 300 F001. Only the ‘object data’ and ‘state-text references’ 

tables are dependent on the peculiarities of the installation and should be created 

accordingly. 

The generation of the EDE files is done automatically after an initial comparison of the 

object table and after every change. The tables edeData*.csv (object data) and 

edeStateText*.csv (state-text references) are created (*=device instance number von 

EYK 300 F001). Since these files very often have to be re-written due to the automatic 

comparison, they are saved in the temporary folder \TEMP. 

The files can be read out via the integrated access-protected FTP server (default: user 

name: Sauter password: 12345). 


12 


EDE (Engineering Data Exchange) 



Data exchange with EYK (FTP) 

13 

13 Data exchange with EYK (FTP) 

EYK BACnet data can be read out or exchanged via the integrated access-protected 

FTP server. (Default: login with user name:Sauter and password:12345). 

This should be used for update and backup functions. 

The data are distributed as follows: 

The persistent files are located in directory \FlashFx. 

• Application NK.LZH 

This is a specially zipped file containing the BACnet functions, WINCE and 

BACstack. The date determines the recognition of the version. Caution: This file 

must always be present! 

• Object list BnsObj*.bin 

One BnsObj*.bin per connected AS is created here (* = AS number). 

All other objects (Device, Schedule, Calendar, Notification Class and Trend Log) are 

stored in file BnsObjRt.bin. 

• Peer-to-peer file Bnsclt*.csv 

If this file is present, the client functionality of the EYK is enabled. 


13 


Data exchange with EYK (FTP) 

• The FSLOADCE.* files 

These files are used to start the application automatically when the EYK is switched 

on. Caution: these files must never be deleted! 

Directory Temp contains the temporary files. 

• Files EDE*.csv 

If these files are present, the BACnet application is able to function; if not, check the 

configuration or the novaNet connection. 



Annexe A: BACnet FAQ 

14 

14 Annexe A: BACnet FAQ 

The Frequently Asked Questions about BACnet and the Sauter EY3600 BACnet 

automation stations are available on the Sauter Intranet. 

Sauter Intranet Technical Support FAQ EY3600 BACnet 


14 


Annexe A: BACnet FAQ 



Annexe B: Troubleshooting the EYK 

15 

15 Annexe B: Troubleshooting the EYK 

15.1 Error log file for the BACnet server 

From version 2.4 onwards, the BACnet server has an integrated error log mechanism to 

improve diagnostic possibilities for EYK users. General error statuses/events are also 

logged in text form in two alternating files ('dynamic' log files: BnsErrA.txt, BnsErrB.txt). 

The maximum size of these files is about 500kByte. In addition, system information or 

errors which can only occur once when the system is started up are stored in a separate 

file ('static' log file: BnsStart.txt) 

You can enable this functionality (co-logging of errors) in the BACnet server configurator 

using the 'Enable error recording' option. 

These error log files can be donwloaded from the EYK (\FlashFx directory) with an FTP 

client, so they can be used for problem analysis. 


15 



Example of an extract from a BnsStart.txt file: 

Time stamp 

Description 

07.09.2005 10:35:41 ** startup ** 

07.09.2005 10:35:42 application version: '2.4-008 build on Aug 31 2005 14:21:49, 

BACstac(TM) 4.0' 

07.09.2005 10:35:42 configuration changed 

07.09.2005 10:35:42 IP-address '10.1.41.11', novaNet-address '31989' 

07.09.2005 10:35:43 normal memory state (avail=24044 [KB], load=7%) 

07.09.2005 10:35:43 verified AS3600 (addr=4111, type=EYL220, index=G) 

07.09.2005 10:35:43 verified AS3600 (addr=4113, type=EYL106, index=H) 




15 

Example of an extract from a BnsErrA.txt file: 

Time stamp Device ID ObjectID Description 

05.08.2005 09:48:22 (device,4111) (trend-log,10) dynamic object creation 

09.08.2005 06:37:10 (device,4111) device communication control 

'disable' 

09.08.2005 18:24:58 (device,4111) (trend-log,10) dynamic object deletion 

09.08.2005 18:33:40 (device,4111) (trend-log,11) dynamic object creation 

11.08.2005 06:09:48 (device,4112) state online 

15.08.2005 09:48:50 (device,4112) state offline 

31.12.1999 23:00:14 (device,4112) state online 

31.12.1999 23:00:14 (device,4111) (binary-input,2) event notif failed, dest={local, 

IP:10.1.142.88:47808}, eventType=change-of-state, fromState=normal, toState=offnormal, 

BACstac status 65: BACnet reject (reject reason 9: Unrecognized service) 

31.08.2005 13:54:25 (device,4112) state offline 

Note: For reasons already stated (see Time synchronisation, section 6.1.3) a time/date 

stamp is not always correct when the device starts up. 

15.2 Communication tests 

The BACnet server application on the EYK is based on a Windows CE operating 

system. After successfully starting this Windows CE, other TCP/IP-based services such 

as 'ping' and 'telnet' are available in addition to the FTP server. These services may be 

used to test the communication between the PC and the EYK so as to test the 

functionality of the EYK card. 

15.2.1 Ping 

To know whether a BACnet communication card is functioning correctly in a LAN (Local 

Area Network), a 'Ping' (ping.exe) must trigger a response. 

1. Start a Command window (Start Run… Open: 'cmd' and and confirm with 

OK) 

2. Enter the 'ping' command with the defined IP address of the EYK 

ping e.g. ping 10.1.41.11 

3. 'Response from…' will be given by an active BACnet EYK that is functioning 

correctly in the network. An incorrect LAN configuration would report 'Request 

time exceeded'. 


15 



You can obtain more information about the 'Ping' command by entering 'ping /?' 

15.2.2 Telnet server 

The EYK's Telnet server can be called up with a Telnet client (telnet.exe) in Windows. 

Start the Telnet client by entering the Host IP address (Start Run… Open: 'telnet 

' and confirm with OK). 




15 

You will see the EYK console. Using the Telnet client, you can now execute DOS 

command line commands (dir, cd, copy, …) on the connected device. This access 

should only be used by experienced technical experts and it can be disabled in the 

BACnet server configurator if necessary. 

15.2.3 Hyperterminal 

A minimal function test can be carried out with a serial PC-EYK connection. In this case, 

three commands are also available. Hyperterminal can be started via Start > 

Programmes > Accessories > Communication. 

1. Configure the Hyperterminal with the following connection settings: 

Baud rate: 19,200; data bits: 8; parity: none; stop bits: 1; flow control: none 

In addition, the Line Feed setting should be switched on in ASCII Setup . 

2. Switch on the EYK (if you have not already done so) and establish the 

Hyperterminal connection. 

3. Enter a command line: 

a. d m : 'display memory'; shows the memory used by the EYK in (%) 

b. d a : 'display application version'; shows the installed application 

c. d r : 'display recipients'; shows all logged-on recipients 

These functions only provide very minimal information and should only be used for 

the purposes of function testing if the card no longer responds via TCP/IP. 


15 





Annexe C: System limits 

16 

16 Annexe C: System limits 

An overview of the system and object limits of the EY3600 BACnet server (software) 

and the BACnet communication card (hardware). 

16.1 System 

Description: EYK hardware Specification Fix 

CPU clock rate (cycle frequency) 133 MHz x 

FlashRAM 16 MByte x 

RAM 32 MByte x 

Flash: minimum number of Delete cycles per 128 kByte block 100,000 

Ethernet interface 10/100 MBits auto 

Serial interface: 

19,200 x 

Baud rate: 19,200, data bits 8, no parity, 1 stop bit, no flow control 

Usable EY3600 AS numbers 1..4194 

Description: BACnet server (software) Specification Fix 

Number of possible COV subscriptions 3000 

gives the number of BACnet clients entered at the same time about 3 

Number of objects, total 1000 x 

Number of subordinate novaNet stations (AS, ecos, novaFlex) 100 

Number of peer-to-peer connections 100 x 

TCP/IP port number for BACnet server configurator 51966 x 

BACnet port number for BACnet data communication 47808..47823 

16.2 Objects 

Object Property Number / limit Fix 

Device Object-List Number of objects, total 1000 x 

Trend Log Number of objects 50 x 

Log-Buffer 

Number of entries in the Trend Log 10'000 x 

buffer, total 

Schedule Number of objects 100 x 

Exception-Schedule Number of 'BACnetSpecialEvent' 40 

entries 

Exception-Schedule Number of 'BACnetTimeValue' entries 12 

per BACnetSpecialEvent 

Weekly-Schedule Number of 'BACnetTimeValue' entries 24 

List-Of-Cbject-Property- 

References 

per Daily-Schedule 

Number of 

'BACnetDeviceObjectPropertyReferenc 

e' entries 

Calendar Number of objects 40 x 

Date-List 

Number of 'BACnetCalendarEntry' 30 

entries 

Notification 

Class 

Recipient-List Number of 'BACnetDestination' entries 12 

More BACnet specifications are available in the BACnet PICS (Sauter-Server-EY3600- 

PICS.pdf). 

30 


16 


Annexe C: System limits 



Annexe D: BACnet data types 

17 

17 Annexe D: BACnet data types 

The BACnet data types are described in the BACnet Standard (Clause 21). But as not 

all users may have received a standard, the most important data types in use are listed 

here. 

BACnetEventState ::= ENUMERATED { 

normal (0), fault (1), offnormal (2), high-limit (3), low-limit (4),…} 

BACnetEventTransitionBits ::= BIT STRING { 

to-offnormal (0), to-fault (1), to-normal (2)} 

BACnetEventType ::= ENUMERATED { 

change-of-bitstring (0), change-of-state (1), change-of-value (2), 

command-failure (3), floating-limit (4), out-of-range (5), …, buffer-ready (10), …} 

BACnetLimitEnable ::= BIT STRING { 

lowLimitEnable (0), highLimitEnable (1)} 

BACnetNotifyType ::= ENUMERATED { 

alarm (0), event (1), ack-notification (2)} 

BACnetPolarity ::= ENUMERATED { 

normal (0), reverse (1)} 

BACnetReliability ::= ENUMERATED { 

no-fault-detected (0), no-sensor (1), over-range (2), under-range (3), 

open-loop (4), shorted-loop (5), no-output (6), unreliable-other (7), 

process-error (8), multi-state-fault (9), configuration-error (10), …} 

BACnetStatusFlags ::= BIT STRING { 

in-alarm (0), fault (1), overridden (2), out-of-service (3)} 

ReinitializeDevice-Request ::= SEQUENCE { 

reinitializedStateOfDevice [0] ENUMERATED { 

coldstart (0), warmstart (1), …} 

password 

[1] CharacterString (1..20) OPTIONAL} 

DeviceCommunicationControl-Request ::= SEQUENCE { 

timeDuration 

[0] Unsigned16 OPTIONAL, 

enable-disable [1] ENUMERATED { 

enable (0), disable (1), disable-initiation (2)}, 

password 

[2] CharacterString (1..20) OPTIONAL} 


17 


Annexe D: BACnet data types 



Annexe E: BACnet client tool 

18 

18 Annexe E: BACnet client tool 

This small tool (BACtool.exe) is used for dynamic client-side creation or deletion of 

BACnet objects. 

The tool is based on the Cimetrics BACstac 4.x and can only be used if a BACstac of 

this kind is installed on the PC and licensed. The use of this tool is intended as an addon 

to the BACnet OPC server from Cimetrics/MBS or other BACnet Operator 

Workstations (B-OWS) which do not allow dynamic creation of objects. 

This tool is very simple and self-explanatory, and it uses the BACnet CreateObject and 

DeleteObject services. It is not possible to specify a 'List of Initial Values' so the objects 

are created with the standard BACnet server values. 

The tool supports objects of types Schedule, Calendar, Trend Log and Notification Class 

as well as all analogue, binary and multistate 'types'. 

The tool can be downloaded from the Sauter Intranet. 


18 


Annexe E: BACnet client tool 



Annexe F: 'Inside' BACnet EYK 

19 

19 Annexe F: 'Inside' BACnet EYK 

The EY3600 BACnet EYK Hardware Platform comprises a baseboard and a processor 

board. 

19.1 Hardware architecture 

EYK 

Baseboard: 

Processor 

board: 

- FSForth 

- AMD SC520 

- OS WinCE 3.0 

ISA-Bus 

Dual-Port 

SRAM 

Ethernet 

interface 

novaNet 

interface 

RJ45 

RJ11 

Ethernet 

novaNet 

Serial 

interface 

DB9 

RS232 

19.2 The baseboard 

The baseboard is a plug-in card which is similar to the EYS290 plug-in card, but with the 

EYU Rack Format as the form factor instead of the familiar ISA format for the PC. 

The baseboard is an ISA-Bus 'Memory Card' comprising a 'Dual Port RAM'. Access is 

possible via novaNet interface and also via the plugged-on processor board (small PC) 

via ISA-Bus. 

The baseboard also contains the DB9 plug for the serial interface and the RJ45 plug for 

the Ethernet network interface of the processor board. 

The voltage supply (12V DC, 0.4 A) comes from the EYU rack (card position A) or from 

the EYK 220 or EYK 230 automation station. 


19 


Annexe F: 'Inside' BACnet EYK 

19.3 The processor board 

The processor board (from FS Forth) is plugged onto the baseboard. The hardware 

comprises one AMD SC520 processor (x86-compatible, MOD520, 133 MHz) with the 

Windows CE 3.0 operating system. The processor board has a 16 MB flash memory for 

persistent data (files, registry) and a working memory (RAM) of 32 MB for the 

applications and the operating system. 

The voltage supply comes from the baseboard. 



Annexe G: BACnet server application update 

20 

20 Annexe G: BACnet server 

application update 

A new BACnet server application (NK.LZH with Windows CE Kernel, BACstac and 

BACnet server application) can be loaded onto the EYK (EYK300, EYK220, EYK230) 

with an FTP client (e.g. Internet Explorer). Perform these steps: 

1. Obtain information (FTP user name, FTP password and IP address) for the 

BACnet card (from the existing BACnet server configuration) 

2. Switch the automation station off 

3. Disconnect the BACnet card from novaNet 

4. Switch the automation station on and wait for at least 30 seconds 

5. Close all applications on the Windows computer and make sure that the 

Windows computer (laptop) will not suffer a power failure during the next steps 

6. Start Internet Explorer or the FTP client and type the following in the address 

field: 

ftp://Username[:Password]@IP address 

e.g. ftp://Sauter@192.168.0.1 

7. In the next dialogue, enter the FTP password and log on. 

8. Go to directory 'FlashFX' 

9. Copy file NK.LZH from the local directory (e.g. c:\temp) into the FlashFX 

directory. 


20 


Annexe G: BACnet server application update 

10. Choose yes to have the existing file overwritten. 

Important note: this process must not be interrupted and may take 1 to 2 

minutes. 

11. After copying is complete, you can close the FTP Explorer. 

12. Connect novaNet to the EYK and switch the station off and on. This allows a 

perfect start for the newly updated BACnet server. 

Notes: 

Information on data exchange with the EYK is also provided in section 13. 

To minimise the FTP transfer risk, you can copy the new application as a file name, 

e.g. nk24009.lzh into the \FlashFx directory. In the next step, delete the existing 

application (or rename it as nk22003.lzh, for example) and correctly name the new 

application (nk24009.lzh) as NK.LZH before restarting the EYK card. 

Files NK.LZH, FSLOADCE.BIN and FSLOADCE.CFG in the \FlashFX directory must 

always be present before the EYK card is switched off and on again. The FSLOADCE.* 

files must never be deleted. 



Annexe H: BACnet on the Internet 

21 

21 Annexe H: BACnet on the Internet 

Interesting BACnet references (various articles, discussions and FAQ) are available on 

the Internet. Here are some links: 

www.bacnet.org - Bibliography 

www.big-eu.org 

www.bacnet.ru 

www.wikipedia.org - BACnet 

www.bacnetassociation.org 

www.wsplab.de - Protokollprüfung 

www.cimetrics.com - BAS Products 

www.mbs-software.de 

www.gopolar.com - BACnet FAQ 

www.aamatrix.com - BACnet Definitions 


21 


Annexe H: BACnet on the Internet 

.

BACnet AS - sauter-controls.com sauter-controls.com

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?