[Message Prev][Message
Next][Thread Prev][Thread Next][Message
Index][Thread Index]
RE: Updated X10 connectors
------=_NextPart_000_0013_01C6B983.A45B2990
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
I've not changed any code related to the areas you mention for quite a
while. Are you saying that these are new behaviours seen with this release
or just that you are testing this one with more demanding wildcard
sequences
than before?
_____
From: xap_automation@xxxxxxx [mailto:xap_automation@xxxxxxx]
On Behalf Of Kevin Hawkins
Sent: 06 August 2006 03:01
To: xap_automation@xxxxxxx
Subject: Re: [xap_automation] Updated X10 connectors at www.erspearson.com
I seem to have a couple more problems Edward
1) I seem to be able to turn a device off but not on - if I send a
BSC off it works fine but change the state= 'off' to 'on' and it
doesn't. With the 'off' I see in the GUI the xAP receive
xAPBSCcmd:<devicename> with 1 block followed by a transmit of the X10
event and then the BSC info or event message . With the on command I
just see the xAP Receive xAPBSC.cmd:<devicename>
2) I am having a load of problems with wildcards . Temporarily I
have set up my names like this example to initially preserve some X10
information whilst I get it working.
ERSP.X10.machine:D7.Hall.TableLamp
I tried targeting ERSP.X10.*:D7.> and nothing worked , in fact I am
not sure anything works with a : in it once wildcarded. So I then
guessed at
ERSP.X10.*.D7.> and I got a load of devices changing state even though
only one of mine has D7 in it. About half my X10 devices changed
state. When I fully qualified the target it seemed to work OK. BTW I
am using ID=*
One of the reasons the wildcarding is quite important for me is that
my little embedded mapper has limited target address space so anything I
(or users) can wildcard saves target string storage eg >:D7.> is much
more compact than the full address although *.X10.>:D7.> is probably
more focussed. Eventually I will probably go for >:*.Hall.TableLamp or
*.X10.>:*.Hall.TableLamp though or better still remove the X10
house/device code totally.
The : is now very important in wildcarding since sub addressing to
divide the address into the two components with the first > matching
'only' to the : and the second to the end of the sub address ie a match
anything is >:> and not *.> (the latter would not match anything
that
had a sub address) although it would match every application. I wonder
if maybe this is a carry over from Stuart not fully integrating sub
addressing into xFX ?
Kevin
Kevin Hawkins wrote:
>
> This could be just my setup here Edward (gosh how I hate X10) but I am
> not reliably seeing the commands showing in the X10 connector window
> (just getting housecodes)., and consequentially no events sent. So I
> send D4 ON and all I see is X10 receive Address: house=D unit=4. Will
> try another site for my X10 receiver and see if it improves. The lamp
> elsewhere does change state correctly but my CM12U is very close to
lots
> of PC's so it may be getting noise. The transmitted X10 from the CM12U
> gets through fine. As some commands do get through it's looking like
an
> X10 hardware issue.
>
> Kevin
>
> Edward Pearson wrote:
> >
> > After a week beset with configuration problems with v2.6 of the
X10
> > connector, I have now got the build scripts sorted, CVS behaving
> > itself again and uploaded the latest builds (v2.6.3) at
> > www.erspearson.com <http://www.erspears <http://www.erspearson.com>
on.com
> <http://www.erspears <http://www.erspearson.com>
on.com>>.
> >
> > Please email if you find any more issues with these versions.
> >
> > Edward
> >
>
>
------=_NextPart_000_0013_01C6B983.A45B2990
Content-Type: text/html; charset=US-ASCII
Content-Transfer-Encoding: 7bit
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3c.org/TR/1999/REC-html401-19991224/loose.dtd";>
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html;
charset=us-ascii"><!-- Network content -->
<META content="MSHTML 6.00.2900.2912"
name=GENERATOR></HEAD>
<BODY style="BACKGROUND-COLOR: #ffffff">
<DIV dir=ltr align=left><SPAN class=390530817-06082006><FONT
face=Arial
color=#0000ff size=2>I've not changed any code related to the areas you
mention
for quite a while. Are you saying that these are new behaviours seen with
this
release or just that you are testing this one with more demanding wildcard
sequences than before?</FONT></SPAN></DIV><BR>
<BLOCKQUOTE
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px
solid; MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B>
xap_automation@xxxxxxx
[mailto:xap_automation@xxxxxxx]
<B>On Behalf Of </B>Kevin
Hawkins<BR><B>Sent:</B> 06 August 2006
03:01<BR><B>To:</B>
xap_automation@xxxxxxx<BR><B>Subject:</B> Re:
[xap_automation] Updated
X10 connectors at
www.erspearson.com<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV id=ygrp-text>
<P>I seem to have a couple more problems Edward<BR><BR>1)
I seem to be able to
turn a device off but not on - if I send a <BR>BSC off it works fine
but
change the state= 'off' to 'on' and it <BR>doesn't. With the 'off' I
see in
the GUI the xAP receive
<BR>xAPBSCcmd:<devicena<WBR>me> with 1 block
followed by a transmit of the X10 <BR>event and then the BSC info or
event
message . With the on command I <BR>just see the xAP Receive
xAPBSC.cmd:<<WBR>devicename><BR><BR>2) I am
having a load of problems
with wildcards . Temporarily I <BR>have set up my names like this
example to
initially preserve some X10 <BR>information whilst I get it
working.<BR><BR>ERSP.X10.machine:<WBR>D7.Hall.TableLam<WBR>p
<BR><BR>I tried
targeting ERSP.X10.*:D7.<WBR>> and nothing worked , in fact I
am <BR>not
sure anything works with a : in it once wildcarded. So I then
<BR>guessed
at<BR><BR>ERSP.X10.*.D7.<WBR>> and I got a load of
devices changing state
even though <BR>only one of mine has D7 in it. About half my X10
devices
changed <BR>state. When I fully qualified the target it seemed to
work OK. BTW
I <BR>am using ID=*<BR><BR>One of the reasons the
wildcarding is quite
important for me is that <BR>my little embedded mapper has limited
target
address space so anything I <BR>(or users) can wildcard saves target
string
storage eg >:D7.> is much <BR>more compact than the
full address
although *.X10.>:D7.> is probably <BR>more focussed.
Eventually I will
probably go for >:*.Hall.TableLamp or
<BR>*.X10.>:*.Hall.<WBR>TableLamp
though or better still remove the X10 <BR>house/device code totally.
<BR>The :
is now very important in wildcarding since sub addressing to
<BR>divide the
address into the two components with the first > matching
<BR>'only' to the
: and the second to the end of the sub address ie a match
<BR>anything is
>:> and not *.> (the latter would not match anything
that <BR>had a
sub address) although it would match every application. I wonder
<BR>if maybe
this is a carry over from Stuart not fully integrating sub
<BR>addressing into
xFX ?<BR><BR>Kevin<BR><BR>Kevin Hawkins
wrote:<BR>><BR>> This could be
just my setup here Edward (gosh how I hate X10) but I am<BR>>
not reliably
seeing the commands showing in the X10 connector window<BR>>
(just getting
housecodes).<WBR>, and consequentially no events sent. So
I<BR>> send D4 ON
and all I see is X10 receive Address: house=D unit=4.
Will<BR>> try another
site for my X10 receiver and see if it improves. The lamp<BR>>
elsewhere
does change state correctly but my CM12U is very close to
lots<BR>> of PC's
so it may be getting noise. The transmitted X10 from the
CM12U<BR>> gets
through fine. As some commands do get through it's looking like
an<BR>> X10
hardware issue.<BR>><BR>>
Kevin<BR>><BR>> Edward Pearson
wrote:<BR>> ><BR>> > After a week
beset with configuration
problems with v2.6 of the X10<BR>> > connector, I have
now got the build
scripts sorted, CVS behaving<BR>> > itself again and
uploaded the latest
builds (v2.6.3) at<BR>> > www.erspearson.<WBR>com
<<A
href="http://www.erspearson.com";>http://www.erspears<WBR>on.com</A>
<BR>>
<<A
href="http://www.erspearson.com";>http://www.erspears<WBR>on.com</A>>>.<BR>>
><BR>> > Please email if you find any more
issues with these
versions.<BR>> ><BR>> >
Edward<BR>> ><BR>><BR>>
<BR><BR></P></DIV><!--End group email
--></BLOCKQUOTE>
<span width="1" style="color:
white;"/>__._,_.___</span>
<!-- **begin egp html banner** -->
<img src="http://geo.yahoo.com/serv?s=97476590&grpId=9674343&grpspId=1600007709&msgId=2892&stime=1154885355";
width="1" height="1"> <br>
<!-- **end egp html banner** -->
<!-- **begin egp html banner** -->
<br><br>
<div style="width:500px; text-align:right; margin-bottom:1px;
color:#909090;">
<tt>SPONSORED LINKS</tt>
</div>
<table bgcolor=#e0ecee cellspacing="13"
cellpadding="0" width=500px>
<tr valign=top>
<td style="width:25%;">
<tt><a href="http://groups.yahoo.com/gads;_ylc=X3oDMTJjMW10MjZoBF9TAzk3NDc2NTkwBF9wAzEEZ3JwSWQDOTY3NDM0MwRncnBzcElkAzE2MDAwMDc3MDkEc2VjA3NsbW9kBHN0aW1lAzExNTQ4ODUzNTU-?t=ms&k=Workflow+automation&w1=Workflow+automation&w2=Automation+equipment&w3=Industrial+automation&w4=Test+automation&w5=Factory+automation&c=5&s=123&g=0&.sig=UMuHyfDcKCN-8Czn5DvjNg";>Workflow
automation</a></tt>
</td>
<td style="width:25%;">
<tt><a href="http://groups.yahoo.com/gads;_ylc=X3oDMTJjdmNrdHZqBF9TAzk3NDc2NTkwBF9wAzIEZ3JwSWQDOTY3NDM0MwRncnBzcElkAzE2MDAwMDc3MDkEc2VjA3NsbW9kBHN0aW1lAzExNTQ4ODUzNTU-?t=ms&k=Automation+equipment&w1=Workflow+automation&w2=Automation+equipment&w3=Industrial+automation&w4=Test+automation&w5=Factory+automation&c=5&s=123&g=0&.sig=hRMkcOBBZ36mW9UeMEmhhg";>Automation
equipment</a></tt>
</td>
<td style="width:25%;">
<tt><a href="http://groups.yahoo.com/gads;_ylc=X3oDMTJjNDVlbjdmBF9TAzk3NDc2NTkwBF9wAzMEZ3JwSWQDOTY3NDM0MwRncnBzcElkAzE2MDAwMDc3MDkEc2VjA3NsbW9kBHN0aW1lAzExNTQ4ODUzNTU-?t=ms&k=Industrial+automation&w1=Workflow+automation&w2=Automation+equipment&w3=Industrial+automation&w4=Test+automation&w5=Factory+automation&c=5&s=123&g=0&.sig=2fnn4Mg42mPil-CoKXA_kg";>Industrial
automation</a></tt>
</td>
</tr>
<tr valign=top>
<td style="width:25%;">
<tt><a href="http://groups.yahoo.com/gads;_ylc=X3oDMTJjbDhnaDB1BF9TAzk3NDc2NTkwBF9wAzQEZ3JwSWQDOTY3NDM0MwRncnBzcElkAzE2MDAwMDc3MDkEc2VjA3NsbW9kBHN0aW1lAzExNTQ4ODUzNTU-?t=ms&k=Test+automation&w1=Workflow+automation&w2=Automation+equipment&w3=Industrial+automation&w4=Test+automation&w5=Factory+automation&c=5&s=123&g=0&.sig=7d_lPdR-fmMQUamXeHQA_A";>Test
automation</a></tt>
</td>
<td style="width:25%;">
<tt><a href="http://groups.yahoo.com/gads;_ylc=X3oDMTJjNHBiN2xuBF9TAzk3NDc2NTkwBF9wAzUEZ3JwSWQDOTY3NDM0MwRncnBzcElkAzE2MDAwMDc3MDkEc2VjA3NsbW9kBHN0aW1lAzExNTQ4ODUzNTU-?t=ms&k=Factory+automation&w1=Workflow+automation&w2=Automation+equipment&w3=Industrial+automation&w4=Test+automation&w5=Factory+automation&c=5&s=123&g=0&.sig=zHQZiPVzgLReC50UMD151Q";>Factory
automation</a></tt>
</td>
</tr>
</table>
<!-- **end egp html banner** -->
<!-- **begin egp html banner** -->
<br>
<div style="text-align:center; color:#909090;
width:500px;">
<hr style="border-bottom:1px; width:500px;
text-align:left;">
<tt>YAHOO! GROUPS LINKS</tt>
</div>
<br>
<ul>
<tt><li type=square> Visit your group "<a
href="http://groups.yahoo.com/group/xap_automation";>xap_automation</a>"
on the web.<br> </tt>
<tt><li type=square> To unsubscribe from this group,
send an email to:<br> <a href="mailto:xap_automation-unsubscribe@xxxxxxx?subject=Unsubscribe";>xap_automation-unsubscribe@xxxxxxx</a><br> </tt>
<tt><li type=square> Your use of Yahoo! Groups is
subject to the <a href="http://docs.yahoo.com/info/terms/";>Yahoo!
Terms of Service</a>.</tt>
</ul>
<br>
<div style="text-align:center; color:#909090;
width:500px;">
<hr style="border-bottom:1px; width:500px;
text-align:left;">
</div>
<br>
<!-- **end egp html banner** -->
<span style="color: white;"/>__,_._,___</span>
</BODY></HTML>
------=_NextPart_000_0013_01C6B983.A45B2990--
xAP_Automation Main Index |
xAP_Automation Thread Index |
xAP_Automation Home |
Archives Home
|