AXIS M7010 Video Encoder
Events
Events
The Axis product can be configured to perform actions when different events occur, for example, start a recording when motion is
detected. The set of conditions that defines how and when the action is triggered is called an
Action Rule
.
Available Action Rule
triggers
and
conditions
include:
•
Detectors
-
Live Stream Accessed
— trigger the rule when any stream is accessed and during edge storage playback.
This can for example be used to send notifications.
-
Motion Detection
— trigger the rule when motion is detected, see
Motion Detection, on page 25
.
-
Tampering
— trigger the rule when tampering is detected, see
Camera Tampering, on page 25
.
•
Hardware
-
Video Signal
— trigger the rule if video signal is lost.
-
Network
— trigger the rule if network connection is lost or restored. This can for example be used to start
recording to the SD card.
•
Input Signal
-
Manual Trigger
— trigger the rule using the
Manual Trigger
button in the Live View page, see
Controls on
the Live View Page, on page 9
. This can for example be used to validate actions during product installation
and configuration.
-
Virtual Inputs
— can be used by a VMS (Video Management System) to trigger actions. Virtual inputs can, for
example, be connected to buttons in the VMS user interface.
•
PTZ
-
Error
— trigger the rule if the PTZ functionality is not working correctly. This can for example be used to
send maintenance notifications.
-
Moving
— trigger the rule when the camera view moves due to a PTZ operation. This can for example be used
as an additional condition to prevent an action rule triggered by motion detection to record video while the
camera view moves due to a PTZ operation.
-
Preset Reached
— trigger the rule when the camera stops at a preset position. This can be for example be used
with the Send Images action to upload images from the preset position.
-
Ready
— trigger the rule when the PTZ functionality is ready to be used. This can for example be used to steer
the camera to a specific preset position when the product is started.
•
Storage
-
Disruption
— trigger the rule if storage problems are detected, for example if the storage device is unavailable,
removed, full, locked or if other read or write problems occur. This can for example be used to send maintenance
notifications.
•
System
-
System Ready
— trigger the rule when the product has been started and all services are running. This can for
example be used to send a notification when the product restarts.
•
Time
-
Recurrence
— trigger the rule periodically, see
Recurrences, on page 31
. This can for example be used to upload
an image every 5 minutes.
28
