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 Serial Class


  • Subject: Re: xAP Serial Class
  • From: Stuart Booth
  • Date: Tue, 11 Nov 2003 20:36:00 +0000

On Tue, 11 Nov 2003 20:28:51 -0000, "Paul Barrett"
<<a
href="/group/xAP_developer/post?postID=XUEHVr1YfLmLcF80FuKTRV4IhoIE8EP-ZW5GdxuG7YEqYCFoDLvpywTgzFeupd5x21UzCpQaAVLamc6Ss7Ef">pbarrett@r...</a>>
wrote:

>Yeh, what I was thinking when I wrote the doc was more of the
transmission
>of the xAP Messages on to a serial bus as apposed to a command / data
>specified in a message.
>More for implementing serial bus/bridge/router/gateway rather than an
>endpoint.

D'oh!

The penny drops! I knew that ... somewhere.

>I'm not sure if this is of any real use, maybe I should just write the
>xAP-485 class and not bother with the more generic one. What do you
think?

You could probably use a good chunk of this class as a basis for
Kevin's SerialComms xAPplication and just tweak its operation by
rearranging the objects/classes you use to share code between a
general serial comms app and your gateway application.

One sends the xAP message.
The other uses the contents of a xAP message to drive itself (serial
port setup, data to send).

S
--
Stuart Booth <<a
href="/group/xAP_developer/post?postID=HNw4g1-QhCs_TYyk8UfWXbdB3rEW-1I2y7_RnQUxsXuddHXmPXOJ3s9xJVGCi4c6qsb7GpuugOyEirWgQHFay-Q1">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_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.