Difference between revisions of "Dedicated SBC Camera Monitor"

From ZoneMinder Wiki
Jump to navigationJump to search
 
(46 intermediate revisions by 2 users not shown)
Line 1: Line 1:
A guide to setup an SBC (Beaglebone black) or Desktop that will monitor a video feed from ZM. Simply add power, and the video feed will appear on boot.  
This is a guide for setting up a dedicated computer (core 2 duo or newer) or SBC (RPI recommended) to view all streams at once. I run this with about 28 streams with live montage of some reasonable slow but usable FPS on a mid-late 2000's used desktop. RPI's would probably only be able to run less streams, maybe 10-15.


OS will be Devuan Jessie, WM will be dwm, terminal st, and browser will be surf. It will be a minimal installation. Leaner than LXDE, the default DE for beaglebone.


I'll include optional steps to setup Device Trees and the I2C peripheral (Beaglebone specific) and read a sensor. Combine with [[ZMTrigger]].
This page is a WIP. It was tested on Debian 8/9. This guide has some other tips in [[Dedicated_RPI_Camera_Monitor]] and [[Desktop_SBC_Camera_Monitor]]. These pages will be incorporated into one page as time permits. There are other ways to do this. You can also have ZMNinja on a dedicated client per http://zoneminder.blogspot.com/p/odroid.html
 
This is noticeably more difficult than connecting a coaxial cable to a CRT such that an analog, older setup would have. But is more flexible. A desktop is generally recommended here, but SBC's can be used as well.
 
After you setup this OS once, it's advisable to copy to an img and then deploy on as many machines as necessary. A good size for the single OS root partition might be 4GB.
 
''Tested in 03/2017 on a Desktop and Beaglebone with Devuan Jessie''
 
Note that in the end, due to faulty video display, I ended up using an old laptop instead. A BBB is able to handle one stream, but seemed to have a bug in the final deployment.
 
Update: 08/2018 Tested with Rpi3 and Debian Stretch migrated to Devuan Ascii here [[Dedicated_RPI_Camera_Monitor]]
 
Another companion to this guide is the [[Desktop_SBC_Camera_Monitor]]
 
11/2018: See also [http://zoneminder.blogspot.com/p/odroid.html Zoneminder Blogspot - ODroid XU4 Zoneminder Client] guide.
== Setup ==
== Setup ==
=== Installation ===
=== Installation ===


'''Requirements'''
'''Requirements'''
* At least 4GB SD
* >8GB HDD / SD
* SBC / Desktop / Laptop
* SBC (RPI4 or equivalent) / old pc (core 2 duo or newer)
* Internet connection
* Internet connection
* Computer monitor
* Computer monitor
* HDMI cable for BBB (I use a HDMI to DVI adaptor)


Install Beaglebone Black Debian Jessie using elinux.com's [http://elinux.org/BeagleBoardDebian BeagleBoardDebian] page.
This guide used to cover install steps for a BBB, but that will be kept in the history. This guide will now just cover general desktop setup steps.


Use the direct image (under Demo, below NetInstall). Not the netinstall, which is slower, unless you know what you are doing.
=== OS ===
Install debian without X/Wayland. Install only SSH and the file system utilities from the ISO wizard.


After booting from the SD card, make sure the network interface is set to load in:
Install dwm from scratch or from the repos (scratch is easier for editing the config file).
<pre>
apt-get install firefox-esr
nano /etc/network/interfaces
</pre>


Next, migrate to Devuan using [https://git.devuan.org/dev1fanboy/Upgrade-Install-Devuan/wikis/Upgrade-to-Devuan  Dev1fanboy Upgrade-Install-Devuan wiki guide]. Skip most of the part about the display environment. Reboot after apt-get dist-upgrade. Try the purge of libsystemd0 in DE section, if you like. May not work. RCN repo seems to want it.
=== Auto Start Computer ===


The first thing we want to do, is get it so the computer will start without user interaction.


Complete the following commands
Edit .xinitrc, /etc/rc.local, /etc/inittab, and .bash_profile to auto startx without requiring a login, load the browser (firefox, chromium, or surf) with the path of the zm server monitor feed, and disable the screensaver.
<pre> su root</pre>
Remove non-free from /etc/apt/sources
<pre> nano /etc/apt/sources.list</pre>
<pre> apt-get install xorg libx11-dev libxft-dev libxinerama-dev gcc make htop sudo tcpdump git</pre>
For Surf
<pre> apt-get install libwebkitgtk-dev libgtk2.0-dev linux-headers-$(uname -r)</pre>
Download simple programs
<pre> git clone http://git.suckless.org/dwm && git clone git://git.suckless.org/st && git clone git://git.suckless.org/surf</pre>
Edit the config for dwm
<pre> nano dwm/config.def.h</pre>
* Later Disable the bar
* Later Remove all workspaces except for 1 (*tags)
* Set Mod4Mask as modkey (redmond key)
* Set MODKEY|Shiftmask to 0 and XK_c to XK_F12 for killclient (personal preference)
* Later disable spawm of dmenucmd and termcmd, but for now leave enabled.


<pre>
cd dwm
make
make install
cd ../st
nano config.def.h
</pre>
* Set termname[] to xterm (resolves some issues with programs that don't understand default termname).
<pre>
make
make install
cd ../surf
nano config.def.h
</pre>
* Review options
* Later set runinfullscreen to TRUE
* Later set kioskmode to TRUE once debugging is over
<pre>
make
make install
</pre>


=== Cleanup ===
Added to /etc/inittab (comment out existing, and add this below. Replace username with your new user):
<pre>apt-get remove nfs-common rpcbind wpasupplicant avahi-daemon ofono apache2</pre>
1:2345:respawn:/bin/login -f USERNAME tty1 </dev/tty1 >/dev/tty1 2>&1
Leave wpasupplicant if you use wifi.
Net installer may want to install acpid. Beware of removing cron. Just disable the service. Remove Exim4 if you want.


At this point maybe 40MB RAM, and <5% CPU. Compare to LXDE.


==== Clock ====
Copy /etc/profile to user that will be auto logging in:
Only needed if you are keeping time.
cp /etc/profile /home/USERNAME/.bash_profile
<pre># apt-get install ntpdate</pre>
Set cron to run ntpdate periodically
<pre>
nano /etc/crontab
*/5 * * * * root /usr/sbin/ntpdate pool.ntp.org
</pre>
This is leaner than running ntpd 24/7
 
=== Auto Start ===
 
Edit .xinitrc, /etc/rc.local, /etc/inittab, and .bash_profile to auto startx without requiring a login, load surf with the path of the zm server monitor feed, and disable the screensaver.
 
 
Added to /etc/inittab (comment out existing, and add this below. Replace username with your new user):
<pre>
1:2345:respawn:/bin/login -f USERNAME tty1 </dev/tty1 >/dev/tty1 2>&1
</pre>


Copy /etc/profile to user that will be auto logging in:
<pre>
cp /etc/profile /home/USERNAME/.bash_profile
</pre>


Appended to /home/USERNAME/.bash_profile :
Appended to /home/USERNAME/.bash_profile :
<pre>
exec startx
exec startx
</pre>


==== Browsers ====
When startx loads, it will pull settings from ~/.xinitrc for USERNAME so edit that (note that .xinitrc requires '''&''' after all commands that are not the final wm).
When startx loads, it will pull settings from ~/.xinitrc for USERNAME so edit that (note that .xinitrc requires '''&''' after all commands that are not the final wm).
<pre>
#!/bin/bash
/usr/local/bin/surf "localhost/zm/cgi-bin/nph-zms??mode=jpeg&monitor=1&scale=100&maxfps=5&buffer=1000&user=user&pass=pass" &
exec dwm
</pre>


#!/bin/bash
/usr/local/bin/surf "localhost/zm/cgi-bin/nph-zms??mode=jpeg&monitor=1&scale=100&maxfps=5&buffer=1000&user=user&pass=pass" &
exec dwm
or firefox might look something like:
#!/bin/bash
/usr/bin/firefox &
exec dwm
or the path for chromium might be:
#!/bin/bash
chromium-browser --home-page http://127.0.0.1/resource --no-sandbox --window-size=1920,1280 --start-fullscreen --test-type
exec dwm
Note that only firefox can view more than 6 streams at once, and requires a switch in about:config to do this (see tips section).


==== Users & Screensaver ====
Add an additional user beside the one used for the auto login, otherwise ssh will fail.  
Add an additional user beside the one used for the auto login, otherwise ssh will fail.  
ssh will try to startx when it loads, and it won't be able to. Add USERNAME2 permissions to sudoers.
ssh will try to startx when it loads, and it won't be able to. Add USERNAME2 permissions to sudoers.
<pre>
# adduser USERNAME2
# adduser USERNAME2
nano /etc/sudoers
nano /etc/sudoers
</pre>
 
 


Disable screensaver for the first USERNAME per [https://wiki.archlinux.org/index.php/Display_Power_Management_Signaling Arch Wiki: Display Power Management SIgnaling]


<pre>
Disable screensaver for the first USERNAME per [https://wiki.archlinux.org/index.php/Display_Power_Management_Signaling Arch Wiki: Display Power Management Signaling]
nano /home/USERNAME/.xinitrc


export DISPLAY=:0 &
nano /home/USERNAME/.xinitrc
xset s off &
export DISPLAY=:0 &
xset -dpms &
xset s off &
</pre>
xset -dpms &


These go before the other commands in .xinitrc, as they have the & symbol.
These go before the other commands in .xinitrc, as they have the & symbol.
The total .xinitrc will be something like:
The total .xinitrc will be something like:
<pre>
#!/bin/bash
#!/bin/bash
export DISPLAY=:0 &
export DISPLAY=:0 &
xset s off &
xset s off &
xset -dpms &
xset -dpms &
/usr/local/bin/surf "localhost/zm/cgi-bin/nph-zms??mode=jpeg&monitor=1&scale=100&maxfps=5&buffer=1000&user=user&pass=pass" &
<browser command here>
exec dwm
exec dwm
</pre>


Note: When troubleshooting xset. You must be the same user that is running X (ssh in as different user, then su to user). And, you must export DISPLAY to :0 or similar. Finally xset q should query the current settings.
Note: When troubleshooting xset. You must be the same user that is running X (ssh in as different user, then su to user). And, you must export DISPLAY to :0 or similar. Finally xset q should query the current settings.
Line 159: Line 82:
=== Fine Tuning ===
=== Fine Tuning ===


At this point, you should be able to boot the SBC or desktop and receive a video feed without user interaction. However there are two problems (Beagle). One, it is not full screen. Two, video may be flickering.
At this point, you should be able to boot the SBC or desktop and receive a video feed without user interaction. All the users have to do is press the power button.
 
==== Flickering Video ====
 
This is a known issue with Beaglebone. The simple solution is: install devmem2 or some other memory editing program, change an address. For details of why this is occuring see: [http://www.spinics.net/lists/dri-devel/msg102380.html] and [http://processors.wiki.ti.com/index.php/DA8xx_LCDC_Linux_FB_FAQs] or search online.
 
Steps:
<pre>
git clone https://github.com/VCTLabs/devmem2
cd devmem2
make
make install
</pre>
Append the memory adjustment to rc.local
<pre>
nano /etc/rc.local
devmem2 0x4c000054 w 0x00FFFFF10
</pre>
 
Watch syslog and FIFO errors should immediately stop upon entering write command on memory.
 
Install steps source: [https://www.scivision.co/devmem2-on-the-beaglebone-black/ Scivision: Devmem2 on the beaglebone black]
The author of devmem2 (Jan-Derk Bakker, website and code found at lartmaker.nl), his website is down at the moment. You can view the root domain at internet archive, but the page for devmem2 is not available. Others like VCTLabs above have copied his code to various spots.
 
==== Full Screen Video Feed ====


Two options come to mind:
==== Choosing the proper page to view on the browser ====
* Point browser to a local html page with the link to the monitor embedded in an img tag
OR
* have a local web server run and point surf to a hosted html page.


First Is easiest. Make an html file. Be sure to include http prefix.
See [[External Live Stream]]. I currently use the API version, where you host the page on the ZM server. It's easier to manage multiple machines pointing to one server than to manage each machines self hosted page.
<pre>
<html>
<img width="###px" height=###px" src="http://serverip/zm/cgi-bin/nph-zms?mode=jpeg&monitor=####&scale=100&maxfps=5&user=username&pass=password" />
</html>
</pre>
Call it on .xinitrc before dwm
<pre>
surf file:///home/username/file.html &
</pre>
Customize the width and height of the img tag to fit your monitor. In my case I put st in the .xinitrc
of my beagle instead of surf, restarted, and from the terminal ran <code>xrandr</code> to see what display it was using. I had 1440x900 but the width and height I could get out of surf without borders causing trouble was 1415 and 875. Multiple img tags can be embedded into an html file however you like. See also [[Example Camera View HTML]]


==== Refresh Screen Periodically ====
==== Refresh Screen Periodically ====
Line 208: Line 93:


Install xdotool
Install xdotool
<pre>
# apt-get install xdotool
# apt-get install xdotool
 
</pre>


Edit surf config.h and add the following to the keybindings section, then make and make install.
Edit surf config.h and add the following to the keybindings section, then make and make install.
<pre>
{ 0, GDK_F5,  reload, { .b = FALSE } },
{ 0, GDK_F5,  reload, { .b = FALSE } },
 
</pre>


Add to /etc/crontab
Add to /etc/crontab
<pre>
DISPLAY=:0
DISPLAY=:0
*/5 * * * * username /usr/bin/xdotool key F5
*/5 * * * * username /usr/bin/xdotool key F5
 
</pre>


To make sure this works, with the browser watching a camera stream, restart apache2 on the ZM server, and the browser feed will freeze. A successful F5 from xdotool will refresh the screen, as long as surf has a keybinding for it.
To make sure this works, with the browser watching a camera stream, restart apache2 on the ZM server, and the browser feed will freeze. A successful F5 from xdotool will refresh the screen, as long as surf has a keybinding for it.
Line 235: Line 117:
in /etc/X11/Xwrapper.config
in /etc/X11/Xwrapper.config
apt-get install x11vnc
apt-get install x11vnc
<pre>
</pre>
Final command may be something like
Final command may be something like
  ssh -L 5900:localhost:5900 user@pineboard  x11vnc -safer  -localhost -nopw -once -auth /tmp/serverauth*  -display :0  
  ssh -L 5900:localhost:5900 user@pineboard  x11vnc -safer  -localhost -nopw -once -auth /tmp/serverauth*  -display :0  
Line 246: Line 128:
But none of the other flags to start. When in doubt, break the commands down to make troubleshooting easier.
But none of the other flags to start. When in doubt, break the commands down to make troubleshooting easier.


== Using the Breakout Headers ==
== Tips ==
=== Device Trees and Pin Initialization ===
 
Here are some notes, from my own setup of I2C. It can be confusing if you are new to the Beagle. This guide is also helpful for configuring other peripherals such as GPIO, UART, and SPI.
 
<pre>https://github.com/beagleboard/bb.org-overlays</pre>
Follow this link for developers. Ignore the part about pre built kernels if you used the RCN based installer or image from elinux.org's [http://elinux.org/BeagleBoardDebian BeagleBoardDebian]. You already have cape manager support.
 
If you don't have DTC where is asks for it in the 2nd step for dtc -version, ignore that step. The ./dtc_overlay.sh script will install the latest compatible device tree compiler.
 
Next
<pre>https://github.com/cdsteinkuehler/beaglebone-universal-io</pre>
And use this to '''configure''' the pins.
 
There are also preset modes with the pins configured in various states, but I found it more satisfying to customize them to my needs.
 
<pre>
cd ..
git clone https://github.com/cdsteinkuehler/beaglebone-universal-io
cd beaglebone-universal-io
</pre>
No installation is required for config-pin.
 
Test it now:
<pre> ./config-pin overlay cape-universal</pre>
 
This will allow a lot of pins to be edited. This must be done first. Then you can configure pins. There are other modes as well, see github. Cape-universal exports all pins except for HDMI and EMMC pins.
 
<pre>
#:~/beaglebone-universal-io# cat /sys/devices/platform/bone_capemgr/slots
0: PF----  -1
1: PF----  -1
2: PF----  -1
3: PF----  -1
7: P-O-L-  0 Override Board Name, 00A0,Override Manuf, cape-universal
</pre>


Now you can run something like this:
* dd or clonezilla the disc to an img to deploy in multiple places .
<pre>
./config-pin p8_07 hi
</pre>
To set Pin 07 on header 8 to GPIO HI


To see more options
* When troubleshooting any streams that flicker, try to downscale the video, per [[External Live Stream]] for clients. I.e. include the stream=50 or some percentage lower than 100 in the ZM path.
<pre>./config-pin -h</pre>


e.g.
* On an SBC a counterfeit SD card could be the cause. A counterfeit or non name brand SD may take one day, what takes 2 hours to do with a name brand card.
<pre>./config-pin -l 9_11
default gpio gpio_pu gpio_pd uart</pre>
Showing us we can set the pin to UART or one of the GPIO modes.
<pre> ./config-pin -a 9_11 uart</pre>
Then we can access the UART through either the direct memory registers, or the linux file system access (search online for more details).


The config-pin overlay cape-universal can be set in /etc/rc.local as well as individual pin settings.
* It's possible to lock down the keyboard. I don't have the need, but you can make a reasonably secure kiosk. Look online.


=== I2C Usage ===
* Firefox starts in workspace 9, so you might have to change over to it in dwm upon boot. You can remove all workspaces except for #1, and then ff will boot by default


<pre>
* For viewing more than 6 monitors, you may need to use firefox. See [https://wiki.zoneminder.com/Dummies_Guide#Notes Dummies Guide - Notes]
# apt-get install i2c-tools
</pre>


List
* To start firefox in full screen mode: The best add-on for this I've found is [https://addons.mozilla.org/en-us/firefox/addon/mfull/ mFull]. It can be configured to load full screen, and to remove or autohide the toolbars and navigation bar. There is also RKiosk but this disables all keys and is not needed in my scenario. I've seen some strange behavior with this plugin. On some machines it works and on other machines it will not work. Note that mFull was used in Firefox 52 or earlier.
<pre>
# i2cdetect -l
</pre>


The i2c peripheral, after being connected to the BBB, will be on one of the three i2c buses.
* To shutdown, use crontab.
Either 0,1, or 2.
<pre>
<pre>
# i2cdetect -r 0
# nano /etc/crontab
00 18 * * * root /sbin/poweroff
</pre>
</pre>
Here we search on 0.
The problem is you need full path to poweroff or shutdown -h now. If you are on a separate lan, you may need to use ntp and query some local ntp server, if RTC is off.
 
I used a BMP180 barometer and mine showed up at 77.
 
Unfortunately, the sensor can't be read from without a driver. What you  
will need to do is recompile the kernel with that driver included, as linux has
a driver for the BMP085, but not by default.
 
 
 
References:
(from http://elinux.org/EBC_Exercise_12_I2C)
[http://beaglebone.cameon.net/home/i2c-devices]
[https://datko.net/2013/11/03/bbb_i2c/]
 
=== Recompile Kernel With Sensor Driver ===
 
I built the kernel natively on the Beagle, but this failed. It easiest to cross compile from a Debian based distro. I received an error trying to cross compile on Gentoo.
<pre>
http://elinux.org/EBC_Installing_Kernel_Source</pre>
is a good guide that doesn't require javascript (as RCN's docs do). I installed via the SD card, not through sshfs. Latter did not work. When searching for the driver, in the kernel compile menu, easiest is to hit "/" key and search. In my case "/" then BMP returns the place of the barometer driver.
 
Finally, with the kernel built with support for your i2c device:
 
<pre>
su root
echo bmp085 0x77 > /sys/class/i2c-adapter/i2c-1/new_device
</pre>
0x77 Can be found from i2c-detect. See references.
 
These steps are only valid for the bmp pressure sensor, and when it's on i2c-1.
Review dmesg to see if kernel recognized device.
<pre>
$ dmesg -T
</pre>
 
Navigate to /sys/bus/i2c/drivers/bmp085/1-0077/
and review what the file system provides access to from the sensor using the newly installed driver.
 
==== Instantiate BMP on boot ====
 
Two quick user space options:
<pre>echo bmp085 0x77 > /sys/class/i2c-adapter/i2c-2/new_device</pre>
in /etc/rc.local.
Or add an init.d service (same idea).
* Create script.sh in /etc/init.d/ with #!/bin/sh
* Add commands
<pre>
#!/bin/sh
logger "starting init of BMP"
echo bmp085 0x77 > /sys/class/i2c-adapter/i2c-2/new_device
logger "BMP init complete"
</pre>
* chmod +x /etc/init.d/script.sh
* update-rc.d script.sh defaults
 
References:
[http://elinux.org/Beagleboard:BMP_on_the_Beagle_Bone_Black Elinux.org - BMP on Beaglebone Black]
[http://raspberrypi.stackexchange.com/questions/43821/cannot-perform-echo-command-to-load-driver-for-rtc-module Raspberry Pi S.Exchange Cannot Perform Echo command to load driver for rtc module]
[http://askubuntu.com/questions/299792/why-is-the-command-in-etc-rc-local-not-executed-during-startup]
[https://www.kernel.org/doc/Documentation/i2c/instantiating-devices]
 
== Todo ==
 
* Make a guide similar to the above, but using stali, sabotage, or a similar static binary distro (would be faster / leaner).
 
* This link here [https://web.archive.org/http://blog.lemoneerlabs.com/3rdParty/Darling_BBB_30fps_DRAFT.html] goes a step further into optimizing video processing for the beaglebone black. While the kernel is probably already optimized for bbb hardware, there is room on the software side to compile for optimizations.
 
* Also, consider the RPi3 and its Hardware encoding capabilities, roughly documented here in [https://forums.zoneminder.com/viewtopic.php?f=34&t=26112 the forums]. It may be advisable for future SBC users to pursue a device with hardware encoding.
 
== Notes / Errata==
 
* The above install requires about 2GB (make partition 3GB or 4GB to be safe). dd or clonezilla the partition to an img to reuse later.
 
* With a beaglebone you can not use firefox to watch video. Too slow.
 
* Surf works OK, at 720x1280 with 3-4FPS. EDIT: I've found some issues with what I believe to be the problem: streaming over long cable drops. Flickering video is possible, even after the devmem2 fix. Lowering the FPS (I set it to 1FPS) and or putting a switch before the BBB helps, but does not completely remove flicker. It flickers maybe 1 time every 12 seconds. I did not see these issues with small cable lengths during testing. Desktops and laptops do not have this issue. I recall being able to get it working without dropouts previously...
 
* I've noticed inconsistent monitor resolutions from X upon boot. When I leave my hdmi -> dvi adaptor plugged in to dvi, without tightening the screws, it boots as 1280x720 or so. When I screw it in, it boots as 1080x720 or so. It's probably the poorly made adaptor and cable I am using.
 
* EDIT 09/2017: Referring to note 3 again, This tested OK, through a VPN over the internet, but when put into production on a LAN the 2nd time, it caused blackouts on the screen every so often (how often depended on framerate). The first time this was put into production it worked, iirc. There was a long drop of cable to the beagle (<50 feet). I tried putting a switch before the beagle as a buffer, and it still dropped out, though less often. Lowering FPS also helped. In the end, I used an old laptop, and it works without any dropouts. The beagle was retired temporarily. I may try to get it working again later. It should be able to work, but something was causing the video monitor screen to go flash black periodically.
 
== Troubleshooting ==
 
=== Installing and updating is slow! ===
 
On an SBC a counterfeit SD card could be the cause. A counterfeit or non name brand SD may take one day, what takes 2 hours to do with a name brand card.
 
=== Video monitor flickers, syslog says FIFO underflow! ===
 
See install steps regarding adjusting memory addresses with devmem2.
 
=== How do I disable keypresses for kiosk mode? ===
 
I don't have the need, but it's possible to do further lockdown. Look online.
 
=== Video is still flickering after devmem2 changes! ===
 
See my note. More research is needed. I was able to see the BBB running a ~3FPS 720p stream without error at one point, but at a later point, it began to drop out occasionally. It may be best to either run the viewing feed at a lower resolution, or to use a more powerful ARM based board (or a desktop if you don't need low power).


== See Also ==
== See Also ==
Line 424: Line 158:


*[http://zoneminder.blogspot.com/p/odroid.html Zoneminder Blogspot - ODroid XU4 Zoneminder Client]
*[http://zoneminder.blogspot.com/p/odroid.html Zoneminder Blogspot - ODroid XU4 Zoneminder Client]
*[https://wiki.alpinelinux.org/wiki/Raspberry_Pi_3_-_Browser_Client#Digital_Signage Alpine Linux Version] - The above guide was adapted for digital signage on an RPI4
[[Category:Dummies_Guide]]

Latest revision as of 06:20, 3 November 2023

This is a guide for setting up a dedicated computer (core 2 duo or newer) or SBC (RPI recommended) to view all streams at once. I run this with about 28 streams with live montage of some reasonable slow but usable FPS on a mid-late 2000's used desktop. RPI's would probably only be able to run less streams, maybe 10-15.


This page is a WIP. It was tested on Debian 8/9. This guide has some other tips in Dedicated_RPI_Camera_Monitor and Desktop_SBC_Camera_Monitor. These pages will be incorporated into one page as time permits. There are other ways to do this. You can also have ZMNinja on a dedicated client per http://zoneminder.blogspot.com/p/odroid.html

Setup

Installation

Requirements

  • >8GB HDD / SD
  • SBC (RPI4 or equivalent) / old pc (core 2 duo or newer)
  • Internet connection
  • Computer monitor

This guide used to cover install steps for a BBB, but that will be kept in the history. This guide will now just cover general desktop setup steps.

OS

Install debian without X/Wayland. Install only SSH and the file system utilities from the ISO wizard.

Install dwm from scratch or from the repos (scratch is easier for editing the config file).

apt-get install firefox-esr

Auto Start Computer

The first thing we want to do, is get it so the computer will start without user interaction.

Edit .xinitrc, /etc/rc.local, /etc/inittab, and .bash_profile to auto startx without requiring a login, load the browser (firefox, chromium, or surf) with the path of the zm server monitor feed, and disable the screensaver.


Added to /etc/inittab (comment out existing, and add this below. Replace username with your new user):

1:2345:respawn:/bin/login -f USERNAME tty1 </dev/tty1 >/dev/tty1 2>&1


Copy /etc/profile to user that will be auto logging in:

cp /etc/profile /home/USERNAME/.bash_profile


Appended to /home/USERNAME/.bash_profile :

exec startx

Browsers

When startx loads, it will pull settings from ~/.xinitrc for USERNAME so edit that (note that .xinitrc requires & after all commands that are not the final wm).

#!/bin/bash
/usr/local/bin/surf "localhost/zm/cgi-bin/nph-zms??mode=jpeg&monitor=1&scale=100&maxfps=5&buffer=1000&user=user&pass=pass" &
exec dwm

or firefox might look something like:

#!/bin/bash
/usr/bin/firefox &
exec dwm

or the path for chromium might be:

#!/bin/bash
chromium-browser --home-page http://127.0.0.1/resource --no-sandbox --window-size=1920,1280 --start-fullscreen --test-type
exec dwm

Note that only firefox can view more than 6 streams at once, and requires a switch in about:config to do this (see tips section).

Users & Screensaver

Add an additional user beside the one used for the auto login, otherwise ssh will fail. ssh will try to startx when it loads, and it won't be able to. Add USERNAME2 permissions to sudoers.

# adduser USERNAME2
nano /etc/sudoers


Disable screensaver for the first USERNAME per Arch Wiki: Display Power Management Signaling

nano /home/USERNAME/.xinitrc
export DISPLAY=:0 &
xset s off &
xset -dpms &

These go before the other commands in .xinitrc, as they have the & symbol. The total .xinitrc will be something like:

#!/bin/bash
export DISPLAY=:0 &
xset s off &
xset -dpms &
<browser command here>
exec dwm

Note: When troubleshooting xset. You must be the same user that is running X (ssh in as different user, then su to user). And, you must export DISPLAY to :0 or similar. Finally xset q should query the current settings.

Fine Tuning

At this point, you should be able to boot the SBC or desktop and receive a video feed without user interaction. All the users have to do is press the power button.

Choosing the proper page to view on the browser

See External Live Stream. I currently use the API version, where you host the page on the ZM server. It's easier to manage multiple machines pointing to one server than to manage each machines self hosted page.

Refresh Screen Periodically

You will want to have the web browser refresh every few minutes. Otherwise, if the feed drops out, it will not return unless you reboot. The way I accomplished this was:

Install xdotool

# apt-get install xdotool


Edit surf config.h and add the following to the keybindings section, then make and make install.

{ 0, GDK_F5,  reload, { .b = FALSE } },


Add to /etc/crontab

DISPLAY=:0
*/5 * * * * username /usr/bin/xdotool key F5


To make sure this works, with the browser watching a camera stream, restart apache2 on the ZM server, and the browser feed will freeze. A successful F5 from xdotool will refresh the screen, as long as surf has a keybinding for it.

Accessing headless X via VNC

In the case that you have a headless device (no monitor attached) yet X is running, here's some tips for accessing the desktop via VNC.

sudo apt-get install xserver-xorg-legacy
add:
allowed-users:anybody 
in /etc/X11/Xwrapper.config
apt-get install x11vnc

Final command may be something like

ssh -L 5900:localhost:5900 user@pineboard  x11vnc -safer  -localhost -nopw -once -auth /tmp/serverauth*   -display :0 

If you are doing headless on vnc, get rid of startx on bash profile and just run it manually.

Test x11vnc with

x11vnc -display :0

But none of the other flags to start. When in doubt, break the commands down to make troubleshooting easier.

Tips

  • dd or clonezilla the disc to an img to deploy in multiple places .
  • When troubleshooting any streams that flicker, try to downscale the video, per External Live Stream for clients. I.e. include the stream=50 or some percentage lower than 100 in the ZM path.
  • On an SBC a counterfeit SD card could be the cause. A counterfeit or non name brand SD may take one day, what takes 2 hours to do with a name brand card.
  • It's possible to lock down the keyboard. I don't have the need, but you can make a reasonably secure kiosk. Look online.
  • Firefox starts in workspace 9, so you might have to change over to it in dwm upon boot. You can remove all workspaces except for #1, and then ff will boot by default
  • To start firefox in full screen mode: The best add-on for this I've found is mFull. It can be configured to load full screen, and to remove or autohide the toolbars and navigation bar. There is also RKiosk but this disables all keys and is not needed in my scenario. I've seen some strange behavior with this plugin. On some machines it works and on other machines it will not work. Note that mFull was used in Firefox 52 or earlier.
  • To shutdown, use crontab.
# nano /etc/crontab
00 18 * * * root /sbin/poweroff

The problem is you need full path to poweroff or shutdown -h now. If you are on a separate lan, you may need to use ntp and query some local ntp server, if RTC is off.

See Also