The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024

Latest message you have seen: RE: Re: Now trying xAP Desktop.... but not displaying any info?


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

Re: Heartbeats and Hardware sub nodes


  • Subject: Re: Heartbeats and Hardware sub nodes
  • From: Stuart Booth
  • Date: Sat, 13 Dec 2003 11:07:00 +0000

On Fri, 12 Dec 2003 22:45:07 -0000, "Kevin Hawkins"
<<a
href="/group/xap_automation/post?postID=AoOKyteKc9S4QlYOpyRaK5uoP0OPfktzjCJ8XBdK9-2EF8angJDW6C1OTCSgbIPW21lVOvT0WbN0e2e47DJA">lists@u...</a>>
wrote:

>Absolutely right - if anything changes after the : in the address then
it is
>still the same application and hence needs only the one heartbeat. The
last
>two digits of the UID must change though if you have different sub
>addresses.

No problem. When I was incrementing the UID values for the hardware
subaddresses I accidentally did it on the main device's own UID, so it
ended up altering the h/b that is pumped out. I only noticed when it
wasn't being removed from the Hub until it timed out as not
responding.

So the SliMP3 Connector has a UID of FF123400 and that's where the h/b
message comes from.

But each SliMP3 Player has its own unique UID of FF123401, FF123402,
etc, and no additional h/b required.

S
--
Stuart Booth <<a
href="/group/xap_automation/post?postID=PkXaaEKrvhdEcZxD_ZBqTTNEqL5R0LlYNYprh2jVZ1xCpqoqUqVxcrYZHuKWbkUId-6tIk_yGbR337Eo4w">stuart@x...</a>>
xAPFramework.net - a xAP software development framework for .net

<a href="http://www.xapautomation.org/";>http://www.xapautomation.org/</a>
<a href="http://www.xapframework.net/";>http://www.xapframework.net/</a>





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.