90
• Event type:
allows you to associate a main type of event to the output, e.g. an event belonging to the Area events type (
see table on page 92
).
• Event subtype:
allows you to refine your choice by selecting a subtype of the category set as Event Type; going back to the Area events type
example, the subtype could be Zone Alarm (
see table on page 92
).
• Event:
corresponds to the maximum detail and allows you to specify exactly which event will allow output activation (
see table on page 92
).
Going back to the example, the event could be Burglary, thereby making it possible to activate the output if a burglary is detected by an
activated area.
• Polarity:
allows you to set the status in standby – consequently the status when activated - of the output.
• Direct: in standby the output is not active, and is controlled only during the active status. If the output controls the coil of a relay, in
standby the coil will not be powered up, and will be powered up only during the active status of the output.
• Inverse: opposite of direct. In standby the output is active, and unlike in the previous case, will not be controlled during the active
status. If the output controls the coil of a relay, in standby the coil will be powered up, and power to it will be switched off
during the active status of the output.
• AND/OR and selection box:
only for certain types of event is an AND/OR selection block available which, together with a selection box, allows
you to organise and, if appropriate, determine the status of the output.
• The OR condition is useful when you intend to group events originating from several sources in a single
output: in the case of an AREAS type of event, for example, it is possible to signal the activation status
of the first three areas on one output only, by selecting, for example, the checkboxes for the first three
areas: in this case, the output would activate if at least one of the three areas was activated, and would
be deactivated if all three areas were deactivated.
• The AND condition is useful for providing summary information of the fact that a certain status is
common, for example, to two or more areas. A practical example, similar to the previous one, could
be a confirmation of activation of several areas, by selecting, for example, the checkboxes of the first
three areas: in this case, the output would activate only if all three areas were activated, and would be
deactivated if any one of the three areas were deactivated.
Sometimes, instead of a selection block based on checkboxes like the one just described, a drop-down
menu will be displayed: in this case the AND or the OR condition will be constructed on the basis of the
options chosen from these menus.
The purpose of the outputs is to move on command, in a configurable manner, when one or more events occur. To explain the behaviour of the
outputs and of the control panel logic properly, it is useful to describe what is meant by the term 'event': at logic level, an event can be defined as the
condition that exists between the detection of a status and its cessation (or the cessation of its active status). By way of a simplified example, and
considered in terms of zone, the 'zone open' event starts when the zone opens and ends, normally, when it is closed again.
For each output, it is possible to associate up to 4 different events (Event 1, Event 2, Event 3, Event 4), each of which can be configured by means
of the parameters Event type, Event subtype, Event and Polarity.
Example:
to make an output act as a burglar alarm output, for the purpose of controlling a siren, you need to make the following selections: in the
first drop-down menu, the event type “Areas”, in the second drop-down menu, select the event subtype “OR Alarm” (to have a signal that
includes multiple alarm sources), and in the third drop-down menu, select the event “General Alarm” or alternatively, “Alarm + sabotage”
Among the active outputs, there must be at least one output configured as: event: Areas; event subtype: Fault; event: Motion sensor jamming fault;
polarity: Direct; AND/OR: OR [Reg. 31]
EVENT 1 / 2 / 3 / 4 /... / 16
• Events logic:
for setting whether the control logic will be AND or OR type. In the case of AND logic, all the events have to be present
simultaneously to generate an activation of the output. For OR logic, the presence of just one of the configured events is sufficient
to generate an activation of the output. The output can be regulated by a timer. Standards CEI EN 50131-1 and EN50131-3 do
not allow timers to be associated with outputs used for signalling events such as Intrusion, Tamper or Robbery. If AND mode is
selected, the output will be enabled only during the timeframes permitted by the activation of the timer, provided that they are
prompted by the events envisaged in the configuration (
see table on page 92
). If OR mode is selected, the output will be active
when prompted by the events envisaged in the configuration (
see table on page 92
) and will also be active in the timeframes
determined by the timer, regardless of the presence or otherwise of other prompts.
All active devices must have OR control logic
[Reg. 29]
• AND Timer:
allows you to choose one of the timers available on the control panel and associate it to AND mode.
All active devices must NOT
have associated timers in AND [Reg. 27]
• OR Timer:
allows you to choose one of the timers available on the control panel and associate it to OR mode.
All active devices must NOT
have associated timers in OR [Reg. 28]
EVENTS ASSOCIATION (AND/OR)
Содержание VEDO 2.6 Series
Страница 99: ...99...