Re: new X10 component: medusa-cm11

["tomvdp" <tomvdp@xxxxxxxxx>]

Hi John,

(replying via Yahoo groups directly... there seems to be a problem
forwarding the msgs via mail)

> Most users won't be aware of the underlying X10 protocol, and they
shouldn't have to be.

If you are going to write xPL X10 commands you better understand the
X10 commands.  You will need to learn housecodes, device codes,
function codes, etc.  The extra bit "you can't send the same function
to devices on a different housecode" will not be insurmountable.

<snip>

> > It forces the sender to construct syntactical correct X10
commands.
>
> But
> device=A1,A2,C3,F5 is also syntactically correct.
>

Not from the point of view of the X10 protocol.

<snip>
>
> The VB6 CM12 app, HomeVision and the MR26E are just some of the
apps that I can think of that use x10.basic - are you sure these
don't support mixed device lists?

How do these send x10.confirm messages ?

device=A1,A2,C3

The first 2 devices can go in 1 X10 command, the C3 in another.

But according to the xpl specs, there should be 1 confirm message...
And what if A1,A2 was successful but C3 wasn't ?

The problem I have with x10.basic is that it does not describe valid
x10 commands.  If one could send only valid X10 commands via xPL,
then there would be no need to go through an extra layer of
interpretation at the receiver's side.  A sender that constructs
messages like device=A1,A2,C3 surely is already some form of logic
(it is probably HAL script or an elaborate determinator) that could
just as well know that is should split the message.

I am not being "contraire" (hopefully you understand that one, I
can't translate it! ;-) : I will stick to the schema, but then the
above points must be clarified.

Regards,
Tom






xPL Links: http://www.xplproject.org.uk http://www.xplhal.com http://www.xpl.myby.co.uk
To Post a Message: ukha_xpl@xxxxxxx
To Subscribe:  ukha_xpl-subscribe@xxxxxxx
To Unsubscribe:  ukha_xpl-unsubscribe@xxxxxxx