If you’ve followed this far and got it working you’ve probably seen this system is going to produce a LOT of JPEG files. Ours spits out around 17,000 per day. That amount of files is gonna quickly get unmanageable.
Also linux disks tend to have a limited number of “i-nodes”, which work like name tags for files. When your disk runs out of name tags it’s “full” whether it’s actually full to data capacity or not. Storing gazillions of tiny JPEGs is a surefire way to run out of i-nodes quickly.
Continue reading “CCTV GUIDE PART 4 – Archiving and cleanup, and setting up the Live monitor” »
Ok so you’ve got the scripts from part 1 and you’ve found your special url from part 2. Now it’s time to bring it all together and actually make it work!
You’ll need some sort of linux pc like a raspberry pi or similar, perhaps even a pi zero, or even just a regular linux pc. I’ve got the live monitoring part running on a Raspberry pi 2 and the logging part running on another random linux pc. It doesn’t really make much difference. The stuff we’re doing here is pretty basic and universal so you should be pretty much good to go regardless of the platform.
Continue reading “CCTV guide part 3 – Putting it all together –” »
In this part of the guide we’re going to try and figure out that special url you need in order to pull the images directly off the CCD of your IP cam, which is what you need in order to make the scripts from the previous part of the guide work properly.
I’m going to assume zero prior knowledge so am going to try and explain everything as we go along.
For this exercise this is the camera I’ll be using. It’s just a standard cheapo Wanscam one off ebay. It’s not the IP camera I actually use for our CCTV system but it works the same so will illustrate just how similarly they all work:
Continue reading “CCTV guide part 2 – Getting the image off your IP cam” »