Internal data points of the BACnet driver

With this data point element browsing for connected devices can be startedin the BACnet network. Thereby a range for the device ID can be entered. If the string is left empty, the whole ID range will be browsed. A range of the device IDs, which shall be browsed, can be input in the following format:

"<device low limit>-<device high limit>"

Example: "100-200"

Contains the supported properties of these objects, which have been found in the BACnet device.

This contains all supported properties only then, if the browsed device supports segmentation and ReadPropertyMultiple.

Defines the mapping of BACnet alarm priorities to WinCC OA alarm classes.

A mapping has the following format:

<BACnet startPrio1> <WinCC OA alarmClass1>

<BACnet startPrio2> <WinCC OA alarmCclass2>

...

An example for such a mapping is:

0 BACnet_danger
50 BACnet_alarm
100 BACnet_warning
200 BACnet_info

I.e.: The BACnet priorities 0-49 belong to the alarm class "BACnet_danger", 50-99 to "BACnet_alarm", 100-199 to "BACnet_warning" and 200-255 (highest BACnet priority) to "BACnet_info".

For further information see Intrinsic and Algorithmic Alarming.

To this data point element all alarms/events are mapped, which can not be assigned to an address. This takes place only if the corresponding config entry reportHomelessAlarms is set.

The information of the alarm/event are coded in a string with the following syntax:

<deviceName>.<deviceId>.<objectType>.<instance>.<eventType>.

<eventState>.<alertType>.<priority>

De-/re-activation of the communication.

0 → The communication of the device is activated

1 → The communication of the device is deactivated (The device will neither respond to services nor initiate any service. It will only respond to the next CommunicationControl service.)

2 → Disable the initiation of messages by the device (The device will respond to services but not initiate any service except IAm service.)

FALSE (0) - the communication of the device on the bus will be deactivated (DM-DCC-A service).

TRUE (1) - the communication of the device on the bus will be re-activated.

Triggers a general query (GQ) for the corresponding device.

The passed value defined the type of data for query:

0 → GQ for values and events

1 → GQ for values only

2 → GQ for events only

3 → Reset UNKNOWN_PROPERTY addresses (this command is triggered, for example, by clicking the "Reset Properties" button in the device faceplate)

10 → GQ for descriptions

11 → GQ for units

Triggers a reinitialization of the device (DM-RD-A service), if a corresponding value is written to the data point element.

Following values can be used:

• 0 → Cold start

• 1 → Warm start

Synchronizes the time in the device with the time of this data point element.

If on the data point element is set to zero-time, the driver takes the current time and sends it with the telegram (DM-TS-A service).

Via this data point elements special services can be set down to the device. The first element of the dyn_string contains the command and parameters. These are the commands with possible parameters:

• CreateObject

  <object type>

  <object instance> (optional)

  <object name> (optional)

• DeleteObject

  <object type>

  <object instance>

• GetProperties

  <object type>

  <object instance>

• LifeSafetyOperation

  <requesting source>

  <BACnet LifeSafetyOperation Code>

  <object type> (optional)

  <object instance> (optional)

• SendTxtMsg

  <message to be sent>

The object type must be passed as string (as stated in the peripheral address) to the commands. The response is returned via the data point element State.Service.

A file transfer using this datapoint is possible, for details see File Transfer.

Example:

CreateObject
 Schedule
 10
 SCH1
 SendTxtMessage
 This is a text for sending

On this data point element the information on static Address Binding of a device is written.

The format is:

<network number>:<IP address>:<port number>

For example: "1:192.168.152.20:47808"

If this data point element is empty, dynamic Address binding is used (the address information is updated automatically).

This data point element is used for different device settings, see also Advanced Configuration.

Following bits are currently used:

B0:

• 0 - Object browsing with property “All”

• 1 - Object browsing without property “All“ (properties are not available)

B1:

• 0 - Use device time for alert time

• 1 - Use reception time for alert time

B2:

• 0 - Interpret device timestamp at local time

• 1 - Interpret device timestamp as UTC

B3:

• 0 - Alarm texts are not retrieved during a general query.

• 1 - The driver reads the Event_Message_Texts property (if supported by the device) during a general query. This property contains the last alarm texts issued by the device i.e. alarm texts are updated by general queries.

B4:

• 0 - Do UTF-8 conversion for strings with ANSI X3.4 (UTF-8) encoding

• 1 - No UTF-8 conversion for strings with ANSI X3.4 (UTF-8) encoding

B5: See TrendLogs time based init

• 0 - TrendLogs were initialized without time-based reading
• 1 - TrendLogs are initialized with time-based reading

B8:

• 0 - No restart detection is used.

• 1 - Use restart detection by evaluation the COV notification

B9:

• Currently not in use but reserved for future extension

B10:

• 0 - Do not add driver to Restart_Notification_Recipients

• 1 - Do add driver to Restart_Notification_Recipients

B11:

• 0 - No COV registration renewal

• 1 - Do COV registration renewal

B12:

• 0 - Do no event general query

• 1 - Do event general query

B13:

• 0 - Do no data general query

• 1 - Do data general query

B15:

• 0 - The driver remains in the recipient list

• 1 - The driver is removed from the respective NOC recipient list (refer to Intrinsic and Algorithmic Alarming

B16:

• 0 - The driver registers with BACnet address to the Notification Class

• 1 - The driver registers with Device Identifier to the Notification Class

B17: See Wait for System_Status

• 0 - Connection is initialized even if the state "Operational" is not yet reached
• 1 - Wait for the state "Operational" before the connection is initialized

The bits 8-13 define the driver behavior if it detects a device restart.

Defines the mapping of BACnet alarm priorities to WinCC OA alarm classes for a BACnet device.

A mapping has the following format:

<BACnet startPrio1> <WinCC OA alarmClass1>

<BACnet startPrio2> <WinCC OA alarmCclass2>

...

An example for such a mapping is:

0 BACnet_danger
50 BACnet_alarm
100 BACnet_warning
200 BACnet_info

I.e.: The BACnet priorities 0-49 belong to the alarm class "BACnet_danger", 50-99 to "BACnet_alarm", 100-199 to "BACnet_warning" and 200-255 (highest BACnet priority) to "BACnet_info".

For further information see Intrinsic and Algorithmic Alarming.