Re: Rules for Instance WAS PIC testing WAS OSD ALERT

[steve.cooper@xxxx]

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

You may still want to reconfig it's instance at runtime from say
GSHED-MYPIC.1 to GSHED_MYPIC.LOUNGE and if you do it the first time xPLHAl
will remember and next time it gets a config.request message from
GSHED-MYPIC.1 it will automatically inform it that it's instance should be
LOUNGE.

> 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?

You can't. This is why a unit needs to have a unique configuration at power
up, hence the use of jumpers or a unique id at the point of programming the
PIC. If two units both come on with GSHED-MYPIC.1 they will both be told
to set there instances to LOUNGE. Ideally a device should store it's new
instance for future use but this is only possible with the newer PIC chip
types.

S.



___________________________________________________________________________
The information contained in this message is confidential and may be
legally privileged. If you are not the intended recipient, please do not
read, copy or otherwise use it and do not disclose it to anyone else.
Please notify the sender of the delivery error and then delete the
message from your system.
Any views or opinions expressed in this email are those of the author only.
Communications will be monitored regularly to improve our service and for
security and regulatory purposes.
Thank you for your assistance.
___________________________________________________________________________