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: Gordon JC Pearce
  • Date: Wed, 10 Dec 2003 12:29:00 +0000

On Wed, 2003-12-10 at 11:03, <a
href="/group/ukha_xpl/post?postID=-j8K55CdL4Q0QLsK4K3bitE0NCBTWftT5tZRxjX81XWTsoqxMiDI2R7SpjVPbJ0woTcjpRxpBqBm9ImmqTPIGDsNCqHe">steve.cooper@u...</a>
wrote:
>
> It might be easier to have some EEPROM type memory or to have an id at
> program time but an alternative method might be to have some jumps on
a few
> spare input pins. Using three pins would allow an instances of 0->7
> allowing you to have up to 8 devices of the same type on a network.
>
> xPLHal can send the proper instance and it can be store in Ram
>
> S.

Presumably then, the unit wouldn't need to listen for a config message,
but just come up ready to run?

What happens if you have identical but reconfigurable units that both
come on at the same time? How do you differentiate between them for the
purposes of sending config messages?

Gordon.







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.