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: Managed to break it.


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

Re: OSD Schema Questions


  • Subject: Re: OSD Schema Questions
  • From: Frank Mc Alinden
  • Date: Sat, 13 Sep 2003 10:30:00 +0000

Hi Tony


>I havent fully implemented it for tivoosd yet. Though I >have
implemented
>triggers for the main commands

Are you saying Tony that TIVO replys with a copy of the message it received
???
If this is so ...has anyone done it using a pic / atmel.. controller ...

Frank






----- Original Message -----
From: Tony Tofts
To: <a
href="/group/ukha_xpl/post?postID=9CU6Qg4O5si9DuLJv0dB8Olz-FkGtfyUxUFxX65fDcGysxb3AkbfgCet3ElXKcCwGcCPTxqx0tKDH3ymtZrhkwrT1w">ukha_xpl@xxxxxxx</a>
Sent: Saturday, September 13, 2003 7:23 PM
Subject: RE: [ukha_xpl] OSD Schema Questions


> Hoping to have some free time soon to work on my osd
> project and decided to download the latest OSD
> Schema...Noticed a couple of changes
> ....Exclusive/Release......It is compulsory to incorporate
> these commands???

Not compulsory, but it should be noted in documentation somewhere so the
user knows.

> and any examples of how its used..???

The idea is that if an xpl message requests exclusive use, then the
device/app should ignore requests from other app's/devices until a release
is received from the same device/app. I use it, for example, to allow the
rio to display it's menu on the tivo without the chance of another
app/device ruining the display.

> Also
> is the trigger Message compulsory????

I havent fully implemented it for tivoosd yet. Though I have implemented
triggers for the main commands.

Regards
Tony



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.