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: Frank Mc Alinden
  • Date: Wed, 10 Dec 2003 09:31:00 +0000

>Hardcoded to a single instance (only 1 per network)

Doesnt Ian want this to be configurable ??

Frank

----- Original Message -----
From: Tony Tofts
To: <a
href="/group/ukha_xpl/post?postID=y4ms45yx991OYNVYeS-N-UuZtVcCQXmonUENgNilxBAXygnfDg5Y2tmbf0iDc80j96wy5F3xGrQpULGAm1-KqDM">ukha_xpl@xxxxxxx</a>
Sent: Wednesday, December 10, 2003 8:27 PM
Subject: RE: [ukha_xpl] Rules for Instance WAS PIC testing WAS OSD ALERT


Something I didn't cover was how a unique instance might be set on a
hardware device like a pic

Some examples

Hardcoded to a single instance (only 1 per network)

Generate unique instance e.g. ip address (for ethernet enabled)

Each device built/burned with a unique id (same principle as nic mac
address)

Jumpers

Particularly for serial attached to a pc, a piece of software (based on
something like xpl_devcom that assigns unique instance per com port)

And I'm sure we can think of a few others

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.