BACnet Configuration Using the Workbench

NOTE: The following describes how to configure BACnet settings via the Workbench.

GENESIS64’s BACnet implementation is an out-of-the-box solution that does not need configuration by default. BACnet devices in a local network are discovered automatically, together with their specific settings and address spaces (provided objects and their properties), which are used for connection.

The steps described below are useful in cases where you need to:

• Override settings of a specific, automatically discovered device, or
• Override objects and/or property names exposed by specific devices, or
• Add a new device that has not been automatically discovered (e.g. because it is in a different IP network subnet).

BACnet Settings for Devices

It is important to realize that this BACnet Configuration Provider is used for the configuration of Global BACnet runtime settings; for providing the BACnet runtime connection with information for specific BACnet devices and for driving what information is exposed by BACnet runtime (device, object and property names).

1. Launch the Workbench.
2. Click the BACnet icon in the Workbench project explorer.
3. Once your BACnet configuration opens, you can select Devices by double-clicking on the item and go to the ‘Communication’ tab, then you will see the setting for your devices.

Devices - Communication Tab

4. Enter the settings for: APDU Timeout, APDU Segment Timeout, and APDU Retries in the ‘Communication’ tab and Default Polling Rate and Default Priority in the ‘General tab’

• APDU Timeout [ms]: The APDU_Timeout property, of type Unsigned, shall indicate the amount of time in milliseconds between retransmissions of an APDU requiring acknowledgment for which no acknowledgment has been received. The default value for this property shall be 3,000 milliseconds for devices that permit modification of this parameter. Otherwise, the default value shall be 60,000 milliseconds. This value shall be non-zero if the Device object property called Number_Of_APDU_Retries is non-zero.

• APDU Segment Timeout [ms]:  The APDU_Segment_Timeout property, of type Unsigned, shall indicate the amount of time in milliseconds between retransmission of an APDU segment. The default value for this property shall be 2000 milliseconds. This value shall be non-zero if the Device object property called Number_Of_APDU_Retries is non-zero. See 5.3. If segmentation of any kind is supported, then the APDU_Segment_Timeout property shall be present.

• APDU Retries: The Number_Of_APDU_Retries property, of type Unsigned, shall indicate the maximum number of times that an APDU shall be retransmitted. The default value for this property shall be 3. If this device does not perform retries, then this property shall be set to zero. If the value of this property is greater than zero, a non-zero value shall be placed in the Device object APDU_Timeout property.

• Expire Time [s]: Specifies the time when the unused values are removed from the BACnet cache (in seconds).  This should be set large enough to avoid thrashing of the system.  For example if a person is paging through graphics the system will be subscribing to object/properties.  If he leaves the graphic , if this parameter was set to zero, the BACnet engine would cancel COV subscription to the device if COV, stop polling, and then delete from the subscription cache.  If he paged immediately  back to the same page then the system would have to re-establish connections to the data, poll it, and re-add to subscribe cache.  This should be set high enough, so that object/properties stay in the cache and subscribed until the user session is finished.

• Subscribe Timeout: This is actually the Subscribe Cycle time. -  The BACnet engine will only process requests, any request including COV subscriptions and Read Property requests, based on a cycle as determined by this setting.  For example if this is set at 5000, (5 seconds),  all requests will be accumulated for 5 seconds, and at the end of this period all requests will be sent to protocol stack for processing.

• Re-Subscribe COV Period [s]: This is actually the Subscribe Cycle time. -  BACnet requires that all COV subscriptions have a timeout.  It is not possible to create a permanent subscription. This parameter sets how often all COV subscriptions will be re subscribed. Resubscription cause a significant load on the controllers and on the IO server.  Consequently the setting of this parameter should be as infrequent as possible, but allowing for the fact that if there is any failure within the controller that causes it to loose a subscription, the IO server will not attempt to reestablish until this defined time.  Note that this operation only applies to device that have been previously discovered, and are in the IO Servers device cache.  New devices will require the discovery process to be activate.

• Offline Device Polling: Once the IO server detects a device is offline, it stops all attempts to communicate with this device or any object in that device.  Periodically  based on this setting the IO server will re-attempt to establish communications with this device.  It successful the device will be placed online and all required communications to objects in that device will attempt to re-establish.

• Max TSM Per Device: The maximum number of BACnet Transactions (ReadProperty, COV Subscribe, WritePropery), that can simultaneously be in active (in a non null state), to a device. When this number is reached, no further transactions will be processed to the device, until one or more transactions are closed.  This can be used to throttle activity to a device.

• Max TSM Per Router: The maximum number of BACnet Transactions (ReadProperty, COV Subscribe, WritePropery), that can simultaneously be in active (in a non null state), and sent through a specific BACnet router. When this number is reached, no further transactions will be sent through that router, until one or more transactions are closed.  This can be used to throttle activity through a router.  Please note that some devices, such as Automated Logic LGR’s, are acting simply as BACnet routers, so that all requests are going directly to the underlying MSTP serial bus. This feature can be used to control the amount of activity being imposed on these busses. 

5. If you made changes, click the Apply button.
6. Now, you need to Add a New Device. Right-click on Devices in the Project Explorer and choose Add Device to Database OR click the Add Device to Database button in the Edit section of the Home ribbon. The Device properties will display.

BACnet Device

7. Type a name in the Name textbox.
8. Type a description in the Description textbox. This is optional.
9. Type a device ID in the Device ID box.
10. You can leave the default polling rate as it is unless you want to override it. If so, then select the ‘Override Default Polling Rate(s)’ checkbox and enter the value (in seconds) in the text entry field. The same goes for 'Override Default Priority'.
11. Enable Static Binding (optional).
12. Type a Network number.
13. You can select a MAC (hex) ID, IP Address or Port number and then enter the required info in the respective text entry field.
14. Click on the Apply button when you are satisfied with the configuration.
15. Now, you are going to Create a New Object under your device.
16. Right-click on your Device and select Add Object or Add Object to Database OR click the Add Object or Add Object to Database button in the Edit section of the Home ribbon. A 'Create Object' window may open, requesting you to select the type of objectObject Types include:
    
    Access Door
    Accumulator
    Analog Input
    Analog Output
    Analog Value
    Averaging
    Binary Input
    Binary Output
    Binary Value
    Calendar
    Command
    Device
    Event Enrollment
    Event Log
    File
    Group
    Life Safety Point
    Life Safety Zone
    Load Control
    Loop
    Multistate Input
    Multistate Output
    Multistate Value
    Notification Class
    Program
    Pulse Converter
    Schedule
    Structured View
    Trend Log
    Trend Log Multiple you'd like to create, as well as create an empty object, specify an instance and/or specify a name. If this occurs, make your selections, then click OK. If not, the Object properties will display.

    

BACnet Object

17. Type a name in the Name textbox and provide a Description (optional).
18. Specify the Object Type in the dropdown menu (Analog Input by default) and specify the right Instance # (usually 1). The Object ID should be generated automatically.
19. You can leave the default polling rate as it is unless you want to override it. If so, then select the ‘Override Default Polling Rate(s)’ checkbox and enter the value in second. The same goes for 'Override Default Priority'.
20. Click the Apply button.
21. Now, you are going to Create a New Property under your object. Right-click on your Object and choose Add Property OR click the Add Property button in the Edit section of the Home ribbon. The Property settings will display.

BACnet Property

22. Type a name in the Name textbox and a description in the Description textbox (optional)
23. Type a property number in the Property text box.
24. You can leave the default polling rate as it is, unless you want to override it. If so, then select the ‘Override Default Polling Rate(s)’ checkbox and enter the value (in second) in the text entry field. The same goes for 'Override Default Priority'.
25. Click the Apply button.
26. The last thing you need to do is Create a Port for your device. Right-click on Ports in the Project Explorer and choose Add Port OR click the Add Port button in the Edit section of the Home ribbon. The Port properties will appear.

BACnet Port

27. Type a name in the Name textbox and provide a Description (optional).
28. You can then enter the Channel Type, Network #, Adapter and the IP Settings.
29. Click Apply to confirm.

NOTE: Default BACnet communication is based on IP protocol, where the default port (47808) can be changed (under Ports) if you really need it to be, but, in most cases, you can use the default settings. Also notice that Ports in the Workbench are ICONICS proprietary interfaces created specifically for BACnet communication, where the IP port is not equal to a Workbench port.

See Also:

BACnet Configuration Quick Start

BACnet Client-Server Architecture

BACnet in Workbench64 and GraphWorX64