Since mjpg-streamer provides a web interface for controlling the camera, we can cause the camera LED to blink to show that things are working, and then turn the camera LED off to make it less obvious it’s doing anything when other people see it (mainly smelly robbers….I’m assuming they’re smelly). root/mjpg-streamer-r63/mjpg_start_script.shĮxec /root/mjpg-streamer-r63/mjpg_streamer -i "/root/mjpg-streamer-r63/plugins/input_uvc.so -d /dev/video0 -r 800圆00 -f 5" -o "/root/mjpg-streamer-r63/plugins/output_http.so -w /root/mjpg-streamer-r63/www -p 9000 -c user:password" -b &Ĭurl 1st line after #!/bin/bash and before sleep 1 is one, massive line for starting mjpg-streamer. In this script, the resolution, framerate, and some other options can be changed for streaming out of the Dockstar:
![dockstar led dockstar led](http://www.yourwarrantyisvoid.com/wp-content/uploads/2010/07/dockstar-side.jpg)
![dockstar led dockstar led](http://www.yourwarrantyisvoid.com/wp-content/uploads/2010/07/dockstar-back-300x225.jpg)
This next script is what does all the configurations for mjpg-streamer. Supposedly the wireless link quality improves when you’re not overdriving the output….
Dockstar led driver#
The driver defaults to 23dbm (I think), but the max output for the card is supposed to be 15dbm (again if I remember right), and that’s where the 15dbm number came from. Setting the TXpower to 15dbm makes sure that the wifi adapter isn’t overdriving the output. Leaving them in doesn’t detract from the operation of the script, however. I don’t remember if the slashes or semicolons at the end are needed or not. root/mjpg-streamer-r63/mjpg_start_script.sh & # In order to enable or disable this script just change the execution # Make sure that the script will "exit 0" on success or any other # This script is executed at the end of each multiuser runlevel. This first script (by the way, these are in no particular order, and some depend on each other) is what gets the wireless connected and mjpg-streamer going too so that Zoneminder can use the video from this camera: I’ll at least describe what each script is doing… There’s basically just gonna be a lot of code and not much else. I assume that you already set the arcNumber to 2998 to make the kernel identify the dockstar as a dockstar.This post is just to document all the scripts that were created/reused to make the Dockstar run pretty much on its own… I am not responsible for any malfunctions or damages on your device!
Dockstar led install#
If you know what you are doing you are ready to download and install the kernel. This part is analogue to my other articles concerning kernel installations: What you need to do is carefully read through davy’s post Newer uBoot as workaround to 3.2 kernel problem? and follow these steps before installing my kernel. If this happens you need to revert to a lower version of the kernel than 3.2.x (find help here: Dockstar: Does not boot with self-compiled Kernel?).įor now I didn’t get the kernel working with the goflex series, so this article is dedicated to dockstar users only. Otherwise your dockstar will fail to boot up.
![dockstar led dockstar led](https://arukam.com/wp-content/uploads/2018/12/44355-3.jpg)
It is absolutely necessary to get a newer version than provided in Jeff’s script. Taking a look at made me jealous… Here it is – a fully working 3.3.3: 1. But following davy’s guide to upgrade U-Boot makes that one boot. With that in mind I started up my VM and looked at what I’ve got there in /usr/src – there was a compiled 3.2.1 that initially wouldn’t boot.
Dockstar led drivers#
As you may have noticed, we were discussing things about newer kernels and drivers in the comments of Dockstar/Goflex: new Kernel 3.1.10 ready to use.