The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

RE: Re: xAP Framework - x10 Connector




------=_NextPart_000_0017_01C4B70B.209363B0
Content-Type: text/plain;
charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

Replying offlist; will post summary when we've come to an understanding...

-----Original Message-----
From: Alistair Watkins [mailto:ukha@xxxxxxx]=20
Sent: 19 October 2004 20:39
To: xAP_developer@xxxxxxx
Subject: [xAP_developer] Re: xAP Framework - x10 Connector



Edward,

Sorry in the delay in replying, heve been kinda side tracked..
Looking at the log, I see the following:

19/10/2004 20:30:49 : ---------------------
19/10/2004 20:30:49 : Start log: 20:30:49 19 October 2004
19/10/2004 20:30:49 : Sending status request
19/10/2004 20:30:49 : R:ff R:ff R:29 R:1e R:0a R:24 R:84 R:67 R:00=20
R:00 R:00 R:00 R:00 R:00 Got status
19/10/2004 20:30:49 : Received status response =3D> unit present
19/10/2004 20:31:07 : Send 2 bytes
19/10/2004 20:31:07 : T:04 T:56=20
19/10/2004 20:31:07 : R:5a Got poll, send poll ack
19/10/2004 20:31:07 : T:c3=20
19/10/2004 20:31:07 : Rx interrupted Tx
19/10/2004 20:31:12 : Transmit timeout, txState =3D interrupted
19/10/2004 20:31:12 : Resend 2 bytes, attempt 1, txState =3D interrupted
19/10/2004 20:31:12 : T:04 T:56=20
19/10/2004 20:31:12 : R:5a Too slow responding to poll, try again
19/10/2004 20:31:17 : Transmit timeout, txState =3D checksumPending
19/10/2004 20:31:17 : Resend 2 bytes, attempt 2, txState =3D=20
checksumPending
19/10/2004 20:31:17 : T:04 T:56=20
19/10/2004 20:31:17 : R:5a Got poll, send poll ack
19/10/2004 20:31:17 : T:c3=20
19/10/2004 20:31:17 : Rx interrupted Tx
19/10/2004 20:31:22 : Transmit timeout, txState =3D interrupted
19/10/2004 20:32:27 : Tried to send in txState =3D interrupted

now, I can see there are errors there, but I dont know why they are=20
happening.  the only thing I can think of it maybe due to is the=20
speed of my machine? I'm running this off my ITX box, which is=20
running Apache as well.. and Windows 2k, so its pretty slugish, dunno=20
if this is the problem though!

Any thoughts?

thanks,

alistair






--- In xAP_developer@xxxxxxx, "Edward Pearson"=20
<edward.mailgroup@b...> wrote:
> Alistair,
>=20=20
> The .net X10 connector is two-way so it should behave as you=20
describe.
> It'd be helpful if you could take a look at the log file that it=20
produces,
> commlog.txt which you will find alongside the plugin dll. This=20
documents all
> the interactions with the CM11.
>=20=20
> One comment on your message below: you say, "this would then
toggle=20
the G1
> light and turn it off", it would turn it on (maybe that's just
a=20
typo), and
> there's no 'toggle' function, you have to send 'command=3Don' and
> 'command=3Doff' explicitly.
>=20=20
> I'm now going to go and plug my X10 stuff together and check it=20
out - I've
> still not unpacked from UKHA04!
>=20=20
> Edward
>=20
> -----Original Message-----
> From: Alistair Watkins [mailto:ukha@a...]=20
> Sent: 05 July 2004 22:59
> To: xAP_developer@xxxxxxx
> Subject: [xAP_developer] xAP Framework - x10 Connector
>=20
>=20
> Hi.
>=20
> been toying with xAP for a while, but am actually trying to make=20
use=20
> of it now.
> I had used patricks Linux xAP X-10 connector, but now I have=20
migrated=20
> the server over to windows I'm looking at the .NET stuff, but I=20
cant=20
> seem to figure out the 'new' x10 connector!
>=20
> with patricks proggy i send (something simular to) :
>=20
>     xap-header
>     {
>         v=3D12
>         hop=3D1
>         uid=3DFF123400
>         class=3Dxap-x10.request
>         source=3Dhome.webserver.php
>         target=3DERSP.X10.kevin
>     }
>     xap-x10.request
>     {
>         command=3DOn
>         device=3DG1
>     }
>=20
> this would then toggle the G1 light and turn it off. but with=20
> the .net connector nothing seems to be sent to the powerline (G1=20
> stays off), but i do get an x10-event message back.
>=20
>     xap-header
>     {
>         v=3D12
>         hop=3D1
>         uid=3DFF182000
>         class=3DxAP-X10.Event
>         source=3DERSP.X10.kevin
>     }
>     xAP-X10.Event
>     {
>         command=3DOn
>         device=3DG1
>     }
>=20
> which is exactly the same as the connector sends when i put an x10=20
> command on the powerline.
>=20
> is this functioning correctly? does the connector not pass on xAP
>=20
> x10 messages?
>=20
> I am pretty sure that the connecter is talking to the CM12U as it=20
> sends a message when i send an x10 command...  Im using the xFX=20
> Message viewer on my PC to see the messages.
>=20
> Well if you need any more further info, please ask!
>=20
> Thanks Guys,
>=20
> Alistair
> (cant wait to get the doorbell xAPified!)
>=20
>=20
>=20
>=20
> Yahoo! Groups Sponsor=20=20=20=20=20=20
>=20
> ADVERTISEMENT
>=20=20
>=20
<http://us.ard.yahoo.com/SIG=3D129thrcrq/M=3D295196.4901138.6071305.300117
6/D=3Dgr
>=20
oups/S=3D1705007709:HM/EXP=3D1089151202/A=3D2128215/R=3D0/SIG=3D10se96mf6/*=
http:
//comp
> anion.yahoo.com> click here=20=20=20=20=20=20
>=20=20
> <http://us.adserver.yahoo.com/l?
M=3D295196.4901138.6071305.3001176/D=3Dgroups/S=3D
> :HM/A=3D2128215/rand=3D801350260>=20=20=20=20=20=20=20
>=20
>=20
>   _____=20=20
>=20
> Yahoo! Groups Links
>=20
>=20
> *      To visit your group on the web, go to:
> http://groups.yahoo.com/group/xAP_developer/
>=20=20=20
>=20
> *      To unsubscribe from this group, send an email to:
> xAP_developer-unsubscribe@xxxxxxx
> <mailto:xAP_developer-unsubscribe@xxxxxxx?
subject=3DUnsubscribe>=20
>=20=20=20
>=20
> *      Your use of Yahoo! Groups is subject to the Yahoo! Terms of=20
Service
> <http://docs.yahoo.com/info/terms/>
.






xAP_Development Main Index | xAP_Development Thread Index | xAP_Development Home | Archives Home

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.