To filter Cu-Handler events, perform the following steps,

  1. In the navigation pane, select the site and afterwards the gateway that you have created.
  1. Click the DESIGOCC unit.
  1. Click event_filter.csv file under the etc folder.
  • The messages are displayed in the right pane:

To filter out an event, that is prevent the signal from reaching Siveillance Control.

The event filtering layout is explained below:

  • Discipline – BA for Building Automation or Fire for Fire Alarm System.
  • Category – The following explains event filtering based on category.
    • BA;Security;High Limit; - Unprocessed;
    • All events having “BA” for a Discipline, “Security” for a Category & “High LimitUnprocessed” for an Eventcode will be filtered out.
    • In other words, “High Limit” events having the “Unprocessed” state, falling under “Security” in the “BA” discipline will be filtered out. Refer to line number 21 in the screenshot.
    • BA;;High Limit; - Unprocessed;
    • All events having “BA” for a Discipline & regardless of Category & “High LimitUnprocessed” for an Eventcode will be filtered out.
    • In other words, “High Limit” events having the “Unprocessed” state, falling under any Category in the “BA” Discipline will be filtered out. Refer to line number 25 in the screenshot.
  • EventCode - The following section explains event filtering based on event code.
    • BA;Security;;
    • All events having “BA” for a Discipline & “Security” for a Category will be filtered out regardless of their Eventcode. Refer to line number 11 in the screenshot.
    • BA;Security;High Limit;
    • All events having “BA” for a Discipline,“Security” for a Category & “High Limit – Unprocessed, High Limit – Acked, High LimitReadyToBeReset or High Limit – Closed” will be filtered out.
    • In other words, all “High Limit” events, regardless of their state, falling under “Security” in the “BA” Discipline will be filtered out. Refer to line number 20 in the screenshot.
    • BA;;High Limit;
    • All events having “BA” for a Discipline & regardless of Category & “High Limit – Unprocessed, High Limit – Acked, High Limit – ReadyToBeReset or High Limit – Closed” will be filtered out.
    • In other words, all “High Limit” events, regardless of their state, falling under any Category in the “BA” Discipline will be filtered out. Refer to line number 19 in the screenshot.
  • Description – Description of the event.

States of an event in Desigo CC are Unprocessed, Acked, ReadyToBeReset and Closed.

  • Refer to the below table on the different parameters the user is allowed to use for event filtering:

Discipline

Category

Event Code

Description

  • BA
  • Emergency
  • High Limit

Any relevant descriptions

  • Fire
  • Life Safety
  • High Limit - Unprocessed

 

  • Security
  • High Limit - Acked
  • Supervisory
  • High Limit - ReadyToBeReset
  • Trouble
  • High Limit - Closed
  • High Medium
  • Low Limit
  • Medium
  • Low Limit - Unprocessed
  • Low
  • Low Limit - Acked
  • Fault
  • Low Limit - ReadyToBeReset
  • Status
  • Low Limit - Closed

 

  • Fault
  • Fault - Unprocessed
  • Fault - Acked
  • Fault - ReadyToBeReset
  • Fault - Closed
  • Life Safety Alarm
  • Life Safety Alarm - Unprocessed
  • Life Safety Alarm - Acked
  • Life Safety Alarm - ReadyToBeReset
  • Life Safety Alarm - Closed
  • Off Normal
  • Off Normal - Unprocessed
  • Off Normal - Acked
  • Off Normal - ReadyToBeReset
  • Off Normal - Closed
  • Device Return
  • Device Return - Unprocessed
  • Device Return - Acked
  • Device Return - ReadyToBeReset
  • Device Return - Closed
  • Device Failure
  • Device Failure - Unprocessed
  • Device Failure - Acked
  • Device Failure - ReadyToBeReset
  • Device Failure - Closed
  • Connected
  • Disconnected
  1. Click the Save icon.
  1. Click Upload in the OIS Gateway.
  • The filtered events are not displayed in Siveillance Control.