Bedienungsanleitung Ksenia Lares 4.0 (Seite 43 von 58) (Englisch)

693399

Zoom out

Zoom in

Vorherige Seite

1/58

Nächste Seite

lares 4.0 PROGRAMMING MANUAL

rev. 0/2018

• Forced to self-exclude: if the system is not ready, it is inserted with forced exclusion of any open areas.

Note: if there is an open area with the "non-excludable" attribute, at the time of arming mode, this zone will not be

excluded and an alarm will be generated.

Zones with the "exclusion" and "self-exclusion" attributes, if open during arming mode, will be excluded and will not

generate alarms even if they return to rest: they will be reincluded when they are switched off.

Zones with the "with reinclusion" attribute, if opened during arming mode, will be excluded and will not generate

alarms. If they go back they will be reincluded and will, therefore, be ready to generate an alarm.

Type: Output

The subtypes available are:

• Enable user: the user's account (including the code, key or remote control), if inactive, is now activated.

• Disable user: the user's account (including the code, key or remote control) is deactivated.

Type: Other

The subtypes available are:

• Clear telephone queue: cancel calls in progress.

• Alarm reset: all outputs associated with an alarm or tamper event are stopped.

This page links events (alarm, tamper, etc.) with various scenarios.

In order to conﬁgure the “Events”, i.e. the execution of the programmed scenarios (arming modes, activation of outputs,

etc.)

in the appropriate section, click on the (

) icon and then on the ( ) symbol. Then enter the various parameters:

• Type: identiﬁes the group that generates an event (e.g. zone, partition, output, etc.).

• Subtype: this is the action related to the previous parameter (e.g. Type: Zone Subtype: zone alarm). You can make a

multiple choice with up to 15 items.

After entering the previously described two parameters, click on ( ).

At this point it is necessary to set two other parameters:

• Entity: the zone, the partition, the device, the user etc. that generates the event.

• Scenario: enter the previously programmed scenario, which will be activated when the event generated by the selected

entity occurs.

The notiﬁcation types are listed below the <“Subtypes”.

Type: Zone

The subtypes available are:

• Alarm: executes the scenario when the zone generates an alarm.

• Restore: runs the scenario when the zone is restored after an alarm.

• Tamper: runs the scenario when the zone generates a tamper alarm.

• Tamper restore: runs the scenario when a tamper is restored.

• Exclusion: runs the scenario when the zone is excluded.

• Inclusion: runs the scenario when the zone is included.

• Masking: runs the scenario when the detector generates a masking alarm.

• Masking restore: runs the scenario when the detector's masking condition is restored.

• Real Time - Alarm: runs the scenario when the zone is alarmed, even with the partition switched off.

• Real time – Restoration: runs the scenario when the previous condition is restored.

Events

Missbrauch melden von Frage und/oder Antwort

Libble nimmt den Missbrauch seiner Dienste sehr ernst. Wir setzen uns dafür ein, derartige Missbrauchsfälle gemäß den Gesetzen Ihres Heimatlandes zu behandeln. Wenn Sie eine Meldung übermitteln, überprüfen wir Ihre Informationen und ergreifen entsprechende Maßnahmen. Wir melden uns nur dann wieder bei Ihnen, wenn wir weitere Einzelheiten wissen müssen oder weitere Informationen für Sie haben.

Ksenia Lares 4.0 Seite 43

Brauchen Sie Hilfe? Stellen Sie Ihre Frage.

Missbrauch melden von Frage und/oder Antwort

Art des Missbrauchs:

Forenregeln

Neu registrieren

Das Handbuch wird per E-Mail gesendet. Überprüfen Sie ihre E-Mail.

Ihre Frage wurde zu diesem Forum hinzugefügt

Info