User‘s Manual

BACnet OPC-Server

1.

Contents

1.

Contents ........................................................................................... 3

2.

Foreword .......................................................................................... 6 2.1.

Supported Operating System Versions........................................... 6

2.2.

Required Hardware ..................................................................... 6

2.3.

Recommended Literature ............................................................. 6

2.4.

Interesting links concerning BACnet in the World Wide Web ........................................................................ 7

2.5.

Registered trademarks ................................................................. 7

2.6.

Copyright ................................................................................... 8

3.

Blockdiagram of the BACnet OPC-server ............................................. 9

4.

Operating mode of the BACnet OPC-server ...................................... 10

5.

Operation of the BACnet OPC-server ................................................ 11 5.1.

The operating screen................................................................. 11

5.2. The status line........................................................................... 12 5.2.1 Information on the selected object........................................... 12 5.2.2 Information on the communication status................................. 12 5.2.3 The standby display ............................................................... 13 5.3. 6.

The tool bar ............................................................................. 14

The menus of the BACnet OPC-server ............................................... 16 6.1. The menu “File“........................................................................ 16 6.1.1 New ..................................................................................... 16 6.1.2 Open ................................................................................... 16 6.1.3 Save..................................................................................... 16 6.1.4 Save as................................................................................. 16 6.1.5 Download from the network.................................................... 16 6.1.6 Export as text file ................................................................... 16 6.1.7 Import as text file ................................................................... 16 6.1.8 List of the files loaded last....................................................... 16 6.1.9 End Server ............................................................................ 16 6.1.10 Delete Object ....................................................................... 17 6.1.11 Add Object ........................................................................... 17 6.1.12 Edit Object ........................................................................... 17 6.1.13 Edit/Read value ..................................................................... 17 6.1.14 Manual Time Synchronization ................................................. 17

3

MBS GmbH Römerstrasse 15 D-47809 Krefeld

Tel.: +49 / 21 51 / 72 94-0 FAX: +49 / 21 51 / 72 94-50 www.mbs-software.de

6.2. Menu “Settings“ ........................................................................ 18 6.2.1 BACnet................................................................................. 18 6.2.2 OPC .................................................................................... 18 6.3. Menu “View“ ............................................................................ 18 6.3.1 Parametrization mode ............................................................ 18 6.3.2 Value monitor ....................................................................... 18 6.3.3 Status line ............................................................................. 18 6.3.4 Shift Window Separation (left/right) ......................................... 18 6.4. Menu “Info“ ............................................................................ 18 6.4.1 About the BACnet OPC-server... ............................................. 18 7.

Parametrization of the BACnet OPC-Server ........................................ 19 7.1.

The download procedure........................................................... 19

7.2. Create/Edit objects manually...................................................... 21 7.2.1 Object type, instance number and OPC-reference names .................................................................................. 21 7.2.2 “Object shall be created dynamically“ ..................................... 21 7.2.3 Entries in the “Object Properties“ list........................................ 22 8.

9.

Communication with the OPC-interface ............................................. 23 8.1.

Supported OPC-versions ........................................................... 23

8.2.

Remote-Start............................................................................. 23

8.3.

OPC-quality ............................................................................. 24

8.4.

Configuration of the OPC-interface ............................................ 24

8.5.

Inquiries via OPC...................................................................... 25

8.6.

Log-in data points via OPC........................................................ 25

8.7.

Initialization of all data points..................................................... 25

Communication with the BACnet-interface ......................................... 26 9.1.

Supported BACnet-versions ....................................................... 26

9.2.

Supported services .................................................................... 26

9.3.

Supported Data-Link-Layer......................................................... 26

9.4.

BACnet PICS ............................................................................ 26

9.5.

Conformance Classes and Functional Groups ............................. 27

9.6.

BIBB’s ...................................................................................... 27

9.7. Configuration of the BACnet-interface......................................... 27 9.7.1 APDU-settings ....................................................................... 27 9.7.2 Event-Settings / COV ............................................................. 29 9.7.3 Event-settings / Intrinsic Reporting ........................................... 30 9.7.4 Download-settings ................................................................. 31 MBS GmbH Römerstrasse 15 D-47809 Krefeld

Tel.: +49 / 21 51 / 72 94-0 FAX: +49 / 21 51 / 72 94-50 www.mbs-software.de

4

9.7.5 9.7.6 9.7.7 9.7.8

Property-Filter........................................................................ 33 Poll-Filter .............................................................................. 34 Time service/Priority............................................................... 35 CC6 Data accesses ............................................................... 36

10. Optimization of the performance....................................................... 37 10.1. Use of the Cache-function ......................................................... 37 10.2. Optimizing the parametrization list.............................................. 37 10.3. Optimizing the BACnet-communication....................................... 38 10.4. Important hint “Parallel Services“ ................................................ 38 10.5. Automatic link monitoring .......................................................... 39 11. Reset of the Priority-Array .................................................................. 40 12. Simple test structure on a PC............................................................. 41 13. Using the Import / Export-interface .................................................... 43 13.1. ASCIl-files as basis .................................................................... 43 13.2. APDU-parameters ..................................................................... 43 13.3. Device object parameter............................................................ 47 13.4. BACnet-objects ......................................................................... 47 13.5. Example of a parametrization file as text file ................................ 48 14. Abbreviations and important terms .................................................... 50

5

MBS GmbH Römerstrasse 15 D-47809 Krefeld

Tel.: +49 / 21 51 / 72 94-0 FAX: +49 / 21 51 / 72 94-50 www.mbs-software.de

2. Foreword Thank you very much for using the BACnet OPC-Server. By means of this easy-to-operate software the connection of BACnet networks to OPC-based visualization systems will become a child´s play.

2.1.

Supported Operating System Versions

As operating system platform, Microsoft Windows NT version 4.0 is supported. The product you have obtained has been tested with all service packs, including the present SP6.

2.2.

Required Hardware

As hardware you require an IBM-compatible Personal Computer. As minimum requirements we recommend a processor type Pentium, min. 133 Mhz and 32 MB RAM memory capacity as well as a CD-ROM drive. For the installation approx. 15 MB free memory on the harddisk is required. For supporting certain BACnet Data-Link-Layer you require e.g. an Ethernet-, ARCnet or LonTalk network card. For using the dongle a parallel printer interface is required, a printer may be connected to the outlet of the dongle.

2.3.

Recommended Literature

ANSI/ASHRAE Standard 135-1995 BACnet A Data Communication Protocol for Building Automation and Control Networks: This is the official ASHRAE standard work with regard to BACnet. It deals with the complete ASHRAE-Standard 135-1995 (BACnet). There are several amendments and extensions to this work which may be loaded from the BAC-net homepage (http://www.bacnet.org). This literature may be purchased from Promotor-Verlag, Postfach 211053, D-76160 Karlsruhe, http://www.cci-promotor.de or Direct purchase from the ASHRAE-Online-bookstore: http://xp10.ashrae.org/bookstore/bookstore.html

MBS GmbH Römerstrasse 15 D-47809 Krefeld

Tel.: +49 / 21 51 / 72 94-0 FAX: +49 / 21 51 / 72 94-50 www.mbs-software.de

6

2.4.

Interesting links concerning BACnet in

the World Wide Web •

www.bacnet.org Official ASHRAE homepage concerning BACnet This is presumably the most important source of information for technical information on BACnet.



www.bacnet.de Homepage of the European BACnet Interest Group with information on activities and events of the BACnet Interest Group e.V.



www.cimetrics.com Homepage of Cimetrics Technology, Inc. with information on BACnet-products, BACnet-Protocolstacks and BACnetSoftwaretools.



www.mbs-software.de Homepage of MBS GmbH with information on BACnet-products, Fieldbus-Gateway-products and software developments.

2.5.

Registered trademarks

In this book trademarks and product names of specific companies are used. The following terms are registered trademarks of the respective vendors and are not especially mentioned in this book: • Microsoft, Windows and MS-DOS are registered trademarks of Microsoft Corporation

7



BACnet and ASHRAE are registered trademarks of the American Society of Heating, Refrigerating and Air-Conditioning Engineers, INC. (ASHRAE)



Intel and Pentium are registered trademarks der Intel Corporation



BACstac is a registered trademark of Cimetrics, Inc.



ARCnet is a registered trademark of the Datapoint Corporation



IBM-PC and IBM-AT are registered trademarks of the International Business Machines Corporation (IBM)



LONTalk is a registered trademark of the Echelon, Inc.

MBS GmbH Römerstrasse 15 D-47809 Krefeld

Tel.: +49 / 21 51 / 72 94-0 FAX: +49 / 21 51 / 72 94-50 www.mbs-software.de

2.6. ©2000

Copyright MBS GmbH Römerstraße 15 D-47809 Krefeld Telefon: Telefax:

+49 / 21 51 / 72 94 - 0 +49 / 21 51 / 72 94 – 54

E-Mail: Internet:

[email protected] http://www.mbs-software.de

All rights reserved. No part of this book may be reproduced in any form (printing, photocopy or any other technique) or processed, duplicated or circulated electronically without written permission of MBS GmbH.

MBS GmbH Römerstrasse 15 D-47809 Krefeld

Tel.: +49 / 21 51 / 72 94-0 FAX: +49 / 21 51 / 72 94-50 www.mbs-software.de

8

3. Blockdiagram of the BACnet OPCserver

BACnetClient interface

OPCServer interface

Operating functions

Driver BACne

Address t

Driver OPC

Actual values

Actual values

Setpoin t values

Setpoint Values

Program course

9

MBS GmbH Römerstrasse 15 D-47809 Krefeld

Tel.: +49 / 21 51 / 72 94-0 FAX: +49 / 21 51 / 72 94-50 www.mbs-software.de

4. Operating mode of the BACnet OPCserver •

The BACnet OPC-server works as client on the BACnet side and makes available BACnet-data points as OPC-server.



The represented data of the BACnet-servers, which are processed and used by the address converter may be stored permanently on the hard-disk in so-called „*.tdb“ files.



Single BACnet-server or object properties may be added or deleted. OPC-clients may subscribe the object properties and will be informed automatically about changes of the present value.



The support of the OPC/DCOM-Interfaces (Distributed COM) enables the separation of client and server to different computers in a single network.



BACnet object properties are displayed separately as OPC-Tags thus enabling a detailed representation of the data points.



The OPC-Browsing Interface is supported, that means a list of the available OPC-Tags from which the desired data points can be selected is displayed in the OPC-Client.



If the writing access to a property of the object is allowed, the value may be changed by the OPC- client. Hereby the default is verified by the BACnet-server and if it is unclear the value is rejected. The present value is then marked as “bad“.



On BACnet-side this software supports the automatic download from the devices. This however implies BACnet-servers of Conformance Class 3 or higher, in all other cases the definitions of the servers may be placed comfortably within the software and stored permanently.



Depending on the selected software option all Data-Link-Layers (except MS/TP) are supported on BACnet-side.



Depending on the selected software option BACnet-servers up to Conformance Class 6 are supported.



The BACnet-addenda A+B are implemented.

MBS GmbH Römerstrasse 15 D-47809 Krefeld

Tel.: +49 / 21 51 / 72 94-0 FAX: +49 / 21 51 / 72 94-50 www.mbs-software.de

10

5. Operation of the BACnet OPC-server A translation table which may be stored as „*.tdb“-file on the hard disk or on a diskette serves as data base for the translation of BACnet objects to OPC. When starting the server the parametrization list which has been stored latest is always loaded thus enabling an automatic start of the software without any problems for example by entry in the autostart program group or by a remote call of a client.

5.1.

The operating screen

This picture displays the operating screen of the BACnet OPC-server. The connected BACnet-servers with their data objects appear on the left half of the window. The right half of the window displays the properties of the selected object. The right half of the window shows the properties of the BACnet object which has been selected in the left half of the window. For each property the data point name (OPC-Tag), the used OPCdatatype and, in case the value display is switched-on, the present value as well as the type of access (reading or reading/writing) is displayed.

11

MBS GmbH Römerstrasse 15 D-47809 Krefeld

Tel.: +49 / 21 51 / 72 94-0 FAX: +49 / 21 51 / 72 94-50 www.mbs-software.de

5.2.

The status line

Three important information are displayed in the status line.

5.2.1.

Information on the selected object

Depending on the selected object this information line displays the amount of data points, hereby a data point corresponds to a BACnetproperty resp. an OPC-Tag.

5.2.2.

Information on the communication status

This information line may take the following states: The program is in the parametrization mode, the communication to BACnet and to OPC is deactivated.

The program is in the operating mode, no connection could yet be established to any of the servers mentioned in the parametrization list. The program is in the operating mode, connections to mentioned servers could already be established, however to at least one server no connection could be established yet. The program is in the operating mode, a communication could be established to all servers. Important hint: If the display of the communication status is permanently red (Offline) please check the settings and the function of the network card. Probably no communication can be established to any device via the network. If the display is permanently blue (building-up phase) please check the parametrization as well as the network settings and function of the network. At least one device to which no connection can be established is defined in the parametrization list.

MBS GmbH Römerstrasse 15 D-47809 Krefeld

Tel.: +49 / 21 51 / 72 94-0 FAX: +49 / 21 51 / 72 94-50 www.mbs-software.de

12

5.2.3.

The standby display

This information line shows the standby mode of the program. If the mouse cursor is moved via an entry of the tool bar or within the menus, a short information on the corresponding program function is displayed.

13

MBS GmbH Römerstrasse 15 D-47809 Krefeld

Tel.: +49 / 21 51 / 72 94-0 FAX: +49 / 21 51 / 72 94-50 www.mbs-software.de

5.3.

The tool bar

The tool bar enables the rapid access to the most important program functions. Below please find a description of the individual functions of the tool bar.

This picture shows the tool bar in the parametrization mode, all functions with the exception of the value display can be selected.

This picture shows the tool bar in the operating mode, only the functions value display and parametrization can be selected. File / New, creates a new parametrization file. File / Open, opens a parametrization file from the hard disk / diskette. File / Save, saves the present parametrization file on the hard disk / diskette. File / Export, exports the parametrization file as text file. File / Import, imports a text file and creates a parametrization file. File / Download, loads the parametrization dynamically from the connected severs. Add Object, allows the manual definition of new objects. Delete Object, deletes the object selected in the left window half. Edit Datapoints, allows the editing of already opened objects. Value Display ON/OFF, switches on or off the value display. Parametrization, switches into the parametrization or online mode. Special features of the functions value display and parametrization: These functions may each take over the ON or OFF state (that means e.g. switch-on value display). If the function is switched-on, the switches in the tool bar appear as if they have been pressed. MBS GmbH Römerstrasse 15 D-47809 Krefeld

Tel.: +49 / 21 51 / 72 94-0 FAX: +49 / 21 51 / 72 94-50 www.mbs-software.de

14

The value display is switched-on. The parametrization mode is active.

15

MBS GmbH Römerstrasse 15 D-47809 Krefeld

Tel.: +49 / 21 51 / 72 94-0 FAX: +49 / 21 51 / 72 94-50 www.mbs-software.de

6.

The menus of the BACnet OPC-server

6.1.

The menu “File“

6.1.1.

New

creates an empty .tdb-file

6.1.2.

Open

loads a tdb-file from the hard disk

6.1.3.

Save

saves the present file on the hard disk

6.1.4.

Save as

saves the present file on the hard disk by selecting a new file name

6.1.5.

Download from the network

searches the BACnet-network and transfers all servers found as well as their objects into the present table, should there already be data in the table you will be asked if you want to add the new data which means the existing parametrization will be amended by new devices and objects. For more detailed information please refer to the chapter „Parametrization“.

6.1.6.

Export as text file

select this option in order to save the present parametrization as text file on the hard disk or diskette.

6.1.7.

Import as text file

select this option to read-in a text file and to create a parametrization list from these information.

6.1.8.

List of the files loaded last

here the 4 parametrization files which have been loaded last, if any, are displayed.

6.1.9.

End Server

ends the BACnet OPC-server. If there are still clients connected to the OPC-server a warning advice informing about this state appears. In this case first of all the connected clients and then the BACnet OPC-server should be finished. MBS GmbH Römerstrasse 15 D-47809 Krefeld

Tel.: +49 / 21 51 / 72 94-0 FAX: +49 / 21 51 / 72 94-50 www.mbs-software.de

16

6.1.10.

Delete Object

deletes the selected object after a safety inquiry, after deletion this object may not be read or written by OPC-clients any more.

6.1.11.

Add Object

adds a new object into the list. For more information concerning the adding of objects please refer to the chapter “Parametrization of the BACnet OPC-server“

6.1.12.

Edit Object

enables the editing of objects which are already contained in the parametrization list. For more information concerning the editing of objects please refer to the chapter “Parametrization of the BACnet OPC-server“

6.1.13.

Edit/Read value

If the writing access to the selected property is allowed, the present value may be changed with this function. If only a reading access to the property is allowed, the value may be read and added in the Windows temporary store by means of the copy functions.

6.1.14.

Manual Time Synchronization

(Available from software option 2 onwards) This function enables a manual time synchronization of the connected devices. For this the BACnet OPC-server has to be set as „Time-Master“.

In this dialog those devices whose time should be synchronized can be selected as well as the time and the date at which the synchronization should be effected. The present date as well as the present time is automatically proposed.

17

MBS GmbH Römerstrasse 15 D-47809 Krefeld

Tel.: +49 / 21 51 / 72 94-0 FAX: +49 / 21 51 / 72 94-50 www.mbs-software.de

6.2.

Menu “Settings“

6.2.1.

BACnet

enables the configuration of the BACnet-interface. For hints concerning the configuration please refer to the chapter “Configuration of the BACnet-Interface”.

6.2.2.

OPC

enables the configuration of the OPC-interface. For hints concerning the configuration please refer to the chapter “Configuration of the OPC-Interface”.

6.3.

Menu “View“

6.3.1.

Parametrization mode

Switches on or off the parametrization mode. A change into the parametrization mode is only possible if no clients are connected via OPC.

6.3.2.

Value monitor

Switches on or off the value display. This function cannot be activated in the parametrization mode.

6.3.3.

Status line

switches the display of the status line on or off.

6.3.4.

Shift Window Separation (left/right)

allows for the shifting of the window separation by means of the keyboard.

6.4.

Menu “Info“

6.4.1.

About the BACnet OPC-server...

Here you may find information about the version state of the BACnet OPC-server.

MBS GmbH Römerstrasse 15 D-47809 Krefeld

Tel.: +49 / 21 51 / 72 94-0 FAX: +49 / 21 51 / 72 94-50 www.mbs-software.de

18

7. Parametrization of the BACnet OPCServer Important hint: A change of the parametrization is only possible if no OPC-clients are connected. Therefore please start the program manually if you want to change the parametrization.

7.1.

The download procedure

The download of information proceeds according to the following principle: When receiving a download request the BACnet OPC-server sends a “Who-is“ inquiry as broadcast to the network and waits for an adjustable period of time for “I-Am”answers of devices.

After that these devices are shown as a list.

Per selected device the property “object list“ of the device object is read and entered in the parametrization list. Possible adjusted download filters (see “BACnet-settings“) are considered.

19

MBS GmbH Römerstrasse 15 D-47809 Krefeld

Tel.: +49 / 21 51 / 72 94-0 FAX: +49 / 21 51 / 72 94-50 www.mbs-software.de

After changing from the parametrization mode to the run mode the properties are read with the command “Read Property“, respectively the entries for COV notifications and events and alarms are sent to the device with the commands “SubscibeCOV” and “AddListElement”.

MBS GmbH Römerstrasse 15 D-47809 Krefeld

Tel.: +49 / 21 51 / 72 94-0 FAX: +49 / 21 51 / 72 94-50 www.mbs-software.de

20

7.2.

Create/Edit objects manually

In order to create new objects please select from the menu “Edit“ the menu point “Add Object“, for editing please select from the menu “Edit“ the menu point “Edit Object”. The following dialog which is the same for both functions opens.

7.2.1. Object type, instance number and OPCreference names Select the desired object type, the object instance number as well as the OPC reference name (OPC-Tag) for the object. In order to re-create the same objects rapidly a range of instance numbers (e.g. 10-20) may be given when adding the objects. Then the given amount of objects will be opened. This function is not available when editing as the editing of objects always refers to the selected individual object.

7.2.2.

“Object shall be created dynamically“

With this setting you determine whether the object should be created dynamically in the server when starting the BACnet OPC-server with the command “CreateObject”. Please only select this setting if this possibility is supported by the connected BACnet-servers.

21

MBS GmbH Römerstrasse 15 D-47809 Krefeld

Tel.: +49 / 21 51 / 72 94-0 FAX: +49 / 21 51 / 72 94-50 www.mbs-software.de

7.2.3.

Entries in the “Object Properties“ list

This list has multiple functions and always refers to the object which has been selected under “Object Type”. Only the properties marked in this list will be taken over into the parametrization list. The second function refers to the checkbox. If the connected BACnetservers allow for it, write requests are transferred via OPC to those properties whose access type “Read AND Write“ has been selected (hook at the checkbox), If this option is not active for the corresponding property, a write attempt via OPC is rejected. This function makes it possible to stop write access via OPC although this would be possible from BACnet side.

This function marks all properties for the selected object type so that these will be taken over into the parametrization list.

This function inverts the selection of the properties.

This function inverts the selection of the read and write authorization.

This function adds the object into the parametrization list.

This function leaves the dialog to add or edit objects.

MBS GmbH Römerstrasse 15 D-47809 Krefeld

Tel.: +49 / 21 51 / 72 94-0 FAX: +49 / 21 51 / 72 94-50 www.mbs-software.de

22

8. Communication with the OPCinterface 8.1.

Supported OPC-versions

From the side of the OPC-interface the present definitions for DataAccess Version 1.0 and 2.0 as well as the event and alarm specifications version 1.0 are supported. Please take into consideration that – when using the IntrinsicReporting-functions, that means transfer of alarms and notifications – the connected OPC-client also must be able to support the OPCevent and alarm specifications.

8.2.

Remote-Start

The BACnet OPC-server may be started by an OPC-client (remote) whereby the program is loaded with the first call. When the last client log-out is executed the program is finished automatically if it has been started by an OPC-client “remote“ before. The program is entered in the Windows registration data bank under the following name: “Cimetrics.BACnetOPCserver.1 (Cimetrics BACnet OPC-Server)“ for OPC-Data-Access and „Cimetrics.BACnetOPCserver.Alarm.1 (Cimetrics BACnet OPC-Server Alarm)“ for OPC-Event-and Alarm Specifications. If you want to start the server at another station than the local one, you require the corresponding access rights under Windows-NT. In this connection we refer you to the documentation of the operating system respectively the OPC-specifications. The configuration of the DCOM interface may be executed, respectively verified by means of the “DCOMCNFG.EXE” program which comes with Windows-NT. Here please also note the help files of the operating system and the program.

23

MBS GmbH Römerstrasse 15 D-47809 Krefeld

Tel.: +49 / 21 51 / 72 94-0 FAX: +49 / 21 51 / 72 94-50 www.mbs-software.de

8.3.

OPC-quality

OPC determines 3 states which reflect the plausibility of a read value: •





uncertain This state is assumed for a value for which the automatic BACnetnotification service (COV=Change-Of-Value) has been logged-in, however no notice of change has been received yet. bad Fruitless efforts have been made to read the value. There may be 3 possible reasons for this: a) The property of the BACnet-object is not supported. b) The device did not supply any value within the timeout period after the respective amount of repetitions has been made. c) An attempt has been made to write a value on a property which is only readable. good The value could be read successfully respectively has been reported by the device.

8.4.

Configuration of the OPC-interface

For configuration of the OPC-interface please open the dialog “OPCSettings“ from the menu “Settings” .

The following settings may be made in this dialog:

MBS GmbH Römerstrasse 15 D-47809 Krefeld

Tel.: +49 / 21 51 / 72 94-0 FAX: +49 / 21 51 / 72 94-50 www.mbs-software.de

24

8.5.

Inquiries via OPC

When receiving inquiries via the OPC-interface normally the OPCclient decides how the data points should be read -> “Decision is taken from the OPC-Flags”. However, since an inquiry from the device may be timely probematically when having huge amounts of data, the BACnet OPCserver offers the possibility to read the data cyclically respectively to enrol them via COV so that an answer to the inquiries may be effected from the temporary store “Cache” first -> “...will always be answered from the Cache“. Regardless of the setting of the OPC-client there is a third possibility, namely the possibility to generally read data from the devices. By means of these settings the timely behavior may be very strongly influenced, please also refer to the chapter “Performance“.

8.6.

Log-in data points via OPC

Furthermore it may be decided for the time of log-in whether the values should be taken from the Cache or whether they should be read from the devices once more at the time of log-in.

8.7.

Initialization of all data points

This switch enables to decide whether the BACnet OPC-server should always be active in the background to read data points from the BACnet devices and keep thus the Cache up-to-date (setting: hook) or whether the Cache should be switched-off (setting: no hook).

25

MBS GmbH Römerstrasse 15 D-47809 Krefeld

Tel.: +49 / 21 51 / 72 94-0 FAX: +49 / 21 51 / 72 94-50 www.mbs-software.de

9. Communication with the BACnetinterface 9.1.

Supported BACnet-versions

The functional scope of the ASHRAE-Standard 135-1995 as well as addenda A and B are supported.

9.2.

Supported services

The following services are not implemented since there are no equivalent OPC functions to them: ConfirmedPrivateTransfer UnconfirmedPrivateTransfer ConfirmedTextMessage UnconfirmedTextMessage VT_Open VT_Data VT_Close An implementation of the “Who-Has“, respectively the “I-Have“ services has been consciously omitted, for a dynamical determination of the supported objects of a device the property “object_list” of the device object is applied.

9.3.

Supported Data-Link-Layer

Depending on the selected software option all BACnet Data-LinkLayer except MS/TP are supported.

9.4.

BACnet PICS

The PICS (Protocol Implementation Conformance Statement) which is contained in the delivery packet informs about the implementation as well as the supported functions.

MBS GmbH Römerstrasse 15 D-47809 Krefeld

Tel.: +49 / 21 51 / 72 94-0 FAX: +49 / 21 51 / 72 94-50 www.mbs-software.de

26

9.5.

Conformance Classes and Functional

Groups The document “BACnet OPC-Server PICS (Protocol Implementation Conformance Statement)“ describes in detail the supported BACnet Conformance Classes and Functional Groups. Depending on the selected software option BACnet-servers are supported up to Conformance Class 6.

9.6.

BIBB’s

The document “BACnet OPC-Server BIBB’s (BACnet Interoperable Building Blocks)“ describes in detail the supported BACnet Building Blocks.

9.7.

Configuration of the BACnet-interface

Please note the document “Configuration of the BACnet Data-LinkLayer“ describing the settings for the different BACnet network media. For configuration of the BACnet-interface please open the dialog “BACnet-Settings“ from the menu “Settings“. This dialog consists of up to seven configuration menus.

9.7.1.

27

APDU-settings

MBS GmbH Römerstrasse 15 D-47809 Krefeld

Tel.: +49 / 21 51 / 72 94-0 FAX: +49 / 21 51 / 72 94-50 www.mbs-software.de

1.1.1.1

Segmentation

For better understanding of the two following points a general understanding of the segmentation of BACnet telegrams is required therefore please find some hints below. A segmentation of BACnet data packets is required if data packets exceeding the maximum allowed packet length are called for. So it is e.g. determined for the Data-Link-Layer Ethernet that the maximum length of a data packet is 1476 bytes. If a data packet which is to be send is bigger than the supported packet length of the protocol, the data packet will be divided into several telegrams (“segments”). Combining the segments to “Windows“. Upon receipt of the segmented packets an acknowledgement of the recipient is required (“Segment-Acknowledge“). If this is not received, the sender recognizes that the packets have to be sent once more. Hereby the “Windowsize” determines after how many segments the recipients sends an acknowledgement.

1.1.1.2

Max. segments

This value determines the maximum possible amount of segmented packets which may be sent to the BACnet OPC-server by the devices. From the vendor´s side this value is set to 32.

1.1.1.3

Max. Window Size

This value determines after how many received segments an acknowledgement to the sender is effected. From the vendor´s side this value is set to 16.

1.1.1.4

Max. frame length

This value determines the max. packet length allowed for the network.

1.1.1.5

Timeout

This value determines how long the answer of a remote device should be waited for before the telegram is regarded as invalid and is resent.

1.1.1.6

Repetitions

This value determines how often a data packet should be repeated (if timeouts occurr).

1.1.1.7

Polldelay

This value determines the time you have to wait after an inquiry from the side of the BACnet OPC-server has been made, the value “0“ means that immediately after receiving an answer the device initiates the next inquiry. Please change this value if the whole packet load MBS GmbH Römerstrasse 15 D-47809 Krefeld

Tel.: +49 / 21 51 / 72 94-0 FAX: +49 / 21 51 / 72 94-50 www.mbs-software.de

28

should be too big on the network. However, if the selected values are too big it may happen that there is a delay in the arrival of the changes of value. Normally the value “0“ which has been set by the vendor can be used.

9.7.2.

1.1.1.8

Event-Settings / COV

use unconfirmed COV

If this setting has been selected, the log-ins for the automatic notification service for COV= Changes-Of-Value are effected with the attribute “unconfirmed“, which means there is no transport acknowledgement which ensures that these messages have arrived the recipient (BACnet OPC-server).

1.1.1.9

use confirmed COV

If this setting has been selected, the log-ins for the automatic notification service for COV = Changes-Of-Value are effected with the attribute “confirmed“, which means after receipt of a COV message the BACnet OPC-server sends a transport acknowledgement to the sending device. This ensures that these messages have arrived the recipient (BACnet OPC-server).

1.1.1.10 do not use COV If this setting has been selected, no COV log-ins to the BACnetserver are initiated. Recommendation: If possible use confirmed COV if this is also supported by the connected devices.

29

MBS GmbH Römerstrasse 15 D-47809 Krefeld

Tel.: +49 / 21 51 / 72 94-0 FAX: +49 / 21 51 / 72 94-50 www.mbs-software.de

1.1.1.11 Delete COV log-ins after program end This setting should be active in the regular operation of the BACnet OPC-server so that logged-in COV services may be logged-out again in the devices after program end. For service purposes this may however be switched-off since logging-off with many data points may take some time.

1.1.1.12 COV-Resubscribe This setting determines after how many seconds the log-ins of the COV-notifications are repeated, a setting of “0“ deactivates this function. If the values are unequal to “0” an additional safety period of 20 seconds is added to the entered interval.

9.7.3.

Event-settings / Intrinsic Reporting

1.1.1.13 use unconfirmed Events If this setting has been selected, the log-ins for the notification for events or alarms (“Intrinsic Reporting”) are effected with the attribute “unconfirmed“, which means there is no transport acknowledgement which ensures that these messages have arrived the recipient (BACnet OPC-server).

1.1.1.14 use confirmed Events If this setting has been selected, the log-ins for the notification for events or alarms (“Intrinsic Reporting”) are effected with the attribute “confirmed“, which means after receipt of an “EventNotification” message the BACnet OPC-server sends a transport acknowledgement to the sending device. This ensures that these messages have arrived the recipient (BACnet OPC-server). MBS GmbH Römerstrasse 15 D-47809 Krefeld

Tel.: +49 / 21 51 / 72 94-0 FAX: +49 / 21 51 / 72 94-50 www.mbs-software.de

30

1.1.1.15 do not use Intrinsic services If this setting has been selected, no log-ins for events or alarms are initiated to BACnet-servers. Recommendation: If possible please use confirmed events if this is also supported by the connected devices.

1.1.1.16 Delete Intrinsic log-ins after program end This setting should be active in the regular operation of the BACnet OPC-server so that logged-in notification services for events and alarms may be logged-out again in the devices after program end. For service purposes this may however be switched-off since loggingoff with many data points may take some time.

9.7.4.

Download-settings

1.1.1.17 Global Broadcast If this setting is active the “Who-Is“ inquiry is sent to all networks as global broadcast command.

1.1.1.18 Local Broadcast If this setting is active the “Who-Is“ inquiry is only sent to that network in which the BACnet OPC-server is running as local broadcast command.

1.1.1.19 Remote via network number If this setting is active the “Who-Is“ inquiry is sent to a certain network as local broadcast command.

31

MBS GmbH Römerstrasse 15 D-47809 Krefeld

Tel.: +49 / 21 51 / 72 94-0 FAX: +49 / 21 51 / 72 94-50 www.mbs-software.de

1.1.1.20 Waiting time for the answer This setting determines the period of time which the BACnet OPCserver should wait for “I-Am“- messages from devices after sending out a “Who-Is“ inquiry.

1.1.1.21 Automatic determination of the access rights (Unfortunately) BACnet does not offer any possibility to read-out dynamically the access rights to objects and their properties. Therefore the BACnet OPC-server offers a function which may be activated with the help of this setting. This function works on the principle of reading a value combined with the effort to re-write the read value. Before writing it is verified whether the properties ”Out-Of-Service“ or “Reliability“ (if supported) allow an access to the object. If this function is not activated, the identification (and possible negative acknowledgement) of write accesses takes place while the program is running which means while an OPC-client is writing.

1.1.1.22 OPC-reference names If this setting is activated OPC-Tags will be composed of object name (property: object_name) and the property name. If this setting is not active, OPC-Tags will be composed of object type and object instance.

MBS GmbH Römerstrasse 15 D-47809 Krefeld

Tel.: +49 / 21 51 / 72 94-0 FAX: +49 / 21 51 / 72 94-50 www.mbs-software.de

32

9.7.5.

Property-Filter

In this dialog it may be determined per BACnet object type which properties shall be taken over into the parametrization list for the dynamic download of information. Porperties marked in blue will be taken over, not selected properties will be ignored. For setting the filter please select at first the object type, afterwards please deactivate those properties which should not be taken over into the parametrization list. Please proceed according to this method for all further BACnetobjects.

33

MBS GmbH Römerstrasse 15 D-47809 Krefeld

Tel.: +49 / 21 51 / 72 94-0 FAX: +49 / 21 51 / 72 94-50 www.mbs-software.de

9.7.6.

Poll-Filter

In this dialog all those objects and properties are determined which should be actualized via polling in any case. The application purpose is that COV log-ins can only be allowed for certain objects. The properties marked in the list will be polled in any case (and not logged-in via COV). For setting please select the desired object and by selection of the corresponding property you determine in the list that the selected property shall be polled. Please proceed according to this method for all further BACnetobjects.

MBS GmbH Römerstrasse 15 D-47809 Krefeld

Tel.: +49 / 21 51 / 72 94-0 FAX: +49 / 21 51 / 72 94-50 www.mbs-software.de

34

9.7.7.

Time service/Priority

1.1.1.23 Global priority With this setting you may determine the priority for wirte accesses. Please note the procedure for command priorization which is described in detail in the BACnet-Standard ASHRAE 135-1995.

1.1.1.24 Time service (available from software option 2 onwards) With this setting the time synchronization may be determined. If the BACnet OPC-server is operated as Time-Master it may be determined additionally at which time intervals a synchronization of the BACnetdevices should be effected. As base serves the time of the computer. If the BACnet OPC-Server is operated as Time-Slave, the time of the computer is set accordingly when receiving a synchronization message.

1.1.1.25 Local network number This setting determines the network number which will be taken over when entered in the notification class objects or at COV log-ins. Normally it is sufficient to specify the local network with the number “0“. If this is not accepted by BACnet-servers this network number may be adjusted according to the given number of the BACnetserver. Please note that this setting will be effected globally for the whole program.

35

MBS GmbH Römerstrasse 15 D-47809 Krefeld

Tel.: +49 / 21 51 / 72 94-0 FAX: +49 / 21 51 / 72 94-50 www.mbs-software.de

9.7.8.

CC6 Data accesses

(available from software option 2 onwards)

1.1.1.26 Conformance Class 6 accesses These settings determine which services should be used for the access to BACnet-servers of Conformance Class 6.

1.1.1.27 Maximum amount of asynchronous processes This setting determines the amount of parallel services. Please note the hints in the chapter “Optimization of the performance“.

MBS GmbH Römerstrasse 15 D-47809 Krefeld

Tel.: +49 / 21 51 / 72 94-0 FAX: +49 / 21 51 / 72 94-50 www.mbs-software.de

36

10. Optimization of the performance The performance of the system may of course only be as good respectively as quick as the weakest parts of the system. This means that unfavorable constellations may and should be avoided by a skillful system configuration, however it is not possible to be quicker than the devices themselves, e.g. if they are slow devices. Here some hints for possible configurations.

10.1. Use of the Cache-function The BACnet OPC-server has the possibility to permanently show a present representation of the values (Cache-function). This enables a rapid answer via OPC at the time of logging-in even though it may happen that not always the most present value is taken, however at least the last valid value. On the other side this procedure implies a possible delayed starting behavior until all values have been initialized for the first time. On the other side it may in individual cases be quicker to switch-off the Cache-function in order to call the data only when they are asked for e.g. when calling a picture via OPC. A general statment which of the possibilities is better suited is not possible due to the partly different requirements (visualization, trend recording, error processing and so on) and therefore has to be considered in the individual case.

10.2. Optimizing the parametrization list Delete unnecessary parameters from the parametrization list if you have switched-on the Cache-function. By doing so the communication is restricted to those properties which really may be asked for. Parameters which are never logged-in via OPC do not belong in the parametrization list.

37

MBS GmbH Römerstrasse 15 D-47809 Krefeld

Tel.: +49 / 21 51 / 72 94-0 FAX: +49 / 21 51 / 72 94-50 www.mbs-software.de

10.3. Optimizing the BACnet-communication Please note above all two important properties in the BACnet settings: APDU_Timeout and APDU_Retries. The parameter APDU_Timeout sets the period of time which should be waited for an answer for the device. The parameter APDU_Retries sets the amount of retries which should be effected after a Timeout (that means a missing answer from the device). Just imagine the following situation: A certain device never answers to a certain inquiry, e.g. to a Read-request for a certain property since this property is not supported (this is a simulated error since BACnet provides for a special Errorcode for such situations, however this is only an example). If you now have set a Timeout period of 10 seconds with 6 Retries, alone for this single parameter you have a whole period of delay of 60 seconds, that is one minute, until it is continued with the next parameter. This means that if it is a permanent state, it might happen that changes of values of other (valid) parameters are delayed for a whole minute. Please try to find and delete these error sources e.g. by using a protocol analyzer.

10.4. Important hint “Parallel Services“ A further important parameter which may influence the system performance is the amount of parallel services. In the BACnet properties this is set under “CC6 data accesses/Amount of asynchronous processes“. BACnet allows for the processing of up to 255 parallel services, e.g. inquiries in order to communicate as fast as possible with connected devices. In the BACnet OPC-server this amount may be set in the range of 1-60. Here problems might occurr when co-operating with devices which cannot support this (high) amount of parallel services since e.g. the respective communication buffers are restricted. The vendor has set the default to the value 30, this value may however be too high for certain devices.

MBS GmbH Römerstrasse 15 D-47809 Krefeld

Tel.: +49 / 21 51 / 72 94-0 FAX: +49 / 21 51 / 72 94-50 www.mbs-software.de

38

The described problem manifests itself in the fact that not all inquiries can be answered correctly by the device following value inquiries which are executed when using the Cache-function cyclically in the background. This implies that these parameters are marked as “Bad“ . This can be observed by switching-on the value display. If in the Run-mode repeatedly “blocks” of parameters take the “Bad” state and after a short time the “Good” state again, most probably the amount is set too high. Remedy: Set back the amount of the parallel services to a value which the connected devices can proceed, if you are unsure you may also set the value “1“. This in any case ensures that this problem will not occurr.

10.5. Automatic link monitoring The BACnet OPC-server supports an automatic link monitoring to connected BACnet-devices. Every 10 seconds a „Who-Is“-inquiry is sent. If parametrized devices fail to answer, a link failure is detected. In this case the state of the status display changes. Furthermore the OPC-Tag “DEVICE_ONLINE_STATUS“ is set to the value „False“.

39

MBS GmbH Römerstrasse 15 D-47809 Krefeld

Tel.: +49 / 21 51 / 72 94-0 FAX: +49 / 21 51 / 72 94-50 www.mbs-software.de

11. Reset of the Priority-Array The BACnet-standard provides for a priority level ranging from 1-16 for so-called “commandable-objects“ which means objects on which may be written. Output objects and depending on the server implementation perhaps value objects belong to these objects. In BACnet the cancellation of a set value is effected by writing a NullValue on the Present-Value of the object. In this case the BACnetserver deletes the value from the priority list so that the next value becomes valid. The BACnet OPC-server also reflects this behavior via the OPC-Tags which represent a Present-Value. The reset of a written value via OPC is effected from the clients side by means of an OPC-write access to the Present-Value with the value “VT_NULL”.

MBS GmbH Römerstrasse 15 D-47809 Krefeld

Tel.: +49 / 21 51 / 72 94-0 FAX: +49 / 21 51 / 72 94-50 www.mbs-software.de

40

12. Simple test structure on a PC The following steps describe how you can easily realize a complete BACnet-test structure with the BACnet OPC-server on a PC. 1. Install Windows-NT 4.0 and a corresponding Service Pack 2. Install the network card support 3. Even if you want to use the test structure only locally on a single computer, a network card as well as the necessary drivers are required 4. Install the BACnet OPC-server software following the instructions during installation 5. After rebooting your PC the below-described structure may help you to follow the complete signal way from a BACnet Server to OPC : At first please start one of the BACnet example-servers which is included in the packet, e.g. the program “COVSERV.EXE“. These programs are MS-DOS based applications simulating BACnet-serverfunctions. COVSERV.EXE: This is a server supporting COV log-ins as well as COVmessages. INTSERV.EXE: This is a server reporting events and alarms via Intrinsic Reporting. PROPSERV.EXE This is a server simulating all properties of the supported BACnet-objects. TEMPSENS.EXE This is a server simulating a simple temperature sensor, additionally the amount of objects ranging from 20-100,000 may be defined and error states resulting from failing telegrams or definable Errorcodes may be simulated. After that please start the BACnet OPC-server and select the menu point “Download from network”. The data points of the BACnetserver will be read-out and represented. Now change from the parametrization mode to the Run-mode. Start your OPC-based visualization software or the program “OPC Data-Client“, which is also packet contents. For verification of the OPC Event/Alarm interface please start the program “OPC AlarmClient“ or another OPC-application supporting the E/A-specifications. Select the BACnet OPC-server in the menu “OPC/Connect“. After that you may add by means of the menu point “OPC/Add Item” the properties of the BACnet-objects in the list of the data points to be

41

MBS GmbH Römerstrasse 15 D-47809 Krefeld

Tel.: +49 / 21 51 / 72 94-0 FAX: +49 / 21 51 / 72 94-50 www.mbs-software.de

represented and you may observe them there or if the properties are writable these can be changed accordingly. Furthermore you may cause changes of value in the example servers enclosed in the delivery packet and observe them through the whole signal way. To do so please enter a question mark in the DOS surface of the program. You will then receive a short help for operating the example program.

MBS GmbH Römerstrasse 15 D-47809 Krefeld

Tel.: +49 / 21 51 / 72 94-0 FAX: +49 / 21 51 / 72 94-50 www.mbs-software.de

42

13. Using the Import / Export-interface The BACnet OPC-server offers an import and export interface enabling to create parametrization files by import as text files and to export existing parametrization files as text files, e.g. for documentation purposes.

13.1. ASCIl-files as basis The text files serving as model are built-up in a special way. The key word “begin“ serves as separation between different areas respectively BACnet-objects. It introduces a new paragraph within the text file to which all following data refer. The ASCII characters CR (Carriage-Return) followed by LF (Line-Feed) serve as line separation. When using the below-mentioned key words please pay attention to the correct notation as well as to the observance of the use of capital and small letters.

13.2. APDU-parameters The global configuration parameters of the program (for the BACnetinterface as well as for the OPC-interface) are determined in the first paragraph of the text file. This paragraph is introduced by the key word “begin“ followed by “APDU props:“. If this paragraph is omitted, the standard values are taken. These however must not always match with the parameters used in the BACnet-network so that in any case the indication of these parameters is recommended. Paragraph mark: begin APDU props: Following parameters may be defined: • apdu-retries This value determines the amount of packet retries.

43



apdu-timeout (unit: s) This value determines the time interval which has to be waited for a telegram acknowledgement.



apdu-poll-delay (unit: ms) This value determines how long should be waited between two value inquiries.



apdu-framelength This value determines the maximum packet length.

MBS GmbH Römerstrasse 15 D-47809 Krefeld

Tel.: +49 / 21 51 / 72 94-0 FAX: +49 / 21 51 / 72 94-50 www.mbs-software.de



apdu-windowsize This value determines the window size for the packet transfer.



apdu-segments This value determines the maximum amount of segments.



apdu-global-write-priority This value determines the global priority of the write access program.



how_to_use_COV This value determines the way how COV should be supported. 0 = use unconfirmed COV 1 = use confirmed COV 2 = use no COV



resubscribe_COV (unitt: s) This value determines the period of time after which a new COVlog-in to the devices is effected. For safety purposes additional 20 s are added so that no changes of value may get lost.



unsubscribe_COV_on_exit This value determines if COV-log-ins should be logged-out with the “UnsubscribeCOV“ command when ending the program. 0 = COV-log-ins are not logged-out. 1 = COV-log-ins are logged-out with “UnsubscribeCOV“ .



unsubscribe_INT_on_exit This value determines if log-ins for Intrinsic Reporting are loggedout with the „RemoveListElement“ command when ending the program. 0 = log-ins for Intrinsic Reporting are not logged-out. 1 = log-ins for Intrinsic Reporting are logged-out with “RemoveListElement“ .



how_to_use_INT This value determines how to support Intrinsic Reporting. 0 = use unconfirmed Events 1 = use confirmed Events 2 = use no intrinsic Event-services



how_many_Slots This value determines the amount of parallel services.



Time-Master This value determines the support of the time synchronization. 0 = Time-Master

MBS GmbH Römerstrasse 15 D-47809 Krefeld

Tel.: +49 / 21 51 / 72 94-0 FAX: +49 / 21 51 / 72 94-50 www.mbs-software.de

44

1 = Time-Slave

45



Time-Resynch (unit: h) This value determines the time interval of the time synchronization if the program is configurated as Time-Master.



how_to_handle_OPC_request This value determines how to answer OPC-requests. 0 = OPC-requests are always answered from the Cache. 1 = OPC-requests are always read from the device. 2 = The decision is taken from the OPC-Flags.



how_to_handle_OPC_add This value determines how the value is transferred when new logins of OPC-data points are effected. 0 = The value is read in the device when logging-in. 1 = The value is initialized with the value from the Cache when logging-in and is read later.



do_initial_polling This value determines whether a representation of the values is produced. 0 = No representation of the values is produced. 1 = A representation of the values is produced.



wait_for_i_am (unit: s) This value determines the period of time which should be waited for “I-Am“-answers of devices after a “Who-Is“-message.



use_read_atomic_file This value determines the support of the file transfer functions. 0 = No file transfer functions are used. 1 = File transfer functions are used.



use_read_conitional This value determines if the “ReadPropertyConditional“ service should be used. 0 = ReadPropertyConditional is not used. 1 = ReadPropertyConditional is used.



use_read_range This value determines if the “ReadRange“ service should be used. 0 = ReadRange is not used. 1 = ReadRange is used.

MBS GmbH Römerstrasse 15 D-47809 Krefeld

Tel.: +49 / 21 51 / 72 94-0 FAX: +49 / 21 51 / 72 94-50 www.mbs-software.de



use_RPMWPM This value determines if the “ReadPropertyMultiple“ and “WritePropertyMultiple“ services should be used. 0 = ReadPropertyMultiple / WritePropertyMultiple is not used. 1 = ReadPropertyMultiple / WritePropertyMultiple is used.



use_device_com_ctrl This value determines if “DeviceCommunicationControl” should be used. 0 = DeviceCommunicationControl is not used. 1 = DeviceCommunicationControl is used.

MBS GmbH Römerstrasse 15 D-47809 Krefeld

Tel.: +49 / 21 51 / 72 94-0 FAX: +49 / 21 51 / 72 94-50 www.mbs-software.de

46

13.3. Device object parameter In the case of the Device-object the key word “begin“ is followed by the text “device:“ as well as by the object name (instance number) separated by semicolon and the name in the display. Paragraph mark: begin device:device(1990);BACnet-device In this example the device object is initiated with the object instance 1990. The properties of the device object which should be represented via OPC are listed in the following lines.

13.4. BACnet-objects In the case of BACnet-objects the key word “begin“ is followed by the text “device:“ as well as by the object name (instance number) separated by semicolon and the name in the display. Paragraph mark: begin object:analog-value(1);Analogvalue1 In this example the “Analog-Value“ object is initiated with the object instance 1. The properties of the object which should be represented via OPC are listed in the following lines. For each property the desired way of access for the OPC-access has to be mentioned. This is defined by the entry “R” for “Read-Only-Access” or “W” for ReadAnd-Write-Access” following the double point (see example). The following object types may be used: • • • • • • • • • • • • • • • • • • • •

47

analog-input analog-output analog-value averaging binary-input binary-output binary-value calendar command event-enrollment file group loop multi-state-input multi-state-output multi-state-value notification-class program schedule trendlog MBS GmbH Römerstrasse 15 D-47809 Krefeld

Tel.: +49 / 21 51 / 72 94-0 FAX: +49 / 21 51 / 72 94-50 www.mbs-software.de

13.5. Example of a parametrization file as text file This example contains a projecting for a device object as well as an analoginput object. begin APDU props: apdu-retries = 3 apdu-timeout = 3 apdu-poll-delay = 0 apdu-framelength = 1476 apdu-windowsize = 16 apdu-segments = 32 apdu-global-write-priority = 16 how_to_use_COV = 1 how_to_use_INT = 1 how_many_Slots = 30 Time-Master = 0 Time-Resynch = 24 how_to_handle_OPC_request = 2 how_to_handle_OPC_add = 1 do_initial_polling = 1 wait_for_i_am = 5 use_read_atomic_file = 1 use_read_conitional = 1 use_read_range = 1 use_RPMWPM = 1 use_device_com_ctrl = 1 begin device:device(1990);device(1990) apdu-timeout : W application-software-version : R daylight-savings-status : R description : R firmware-revision : R local-date : R local-time : R location : R max-apdu-length-accepted : W model-name : R number-of-apdu-retries : W object-identifier : R object-list : R object-name : R object-type : R protocol-conformance-class : R protocol-object-type-supported : R protocol-services-supported : R protocol-version : R segmentation-supported : R system-status : W utc-offset : R vendor-identifier : R vendor-name : R begin object:analog-input(1);analog-input(1) description : R device-type : R event-state : R max-pres-value : R min-pres-value : R object-identifier : R object-name : R object-type : R out-of-service : W present-value : W reliability : R resolution : R status-flags : R units : R

MBS GmbH Römerstrasse 15 D-47809 Krefeld

Tel.: +49 / 21 51 / 72 94-0 FAX: +49 / 21 51 / 72 94-50 www.mbs-software.de

48

update-interval : W

49

MBS GmbH Römerstrasse 15 D-47809 Krefeld

Tel.: +49 / 21 51 / 72 94-0 FAX: +49 / 21 51 / 72 94-50 www.mbs-software.de

14. Abbreviations and important terms Acknowledge

Bestätigen

AddListElement

Hinzufügen eines Eintrags in eine Liste

ASHRAE

American Society of Heating, Refrigerating and AirConditioning Engineers, INC. Amerikanische Vereinigung der Heizungs-, Kälteund Klima- Ingenieure

ANSI

American National Standards Institute Nationales Normungsinstitut Amerika

Array

Speicherbereich mit festgelegter Größe, kann eine bestimmte Anzahl festgelegter Daten aufnehmen

BACnet

Abkürzung für Building Automation and Control Network Mit dem Begriff BACnet ist der ASHRAE-Standard 135-1995 gemeint

Bit

kleinste Einheit der EDV, bildet die Zustände 0 oder 1 ab

BTA

Abkürzung für betriebstechnische Anlage

ChangeOfBitstring

Änderung einer Folge von Bits

ChangeOfState

Änderung eines Zustandes

ChangeOfValue

Änderung eines Wertes

Client

Gerät, welches auf Daten anderer Geräte zugreift und diese weiterverarbeitet

MBS GmbH Römerstrasse 15 D-47809 Krefeld

Tel.: +49 / 21 51 / 72 94-0 FAX: +49 / 21 51 / 72 94-50 www.mbs-software.de

50

CommandFailure Fehler beim Ausführen eines Kommandos (Stellbefehls) Condition

Bedingung

Confirmed

bestätigte Datenübertragung, der Empfänger quittiert den Empfang

Conformance Class COV

Konformitätsklasse

Abkürzung für Change of Value BACnet-Dienst, der Wertänderungen an angeschlossene BACnet-Clients meldet

CreateObject

Erzeugen eines Objektes

DataLinkLayer

Schicht 2 des ISO/OSI Schichtenmodells für Netzwerkkommunikation, beschreibt die Sicherungsschicht einer Datenübertragung

DDC

Abkürzuung für Direct Digital Control Intelligente Controller, die in einer betriebstechnischen Anlage, selbständig Steuerungs- und Regelungsaufgaben ausführen können.

Device

Gerät

DeleteObject

51

MBS GmbH Römerstrasse 15 D-47809 Krefeld

Löschen eines Objektes

Tel.: +49 / 21 51 / 72 94-0 FAX: +49 / 21 51 / 72 94-50 www.mbs-software.de

Event

Ereignis Ereignisse treten aufgrund von Zuständsänderungen innerhalb der betriebstechnischen Anlage auf

File

Datei

Floating Limit

Grenzverletzung eines Fließkommawertes

Functional Group Funktionsgruppe Gateway

Hiermit ist ein Gerät gemeint, das eine Datenumsetzung von unterschiedlichen Protokollen ermöglicht.

I-Am

„Ich bin...“

I-Have

„Ich habe...“

LONTalk

Local Operating Network Talk (=Sprechen) Datenprotokoll der Firma Echelon konzipiert für die Feld- und Automationsebene der Gebäudeautomation

MAC-Adresse

Medium Access Control Eindeutige Netzwerkkartenadresse, wird vom Hersteller der Netzwerkkarte weltweit eindeutig vergeben

Minimum-On-Time

Minimale Einschaltzeit

Minimum-Off-Time

Minimale Ausschaltzeit

Multiple MBS GmbH Römerstrasse 15 D-47809 Krefeld

Mehrfach Tel.: +49 / 21 51 / 72 94-0 FAX: +49 / 21 51 / 72 94-50 www.mbs-software.de

52

Notification

Benachrichtigung

Objekt

Hiermit sind BACnet Objekte gemeint. Diese stellen Abbildungen realer Größen , zum Beispiel Meßwerte (Analog Input) oder Schalterstufen (Multistate) dar.

Out-Of-Range

Wert außerhalb des Meßbereichs

PICS

Protocol Implementation Conformance Statement Dokument, welches den implementierten BACnet Funktionsumfang eines Gerätes bzw. einer Software kennzeichnet.

Priority_Array

Speicherbereich, der zur Aufnahme der Schreibprioritäten dient

Property

Eigenschaft Hiermit sind Eigenschaften von BACnet Objekten gemeint, zum Beispiel der aktuelle Wert, obere/untere Grenze, usw.

Range

53

Bereich

Relinquish_Default

Vorgabewert, wenn das Priority_Array leer ist

RemoveListElement

Entfernen eines Eintrags aus einer Liste

Remote

entfernt, Ausführen einer Funktion in einem entfernten (Remote-) Gerät

Read

Lesen

MBS GmbH Römerstrasse 15 D-47809 Krefeld

Tel.: +49 / 21 51 / 72 94-0 FAX: +49 / 21 51 / 72 94-50 www.mbs-software.de

Server

Gerät, welches Daten anderen Geräten bereitstellt

Synchronization Synchronisierung von Daten Time

Zeit

Unconfirmed

unbestätigte Datenübertragung, keine Quittierung vom Empfänger erforderlich

Who-Is

„Wer ist...“

Who-Has

„Wer hat...“

Write

Schreiben

MBS GmbH Römerstrasse 15 D-47809 Krefeld

Tel.: +49 / 21 51 / 72 94-0 FAX: +49 / 21 51 / 72 94-50 www.mbs-software.de

54

MBS GmbH Römerstrasse 15 D-47809 Krefeld www.mbs-software.de [email protected]