ZoneMinder Wiki - User contributions [en]

Zone Parameter Explanations version 1.21

2011-08-17T11:44:13Z

Jeraldinesewell:

[[General_Notes#Zone_Configurations_and_Fine_Tunings|Back]]

===Zone Parameter Explanations===
*Note: This area is complex and needs alot of work. Please help in any way that you can!

==Name==
Each Zone can be named for reference purposes. Choose a name that helps you identify your zones.

==Type==
*Active -

*Inclusive -

*Exclusive -

*Preclusive -

*Inactive -

==Units==

*Pixels - Selecting this option will allow many of the following values to be entered (or viewed) in units of pixels.

*Percentage - Selecting this option will allow may of the following values to be entered (orviewed) as a percentage.

==Minimum X - Minimum Y - Maximum X - Maximum Y==
Use these parameters to define the X,Y coordinates of the corners of the zone that is to be defined.

==Alarm Colour==

These parameters can be used to indvidually colorize the zone overlay pattern. By default, red is the active zone and green is the ??? zone.

==Alarm Check Method==
*Alarmed Pixels -

Choosing this Check Method will grey out many of the available parameters. This can simplify the tuning process, and could possibly be a better starting point for learning to adjust the many advanced parameters that are enabled with the other options.

*Filtered Pixels -

Choosing this Check Method opens up the Filtered parameters for adjustment in addition to the Alarmed Pixels above. This should give more accuracy, once you know how to adjust the various parameters and assist with eliminating false alarms and triggering on desired conditions.

*Blob Pixels -

Choosing this Check Methos opens up all of the available parameters. Enabling Blobs provides one more analysis for determination of what is a valid alarm and what is not.

==Minimum Pixel Threshold==
These setting are used to define limits for the difference in value between a pixel and its predecessor in the reference image.

I believe that this value (and the Maximum value as well) defines the amount of change that a single pixel must undergo, from the prior image (the reference image) and the current image, in order for the pixel to have been considered to have changed.

Small abberations in lighting or auto exposure camera adjustments may cause the explicit value of a pixel to vary by small amounts from image to image. This parameter allows you to set the limits of what will be considered a "changed pixel". For example, if your camera points to a blank white wall, and you raise a black colored item into view, then the change in any one pixel will be great, indeed, extreme. If however, you raise a white piece of paper, then the change that an individual pixes sees will be more subtle. Setting this minimum value too high, may allow a white cat to walk undetected across the view of the white wall.

The default value for this parameter is X%. Generally, this value may range in the 5% to 15% range.

==Maximum Pixel Threshold==
See the Minimum Pixel Threshold (above) for some explanation.

The default value for this parameter is 0% or 0 (zero) pixels, which disables the check. In other words, a pixel that changes from extreme white to extreme black will always be considered to be changed. This value is probably best left at a value of 0 (zero).

==Minimum Alarmed Area==

==Maximum Alarmed Area==

==Filter Width and Filter Height (pixels)==
This parameter is always specified in Pixels, even when Percentages are the selected units.

This parameter defines a group of pixels and should always be an odd number.

3 x 3 is the default value, and 5 x 5 is also suggested as another valid option. It is suggested that these numbers be small in number.

==Minimum Filtered Area==

* This value should always be equal to or less than the Minimum Alarmed Area

==Maximum Filtered Area==

* This value should always be equal to or less than the Maximum Alarmed Area

==Minimum Blob Area==
* The following Blob parameters are only available if you have selected "Blobs" as the "Alarm Check Method" above.

When two or more Filtered areas touch or share a boundary, they probably should be evaluated as one contiguous area and not as separate entities. A Blob is the coalesced or consolodated area of multiple filtered areas.

The Minimum blob area the smallest area that would be considered to be a blob.

==Maximum Blob Area==
This parameter is probably best left at the default value of 0 (zero) or disabled.

==Minimum Blobs==
Normally, you would want any single blob to trigger an event, so the default value of 1 (one) should suffice. In some circumstances, it may benefit to have only one blob NOT trigger an event, in which case, setting this value to 2 or higher may serve some special purpose.

==Maximum Blobs==
I believe that the usefulness of this parameter is negligible. Normally set to 0 (zero), it is probably best left at that value.

[http://custom-essay-writing-service.org/index.php custom writing]

AxisMotionDetection

2011-08-17T11:44:11Z

Jeraldinesewell:

I had this performance problem while monitoring and event recording for 8-10 IP cameras using the ZM.
ZM is too good a software to abandon just for performance issues. So I decided I should pay more attention to the motion detection feature of the cameras I have and relieve the ZM server from the task of detecting motion.
I've finally managed to use the on-camera motion detection feature of Axis Cams and here are my notes:

== Cameras ==

I've set my Axis camera as follows:

[[Image:AxisMDetect1.png]]
[[Image:AxisMDetect2.png]]

The text "1|on 5|5|cause|text|showtext" means that
alarm will be triggered for the monitor which has ID=1,
alarm will set recording on
alarm will be cleared after 5 seconds.
The score of the alarm is 5 ( any score >0 is OK)
"text" and "showtext" are just explanatory notes.

The ZM specs tells us that the format of the message can include a "duration" as long as the message is sent as:
"1|on+5|5|cause|text|showtext" bu the problem is the Axis camera cannot or will not save the "+" sign which appears in the message. A CGI parameter conversion problem I presume...

I've taken care of this "+" problem with a small modification in zmtrigger.pl source (see below).

Next, I specified the host IP address of the zm computer and its default zmtrigger port of 6802.

[[Image:AxisMDetect3.png]]
[[Image:AxisMDetect4.png]]

The second important setup is the "motion detection" setup on the Axis. I created a window which covers the area of interest; kept the object size as small as possible, pulled the history slider all the way back to zero and left the sensitivity slide somewhere past the %50 value.

== ZM settings ==

There is no special setting for the ZM except that I've assigned the "Nodect" function to my camera monitor.

[[Image:AxisMDetect5.png]]

Finally, I modified the zmtrigger.pl file so that the first few lines of the
function handleMessage looks like this:

Code:
sub handleMessage{
my $connection = shift;
my $message = shift;
#
# CUA - Axis camera send the message quoted with"
# CUA - Also Axis camera cannot save the plus sign which
# CUA - possibly exists in the 1|on+20|score|cause|text|showtext formatted msg

$message=~ s/^\"//g;
$message=~ s/\"$//g;
$message=~ s/on /on\+/;

# CUA - end of modifications

my ( $id, $action, $score, $cause, $text, $showtext ) = split( /\|/, $message );

a few other modifications I made in the zmtrigger.pl file are commenting out some unused modules and pushes:

Code:
use ZoneMinder::Trigger::Channel::Inet;
#CUA use ZoneMinder::Trigger::Channel::Unix;
#CUA use ZoneMinder::Trigger::Channel::Serial;
use ZoneMinder::Trigger::Connection;

my @connections;
push( @connections, ZoneMinder::Trigger::Connection->new( name=>"Chan1", channel=>ZoneMinder::Trigger::Channel::Inet->new( port=>6802 ), mode=>"rw" ) );
#CUA push( @connections, ZoneMinder::Trigger::Connection->new( name=>"Chan2", channel=>ZoneMinder::Trigger::Channel::Unix->new( path=>'/tmp/test.sock' ), mode=>"rw" ) );
#push( @connections, ZoneMinder::Trigger::Connection->new( name=>"Chan3", channel=>ZoneMinder::Trigger::Channel::File->new( path=>'/tmp/zmtrigger.out' ), mode=>"w" ) );
#CUA push( @connections, ZoneMinder::Trigger::Connection->new( name=>"Chan4", channel=>ZoneMinder::Trigger::Channel::Serial->new( path=>'/dev/ttyS0' ), mode=>"rw" ) );

my modifs are marked with "# CUA"

These three regular expressions remove the quotes sent by Axis which envelope the message string and insert a plus sign if the "on" command is followed by a space). These 3 statements convert an incoming message of the form

Code:
"1|on 25|5|cause|text|showtext"

to

Code:
1|on+25|5|cause|text|showtext

and of course, you shouln"t forget to restart zmtrigger.pl; or better still modify the zm startup script so that it starts zmtrigger.pl everytime zm is [re]started.

I added the line '/usr/bin/zmtrigger.pl &" in the start section of
/etc/init.d/zoneminder and also added the line "pkill zmtrigger.pl" in the stop section.

Code:

start() {
echo -n "Starting $prog: "
$command start
# CUA
/usr/bin/zmtrigger.pl &

RETVAL=$?
[ $RETVAL = 0 ] && echo success
[ $RETVAL != 0 ] && echo failure
echo
[ $RETVAL = 0 ] && touch /var/lock/zm
return $RETVAL
}
stop() {
echo -n $"Stopping $prog: "
#
# Why is this status check being done?
# as $command stop returns 1 if zoneminder
# is stopped, which will result in
# this returning 1, which will stuff
# dpkg when it tries to stop zoneminder before
# uninstalling . . .
#
# CUA
pkill zmtrigger.pl

I just hope that this helps other people trying to implement the on-camera motion detection with ZM.

Again; many thanks to those people who developed ZM at the first place and to those who helped it to become a perfect opensource project.

[http://www.zoneminder.com/forums/viewtopic.php?t=10872 Original Thread]

'''DO NOT PM THESE USERS ""just post a question in the forum'

Copied By: KingOfKYA

Created By: cayfer

[http://custom-essay-writing-service.org/index.php custom essay writing]