So just a little update re the crypto-radiator – I’ve since got the TEMPer USB thermal probe working on the machine and have set it to log temperatures.
There is however a slight issue in that the usb ports are on the back of the machine and that’s also where the warmed air comes out , so the heat from that does affect the reading from the TEMPer device somewhat, which means the temperature reading can’t really be relied upon to be entirely accurate.
Just found this wordpress penetration-testing tool – looks pretty handy, especially since it seems to have some follow-up tools to do stuff once you’ve gained access. Another one for the testing arsenal!
How handy would it be to have a shared network folder where you can drop a PDF to print and it just magically pops out of the printer a couple of mins later? Especially since you can print to PDF from pretty much any platform or device..including mobile phones and tablets. Pretty handy I think! Especially if you can do so with pretty much any old (or even ancient) printer rather than having to buy a funky new bluetooth/wireless one.
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.
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.
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:
This post is the first part of a series which shows how to turn your IP-cam and raspberry pi (or other embedded linux machine. pc etc) into a pretty decent and *reliable* security system which logs images, auto archives old images and cleans up after itself.
It’s free, and all you need is a text editor and a bit of time to figure out the particulars for your system. I’ve done the hard bit which is working out the process and writing the bash scripts to actually do the hard work.