RC-E User Manual
Management Client (RC-E Manager)
Generate
events
Apply new device settings, for example a different resolution on a camera
Start and stop plug-ins
Start and stop feeds from devices
How is stopping the feed from a device different from manually disabling the device?
Stopping a device means
that video will no longer be transferred from the device to RC-E, in which case neither live viewing nor recording will
be possible. However, a device on which the feed has been stopped will still be able to communicate with the
recording server, and the feed from device can be started automatically through a rule, as opposed to when the
device is manually disabled in the Management Client.
IMPORTANT:
Some rule content may require that certain features are enabled for the devices in question. For
example, a rule specifying that a camera should record will not work as intended if recording is not enabled for the
camera in question. Before creating a rule it is therefore highly recommended that you verify that the devices involved
will be able to perform as intended. For a number of typically required rules, such prerequisites are described in
Create Typical Rules (on page 116).
How a Rule Is Triggered
Rules can be triggered by two types of conditions:
Events:
When events occur on the surveillance system (for example when motion is detected, when the system
receives input from external sensors, etc.)
Time:
When specific periods of time are entered (for example
Thursday 16th August 2007 from 07.00 to 07.59
, or
every Saturday and Sunday
)
What You Can Cover in a Rule
Your exact number of options depends on the type of rule you want to create, and on the number of devices available
on your system.
Rules, however, provide a high degree of flexibility: You are able to combine event and time conditions, you are able
to specify several actions in a single rule, and very often you are able to create rules covering several or all of the
devices on your system.
You can make your rules as simple or complex as required. For example, you can create very simple time-based
rules:
Example
Very Simple Time-Based Rule: On Mondays between 08.30 and 11.30 (time condition), Camera
1 and Camera 2 should start recording (action) when the time period begins and stop recording (stop action)
when
the time
period ends.
And you can create very simple event-based rules, involving events on one device only:
Example Very Simple Event-Based Rule: When motion is detected (event condition) on Camera 1, Camera
1 should start recording (action) immediately, then stop recording (stop action) after 10 seconds.
However, even though an event-based rule is activated by an event on one device, you can specify that actions
should take place on one or more other devices.
Example Rule Involving Several Devices: When motion is detected (event condition) on Camera 1,
Camera 2 should start recording (action) immediately, and the siren connected to Output 3 should sound
(action) immediately; then, after 60 seconds, Camera 2 should stop recording (stop action), and the siren
connected to Output 3 should stop sounding (stop action).
You can of course also combine events and scheduled times in a rule:
On-Net Surveillance Systems, Inc.
134
