System information

Using scripts in Axis Camera/Video products
Axis Communications AB provides NO support for application development of any kind. The information
here is provided "as is", and there is no guarantee that any of the examples shown will work in your
particular application.
Revision 1.02 October 2002 10
IMPORTANT!
The default behavior when an event is triggered is that the program runs, exits and starts again,
for as long as the triggering event is valid.
once
Specifying once tells utask to skip starting the program as long as the event has not been
invalidated. Utask checks for events ten times a second (if not in standby mode). Thus, if an
event is specified to run at a certain point in time, e.g. time(h(0) m(0) s(0)), then, in
theory, this would run the program up to ten times, since the event is active for a whole second.
immune
Child processes can be protected against premature killing by using the immune tag in the script
entry. An immune script will always run until it terminates.
3.2.1.1 Trigger Patterns for /etc/task.list
Trigger Patterns for alarm input connectors:
IO<n>:/ (Rising edge)
IO<n>:H (Input is high)
IO<n>:\ (Falling edge)
IO<n>:L (Input is low)
Where n is the number of the alarm input used, depending on the product, <n>={0,1,...,3}
Trigger Patterns for boot
boot is defined by an “always true” event that is started once:
once % program : params ;
This will start the program only at startup or if utask is terminated and
restarted.
Trigger Patterns for Motion Detection (2120/2420)
M<n>:/ (Motion starts)
M<n>:H (Motion is detected)
M<n>:\ (Motion stops)
M<n>:L (No motion)
with <n>={0,1,2} for the window identifier.
Trigger Patterns for Video Loss (2400/2401)
V<n>:\ (Video lost)
V<n>:/ (Video back)
with, depending on product, <n>={0,1,...,3}