RC-E User Manual
Management Client (RC-E Manager)
Devices/recording server/management server link
: When you have selected the required event, clicking
the
devices/recording server/management server
link opens the
Select Group Members
window, which lets
you specify the devices on which device the event should occur in order for the rule to apply.
In this example
... the event should occur on Camera 1 in order for the rule to apply. In the
Select Group
Members
window we therefore drag Camera 1 to the
Selected
list and click
OK
.
5. Click
Next
to move to step 2 of the wizard. On step 2 of the wizard, specify which time conditions should be
met in order for the rule to apply.
In this example
... we simply want the rule to apply whenever motion is detected on Camera 1,
regardless of time. When creating event-based rules it is possible to bypass the time conditions; we
therefore want to skip step 2 entirely.
6. Click
Next
to move to step 3 of the wizard. On step 3 of the wizard, first specify which actions to perform.
In this example
... we want to set a specific live frame rate. We therefore select the action
Set live frame
rate on <devices>
:
Based on the selection of actions, the wizard automatically extends the rule description in the lower part of
the wizard window.
In this example
... Based on our selection
Set live frame rate on <devices>
, the wizard automatically
suggests a rule description in which the frame rate should be set on
the device on which event occurred
.
The wizard furthermore prompts us to specify the required number of frames per second:
To specify the required number of frames per second, we click the
frames per second link
, specify a frame
rate of 25, and click
OK
:
The rule description now indicates that the frame rate will be set to 25 frames per second.
7. Click
Next
to move to step 4 of the wizard. On step 4 of the wizard, select stop criteria. Stop criteria are
important in many types of rules. Without a stop criterion, many actions could go on indefinitely once started.
In this example
... Without a stop criterion, the rule in this example would set the frame rate for the
camera to 25 FPS indefinitely upon motion detection. Based on the elements in our rule description, the
wizard therefore automatically suggests the stop criterion
Perform stop action on <event>
:
Note that the stop criterion
No actions performed on rule end
is not available: a stop criterion must be defined
for this type of rule. In the rule description, the wizard furthermore automatically suggests that the stop action
is performed when motion is no longer detected on Camera 1:
This is just what we want; we do not need to change any of the wizard's suggestions. However, we still need
to define exactly which kind of stop action should take place when motion ends on Camera 1.
8. Click
Next
to move to the next step of the wizard. In this step, the wizard suggests one or more stop actions
based on the previously selected start actions.
In this example
... Based on the start action
set frame rate
in our rule description, the wizard
automatically suggests the stop action
restore default frame rate
. It furthermore suggests that the default
frame rate should be restored immediately after the last detected motion:
This is also just what we want; we do not need to change it, although by clicking the
immediately
link we
could have specified a delay of e.g. 3 seconds.
Your rule is by default active, meaning that once you have created it, it will be applied as soon as the rule's
conditions are met. If you do not want the rule to be active straight away, clear the
Active
check box in the top
part of the
Manage Rule
window:
Tip
: You can always activate/deactivate the rule later.
On-Net Surveillance Systems, Inc.
118
