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: so as theres a xPL-xAP gateway, can homeseer talk to xPL?


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

RE: Osd Row Question


  • Subject: RE: Osd Row Question
  • From: Keith Doxey
  • Date: Tue, 20 May 2003 16:47:00 +0000

If you remember the Pic Basic code I showed you I was using 2 ASCII
characters for all numeric values eg 02, 23, 45 even though internally my
program wanted a single decimal value eg 2, 23, 45.

PicBasicPro makes it a doddle to receive this on the serial port by
specifying [DEC2 myVar].

If it received the ASCII characters "2" and "Q" it
realises than the "Q" is
not a number and returns from the function with the desired value of 2
anyway!

Unfortunately you still have to send it two numbers because the
"Q" would be
discarded in the process.

There is also a similar function that receives 0-9 A-F as HEX so there is
no
need to ever send the single byte 0xFE when you can send ASCII characters F
and E provided that your PIC code knows when to expect them.

I will be looking very closely at xPL and A.N.OtherProtocol to see if a
gateway can be incorporated into my design. Creating the outgoing messages
is a doddle as it is just a case of putting a wrap around the data that I
will already have. Parsing incoming messages is more complex and processor
hungry as not all messages would be relevant to me.

What I plan on trying is this....

MAIN_PIC_TX---------------------------Outgoing_Message
MAIN_PIC_RX-----TX_GATEWAY_PIC_RX-----Incoming_Message

The incoming messages would be received by another PIC which would
constantly be looking for messages targeted at me and upon receipt of a
suitable message it would remove the wrap, format the data to the KAT5
protocol for the main processor to deal with.

The main PIC can easily apply the fixed format wrap to the outgoing message
with very little overhead.

Just one brief question... does xPL use the same port as xAP and if so, is
it possible that someone could run both?

Keith

www.diyha.co.uk
www.kat5.tv


> -----Original Message-----
> From: Ian Lowe [mailto:<a
href="/group/ukha_xpl/post?postID=QV6YOw-HzXwzHMqTsY1bCPcfgSlgy7b2VoJfZeAEN_M0Pmdv6T-aZhxs7NfyHoK7nHNQ-8Ajh01IRql6Vgcs">ian@w...</a>]
> Sent: 20 May 2003 15:25
> To: <a
href="/group/ukha_xpl/post?postID=st4hOIgasX215ozXpsCCfdl6YvalUokJNbnW-3QESBqnVS-elOI-2m-BA0mAsvol3768kfh7LWIynqZ7REVgccU">ukha_xpl@xxxxxxx</a>
> Subject: Re: [ukha_xpl] Osd Row Question
>
>
> ----- Original Message -----
> From: "John" <<a
href="/group/ukha_xpl/post?postID=6KYetDZA3lykXrTfvAg-ohKgr_8Jdldce-0cAKHqMCD9ing05Js-BV1sZORshMzfVsTRg_y6oLasAG0qYwD3EeRBGCFqRNLX49qn">home-automation@j...</a>>
> To: <<a
href="/group/ukha_xpl/post?postID=st4hOIgasX215ozXpsCCfdl6YvalUokJNbnW-3QESBqnVS-elOI-2m-BA0mAsvol3768kfh7LWIynqZ7REVgccU">ukha_xpl@xxxxxxx</a>>
> Sent: Tuesday, May 20, 2003 2:29 PM
> Subject: Re: [ukha_xpl] Osd Row Question
>
>
> > Hi Frank,
> >
> > I'd stick with using the ASCII characters - at least that
> way it will be
> > easier to read your messages using the xPL monitor.
>
> Yep, this is something we need to revisit with some of the
> original data
> formats as well: rather than using arbitrary binary values,
> we need to make
> sure these things are encoded in a standard way: it's one of
> the key things
> I spoke about in my Sunday presentation at UKHA2003 (which
> was reasonably
> technical)
>
> There are a few formats at the moment that will be formed up
> over the coming
> days and weeks. It's really important to get these right at
> this stage, as
> modding the data formats at a later date will break things.
>
> > I'm not even sure if binary characters are allowed - I'm
> sure Tony/Ian
> > will confirm.
>
> Nope. ASCII Characters at all times over the wire.
>
> Also, where a "gateway" application translates between a low
> level protocol
> (like Keith's KAT5 Switcher for example) and the xPL network,
> the gateway is
> expected to translate the low level control codes into something more
> meaningful..
>
> Keith and I discussed this at UKHA2003 on the last day, and
> whereas the KAT5
> switcher uses a command (from memory!) like ^V4S12 to tell
> the switch to
> output AV Source twelve, on output 4, the "on the wire" xPL
> version of the
> command would be:
>
> ZONE=4
> SOURCE=12
>
> Or possibly using labels to make the "4" and "12"
a little
> more readable. In
> any case, the gateway app/hardware is expected to carry out
> the required
> conversion.
>
> Ian.
>
>
>
> ------------------------ Yahoo! Groups Sponsor
> ---------------------~-->
> Get A Free Psychic Reading!
> Your Online Answer To Life's Important Questions.
> <a href="http://us.click.yahoo.com/aM1XQD/od7FAA/uetFAA/h6uqlB/TM";>http://us.click.yahoo.com/aM1XQD/od7FAA/uetFAA/h6uqlB/TM</a>
> --------------------------------------------------------------
> -------~->
>
> xPL Links: <a href="http://www.xplproject.org.uk";>http://www.xplproject.org.uk</a>
<a href="http://www.xplhal.com";>http://www.xplhal.com</a>
<a href="http://www.xpl.myby.co.uk";>http://www.xpl.myby.co.uk</a>
To Post a Message: <a
href="/group/ukha_xpl/post?postID=st4hOIgasX215ozXpsCCfdl6YvalUokJNbnW-3QESBqnVS-elOI-2m-BA0mAsvol3768kfh7LWIynqZ7REVgccU">ukha_xpl@xxxxxxx</a>
To Subscribe: <a
href="/group/ukha_xpl/post?postID=qhTnAnDgh3Sj-GGdomLeGdr0Z37w2Wk1QWFZABTGCgDgyh-a8CstxuK8E5_Y_GMZBF8FFpO35zHROanhXW8sOpi0h-PM8K0x4w">ukha_xpl-subscribe@xxxxxxx</a>
To Unsubscribe: <a
href="/group/ukha_xpl/post?postID=5LoTyvFfZtoFzsH4yjNPSd0VfTDuCubp606yqVMszVtSTO1xj4YHRRLKagPG3p6hs-aMknVXu8AFjb4wbPP2YQrr5q60PZ59IsvlGuE">ukha_xpl-unsubscribe@xxxxxxx</a>

Your use of Yahoo! Groups is subject to <a href="http://docs.yahoo.com/info/terms/";>http://docs.yahoo.com/info/terms/</a>







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