[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]
xAP-X10 schema error and improvements
- Subject: xAP-X10 schema error and improvements
- From: "jlgalindo" <jlgalin@xxxxxxxxxxx>
- Date: Sat, 22 Dec 2012 09:44:42 -0000
--1-0916945394-1144426758=:8
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hi group,
I recently worked on a xAP X10 connector according to the xAP-X10 scheme
published in the website (xapautomation.org), and I found a minor bug in
the page and researching the X10 protocol there is some information that
could be added to the scheme, including some already but currently with
few details.
Error found:
- In the "Schema Extensions" section in the last example:
xap-x10.event
{
command=3Don
device=3DB3,B5
}
where the word "command" appear it must be "event" as
the message class
is xap-x10.event.
Improvements:
- In the "Schema Extensions" section there is a list of
additional X10
commands not named before, this is the text from the web:
Additional event request and commands Each adaptor implementation can
define event or request messages for some or all of the following X10
commands.
hail_req
hail_ack
preset_dim_1
preset_dim_2
status_on
status_off
status_req
ext_data
since the X10 protocol is defined I think it would be convenient for
people starting in this protocol provide a correct definition of the
commands since some can not be used with the class xap-x10.event and
class xap-x10.request interchangeably and some require some additional
parameter must be defined so that it can produce a successful
communication between various xap-x10 connectors.
- First, in the command list there is a command not mentioned to be
added to the list: ext_code
- From my interpretation of the X10 protocol hail_ack and hail_req can
not be used interchangeably, hail_req can only be used in a
xap-x10.request message and hail_ack can only be used in a xap-x10.event
message
- For the commands ext_data, ext_code, preset_dim_1 and preset_dim_2
additional keys must be added, I suggest we can use the keys used
previously by Edward Pearson for his connector (extCmd and extData for
ext_code and ext_data, and count for preset_dim_1 and preset_dim_2):
http://tech.groups.yahoo.com/group/xap_automation/message/3632
<http://tech.groups.yahoo.com/group/xap_automation/message/3632>
These messages could be like this:
xAP-X10.Request
{
Device=3DA1
Command=3Dext_code
extCmd=3D49
extData=3D32
}
xAP-X10.Request
{
Device=3DA1
Command=3Dpreset_dim_1
count=3D25
}
- I would also add additional commands like extended1, extended2 and
extended3. These commands are equivalent to ext_code, ext_data and
preset_dim_1 respectively. These commands are also used by Edward.
I think it would be appropriate to unify criteria for the implementation
of this schema as X10 it is well defined and not leave it for everyone
to use it in their own way or interpretation, because it harms the
compatibility of the xAP protocol itself.
If you definitely decide to modify the xap-x10 schema, can count with me
to do it.
Regards,
Jose
--1-0916945394-1144426758=:8
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<head>
<style type="text/css">
<!--
/* start of attachment style */
.ygrp-photo-title{
clear: both;
font-size: smaller;
height: 15px;
overflow: hidden;
text-align: center;
width: 75px;
}
div.ygrp-photo{
background-position: center;
background-repeat: no-repeat;
background-color: white;
border: 1px solid black;
height: 62px;
width: 62px;
}
div.photo-title
a,
div.photo-title a:active,
div.photo-title a:hover,
div.photo-title a:visited {
text-decoration: none;
}
div.attach-table div.attach-row {
clear: both;
}
div.attach-table div.attach-row div {
float: left;
/* margin: 2px;*/
}
p {
clear: both;
padding: 15px 0 3px 0;
overflow: hidden;
}
div.ygrp-file {
width: 30px;
valign: middle;
}
div.attach-table div.attach-row div div a {
text-decoration: none;
}
div.attach-table div.attach-row div div span {
font-weight: normal;
}
div.ygrp-file-title {
font-weight: bold;
}
/* end of attachment style */
-->
</style>
</head>
<html>
<head>
<style type="text/css">
<!--
#ygrp-mkp {
border: 1px solid #d8d8d8;
font-family: Arial;
margin: 10px 0;
padding: 0 10px;
}
#ygrp-mkp hr {
border: 1px solid #d8d8d8;
}
#ygrp-mkp #hd {
color: #628c2a;
font-size: 85%;
font-weight: 700;
line-height: 122%;
margin: 10px 0;
}
#ygrp-mkp #ads {
margin-bottom: 10px;
}
#ygrp-mkp .ad {
padding: 0 0;
}
#ygrp-mkp .ad p {
margin: 0;
}
#ygrp-mkp .ad a {
color: #0000ff;
text-decoration: none;
}
-->
</style>
</head>
<body>
<!-- **begin egp html banner** -->
<br><br>
<!-- **end egp html banner** -->
<P>Hi group,</P>
<P>I recently worked on a xAP X10 connector according to the xAP-X10
scheme published in the website (xapautomation.org), and I found a minor
bug in the page and researching the X10 protocol there is some information
that could be added to the scheme, including some already but currently
with few details.</P>
<P><STRONG>Error found:<BR></STRONG>- In the
"Schema Extensions" section in the last example:</P>
<P>xap-x10.event<BR>{<BR>command=on<BR>device=B3,B5<BR>}</P>
<P>where the word "command" appear it must be
"event" as the message class is xap-x10.event.</P>
<P><STRONG>Improvements:</STRONG><BR>- In the
"Schema Extensions" section there is a list of additional X10
commands not named before, this is the text from the web:</P>
<P><EM>Additional event request and commands Each adaptor
implementation can define event or request messages for some or all of the
following X10 commands. <BR> hail_req
<BR> hail_ack <BR> preset_dim_1
<BR> preset_dim_2 <BR> status_on
<BR> status_off <BR> status_req
<BR> ext_data </EM></P>
<P><SPAN class="hps">since the</SPAN> <SPAN
class="hps">X10</SPAN> <SPAN
class="hps">protocol</SPAN> <SPAN
class="hps">is defined</SPAN> <SPAN
class="hps">I think</SPAN> <SPAN
class="hps">it would be convenient</SPAN> <SPAN
class="hps">for people</SPAN> <SPAN
class="hps">starting in</SPAN> <SPAN
class="hps">this protocol</SPAN> <SPAN
class="hps">provide</SPAN> <SPAN
class="hps">a correct</SPAN> <SPAN
class="hps">definition of</SPAN> <SPAN
class="hps">the commands</SPAN> <SPAN
class="hps">since some</SPAN> <SPAN
class="hps">can not be used</SPAN> <SPAN
class="hps">with the
class</SPAN> xap-x10.event<SPAN class="hps">
and</SPAN>
<SPAN
class="hps">class xap-x10.request</SPAN>
<SPAN class="hps">interchangeably and</SPAN> <SPAN
class="hps">some require</SPAN> <SPAN
class="hps">some</SPAN> <SPAN
class="hps">additional</SPAN> <SPAN
class="hps">parameter</SPAN> <SPAN
class="hps">must</SPAN> <SPAN
class="hps">be defined</SPAN> <SPAN
class="hps">so that it can</SPAN> <SPAN cl
ass="hps">produce a</SPAN> <SPAN
class="hps">successful communication between</SPAN>
<SPAN class="hps">various xap-x10
connectors.</SPAN></P>
<P><SPAN class="hps"><SPAN
class="hps">- First,</SPAN> <SPAN
class="hps">in</SPAN> <SPAN
class="hps">the</SPAN> <SPAN
class="hps">command</SPAN> <SPAN
class="hps">list</SPAN> <SPAN
class="hps">there is</SPAN> a command <SPAN
class="hps">not</SPAN> <SPAN
class="hps">mentioned</SPAN> <SPAN
class="hps">to be added</SPAN> <SPAN
class="hps">to the list:</SPAN> <SPAN
class="hps">ext_code</SPAN></SPAN></P>
<P><SPAN class="hps"><SPAN
class="hps">- From my interpretation of the X10 protocol
hail_ack and hail_req<SPAN class="hps"> can
not</SPAN> <SPAN class="hps">be used interchangeably,
hail_req can only be used in a xap-x10.request message and hail_ack can
only be used in a xap-x10.event
message</SPAN></SPAN></SPAN></P>
<P><SPAN class="hps"><SPAN
class="hps"><SPAN class="hps">- For the
commands ext_data, ext_code, preset_dim_1 and preset_dim_2
additional keys must be added, I <SPAN
class="hps">suggest</SPAN> we can use the<SPAN
class="hps"> keys used</SPAN> <SPAN
class="hps">previously</SPAN> by Edward
Pearson <SPAN
class="hps">for</SPAN> his connector (extCmd
and extData for ext_code and ext_data, and count for preset_dim_1 and
preset_dim_2):</SPAN></SPAN></SPAN></P>
<P><SPAN class="hps"><SPAN
class="hps"><SPAN class="hps"><A
href="http://tech.groups.yahoo.com/group/xap_automation/message/3632";>http://tech.groups.yahoo.com/group/xap_automation/message/3632</A></SPAN></SPAN></SPAN></P>
<P><SPAN class="hps"><SPAN
class="hps"><SPAN class="hps"><SPAN
class="hps">These</SPAN> <SPAN
class="hps">messages could be</SPAN> like
this:</SPAN></SPAN></SPAN></P>
<P><SPAN class="hps"><SPAN
class="hps"><SPAN
class="hps">xAP-X10.Request<BR>{<BR>Device=A1<BR>Command=ext_code<BR>extCmd=49<BR>extData=32<BR>}</SPAN></SPAN></SPAN></P>
<P><SPAN class="hps"><SPAN
class="hps"><SPAN class="hps"><SPAN
class="hps"><SPAN class="hps"><SPAN
class="hps">xAP-X10.Request<BR>{<BR>Device=A1<BR>Command=preset_dim_1<BR>count=25<BR>}</SPAN></SPAN></SPAN><BR></P></SPAN></SPAN></SPAN>
<P><SPAN class="hps"><SPAN
class="hps"><SPAN class="hps">- I would also
add additional commands like extended1, extended2 and extended3. These
commands are equivalent to ext_code, ext_data and preset_dim_1 <SPAN
class="hps">respectively. These commands are also used by
Edward.</SPAN></SPAN></SPAN></SPAN></P>
<P><SPAN class="hps"><SPAN
class="hps"><SPAN class="hps"><SPAN
class="hps"><SPAN class="hps">I</SPAN>
<SPAN class="hps">think it would be</SPAN> <SPAN
class="hps">appropriate to</SPAN> <SPAN
class="hps">unify criteria for the</SPAN> <SPAN
class="hps">implementation</SPAN> <SPAN
class="hps">of this schema</SPAN> <SPAN
class="hps">as X10 it</SPAN> <SPAN
class="hps">is well defined</SPAN> <SPAN
class="hps">and not leave it</SPAN> <SPAN
class="hps">for everyone to</SPAN> <SPAN
class="hps">use it</SPAN> <SPAN
class="hps">in their own way</SPAN> <SPAN
class="hps">or</SPAN> <SPAN
class="hps">interpretation</SPAN><SPAN>,</SPAN&
gt; <SPAN class="hps">because</SPAN> <SPAN
class="hps">it harms</SPAN> <SPAN
class="hps">the compatibility</SPAN> <SPAN
class="hps">of the xAP protocol
itself</SPAN><SPAN>.</SPAN></SPAN></SPAN></SPAN></SPAN></P>
<P><SPAN class="hps"><SPAN
class="hps"><SPAN class="hps"><SPAN
class="hps"><SPAN><SPAN class="hps">If
you</SPAN> <SPAN class="hps">definitely</SPAN>
<SPAN class="hps">decide to modify</SPAN> <SPAN
class="hps">the xap-x10 schema,</SPAN> <SPAN
class="hps">can</SPAN> <SPAN
class="hps">count with me to</SPAN> <SPAN
class="hps">do
it</SPAN><SPAN>.</SPAN></SPAN></SPAN></SPAN></SPAN></SPAN></P>
<P><SPAN class="hps"><SPAN
class="hps"><SPAN class="hps"><SPAN
class="hps"><SPAN><SPAN>Regards,</SPAN></SPAN></SPAN></SPAN></SPAN></SPAN></P>
<P><SPAN class="hps"><SPAN
class="hps"><SPAN class="hps"><SPAN
class="hps"><SPAN><SPAN>Jose</SPAN></SPAN></SPAN></SPAN></SPAN></SPAN></P>
<!-- **begin egp html banner** -->
<br>
<br>
<!-- **end egp html banner** -->
<div width="1" style="color: white; clear:
both;"/>__._,_.___</div>
<!-- Start Recommendations -->
<!-- End Recommendations -->
<!-- **begin egp html banner** -->
<img src="http://geo.yahoo.com/serv?s=97476590/grpId=9674343/grpspId=1705007709/msgId=4825/stime=1356174157";
width="1" height="1"> <br>
<!-- **end egp html banner** -->
<!-- **begin egp html banner** -->
<br>
<div style="font-family: verdana; font-size: 77%; border-top: 1px
solid #666; padding: 5px 0;" >
Your email settings: Individual EmailTraditional <br>
<a href="http://groups.yahoo.com/group/xap_automation/join;_ylc=X3oDMTJmZ3BkdmtjBF9TAzk3NDc2NTkwBGdycElkAzk2NzQzNDMEZ3Jwc3BJZAMxNzA1MDA3NzA5BHNlYwNmdHIEc2xrA3N0bmdzBHN0aW1lAzEzNTYxNzQxNTc-";>Change
settings via the Web</a> (Yahoo! ID required) <br>
Change settings via email: <a href="mailto:xap_automation-digest@xxxxxxx?subject=Email
Delivery: Digest">Switch delivery to Daily Digest</a> <a
href = "mailto:xap_automation-fullfeatured@xxxxxxx?subject=Change
Delivery Format: Fully Featured">Switch to Fully Featured</a>
<br>
<a href="http://groups.yahoo.com/group/xap_automation;_ylc=X3oDMTJkdXI1bzFtBF9TAzk3NDc2NTkwBGdycElkAzk2NzQzNDMEZ3Jwc3BJZAMxNzA1MDA3NzA5BHNlYwNmdHIEc2xrA2hwZgRzdGltZQMxMzU2MTc0MTU3";>
Visit Your Group
</a>
<a href="http://docs.yahoo.com/info/terms/";>
Yahoo! Groups Terms of Use
</a>
<a href="mailto:xap_automation-unsubscribe@xxxxxxx?subject=Unsubscribe";>
Unsubscribe
</a>
<br>
</div>
<br>
<!-- **end egp html banner** -->
<div style="color: white; clear:
both;"/>__,_._,___</div>
</body>
</html>
--1-0916945394-1144426758=:8--
xAP_Automation Main Index |
xAP_Automation Thread Index |
xAP_Automation Home |
Archives Home
|