RE: Configuration process

[Ian Lowe]

>Apologies if this was covered in the xAP group but even if it was, it
could
>well be different here!

Configuration is, as I understand it, pending v1.3 in xAP, so it may end up
similar!

>What happens if several similar devices have been plugged in ?

Confusion reigns! in all probability, the config message would end up with
both devices taking on the new ID, and much gnashing of teeth would
follow..

The short version, "extremely simple" is the watchword, and you
have a
little more work as an installer, in return for greater simplicity in
getting to that point!

>having to go back to the console everytime a device was installed would
be
>tiresome to say the least.

possibly, but it is a one-time only process.

>Presumably each device would have to have some form of non-volatile
memory
>such as EEPROM to store its config otherwise it would need to be
>re-addressed after each power failure.

Yep. It's implied that any device which can be configured has some
mechanism
for retaining this configuration between power-ups.

>One further point that I dont specifically see mentioned in the spec
are
the
>delimiters identification. I am assuming that because the fields are
not
>fixed length but length limited that "-" delimits
VENDOR-DEVICE and "."
>delimits DEVICE.INSTANCE is this correct.

That's correct, I'll get the document updated.

>Also is white space banned/ignored unless it falls between
"=" and <CR> in
a
>name/value pair as per xAP.

ditto, again, I'll get the doc updated.

>Makes interesting reading :-)

Thanks Keith!

I.