Bacnet Ows Device Manager

The Bacnet Ows Device Manager (Figure A.21) is the default view for the BacnetOwsNetwork (and any BacnetOwsDeviceFolder), and provides all the same features as the regular Bacnet Device Manager.

Figure A.21. Bacnet Ows Device Manager is default view for BacnetOwsNetwork


Bacnet Ows Device Manager is default view for BacnetOwsNetwork

You discover BACnet devices in this view the same as in the Bacnet Device Manager view. For details, see About Bacnet Device Find Parameters. When doing a discover, the Add dialog provides standard fields for BacnetDevice components. See BacnetDevice properties.

NoteAll devices are represented as standard BacnetDevices in a BacnetOwsNetwork.

The bottom row of buttons in the Bacnet Ows Device Manager include two that are in the standard Bacnet Device Manager: TSynch and DeviceID. For more details, see Timesynch (TSynch) function and Device ID function.

Two additional buttons are in the bottom row in the Bacnet Ows Device Manager. These correspond to additional B-OWS functions that can be performed on BacnetDevices.

These additional buttons available in the Bacnet Ows Device Manager are:

Event Information

(Also in the Bacnet Aws Device Manager) This button in the Bacnet Ows Device Manager retrieves event information from the selected device, requesting all outstanding events from the BACnet device. The purpose of this feature is that if Niagara somehow missed receiving an event, you can still retrieve and acknowledge this event using the Event Information service. For example, the Niagara station may not have been running at the time the original event occurred.

If the GetEventInformation service is supported, this will be used to retrieve events. The events retrieved in this manner contain enough information to generate a valid acknowledgment to the remote device. These event summaries will be propagated to the Niagara Alarm Service through the alarm class assigned in the eventSummaryAlarmClass property of the Event Handler.

Event Handler configuration is contained within the Server layer configuration of the network’s BacnetComm container, as shown in Figure A.22.

Figure A.22. Event Summary Alarm Class (BacnetOwsNetwork)


Event Summary Alarm Class (BacnetOwsNetwork)

If the GetEventInformation service is not supported, but the GetAlarmSummary service is supported, the events will be retrieved using GetAlarmSummary. The GetAlarmSummary service retrieves only events with a Notify_Type of “alarm”, so events with a Notify_Type of “event” are not retrieved.

NoteThe GetAlarmSummary service has been deprecated by the BACnet Committee, and manufacturers should no longer be making devices that use it. Typically, this is seen only in older devices.

Event summaries retrieved using GetAlarmSummary do not have enough information to generate a valid acknowledgment, so they are not propagated to the Niagara Alarm Service. In this case, a dialog box is presented to the user, such as shown in Figure A.23.

Figure A.23. Alarm Summary dialog, showing a single object in alarm


Alarm Summary dialog, showing a single object in alarm

Enrollment Summary

(Also in the Bacnet Aws Device Manager) This button in the Bacnet Ows Device Manager retrieves a summary of all objects within the device that match a set of filter criteria that you define. When you click the Enrollment Summary button, a filter configuration dialog box is displayed, as shown in Figure A.24.

Figure A.24. Get Enrollment Summary request configuration dialog


Get Enrollment Summary request configuration dialog

Here you configure the various options to define the specific types of objects you wish to locate, and then click OK. The device is queried for a list of objects that meet the specified filter criteria, and the result is displayed in a dialog box, as shown in Figure A.25.

Filter options include the following:

  • Acknowledgement

    Filter on points that are acknowledged, or unacknowledged, or leave the filter open to all points.

  • Enrollment

    Filter on only event mechanisms that have a specific recipient, definable either by device id or by device address.

  • Event State

    Specify a particular event state, to restrict the request to include only points that are currently in a specific event state.

  • Event Type

    Restrict the filter to objects that use a particular event type algorithm.

  • Priority

    Choose to only include objects where the priority of the last transition is within certain bounds.

  • Notification Class

    Include only objects and event mechanisms where the notification class used to route the event notifications is equal to a specific number.

Figure A.25. Example Get Enrollment Summary response dialog


Example Get Enrollment Summary response dialog