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]

Red Rat 3 / IR Schema


  • Subject: Red Rat 3 / IR Schema
  • From: "Michael McSharry" <mcs101main@xxxxxxx>
  • Date: Fri, 11 Jun 2004 21:10:11 -0700

------=_NextPart_000_101D_01C44FF8.7B2B8570
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Someone on the Homeseer Message Board asked about RedRat3 support in
Homeseer.  I noticed that you just released an xap connector for it and my
xapPlugin to homeseer will function as an IR interface to homeseer.  The
schema that I use, however is different that what you have implemented.
I've pasted sections from the homseer xap manual that describe the
Homeseer.IR schema.

I have no problem with implementing a different schema, however I think
tha=
t
there should be some way to find common ground.  The model I'm working
unde=
r
is that a connector should be able to describe the capabilities it is able
to support and then based upon the response the controllling node will know
what commands to send or what notifications to expect.

The Homeseer IR model is a linear IR space where each location in this
spac=
e
represents an IR code.  The space is logically divided into a set of
device=
s
and each device contains a set of keys.  Beyond that there are also zones
where each zone is correlated to a unique IR emitter.  A device can be
assigned a logical name and the same is true for a key within a device. 
Fo=
r
example, a IR device may have capacity for 500 IR codes and these are
logically organized into 36 keys for each of (500/25)=3D 20 devices. 
Devic=
e 1
may be "Slimp3".  Key 1 of device 1 may be given the name
"play".

I set the schema to deal with the linear IR space so only numbers in the
range 1 to 500 would be used to communicate the codes.  I did this because
=
I
viewed the mapping of a code to a function to be at a higer level than the
IR device that is doing the translations between IR pulses and IR codes.

I'm not familiar with the RedRat3, but based upon the schema definition I
assume that it is programmed externally to associate codes with devices and
keys.  The memory of this relationship is then retained within the RedRat3
and these logical names are then used over the serial/usb port from the
RedRat3.

Since my homeseer xap plugin can support any number of IR interfaces it
needs to know what is connected so it can establish a common protocol.  I
noticed that there is pronto-related support in our schema.  What is the
mechanism that can be used to query the network to determine which IR
connector is available?

In my IR.Transmit section I have a Zone key.  Now that I think about it,
this probably should be more like a subaddress where the zone is specified
as part of the header such as you do with the slimp3 player.

1.1.1.1.1   Class Homeseer.IR
1.1.1.1.1.1     Section: IR.Query
Description: Sent to request capabilities of an IR device.  Response
provided by IR.Notification message.

Keys:

Required      Item      Description
None          N/A      N/A

1.1.1.1.1.2     Section: IR.Transmit
Description: Sent to request an IR-capable device to transmit IR code at
specified location.  Header target can be used to select specific IR
provider.

Keys:

Required      Item      Description
No      Unit      Unit designation for box holding the remote IR
No      Zone      Zone designation of IR emitter to be utilized
Yes     Location  IR memory location where learned-code is stored

1.1.1.1.1.3     Section: IR.Match
Description: Used by an xAP application to report results of
Trigger.Condition message.  Because of the timing associated with event
condition processing this xap message is not expected to be utilized, but
i=
s
included for completeness.

Keys:

Required     Item     Description

Yes         Match     IR Number for which match occurred


1.1.1.1.1.1     Section: IR.Notification
Description: Sent by an xAP application that supports IR to describe the IR
configuration.  Sent in response to a IR.Query message

Keys:

Required     Item     Description

No     Zones       Number of zones (assumed =3D 1)
Yes    Keys        Number of keys per logical device
Yes    Devices     Number of logical devices
No     IRMatch     True is able to return IR match
No     Options     True if setup form to be invoked with option selec=
tion



------=_NextPart_000_101D_01C44FF8.7B2B8570
Content-Type: text/html; charset=ISO-8859-1
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=iso-8859-1">
<META content="MSHTML 6.00.2800.1400" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>


<DIV><FONT face=Arial size=2>Someone on the Homeseer Message
Board asked about
RedRat3 support in<BR>Homeseer.&nbsp; I noticed that you just
released an xap
connector for it and my<BR>xapPlugin to homeseer will function as an
IR
interface to homeseer.&nbsp; The<BR>schema that I use, however is
different that
what you have implemented.<BR>I've pasted sections from the homseer
xap manual
that describe the<BR>Homeseer.IR schema.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>I have no problem with
implementing a different
schema, however I think that<BR>there should be some way to find
common
ground.&nbsp; The model I'm working under<BR>is that a connector
should be able
to describe the capabilities it is able<BR>to support and then based
upon the
response the controllling node will know<BR>what commands to send or
what
notifications to expect.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>The Homeseer IR model is a linear
IR space where
each location in this space<BR>represents an IR code.&nbsp; The
space is
logically divided into a set of devices<BR>and each device contains a
set of
keys.&nbsp; Beyond that there are also zones<BR>where each zone
is correlated to
a unique IR emitter.&nbsp; A device can be<BR>assigned a logical
name and the
same is true for a key within a device.&nbsp; For<BR>example, a
IR device may
have capacity for 500 IR codes and these are<BR>logically organized
into 36 keys
for each of (500/25)= 20 devices.&nbsp; Device 1<BR>may be
"Slimp3".&nbsp; Key 1
of device 1 may be given the name
"play".</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>I set the schema to deal with the
linear IR space
so only numbers in the<BR>range 1 to 500 would be used to communicate
the
codes.&nbsp; I did this because I<BR>viewed the mapping of a code
to a function
to be at a higer level than the<BR>IR device that is doing the
translations
between IR pulses and IR codes.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>I'm not familiar with the RedRat3,
but based upon
the schema definition I<BR>assume that it is programmed externally to
associate
codes with devices and<BR>keys.&nbsp; The memory of this
relationship is then
retained within the RedRat3<BR>and these logical names are then used
over the
serial/usb port from the<BR>RedRat3.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>Since my homeseer xap plugin can
support any number
of IR interfaces it<BR>needs to know what is connected so it can
establish a
common protocol.&nbsp; I<BR>noticed that there is pronto-related
support in our
schema.&nbsp; What is the<BR>mechanism that can be used to query
the network to
determine which IR<BR>connector is
available?</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>In my IR.Transmit section I have a
Zone key.&nbsp;
Now that I think about it,<BR>this probably should be more like a
subaddress
where the zone is specified<BR>as part of the header such as you do
with the
slimp3 player.</FONT></DIV>
<DIV><FONT face=Arial
size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>1.1.1.1.1&nbsp;&nbsp;
Class
Homeseer.IR<BR>1.1.1.1.1.1&nbsp;&nbsp;&nbsp;&nbsp;
Section:
IR.Query<BR>Description: Sent to request capabilities of an IR
device.&nbsp;
Response<BR>provided by IR.Notification
message.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>Keys:</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=Arial
size=2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Required&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Item&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Description</FONT></DIV>
<DIV><FONT face=Arial
size=2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
None&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
N/A&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
N/A</FONT></DIV><FONT face=Arial size=2>
<DIV><BR>1.1.1.1.1.2&nbsp;&nbsp;&nbsp;&nbsp;
Section:
IR.Transmit<BR>Description: Sent to request an IR-capable device to
transmit IR
code at<BR>specified location.&nbsp; Header target can be used to
select
specific IR<BR>provider.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Keys:</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Required&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Item&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Description</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
No&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Unit&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Unit designation for
box holding the remote
IR</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
No&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Zone&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Zone designation of
IR emitter to be
utilized</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Yes&nbsp;&nbsp;&nbsp;&nbsp; Location&nbsp;
IR memory location where learned-code is stored</DIV>
<DIV><BR>1.1.1.1.1.3&nbsp;&nbsp;&nbsp;&nbsp;
Section: IR.Match<BR>Description:
Used by an xAP application to report results of<BR>Trigger.Condition
message.&nbsp; Because of the timing associated with
event<BR>condition
processing this xap message is not expected to be utilized, but
is<BR>included
for completeness.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Keys:</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Required&nbsp;&nbsp;&nbsp;&nbsp;
Item&nbsp;&nbsp;&nbsp;&nbsp; Description</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Yes&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Match&nbsp;&nbsp;&nbsp;&nbsp; IR Number for which match
occurred</DIV>
<DIV>&nbsp;</DIV>
<DIV><BR>1.1.1.1.1.1&nbsp;&nbsp;&nbsp;&nbsp;
Section:
IR.Notification<BR>Description: Sent by an xAP application that
supports IR to
describe the IR<BR>configuration.&nbsp; Sent in response to a
IR.Query
message</DIV>
<DIV>&nbsp;</DIV>
<DIV>Keys:</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Required&nbsp;&nbsp;&nbsp;&nbsp;
Item&nbsp;&nbsp;&nbsp;&nbsp; Description</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
No&nbsp;&nbsp;&nbsp;&nbsp;
Zones&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Number of
zones (assumed = 1)</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Yes&nbsp;&nbsp;&nbsp;
Keys&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Number of keys per logical
device</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Yes&nbsp;&nbsp;&nbsp;
Devices&nbsp;&nbsp;&nbsp;&nbsp; Number of logical
devices</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
No&nbsp;&nbsp;&nbsp;&nbsp;
IRMatch&nbsp;&nbsp;&nbsp;&nbsp; True is able to return IR
match</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
No&nbsp;&nbsp;&nbsp;&nbsp;
Options&nbsp;&nbsp;&nbsp;&nbsp; True if setup form to be
invoked with option
selection</DIV>
<DIV>&nbsp;</DIV>
<DIV><BR></FONT>&nbsp;</DIV>

<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=129omth78/M=298184.5022502.6152625.3001176/D=groups/S=1705007709:HM/EXP=1087099827/A=2164339/R=0/SIG=11e2d64in/*http://www.netflix.com/Default?mqso=60183348";
alt=""><img src="http://us.a1.yimg.com/us.yimg.com/a/ne/netflix/yhoo0504_a_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=2164339/rand=962751099";></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>&nbsp;
<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>&nbsp;
<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_101D_01C44FF8.7B2B8570--


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.