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: xAP Plugin for HouseBot - a touchscreen based frontend.


  • Subject: Re: xAP Plugin for HouseBot - a touchscreen based frontend.
  • From: "Kevin Hawkins" <yahoogroupskh@xxxxxxxxxxxxxx>
  • Date: Thu, 01 May 2008 22:24:36 -0000

--- In xap_automation@xxxxxxx, "Taras" <tartheode@...>
wrote:

>
> The first hurdle for my xAP driver appears to be basic
> communications! My first baby step is to create a simple listener but
> I've had no luck establishing an Ethernet connection.
>
> Assuming a xAP hub is running on localhost, what should I point
> Premise's TCP/IP driver to?  Localhost, yes?  What port should it be
> listening to? 3639? 3640? Other?


xAP uses UDP - I suspect you are trying to create a TCP connection.
The reason we use UDP is that we wanted every device to be able to
hear/control every other device. This is only practical with a
broadcast protocol like UDP.  When routing xAP over the internet we do
of course use TCP for reliability.

Assuming you have another xAP application on the same PC you will
need to have a xAP hub installed and running as the very first xAP
application. This is because Windows can't share incoming ports so the
hub acts as a realy - it must be able to acquire port 3639 so must
launch first.  Basically in your application you should acquire any
free port (recommended above 32767) and when you send your first xAP
heartbeat, to the broadcast address port 3639,   the hub will see the
port that your application is listening on and then start to forward
all xAP messages to you.

You can use xAP Viewer to see your outgoing messages.

cheers Kevin
>



------------------------------------


xAP_Automation Main Index | xAP_Automation Thread Index | xAP_Automation 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.