Re: BCS and X10 Question

["g8kmh" <g8kmh@xxxxxxxxxxx>]

--- In xAP_developer@xxxxxxx, Kevin Hawkins <lists@u...>=20
wrote:
>
> >
> > Very relevant as I'm in the middle of an xAP->DMX plug-in for
xFx=20
> > using BSC. There an xAP address and/or ID has to be translated=20
into a=20
> > DMX channel.
> >=20=20=20
>=20
> Is that using the Milford Instrument board ??

Yes, it is the Milford DMX transmitter board.

>=20
> > I know that there is an awareness that 255 ID's isn't
sufficient=20
(a=20
> > single universe can have 512 channels) but in any event=20
addressing=20
> > individual channels isn't friendly.=20
>=20
> Yes we have long said that a new UID format is 'in the wings' where=20
the=20
> 255 limit will be replaced by either a significantly larger limit=20
or=20
> perhaps no limit at all...

I'd go with the no limit (on BSC ID)and be controversial - drop the=20
source UID in the header completely. Is there an application that=20
uses it? So far I think the real world PIC applications have used=20
another protocol on the wire or used a device with enough horsepower=20
to parse addresses(PIC18F) - not sure about your Rabbit apps.

> > The approach I've taken is to map=20
> > subaddress.subsubaddress (and I'm sure that's not the right=20
> > terminology but octet isn't right either!) to a channel. So=20
> > mmwave.dmx512.system:lounge.tablelamp1 might be DMX channel=20
324/ID=3D10.
> > Sending a BSC with ID=3D* and target
mmwave.dmx512.system:lounge.>=20
with=20
> > a state=3Doff would turn all the lounge lights off.
> >=20=20=20
>=20
> That's a a sensible use of the sub adressing hierarchy.
> > Right now all of the configuration is coded in an XML file (AMS)
> > without a means of 'over the wire' change, albeit not
something=20
> > you're going to do often but I'll add a specific schema for
that=20
and=20
> > scenes.
> >=20=20=20
> Yes, having the endpoint mappings configurable and recoverable from=20
a=20
> device lends itself to some portability across connectors in a=20
different=20
> way...

Also allows a default value per channel for startup/power fail=20
recovery.

> > BTW. Celsius doesn't have a degrees.......
> >=20=20=20
> Oh..really.... interesting - (and I am assume Centigrade and=20
Celsius and=20
> probably Kelvin ?? are the same in this respect) you learn=20
something=20
> every day...  K
Mmmm, well, actually it appears I'm confused :-( Whilst I'm used to=20
using 20C as a temperature - the definitive answer seems to be it=20
should be 20=B0C to avoid confusion with Coulombs... but Kelvin doesn't=20
have the =B0. So maybe all xAP temperatures should be in Kelvin - 303K=20
for me please!

Lehane