Possible config entries of the BACnet driver

Entry	Type	Default	Range	Description
alarmExternAckFirst	bool	0	0\|1	Due to the combination of the WinCC OA alert class acknowledgement mode "came or went must be acknowledged" and the BACnet notification class "AckRequired: TO_OFFNORMAL=1, TO_NORMAL=0", the following behavior may occur: Alarms are acknowledged in the wrong order (WENT before CAME). Therefore, alarms in the device won't be acknowledged. Setting this entry will avoid this behavior, however, it must only be set if the combination is really needed in the project. By setting this entry to 1, the transition that requires extern acknowledgement will be acknowledged first. Thus, you can ensure acknowledgement in the devise (see also Intrinsic and Algorithmic Alarming).
APDURetries	int	3	1 - 5	Defines the number of retransmissions, if no response is received from the device.
APDUTimeout	int	2000	500 - 5000	Defines the time in milliseconds, which is used to wait for a telegram response.
autoGQ	uint	0	0 - 3	Specifies whether the driver is executing an automatic general query (GQ). 0 -> no automatic GQ 1 -> automatic GQ during connection establishment 2 -> automatic GQ during redundancy switchover 3 -> automatic GQ during connection establishment and redundancy switchover
connUserBitPrio	int	8	0 - 16	Defines the user bit, which is used by the driver for command prioritization (see chapter Command Prioritization). 0 -> no user bit is used and the value is written normally.
COVLifeTime	uint	7200 (sec)	>= 0	This config entry prevents that COVs without time limit are used. I.e. COVs are registered with an expiration time. After the half time the subscription is renewed (by default every 60 minutes). If the value is 0, it is registered without expiration time.
deviceStatusPollTimeout	int	30	> 0	time interval in seconds in which the driver checks the life beat of the devices.
eventGQMode	int	0	0\|1	If the eventGQmode is activated (=1) the additional values will also be transmitted with the GetEventInformation. Note The ReadPropertyMultiple service is required for this feature.
localDeviceId	uint	10	> 0	The local ID for the device object of the WinCC OA driver. This ID will appear to all other devices on the network and thus it must be unique.
localDeviceName	string	WinCCOA_OWS_<localDeviceId>	-	The local name for the device object of the WinCC OA driver. This name will appear to all other devices on the network.
maxNumForReadMultiple	int	8	> 0	Specifies the maximum number of properties that are read in one Read Multiple Request. Read Requests are grouped into Multiple Read Requests in order to improve the performance during requests in large projects.
mapEventValuesToComment	bool	0	0\|1	Obsolete since version 3.10. Defines whether the string with the Notification parameters of an event type (CHANGE_OF_STATE, COMMAND_FAILURE or OUT_OF_RANGE) should be written to the alarm comment of the Event_State property of the corresponding BACnet data point (TRUE (=1) = yes, FALSE (=0) = no). Fur further information on event types see Intrinsic and Algorithmic Reporting.
mapOutOfServiceToInvalid	bool	0	0\|1	Specifies whether the driver sets WinCC OA invalid bit, if BACnet OUT_OF_SERVICE status bit is set.
processIdentifier	uint	1	> 0	This entry defines the process identifier, which is used by the BACnet driver for COV registration and alarm acknowledgement.
reportHomelessAlarms	bool	0	0\|1	Specifies whether the driver maps alarms/events, which cannot be mapped to addresses, to the DPE _Bacnet.State.HomelessAlarm in string form.
requestsPerCycle	int	10	> 0	Defines how many BACnet requests are issued in one driver cycle. If a low value is set , the request load, through frequent queries, is reduced, what reduces also the data throughput. This config entry defines the number of requests per device.
requestQueueMaxSize	int	1000	> 0	The BACnet driver manages the output queue for different BACnet requests. This config entry determines the maximum size of this queue. If this size is exceeded, requests are discarded and error messages are written to the WinCC OA log.
sendUnicastIam	bool	0	0\|1	Defines whether an I-Am answer to an Who-Is is sent as Unicast. Per default, this entry is 0 and I-Am answers will be sent as broadcasts. However, sometimes there is no BBMD functionality. Therefore, broadcast answers will be blocked. This problem can be solved with sendUnicastIam=1 .
userBitStatusFlagx	int	0	0 - 31	Defines how the BACnet status flags are mapped on the WinCC OA user bits. The value 0 means that the corresponding status flag is not mapped. The value for "x" stands for the bit number in the status flags word: 0 -> in alarm 1.-> fault 2 -> overwritten 3 -> out of service 4 -> not specified 5.-> not specified ... 31 -> not specified
userByteAlarmPrio	uint	0	0 - 4	Obsolete since version 3.10. This config entry enables the mapped BACnet priority (see Config.AlarmPrioMapping) also for the BACnet Application. This config entry defines to which user byte number (1 - .4) the BACnet priority is reflected. Default is 0 (= no mapping).
useWriteMultiple	bool	0	0\|1	Defines if the WriteMultiple service is used for grouping write requests. If the result of write requests should be shown in the application this entry must be set to false.
userBitTrendLog	uint	0	0 - 32	This entry defines the user bit which will be set if the data of a TrendLog object shall be saved additionally to a set property and not only to the Log_Buffer property. If this entry is set to 0 or not defined, the values will only be saved inside / can only be read from the Log_Buffer property This config entry provides additional protection against data loss, for example, if a TrendLog object is not longer needed and will be deleted (thus also the data from his Log_Buffer property will be lost) its values can still be read from the defined user bit. If the TrendLog values should be written as correction values (this is necessary iff original values of the trended property also are written by other sources) it is required to set also the config entry histDataBits in the [bacnet] section.