The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

RE: Rules for Instance WAS PIC testing WAS OSD ALERT


  • Subject: RE: Rules for Instance WAS PIC testing WAS OSD ALERT
  • From: Tony Tofts
  • Date: Wed, 10 Dec 2003 09:23:00 +0000

> What im trying to say is ...a new OSD device when its first
> connected would be aec-tvosd.default and it would then send a
> config heartbeat and get a new instance...I thought the
> default instance alerted xpl hal that this is a new device???...

If your device can remember it's instance in non-volatile ram (or whatever)
that's fine, if it can't it needs to either a generate a unique instance or
you can only have one on a single xpl network.

E.g.

An OSD starts with instance of 'default' gets set to 'LOUNGE'
(aec-tvosd.LOUNGE)

A 2nd OSD starts with instance of 'default' gets set to 'BEDROOM2'
(aec-tvosd.BEDROOM2)

So far, so good - but

If you turn off the power to both OSD's and switch them back on and they
_both_ restart with an instance of 'default' (aec-tvosd.default) how does
xplhal know which is 'LOUNGE' and which is 'BEDROOM2'?

If they both remember that they were 'LOUNGE' or 'BEDROOM2' then everything
is fine.

Regards
Tony






xPL Main Index | xPL Thread Index | xPL Home | Archives Home

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.