30.01.2015 Views

Picture Perfect 4.6 User Manual - UTCFS Global Security Products

Picture Perfect 4.6 User Manual - UTCFS Global Security Products

Picture Perfect 4.6 User Manual - UTCFS Global Security Products

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 8<br />

Device management<br />

127<br />

Parent input groups<br />

Keep the following in mind, when working with Parent Input Groups:<br />

• An input group that is connected to a parent input group becomes an input of that parent<br />

input group, and is subject to the parent’s Boolean or non-Boolean settings.<br />

• Each input group can have up to three input groups as its parents, and each input group can<br />

be the parent of any number of input groups. An input group cannot be its own parent.<br />

• A tree-like hierarchy of input groups can be built, with each input group propagating its state<br />

changes on to its parent input group. Do not create a circular hierarchy, where A is a parent of<br />

B, and B is a parent of A.<br />

• An input group’s alarm and output groups are not affected by its association with a parent.<br />

They all work independently.<br />

Note:<br />

Changes to parent input groups through schedules only take effect on the child input groups after the controller<br />

has been reset.<br />

Example of a parent input group<br />

A high-security vault is equipped with three motion detectors and a security guard patrols the vault<br />

periodically. Any one of the motion detectors must be able to activate the alarm, but the alarm must<br />

be disabled during the patrol.<br />

This scenario can be resolved as follows: (See Figure 53, Example of a Parent Input Group on<br />

page 128)<br />

1. Assign the three motion detectors (inputs 1, 2, and 3) to a Motion input group. This input<br />

group would have a boolean type of Any, so any single motion detector could activate this<br />

group.<br />

2. Assign Motion the parent input group of Vault. No alarms or outputs are associated directly<br />

with Motion.<br />

3. Assign Vault the appropriate alarm and output groups desired for motion being detected in<br />

the vault area, and assign it a boolean type of All.<br />

4. Associate a toggle reader (see Toggle on page 179) with an input group called Control. The<br />

toggle reader is the only input in this group. Control is a Trigger on Input (Individual) input<br />

group which is non-boolean, so a badge swipe through this reader toggles the input group’s<br />

state on or off.<br />

5. Assign Control the parent input group of Vault. No alarms or outputs are associated directly<br />

with Control.<br />

Vault’s only inputs are its child input groups, Motion and Control. Both of these must be activated to<br />

trigger the alarm, since Vault’s boolean type is All.<br />

When the vault is unpatrolled, the toggle reader is used to toggle-on Control, meaning that this input<br />

group is activated. If any of the three motion detectors should activate, the Motion input group is<br />

triggered (since its boolean type is Any). The Vault input group then receives the activated state<br />

change of Motion. When that happens, the All condition of Vault has been met, and the associated<br />

alarm and output groups are triggered.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!