The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024

Latest message you have seen: Re: external weather sensor


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Controllerless distributed automation


  • To: "Ukha" <ukha_d@xxxxxxx>
  • Subject: Controllerless distributed automation
  • From: "Ian B" <ian.bird@xxxxxxx>
  • Date: Fri, 16 Feb 2001 00:02:09 -0000
  • Delivered-to: rich@xxxxxxx
  • Delivered-to: mailing list ukha_d@xxxxxxx
  • Mailing-list: list ukha_d@xxxxxxx; contact ukha_d-owner@xxxxxxx
  • Reply-to: ukha_d@xxxxxxx

I have three of the Bik sensors from when he was selling them. I have also
downloaded all the info from his site. It would be interesting to try and
make one of these. From what I have seen whilst using mine they work and
are
reputably safe. It's spooky to see the led come in when you walk into the
room.

Anyone know why he stopped selling them?

If you want any more info then mail me or the list.

Ian



-----Original Message-----
From: David Paterson (Pixi) [mailto:david.paterson@xxxxxxx]
Sent: 15 February 2001 23:04
To: ukha_d@xxxxxxx
Subject: Re: [ukha_d] Controllerless distributed automation


On Wed, 14 Feb 2001 23:57:06 -0000, you wrote:

>That's a fair point, but it does serve to illustrate part of the
problem,
>who (or what) decides which neighbours are relevent to each other? - if
a
>room thermostat does not "know" that the actions of a light
switch in the
>same room are relevant to it's operation, then might not the heating
stay
on
>way beyond the time the room has ceased to be occupied?

Yep, it's one of the basic problems that I need to solve.  I can either
predefine the "relevance relationships" of device types, but that
might
lead to limitations in what the system can do, or I can design the
system to figure it out for itself, which will probably be impossible to
do effectively.  These initial design choices are going to be the
hardest and most important - and the hardest.

>Actually,
>occupancy detection is a really good one to test out any system on, as
this
>has been discussed at >great< length before, and the groups'
collective
>expertise has yet to come up with a failsafe system.

I agree that occupancy sensing is a key part of any effective system,
and is one of those problems just waiting for a good, cheap solution.
To me it seems fundamental for ensuring the system is delivering the
right services in the right places at the right times.

I've been interested for a while in the Bik RF systems, but they're no
longer being produced commercially (AFAIK) so that's maybe not a real
option now.  I did hear he'd put the designs into the public domain for
hobby or non- profit use, so I might have a look at them and se if
there's any potential in them.

>But, my point is,
>that unless the room thermostat knows the difference between a
thermostat
>and a light switch, how is it to know that it does not care about that
>difference? - with a distributed intelligence system, you have to think
>about these things. - any component >must< have a knowledge of
it's
>environment in order to interact successfully within that
environment...

That's true, but the question I'm trying to resolve is how much
knowledge does it need, and how can I represent it effectively.  I need
to reduce all the different forms of information down to their lowest or
simplest forms, and then build a knowledge base from them.  All a bit
vague at the moment, but discussing it makes me think things through a
bit more carefully.

> (snip)
>
>OK, you got me, - you're right, I am broadly in favour of a distributed
>intelligence model, but only to a certain point. - I don't yet see the
>technology available to implement such a model (at reasonable cost).
You're
>example (frivolous as it may have been ), of a light switch with 1Ghz
CPU
>and 128MB RAM, will no doubt be with us one day in the not-too-distant
>future, but (and this is the important bit), >NOT< today, and
>NOT<
tomorrow
>either. (much to my chagrin) (and undoubtedly yours too?)

Well, it wasn't entirely frivolous.  Having watched Moore's law in
action for the past 25 or so years, I can confidently predict that
within 5 years time I'll be able to buy a microcontroller running at
about 200 MHz, with at least 256K of memory, and probably for around £20
or less.  The 1 gig chip won't take much longer after that.

Of course you'll get the "why would you need all that power?"
perennial
question, but there are always newer applications, smarter ideas and
clever ways to do things which just soak up every drop of processing
resource you have.  You can _never_ have too much power :-)

> (snip)
>
>Keep up the good work, - 'cos if anyone comes up with a solution, it
will
be
>a goldmine!!

Well, I'm not sure I'll succeed, but I'll give it a try.  I've got a
fair bit of relevant (and irrelevant) experience from various jobs doing
things like embedded systems, production line automation, distributed
interactive simulation, and video game development, and there are a lot
of ideas and techniques I've picked up over the years which might be of
some use.

At least I should be able to design a really flashy user interface for
it if nothing else :-)

DP

--
David_Paterson = david.paterson@xxxxxxx ¦ david.paterson@xxxxxxx;

R & D programmer        There are three kinds of people in the world -
Visual Sciences Ltd.      those who can count, and those who can't...








Home | Main Index | Thread Index

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.