[Message Prev][Message
Next][Thread Prev][Thread Next][Message
Index][Thread Index]
RE: Red Rat 3 / IR Schema
- Subject: RE: Red Rat 3 / IR Schema
- From: "Chris Dodge" <chris@xxxxxxxxxxxx>
- Date: Mon, 14 Jun 2004 16:11:47 +0100
------=_NextPart_000_0057_01C4522A.4BABC970
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
Hi,
I'm pretty new to the xAP forums, but as the Redrat developer guy, I've
been
following this thread with interest. I have to say that as I'm not that
familiar yet with either xAP or HomeSeer yet, so am not really sure whether
I can contribute too much to this thread, but I'm very happy to look into
adding additional ways of doing things to the RR SDK if it doesn't
currently
easily support the IR schema you decide on.
Both HomeSeer and the RR core software have been designed for use a single
app, so the idea of a single signal DB and some method of providing a key
to
an IR signal in the DB works well - (device, signal-name) for RR or (index)
for HS. xAp is distrubuted so this doesn't work as well.
What about passing the actual IR data itself around? Instead of saying
"here's a key to an IR signal in a DB that may or may not know
about", pass
the actual bit of IR data itself so that a connector/app when it receives
the data can see whether it recognizes it and take the appropriate action?
I
guess that this is quite a bit more complex - deciding on an IR format
etc.,
but would mean that IR output devices could just output the data without
having to have a DB setup which could be useful for embedded xAP devices.
OR: Pass some DB independant, unambiguous desription of the remote control
and the button that was pressed so that a xAP app/connector could say
"when
that button is pressed I do this". A unique description would probably
need:
manufacturer, e.g. Technics
device type e.g. CD-player
device model e.g. SL-PG520A
remote model (not so improtant)
button name e.g. Play
Not very elegant and probably error prone (e.g. is slpg520a the same as
SL-PG520A)?
Anyway, these are just a few thoughts, and its probably clear from this
that
I'm not very familiar with xAP!
Cheers
Chris
RedRat Ltd.
_____
From: mcs101main@xxxxxxx [mailto:mcs101main@xxxxxxx]
Sent: 14 June 2004 05:36
To: xAP_developer@xxxxxxx
Subject: Re: [xAP_developer] Red Rat 3 / IR Schema
I think we need to decide how we want to manage IR database in general and
then a xap requirements to support this management should flow easily.
There are about 10 IR interfaces currently available with plugins written
for Homeseer. Each of these use the IR Index to identify a signal and the
database of signal to index is a pair of text files.
For sake of discussion assume that there are two XAP connectors for IR
devices and each of these has its own database supported by the IR device
supplier and recognized by the respective XAP IR connector. While
documented well each of these database layouts is unique to the individual
device.
So we have a situation now where in one case the names are maintained by
the
unit which is commanding the IR and in the other case they are maintained
by
the hardware device/connector that receives the command.
In a generalized scenario it should be possible to command different
hardware devices at the same approximate time. Homeseer is oriented to
support only one IR device at time. This is a restriction that does not
need to be propogated into a genalize IR solution.
The simple solution to adding RR/xap connector to Homeseer is to let the
Homeseer user manually enter the Device/signal pairs using the GUI provided
by Homeseer for this purpose. The elegant solution would be for James' and
my Homeseer xap plugins to query the xap-IR connector when an xap-IR
interface is selected to be the Homeseer IR interface and then build the
database used by Homeseer from the query response.
There must be other HA engines besides Homeseer that have the ability to
command IR. How do they handle the situation?
-----------------------
A proposed dual schema shown below uses two section names. What are the
merit of maintaining a single section name in the schema, but require
either
Device/Signal or Location?
Class=IR.Receive
IR.Signal
{
Device=[Name of IR Device e.g. SliMP3]
Signal=[Name of IR signal e.g. Play, Stop, Next]
}
IR.HomeSeer
{
Location=[index value]
}
------=_NextPart_000_0057_01C4522A.4BABC970
Content-Type: text/html; charset=US-ASCII
Content-Transfer-Encoding: 7bit
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0
Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html;
charset=us-ascii"><!-- BEGIN WEBMAIL STATIONERY -->
<STYLE type=text/css>
p {
margin: 0px;
}
</STYLE>
<META content="MSHTML 6.00.2800.1400"
name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><FONT face=Verdana size=2><SPAN
class=830191614-14062004>Hi,</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Verdana size=2><SPAN
class=830191614-14062004></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Verdana size=2><SPAN
class=830191614-14062004>I'm pretty new to the xAP forums, but as the
Redrat
developer guy, I've been following this thread with interest. I have to say
that
as I'm not that familiar yet with either xAP or HomeSeer
yet, so am
not really sure whether I can contribute too much to this thread, but I'm
very
happy to look into adding additional ways of doing things to the RR SDK if
it
doesn't currently easily support the IR schema you decide
on.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Verdana size=2><SPAN
class=830191614-14062004></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Verdana size=2><SPAN
class=830191614-14062004>Both HomeSeer and the RR core software have
been
designed for use a single app, so the idea of a single signal DB
and some
method of providing a key to an IR signal in the DB works well -
(device,
signal-name) for RR or (index) for HS. xAp is distrubuted so this doesn't
work
as well.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Verdana size=2><SPAN
class=830191614-14062004></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Verdana size=2><SPAN
class=830191614-14062004>What about passing the actual IR data itself
around?
Instead of saying "here's a key to an IR signal in a DB that may or
may not know
about", pass the actual bit of IR data itself so that a connector/app
when it
receives the data can see whether it recognizes it and take the appropriate
action? I guess that this is quite a bit more complex - deciding on an IR
format etc., but would mean that IR output devices could
just output
the data without having to have a DB setup which could be useful for
embedded
xAP devices.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Verdana size=2><SPAN
class=830191614-14062004></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Verdana size=2><SPAN
class=830191614-14062004>OR: Pass some DB independant, unambiguous
desription of
the remote control and the button that was pressed so that a xAP
app/connector
could say "when that button is pressed I do this". A unique
description would
probably need:</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Verdana size=2><SPAN
class=830191614-14062004></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Verdana size=2><SPAN
class=830191614-14062004> manufacturer,
e.g.
Technics</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Verdana size=2><SPAN
class=830191614-14062004> device type e.g.
CD-player</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Verdana size=2><SPAN
class=830191614-14062004> device model
e.g.
SL-PG520A</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Verdana size=2><SPAN
class=830191614-14062004> remote model
(not so
improtant)</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Verdana size=2><SPAN
class=830191614-14062004> button name e.g.
Play</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Verdana size=2><SPAN
class=830191614-14062004></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Verdana size=2><SPAN
class=830191614-14062004>Not very elegant and probably error prone (e.g.
is
slpg520a the same as SL-PG520A)?</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Verdana size=2><SPAN
class=830191614-14062004></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Verdana size=2><SPAN
class=830191614-14062004>Anyway, these are just a few thoughts, and its
probably
clear from this that I'm not very familiar with
xAP!</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Verdana size=2><SPAN
class=830191614-14062004></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Verdana size=2><SPAN
class=830191614-14062004>Cheers</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Verdana size=2><SPAN
class=830191614-14062004></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Verdana size=2><SPAN
class=830191614-14062004>Chris</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Verdana size=2><SPAN
class=830191614-14062004>RedRat
Ltd.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Verdana size=2><SPAN
class=830191614-14062004></SPAN></FONT> </DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> mcs101main@xxxxxxx
[mailto:mcs101main@xxxxxxx]
<BR><B>Sent:</B> 14 June 2004
05:36<BR><B>To:</B>
xAP_developer@xxxxxxx<BR><B>Subject:</B> Re:
[xAP_developer] Red Rat 3 /
IR Schema<BR></FONT><BR></DIV>
<DIV></DIV><!-- WEBMAIL STATIONERY noneset -->
<P>I think we need to decide how we want to manage IR database in
general and
then a xap requirements to support this management should flow
easily.
There are about 10 IR interfaces currently available with plugins written
for
Homeseer. Each of these use the IR Index to identify a signal and
the
database of signal to index is a pair of text files.</P>
<P>For sake of discussion assume that there are two XAP connectors
for IR
devices and each of these has its own database supported by the IR device
supplier and recognized by the respective XAP IR connector. While
documented well each of these database layouts is unique to the individual
device.</P>
<P>So we have a situation now where in one case the names are
maintained by the
unit which is commanding the IR and in the other case they are maintained
by the
hardware device/connector that receives the command.</P>
<P>In a generalized scenario it should be possible to command
different hardware
devices at the same approximate time. Homeseer is oriented to
support only
one IR device at time. This is a restriction that does not need
to be
propogated into a genalize IR solution.</P>
<P>The simple solution to adding RR/xap connector to Homeseer is to
let the
Homeseer user manually enter the Device/signal pairs using the GUI provided
by
Homeseer for this purpose. The elegant solution would be for
James' and my
Homeseer xap plugins to query the xap-IR connector when an xap-IR interface
is
selected to be the Homeseer IR interface and then build the database used
by
Homeseer from the query response.</P>
<P>There must be other HA engines besides Homeseer that have the
ability to
command IR. How do they handle the situation?</P>
<P>-----------------------<BR>A proposed dual schema shown
below uses two
section names. What are the merit of maintaining a single section
name in
the schema, but require either Device/Signal or Location?</P>
<P>Class=IR.Receive</P>
<P>IR.Signal<BR>{<BR>
Device=[Name of IR Device e.g.
SliMP3]<BR> Signal=[Name of IR signal
e.g. Play, Stop,
Next]<BR>}<BR>IR.HomeSeer<BR>{<BR>
Location=[index
value]<BR>}<BR></P>
<br>
<!-- **begin egp html banner** -->
<table border=0 cellspacing=0 cellpadding=2>
<tr bgcolor=#FFFFCC>
<td align=center><font size="-1"
color=#003399><b>Yahoo! Groups
Sponsor</b></font></td>
</tr>
<tr bgcolor=#FFFFFF>
<td align=center width=470><table border=0 cellpadding=0
cellspacing=0> <tr> <td align=center><font face=arial
size=-2>ADVERTISEMENT</font><br><a href="http://us.ard.yahoo.com/SIG=129cvk53n/M=298184.5022502.6152625.3001176/D=groups/S=1705007709:HM/EXP=1087312458/A=2164330/R=0/SIG=11eamf8g4/*http://www.netflix.com/Default?mqso=60183350";
alt=""><img src="http://us.a1.yimg.com/us.yimg.com/a/ne/netflix/yhoo0504_testa_300250a052604.gif";
alt="click here" width="300" height="250"
border="0"></a></td></tr></table>
</td>
</tr>
<tr><td><img alt="" width=1 height=1 src="http://us.adserver.yahoo.com/l?M=298184.5022502.6152625.3001176/D=groups/S=:HM/A=2164330/rand=166704207";></td></tr>
</table>
<!-- **end egp html banner** -->
<!-- **begin egp html banner** -->
<br>
<tt><hr width="500">
<b>Yahoo! Groups Links</b><br>
<ul>
<li>To visit your group on the web, go to:<br><a
href="http://groups.yahoo.com/group/xAP_developer/";>http://groups.yahoo.com/group/xAP_developer/</a><br>
<li>To unsubscribe from this group, send an email to:<br><a
href="mailto:xAP_developer-unsubscribe@xxxxxxx?subject=Unsubscribe";>xAP_developer-unsubscribe@xxxxxxx</a><br>
<li>Your use of Yahoo! Groups is subject to the <a href="http://docs.yahoo.com/info/terms/";>Yahoo!
Terms of Service</a>.
</ul>
</tt>
</br>
<!-- **end egp html banner** -->
</BODY></HTML>
------=_NextPart_000_0057_01C4522A.4BABC970--
xAP_Development Main Index |
xAP_Development Thread Index |
xAP_Development Home |
Archives Home
|
![http://us.a1.yimg.com/us.yimg.com/a/ne/netflix/yhoo0504_testa_300250a052604.gif"](http://us.a1.yimg.com/us.yimg.com/a/ne/netflix/yhoo0504_testa_300250a052604.gif"){kind=link}