                                                                                                                                                                                                                                                                
Received-SPF: pass (google.com: domain of markstew...@gmail.com designates 209.85.223.181 as permitted sender) client-ip=209.85.223.181;
MIME-Version: 1.0
In-Reply-To: <CADHhd=zeFadaYbO06dw7x=eaqo9G+weXMDkZ3GZ8-XSpasH...@mail.gmail.com>
References: <CADHhd=zeFadaYbO06dw7x=eaqo9G+weXMDkZ3GZ8-XSpasH...@mail.gmail.com>
Date: Mon, 1 Oct 2012 20:30:11 +0100
Message-ID: <CAPyX2ne+-ciXGdpjWe7FMR-3oCUWR0+wga_T+8DkWFNd7cY...@mail.gmail.com>
Subject: Re: [london-hack-space] Doorbot and cams
From: Mark Steward <markstew...@gmail.com>
To: london-hack-space@googlegroups.com
Content-Type: multipart/alternative; boundary=bcaec545479a1f895c04cb046f0d

--bcaec545479a1f895c04cb046f0d
Content-Type: text/plain; charset=ISO-8859-1

There's a script that reduces them down to one snapshot per minute
(currently not in crontab).  There were lots of suggestions for timelapses
by more arty people than me a while back, so I've left it at that for now,
but suggestions on how to manage would be welcomed.


On Mon, Oct 1, 2012 at 8:18 PM, Matthew Copperwaite <mattc...@gmail.com>wrote:

> So on the weekend Filbert (Jon) and I decided to figure out what
> happened to the doorbot cam. Tested all the cables from cam to Babbage
> and everything looks good. I spent an hour on it, and rather
> infuriatingly Jon just came along, found the problem in the config
> file and it just started working.
>
> So specifically the problem was that in /etc/motion/motion.conf on
> Babbage 'thread3' was commented out. To enable it Jon uncommented it.
> I imagine someone at some point disabled it (possibly when the
> cam/capture card was faulty) and never re-enabled it as it does take
> up an incredible amount of CPU resources on poor Babbage. I've added
> this to Babbages log on the wiki.
>
> Future plans were vigorously discussed on IRC, but I think for the
> moment if we want a working door cam we're kind of stuck with what we
> got until/if we retire Babbage.
>
> Also I didn't spend that hour twiddling my thumbs I was looking
> through how motion works on Babbage and noticed that there seems to be
> a reasonably complete archive of stills certainly on cam1 going back
> to April this year. Each day takes up 100-500MB on disk (I'm currently
> still calculating it all). I wanted to bring this up because I wasn't
> sure if this was known, whether they should be kept, whether they
> should be analysed (sounds like the most fun) or perhaps have a cron
> job that deletes the anything older than, lets say a week (most
> sensible).
>
> Anyway thanks to Jon for getting it to work.
>
> Matt
> (yaMatt)
>

--bcaec545479a1f895c04cb046f0d
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

There&#39;s a script that reduces them down to one snapshot per minute (cur=
rently not in crontab). =A0There were lots of suggestions for timelapses by=
 more arty people than me a while back, so I&#39;ve left it at that for now=
, but suggestions on how to manage would be welcomed.<div>
<br><br><div class=3D"gmail_quote">On Mon, Oct 1, 2012 at 8:18 PM, Matthew =
Copperwaite <span dir=3D"ltr">&lt;<a href=3D"mailto:mattc...@gmail.com" tar=
get=3D"_blank">mattc...@gmail.com</a>&gt;</span> wrote:<br><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pad=
ding-left:1ex">
So on the weekend Filbert (Jon) and I decided to figure out what<br>
happened to the doorbot cam. Tested all the cables from cam to Babbage<br>
and everything looks good. I spent an hour on it, and rather<br>
infuriatingly Jon just came along, found the problem in the config<br>
file and it just started working.<br>
<br>
So specifically the problem was that in /etc/motion/motion.conf on<br>
Babbage &#39;thread3&#39; was commented out. To enable it Jon uncommented i=
t.<br>
I imagine someone at some point disabled it (possibly when the<br>
cam/capture card was faulty) and never re-enabled it as it does take<br>
up an incredible amount of CPU resources on poor Babbage. I&#39;ve added<br=
>
this to Babbages log on the wiki.<br>
<br>
Future plans were vigorously discussed on IRC, but I think for the<br>
moment if we want a working door cam we&#39;re kind of stuck with what we<b=
r>
got until/if we retire Babbage.<br>
<br>
Also I didn&#39;t spend that hour twiddling my thumbs I was looking<br>
through how motion works on Babbage and noticed that there seems to be<br>
a reasonably complete archive of stills certainly on cam1 going back<br>
to April this year. Each day takes up 100-500MB on disk (I&#39;m currently<=
br>
still calculating it all). I wanted to bring this up because I wasn&#39;t<b=
r>
sure if this was known, whether they should be kept, whether they<br>
should be analysed (sounds like the most fun) or perhaps have a cron<br>
job that deletes the anything older than, lets say a week (most<br>
sensible).<br>
<br>
Anyway thanks to Jon for getting it to work.<br>
<br>
Matt<br>
(yaMatt)<br>
</blockquote></div><br></div>

--bcaec545479a1f895c04cb046f0d--