ZoneMinder Wiki - User contributions [en]

Hardware Compatibility List

2016-07-08T11:02:42Z

Stevegilvarry: Reapplying edits

Zoneminder will work with almost any capture card that is supported by the linux kernel. You may find additional details about supported hardware in the part of the forums. Also if you find something in the forums that is missing from the wiki ADD IT.

== Capture Cards ==

[[Anykeeper]]

[[Avermedia]]

[[Camsecure PCI Express video capture]]

[[Digiflower]]

[[Geovision GV250 - bt878a chip]]

[[Grandtec Grand X Guard]]

[[Hauppauge]]

[[Howell-Tempest VC 878B-Q]]

[[Ituner Spectra 8]]

[[Kodicom 4400r]]

[[Kodicom 8800]]

[[Tungson TE-8008]]

Leadtek WinFast VC 100 - the cheapest bt878 model with no tuner on it, just Com/Svideo in.

[[LinkDelight CCTV H.264 4CH DVR Card]]

[[Linux Media Labs LMLBT44]]

[[Osprey 100]]

[[Provideo PV- series (Bluecherry)]]
[[ Bluecherry - BC-H16480A]]
[[TView 95/99]]

[[UDP Technology NCP3200v2]]

[[Videocards with Philips saa7134 chipset]]

[[WinFast TV2000 XP]]

[[Rapid OS]]

[[KesCom PG104]]

[[IEI Technology Corp. IVC-268G-R20]]

== bt8x8 Cards ==
A note on the bt8x8-based TV-tuner cards: these usually have beside the tuner input, also a Composite and an S-Video input. You can hook up 2 analog cameras to these, and access from ZoneMinder both of them as individual cameras, at max 15Fps. You don't need two separate TV cards for two cameras!

[[Pico2000]] - 4 port card, one chip bt878, around 2 fps when using all channels

[[Bt878_4chip_8inputs]] -4 chips bt878, 8 inputs, around 5 fps when using 2 inputs per chip

[[:Image:Karta.jpg| bt878 8 chip 8 input]] - This card is supplied with D-sub to 8 BNC connector and uses the bt878 chip for each input allowing full frame rates and quality. See [[Kodicom 8800]] for more information.

Geovision GV250 bt878a single chip 4 inputs - This capture Card is supplied with 4 video inputs but with NO audio channel

'''Most other BTTV (bt878, bt848) cards, see /usr/src/linux/Documentation/video4linux/bttv/CARDLIST on your system for a list of some of them.'''

== Analog Cameras ==

Any regular composite or S-video camera connected via a supported capture card. Some analog cameras feature camera control - ZM supports several of these camera's Pan/Tilt/Zoom functions via serial port control, as well as camera Presets, Focus, Iris, etc.
*[[PicturetelControlScript | PictureTel PTZ2N]].

== Network Cameras ==
For Network Cams to work they need to be able to stream MJPEG without the requirement of activex controls. If you see the requirement for the camera calls for IE then there is a good chance it may not work. The other option is to grab JPEG images if the camera supports that option which will work but at a lower frame rate.

Any network camera that allows access to single JPEG image grabs or '''some but not all''' multi-part JPEG feeds.

'''Full Compatibility '''

* [[7Links]](TM Trade Mark)

* [[A-mtk]]

* [[Abus]] some

* [[Airlink 101]] some

* [[AirLive AirCam OD325HD]]

* [[Amcrest QCam]]

* [[Amovision AM-Q630M]]

* [[Android]]

* [[Anran VGB101-IP]]

* [[Apexis]] most if not all (only tested some)

* [[ArecontVision]] (AV3130M, probably other too)

* [[Astak Mole]] Some

* [[Axis]] All

* [[Brickcom]] These have been tested

* [[B-QTECH]] H.264 Camera

* [[BSTI]] Some

* [[Cisco]] some

* [[Dahua]] (IPC-HDB3200C, probably others)

* [[DBPower]] (H.264 Model, possibly others)

* [[D-Link]] Most

* [[EasyN]] (Mini Speed Dome 1BF)

* [[Edimax]] only tested some

* [[Foscam]] (FI8908W, FI8904W, possibly others)

* [[Gadspot]] Most

* [[Generic]] Only tested one

* [[Geovision]] (GV-FE420, possibly others)

* [[Grandstream]] Grandstream (GXV-3672-FHD & GXV-3672-FHD-36 & GXV3611_HD tested)

* [[Hikvision]] Some

* [[hootoo]] Some

* [[Iguard]] IP390E

* [[Instar]] (IN-2905, possibly others)

* [[InternetEye]] M6840

* [[Level One]] some

* [[Linksys]] WVC-210 / WVC2300 / PVC2300 / WVC54GC

* [[Loftek]] Sentinel PTZ

* [[Maygion]] (IP-603, IP-604, possibly others)

* [[Messoa]] (NCR870, probably others)

* [[Netcat]] IP Cameras

* [[Pelco]] IP Cameras

* [[Rimax]] Some

* [[Rovio]]

* [[Sony]] Most

* [[TP-LINK]] Some

* [[Trendnet]] Most

* [[Vstar T7833WIP HD Dome Network Camera]]

* [[Wanscam]] FR4020A2 (Foscam clone)

* [[x-vision]] Xvision cameras by y3k (some)

* [[Y-Cam]] (Sharx Ip) Most

* [[Zavio]] Some

* [[Zecumate]] JPT3815W

* [[ZoneWay ZW-NC863M-P Megapixel IP]]

* Remote systems, themselves running zoneminder, can be accessed as cameras using the Remote Path of '''/cgi-bin/nph-zms?mode=single&monitor=1&scale=100&maxfps=5&buffer=1000''' - where the monitor number is the correct camera on the remote system.

'''Single Jpeg Only'''

* [[Airlink 101]] some

* [[JVC]] some

* [[Panasonic]] some

* [[PLANET]] some

*[[Toshiba]] some

* [[Veo Observer IP NetCam]] most

*[[Vivotek]] All

'''Mpeg(ver1.24.0 and up)'''

*[[ABS_MegaCam]]

* [[Axis]] All

* [[ ACTi]] All

*[[Vivotek]] Most

*[[Logitech 700 series]] some

*[[Ubiqiti]] some

'''Compatible with modifications'''

*[[Aviosys]] some

* [[Mobotix]] all

* [[Conceptronic]] some

'''Compatible with problems'''

* [[Compro]] IP70. MPEG4 only, some reliability issues and general poor firmware quality.

* [[Grandtec]] [[Grandtec_WLAN_Camera|WLAN Camera]] WiFi or III - acceptable indoor quality, no infrared-filter (better nightvision) cheap!

* [[Intellinet]] IPCamera with the new firmware.

* Old Intellinet IPCamera (model MWNC-100) with this (http://www.zoneminder.com/forums/viewtopic.php?t=7500) protocol adapter.

* OvisLink AirLive WL-5400CAM

Useful link: Flash's IP Camera Database, with Zoneminder compatibility guide: http://digdilem.org/cameras

== Network Digitizers ==

Like Network Cameras, these devices produce a video stream - but they accept an analog video input from a camera or other video source.

* [[Synectics E100]] encoder
*The [[IP9100 | Aviosys IP9100, Models A, B and Plus]] has four analog video inputs. It produces a ZM compatible video stream from one of the inputs, which is selectable via an HTTP GET command. There might even be a control script for ZM that lets you select the active video input using ''ZM's Camera Control Presets!''

With the yoics Aviosys 9100 firmware at http://www.yoics.com/?p=28, ZoneMinder can directly access all four ports via /usr/yoicsX.jpg as the remote host path, where X is 0 - 3.

* [[Bosch VIP X1 Single-channel]] video encoder [http://products.boschsecuritysystems.eu/en/EMEA/products/bxp/SKU15449253232961378955-CATMda7ec5dc0edf5b1a0b8cb619e2e11308]

* Video cameras & safes for antitheft purpose on the website http://www.infosafe.fr

== USB Cameras ==

*Just Zoom USB cam

*Creative Webcam Pro, Webcam 3, LIVE! Cam OPTIA PRO (V4L2, Chan 0, PAL, YUYV)

*''Most'' UVCvideo cameras, including: Advent AWC213, Creative Labs VF0420, [[Logitech QuickCam Express]], Logitech HD C270, QuickCam Pro 3000, [[QuickCam Pro 4000]], QuickCam Communicate STX/Deluxe, [[Logitech Webcam Pro 9000]], and [[Webcam C250]]

*Logitech Quickcam Orbit/Sphere (experimental basic pan/tilt control has also published for testing and hacking [http://www.zoneminder.com/forums/viewtopic.php?t=9788])

*[[Philips]]

*Any OV511 based USB camera [http://alpha.dyndns.org/ov511/cameras.html]

*Any CPIA based USB camera [http://webcam.sourceforge.net]

*[[LabTec WebCam Pro]]

*Confirmed basic functionality with Microsoft Lifecam VX 5000 using UVC Streaming method

Note that most USB cameras that can use Video4Linux/V4L2, and so can be used by ZoneMinder. Some have older chipsets and can be hard to find new.

Note that PWC drivers are not included in the kernel. Some distribution's add them in and other may not. Here are some relevant links:
* [http://www.smcc.demon.nl/webcam/ Old Maintainer]
* [http://www.saillard.org/linux/pwc/ Current PWC Maintainer]

== X10 Devices ==
The only device that really needs to be compatable with ZM is the Transceiver, all other x10 devices comunicate through that device.
*[[CM11]] Bi-Directional Transceiver

Other X10 notes:

[http://www.zoneminder.com/forums/viewtopic.php?t=6423&highlight=x10 Topic 6423]

[http://www.zoneminder.com/forums/viewtopic.php?t=7082&highlight=x10 Topic 7082]

== All other hardware as supported by Linux ==
To find out if your hardware is supported, check the [http://www.zoneminder.com/forums/viewforum.php?f=10 HCL]

== Plug Computers ==
Guruplug Server Plus -> How to install Zoneminder

== Raspberry Pi - Raspbian ==

ZM 1.25 is already in Raspbian. Newer development packages are available.

You will want libjpeg-turbo from the following repository by adding to your /etc/apt/sources.list

deb http://zarrenspry.info/repos/apt/raspbian testing main
deb-src http://zarrenspry.info/repos/apt/raspbian testing main

Add gpg by

wget -O - http://zarrenspry.info/zarrenspry.gpg.key|apt-key add -

apt-get install libturbojpeg8 libturbojpeg8-dev

If using the Pi camera, you will need to enable it in raspi-config as well as loading the v4l2 kernel module by adding the following to your /etc/modules

bcm2835-v4l2

Although the camera will can capture high res, you don't have enough RAM currently to do so. Especially if you have the early 256MB model. So ust stick to 640x480.

You should be able to get around 20fps, but if you do anything involving the CPU you will get underruns.

== Raspberry Pi 2 - Fedora ==

The latest version of ZoneMinder is available for the Raspberry Pi 2 when running Fedora.
Browse to the zmrepo site for installation instructions: https://zmrepo.zoneminder.com/

== Raspberry Pi 2 - Raspbian ==

Installed fine from packages as found in instructions in other locations.

Five Dahua HFW-4300S cameras resulted in a load of 13+, running at reasonably 720x576 capture. Nothing I could do seemed to save this attempted project. Switched to Ordoid XU4, see below.

== Odroid - XU4 - Ubuntu Mate ==
Installed Zoneminder via Ubuntu package and then upgraded to 1.29.0 without issue.
Five Dahua HFW-4300S cameras running at 720x576 as FFMPEG results in a system load of around 2-3, so not too bad. System running several other always on systems, but Zoneminder consumes most the CPU. No local storage, used QNAP as dedicated image/events storage.
Compiled libjpeg-turbo and that reduced CPU a little, not a lot.

Hardware Compatibility List

2016-07-08T10:57:57Z

Stevegilvarry:

Zoneminder will work with almost any capture card that is supported by the linux kernel. You may find additional details about supported hardware in the part of the forums. Also if you find something in the forums that is missing from the wiki ADD IT.

== Capture Cards ==

[[Anykeeper]]

[[Avermedia]]

[[Camsecure PCI Express video capture]]

[[Digiflower]]

[[Geovision GV250 - bt878a chip]]

[[Grandtec Grand X Guard]]

[[Hauppauge]]

[[Howell-Tempest VC 878B-Q]]

[[Ituner Spectra 8]]

[[Kodicom 4400r]]

[[Kodicom 8800]]

[[Tungson TE-8008]]

Leadtek WinFast VC 100 - the cheapest bt878 model with no tuner on it, just Com/Svideo in.

[[LinkDelight CCTV H.264 4CH DVR Card]]

[[Linux Media Labs LMLBT44]]

[[Osprey 100]]

[[Provideo PV- series (Bluecherry)]]
[[ Bluecherry - BC-H16480A]]
[[TView 95/99]]

[[UDP Technology NCP3200v2]]

[[Videocards with Philips saa7134 chipset]]

[[WinFast TV2000 XP]]

[[Rapid OS]]

[[KesCom PG104]]

[[IEI Technology Corp. IVC-268G-R20]]

== bt8x8 Cards ==
A note on the bt8x8-based TV-tuner cards: these usually have beside the tuner input, also a Composite and an S-Video input. You can hook up 2 analog cameras to these, and access from ZoneMinder both of them as individual cameras, at max 15Fps. You don't need two separate TV cards for two cameras!

[[Pico2000]] - 4 port card, one chip bt878, around 2 fps when using all channels

[[Bt878_4chip_8inputs]] -4 chips bt878, 8 inputs, around 5 fps when using 2 inputs per chip

[[:Image:Karta.jpg| bt878 8 chip 8 input]] - This card is supplied with D-sub to 8 BNC connector and uses the bt878 chip for each input allowing full frame rates and quality. See [[Kodicom 8800]] for more information.

Geovision GV250 bt878a single chip 4 inputs - This capture Card is supplied with 4 video inputs but with NO audio channel

'''Most other BTTV (bt878, bt848) cards, see /usr/src/linux/Documentation/video4linux/bttv/CARDLIST on your system for a list of some of them.'''

== Analog Cameras ==

Any regular composite or S-video camera connected via a supported capture card. Some analog cameras feature camera control - ZM supports several of these camera's Pan/Tilt/Zoom functions via serial port control, as well as camera Presets, Focus, Iris, etc.
*[[PicturetelControlScript | PictureTel PTZ2N]].

== Network Cameras ==
For Network Cams to work they need to be able to stream MJPEG without the requirement of activex controls. If you see the requirement for the camera calls for IE then there is a good chance it may not work. The other option is to grab JPEG images if the camera supports that option which will work but at a lower frame rate.

Any network camera that allows access to single JPEG image grabs or '''some but not all''' multi-part JPEG feeds.

'''Full Compatibility '''

* [[7Links]](TM Trade Mark)

* [[A-mtk]]

* [[Abus]] some

* [[Airlink 101]] some

* [[AirLive AirCam OD325HD]]

* [[Amcrest QCam]]

* [[Amovision AM-Q630M]]

* [[Android]]

* [[Anran VGB101-IP]]

* [[Apexis]] most if not all (only tested some)

* [[ArecontVision]] (AV3130M, probably other too)

* [[Astak Mole]] Some

* [[Axis]] All

* [[Brickcom]] These have been tested

* [[B-QTECH]] H.264 Camera

* [[BSTI]] Some

* [[Cisco]] some

* [[Dahua]] (IPC-HDB3200C, probably others)

* [[D-Link]] Most

* [[EasyN]] (Mini Speed Dome 1BF)

* [[Edimax]] only tested some

* [[Foscam]] (FI8908W, FI8904W, possibly others)

* [[Gadspot]] Most

* [[Generic]] Only tested one

* [[Geovision]] (GV-FE420, possibly others)

* [[Grandstream]] Grandstream (GXV-3672-FHD & GXV-3672-FHD-36 & GXV3611_HD tested)

* [[Hikvision]] Some

* [[hootoo]] Some

* [[Iguard]] IP390E

* [[Instar]] (IN-2905, possibly others)

* [[InternetEye]] M6840

* [[Level One]] some

* [[Linksys]] WVC-210 / WVC2300 / PVC2300 / WVC54GC

* [[Loftek]] Sentinel PTZ

* [[Maygion]] (IP-603, IP-604, possibly others)

* [[Messoa]] (NCR870, probably others)

* [[Netcat]] IP Cameras

* [[Pelco]] IP Cameras

* [[Rimax]] Some

* [[Rovio]]

* [[Sony]] Most

* [[TP-LINK]] Some

* [[Trendnet]] Most

* [[Vstar T7833WIP HD Dome Network Camera]]

* [[Wanscam]] FR4020A2 (Foscam clone)

* [[x-vision]] Xvision cameras by y3k (some)

* [[Y-Cam]] (Sharx Ip) Most

* [[Zavio]] Some

* [[Zecumate]] JPT3815W

* [[ZoneWay ZW-NC863M-P Megapixel IP]]

* Remote systems, themselves running zoneminder, can be accessed as cameras using the Remote Path of '''/cgi-bin/nph-zms?mode=single&monitor=1&scale=100&maxfps=5&buffer=1000''' - where the monitor number is the correct camera on the remote system.

'''Single Jpeg Only'''

* [[Airlink 101]] some

* [[JVC]] some

* [[Panasonic]] some

* [[PLANET]] some

*[[Toshiba]] some

* [[Veo Observer IP NetCam]] most

*[[Vivotek]] All

'''Mpeg(ver1.24.0 and up)'''

*[[ABS_MegaCam]]

* [[Axis]] All

* [[ ACTi]] All

*[[Vivotek]] Most

*[[Logitech 700 series]] some

*[[Ubiqiti]] some

'''Compatible with modifications'''

*[[Aviosys]] some

* [[Mobotix]] all

* [[Conceptronic]] some

'''Compatible with problems'''

* [[Compro]] IP70. MPEG4 only, some reliability issues and general poor firmware quality.

* [[Grandtec]] [[Grandtec_WLAN_Camera|WLAN Camera]] WiFi or III - acceptable indoor quality, no infrared-filter (better nightvision) cheap!

* [[Intellinet]] IPCamera with the new firmware.

* Old Intellinet IPCamera (model MWNC-100) with this (http://www.zoneminder.com/forums/viewtopic.php?t=7500) protocol adapter.

* OvisLink AirLive WL-5400CAM

Useful link: Flash's IP Camera Database, with Zoneminder compatibility guide: http://digdilem.org/cameras

== Network Digitizers ==

Like Network Cameras, these devices produce a video stream - but they accept an analog video input from a camera or other video source.

* [[Synectics E100]] encoder
*The [[IP9100 | Aviosys IP9100, Models A, B and Plus]] has four analog video inputs. It produces a ZM compatible video stream from one of the inputs, which is selectable via an HTTP GET command. There might even be a control script for ZM that lets you select the active video input using ''ZM's Camera Control Presets!''

With the yoics Aviosys 9100 firmware at http://www.yoics.com/?p=28, ZoneMinder can directly access all four ports via /usr/yoicsX.jpg as the remote host path, where X is 0 - 3.

* [[Bosch VIP X1 Single-channel]] video encoder [http://products.boschsecuritysystems.eu/en/EMEA/products/bxp/SKU15449253232961378955-CATMda7ec5dc0edf5b1a0b8cb619e2e11308]

* Video cameras & safes for antitheft purpose on the website http://www.infosafe.fr

== USB Cameras ==

*Just Zoom USB cam

*Creative Webcam Pro, Webcam 3, LIVE! Cam OPTIA PRO (V4L2, Chan 0, PAL, YUYV)

*''Most'' UVCvideo cameras, including: Advent AWC213, Creative Labs VF0420, [[Logitech QuickCam Express]], Logitech HD C270, QuickCam Pro 3000, [[QuickCam Pro 4000]], QuickCam Communicate STX/Deluxe, [[Logitech Webcam Pro 9000]], and [[Webcam C250]]

*Logitech Quickcam Orbit/Sphere (experimental basic pan/tilt control has also published for testing and hacking [http://www.zoneminder.com/forums/viewtopic.php?t=9788])

*[[Philips]]

*Any OV511 based USB camera [http://alpha.dyndns.org/ov511/cameras.html]

*Any CPIA based USB camera [http://webcam.sourceforge.net]

*[[LabTec WebCam Pro]]

*Confirmed basic functionality with Microsoft Lifecam VX 5000 using UVC Streaming method

Note that most USB cameras that can use Video4Linux/V4L2, and so can be used by ZoneMinder. Some have older chipsets and can be hard to find new.

Note that PWC drivers are not included in the kernel. Some distribution's add them in and other may not. Here are some relevant links:
* [http://www.smcc.demon.nl/webcam/ Old Maintainer]
* [http://www.saillard.org/linux/pwc/ Current PWC Maintainer]

== X10 Devices ==
The only device that really needs to be compatable with ZM is the Transceiver, all other x10 devices comunicate through that device.
*[[CM11]] Bi-Directional Transceiver

Other X10 notes:

[http://www.zoneminder.com/forums/viewtopic.php?t=6423&highlight=x10 Topic 6423]

[http://www.zoneminder.com/forums/viewtopic.php?t=7082&highlight=x10 Topic 7082]

== All other hardware as supported by Linux ==
To find out if your hardware is supported, check the [http://www.zoneminder.com/forums/viewforum.php?f=10 HCL]

== Plug Computers ==
Guruplug Server Plus -> How to install Zoneminder

== Raspberry Pi - Raspbian ==

ZM 1.25 is already in Raspbian. Newer development packages are available.

You will want libjpeg-turbo from the following repository by adding to your /etc/apt/sources.list

deb http://zarrenspry.info/repos/apt/raspbian testing main
deb-src http://zarrenspry.info/repos/apt/raspbian testing main

Add gpg by

wget -O - http://zarrenspry.info/zarrenspry.gpg.key|apt-key add -

apt-get install libturbojpeg8 libturbojpeg8-dev

If using the Pi camera, you will need to enable it in raspi-config as well as loading the v4l2 kernel module by adding the following to your /etc/modules

bcm2835-v4l2

Although the camera will can capture high res, you don't have enough RAM currently to do so. Especially if you have the early 256MB model. So ust stick to 640x480.

You should be able to get around 20fps, but if you do anything involving the CPU you will get underruns.

== Raspberry Pi 2 - Fedora ==

The latest version of ZoneMinder is available for the Raspberry Pi 2 when running Fedora.
Browse to the zmrepo site for installation instructions: https://zmrepo.zoneminder.com/

== Raspberry Pi 2 - Raspbian ==

Installed fine from packages as found in instructions in other locations.

Five Dahua HFW-4300S cameras resulted in a load of 13+, running at reasonably 720x576 capture. Nothing I could do seemed to save this attempted project. Switched to Ordoid XU4, see below.

== Odroid - XU4 - Ubuntu Mate ==
Installed Zoneminder via Ubuntu package and then upgraded to 1.29.0 without issue.
Five Dahua HFW-4300S cameras running at 720x576 as FFMPEG results in a system load of around 2-3, so not too bad. System running several other always on systems, but Zoneminder consumes most the CPU. No local storage, used QNAP as dedicated image/events storage.
Compiled libjpeg-turbo and that reduced CPU a little, not a lot.

Hardware Compatibility List

2016-07-08T10:40:43Z

Stevegilvarry: Undo revision 7637 by Intansrirahayu (talk)

Zoneminder will work with almost any capture card that is supported by the linux kernel. You may find additional details about supported hardware in the part of the forums. Also if you find something in the forums that is missing from the wiki ADD IT.

== Capture Cards ==

[[Anykeeper]]

[[Avermedia]]

[[Camsecure PCI Express video capture]]

[[Digiflower]]

[[Geovision GV250 - bt878a chip]]

[[Grandtec Grand X Guard]]

[[Hauppauge]]

[[Ituner Spectra 8]]

[[Kodicom 4400r]]

[[Kodicom 8800]]

[[Tungson TE-8008]]

Leadtek WinFast VC 100 - the cheapest bt878 model with no tuner on it, just Com/Svideo in.

[[LinkDelight CCTV H.264 4CH DVR Card]]

[[Linux Media Labs LMLBT44]]

[[Osprey 100]]

[[Provideo PV- series (Bluecherry)]]
[[ Bluecherry - BC-H16480A]]
[[TView 95/99]]

[[Videocards with Philips saa7134 chipset]]

[[WinFast TV2000 XP]]

[[Rapid OS]]

== bt8x8 Cards ==
A note on the bt8x8-based TV-tuner cards: these usually have beside the tuner input, also a Composite and an S-Video input. You can hook up 2 analog cameras to these, and access from ZoneMinder both of them as individual cameras, at max 15Fps. You don't need two separate TV cards for two cameras!

[[Pico2000]] - 4 port card, one chip bt878, around 2 fps when using all channels

[[Bt878_4chip_8inputs]] -4 chips bt878, 8 inputs, around 5 fps when using 2 inputs per chip

[[:Image:Karta.jpg| bt878 8 chip 8 input]] - This card is supplied with D-sub to 8 BNC connector and uses the bt878 chip for each input allowing full frame rates and quality. See [[Kodicom 8800]] for more information.

Geovision GV250 bt878a single chip 4 inputs - This capture Card is supplied with 4 video inputs but with NO audio channel

'''Most other BTTV (bt878, bt848) cards, see /usr/src/linux/Documentation/video4linux/bttv/CARDLIST on your system for a list of some of them.'''

== Analog Cameras ==

Any regular composite or S-video camera connected via a supported capture card. Some analog cameras feature camera control - ZM supports several of these camera's Pan/Tilt/Zoom functions via serial port control, as well as camera Presets, Focus, Iris, etc.
*[[PicturetelControlScript | PictureTel PTZ2N]].

== Network Cameras ==
For Network Cams to work they need to be able to stream MJPEG without the requirement of activex controls. If you see the requirement for the camera calls for IE then there is a good chance it may not work. The other option is to grab JPEG images if the camera supports that option which will work but at a lower frame rate.

Any network camera that allows access to single JPEG image grabs or '''some but not all''' multi-part JPEG feeds.

'''Full Compatibility '''

* [[7Links]](TM Trade Mark)

* [[A-mtk]]

* [[Abus]] some

* [[Airlink 101]] some

* [[Apexis]] (APM-J011-WS, APM-J012-WS, possibly others)

* [[ArecontVision]] (AV3130M, probably other too)

* [[Astak Mole]] Some

* [[Axis]] All

* [[Brickcom]] These have been tested

* [[BSTI]] Some

* [[Cisco]] some

* [[D-Link]] Most

* [[DBPower]] (H.264 Model, possibly others)

* [[Foscam]] (FI8908W, FI8904W, possibly others)

* [[Gadspot]] Most

* [[Generic]] Only tested one

* [[Geovision]] (GV-FE420, possibly others)

* [[Hikvision]] Some

* [[hootoo]] Some

* [[Iguard]] IP390E

* [[Instar]] (IN-2905, possibly others)

* [[Level One]] some

* [[Linksys]] WVC-210 / WVC2300 / PVC2300 / WVC54GC

* [[Loftek]] Sentinel PTZ

* [[Maygion]] (IP-603, IP-604, possibly others)

* [[Rimax]] Some

* [[Rovio]]

* [[Sony]] Most

* [[TP-LINK]] Some

* [[Trendnet]] Most

* [[Wanscam]] FR4020A2 (Foscam clone)

* [[x-vision]] Xvision cameras by y3k

* [[Y-Cam]] (Sharx Ip) Most

* [[Zavio]] Some

* [[Zecumate]] JPT3815W

* Remote systems, themselves running zoneminder, can be accessed as cameras using the Remote Path of '''/cgi-bin/nph-zms?mode=single&monitor=1&scale=100&maxfps=5&buffer=1000''' - where the monitor number is the correct camera on the remote system.

'''Single Jpeg Only'''

* [[Airlink 101]] some

* [[JVC]] some

* [[Panasonic]] some

* PLANET some

*[[Toshiba]] some

* [[Veo Observer IP NetCam]] most

*[[Vivotek]] All

'''Mpeg(ver1.24.0 and up)'''

*[[ABS_MegaCam]]

* [[Axis]] All

* [[ ACTi]] All

*[[Vivotek]] Most

'''Compatible with modifications'''

*[[Aviosys]] some

* [[Mobotix]] all

*[[Edimax]] some

* [[Conceptronic]] some

'''Compatible with problems'''

* [[Compro]] IP70. MPEG4 only, some reliability issues and general poor firmware quality.

* [[Grandtec]] [[Grandtec_WLAN_Camera|WLAN Camera]] WiFi or III - acceptable indoor quality, no infrared-filter (better nightvision) cheap!

* [[Intellinet]] IPCamera with the new firmware.

* Old Intellinet IPCamera (model MWNC-100) with this (http://www.zoneminder.com/forums/viewtopic.php?t=7500) protocol adapter.

* OvisLink AirLive WL-5400CAM

Useful link: Flash's IP Camera Database, with Zoneminder compatibility guide: http://digdilem.org/cameras

== Network Digitizers ==

Like Network Cameras, these devices produce a video stream - but they accept an analog video input from a camera or other video source.

* [[Synectics E100]] encoder
*The [[IP9100 | Aviosys IP9100, Models A, B and Plus]] has four analog video inputs. It produces a ZM compatible video stream from one of the inputs, which is selectable via an HTTP GET command. There might even be a control script for ZM that lets you select the active video input using ''ZM's Camera Control Presets!''

With the yoics Aviosys 9100 firmware at http://www.yoics.com/?p=28, ZoneMinder can directly access all four ports via /usr/yoicsX.jpg as the remote host path, where X is 0 - 3.

== USB Cameras ==

*Just Zoom USB cam

*Creative Webcam Pro, Webcam 3, LIVE! Cam OPTIA PRO (V4L2, Chan 0, PAL, YUYV)

*''Most'' UVCvideo cameras, including: [[Logitech QuickCam Express]], QuickCam Pro 3000, [[QuickCam Pro 4000]], QuickCam Communicate STX/Deluxe, [[Logitech Webcam Pro 9000]], and [[Webcam C250]]

*Logitech Quickcam Orbit/Sphere (experimental basic pan/tilt control has also published for testing and hacking [http://www.zoneminder.com/forums/viewtopic.php?t=9788])

*[[Philips]]

*Any OV511 based USB camera [http://alpha.dyndns.org/ov511/cameras.html]

*Any CPIA based USB camera [http://webcam.sourceforge.net]

*[[LabTec WebCam Pro]]

*Confirmed basic functionality with Microsoft Lifecam VX 5000 using UVC Streaming method

Note that most USB cameras that can use Video4Linux/V4L2, and so can be used by ZoneMinder. Some have older chipsets and can be hard to find new.

Note that PWC drivers are not included in the kernel. Some distribution's add them in and other may not. Here are some relevant links:
* [http://www.alliedarmament.com/ Toko Bunga Jakarta]
* [https://www.tokobungakarangan.com/ Toko Bunga Online]
* [http://www.smcc.demon.nl/webcam/ Old Maintainer]
* [http://www.saillard.org/linux/pwc/ Current PWC Maintainer]

== X10 Devices ==
The only device that really needs to be compatable with ZM is the Transceiver, all other x10 devices comunicate through that device.
*[[CM11]] Bi-Directional Transceiver

Other X10 notes:

[http://www.zoneminder.com/forums/viewtopic.php?t=6423&highlight=x10 Topic 6423]

[http://www.zoneminder.com/forums/viewtopic.php?t=7082&highlight=x10 Topic 7082]

== All other hardware as supported by Linux ==
To find out if your hardware is supported, check the HCL [http://www.mpsmsc.com/recruitment-indonesia.html MSC Recruitment Indonesia]

== Links ==
* [http://www.mpsmsc.com/crewing-indonesia.html MSC Crewing Indonesia]
* [http://www.doxapest.co.id/index.php/pest-control-dan-anti-rayap Pest Control]
* [http://www.tokobungasabana.com Toko Bunga Online]

== Plug Computers ==
Guruplug Server Plus -> How to install Zoneminder

General Notes

2016-05-22T09:12:35Z

Stevegilvarry: Spammer Revert

==Zoneminder Build Notes==
==== Required for Building ====
* MySQL [http://www.lamphowto.com www.lamphowto.com] Notes on compiling MySQL from source
* OpenSSL
* PHP
* Apache
* Perl/Libperl
./configure will complain if anything is missing.

==== Installing from Source ====
* http://www.zoneminder.com/fileadmin/downloads/README.html 
* http://www.zoneminder.com/forums/viewtopic.php?t=5715 
* http://www.zoneminder.com/forums/viewtopic.php?t=5929 
:./configure --with-mysql=/usr/local/mysql
:--with-ffmpeg=/home/src/ffmpeg-0.4.9-pre1
:--with-lame=/home/src/lame-3.96.1/libmp3lame
:--with-webdir=/home/sites/Security.658Ridgecrest.com/web
:--with-cgidir=/home/sites/Security.658Ridgecrest.com/web
:--with-webuser=httpd
:--with-webgroup=httpd
:--with-libarch=lib
:--enable-debug=yes
OR
:./configure --with-webdir=/var/www/htdocs/ZM
:--with-cgidir=/var/www/cgi-bin --sysconfdir=/etc
:--with-webuser=httpd
:--with-webgroup=httpd
OR
* http://www.zoneminder.com/forums/viewtopic.php?t=6053
:./configure --with-webdir=/var/www/html/zm
:--with-cgidir=/var/www/cgi-bin ZM_DB_PASS=<password>

==== Create and Populate the Database ====
* http://www.zoneminder.com/forums/viewtopic.php?t=5754 
* http://www.zoneminder.com/forums/viewtopic.php?t=6023 
<code>
:mysql mysql < db/zm_create.sql
:mysql mysql
:> grant select,insert,update,delete on <database name>.* to '<database user>'@localhost identified by '<database password>';
:> quit
: mysqladmin reload</code>

==== Misc Notes (Anyone care to categorize?) ====
Check zone.conf or zm.conf. Check that there are no bogus vesions of this file lying around. 
"nobody" doesn't have shell access, choose a different Apache alias like "httpd". 
zmdc.log or /var/log/messages log any errors. 
zm.sock file must be able to be created.

==Apache ==

==== Permissions Problems ====
* http://www.zoneminder.com/forums/viewtopic.php?t=5642
<code>sudo -u apache /etc/rc.d/rc.zoneminder start</code>
** now.. zmc and zma is running on user apache

==== su Issue ====
http://www.zoneminder.com/forums/viewtopic.php?t=5652

==== Allowing CGI Execution (REQUIRED for ZM) ====
http://www.zoneminder.com/forums/viewtopic.php?t=5853
*/usr/local/etc/zm.conf must exist and what process owns it.
webuser and webgroup must be correct for apache to have ownership over zm.conf

==BIOS Issues==
Turning off ACPI power management in the BIOS may help alleviate some issues with ZoneMinder and capture hardware.

==Brightness control==
* http://www.zoneminder.com/forums/viewtopic.php?t=3953
* http://www.zoneminder.com/forums/viewtopic.php?t=5680
* http://www.zoneminder.com/forums/viewtopic.php?t=3657

== Contribs Forum==
The [http://www.zoneminder.com/forums/viewforum.php?f=9 contribs forum] contains contributions from ZoneMinder users like yourself!

==Cambozola==
Cambozola is a Java plugin that decodes multipart JPEG streams. Mozilla-based browser have native support, so this plugin is for browsers like Internet Explorer that lack that support.

To install Cambozola for use in zm, Download the cambozola.jar file from the Downloads page or directly from the charliemouse website. If you download from charliemouse you will need to extract the one file (cambozola.jar) from the archive. Place cambozola.jar in the ZM root web directory (so if your web pages for ZM is installed at /var/www/html/zm the file should go there as well). Now all thats left to be done is to enable it in ZM goto options and under the web tab check that cambozola is enabled. In 1.25 you will find OPT_CAMBOZOLA under the '''Images''' tab. That's it, you're done.

* http://www.zoneminder.com/forums/viewtopic.php?t=5745
* http://www.zoneminder.com/forums/viewtopic.php?t=6320

NOTE: If you find that the Cambozola applet loads in IE but the applet just displays the version # of Cambozola and the author's name (as opposed to seeing the streaming images), you may need to chmod your cambozola.jar:

$ sudo chmod 775 cambozola.jar

Once I did this, images started to stream for me.

NOTE: If you find that Cambozola doesn't load in IE at all, but instead you get a black 'X' where the video should be, Zoneminder is incorrectly detecting that your IE can handle MJPEG streams. To fix, go to '''Options''' then '''High B/W''', '''Medium B/W''', or '''Low B/W''' (depending on which you use) and set the option '''Override the automatic detection of browser streaming capability''' to "no". This will force all browsers to use Cambozola. Also, with modern versions of Java, you'll probably also have to go into your Control Panel to the Java options and add the URL of your Zoneminder instance to your Exception Site List, due to the fact that Cambozola.jar is self-signed. Otherwise you'll get a Java message '''Application Blocked by Security Settings'''

==Capture Card Issues==
==== Image is Flipped ====
* Applies to 4 inputs on one chip:
**http://www.zoneminder.com/forums/viewtopic.php?t=6042

==== Scrambled Images ====
* Applies to 4 inputs on one chip, using lspci and dmesg to determine hardware.
**http://www.zoneminder.com/forums/viewtopic.php?t=6024
**http://www.zoneminder.com/wiki/index.php/Pico2000

==== Black Screen bttv Video Devices ====
* Black Screen in ZM when using 2.6.21.5 kernel '''but''' works with TVTime
** http://www.zoneminder.com/forums/viewtopic.php?t=10108 describes why a V4L2 app has to init the devices 1st before a V4L1 app.
** A script to workaround this is available at http://www.zoneminder.com/forums/viewtopic.php?t=9414

==CAUSE NOTES field section==
*http://www.zoneminder.com/forums/viewtopic.php?t=6065

==Database MySQL==
==== Create a New Database ====
* http://www.zoneminder.com/forums/viewtopic.php?t=5754

==== Repair a Database ====
* http://www.zoneminder.com/forums/viewtopic.php?t=5657
* http://www.zoneminder.com/forums/viewtopic.php?t=5845

==== Backup a Database ====
In Ubuntu and other modern distributions you can install MySQL administrator GUI.

the default login is :- 
Server Hostname ---- localhost Username ---- Root Password ----- (Blank, no password)

In here, there is backup and restore functions. The backup can also be scheduled.

==== Delete Databases/Tables ====

==== Database Tricks/Tips ====

=====MySQL Tune Up=====
For small one or two camera systems with few events the default MySQL settings should work quite well. Hi resolution cameras with lots of activity or monitors on Record or Mocord will run up thousands of events in short order. This will put a strain on MySQL with default settings.
Many Linux distributions provide MySQL 5.5 or older. For these I recommend setting up MySQL to use INNODB tables. Researching the web I found this to be faster for larger tables (as events grow) and much more reliable. to do this:

Edit the MySQL config file (for Ubuntu 14.04 it is /etc/mysql/my.cnf) and add:

[mysqld]

innodb_file_per_table

If you have a running system you can convert to INNODB
*[[Enable and convert MySQL to innodb_file_per_table for Zoneminder]]

One tool I use is mysqltuner. This is run from the command line and gives clear instructions as to what values to change. If these instructions are not clear to you I recommend my friend Google.

On a new system under load we recommend running mysqltuner daily until you get to stability with the amount of events you store.

When you run mysqltuner you will be prompted to enter the admin user (normally root) and then the password.

Many of the settings in MySQL are "default" and are not listed in the configuration file. So, if mysqltuner recommends you change the value for innodb_buffer_pool_size and you open the my.cnf (or other config file) and you do not find the value you will have to add it! Something like this:

[mysqld]

innodb_file_per_table

innodb_buffer_pool_size = 512m (Note that memory values can be also written in bytes)

Stop Zoneminder, restart MySQL, then start Zoneminder to apply changes

Forum topics about MySQL
* http://www.zoneminder.com/forums/viewtopic.php?t=6000
* http://www.zoneminder.com/forums/viewtopic.php?t=6143
* http://www.zoneminder.com/forums/viewtopic.php?t=5657
* http://www.zoneminder.com/forums/viewtopic.php?t=6095

====Update Database After Installing from RPM's====
* http://www.zoneminder.com/forums/viewtopic.php?t=5887

== ffmpeg ==
*Install ffmpeg for Fedora with
yum -i ffmpeg 
yum -i ffmpeg-devel

*Install ffmpeg and ffmpeg-devel on Fedore4
**http://www.zoneminder.com/forums/viewtopic.php?t=5601
<code>
rpm -ivh http://rpm.livna.org/livna-release4.rpm
yum install ffmpeg ffmpeg-devel
</code>
Place the devel stuff in /usr/include/ffmpeg
Now configure, make, make install

*http://www.zoneminder.com/forums/viewtopic.php?t=5576&sid=4e7192b74fe4306e341e9c4036727f7b
*After getting ffmpeg from CVS, do:
<code>./configure , make, make install, make installibs</code>

===Changes in ffmpeg again===
It would seem that ffmpeg has possibly changed things again, no real supprise there but it complicates building ZM.

So if you find when you make:

zm_mpeg.h:29:29: error: ffmpeg/avformat.h: No such file or directory

zm_mpeg.h:31:28: error: ffmpeg/swscale.h: No such file or directory

and whereis turns up:

/usr/include/libavformat/avformat.h

/usr/include/libswscale/swscale.h

The file you would need to change is zm_mpeg.h
and change the following two lines in that file:

#include <ffmpeg/avformat.h>
#include <ffmpeg/swscale.h>

Would have to be canged to:

#include <libavformat/avformat.h>
#include <libswscale/swscale.h>

==Increase Image size==
If you increase the image size on a camera, it's always best to close down any streams and restart ZM to make sure that all memory is released.
http://www.zoneminder.com/forums/viewtopic.php?t=7049

==Image display problems==
http://www.zoneminder.com/forums/viewtopic.php?t=6027

Also remember you may need to increase your 'shared memory'. See the FAQ for details

==Firefox, Colorzilla Extensions==
http://www.zoneminder.com/forums/viewtopic.php?t=5647

==Kodicom Capture Cards==
* http://www.zoneminder.com/forums/viewtopic.php?t=5640
* http://www.zoneminder.com/forums/viewtopic.php?t=4130
* http://www.zoneminder.com/forums/viewtopic.php?t=6158
*KMC-8800 8-chip bt878 capture card
** http://www.zoneminder.com/forums/viewtopic.php?t=5609
** http://www.linuxtv.org/wiki/index.php/Kodicom_4400R
** http://www.linuxtv.org/wiki/index.php/Kodicom_8800R
** http://www.zoneminder.com/forums/viewtopic.php?t=6012

*modprobe.conf file
**http://www.zoneminder.com/forums/viewtopic.php?t=5508&postdays=0&postorder=asc&start=15
** http://www.zoneminder.com/forums/viewtopic.php?t=6024
Edit your /etc/modprobe.conf file and add this line: 
options bttv card=77 
*http://www.linux.com/howtos/Webcam-HOWTO/dev-intro.shtml
*http://www.zoneminder.com/forums/viewtopic.php?t=6892
All screens must be the same resolution.

*bttv settings
**http://www.zoneminder.com/forums/viewtopic.php?t=5603&sid=4e7192b74fe4306e341e9c4036727f7b

note that under ubuntu that the file to edit is /etc/modprobe.d/aliases.

==Logitech USB QuickCam==
*I'm using FC4 and had a similiar problem with a quickcam 4000.
I guess you are using the default module supplied with CentOS. I think, not sure about this though, that it is missing some capabilities. So I installed the pwc module (http://www.saillard.org/linux/pwc/INSTALL.en) and these crashes stopped.
http://www.zoneminder.com/forums/viewtopic.php?t=5906

==Message Logs==
http://www.zoneminder.com/forums/viewtopic.php?t=5771

==Memory Problems/Tweaks==
*http://www.zoneminder.com/forums/viewtopic.php?t=6242
*Shared memory setting must be high.
**http://www.zoneminder.com/forums/viewtopic.php?t=6024

==SELinux Issues==
*http://www.zoneminder.com/forums/viewtopic.php?t=6337
*http://www.zoneminder.com/forums/viewtopic.php?t=4836
*http://www.zoneminder.com/forums/viewtopic.php?t=6147
<code>
cat sysctl.conf
# Disable response to broadcasts.
# You don't want yourself becoming a Smurf amplifier.
net.ipv4.icmp_echo_ignore_broadcasts = 1
# enable route verification on all interfaces
net.ipv4.conf.all.rp_filter = 1
# enable ipV6 forwarding
#net.ipv6.conf.all.forwarding = 1
kernel.shmall = 134217728
kernel.shmmax = 134217728
</code>
* http://www.zoneminder.com/forums/viewtopic.php?t=6000

==Mocord, Record, Modect==
http://www.zoneminder.com/forums/viewtopic.php?t=6120

==External Triggering==
====zmtrigger.pl====
Some discussion on using external events (X10 for example) to trigger your ZM camera:
http://www.zoneminder.com/forums/viewtopic.php?t=6423&highlight=

(Could use your help here)

==Modprobe==
modprobe.conf
mod = 133 or something like that for Kodicom
http://www.zoneminder.com/forums/viewtopic.php?t=5603

==Official ZoneMinder Manual==
http://www.zoneminder.com/fileadmin/downloads/README.html

==MMS Gateway and API Aoftware==
GPRS or HTTP a Jpeg image to the MMS gateway server which in turn sends the image to a mobile phone
*http://www.redcoal.com/
*http://www.zoneminder.com/forums/viewtopic.php?t=6101
*http://wurfl.sourceforge.net/

==Multiple zones==
http://www.zoneminder.com/forums/viewtopic.php?t=6079

==Perl Package zmpgk.pl==
*http://www.zoneminder.com/forums/viewtopic.php?t=5801

==Roundrobin==
*http://www.zoneminder.com/forums/viewtopic.php?t=5658

==Remote Camera Source/ Using Another ZM Box as a Source====
*http://www.zoneminder.com/forums/viewtopic.php?t=5549
*http://www.zoneminder.com/forums/viewtopic.php?t=5595
*http://www.zoneminder.com/forums/viewtopic.php?t=5549
*http://www.zoneminder.com/forums/viewtopic.php?t=12037

==Simultaneous connections (number off ) to Web browser==
*http://www.zoneminder.com/forums/viewtopic.php?t=6765

==Streaming ==
*rtp and raw streaming
http://www.zoneminder.com/forums/viewtopic.php?t=5572

==Settings==
*"disable farm out writing of images" if frame capture errors appear in log. 
** http://www.zoneminder.com/forums/viewtopic.php?t=5992

*color pallet, video hieght, or video width. Try starting with 320x240 (assuming ntsc) and try different pallets.
**http://www.zoneminder.com/forums/viewtopic.php?t=6027&sid=9a52386394831b24741c67ba70cc1507

==Timelapsed video==
http://www.zoneminder.com/forums/viewtopic.php?t=6049

==Vehicle Detection Links==
*http://www.zoneminder.com/forums/viewtopic.php?t=5858
*http://www.zoneminder.com/forums/viewtopic.php?t=5184&highlight=truck+intersection

*All things are possible and the example someone posted a while back of detecting trucks and buses, but not cars, passing over a distant intersection is probably appropriate for you. What I would suggest you need are quite high pixel differences (indicating difference from the background) and pretty small counts of changed pixels or blob sizes. You might find it useful to turn on diagnostic images initially (and only for a while as they slow everything down a lot) which will output what ZM thinks the differences etc are are in the images.

==Water marked==
http://www.zoneminder.com/forums/viewtopic.php?t=4591&highlight=watermark
http://www.zoneminder.com/forums/viewtopic.php?t=4188&highlight=watermark

==xawtv ==
*http://www.zoneminder.com/forums/viewtopic.php?t=5696
what from xawtv -hwscan?
xawtv -device /dev/video?

==zmc daemon captures the images==
*http://www.zoneminder.com/forums/viewtopic.php?t=6146

==Zone Configurations and Fine Tunings==

The way I tuned my zones was to walk out in front of the camera and stand at the furthest distance from the camera where it would be useful to detect motion.

Then I replayed the footage and took a still of my standing away from the camera, loaded it into a photo editor and cropped the image to the size of my body.

Then looking at the image attibutes gave me the dimensions of the remaining space, I took the height and width and multiplied them to get a minumum number of changed pixels I wanted to cause an alarm.

I went into my zone and changed the units from percent to pixels. Then input the number I got from my previous calculation into the first two min fields, and subtracted 15% and put that number in the last minumum field.

* This section needs alot of work. Please contribute as much as you can!

Once you have Zoneminder up and running and all your cameras recording events, it then becomes important to fine tune your zones so that you record all of the events that are important to you, and just as important, NOT record events that are not important

There are many parameters to be adjusted. So many, in fact, that it is easy to change just a few parameters, and create a config that does not do what you want at all. It is all so confusing. Here, we will attempt to document some basic configs, and explain in some detail the effects that each parameter will have and how each parameter relates to the other parameters.

The Documentation page offers some help in understanding how these parameters are related and important. You can view the online documentation here:

[http://www.zoneminder.com/fileadmin/downloads/README.html#_Toc151468571 Zone Config Documentation]

[[Reference Image Blend Percentage aka Vapor Trails]]

[[Zone Parameter Explanations version 1.21]]

[[Zone Parameter Explanations version 1.22]]

[[Zone Analysis Pseudo Algorithm]]

[[Zone Configuration Basics]]

[[Zone Configuration Advanced]]

[[Special Situation Configs]]

How to export download and view events

2016-05-22T09:09:56Z

Stevegilvarry: Spammer Revert

--[[User:Stagecoach|stagecoach]] 15:34, 23 October 2010 (BST)

Go back to the [[How_To|How To]] pages...

=Prerequisites=
To export, download and view the events from ZoneMinder there are 3 prerequisites.
# Access to your ZoneMinder website.
# An application to unpack the exported files.
#* For Linux most distributions include an application like unzip or untar.
#* For Windows an excellent open source alternative to the default archive manager is [http://www.7-zip.org/download.html 7-Zip]
=Export Methods=
There are three ways to export events from ZoneMinder. Depending on what events you wish to export one of these methods will usually be superior.
==Front end interface method==
This is the easiest way to view events if you want to check all events in the hour/day/week/month or all events for a certain particular camera.
===Steps===
[[image:zm_home.png|right|thumb|caption|ZoneMinder homepage]]
[[image:eventsview.png|right|thumb|caption|Events view allows you to select which events to export]]
# Login to ZoneMinder as a user who has rights to view the desired monitor.
# From the home page you should see a table with columns labeling camera name events per hour/day/week/month/all. The very bottom column of this table totals the events across all cameras for the given hour/day etc. Click on the total events under the hour row to continue.
# You should now be on the event view page. This pages purpose is to list the events selected by your query method. From this view we are provided with many statistics about individual events. We may choose to review the events from this page by clicking on the name of the event, however for the purpose of this ''how to'' we will simply choose to export all events by selecting the check-box in the top right cell. After selecting all the events from this view we open up the export dialog by clicking the EXPORT button located in the bottom right corner.
# This export options dialog that pops up allows us to select the file type that is exported. Before clicking the export button you must first make sure too check the following settings:
##Export Event Details
##Export Frame Details
##Export File Format: Zip
[[image:zmexport.png|right|thumb|caption|Typical Export form settings]]
# Once you click the export button ZoneMinder will go through the process of packaging and formatting the events for you, this process can be quite intensive for the server if a large number of events are selected. When the process is completed a download link for a file called zmExport.zip should pop up, select save file and click ok. It is important to make a note of where you save your file as you will need to access it later.

==Event Filter==
[[image:eventfilter.png|right|thumb|caption|Events Filter form]]
The filter method of exporting events gives the user the most detail and control in the event query. As this method allows you to make very refined queries it does add some complexity to the process. To illustrate the power of this export method I will show you how Event Filter can create a custom query that is saved for future use, this custom query will select all events that have had more than 50 alarm frames on Mondays.

===Steps===
# On the bottom left side of your ZoneMinder homepage there should be a button labeled "Filter"
# The form section under the use filter select box is the area where we will define steps the event filter evaluates. To add the second step for the event filter simply click the + button on the bottom left of the field-set
## The first filter should be ''Alarm Frames'' - ''greater than'' - 50
## Your second filter should be ''and'' - ''Weekday'' - ''equal to'' - ''Monday''
# To save this event filter method click on the save button. Make sure to write in a descriptive name for the filter.
[[image:alarmfiltersave.png|right|thumb|caption|Events Filter save form box]]
# Executing the event filter after you have saved it is as simple as clicking execute at the bottom of the page.
# You should now be on the event view page. This pages purpose is too list the events selected by your query method. From this view we are provided with many statistics about individual events. We may choose to review the events from this page by clicking on the name of the event, however for the purpose of this how to we will simply choose to export all events by selecting the check-box in the top right cell. After selecting all the events from this view we open up the export dialog by clicking the EXPORT button located in the bottom right corner.
# This export options dialog that pops up allows us to select the file type that is exported. Before clicking the export button you must first make sure too check the following settings:
##Export Event Details
##Export Frame Details
##Export File Format: Zip
# Once you click the export button ZoneMinder will go through the process of packaging and formatting the events for you, this process can be quite intensive for the server if a large number of events are selected. When the process is completed a download link for a file called zmExport.zip should pop up, select save file and click ok. It is important to make a note of where you save your file as you will need to access it later.

==Individual camera export==
[[image:individualview.png|right|thumb|caption|Individual camera view allows you to select specific events]]
[[image:individualeventview.png|right|thumb|caption|From the individual event view exporting is as simple as clicking export (top left)]]
This export Method is the simplest way to check and export an individual event that has happened recently on a specific monitor
===Steps===
# From your ZoneMinder homepage open the [[individual view]] of a specific camera
# On the "watch" view of a monitor the recent events should be listed by date under the live stream. Click on an event from this list to view the individual event.
# On the individual event view page you should get a stream of the event. To export this event simply click the Export link located at the top of the page.
# This export options dialog that pops up allows us to select the file type that is exported. Before clicking the export button you must first make sure too check the following settings:
##Export Event Details
##Export Frame Details
##Export File Format: Zip
# Once you click the export button ZoneMinder will go through the process of packaging and formatting the events for you, this process can be quite intensive for the server if a large number of events are selected. When the process is completed a download link for a file called zmExport.zip should pop up, select save file and click ok. It is important to make a note of where you save your file as you will need to access it later.

=Extracting Events=
A note about this section of the how to, For the examples i am using a custom export_functions.php plug-in that comes native in stagecoach wireless ZoneMinder installs.
Once you have selected your desired set of events you need a logical way to organize them and store them on your computer. My suggestion is too unzip all ZoneMinder exports to a specific folder so you have them all in one place to easily browse and backup.
==How to unpack the export files==
Most operating systems have many different applications that allow you to extract zoneminder.zip packages. For this example i will show you one way to do this.
===Linux===
[[image:archiveopen.png|right|thumb|caption|Ready to extract the events folder for viewing]]
#Navigate to the folder where zmexport.zip was downloaded to. In this example i have 4 zmexport.zip files extracted to the folder
#Double click opening up the archive manager
#Drag the events folder from the archive manager window into another folder. For ease of use i suggest you make a separate folder to store all your ZM export events in.
===Windows===
# Navigate to the folder where zmexport.zip was downloaded to. In this example i have 4 zmexport.zip files extracted to the folder
# Right-click the filename and select open with your archive manager (e.g 7-zip, winzip or winrar if you are using windows)
# When your archiving software is loaded up you should be able to select the events folder from zmexport.zip and drag it to your desired location in the file structure.

=Viewing Extracted Events=
[[image:zmeventsmasterfile.png|right|thumb|caption|zmEventImagesMaster.html has a time-stamp identifier so you can extract multiple events to one folder and still organize them by date]]
To view the events you have just extracted simply browse to the ''events'' folder. To view the interface of all events open up the newest zmEventImagesMaster file in Fire Fox.
From this page you get a tabbed view showing you events organized by monitor and chronological order. Within each events view you can display individual frames from the event or meta data about the event date/time/length
<gallery>
Image:zmeventmaster.png|Event viewer
Image:zmeventframes.png|Frames viewer
Image:zmeventdetails.png|Event data view
</gallery>
==Events folder structure==
*events
**monitor-ids
***event-ID
****zmEventDetail.html (this is the file that contains meta data about an individual event)
****zmEventFrames.html (this is the file containing a listed view of all event frames)
****xxx-capture.jpg (individual snapshot from the event)
**zmEventImagesMaster.html (this is the file that acts as the "home" page for each event extraction. you can extract multiple event sets to the events folder and acquire a list of these files

Axis

2016-05-22T09:06:31Z

Stevegilvarry: Spammer Revert

[[Image:Axis cameras.jpg]]

ZoneMinder will work well with just about any [http://www.axis.com Axis camera], including the 205, 206, 207, 209, 210, 211 and M10 ranges. It will also work with the 213 and 2130 cameras and support their [[PTZ]] functions through the web interface.

Please note that early 207's has some hardware issues. See [http://www.zoneminder.com/forums/viewtopic.php?t=5022 this thread] in the forum for details.
Also note that the [http://www.axis.com/techsup/cam_servers/cam_2100/index.htm 2100 has been discontinued by Axis] and no longer supported, possibly due to hardware related problems. It's noted in the [http://www.zoneminder.com/forums/viewtopic.php?t=10079 forums that the camera sends the pictures it captures somewhat diced up.]

How to Offload the Motion to cameras [[AxisMotionDetection]]

Axis publishes their full, open API named VAPIX; documentation may be found at [http://www.axis.com/techsup/cam_servers/dev/index.htm Axis Developer Pages]. Note in particular the HTTP API which defines the remote host path arguments which may be used by Zoneminder.

== AXIS 2110 ==

/axis-cgi/mjpg/video.cgi?camera=&resolution=320×240

== AXIS 207W ==

<User>:<Password>@<IP Address>/axis-cgi/mjpg/video.cgi?camera=&resolution=320×240

== AXIS P33XX-V/VE ==

<User>:<Password>@<IP Address>/axis-cgi/mjpg/video.cgi?camera=&resolution=320×240
or
<User>:<Password>@<IP Address>/mjpg/video.mjpg

== AXIS P1311 / P1344 ==

<User>:<Password>@<IP Address>/mjpg/video.mjpg

== AXIS P1357-E ==
This is set up to have the camera send an event to zoneminder.
* General
** Source type: Ffmpeg
** Function: Nodect
** Maximum FPS: <blank>
* Source
** rtsp://<CAM IP/HOSTNAME>/axis-media/media.amp?videocodec=h264&resolution=2592x1944&streamprofile=Quality&tcp&compression=0
** Capture Width: 2592
** Capture Height: 1944

modify /etc/init.d/zoneminder:
add to start section:
* /usr/bin/zmtrigger.pl&
to stop section:
* pkill zmtrigger.pl
* Options
** Images
*** OPT_FFMPEG: checked
*** PATH_FFMPEG: /usr/bin/avconv

For the camera:
* Detectors
** Motion Detection Add a window for detection. Adjust Object Size, History, Sensitivity. Check Activity to determine whether the settings are correct.
* Events
** Recipients Add a recipient. Choose Name, Type is TCP. Address is zoneminder name or IP address.
** Action Rules Enable rule.
*** Trigger
**** Detectors
**** Motion Detection
**** Name of detector set above
**** Motion: Yes
**** Schedule: Always
*** Actions:
**** Type: Send Notification
**** Recipient: Name as set above
**** Message: 1|on+5|5|cause|text|showtext
**** Check box for send notifications continuously
**** Send notification every 1 second

== AXIS 213PTZ ==
The axis 213PTZ works perfectly. Use the folowing settings:
'''SOURCE'''
Remote Protocol: RTSP
Remote Method: RTP/RTSP
Remote Host Name: <USER>:<PASS>@<CAM IP/HOSTNAME>
Remote Host Port: 554
Remote Host Path: /mpeg4/media.amp

'''CONTROL'''
Controllable: Yes
Control Type: Axis API v2
Control Address: <USER>:<PASS>@<CAM IP/HOSTNAME>

The resolution must match the one especified in the camera settings. Resolutions up to CIF will work without any problems but 2CIF and 4CIF will need the shared memory tweak (lean more at the [[FAQ]])

The [[AxisMotionDetection]] trick works quite well with this camera.

The Max FPS option of zoneminder introduces very big latency, so I use the option of the camera for limiting the FPS.

This was tested with zoneminder 1.24.2 running on Gentoo stable

== AXIS M1011-W ==

[http://www.axis.com/products/cam_m1011w/ M1011-W]

I get a lower load by using the MJPEG stream compared to the JPEG still images. [[User:Mathieumd|Mathieumd]] 15:52, 17 May 2012 (BST)

'''General'''
{| border="1"
! Tab/Label
! MJPEG Stream
! JPEG Stills
|-
| colspan="3" | '''General'''
|-
| Source Type
| colspan="2" align="center" | Remote
|-
| Maximum FPS
|
| 5
|-
| Alarm Maximum FPS
|
| 15
|-
| colspan="3" | '''Source'''
|-
| Remote Protocol
| colspan="2" align="center" | HTTP
|-
| Remote Method
| colspan="2" align="center" | Simple
|-
| Remote Host Name
| colspan="2" align="center" | [<USER>:<PASS>@]'''<CAM IP/HOSTNAME>'''
|-
| Remote Host Port
| colspan="2" align="center" | <CAM PORT> (usually 80 or 443)
|-
| Remote Host Path
| /axis-cgi/'''mjpg/video'''.cgi?resolution=640x480&fps=15
| /axis-cgi/'''jpg/image'''.cgi?resolution=640x480
|-
| Capture Width (pixels)
| colspan="2" align="center" | 640
|-
| Capture Height (pixels)
| colspan="2" align="center" | 480
|}

== AXIS M1031-W ==

[http://www.axis.com/products/cam_m1031w/ M1031-W]

'''SOURCE'''
Remote Protocol: HTTP
Remote Method: Simple
Remote Host Name: <CAM IP/HOSTNAME>
Remote Host Port: <CAM PORT>
Remote Host Path: /axis-cgi/mjpg/video.cgi?resolution=640x480

OR for mpeg-4

'''SOURCE'''
Remote Protocol: RTSP
Remote Method: RTP/RTSP/HTTP
Remote Host Name: <USER>:<PASS>@<CAM IP/HOSTNAME>
Remote Host Port: <CAM PORT>
Remote Host Path: /mpeg4/media.amp

[[Category:Cameras]]

== AXIS M1054 ==

Working just fine with my zoneminder setup under Ubuntu 10.04 and 11.04, using MJPEG setup.

My camera setup:
* Source type: remote
* Function: modect
* maximum fps 8.00
* alarm fps 30.00
* remote protocol: http
* remote method: simple
* remote host name: the DNS name of the camera (or IP adress I suppose)
* remote host port: 80
* remote host path: /axis-cgi/mjpg/video.cgi
* capture width: 1280
* capture height: 800

I just captured some thiefs with this setup, police caught them and used the pictures as proof. High quality pictures for that price of a camera and very reliable (running 1/2 year now without a single crash or disfunction).

==AXIS M1114==
works with following entrys
* Source type: remote
* Function: [what_you_want]
* maximum fps 0 # don't put any value here
* alarm fps 0 # don't put any value here
* remote protocol: http
* remote method: simple
* remote host name: user:password@IP-Address or user:password@DNS_Name
* remote host port: 80
* remote host path: /mjpg/video.mjpg?resolution=480x360
* capture width: 480 #depends on your "remote host path" setting, must to be the same!
* capture height: 360 #depends on your "remote host path" setting, must to be the same!

Using remote host path and arguments from the Axis VAPIX HTTP API. Includes limiting the frame rate (fps=x)

* Remote Protocol: HTTP
* Remote Method: Simple
* Remote Host Name: <user>:<password>@<hostname or IP>
* Remote Host Port: 80
* Remote Host Path: /axis-cgi/mjpg/video.cgi?fps=15&resolution=1024x640
* Remote Image Colours: 24 bit color
* Capture Width (pixels): 1024
* Capture Height (pixels): 640

==AXIS Q6032-E==

* Remote Protocol: HTTP
* Remote Method: Simple
* Remote Host Name: <user>:<password>@<hostname or IP>
* Remote Host Port: 80
* Remote Host Path: /mjpg/video.mjpg
* Remote Image Colours: <24 bit color|32 bit color>
* Capture Width (pixels): 704
* Capture Height (pixels): 480

==AXIS M7014==

-4 channel video encoder with receives signal from a Closed-Circuit-style camera via a BNC connector for each channel.

Works very well with zoneminder using the following settings:

* Remote Protocol: HTTP
* Remote Method: Simple
* Remote Host Name: <user>:<password>@<hostname or IP>
* Remote Host Port: 80
* Remote Host Path: /axis-cgi/jpg/image.cgi?camera=X where X is 1,2,3 or 4 - for each channel
* Remote Image Colours: <24 bit color|32 bit color>
* Capture Width (pixels): 704
* Capture Height (pixels): 480

Note: An axis tech suggested using:
rtsp://<ip>/axis-media/media.amp?camera=X but I didn't try it.
This is a really nice device for ZoneMinder - lets you use legacy cams easily. Highly recommended.

==AXIS M3007==
[http://www.axis.com/products/cam_m3007pv/ M3007]

* Remote Protocol: HTTP
* Remote Method: Simple
* Remote Host Name: <user>:<password>@<hostname or IP>
* Remote Host Port: 80
* Remote Host Path:
Overview - /mjpg/video.mjpg or /mjpg/1/video.mjpg
Panorama - /mjpg/video.mjpg?camera=2 or /mjpg/2/video.mjpg
Double Panorama - /mjpg/video.mjpg?camera=3 or /mjpg/3/video.mjpg
Quad - /mjpg/video.mjpg?camera=4 or /mjpg/4/video.mjpg
Feed 1 - /mjpg/video.mjpg?camera=5 or /mjpg/5/video.mjpg
Feed 2 - /mjpg/video.mjpg?camera=6 or /mjpg/6/video.mjpg
Feed 3 - /mjpg/video.mjpg?camera=7 or /mjpg/7/video.mjpg
Feed 4 - /mjpg/video.mjpg?camera=8 or /mjpg/8/video.mjpg

To make the PTZ work on feeds 1-4

* Control Type: Axis API V2
* Control Device: &camera=5 (6,7 or 8 depending on Feed 1,2,3 or 4)
* Control Address: user:pass@ipaddress:80
* Edit AxisV2.pm and change the following in the sendCmd subroutine. Rebooting seems to be the only way to make ZM reload the modified module.

'''CODE'''
my $req = HTTP::Request->new( GET=>"http://".$self->{Monitor}->{ControlAddress}."$cmd" );

to this

'''CODE'''
my $req = HTTP::Request->new( GET=>"http://".$self->{Monitor}->{ControlAddress}."$cmd".$self->{Monitor}->{ControlDevice} );

Installing using ZoneMinder RPMs for SuSE

2016-05-22T09:01:19Z

Stevegilvarry: Sneaky spammer 4 years no one found it.

[[Image:ZoneMinderSuSERPMS.png|left]]
This is a short How-to for installing [[ZoneMinder]] on [[SuSE|openSUSE]] with RPMs
Currently RPMS are available for openSuSE 11.4, 12.1, 12.2, 12.3 and 13.1 architectures are i586 and x86_64.

There are two versions available for every above listed [[SuSE]] version even one which requires only the packages that comes with the official [[SuSE]] release. These packages have some missing features of [[ZoneMinder]] like ffmpeg support and mjpeg streaming from remote cameras. The other version is build against the packages from [[VLC]] ([http://www.videolan.org/vlc/download-suse.html]) and do not lack these features. They can be identified by the "MP" in the package name, for example ZoneMinder-MP-1.28.1-1.1.x86_64.rpm.

== Installation of [[SuSE|openSUSE]] ==
Install [[SuSE]] on any supported way on your system. Detailed installation instruction are listed at [http://en.opensuse.org/Released_Version].

== Installation of [[ZoneMinder]] ==
=== using [[YaST]] ===
The best and easiest way is to install the [[ZoneMinder]] package via [[YaST]]. First you have to find out which [[SuSE]] version you are using. The urls to the different repositories are:

[[SuSE|openSUSE]] 13.1:
http://www.liquid-co.de/pub/suse/repositories/13.1/

[[SuSE|openSUSE]] 13.2:
http://www.liquid-co.de/pub/suse/repositories/13.2/

[[SuSE|openSUSE Leap]] 42.1:
http://www.liquid-co.de/pub/suse/repositories/42.1/

'''Depreciated openSUSE versions''' (repository is still there but not updated anymore)

[[SuSE]] 10.0:
Last ZoneMinder version: 1.22.3
http://www.liquid-co.de/pub/suse/repositories/discontinued/10.0/

[[SuSE]] 10.1:
Last ZoneMinder version: 1.23.3
http://www.liquid-co.de/pub/suse/repositories/discontinued/10.1/

[[SuSE|openSUSE]] 10.2:
Last ZoneMinder version: 1.23.3
http://www.liquid-co.de/pub/suse/repositories/discontinued/10.2/

[[SuSE|openSUSE]] 10.3:
Last ZoneMinder version: 1.24.2
http://www.liquid-co.de/pub/suse/repositories/discontinued/10.3/

[[SuSE|openSUSE]] 11.0:
Last ZoneMinder version: 1.24.2
http://www.liquid-co.de/pub/suse/repositories/discontinued/11.0/

[[SuSE|openSUSE]] 11.1:
Last ZoneMinder version: 1.24.2
http://www.liquid-co.de/pub/suse/repositories/discontinued/11.1/

[[SuSE|openSUSE]] 11.2:
Last ZoneMinder version: 1.24.2
http://www.liquid-co.de/pub/suse/repositories/discontinued/11.2/

[[SuSE|openSuSE]] 11.3:
Last ZoneMinder version: 1.25.0
http://www.liquid-co.de/pub/suse/repositories/discontinued/11.3/

[[SuSE|openSUSE]] 11.4:
Last ZoneMinder version: 1.27.0
http://www.liquid-co.de/pub/suse/repositories/discontinued/11.4/

[[SuSE|openSUSE]] 12.1:
Last ZoneMinder version: 1.27.0
http://www.liquid-co.de/pub/suse/repositories/discontinued/12.1/

[[SuSE|openSUSE]] 12.2:
Last ZoneMinder version: 1.27.0
http://www.liquid-co.de/pub/suse/repositories/discontinued/12.2/

[[SuSE|openSUSE]] 12.3:
Last ZoneMinder version: 1.27.0
http://www.liquid-co.de/pub/suse/repositories/discontinued/12.3/

Now you have to add the adequate repositories to [[YaST]]. Start [[YaST]] and go to "installation source". Select "add" and choose "http" as protocol. Enter as server "liquid-co.de" and as path "pub/suse/repositories/10.x". For more details on how to add package repositories to [[YaST]] go to [http://en.opensuse.org/Add_Package_Repositories_to_YaST].

Optional you can add one [[packman]] repository from [ftp://packman.links2linux.de/pub/packman/MIRRORS] so that it is possible to install the RPM build against the [[packman]] RPMs with mjpeg streaming support and dependencies to ffmpeg. However, newer versions of the ZoneMinder-MP package require the VLC repository.

Now go to [[YaST]]->Softwaremanagement search for [[ZoneMinder]] and select the version you want (either ZoneMinder or ZoneMinder-MP). Keep in mind that ZoneMinder-MP requires the VLC repository. Then proceed as normal, all other required packages will be resolved due to dependencies.

=== using one-click-install ([[SuSE|openSuSE]] >= 10.3) ===
[[SuSE|openSuSE]] 10.3 offers an installation by only one click. Just click on the following button. If you prefer the non MP version use the following link: [http://www.liquid-co.de/pub/suse/one-click-install/ZoneMinder.ymp Install normal version]

If you prefer the MP version use this one. If you don't already added one packman repository you can select one packman repository during the one-click-install dialogue.
[http://www.liquid-co.de/pub/suse/one-click-install/ZoneMinder-MP.ymp install MP version]

=== using [[Yum]] ===
You must have already installed [[Yum]] to use this way of installation. [[Yum]] easily can be installed via [[Yast]]. Choose the adequate link for your [[SuSE]] version above and download the ZoneMinder.repo file. (http://www.liquid-co.de/pub/suse/repositories/10.x/ZoneMinder.repo) and copy it to /etc/yum.repos.d/. Then run:

yum install ZoneMinder

which will list you the two available versions of [[ZoneMinder]]. Choose your wanted version and install [[ZoneMinder]]. All required packages will be installed automaticly.

'''Note:''' To install the RPM build against the [[packman]] RPMs with mjpeg streaming support and dependencies to ffmpeg you must have added the packman repository to Yum before.

=== Manual installation through rpm command ===
Download your choosen RPM from the listed repositories. Start root console and run:

rpm -ivh <ZoneMinder package>

'''Note:''' When you choose this way you have to resolve the package dependencies all by yourself. So the other methods are recommended.

== Setting up [[MySQL]] and [[Apache]] ==
After you successfully installed all RPMs start root console. Before you proceed to start [[Apache]] you should verify the timezone (date.timezone) in /etc/php5/apache2/php.ini. If the timezone isn't configured properly the hashed based authentication might not work. For a list of valid timezones have a look at [http://www.php.net/manual/en/timezones.php].

Now start [[Apache]] and [[MySQL]] by issuing the following commands:

openSUSE 12.1 and newer (systemd):
systemctl start mysql.service
systemctl start apache2.service

'''Note for systemd users:''' all output is redirected to /var/log/messages instead of printing them on stdout and stderr which means if something goes wring you should have a look at /var/log/messages.

openSUSE 11.4 and prior:
rcmysql start
rcapache2 start

When this is the first time you start [[MySQL]] it is highly recommended to set up a root password after you've started [[MySQL]] by invoking mysql_secure_installation.
mysql_secure_installation
NOTE: RUNNING ALL PARTS OF THIS SCRIPT IS RECOMMENDED FOR ALL MySQL
SERVERS IN PRODUCTION USE! PLEASE READ EACH STEP CAREFULLY!

In order to log into MySQL to secure it, we'll need the current
password for the root user. If you've just installed MySQL, and
you haven't set the root password yet, the password will be blank,
so you should just press enter here.

Enter current password for root (enter for none):
OK, successfully used password, moving on...

Setting the root password ensures that nobody can log into the MySQL
root user without the proper authorisation.

Set root password? [Y/n]
New password:
Re-enter new password:
Password updated successfully!
Reloading privilege tables..
... Success!

By default, a MySQL installation has an anonymous user, allowing anyone
to log into MySQL without having to have a user account created for
them. This is intended only for testing, and to make the installation
go a bit smoother. You should remove them before moving into a
production environment.

Remove anonymous users? [Y/n]
... Success!

Normally, root should only be allowed to connect from 'localhost'. This
ensures that someone cannot guess at the root password from the network.

Disallow root login remotely? [Y/n]
... Success!

By default, MySQL comes with a database named 'test' that anyone can
access. This is also intended only for testing, and should be removed
before moving into a production environment.

Remove test database and access to it? [Y/n]
- Dropping test database...
... Success!
- Removing privileges on test database...
... Success!

Reloading the privilege tables will ensure that all changes made so far
will take effect immediately.

Reload privilege tables now? [Y/n]
... Success!

Cleaning up...

All done! If you've completed all of the above steps, your MySQL
installation should now be secure.

Thanks for using MySQL!

When you plan to start ZoneMinder at boot, you can now add [[Apache]] and [[MySQL]] for automatic start by typing:

openSUSE 12.1 and newer (systemd):
systemctl enable mysql.service
systemctl enable apache2.service

openSUSE 11.4 and prior:
chkconfig apache2 on
chkconfig mysql on

'''Note:''' Of course you can also use [[YaST]] Runleveleditor for this task.

== Initializing [[ZoneMinder]] ==
Log in into root console and run:
zm_database_init

and follow the steps on the screen. This script will setup the [[ZoneMinder]] database, creating the zm_admin user for database access and update the /etc/zom.conf with the new set password for zm_admin user. Example output:
zm_database_init
INFO: when db is correctly installed and you just reinstalled rpm, then answer all questions with 'n'
Enter mysql root password:
generated/updated ~/.my.cnf
run mysql command to create db as user root? [Y/n]:
create user zm_admin for zoneminder? [Y/n]:
enter new passwd for user zm_admin:
retype password:
should the config file updated with the new passwd? [Y/n]:
database successfully initialized
you can now start ZonMinder with rczmstart or systemctl start zm.service
removing lock file

'''Important Note:''' If you entered the wrong mysl root password or changed the mysql root password and you get something like ''Permission denied for user root'' when running zm_database_init (you don't get prompted for the mysql root password again) you have to edit /root/.my.cnf and enter the correct mysql root password there or remove that file to get prompted for the root password again (during execution of zm_database_init). After that run zm_database_init again which should now proceed as desired.

Then run the following command to start [[ZoneMinder]]:

openSUSE 12.1 and newer (systemd):
systemctl start zm.service

'''Note for systemd users:''' all output is redirected to /var/log/messages instead of printing them on stdout and stderr which means if something goes wring you should have a look at /var/log/messages.

openSUSE 11.4 and prior:
rczm start

To enable the start of [[ZoneMinder]] at boot enter:

openSUSE 12.1 and newer (systemd):
systemctl enable zm.service

openSUSE 11.4 and prior:
chkconfig zm on

After this [[ZoneMinder]] will start at boot after apache2 and mysql were started.

After successfully installation the ZoneMinder web interface can be reached at http://localhost/zm

'''Hint:''' Since [[SuSE|openSuSE]] 10.3 PHP short_open_tag is disabled by default. The RPM now includes a config file for apache to avoid a manual edit. The only thing you have to do is to '''restart apache''' after the installation (rcapache2 restart)!

'''Note:''' When trying to run rczm start without running zm_database_init the start will fail.

== Update [[ZoneMinder]] ==
When new version of [[ZoneMinder]] or of the RPMs are available you might want to update your existing installation. You can use [[YaST]] again for this task. Before you enter [[YaST]] run "rczm stop" to stop [[ZoneMinder]]. Go to [[YaST]] -> Softwaremanagement and search for [[ZoneMinder]]. Switch the checkbox to "upgrade" (look for icon explaining in [[YaST]] or in textmode for ">"). Choose your wanted version as described in [[Installing_using_ZoneMinder_RPMs_for_SuSE#Installation of ZoneMinder | Installation of ZoneMinder]] and proceed. After installation run zm_database_init and follow the steps on the screen to update your database.

'''Note:''' When upgrading without [[ZoneMinder]] version change, this happens for example when upgrading from one rpm version to a later RPM version (for example from ZoneMinder-1.22.3-10.x86_64.rpm to ZoneMinder-1.22.3-11.x86_64.rpm ) then the database is already installed and no database upgrade is necessary. In this case, when you will be asked weather to create zm database or to create the zoneminder database user, you have to answer all questions from the zm_database_init script with "no".

'''Note:''' If not stopping [[ZoneMinder]] (rczm stop) before upgrading you might get an information box with "... failed". you can ignore this box, but after installation ZoneMinder will be stopped.

*** '''Due to package name change of the MP package you have to run "cp /etc/zm.conf.rpmsave /etc/zm.conf" and before "zm_datbase_init" when upgrading the MP package from 1.22.3 to 1.23.x. Finally you have to rerun "chkconfig zm on" when you want to start [[ZoneMinder]] at boot. For more detailed informations look at [[Installing_using_ZoneMinder_RPMs_for_SuSE#Switching between MP and non MP version | Switching between MP and non MP version]].'''

== Upgrade from manual installation to RPM ==
When upgrading from a manual installation from [[ZoneMinder]] to any RPM version remove all related zoneminder files except the config file /etc/zm.conf. Then install the RPM and follow the steps listed in[[Installing_using_ZoneMinder_RPMs_for_SuSE#Installation of ZoneMinder | Installation of ZoneMinder]].

== Switching between MP and non MP version ==
Follow the steps described at [[Installing_using_ZoneMinder_RPMs_for_SuSE#Installation of ZoneMinder | Installation of ZoneMinder]]. Because ZoneMinder-MP and ZoneMinder packages are conflicting [[YaST]] will report a conflict. Resolve the dependencies by deleting the unwanted [[ZoneMinder]] version. After finished installation you have to replace the new installed configuration file by typing (as root):
cp /etc/zm.conf.rpmsave /etc/zm.conf
the run zm_database_init if this is not an update of ZoneMinder (compare to [[Installing_using_ZoneMinder_RPMs_for_SuSE#Update ZoneMinder | Update Zoneminder]]) and answer all questions with '''no''' otherwise follow the update steps on the screen.

'''Note:''' After switching between MP and non MP version you have to run "chkconfig zm on" again if you want to start [[ZoneMinder]] at boot.

== Uninstalling [[ZoneMinder]] ==
If you are uninstalling ZoneMiner the database will be untouched, the recorded events and logfiles will reside on the disk and the zm.conf file in /etc will be copied to zm.conf.rpmsave.

== Info on Shared Memory ==
Since package version 1.25.0-44 [[ZoneMinder]] is compiled with mmap enabled. This should simplify the shared memory handling by using /dev/shm. The available space by default is half of the available RAM.

To adjust the shared memory settings for prior versions have a look at the [[FAQ#What_does_a_.27Can.27t_shmget:_Invalid_argument.27_error_in_my_logs_mean.3F_and_my_cameras_won.27t_display_video_at_higher_resolutions.|FAQ Section]].

D-Link

2016-05-22T08:58:27Z

Stevegilvarry: Undo revision 4650 by Xadmin (talk)

DLink is a supplier of several IP Cameras. Not all work with ZoneMinder.
DCS-1000(W) and DCS-900 - plus other D-Link IP models (This have been hit and miss, not all work with ZM. A partial list of unsupported cameras are inside).

=DCS-900=
[[Image:DCS900.png]]

There are 2 versions of this camera. The "A" version is reported to work extremely well with ZoneMinder. The "B" version also works, but has a been reported to have lesser performance. I have been able to get upto 8 fps with my revision "B" camera.

Source Type: Remote
Remote Host Name: IP Address of Camera
Remote Host Port: 80 (Default)
Remote Host Path: /VIDEO.CGI or /IMAGE.JPEG
(/VIDEO.CGI is the MJpeg stream, and gets higher FPS in my testing)

With version A2
Source Type: Remote
Remote Host Name: user:pass@<IP_Address_of_Camera> (user:pass@192.168.0.5)
Remote Host Port: 80 (Default)
Remote Host Path: VIDEO.CGI

With the latest versions of the DCS-900 "B" there is an additional step needed in the "Options > Network" section of ZoneMinder.
ZM_NETCAM_REGEXPS Value = (no-checkmark)

=DCS-910 / 920=
[[Image:DCS-910.jpg]]

Source Type: Remote
Remote Host Name: user:pass@<IP Address of Camera>
Remote Host Port: 80 (Default)
Remote Host Path: /VIDEO.CGI? for stream

There is the same aditional step as in DCS-900B, in the "Options > Network" section of ZoneMinder.
ZM_NETCAM_REGEXPS Value = (no-checkmark)

=DCS-930L / 932L=
[[Image:DCS-930L.jpg]]

Source Type: Remote
Remote Host Name: user:pass@<IP Address of Camera>
Remote Host Port: 80 (Default)
Remote Host Path: /image/jpeg.cgi
Capture Width (pixels): 640
Capture Height (pixels): 480

Additionally MJPEG stream avaliable at: /MJPEG.CGI but next step is required for it, in the "Options > Network" section of ZoneMinder.
ZM_NETCAM_REGEXPS Value = (no-checkmark)

The "Snapshot URL Authentication" must be disabled on the camera. Maintenance > Server Settings > Set Snapshot URL Authentication to "Disabled".

For the '''DCS-932L''' also works:

Remote Host Path: /video.cgi

If you want to limit the FPS just as it is set in the camera's setup -> video -> FPS, then you will need to use the video stream (video.cgi) and not the snapshot stream (/image/jpeg.cgi).

Using /mjpeg.cgi gives a lot of erros in the log files:

ERR [Invalid JPEG file structure: two SOI markers]
ERR [Unable to decode jpeg]

=DCS-931L / DCS-933L / DCS-934L=
[[Image:DCS931L.png]]

This camera can do up to 30 fps with MJPEG. (Firmware 1.01, zoneminder 1.25.0)

To set video properties on the camera, click on setup, then video. Here you can adjust settings for mjpeg quality and the frame rate. You might also want to set the default (browser) view mode to image, so that you'll get something when logging into the camera if you don't have java installed.

MJPEG settings for zoneminder:

Source Type: Remote
Remote Protocol: HTTP
Remote Method: Simple
Remote Host Name: user:pass@IP Address of Camera
Remote Host Port: 80 (Default)
Remote Host Path: /video.cgi
Colors: 24 bit
Capture width: 640
Capture Height: 480

Notes:

# An unknown-quality H.264 stream available at http://user:pass@ip.of.camera/h264.flv. Haven't worked out how to get it working in zoneminder yet.
# Audio is available from http://user:pass@ip.of.camera/dgaudio.cgi .

=DCS-942L=

Image capture works the same as 932L and /image/jpeg.cgi over HTTP.
RTSP stream works with MPEG streams (/3gpp by default)
RTSP H.264 streaming works if set as follows:

Source Type: ffmpeg
Source Path: rtsp://<camera ip>:554/play2.sdp

To stream the motion JPEG in 640x480:
Source Type: remote
Protocol:HTTP
Remote Host Name: <username>:<password>@<camera ip>
Remote Host Path: /video/mjpg.cgi?profileid=1

For 320x240 motion JPEG, substitute profileid=3. The profile IDs are configurable under the "Audio and Video" setup screen in the camera's built-in web server.

If the Zoneminder (1.25) monitor crashes every 10-30s (check your logs), set:

echo 536870912 >/proc/sys/kernel/shmmax

from the wiki [[FAQ#What_does_a_.27Can.27t_shmget:_Invalid_argument.27_error_in_my_logs_mean.3F_and_my_cameras_won.27t_display_video_at_higher_resolutions.]]

=DCS-1100=
[[File:dcs-1100.jpg|100px]]
Source Type: Remote
Remote Protocol: HTTP
Remote Method: Simple
Remote Host Name: user:pass@<IP Address of Camera>
Remote Host Port: 80 (Default)
Remote Host Path: /video/mjpg.cgi?profileid=3

Where Profileid is setup in the camara's setup interface.

=DCS-2100+, DCS-2100G=
[[Image:DSC2100plus.jpg]][[Image:DCS2100g.jpg]]
Source Type: Remote
Remote Host Name: IP Address of Camera
Remote Host Port: 80 (Default)
Remote Host Path: /cgi-bin/video.jpg

Note: you must change Network -> ZM_HTTP_VERSION option to 1.0 for this camera to work!

=DCS-2120=
[[Image:DCS2100g.jpg]]

Source Type: Remote
Remote Host Name: IP Address of Camera
Remote Host Port: 80 (Default)
Remote Host Path: /cgi-bin/video.jpg

=DCS-2121=
JPG Stills:
Source Type: Remote
Remote Host Name: username:password@cam_ip
Remote Host Port: 80 (Default)
Remote Host Path: /image/jpeg.cgi?profileid=1

MJPEG:
Source Type: Remote
Remote Host Name: username:password@cam_ip
Remote Host Port: 80 (Default)
Remote Host Path: /video/mjpg.cgi

=DCS-2130=
Source Type: Remote
Remote Host Name: username:password@cam_ip
Remote Host Port: 80 (Default)
Remote Host Path: /image/jpeg.cgi?profileid=1

=DCS-2210 and DCS-2230=

MPEG4:
<pre>
(Change in video settings of the camera the mode to MPEG4 first)
Source Type: Remote
Remote Protocol: RTSP
Remote Method: RTP/Unicast
Remote Host Port: 554
Remote Host Name: <IP Address of Camera>
Remote Host Path: /live1.sdp
</pre>

H.264:
<pre>
Source Type: Remote
Remote Protocol: Ffmpeg
Remote Method: RTP/RTSP
Source Path: rtsp://<IP Address of Camera>:554/live1.sdp
</pre>

MJPEG:
<pre>
(Change in video settings of the camera the mode to JPEG first)
Source Type: Remote
Remote Protocol: HTTP
Remote Host Port: 80
Remote Host Name: user:pass@<IP Address of Camera>
Remote Host Path: /video1.mjpg
</pre>

Notes:
<ul>
<li>These cameras can transmit multiple streams ("profiles") simultaneously, but they do not produce their advertised frame rates with some combinations, particularly if using MJPEG in certain resolutions. Using MJPEG in resolutions other than 800x450 or 640x360 will cause large reduction in video frame rate on all the other profiles. A configuration known to produce 1920x1080 @ 17fps is:
<pre>
Number of profiles: 2
Aspect ratio: 16:9
Profile 1: 1920 x 1080
Profile 1 frame rate: 15
Profile 1 encoding: H.264
Profile 2: 640x360
Profile 2 frame rate: 7
Profile 2 encoding: MJPEG
</pre>
<li>Profile 1 MUST be set to 1080p. Otherwise the image appears "zoomed in." This is a known firmware bug with the DCS-2230.
</ul>

=DCS-3220=
[[Image:DCS-3220.jpg]]
Source Type: Remote
Remote Method: Simple (using ZM 1.28.1 and latest FW, '''"Regexp"''' seems to fix broken frames and "Unable to decode" messages in log)
Remote Host Name: IP Address of Camera
Remote Host Port: 80 (Default)
Remote Host Path: /cgi-bin/video.jpg

=DCS-3410=

[[Image:DSC-3410.jpg]]

HTTP
Source Type: Remote
Remote Host Name: user:pass@<IP Address of Camera>
Remote Host Port: 80 (Default)
Remote Host Path: /video/mjpg.cgi (for mjpeg stream)

RTSP
Source Type: ffmpeg
Source Path: rtsp://user:pass@<IP Address of Camera>/play1.sdp (or play2.sdp)

ZoneMinder 1.24.2 (Haven't tried earlier versions)

Tried it with just admin:@<IP Address of Camera> without password before setting camera password and it worked. Created an account with a password, tried that and it also worked.

May need /video/mjpg.cgi?profileid=3 caught that from tcpdump, suspect the numbers are resolution but don't seem to have any affect.

Seems like it's operating in factory default Profile 3, 704x480 10fps jpeg. Haven't found a way to change the Profile used yet. Could only pull about 22fps when camera was set to 30fps (mjpeg) so opted to set camera to 15fps.

RTSP works with ffmpeg as above pulling 30fps when camera set to 30fps for that Profile but could not get it working with Source Type Remote and Remote Protocol RTSP.

Looks like Audio is at /audio/ACAS.cgi but haven't done anything with that.

=DCS-3710=
HTTP
Source Type: Remote
Remote Host Name: user:pass@<IP Address of Camera>
Remote Host Port: 80 (Default)
Remote Host Path: /video2.mjpg (for stream 2)

ZoneMinder 1.24.3 (Haven't tried earlier versions)

Video profile mode must be set to JPEG.

=DCS-4602EV=

[[Image:DCS-4602EV.png|DCS4602EV]]
Source Type: Remote
Remote Protocol: HTTP
Remote Method: Simple
Remote Host Name: user:pass@<IP Address of Camera>
Remote Host Port: 80 (Default)
Remote Host Path: /video1.mjpg
Colors: 24 bit
Capture width: 1920
Capture Height: 1080

ZoneMinder 1.29.0 (Haven't tried earlier versions)

=DCS-5010L, DCS-5020L and DCS-5025L=

[[Image:DCS5010Lfront.png|left|DCS5010L]]
[[Image:DCS5020Lfront.png|DCS5020L]]

 

The features and firmware of both of these models are identical excepting that the DCS-5020L has a wifi repeater built in, which does not affect the video capabilities of the camera. The DCS-5025L has 720p resolution. These cameras can do up to 30 fps with MJPEG. (Firmware 1.01, zoneminder 1.25.0)

To set video properties on the camera, click on setup, then video. Here you can adjust settings for mjpeg quality and the frame rate. You might also want to set the default (browser) view mode to image, so that you'll get something when logging into the camera if you don't have java installed.

MJPEG settings for zoneminder:

Source Type: Remote
Remote Protocol: HTTP
Remote Method: Simple
Remote Host Name: user:pass@IP Address of Camera
Remote Host Port: 80 (Default)
Remote Host Path: /video.cgi
Colors: 24 bit
Capture width: 640 (1280 for DCS-5025)
Capture Height: 480 (720 for DCS-5025)

PTZ Controls can be used from within ZoneMinder using the control script linked below. Copy the script contents into a file alongside of the other ZM Control Scripts.

[[D-Link DCS-5020L Control Script]]

PTZ Settings:

Main: Type: Remote, Protocol: DCS5020L, Name: DCS5020L, Can Wake, Can Sleep, Can Reset
Move: Can Move, Can Move Diagonally, Can Move Mapped, Can Move Relative
Pan: Can Pan, Min Pan Step 1, Max Pan Step 30
Tilt: Can Tilt, Min Tilt Step 1, Max Pan Step 30
Presets: Has Presets, Number: 24, Has Home Preset

Note: Wake turns IR on, Sleep turns IR off, Reset turns IR to auto.

Settings for Control Tab:

Controllable, Control Type: DCS5020L, Control address: user:pass@ipaddress

Notes:

# For PTZ control, the user/pass combination must be an administrator on the camera. A regular view-only user will not work.
# An unknown-quality H.264 stream available at http://user:pass@ip.of.camera/dgh264.raw . Haven't worked out how to get it working in zoneminder yet.
# Audio is available from http://user:pass@ip.of.camera/dgaudio.cgi while the accompanying video is at http://user:pass@ip.of.camera/dgvideo.cgi
# The DCS-5020L script was based on the Trendnet TV-IP400W control script, available at http://www.sfpeter.com/2008/07/new-trendnet-tv-ip400w-controller-for-zoneminder-123x/ . "<tt>use ZoneMinder::Debug qw(:all);</tt>" was replaced with "<tt>use ZoneMinder::Logger qw(:all);</tt>" for zoneminder 1.25 compatibility.

=DCS-5222L=

[[Image:DSC-5222L.jpg]]

HTTP
Source Type: Remote
Remote Host Name: user:pass@<IP Address of Camera>
Remote Host Port: 80 (Default)
Remote Host Path: /video/mjpg.cgi (for mjpeg stream)
Remote Host Path: /image/jpeg.cgi (for jpeg stream)

The jpeg and the mjpeg both output at the resolution specified for "video profile 3"

RTSP
Source Type: ffmpeg
Source Path: rtsp://user:pass@<IP Address of Camera>/play1.sdp (or play2.sdp)

May need /video/mjpg.cgi?profileid=3 might catch other profiles by using this URL

Looks like Audio is at /audio/ACAS.cgi but haven't done anything with that.

=DCS-5300G=

[[Image:DCS-5300G.jpg]]

Source Type: Remote
Remote Host Name: IP Address of Camera
Remote Host Port: 80 (Default)
Remote Host Path: /cgi-bin/video.jpg

Note: you must change Network -> ZM_HTTP_VERSION option to 1.0 for this camera to work!

=DCS-6010L=

[[Image:DCS-6010.jpeg]]

HTTP
Source Type: Remote
Remote Host Name: user:pass@<IP Address of Camera>
Remote Host Port: 80 (Default)
Remote Host Path: /video/mjpg.cgi (for mjpeg stream)
Remote Host Path: /image/jpeg.cgi (for jpeg stream)

The jpeg and the mjpeg both output at the resolution specified for "video profile 3"

May need /video/mjpg.cgi?profileid=3 might catch other profiles by using this URL

=DCS-6111=

[[File:DCS6111.jpg]]

Source Type: Remote
Remote Protocol: HTTP
Remote Host Port: 80 (Default)
Remote Host Name: user:pass@<IP Address of Camera>
Remote Host Path: (stream 1): /video.mjpg
Remote Host Path: (stream 2): /video2.mjpg

=DCS-1000=

[[File:DCS-1000_left.png]]

Source Type: Remote
Remote Protocol: HTTP
Remote Host Port: 80 (Default)
Remote Host Name: user:pass@<IP Address of Camera>
Remote Host Path: VIDEO.CGI (You must upgrade the firmware on the camera to 1.30 for this to work. Try this [http://www.dlink.co.uk/cs/Satellite?c=TechSupport_C&childpagename=DLinkEurope-GB%2FDLTechProduct&cid=1197319187751&p=1197318962293&packedargs=locale%3D1195806691854&pagename=DLinkEurope-GB%2FDLWrapper site] for the firmware and the ipview software to install the firmware.)

=DCS-6620G=

[[Image:DCS-6620G.jpg]]

Source type: Remote
Remote Host Name: IP Address of Camera
Remote Host Port: 80 (Default) or the non-default port assigned to the camera in your network
Remote host Path: /cgi-bin/video.jpg
Control script: download at www.condrau.com/download/zmcontrol-dcs6620g.pl

The control script supports all controls for this camera, but it can be used for other D-Link and Vivotek cameras as well. I verified it with DCS-6620 and Vivotek's PT7137, as the software is compatible with these 2 cameras. It should also work with other models such as the DCS-5300.

Note that I implemented a real name preset functionality, where you can set any desired name as the preset name. It is basically possible to set the presets through ZM's interface, but I prefer to do it through the cam's firmware interface, which is the default setting in the script. By changing one constant definition, you may change this behaviour. In any case still activate the "can set presets" option in ZM, after which you can assign names to each preset.

I would further recommend to update the cam's firmware. I found smoother operation in ZM after having updated the firmware, and also with the latest firmware you can set ZM_HTTP_VERSION option to 1.1.
[bco]

The camera will work with Zoneminder 1.25 with some minor modifications to the template PanasonicIp.pm script. Copy file and rename to DCS6620. Changed commands are listed below. The the only tricky part was zoom. Changes nearly identically for (PZ8111) which is almost the same camera. Note difference /cgi-bin/$cmd instead of /cgi-bin/camctrl/$cmd in. For some reason the zoom ui is calling Tele and Wide functions instead of zoomConTele and zoomConWide. Use the options below
Monitor
* Control Type = DCS6620
* Control Device = blank
* Control Address = <ip address of your camera>
Control Capabilities
* Type = Remote
* Protocol = DCS6620
* Can Move = Check
* Can Move Continuous = Check
* Can Pan = Check
* Can Tilt = Check
* Can Zoom = Check

<pre>
package ZoneMinder::Control::DCS6620;
sub sendCmd
{
my $self = shift;
my $cmd = shift;

my $result = undef;

printMsg( $cmd, "Tx" );

my $req = HTTP::Request->new( GET=>"http://".$self->{Monitor}->{ControlAddress}."/cgi-bin/$cmd" );
my $res = $self->{ua}->request($req);

if ( $res->is_success )
{
$result = !undef;
}
else
{
Error( "Error check failed: '".$res->status_line()."'" );
}

return( $result );
}

sub moveConUp
{
my $self = shift;
Debug( "Move Up" );
my $cmd = "camctrl.cgi?move=up";
$self->sendCmd( $cmd );
}

sub moveConDown
{
my $self = shift;
Debug( "Move Down" );
my $cmd = "camctrl.cgi?move=down";
$self->sendCmd( $cmd );
}

sub moveConLeft
{
my $self = shift;
Debug( "Move Left" );
my $cmd = "camctrl.cgi?move=left";
$self->sendCmd( $cmd );
}

sub moveConRight
{
my $self = shift;
Debug( "Move Right" );
my $cmd = "camctrl.cgi?move=right";
$self->sendCmd( $cmd );
}

sub Tele
{
my $self = shift;
#my $params = shift;
#my $step = $self->getParam( $params, 'step' );
Debug( "Zoom Tele" );
my $cmd = "camctrl.cgi?zoom=tele";
$self->sendCmd( $cmd );
}

sub Wide
{
my $self = shift;
#my $params = shift;
#my $step = $self->getParam( $params, 'step' );
Debug( "Zoom Wide" );
my $cmd = "camctrl.cgi?zoom=wide";
$self->sendCmd( $cmd );
}

</pre>

=DCS-7010L=

Change in video settings of the camera the mode to MPEG4 and restart the device.
<pre>
Source Type: Remote
Remote Protocol: RTSP
Remote Method: RTP/Unicast
Remote Host Port: 554
Remote Host Name: <IP Address of Camera> (RTSP authentication didn't work with this method)
Remote Host Path: /live1.sdp
</pre>
<pre>
Source Type: Remote
Remote Protocol: Ffmpeg
Remote Host Path: rtsp://<IP Address of Camera>:554/live1.sdp
Remote Host Path: rtsp://user:pass@<IP Address of Camera>:554/live1.sdp (when RTSP authentication is enabled)
</pre>
<pre>
Source Type: Remote
Remote Protocol: HTTP
Remote Host Port: 80
Remote Host Name: user:pass@<IP Address of Camera>
Remote Host Path: /video1.mjpg
</pre>

=DCS-7110=

Device's web server gives example code for various setups. Verified 2012-12-08.

<pre>
* http://<cam-ip>:80/cgi-bin/viewer/video.jpg?streamid=0&quality=5 // single-shot jpg image
* rtsp://<cam-ip>:554/live.sdp // feeds VLC
</pre>

=Incompatible Hardware=

I know that the DCS-1110 is not compattible with ZoneMinder, as it requires ActiveX to recive the MJpeg stream.

If you know of other DLink cameras that don't work, please add them to the list!

DCS-950 not compatible. Mpeg stream. Authentication is OCX application based, not web standard authentication. JPG file generated at random url, not predictable.

[[Category:Cameras]]
[[Category:Network Cameras]]

Ubuntu

2016-05-22T08:22:13Z

Stevegilvarry:

Ubuntu is a Linux distribution based on Debian. It's a good system for a home / office user and the install CD installs 'most everything the home / office user will need.

==Installation Guides==

* Using an Ubuntu Desktop distro, you will be able to host a complete ZM installation, and also watch the console/events/streams on the same machine;

* Using an Ubuntu Server distro, '''you will not be able to watch ZM''' on the same machine at all; but the system becomes much more light, using less resources and using an '''optimized Kernel''' for server applications;

Before choosing, consider checking

http://www.ubuntu.com/products/whatisubuntu/serveredition/features

http://www.ubuntu.com/products/whatisubuntu/serveredition/features/kernel

===Common Issues with Zoneminder Installation on Ubuntu. Includes upgrade instructions!===

[[Common Issues with Zoneminder Installation on Ubuntu]] '''Includes upgrade instructions!'''

===Guides for Ubuntu Server===

[[Ubuntu Server 12.04 64-bit with Zoneminder 1.25.0 the easy way]]

[[Ubuntu Server 14.04 64-bit with Zoneminder 1.26.5 the easy way]]

[[Ubuntu Server 15.04 64-bit with Zoneminder 1.26.5 the easy way]]

[[Ubuntu Server 15.10 64-bit with Zoneminder 1.28.1 the easy way]]

[[Ubuntu Any Version 12.04+ 64-bit with Zoneminder 1.28.1 the Docker way (two commands)]]

[[Ubuntu Server 14.04 64-bit with Zoneminder 1.29.0 the easy way]]

[[Ubuntu Server 15.04 or 15.10 64-bit with Zoneminder 1.29.0 the easy way]]

[[Ubuntu Server 16.04 64-bit with Zoneminder 1.29.0 the easy way]]

===Guides for Ubuntu Desktop===

Installing Zoneminder on a desktop system can have its benefits. It can also pose problems!

If you use one of the desktops provided with Ubuntu (Gnome, Unity, KDE, et. al.) use the corresponding Ubuntu server install/upgrade instructions. You may need to install tasksel to make it easier to install LAMP as most of the Ubuntu instructions start with a system set up with LAMP. It is recommended to install Zoneminder from a terminal. Using a software/package manager can get you in trouble!

If you are using a distro such as Mint, find out which Ubuntu system your version is based on and use the corresponding Ubuntu server install/upgrade. And do the procedure from a terminal!

Oh, did I fail to mention it is easy to copy the command instructions from the instructions on the WIKI and paste them into the terminal window? It is a great way to avoid typos!!!

[[Lubuntu 16.04 with Zoneminder 1.29.0 pre-configured CD or USB]]

[[Lubuntu 14.04 with Zoneminder 1.29.0 pre-configured CD or USB]]

[[Ubuntu 12.04/13.04 Desktop]]

===Outdated versions===

* You may find useful or related info under the following guides to older ubuntu versions:

[[Ubuntu Server 14.04 64-bit with Zoneminder 1.28.0 the easy way]]

[[Ubuntu Server 14.04 64-bit with Zoneminder 1.28.1 the easy way]]

[[Ubuntu Server 14.10 64-bit server with Zoneminder to use systemd]]

[[Ubuntu Server 15.04 64-bit with Zoneminder 1.28.1 the easy way]]

==Installation Notes==
http://www.zoneminder.com/forums/viewtopic.php?t=5633
GUI package that installs Mplayer etc.

http://ubuntuforums.org/showpost.php?p=356392
EXTRA_LIBS parameter in .configure script

http://www.zoneminder.com/forums/viewtopic.php?t=6141

http://www.zoneminder.com/forums/viewtopic.php?t=13140 How to install latest Zoneminder on Ubuntu 8.10

==Links==
[http://ubuntulinux.org http://ubuntulinux.org]

[[Categories: Linux distributions]]

ACTi

2016-05-22T08:03:18Z

Stevegilvarry:

== ACM 5611 ==

This is the setup I am using for the ACM 5611

Source type = remote

Remote Protocol = HTTP

Remote Method = Simple

Remote Host Name = login:pwd@IP_address

Remote Port = 80

Remote Host Path = /cgi-bin/cmd/encoder?GET_STREAM

Remote Image Colours = 24 bit colour

Capture Width 1280

Capture Height 720 (also used 1024)

Those were all I set and it came right up.

I have used this same format with other cameras of the

ACM family, they all worked.

== ACTi D32 ==

HTTP support buggy in the D32. Use RTSP.

Remote Method: RTP/RTSP

Remote host name: user:pass@host

Remote Host Port: 7070 (this is the default port for the factory configuration. can be changed in Network menu)

Remote Host Path: (leave empty)

Target Colorspace 24 bit color

Capture Width: (set the same as camera's config)

Capture Height: (set the same as camera's config)

Preserve Aspect Ratio: unchecked

Orientation: (set to whatever you need/like)

Deinterlacing: Disabled

== ACTi TCM-5611 working setup ==

I could only get the streaming unicast from the camera working with VLC but not with Zoneminder so I went the HTTP route.

Using the camera's web configurator page, I first set the camera to 640x480, MJPEG.

Then created a device in Zoneminder.

Source: remote

protocol: HTTP

FPS: blank

max FPS: blank

640x480

address: user:password@xxx.xxx.xxx.xxx

path: /cgi-bin/cmd/system?GET_STREAM

=== RTP B2 Frames ===

Some ACTi cameras, including the KCM-5611 and B95, have a proprietary feature which injects "B2 Frames" (an ACTi-proprietary data blob containing timestamps and other info) into the MJPEG stream. If this feature is enabled, neither ZoneMinder nor browsers like Firefox and Chrome will be able to decode the MJPEG stream from the camera. On some cameras this option is enabled by default; to disable the B2 frames, go to the Network->RTP page in the camera's Web Configurator and un-check the RTP B2 Frame option.

MediaWiki:Sidebar

2016-05-22T07:00:35Z

Stevegilvarry:

The ZoneMinder ToolKit

2016-03-31T09:59:17Z

Stevegilvarry: Undo revision 5721 by Chereame (talk)

The ZoneMinder ToolKit (ZMTK) is an implementation of the principles outlined in the [[ZM2 Architecture Discussion]] page. It is not currently a finished product and has no installer as such. It is intended as a demonstration of the possibilities of a modular framework and how it can be used to easily build applications from reusable components to perform any number of specific video security related tasks.

A sample application is included in the zmx.cpp file, actually there are several applications available within it so if you want to try one out just ensure you un-comment the appropriate section. Example applications are as follows, they are easy to modify to work differently if you want to try something else.

* Simple stream capture to file
* Simple stream capture to shared memory ring buffer
* Extraction of stream from shared memory buffer to file
* Simple stream capture and presentation as HTTP, RTSP, or RTMP (flash) streams
* Simple stream capture, timestamping and presentation as HTTP, RTSP, or RTMP (flash) streams
* Multiple stream capture, integration into 'quad' display and presentation as HTTP, RTSP, or RTMP (flash) streams
* Stream capture, motion detection and conditionally written to video file
* Stream extraction from file, motion detection and presentation as HTTP, RTSP, or RTMP (flash) streams
* Stream capture, motions detection, and quad presentation of motion detection state via HTTP, RTSP, or RTMP (flash) streams

ZMTK applications are highly threaded and this should be born in mind when devising new applications, though for the most part this implementation is hidden at the high level.

Supported distributions

2016-02-06T09:45:53Z

Stevegilvarry:

Based on either known supported versions in zmrepo, official packages and PPA

RedHat EL 6 & 7

[[Fedora]] 22 & 23

[[CentOS]] 6 & 7

[[Ubuntu]] 14.04, 15.04, 15.10

[[Debian]] 8

* TIP: for specific distro install guides, check great articles available under [[contents#Distribution-specific guides]];

Supported distributions

2016-02-06T09:44:26Z

Stevegilvarry:

Based on either known supported versions in zmrepo, official packages and PPA

[[RedHat EL]] 6 & 7

[[Fedora]] 22 & 23

[[CentOS]] 6 & 7

[[Ubuntu]] 14.04, 15.04, 15.10

[[Debian]] 8

* TIP: for specific distro install guides, check great articles available under [[contents#Distribution-specific guides]];

FAQ

2015-11-13T12:59:13Z

Stevegilvarry:

== ZoneMinder Frequently Asked Questions ==

This is the FAQ page. Feel free to contribute any FAQs that you think are missing.

===How can I stop ZoneMinder filling up my disk?===

Recent versions of ZoneMinder come with a filter you can use for this purpose already included. However '''by default it is not enabled for event deletion'''.

The filter is called ''PurgeWhenFull'' and to find it, choose one of the event counts from the console page, for instance events in the last hour, for one of your monitors.

This will bring up an event listing and a filter window.

In the filter window there is a drop down select box labeled 'Use Filter', that lets your select a saved filter. Select 'PurgeWhenFull' and it will load that filter.

Make any modifications you might want, such as the percentage full you want it to kick in, or how many events to delete at a time (it will repeat the filter as many times as needed to clear the space, but will only delete this many events each time to get there).

Then click on 'Save' which will bring up a new window. Make sure the 'Automatically delete' box is checked and press save to save your filter. This will then run in the background to keep your disk within those limits.

After you've done that, you changes will automatically be loaded into zmfilter within a few minutes.

Check the <tt>zmfilter.log</tt> file to make sure it is running as sometimes missing perl modules mean that it never runs but people don't always realize.

PURGE BY AGE

To delete events that are older than 7 days, create a new filter with "Date" set to "less than" and a value of "-7 days", sort by "date/time" in "asc"ending order, then enable the checkbox "delete all matches". You can also use a value of week or week and days: "-2 week" or "-2 week 4 day"

Save with 'Run Filter In Background' enabled to have it run automatically.

Optional skip archived events: click on the plus sign next to -7 days to add another condition. "and" "archive status" equal to "unarchived only".

Optional slow delete: limit the number of results to 3. If you have a large backlog of events that would be deleted, this can hard spike the CPU usage for a long time. Limiting the number of results to only the first three each time the filter is run spreads out the delete processes over time, dramatically lessening the CPU load.

There are two methods for ZM to remove files when they are deleted that can be found in Options under the System tab ZM_OPT_FAST_DELETE and ZM_RUN_AUDIT.

ZM_OPT_FAST_DELETE:

Normally an event created as the result of an alarm consists of entries in one or more database tables plus the various files associated with it. When deleting events in the browser it can take a long time to remove all of this if your are trying to do a lot of events at once. It is recommended that you set this option which means that the browser client only deletes the key entries in the events table, which means the events will no longer appear in the listing, and leaves the zmaudit daemon to clear up the rest later.

ZM_RUN_AUDIT:

The zmaudit daemon exists to check that the saved information in the database and on the file system match and are consistent with each other. If an error occurs or if you are using 'fast deletes' it may be that database records are deleted but files remain. In this case, and similar, zmaudit will remove redundant information to synchronize the two data stores. This option controls whether zmaudit is run in the background and performs these checks and fixes continuously. This is recommended for most systems however if you have a very large number of events the process of scanning the database and file system may take a long time and impact performance. In this case you may prefer to not have zmaudit running unconditionally and schedule occasional checks at other, more convenient, times.

ZM_AUDIT_CHECK_INTERVAL:

The zmaudit daemon exists to check that the saved information in the database and on the files system match and are consistent with each other. If an error occurs or if you are using 'fast deletes' it may be that database records are deleted but files remain. In this case, and similar, zmaudit will remove redundant information to synchronize the two data stores. The default check interval of 900 seconds (15 minutes) is fine for most systems however if you have a very large number of events the process of scanning the database and file system may take a long time and impact performance. In this case you may prefer to make this interval much larger to reduce the impact on your system. This option determines how often these checks are performed.

===What does a 'Can't shmget: Invalid argument' error in my logs mean? and my cameras won't display video at higher resolutions.===

This error is discussed in the README in the following excerpt:-
''...this is caused by an attempt to allocate an amount of shared memory greater than your system can handle. The size it requests is based on the following formula, <tt>ring buffer size x image width x image height x 3 (for 24 bit images) + a bit of overhead</tt>.

So, for example:
<pre>384x288 capture resolution, that makes: 110 592 pixels
in 24 bit color that's x24 = 2 654 208 bits per frame
by 80 frames ring buffer x80 = 212 336 640 bits per camera
by 4 cameras x4 = 849 346 560 bits.
Plus 10% overhead = 934 281 216 bits
That's 116 785 152 bytes, and
= 114 048 kB, respectively 111.38 MB.
If my shared memory is set to 134 217 728, which is exactly 128MB,
that means I shouldn't have any problem.
(Note that 1 byte = 8 bits and 1kbyte = 1024bytes, 1MB = 1024 kB)</pre>

If for instance you were using 24bit 640x480 then this would come to about 92Mb if you are using the default buffer size of 100. If this is too large then you can either reduce the image or buffer sizes or increase the maximum amount of shared memory available. If you are using RedHat then you can get details on how to change these settings at http://www.redhat.com/docs/manuals/database/RHDB-2.1-Manual/admin_user/kernel-resources.html .

You should be able to use a similar procedure with other distributions to modify the shared memory pool without kernel recompilations though in some cases this may be necessary. Note, this error also sometimes occurs if you have an old shared memory segment lying around from a previous run that is too small. Use the ipcs and ipcrm system commands to check and remove it if necessary.'"

You can often find out how many 4KB shared memory pages are available by typing the following :-
<pre># cat /proc/sys/kernel/shmall
2097152</pre>

In recent kernels the shmall is set to 2097152 memory pages multiplied by 4096 bytes per page for a total of 8 GB of shared memory available. You only need to increase the shmall value if you have a computer with more than 8GB of memory and wish to use more of it for shared memory usage, such as large databases.

The most shared memory bytes you can allocate in one go :-
<pre># cat /proc/sys/kernel/shmmax
33554432</pre>

In recent kernels the shmmax is set to 33554432 bytes for only 32 MB of maximum shared memory allocatable at a time, hardly enough for ZoneMinder to go above 320 x 240 x 24-bit resolution at 40 frames in the buffer if it is using the /dev/shm shared memory device, so this value needs to be increased. If you are using ZoneMinder with the memory mapped (mmap) compile time option then this doesn't affect you.

To change the value to 128 MB temporarily during this kernel execution type (for example) :-
<pre>echo 536870912 >/proc/sys/kernel/shmmax</pre>

'''Be sure to restart ZoneMinder after this.'''
However be aware that sometimes you will only need to change the shmmax value as shmall is often large enough. Also changing these values in this way is only effective until your machine is rebooted.

To change them permanently you will need to edit <tt>/etc/sysctl.conf</tt> and add the following lines (for example) :-
<pre>kernel.shmmax = 536870912</pre>

Or if your distribution has the <tt>/etc/sysctl.d/</tt> folder you can create a file in this folder without modifying the <tt>/etc/sysctl.d</tt> so you won't lose the changes during distro upgrades :-
<pre>echo kernel.shmmax = 536870912 >/etc/sysctl.d/60-kernel-shm.conf</pre>

To load these settings in the sysctl.conf file type:
<pre>sysctl -p</pre>

To check your shared memory settings type:
<pre>ipcs -l</pre>

Note that with Megapixel cameras like the Axis 207mw becoming cheaper and more attractive, the above memory settings are not adequate. To get Zoneminder working with a full 1280x1024 resolution camera in full color, increase <tt>134217728</tt> (128 MB) to, for example, <tt>268435456</tt> (256 MB) and multiple this value by each camera.

These changes will now also be set the next time your machine is restarted.

Versions 1.24.x of ZoneMinder also allows you to use an alternate method of shared memory allocation, [http://en.wikipedia.org/wiki/Mmap mapped memory]. This requires less configuration and can be simpler to use. Mapped memory allows you to use a special type of file as the placeholder for your memory and this file is 'mapped' into memory space for easy and fast access.

To enable mapped memory in ZoneMinder you need add add the --enable--mmap=yes switch to your configure line. By default mapped memory files are created in /dev/shm which on most distributions is a dedicated pseudo-partition containing memory formatted as a filesystem. If your system uses a different path then this can be changed in ZoneMinder in Options->paths->PATH_MAP. It uses a filesystem type called [http://en.wikipedia.org/wiki/Tmpfs tmpfs]. If you type 'df -h' you should see this area and the size of memory it currently allows. To increase size for tmpfs you need to edit /etc/default/tmpfs. Search for:
<pre>SHM_SIZE=128M</pre>
and change to something like
<pre>SHM_SIZE=1G</pre>
then reboot the system. You could possibly need to change RUN_SIZE, too.

It is important that you do not use a disk based filesystem for your memory mapped files as this will cause memory access to be extremely slow. ZoneMinder creates files called .zm.mmap.<monitor id> in the mapped memory filesystem.

Mapped memory is subject to the same limitations in terms of total memory as using more traditional shared memory but does not require any configuration per allocation or chunk. In future versions of ZoneMinder this will be the default shared memory storage method.

<div id="AlternateSharedMemory" style="width:80%; border:2px solid #8a8588; background:#faf5ff; vertical-align:top; margin-top: 6px; padding: 4px;">
Another good article about shared memory settings http://publib.boulder.ibm.com/infocenter/db2luw/v9/index.jsp?topic=/com.ibm.db2.udb.uprun.doc/doc/t0008238.htm .
It made a statement that conflicted with those in the Redhat article but they fixed a [http://www.zoneminder.com/forums/viewtopic.php?t=9692 long standing memory issue on FC6], so give them a try.

'''The essential difference was that the kernel.shmall setting is NOT in a direct memory setting in KB but in pages of memory. it is Max Pages of memory'''

'''For example:''' If you want to allocate a maximum memory setting to 8GB you have to convert it to the number of pages (or segments).
with a page size of 4096.
*kernel.shmall = 8000x1024x1024/4096
<pre>kernel.shmall = 2097152</pre>
NOT 8388608000 as would be suggested in the RedHat article linked above.

shmmax is the max amount to allocate in one request -
this is is an actual memory size (as opposed to pages) set to 4GB
<pre>kernel.shmmax = 4294967296</pre>

The <tt>/etc/sysctl.conf</tt> would have these lines
<pre>kernel.shmall = 2097152
kernel.shmmax = 4294967296</pre>

As above, reload your sysctl.conf with <tt>sysctl -p</tt> and check that the settings are correct with <tt>ipcs -l</tt>.
</div>

===I have enabled motion detection but it is not always being triggered when things happen in the camera view===

ZoneMinder uses zones to examine images for motion detection. When you create the initial zones you can choose from a number of preset values for sensitivity etc. Whilst these are usually a good starting point they are not always suitable for all situations and you will probably need to tweak the values for your specific circumstances. The meanings of the various settings are described in the documentation (http://www.zoneminder.com/wiki/index.php/Documentation#Defining_Zones) however if you believe you have sensible settings configured then there are two diagnostic approaches you can use.

====Event Statistics====
The first technique is to use event statistics. Firstly you should ensure they are switched on in Options->Logging->RECORD_EVENT_STATS. This will then cause the raw motion detection statistics for any subsequently generated events to be written to the DB. These can then be accessed by first clicking on the Frames or Alarm Frames values of the event from any event list view in the web gui. Then click on the score value to see the actual values that caused the event. Alternatively the stats can be accessed by clicking on the 'Stats' link when viewing any individual frame. The values displayed there correspond with the values that are used in the zone configuration and give you an idea of what 'real world' values are being generated.

Note that if you are investigating why events 'do not' happen then these will not be saved and so won't be accessible. The best thing to do in that circumstance is to make your zone more sensitive so that it captures all events (perhap even ones you don't want) so you can get an idea of what values are being generated and then start to adjust back to less sensitive settings if necessary. You should make sure you test your settings under a variety of lighting conditions (e.g. day and night, sunny or dull) to get the best feel for that works and what doesn't.

Using statistics will slow your system down to a small degree and use a little extra disk space in the DB so once you are happy you can switch them off again. However it is perfectly feasible to keep them permanently on if your system is able to cope which will allow you to review your setting periodically.

====Diagnostic Images====
The second approach is to use diagnostic images which are saved copies of the intermediate images that ZM uses when determining motion detection. These are switched on and off using Options->Logging->RECORD_DIAG_IMAGES.

There are two kinds of diagnostic images which are and are written (and continuously overwritten) to the top level monitor event directory. If an event occurs then the files are additionally copied to the event directory and renamed with the appropriate frame number as a prefix.

The first set are produced by the monitor on the image as a whole. The diag-r.jpg image is the current reference image against which all individual frames are compared and the diag-d.jpg image is the delta image highlighting the difference between the reference image and the last analysed image. In this images identicial pixels will be black and the more different a pixel is the whiter it will be. Viewing this image and determining the colour of the pixels is a good way of getting a feel for the pixel differences you might expect (often more than you think).

The second set of diag images are labelled as diag-<zoneid>-<stage>.jpg where zoneid is the id of the zone in question (Smile) and the stage is where in the alarm check process the image is generated from. So if you have several zones you can expect to see multiple files. Also these files are only interested in what is happening in their zone only and will ignore anything else outside of the zone. The stages that each number represents are as follows,

# Alarmed Pixels - This image shows all pixels in the zone that are considered to be alarmed as white pixels and all other pixels as black.
# Filtered Pixels - This is as stage one except that all pixels removed by the filters are now black. The white pixels represent the pixels that are candidates to generate an event.
# Raw Blobs - This image contains all alarmed pixels from stage 2 but aggrageted into blobs. Each blob will have a different greyscale value (between 1 and 254) so they can be difficult to spot with the naked eye but using a colour picker or photoshop will make it easier to see what blob is what.
# Filtered Blobs - This image is as stage 3 but under (or over) sized blobs have been removed. This is the final step before determining if an event has occurred, just prior to the number of blobs being counted. Thus this image forms the basis for determining whether an event is generated and outlining on alarmed images is done from the blobs in this image.

Using the above images you should be able to tell at all stages what ZM is doing to determine if an event should happen or not. They are useful diagnostic tools but as is mentioned elsewhere they will massively slow your system down and take up a great deal more space. You should never leave ZM running for any length of time with diagnostic images on.

===Why can't ZoneMinder capture images (either at all or just particularly fast) when I can see my camera just fine in xawtv or similar?===

With capture cards ZoneMinder will pull images as fast as it possibly can unless limited by configuration. ZoneMinder (and any similar application) uses the frame grabber interface to copy frames from video memory into user memory. This takes some time, plus if you have several inputs sharing one capture chip it has to switch between inputs between captures which further slows things down.

On average a card that can capture at 25fps per chip PAL for one input will do maybe 6-10fps for two, 1-4fps for three and 1-2 for four. For a 30fps NTSC chip the figures will be correspondingly higher. However sometimes it is necessary to slow down capture even further as after an input switch it may take a short while for the new image to settle before it can be captured without corruption.

When using xawtv etc to view the stream you are not looking at an image captured using the frame grabber but the card's video memory mapped onto your screen. This requires no capture or processing unless you do an explicit capture via the J or ctrl-J keys for instance. Some cards or drivers do not support the frame grabber interface at all so may not work with ZoneMinder even though you can view the stream in xawtv. If you can grab a still using the grab functionality of xawtv then in general your card will work with ZoneMinder.

===Why can't I see streamed images when I can see stills in the Zone window etc?===

This issue is normally down to one of two causes

1) You are using Internet Explorer and are trying to view multi-part jpeg streams. IE does not support these streams directly, unlike most other browsers. You will need to install Cambozola or another multi-part jpeg aware pluging to view them. To do this you will need to obtain the applet from the Downloads page and install the cambozola.jar file in the same directly as the ZoneMinder php files. Then find the ZoneMinder Options->Images page and enable ZM_OPT_CAMBOZOLA and enter the web path to the .jar file in ZM_PATH_CAMBOZOLA. This will ordinarily just be cambozola.jar. Provided (Options / B/W tabs) WEB_H_CAN_STREAM is set to auto and WEB_H_STREAM_METHOD is set to jpeg then Cambozola should be loaded next time you try and view a stream.

'''NOTE''': If you find that the Cambozola applet loads in IE but the applet just displays the version # of Cambozola and the author's name (as opposed to seeing the streaming images), you may need to chmod (''-rwxrwxr-x'') your (''usr/share/zoneminder/'') cambozola.jar:

$ sudo chmod 775 cambozola.jar

Once I did this, images started to stream for me.

2) The other common cause for being unable to view streams is that you have installed the ZoneMinder cgi binaries (zms and nph-zms) in a different directory than your web server is expecting. Make sure that the --with-cgidir option you use to the ZoneMinder configure script is the same as the CGI directory configure for your web server. If you are using Apache, which is the most common one, then in your httpd.conf file there should be a line like <pre>ScriptAlias /cgi-bin/ "/var/www/cgi-bin/"</pre> where the last directory in the quotes is the one you have specified. If not then change one or the other to match. Be warned that configuring apache can be complex so changing the one passed to the ZoneMinder configure (and then rebuilding and reinstalling) is recommended in the first instance. If you change the apache config you will need to restart apache for the changes to take effect. If you still cannot see stream reliably then try changing Options->Paths->ZM_PATH_ZMS to just use zms if nph-zms is specified, or vice versa. Also check in your apache error logs.

===I have several monitors configured but when I load the Montage view in FireFox why can I only see two? or, Why don't all my cameras display when I use the Montage view in FireFox?===

By default FireFox only supports a small number of simultaneous connections. Using the montage view usually requires one persistent connection for each camera plus intermittent connections for other information such as statuses.

You will need to increase the number of allowed connections to use the montage view with more than a small number of cameras. Certain FireFox extensions such as FasterFox may also help to achieve the same result.

To resolve this situation, follow the instructions below:

<pre>Enter about:config in the address bar

scroll down to
browser.cache.check_doc_frequency 3
change the 3 to a 1

browser.cache.disk.enable True -> False
network.http.max-connections-per-server -> put a value of 100
network.http.max-persistent-connections-per-proxy -> 100 again
network.http.max-persistent-connections-per-server -> 100 again
</pre>

===Why is ZoneMinder using so much CPU?===

The various elements of ZoneMinder can be involved in some pretty intensive activity, especially while analysing images for motion. However generally this should not overwhelm your machine unless it is very old or underpowered.

There are a number of specific reasons why processor loads can be high either by design or by accident. To figure out exactly what is causing it in your circumstances requires a bit of experimentation.

The main causes are.

# Using a video palette other than greyscale or RGB24. This can cause a relatively minor performace hit, though still significant. Although some cameras and cards require using planar palettes ZM currently doesn't support this format internally and each frame is converted to an RGB representation prior to processing. Unless you have compelling reasons for using YUV or reduced RGB type palettes such as hitting USB transfer limits I would experiment to see if RGB24 or greyscale is quicker. Put your monitors into 'Monitor' mode so that only the capture daemons are running and monitor the process load of these (the 'zmc' processes) using top. Try it with various palettes to see if it makes a difference.
# Big image sizes. A image of 640x480 requires at least four times the processing of a 320x240 image. Experiment with different sizes to see what effect it may have. Sometimes a large image is just two interlaced smaller frames so has no real benefit anyway. This is especially true for analog cameras/cards as image height over 320 (NTSC) or 352 PAL) are invariably interlaced.
# Capture frame rates. Unless there's a compelling reason in your case there is often little benefit in running cameras at 25fps when 5-10fps would often get you results just as good. Try changing your monitor settings to limit your cameras to lower frame rates. You can still configure ZM to ignore these limits and capture as fast as possible when motion is detected.
# Run function. Obviously running in Record or Mocord modes or in Modect with lots of events generates a lot of DB and file activity and so CPU and load will increase.
# Basic default detection zones. By default when a camera is added one detection zone is added which covers the whole image with a default set of parameters. If your camera covers a view in which various regions are unlikely to generate a valid alarm (ie the sky) then I would experiment with reducing the zone sizes or adding inactive zones to blank out areas you don't want to monitor. Additionally the actual settings of the zone themselves may not be optimal. When doing motion detection the number of changed pixels above a threshold is examined, then this is filter, then contiguous regions are calculated to see if an alarm is generated. If any maximum or minimum threshold is exceeded according to your zone settings at any time the calculation stops. If your settings always result in the calculations going through to the last stage before being failed then additional CPU time is used unnecessarily. Make sure your maximum and minimumzone thresholds are set to sensible values and experiment by switching RECORD_EVENT_STATS on and seeing what the actual values of alarmed pixels etc are during sample events.
# Optimise your settings. After you've got some settings you're happy with then switching off RECORD_EVENT_STATS will prevent the statistics being written to the database which saves some time. Other settings which might make a difference are ZM_FAST_RGB_DIFFS, ZM_OPT_FRAME_SERVER and the JPEG_xxx_QUALITY ones.

I'm sure there are other things which might make a difference such as what else you have running on the box and memory sizes (make sure there's no swapping going on). Also speed of disk etc will make some difference during event capture and also if you are watching the whole time then you may have a bunch of zms processes running also.

I think the biggest factors are image size, colour depth and capture rate. Having said that I also don't always know why you get certains results from 'top'. For instance if I have a 'zma' daemon running for a monitor that is capturing an image. I've commented out the actual analysis so all it's doing is blending the image with the previous one. In colour mode this takes ~11 milliseconds per frame on my system and the camera is capturing at ~10fps. Using 'top' this reports the process as using ~5% of CPU and permanently in R(un) state. Changing to greyscale mode the blending takes ~4msec (as you would expect as this is roughly a third of 11) but top reports the process as now with 0% CPU and permanently in S(leep) state. So an actual CPU resource usage change of a factor of 3 causes huge differences in reported CPU usage. I have yet to get to the bottom of this but I suspect it's to do with scheduling somewhere along the line and that maybe the greyscale processing will fit into one scheduling time slice whereas the colour one won't but I have no evidence of this yet!

===Why is the timeline view all messed up?===

The timeline view is a new view allowing you to see a graph of alarm activity over time and to quickly scan and home in on events of interest. However this feature is highly complex and still in beta. It is based extensively on HTML div tags, sometimes lots of them. Whilst FireFox is able to render this view successfully other browsers, particular Internet Explorer do not seem able to cope and so present a messed up view, either always or when there are a lot of events.
Using the timeline view is only recommended when using FireFox, however even then there may be issues.

This function has from time to time been corrupted in the SVN release or in the stable releases, try and reinstall from a fresh download.

===How much Hard Disk Space / Bandwidth do I need for ZM?===
Please see [http://www.jpwilson.eu/ZM_Utils/ZM%20storage%20calc%20sheet.xls Storage Calc] in excel format

Or go to [http://www.axis.com/products/video/design_tool/index.htm this link] for the Axis bandwidth calculator. Although this is aimed at Axis cameras it still produces valid results for any kind of IP camera.

As a quick guide I have 4 cameras at 320x240 storing 1 fps except during alarm events. After 1 week 60GB of space in the volume where the events are stored (/var/www/html/zm) has been used.

===When I try and run ZoneMinder I get lots of audit permission errors in the logs and it won't start===
Many Linux distributions nowadays are built with security in mind. One of the latest methods of achieving this is via SELinux (Secure Linux) which controls who is able to run what in a more precise way then traditional accounting and file based permissions ([http://en.wikipedia.org/wiki/Selinux]).
If you are seeing entries in your system log like:

Jun 11 20:44:02 kernel: audit(1150033442.443:226): avc: denied { read } for pid=5068
comm="uptime" name="utmp" dev=dm-0 ino=16908345 scontext=user_u:system_r:httpd_sys_script_t
tcontext=user_u:object_r:initrc_var_run_t tclass=file

then it is likely that your system has SELinux enabled and it is preventing ZoneMinder from performaing certain activities. You then have two choices. You can either tune SELinux to permit the required operations or you can disable SELinux entirely which will permit ZoneMinder to run unhindered. Disabling SELinux is usually performed by editing its configuration file (e.g., <tt>/etc/selinux/config</tt>) and then rebooting. However if you run a public server you should read up on the risks associated with disabled Secure Linux before disabling it.

Note that SELinux may cause errors other than those listed above. If you are in any doubt then it can be worth disabling SELinux experimentally to see if it fixes your problem before trying other solutions.

=== How do I enable ZoneMinder's security? ===
In the console, click on Options. Check the box next to "ZM_OPT_USE_AUTH". You will immediately be asked to login. The username is 'admin' and the password is 'admin'.

'''To Manage Users:''' 
In main console, go to '''Options->Users'''.

* You may also consider to use the web server security, for example, htaccess files under Apache scope; You may even use this as an additional/redundant security on top of Zoneminders built-in security features;

=== Why does ZM stop recording once I have 32000 events for my monitor? ===
Storing more than 32k files in a single folder is a limitation of some filesystems. To avoid this, enable USE_DEEP_STORAGE under Options.

USE_DEEP_STORAGE is now the default for new ZoneMinder systems so this limitation should only apply to users upgrading from a previous version of ZoneMinder.

Versions of ZM from 1.23.0 onwards allow you to have a deeper filesystem with fewer files per individual directory. As well as not being susceptible to the 32k limit, this is also somewhat faster.

If you have upgraded from a previous version of ZoneMinder and this option is not already enabled, it is very important to follow the steps below to enable it on an existing system. Failure to properly follow these steps WILL RESULT IN LOSS OF YOUR DATA!

# Stop ZoneMinder
# Backup your event data and the dB if you have the available storage
# Enable USE_DEEP_STORAGE under Options.
# From the command line, run "sudo zmupdate.pl --migrate-events"
# Monitor the output for any events that fail to convert.
# After the conversion completes, you can restart ZoneMinder

Note that you can re-run the migrate-events command if any error messages scroll off the screen.

You can read about the lack of a limit in the number of sub-directories in the ext4 filesystem at:
http://kernelnewbies.org/Ext4
and see what tools may assist in your use of this filesystem in:
http://ext4.wiki.kernel.org/index.php/Ext4_Howto
If you search for ext3 or reiserfs on the forums you will find various threads on this issue with guidance on
how to convert.

== Managing system load ''(with IP Cameras in mind)'' ==

=== Introduction ===
Zoneminder is a superb application in every way, but it does a job that needs a lot of horsepower especially when using multiple IP cameras. IP Cams require an extra level of processing to analogue cards as the jpg or mjpeg images need to be decoded before analysing. This needs grunt. If you have lots of cameras, you need lots of grunt.

Why do ZM need so much grunt?
Think what Zoneminder is actually doing. In modect mode ZM is:
1. Fetching a jpeg from the camera. (Either in single part or multipart stream)
2. Decoding the jpeg image.
3. Comparing the zoned selections to the previous image or images and applying rules.
4. If in alarm state, writing that image to the disk and updating the mysql database.

If you're capturing at five frames per second, the above is repeated five times every second, multiplied by the number of cameras. Decoding the images is what takes the real power from the processor and this is the main reason why analogue cameras which present an image ready-decoded in memory take less work.

=== How do I know if my computer is overloaded? ===
If your CPU is running at 100% all the time, it's probably overloaded (or running at exact optimisation). If the load is consistently high (over 10.0 for a single processor) then Bad Things happen - like lost frames, unrecorded events etc. Occasional peaks are fine, normal and nothing to worry about.

Zoneminder runs on Linux, Linux measures system load using "load", which is complicated but gives a rough guide on what the computer is doing at any given time. Zoneminder shows Load on the main page (top right) as well as disk space. Typing "uptime" on the command line will give a similar guide, but with three figures to give a fuller measure of what's happening over a period of time but for the best guide to see what's happening, install "htop" - which gives easy to read graphs for load, memory and cpu usage.

A load of 1.0 means the processor has "just enough to do right now". Also worth noting that a load of 4.0 means exactly the same for a quad processor machine - each number equals a single processor's workload. A very high load can be fine on a computer that has a stacked workload - such as a machine sending out bulk emails, or working its way through a knotty problem; it'll just keep churning away until it's done. However - Zoneminder needs to process information in real time so it can't afford to stack its jobs, it needs to deal with them right away.

For a better and full explanation of Load: http://en.wikipedia.org/wiki/Load_%28computing%29

=== My load is too high, how can I reduce it? ===
Zoneminder is /very/ tweakable and it's possible to tune it to compromise. The following are good things to try, in no particular order;

Change the jpeg libraries. In most distributions Linux uses standard jpeg libraries which although fine for most things, don't use the MMX functions in nearly all modern processors. Check whether your cpu supports mmx by running "cpuid |grep MMX" which should give you a line or two along the lines of "MMX instructions". If so, give the libs a try. Most people report their load halves simply by using these libs. You may be able to experience substantial Zoneminder performance boosts now by merely upgrading your operating system, without having to download libraries and compile your own binaries, etc. as described in the forum thread linked below. Some distributions, e.g. Fedora 14 now include library code to utilize the instruction set extensions available in your processor:

http://fedoraproject.org/wiki/Fedora_14_Alpha_release_notes#Faster_JPEG_Compression.2FDecompression

"The replacement of libjpeg with libjpeg-turbo brings speed improvements to a wide range of applications when handling images in JPEG format ..."

http://fedoraproject.org/wiki/Releases/14/Schedule

still states "2010-11-02 final release".

CentOS 6.4 now has libjpeg-turbo built in as the default jpeg library allowing the best results out of the box.

http://libjpeg-turbo.virtualgl.org/

provides some history on its project page. If you seek confirmation for which library is in use, you may consider querying e.g. while running on a prior distribution:
<pre>
[u@who ~]$ rpm -q --whatprovides libjpeg
libjpeg-6b-46.fc12.i686
[u@who ~]$
</pre>
and comparing the response to querying when the higher-performance library is available:
<pre>
[u@who ~]$ rpm -q --whatprovides libjpeg
libjpeg-turbo-1.0.1-1.fc14.x86_64
[u@who ~]$
</pre>
As noted in other forum postings, some zoneminder camera and usage configurations may not make much use of jpeg processing (e.g. some webcams), and thus obtain little performance benefit. Otherwise, you should be able to select one or more of:
* running more cameras,
* running existing cameras at higher image resolutions,
* running cameras at a faster frame rate,
* saving MoDect images with higher quality,
* having more CPU cycles available for any non-Zoneminder workload, etc.

http://www.zoneminder.com/forums/viewtopic.php?t=6419 gives more info on the download-the-library-yourself, compile-your-own-Zoneminder binary, etc. approach if needed. Nobody's posted there to say it broke their system... Yet.

If your camera allows you to change image size, think whether you can get away with smaller images. Smaller pics = less load. 320x240 is usually ok for close-up corridor shots.

Go Black and White. Colour pictures use twice to three times the CPU, memory and diskspace but give little benefit to identification.

Reduce frames per second. Halve the fps, halve the workload. If your camera supports fps throttling (Axis do), try that - saves ZM having to drop frames from a stream. 2-5 fps seems to be widely used.

Experiment with using jpeg instead of mjpeg. Some users have reported it gives better performance, but YMMV.

Tweak the zones. Keep them as small and as few as possible. Stick to one zone unless you really need more.

Schedule. If you are running a linux system at near capacity, you'll need to think carefully about things like backups and scheduled tasks. updatedb - the process which maintains a file database so that 'locate' works quickly, is normally scheduled to run once a day and if on a busy system can create a heavy increase on the load. The same is true for scheduled backups, especially those which compress the files. Re-schedule these tasks to a time when the cpu is less likely to be busy, if possible - and also use the "nice" command to reduce their priority. (crontab and /etc/cron.daily/ are good places to start)

Reduce clutter on your PC. Don't run X unless you really need it, the GUI is a huge overhead in both memory and cpu.

More expensive options:

Increase RAM. If your system is having to use disk swap it will HUGELY impact performance in all areas. Again, htop is a good monitor - but first you need to understand that because Linux is using all the memory, it doesn't mean it needs it all - linux handles ram very differently to Windows/DOS and caches stuff. htop will show cached ram as a different colour in the memory graph. Also check that you're actually using a high memory capable kernel - many kernels don't enable high memory by default.

Faster CPU. Simple but effective. Zoneminder also works very well with multiple processor systems out of the box (if SMP is enabled in your kernel). The load of different cameras is spread across the processors.

Try building Zoneminder with processor specific instructions that are optimised to the system it will be running on, also increasing the optimisation level of GCC beyond -O2 will help.
<pre>
./configure CFLAGS="-g -O3 -march=athlon-xp -mtune=athlon-xp" CXXFLAGS="-g -O3 -march=athlon-xp -mtune=athlon-xp"
</pre>
The above command is optimised for an Athlon XP cpu so you will need to use the specific processor tag for your cpu, also the compiler optimisation has been increased to -O3.

You also need to put in your normal ./configure commands as if you were compiling with out this optimisation.

A further note is that the compile must be performed on the system that Zoneminder will be running on as this optimisation will make it hardware specific code.

Processor specific commands can be found in the GCC manual along with some more options that may increase performanc.
<pre>
http://gcc.gnu.org/onlinedocs/gcc/i386-and-x86_002d64-Options.html#i386-and-x86_002d64-Options
</pre>

The below command has been used to compile Zoneminder on a Athlon XP system running CentOS 5.5 and along with the libjpeg-turbo modification to reduce the CPU load in half, libjpeg-turbo reduced the load by 1/3 before the processor optimisation.
<pre>
./configure --with-webdir=/var/www/html/zm --with-cgidir=/var/www/cgi-bin CFLAGS="-g -O3 -march=athlon-xp -mtune=athlon-xp" CXXFLAGS="-D__STDC_CONSTANT_MACROS -g -O3 -march=athlon-xp -mtune=athlon-xp" --enable-mmap --sysconfdir=/etc/zm
</pre>

The following command has been used to compile Zoneminder 1.25 on a CentOS 6.0 system, the native command should choose the processor automatically during compile time, this needs to be performed on the actual system!!.

<pre>
CFLAGS="-g -O3 -march=native -mtune=native" CXXFLAGS="-D__STDC_CONSTANT_MACROS -g -O3 -march=native -mtune=native" ./configure --with-webdir=/var/www/html/zm --with-cgidir=/var/www/cgi-bin --with-webuser=apache --with-webgroup=apache ZM_DB_HOST=localhost ZM_DB_NAME=zm ZM_DB_USER=your_zm_user ZM_DB_PASS=your_zm_password ZM_SSL_LIB=openssl
</pre>

=== What about disks and bandwidth? ===

In most modern pc-based servers, disk I/O is more than adequate for the speeds involved in capturing from multiple cameras in most scenarios.

A typical 100mbit LAN will cope with most setups easily. If you're feeding from cameras over smaller or internet links, obviously fps will be much lower.

Disk and Bandwidth calculators are referenced on the Zoneminder wiki here: http://www.zoneminder.com/wiki/index.php/FAQ#How_much_Hard_Disk_Space_.2F_Bandwidth_do_I_need_for_ZM.3F

== Building ZoneMinder ==

=== When running configure I am getting a lot of messages about not being able to compile the ffmpeg libraries ===

If you see output from configure that looks like this

<pre>checking libavcodec/avcodec.h usability... no
checking libavcodec/avcodec.h presence... yes
configure: WARNING: libavcodec/avcodec.h: present but cannot be compiled
configure: WARNING: libavcodec/avcodec.h: check for missing
prerequisite headers?
configure: WARNING: libavcodec/avcodec.h: see the Autoconf documentation
configure: WARNING: libavcodec/avcodec.h: section "Present But
Cannot Be Compiled"
configure: WARNING: libavcodec/avcodec.h: proceeding with the compiler's
result
configure: WARNING: ## ------------------------------------- ##
configure: WARNING: ## Report this to support@zoneminder.com ##
configure: WARNING: ## ------------------------------------- ##</pre>

then it is caused not by the ZoneMinder build system but ffmpeg itself. However there is a workaround you can use which is to add

CPPFLAGS=-D__STDC_CONSTANT_MACROS

to the ZoneMinder ./configure command which should solve the issue. However this is not a proper 'fix' as such, which can only come from the ffmpeg project itself.

=== I cannot build ZoneMinder and am getting lots of undefined C++ template errors===

This is almost certainly due to the 'ccache' package which attempts to speed up compilation by caching compiled objects. Unfortunately one of the side effects is that it breaks the GNU g++ template resolution method that ZoneMinder uses in building by prevent files getting recompiled. The simplest way around this is to remove the ccache package using your distros package manager.

=== How do I build for X10 support? ===

You do not need to rebuild ZM for X10 support. You will need to install the perl module and switch on X10 in the options, then restart. Installing the perl module is covered in the README amongst other places but in summary, do:

perl -MCPAN -eshell
install X10::ActiveHome
quit

== Extending ZoneMinder ==

=== How can I get ZM to do different things at different times of day or week? ===
If you want to configure ZoneMinder to do motion detection during the day and just record at night, for example, you will need to use ZoneMinder 'run states'. A run state is a particular configuration of monitor functions that you want to use at any time.

To save a run state you should first configure your monitors for Modect, Record, Monitor etc as you would want them during one of the times of day. Then click on the running state link at the top of the Console view. This will usually say 'Running' or 'Stopped'. You will then be able to save the current state and give it a name, 'Daytime' for example. Now configure your monitors how you would want them during other times of day and save that, for instance as 'Nighttime'.

Now you can switch between these two states by selecting them from the same dialog you saved them, or from the command line from issue the command ''zmpkg.pl <run state>'', for example ''zmpkg.pl Daytime''.

The final step you need to take, is scheduling the time the changes take effect. For this you can use [http://en.wikipedia.org/wiki/Cron cron]. A simple entry to change to the Daylight state at at 8am and to the nighttime state at 8pm would be as follows,
<pre>0 8 * * * root /usr/local/bin/zmpkg.pl Daytime
0 20 * * * root /usr/local/bin/zmpkg.pl Nighttime</pre>

On Ubuntu 7.04 and possibly others, look in /usr/bin not just /usr/local/bin for the zmpkg.pl file.

Although the example above describes changing states at different times of day, the same principle can equally be applied to days of the week or other more arbitrary periods.

For an alternative method of time controlling ZoneMinder, forum user 'voronwe' has created a more interactive calendar style integration. Details of this can be found in this [http://www.zoneminder.com/forums/viewtopic.php?t=6519 forum thread]. If you would like to find out more about this contribution please post on this thread.

=== How can I use ZoneMinder to trigger something else when there is an alarm? ===
ZoneMinder includes a perl API which means you can create a script to interact with the ZM shared memory data and use it in your own scripts to react to ZM alarms or to trigger ZM to generate new alarms. Full details are in the README or by doing 'perldoc ZoneMinder', 'perldoc ZoneMinder::SharedMem' etc.
Below is an example script that checks all monitors for alarms and when one occurs, prints a message to the screen. You can add in your own code to make this reaction a little more useful. This script will check every second and perform the action so you may want to store the last state and only perform your action on change.

<pre>#!/usr/bin/perl -w

use strict;

use ZoneMinder;

$| = 1;

my $dbh = DBI->connect( "DBI:mysql:database=".$Config{ZM_DB_NAME}.";host=".$Config{ZM_DB_HOST}, $Config{ZM_DB_USER}, $Config{ZM_DB_PASS} ) or croak( "Can't connect to db" );

my $sql = "select M.*, max(E.Id) as LastEventId from Monitors as M left join Events as E on M.Id = E.MonitorId where M.Function != 'None' group by (M.Id)";
my $sth = $dbh->prepare_cached( $sql ) or die( "Can't prepare '$sql': ".$dbh->errstr() );

my $res = $sth->execute() or die( "Can't execute '$sql': ".$sth->errstr() );
my @monitors;
while ( my $monitor = $sth->fetchrow_hashref() )
{
push( @monitors, $monitor );
}

while( 1 )
{
foreach my $monitor ( @monitors )
{
next if ( !zmMemVerify( $monitor ) );

if ( my $last_event_id = zmHasAlarmed( $monitor, $monitor->{LastEventId} ) )
{
$monitor->{LastEventId} = $last_event_id;
print( "Monitor ".$monitor->{Name}." has alarmed\n" );
#
# Do your stuff here
#
}
}
sleep( 1 );
}</pre>

==Trouble Shooting==
Here are some things that will help you track down whats wrong.
This is also how to obtain the info that we need to help you on the forums.

===What logs should I check for errors?===
ZoneMinder creates its own logs and are usually located in the <tt>/tmp</tt> directory.

The ZoneMinder logs for the RPM packages are located in <tt>/var/log/zm</tt>.

Depending on your problem errors can show up in any of these logs but, usually the logs of interest are <tt>zmdc.log</tt> and <tt>zmpkg.log</tt> if ZM is not able to start.

Now since ZM is dependent on other components to work, you might not find errors in ZM but in the other components.
Other logs of interest are:<tt>
*/var/log/messages and/or /var/log/syslog
*/var/log/dmesg
*/var/log/httpd/error_log</tt> (RedHat/Fedora) or <tt>/var/log/apache2/error_log
*/var/log/mysqld.log</tt> (Errors here don't happen very often but just in case)

If ZM is not functioning, you should always be able to find an error in at least one of these logs. Use the [[tail]] command to get info from the logs. This can be done like so:

tail -f /var/log/messages /var/log/httpd/error_log /var/log/zm/zm*.log

This will append any data entered to any of these logs to your console screen (<tt>-f</tt>). To exit, hit [ctrl -c].

More verbose logging for the ZoneMinder binaries is available by enabling the debug option from the control panel and will be placed in the path you have configured for the debug logs. Output can be limited to a specific binary as described in the Debug options page under the "?" marks.

===How can I trouble shoot the hardware and/or software?===
Here are some commands to get information about your hardware. Some commands are distribution dependent.
* <tt>[[lspci]] -vv</tt> -- Returns lots of detailed info. Check for conflicting interrupts or port assignments. You can sometimes alter interrupts/ ports in bios. Try a different pci slot to get a clue if it is HW conflict (comand provided by the pciutils package).
* <tt>[[scanpci]] -v</tt> -- Gives you information from your hardware EPROM
* <tt>[[lsusb]] -vv</tt> -- Returns lots of detail about USB devices (camand provided by usbutils package).
* <tt>[[dmesg]]</tt> -- Shows you how your hardware initialized (or didn't) on boot-up. You will get the most use of this.
* <tt>[[v4l-info]]</tt> -- to see how driver is talking to card. look for unusual values.
* <tt>[[modinfo bttv]]</tt> -- some bttv driver stats.
* <tt>[[zmu]] -m 0 -q -v</tt> -- Returns various information regarding a monitor configuration.
* <tt>[[ipcs]] </tt> -- Provides information on the ipc facilities for which the calling process has read acccess.
* <tt>[[ipcrm]] </tt> -- The ipcrm command can be used to remove an IPC object from the kernel.
* <tt>cat /proc/interrupts</tt> -- This will dispaly what interrupts your hardware is using.

===Why is it that when monitoring a camera, the top portion of the image is cutoff and appears at the bottom of the image, with a line seperating the top from the bottom?===

=== Why am I getting a 403 access error with my web browser when trying to access http //localhost/zm? ===

The apache web server needs to have the right permissions and configuration to be able to read the Zoneminder files. Check the forums for solution, and edit the apache configuration and change directory permissions to give apache the right to read the Zoneminder files. Depending on your Zoneminder configuration, you would use the zm user and group that Zoneminder was built with, such as wwwuser and www.

=== Why am I getting broken images when trying to view events? ===

Zoneminder and the Apache web server need to have the right permissions. Check this forum topic and similar ones:
http://www.zoneminder.com/forums/viewtopic.php?p=48754#48754

===Why is the image from my color camera appearing in black and white?===
If you recently upgraded to zoneminder 1.26, there is a per camera option that defaults to black and white and can be mis-set if your upgrade didn't happen right. See this thread: http://www.zoneminder.com/forums/viewtopic.php?f=30&t=21344

This may occur if you have a NTSC analog camera but have configured the source in ZoneMinder as PAL for the Device Format under the source tab. You may also be mislead because zmu can report the video port as being PAL when the camera is actually NTSC. Confirm the format of your analog camera by checking it's technical specifications, possibly found with the packaging it came in, on the manufacturers website, or even on the retail website where you purchased the camera. Change the Device Format setting to NTSC and set it to the lowest resolution of 320 x 240. If you have confirmed that the camera itself is NTSC format, but don't get a picture using the NTSC setting, consider increasing the shared memory '''kernel.shmall''' and '''kernel.shmmax''' settings in /etc/sysctl.conf to a larger value such as 268435456. This is also the reason you should start with the 320x240 resolution, so as to minimize the potential of memory problems which would interfere with your attempts to troubleshoot the device format issue. Once you have obtained a picture in the monitor using the NTSC format, then you can experiment with raising the resolution.

===Why do I only see blue screens with a timestamp when monitoring my camera?===
If this camera is attached to a capture card, then you may have selected the wrong Device Source or Channel when configuring the monitor in the ZoneMinder console. If you have a capture card with 2 D-sub style inputs(looks like a VGA port) to which you attach a provided splitter that splits off multiple cables, then the splitter may be attached to the wrong port. For example, PV-149 capture cards have two D-sub style ports labeled as DB1 and DB2, and come packaged with a connector for one of these ports that splits into 4 BNC connecters. The initial four video ports are available with the splitter attached to DB1.

===Why do I only see black screens with a timestamp when monitoring my camera?===
In the monitor windows where you see the black screen with a timestamp, select settings and enter the Brightness, Contrast, Hue, and Color settings reported for the device by '''zmu -d <device_path> -q -v'''. 32768 may be appropriate values to try for these settings. After saving the settings, select Settings again to confirm they saved successfully.

===I am getting messages about a backtrace in my logs, what do I do?===
If you are seeing entries in your log like the following
<pre>Jan 11 20:25:22 localhost zma_m2[19051]: ERR [Backtrace: /lib64/libc.so.6 [0x3347230210]]
Jan 11 20:25:22 localhost zma_m2[19051]: ERR [Backtrace: /lib64/libc.so.6(memset+0xce) [0x334727684e]]
Jan 11 20:25:22 localhost zma_m2[19051]: ERR [Backtrace: /usr/local/bin/zma [0x40ee9a]]
Jan 11 20:25:22 localhost zma_m2[19051]: ERR [Backtrace: /usr/local/bin/zma [0x419946]]
Jan 11 20:25:22 localhost zma_m2[19051]: ERR [Backtrace: /usr/local/bin/zma [0x4213cf]]
Jan 11 20:25:22 localhost zma_m2[19051]: ERR [Backtrace: /usr/local/bin/zma(cos+0x35c) [0x404674]]
Jan 11 20:25:22 localhost zma_m2[19051]: ERR [Backtrace: /lib64/libc.so.6(__libc_start_main+0xf4) [0x334721da44]]
Jan 11 20:25:22 localhost zma_m2[19051]: ERR [Backtrace: /usr/local/bin/zma(cos+0xd1) [0x4043e9]]
Jan 11 20:25:22 localhost zma_m2[19051]: INF [Backtrace complete]</pre>
then you can help diagnose the problem by running a special command to translate the hex addresses into helpful information. This command is called addr2line and you can type 'man addr2line' for more information.
Basically addr2line takes two sets of parameters, the first is the name of the binary file, and the second is a list of addresses. Both of these pieces of information are displayed in the logs. The filename is the first part after the 'Backtrace:' tag, in this case /usr/local/bin/zma, though it may well be different in your case. Some of the lines refer to libraries rather than the zma executable but those can be ignored for now, the important part is noting which ZM binary is involved. The binary file is passed in following the -e flag. The addresses to pass to addr2line are those contained in the '[]' pairs. Again you can ignore those that are on a line that refers to a library but it will not hurt if you include them.
So in the example above, the command would be <pre>addr2line -e /usr/local/bin/zma 0x40ee9a 0x419946 0x4213cf 0x404674 0x4043e9</pre>
This should then dump out a more symbolic list containing source file names and line numbers, and it is this information which will be helpful if posted to the forums. Sometimes addr2line fails to produce useful output. This is usually because either the problem is so severe that it has corrupted the stack and prevented useful information from being displayed, or that you have either compiled ZM without the -g flag for debug, or you have stripped the binaries of symbol information after installation. This this case you would need to rebuild temporarily with debug enabled for the information to be useful.

This error some times happens when a linked camera looses its link or it is corrupted by the user or some other system event, try deleting the affected cameras and recreating them in the Zoneminder console.

===How do I repair the MySQL Database?===
There is two ways to go about this. In most cases you can run from the command prompt ->
* mysqlcheck --all-databases --auto-repair -p'''your_database_password''' -u '''your_databse_user'''

If that does not work then you will have to make sure that ZoneMinder is stopped then run the following (nothing should be using the database while running this and you will have to adjust for your correct path if it is different). ->
* myisamchk --silent --force --fast --update-state -O key_buffer=64M -O sort_buffer=64M -O read_buffer=1M -O write_buffer=1M /var/lib/mysql/*/*.MYI

===How do I repair the MySQL Database when the cli fails?===
In Ubuntu, the commands listed above do not seem to work. However, actually doing it by hand from within MySQL does. (But that is beyond the scope of this document) But that got me thinking... And phpmyadmin does work. Bring up a terminal.
sudo apt-get install phpmyadmin

Now go to http://zoneminder_IP/ and stop the ZM service. Continue to http://zoneminder_IP/phpmyadmin and select the zoneminder database. Select and tables marked 'in use' and pick the action 'repare' to fix. Restart the zoneminder service from the web browser. Remove or disable the phpmyadmin tool, as it is not always the most secure thing around, and opens your database wide to any skilled hacker.
sudo apt-get remove phpmyadmin

===I upgraded by distribution and ZM stopped working===
Some possibilties (Incomplete list and subject to correction)
#[[/usr/local/bin/zmfix: /usr/lib/libmysqlclient.so.15: version `MYSQL_5.0' not found (required by /usr/local/bin/zmfix)]] :: Solution: Recompile and reinstall Zoneminder.
Any time you update a major version that ZoneMinder depends on, you need to recompile ZoneMinder.

===Zoneminder doesn't start automatically on boot===
Check the list for log entries like "zmfix[766]: ERR [Can't connect to server: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)] ".
What can happen is that zoneminder is started too quickly after Mysql and tries to contact the database server before it's ready. Zoneminder gets no answer and aborts.
August 2010 - Ubuntu upgrades seem to be leaving several systems in this state. One way around this is to add a delay to the zoneminder startup script allowing Mysql to finish starting.
"Simply adding 'sleep 15' in the line above 'zmfix -a' in the /etc/init.d/zoneminder file fixed my ZoneMinder startup problems!" - credit to Pada.

=== Remote Path setup for Panasonic and other Camera ===
On adding or editing the source you can select the preset link for the parameters for the specified camera . In version 1.23.3 presets for BTTV,Axis,Panasonic,GadSpot,VEO, and BlueNet are available . Selecting the presets ZM fills up the required value for the remote path variable

=== Why do I get repeated/ mixed/unstable/ blank monitors on bt878-like cards (a.k.a. PICO 2000) ===

Please have a check at [[Pico2000]];

===What causes "Invalid JPEG file structure: two SOI markers" from zmc (1.24.x)===

Some settings that used to be global only are now per camera. On the Monitor Source tab, if you are using Remote Protocol "HTTP" and Remote Method "Simple", try changing Remote Method to "Regexp".

== Miscellaneous ==
=== I see ZoneMinder is licensed under the GPL. What does that allow or restrict me in doing with ZoneMinder? ===

The ZoneMinder license is described at the end of the documentation and consists of the following section

This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as
published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty
of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

This means that ZoneMinder is licensed under the terms described [http://www.gnu.org/copyleft/gpl.html here]. There is a comprehensive FAQ covering the GPL at http://www.gnu.org/licenses/gpl-faq.html but in essence you are allowed to redistribute or modify GPL licensed software provided that you release your distribution or modifications freely under the same terms. You are allowed to sell systems based on GPL software. You are not allowed to restrict or reduce the rights of GPL software in your distribution however. Of course if you are just making modifications for your system locally you are not releasing changes so you have no obligations in this case. I recommend reading the GPL FAQ for more in-depth coverage of this issue.

=== Can I use ZoneMinder as part of my commercial product? ===

The GPL license allows you produce systems based on GPL software provided your systems also adhere to that license and any modifications you make are also released under the same terms. The GPL does not permit you to include ZoneMinder in proprietary systems (see http://www.gnu.org/licenses/gpl-faq.html#GPLInProprietarySystem for details). If you wish to include ZoneMinder in this kind of system then you will need to license ZoneMinder under different terms. This is sometimes possible and you will need to contact me for further details in these circumstances.