Re: Rules for Instance WAS PIC testing WAS OSD ALERT

[Ian Lowe]

----- Original Message -----
From: "Gordon JC Pearce" <<a
href="/group/ukha_xpl/post?postID=CqrcQVDv47jgGX5U-kCRx_3Gef6lCyhR7kEzBkdjk3WUZVP0xy6KKhgNEV8InS7cwyMw1Jda">gordon@g...</a>>
> 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?

Which brings us nicely back to the reasoning behind requiring a device to
store it's own config in NV storage.. We can make clear in the
documentation
that you install devices one at a time, but if devices can't remember a
name
change, or in some way be unique, it's a royal PITA. :

I.