ZoneMinder Wiki - User contributions [en]

Trendnet

2011-09-17T20:25:00Z

Piggles: added TV-IP201W

= TV-IP100 =
Trendnet TV-IP100 works ok.
http://x.x.x.x/video.cgi

= TV-IP100W-N =
great little wireless camera with digital zoom

Remote Protocol: HTTP
Remote Method: Simple
Remote Host Name: user:pass@x.x.x.x (admin:admin is the default user/pass)
Remote Host Port: 80
Remote Host Path: /MJPEG.CGI

=TV-IP110 & TV-IP110W=

Remote Protocol: HTTP
Remote Method: Simple
Remote Host Name: <username>:<password>@x.x.x.x
Remote host Port: 80
Remote Host Path: /cgi/mjpg/mjpg.cgi
Remote Image Colors: 24 bit color
Capture Width: 640
Capture Height: 480

The capture height and width can be changed using the camera's web interface by modifying the "Video Quality" setting.
VGA = 640 x 480
QVGA = 320 x 240
QQVGA = 160 x 120

= TV-IP201P and TV-IP201W =
Remote Protocol: HTTP
Remote Method: Simple
Remote Host Name: user:pass@x.x.x.x (admin:admin is the default user/pass and 192.168.0.30 is the default IP)
Remote Host Port: 80
Remote Host Path: /goform/capture

= TV-IP252P =
Remote Protocol: HTTP
Remote Method: Simple
Remote Host Name: user:pass@x.x.x.x (admin:admin is the default)
Remote Host Port: 80
Remote Host Path: cgi/mjpg/mjpg.cgi

= TV-IP300 =
Just remember to turn 1.0 in ZM_HTTP_VERSION in the Options > Network tab. In the x.x.x.x/cgi-bin/video.jpg gives 352 x 240 jpg.

= TV-IP301 =
This camera sends the wrong mime/type and is not compatible with ZoneMinder natively but can be made to work.

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

= TV-IP400 / TV-IP400W =
These are cheap but fun Pan Tilt Zoom IP cameras and are now also supported by ZoneMinder.

New Driver and instructions for ZM 1.23.x :
http://www.sfpeter.com/2008/07/31/new-trendnet-tv-ip400w-controller-for-zoneminder-123x/

Older Driver and instructions for 1.22.x:
http://www.sfpeter.com/2007/08/14/controlling-the-trendnet-tv-ip400w-camera-with-zoneminder/
The above link is missing the "Move" tab when creating the control. You need to select "Can Move", "Can Move Diagonally" and "Can Move Relative".

= TV-IP501P =
This camera works just like the IP400 without the PTZ contols.

Remote Protocol: HTTP
Remote Method: Simple
Remote Host Name: user:pass@x.x.x.x (admin:admin is the default user/pass)
Remote Host Port: 80
Remote Host Path: /MJPEG.CGI

= TV-IP501W =

the Trendnet IP501W works. Here are the settings

Source Type: Remote

Remote Protocol: HTTP

Remote Method: Simple

Remote Host Name: username:password@IP-address

Remote Host Port: 80

Remote Path: /video.cgi

=TV-IP512P=

[[Image:TV-IP512P.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 a single jpeg frame)

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)

RTSP works with ffmpeg as above pulling 30fps when camera set to 30fps for that Profile.

Alternatively, the monitor can be configured:

Source Type: Remote
Remote Protocol: RTSP
Remote Method: RTP/Unicast
Remote Host Name: user:pass@<IP Address of Camera>
Remote Host Port: 554
Remote Host Path: /play1.sdp

When using the above ffmpeg RTSP and camera is set to Night Mode using the 30fps setting fps drop to 15fps in the dark as per the warning that this may happen at low light levels.

=TV-IP512WN=
The TV-IP512WN is pretty much the same device as TV-IP512P. It features an additional WLAN interface and can be used with the same settings as the [[Trendnet#TV-IP512P|TV-IP512P]].

=TV-IP522P=
Warning: even though this is a 'MegaPixel' camera, it has a very wide-angle lens so the image detail isn't very high. Furthermore, replacement 1/2" lenses seem to be hard to find.

ZM configuration is similar to TV-IP512P (above) except the 522 has multiple video profiles, which should be specified as

Remote Host Path: /video/mjpg.cgi?profileid=1

(1, 2, or 3, depending on the desired profile)

Also be sure to set Capture Width and Capture Height appropriately.

MPEG and RTSP were not tested but the camera does support them.[http://www.blognesian.com/ ]

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

Debian Squeeze

2011-09-17T20:20:48Z

Piggles:

==Zoneminder on Debian Squeeze==
Installation of Zoneminder on an Squeeze System

The installation on an Debian system is very easy, because the complete zoneminder software is packaged for all Debian platforms. The current version in Squeeze for Zoneminder is 1.24.2.

===Preparations===
If you will not use USB or IP cameras please be sure the capture card is working well. First be sure the card supported by the kernel. You can test this with a simple <code>lspci -v</code> with root privileges. Every channel will be shown as a seperate entry. Look for something similar '''...SAA71xx...'''.<br/>
Take also a look at the used kernel modul.

...
04:08.0 Multimedia controller: '''Philips Semiconductors SAA7130 Video Broadcast Decoder''' (rev 01)
Subsystem: Philips Semiconductors Behold TV 401
Flags: bus master, medium devsel, latency 32, IRQ 20
Memory at fdcff000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [40] Power Management version 1
'''Kernel driver''' in use: '''saa7134'''

04:09.0 Multimedia controller: '''Philips Semiconductors SAA7130 Video Broadcast Decoder''' (rev 01)
Subsystem: Philips Semiconductors Behold TV 401
Flags: bus master, medium devsel, latency 32, IRQ 19
Memory at fdcfe000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [40] Power Management version 1
'''Kernel driver''' in use: '''saa7134'''

04:0a.0 Multimedia controller: '''Philips Semiconductors SAA7130 Video Broadcast Decoder''' (rev 01))
Subsystem: Philips Semiconductors Behold TV 401
Flags: bus master, medium devsel, latency 32, IRQ 18
Memory at fdcfd000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [40] Power Management version 1
'''Kernel driver''' in use: '''saa7134'''

04:0b.0 Multimedia controller: '''Philips Semiconductors SAA7130 Video Broadcast Decoder''' (rev 01)
Subsystem: Philips Semiconductors Behold TV 401
Flags: bus master, medium devsel, latency 32, IRQ 16
Memory at fdcfc000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [40] Power Management version 1
'''Kernel driver''' in use: '''saa7134'''

04:0c.0 Multimedia controller: '''Philips Semiconductors SAA7130 Video Broadcast Decoder''' (rev 01)
Subsystem: Philips Semiconductors Behold TV 401
Flags: bus master, medium devsel, latency 32, IRQ 20
Memory at fdcfb000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [40] Power Management version 1
'''Kernel driver''' in use: '''saa7134'''

04:0d.0 Multimedia controller: '''Philips Semiconductors SAA7130 Video Broadcast Decoder''' (rev 01)
Subsystem: Philips Semiconductors Behold TV 401
Flags: bus master, medium devsel, latency 32, IRQ 19
Memory at fdcfa000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [40] Power Management version 1
'''Kernel driver''' in use: '''saa7134'''

04:0e.0 Multimedia controller: '''Philips Semiconductors SAA7130 Video Broadcast Decoder''' (rev 01)
Subsystem: Philips Semiconductors Behold TV 401
Flags: bus master, medium devsel, latency 32, IRQ 18
Memory at fdcf9000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [40] Power Management version 1
'''Kernel driver''' in use: '''saa7134'''

04:0f.0 Multimedia controller: '''Philips Semiconductors SAA7130 Video Broadcast Decoder''' (rev 01)
Subsystem: Philips Semiconductors Behold TV 401
Flags: bus master, medium devsel, latency 32, IRQ 16
Memory at fdcf8000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [40] Power Management version 1
'''Kernel driver''' in use: '''saa7134'''
...

As you can see there are 8 channels. We will find them (hopefully :-) )in the devfs filesystem.
ls -ls /dev/video*
0 crw-rw----+ 1 root video 81, 0 30. Jul 15:18 /dev/video0
0 crw-rw----+ 1 root video 81, 2 30. Jul 15:18 /dev/video1
0 crw-rw----+ 1 root video 81, 4 30. Jul 15:43 /dev/video2
0 crw-rw----+ 1 root video 81, 6 30. Jul 15:43 /dev/video3
0 crw-rw----+ 1 root video 81, 8 30. Jul 15:17 /dev/video4
0 crw-rw----+ 1 root video 81, 10 30. Jul 15:17 /dev/video5
0 crw-rw----+ 1 root video 81, 12 30. Jul 15:17 /dev/video6
0 crw-rw----+ 1 root video 81, 14 30. Jul 15:17 /dev/video7
That looks not bad, but there will be problems later. We see every entry is owend by the user 'root' und the group 'video'. But zoneminder will run with www-data rights, so with this constellation zoneminder can't access the devfs entrys. So the easiest way ist to used a special udev rule that changed the ownership of the dev entrys. Let's create this rule. Create a file <code>/etc/udev/rules.d/90-zoneminder.rules</code>.
vi /etc/udev/rules.d/90-zoneminder.rules
and put the following stuff into, this will set the mode of the /dev/video* files to 0666
# allow non-privileged users to access the /dev/video* files
SUBSYSTEM!="video4linux", GOTO="zm_rules_end"
SUBSYSTEM=="video4linux", MODE="0666", GROUP="video"
LABEL="zm_rules_end"
After reloading the udev rules the entrys will look like this:
ls -ls /dev/video*
0 crw-rw-rw-+ 1 root video 81, 0 30. Jul 15:18 /dev/video0
0 crw-rw-rw-+ 1 root video 81, 2 30. Jul 15:18 /dev/video1
0 crw-rw-rw-+ 1 root video 81, 4 30. Jul 15:43 /dev/video2
0 crw-rw-rw-+ 1 root video 81, 6 30. Jul 15:43 /dev/video3
0 crw-rw-rw-+ 1 root video 81, 8 30. Jul 15:17 /dev/video4
0 crw-rw-rw-+ 1 root video 81, 10 30. Jul 15:17 /dev/video5
0 crw-rw-rw-+ 1 root video 81, 12 30. Jul 15:17 /dev/video6
0 crw-rw-rw-+ 1 root video 81, 14 30. Jul 15:17 /dev/video7

===Installation===
The installation is really simple, just type <code>apt-get install zoneminder</code> with root privileges.

That's all. Now you have to setup your zoneminder under <nowiki>http://localhost/zm</nowiki> .

===Other Issues===
====No Link to Webserver directories====
If you get a 404 error when browsing to '''<nowiki>http://localhost/zm</nowiki>''', Zoneminder has failed to setup a correct link to the Apache2 web directories. This can be fixed via (must be root):
$ln -s /usr/share/zoneminder /var/www/zm

====Inadequate Memory Allocation====
On my P Series Lifebook, Zoneminder would install, but image capture from a remote camera wouldn't work. The problem was an inability to allocate enough shared memory, and was could be seen by examining /var/syslog:
$tail /var/syslog
zmc_m2[22910]: INF [Starting Capture]
zmc_m2[22910]: ERR [Invalid response status 401: Unauthorized]
zmc_m2[22910]: ERR [Unable to get response]
zmc_m2[22910]: ERR [Failed to capture image from monitor 2 (0/1)]
zmdc[22798]: ERR ['zmc -m 2' exited abnormally, exit status 255]
zmwatch[22830]: ERR [Can't get shared memory id '7a6d0002', 2: No such file or directory]
zmwatch[22830]: ERR [Can't get shared memory id '7a6d0002', 2: No such file or directory]

The solution was to increase the amount of memory allocated to the kernel:
Open the file “/etc/sysctl.conf”, and paste these lines at the bottom of the file, then reboot.
# Increase the maximum shared memory
kernel.shmall = 167772160
kernel.shmmax = 167772160

If you want to see if this fix works, you can temporarily allocate more memory (must login as root) by doing the following:
$echo 167772160 >/proc/sys/kernel/shmall
$echo 167772160 >/proc/sys/kernel/shmmax

Debian Squeeze

2011-09-17T20:16:38Z

Piggles: noted fix for apache ZM link issue, and memory allocation problem

==Zoneminder on Debian Squeeze==
Installation of Zoneminder on an Squeeze System

The installation on an Debian system is very easy, because the complete zoneminder software is packaged for all Debian platforms. The current version in Squeeze for Zoneminder is 1.24.2.

===Preparations===
If you will not use USB or IP cameras please be sure the capture card is working well. First be sure the card supported by the kernel. You can test this with a simple <code>lspci -v</code> with root privileges. Every channel will be shown as a seperate entry. Look for something similar '''...SAA71xx...'''.<br/>
Take also a look at the used kernel modul.

...
04:08.0 Multimedia controller: '''Philips Semiconductors SAA7130 Video Broadcast Decoder''' (rev 01)
Subsystem: Philips Semiconductors Behold TV 401
Flags: bus master, medium devsel, latency 32, IRQ 20
Memory at fdcff000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [40] Power Management version 1
'''Kernel driver''' in use: '''saa7134'''

04:09.0 Multimedia controller: '''Philips Semiconductors SAA7130 Video Broadcast Decoder''' (rev 01)
Subsystem: Philips Semiconductors Behold TV 401
Flags: bus master, medium devsel, latency 32, IRQ 19
Memory at fdcfe000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [40] Power Management version 1
'''Kernel driver''' in use: '''saa7134'''

04:0a.0 Multimedia controller: '''Philips Semiconductors SAA7130 Video Broadcast Decoder''' (rev 01))
Subsystem: Philips Semiconductors Behold TV 401
Flags: bus master, medium devsel, latency 32, IRQ 18
Memory at fdcfd000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [40] Power Management version 1
'''Kernel driver''' in use: '''saa7134'''

04:0b.0 Multimedia controller: '''Philips Semiconductors SAA7130 Video Broadcast Decoder''' (rev 01)
Subsystem: Philips Semiconductors Behold TV 401
Flags: bus master, medium devsel, latency 32, IRQ 16
Memory at fdcfc000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [40] Power Management version 1
'''Kernel driver''' in use: '''saa7134'''

04:0c.0 Multimedia controller: '''Philips Semiconductors SAA7130 Video Broadcast Decoder''' (rev 01)
Subsystem: Philips Semiconductors Behold TV 401
Flags: bus master, medium devsel, latency 32, IRQ 20
Memory at fdcfb000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [40] Power Management version 1
'''Kernel driver''' in use: '''saa7134'''

04:0d.0 Multimedia controller: '''Philips Semiconductors SAA7130 Video Broadcast Decoder''' (rev 01)
Subsystem: Philips Semiconductors Behold TV 401
Flags: bus master, medium devsel, latency 32, IRQ 19
Memory at fdcfa000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [40] Power Management version 1
'''Kernel driver''' in use: '''saa7134'''

04:0e.0 Multimedia controller: '''Philips Semiconductors SAA7130 Video Broadcast Decoder''' (rev 01)
Subsystem: Philips Semiconductors Behold TV 401
Flags: bus master, medium devsel, latency 32, IRQ 18
Memory at fdcf9000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [40] Power Management version 1
'''Kernel driver''' in use: '''saa7134'''

04:0f.0 Multimedia controller: '''Philips Semiconductors SAA7130 Video Broadcast Decoder''' (rev 01)
Subsystem: Philips Semiconductors Behold TV 401
Flags: bus master, medium devsel, latency 32, IRQ 16
Memory at fdcf8000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [40] Power Management version 1
'''Kernel driver''' in use: '''saa7134'''
...

As you can see there are 8 channels. We will find them (hopefully :-) )in the devfs filesystem.
ls -ls /dev/video*
0 crw-rw----+ 1 root video 81, 0 30. Jul 15:18 /dev/video0
0 crw-rw----+ 1 root video 81, 2 30. Jul 15:18 /dev/video1
0 crw-rw----+ 1 root video 81, 4 30. Jul 15:43 /dev/video2
0 crw-rw----+ 1 root video 81, 6 30. Jul 15:43 /dev/video3
0 crw-rw----+ 1 root video 81, 8 30. Jul 15:17 /dev/video4
0 crw-rw----+ 1 root video 81, 10 30. Jul 15:17 /dev/video5
0 crw-rw----+ 1 root video 81, 12 30. Jul 15:17 /dev/video6
0 crw-rw----+ 1 root video 81, 14 30. Jul 15:17 /dev/video7
That looks not bad, but there will be problems later. We see every entry is owend by the user 'root' und the group 'video'. But zoneminder will run with www-data rights, so with this constellation zoneminder can't access the devfs entrys. So the easiest way ist to used a special udev rule that changed the ownership of the dev entrys. Let's create this rule. Create a file <code>/etc/udev/rules.d/90-zoneminder.rules</code>.
vi /etc/udev/rules.d/90-zoneminder.rules
and put the following stuff into, this will set the mode of the /dev/video* files to 0666
# allow non-privileged users to access the /dev/video* files
SUBSYSTEM!="video4linux", GOTO="zm_rules_end"
SUBSYSTEM=="video4linux", MODE="0666", GROUP="video"
LABEL="zm_rules_end"
After reloading the udev rules the entrys will look like this:
ls -ls /dev/video*
0 crw-rw-rw-+ 1 root video 81, 0 30. Jul 15:18 /dev/video0
0 crw-rw-rw-+ 1 root video 81, 2 30. Jul 15:18 /dev/video1
0 crw-rw-rw-+ 1 root video 81, 4 30. Jul 15:43 /dev/video2
0 crw-rw-rw-+ 1 root video 81, 6 30. Jul 15:43 /dev/video3
0 crw-rw-rw-+ 1 root video 81, 8 30. Jul 15:17 /dev/video4
0 crw-rw-rw-+ 1 root video 81, 10 30. Jul 15:17 /dev/video5
0 crw-rw-rw-+ 1 root video 81, 12 30. Jul 15:17 /dev/video6
0 crw-rw-rw-+ 1 root video 81, 14 30. Jul 15:17 /dev/video7

===Installation===
The installation is really simple, just type <code>apt-get install zoneminder</code> with root privileges.

That's all. Now you have to setup your zoneminder under <nowiki>http://localhost/zm</nowiki> .

===Other Issues===
====No Link to Webserver directories====
Zoneminder failed to setup a correct link to the Apache2 web directories. This can be fixed via:
ln -s /usr/share/zoneminder /var/www/zm

====Inadequate Memory Allocation====
On my P Series Lifebook, Zoneminder would install, but image capture from a remote camera wouldn't work. The problem was an inability to allocate enough shared memory, and was could be seen by examining /var/syslog:
$tail /var/syslog
zmc_m2[22910]: INF [Starting Capture]
zmc_m2[22910]: ERR [Invalid response status 401: Unauthorized]
zmc_m2[22910]: ERR [Unable to get response]
zmc_m2[22910]: ERR [Failed to capture image from monitor 2 (0/1)]
zmdc[22798]: ERR ['zmc -m 2' exited abnormally, exit status 255]
zmwatch[22830]: ERR [Can't get shared memory id '7a6d0002', 2: No such file or directory]
zmwatch[22830]: ERR [Can't get shared memory id '7a6d0002', 2: No such file or directory]

The solution was to increase the amount of memory allocated to the kernel:
Open the file “/etc/sysctl.conf”, and paste these lines at the bottom of the file, then reboot.
# Increase the maximum shared memory
kernel.shmall = 167772160
kernel.shmmax = 167772160

If you want to see if this fix works, you can temporarily allocate more memory (must login as root) by doing the following:
$echo 167772160 >/proc/sys/kernel/shmall
$echo 167772160 >/proc/sys/kernel/shmmax