Axis M3204-V, Руководство пользователя

Страница: 30 / 54

AXIS M3204-V Network Camera
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:
• Applications – Use installed applications to trigger the rule. See Applications on page 28 .
• 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
- Network – Trigger the rule if network connection is lost or restored.
• 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
- 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.
• 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 33 . This can for example be used to upload
an image every 5 minutes.
- Use Schedule – Trigger the rule according to the selected schedule. See Schedules on page 33 .
Available actions include:
• Overlay Text – Display an overlay text. See Using Overlay Text in an Action Rule on page 19 .
• PTZ Control
30