User guide
SerVision MVG 400 System Guide
Configuring the MVG 400 102
triggers a VMD event. You can configure the VMD itself, and the event notifications that are
generated when VMD events are triggered.
About VMD Regions
The FOV is divided into regions, and the relative sensitivity of the motion detection can vary
from region to region. For example, if a computer monitor in the FOV of the camera causes
motion detection events to be triggered unnecessarily, you can choose to mark the region of
the monitor for low sensitivity, or even no motion detection, while the rest of the FOV would
have high sensitivity.
If the camera is connected to the MVG 400, and regions are enabled, the
Camera
configuration screen shows the current FOV of the camera. Regions that are not included in
motion detection are not marked. Regions that are included in motion detection are marked
with a colored
x, as follows:
Sensitivity Level Color
No motion detection None
Low Blue
Middle Green
High Red
NOTE: If VMD is enabled, but regions are not, middle sensitivity is applied to the entire
FOV.
NOTE: If the camera is not connected to the MVG 400, a blank tan image is displayed. It is
recommended that you select the regions for inclusion in VMD when you can see
an actual image.
About VMD Event Settings
A VMD event starts when motion is first detected and ends when there is no motion.
However, in many cases what is seen by the human eye as one event can be interpreted by the
unit as a series of motions with idle periods, and the motion event is broken into a series of
multiple small ones. On the other hand, a motion event can be exhaustingly long, such as a
full day in a busy shop, and we would like to break it down to smaller events.
To solve these two problems, VMD event detection can be configured to control the length of
events using the following parameters:
• Debounce: The interval between the end of motion as detected by the unit and the time
when the event is defined as ending
• Maximum length: The maximum length of a single event
Separate events are defined when motion is not detected for a specified debounce interval. For
example, if the interval is 15 seconds, event A ends when motion is not detected for 15
seconds, and event B begins if motion is detected again after more than 15 seconds have