Installation & User Manual – Oncam C-12 Series
©
Oncam Global Group AG, 2021. All rights reserved.
166
Category
Event Trigger
Name
Description
the camera starts recording. The camera can
produce 3 tracks: video, audio and metadata.
Which tracks are created depends on the
profile configuration.
Delete Recording The
Delete
Recording
event is generated
when a recording configuration is deleted.
Delete Track
This
Delete
Track
event is generated when a
track is deleted. The reason for track deletion
is when a recording is deleted.
Delete Track Data
The
Delete
Track
Data
event is generated
when a track’s data is deleted to create a
space for recording if MicroSD is getting full
and the recording configuration’s
Purge Data
option has been selected.
Job State
The Recording job can be either in Idle or
Active state. In Active state, camera keeps
recording, in Idle state recording is stopped.
This event is generated when
Job
State
is
changed.
Recording
Configuration
Recording
configuration
changes are
updated via this event.
Recording Job
Configuration
This is generated when the
Recording Job
Configuration
is changed from Idle to Active
or vice versa.
Track
Configuration
The
Track
Configuration
event occurs when
the recording track is changed due to changes
in media profile.
Recording
History/Recording
State
This event is generated when the recording is
stored on the MicroSD card. The recording
history stores information about the
State
changes in the SD card.
Audio Parameters This event is generated when recording stored
includes audio track.
State
This event is generated when recording
Track
State
is changed and when recording is Idle or
Active.
Video Parameters This event is generated when recording stored
includes video track.
Rule Engine/Region
Object Detector
Objects Inside
Region Object Detector
event is generated
for checked objects state (i.e. object with ID=id
is inside or not). This feature requires an
analytic rule to configure object rectangles.
This feature requires an Advanced Analytics
license.
Rule Engine/Loitering
Object Detector
Object is Loitering
Object Loitering Detector
event is based on
the polygon region which reports about objects
staying inside it for longer than the designated
threshold value. If configured, periodically this
event can be sent if the object remains within
the region. This feature requires an analytics
rule to configure the polygon region. This
feature requires an Advanced Analytics
license.
Rule Engine/Region
Motion Detector
Motion
Region Motion Detector
event is generated
for the motion alarms for a specific region
defined by a polygon. Polygon region needs to
be defined via the analytics rule.