[Message Prev][Message
Next][Thread Prev][Thread Next][Message
Index][Thread Index]
Re: xAP TSC - A callup request :-), Floorplan TSC
--Apple-Mail-14-831416575
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=windows-1252;
format=flowed;
delsp=yes
http://mi4.biz/files/xapfloorplan/floorplantsctest.zip
Hopefully this is a start. It supports TSC pretty much the same way=20=20
it does with BSC devices. Auto discovery so no need to setup
anything.=20=20
Send commands to set value or setpoints, I would of added setting of=20=20
alarmhi and alarmlo but I couldn't see a suitable schema although
it's=20=20
probably just the same as setpoint though.
All the usual scripts, events, links etc. are there. Display is
pretty=20=20
much like BSC in the config pages, as in sorted by xAP source=20=20
address. On the main pages a new Telemetry tab which groups found=20=20
devices by type, eg Temperature,Voltage etc, it also has a simple
plot=20=20
of current value/setpoint/alarm range/min max to make for a simple=20=20
overview.
New Functions for scripts
Function GetUnit(xAPName) As String
Function GetTSCType(xAPName) As String
Function GetTSCAlarmLo(xAPName) As String
Function GetTSCAlarmHi(xAPName) As String
Should just install over an existing copy.
I am sure once in use with other apps and devices that extra=20=20
functionality will be needed just as like the BSC support evolved but=20=20
as this is built on top of the existing BSC structure it has a better=20=20
start.
It will use TSC. and xAPTSC (spec .42, the one on the wiki) class
of=20=20
messages but it won't work with the previously mentioned off spec TSC=20=20
schema that didn't use sub address and rather used a name=3D parameter.
Anyway let me know if you have any suggestions
James
On 13 Nov 2009, at 14:19, Kevin Hawkins wrote:
> We have a bit of a Catch22 situation with xAP TSC. Until we have
> supporting applications then people don't want to write data
sources=20=20
> and
> vica versa and we can't ratify TSC into xAPTSC until it has some real
> world experience... Hence xAPBSC is being abused as non appropriate
> data is shoehorned in, aprticularly by representing numeric data as a
> text device. So here's a call to xAP Developers to add support for TSC
> within their existing applications and hopefully it will become as
> successful as BSC.
>
> Here's a copy of part of my response to a xAP Automation list post
>
> K
>
> There is a bit of 'chicken & egg' here and so it is worth trying
to=20=20
> see
> if we can get better support for TSC within the key xAP applications -
> especially the ones that already directly support BSC , as most of the
> work is already done.
>
> I know Daniel had mentioned he would look towards supporting TSC , and
> it is particularly well suited towards 1-wire applications ,=20=20
> although I
> would recommend that BSC remains supported , at least transitionally.
> Without such widespread adoption TSC will remain sidelined and BSC
> abused instead. Also there are few test applications to develop
> against which doesn't help people like Mikko. I remember KevinT has
> some however and Lehane uses TSC extensively in his home project.
>
> So I'll revisit my contributions and see what I can do here and
> hopefully a couple of others will too. Many applications will already
> handle TSC as a generic schema as well but having the plug and play
> integration in the same way that we have with TSC would be far=20=20
> preferable
>
>=20
--Apple-Mail-14-831416575
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 7bit
<head>
<style type="text/css">
<!--
/* start of attachment style */
.ygrp-photo-title{
clear: both;
font-size: smaller;
height: 15px;
overflow: hidden;
text-align: center;
width: 75px;
}
div.ygrp-photo{
background-position: center;
background-repeat: no-repeat;
background-color: white;
border: 1px solid black;
height: 62px;
width: 62px;
}
div.photo-title
a,
div.photo-title a:active,
div.photo-title a:hover,
div.photo-title a:visited {
text-decoration: none;
}
div.attach-table div.attach-row {
clear: both;
}
div.attach-table div.attach-row div {
float: left;
/* margin: 2px;*/
}
p {
clear: both;
padding: 15px 0 3px 0;
overflow: hidden;
}
div.ygrp-file {
width: 30px;
valign: middle;
}
div.attach-table div.attach-row div div a {
text-decoration: none;
}
div.attach-table div.attach-row div div span {
font-weight: normal;
}
div.ygrp-file-title {
font-weight: bold;
}
/* end of attachment style */
-->
</style>
</head>
<html><head></head><body style="word-wrap:
break-word; -webkit-nbsp-mode: space; -webkit-line-break:
after-white-space; ">
<!-- **begin egp html banner** -->
<br><br>
<!-- **end egp html banner** -->
<div><br></div><div><br></div><div><a
href="http://mi4.biz/files/xapfloorplan/floorplantsctest.zip";>http://mi4.biz/files/xapfloorplan/floorplantsctest.zip</a></div><div><br></div><div><br></div><div>Hopefully
this is a start. It supports TSC pretty much the same way it does
with BSC devices. Auto discovery so no need to setup anything. Send
commands to set value or setpoints, I would of added setting of alarmhi and
alarmlo but I couldn't see a suitable schema although it's probably just
the same as setpoint though.</div><div>All the usual scripts,
events, links etc. are there. Display is pretty much like BSC in
the config pages, as in sorted by xAP source address. On the main pages a
new Telemet
ry tab which groups found devices by type, eg Temperature,Voltage etc, it
also has a simple plot of current value/setpoint/alarm range/min max to
make for a simple overview.</div><div>New Functions for
scripts</div><div>Function GetUnit(xAPName) As
String</div><div>Function
GetTSCType(xAPName) As String</div><div>Function
GetTSCAlarmLo(xAPName) As String</div><div>Function
GetTSCAlarmHi(xAPName) As
String</div><div><br></div><div>Should just
install over an existing
copy.</div><div><br></div><div>I am sure once
in use with other apps and devices that extra functionality will be needed
just as like the BSC support evolved but as this is built on top of the
existing BSC structure it has a better
start.</div><div><br></div><div>It will use
TSC. and xAPTSC (spec .42, the one on the wiki) class
of messages but it won't work with the previously mentioned off spec TSC
schema that didn't use sub address and rather used a name=
parameter.</div><div><br></div><div><br></div><div>Anyway
let me know if you have any
suggestions</div><div><br></div><div><br></div
><div><br></div><div>James</div><div><br></div><div><br></div><div><br></div><br><div><div>On
13 Nov 2009, at 14:19, Kevin Hawkins wrote:</div><br
class="Apple-interchange-newline"
><blockquote type="cite">
<div style="background-color: rgb(255, 255, 255); position: static;
z-index: auto; ">
<span style="display:none"> </span>
<div id="ygrp-text"><p>We have a bit of a Catch22
situation with xAP TSC. Until we have <br>
supporting applications then people don't want to write data sources and
<br>
vica versa and we can't ratify TSC into xAPTSC until it has some real
<br>
world experience..<wbr>. Hence xAPBSC is being abused as non
appropriate <br>
data is shoehorned in, aprticularly by representing numeric data as a
<br>
text device. So here's a call to xAP Developers to add support for TSC
<br>
within their existing applications and hopefully it will become as
<br>
successful as BSC.<br>
<br>
Here's a copy of part of my response to a xAP Automation list
post<br>
<br>
K<br>
<br>
There is a bit of 'chicken & egg' here and so it is worth trying to
see <br>
if we can get better support for TSC within the key xAP applications -
<br>
especially the ones that already directly support BSC , as most of the
<br>
work is already done. <br>
<br>
I know Daniel had mentioned he would look towards supporting TSC , and
<br>
it is particularly well suited towards 1-wire applications , although I
<br>
would recommend that BSC remains supported , at least transitionally.
<br>
Without such widespread adoption TSC will remain sidelined and BSC
<br>
abused instead. Also there are few test applications to develop
<br>
against which doesn't help people like Mikko. I remember KevinT has
<br>
some however and Lehane uses TSC extensively in his home project.<br>
<br>
So I'll revisit my contributions and see what I can do here and <br>
hopefully a couple of others will too. Many applications will already
<br>
handle TSC as a generic schema as well but having the plug and play
<br>
integration in the same way that we have with TSC would be far
preferable<br>
<br>
</p>
</div>
</div>
<!-- end group email -->
</blockquote></div><br>
<!-- **begin egp html banner** -->
<br>
<br>
<!-- **end egp html banner** -->
<div width="1" style="color: white; clear:
both;"/>__._,_.___</div>
<!-- Start Recommendations -->
<!-- End Recommendations -->
<!-- **begin egp html banner** -->
<img src="http://geo.yahoo.com/serv?s=97476590/grpId=9629476/grpspId=1705007709/msgId=2031/stime=1258311500";
width="1" height="1"> <br>
<!-- **end egp html banner** -->
<!-- **begin egp html banner** -->
<br>
<div style="font-family: verdana; font-size: 77%; border-top: 1px
solid #666; padding: 5px 0;" >
Your email settings: Individual EmailTraditional <br>
<a href="http://groups.yahoo.com/group/xAP_developer/join;_ylc=X3oDMTJmMnZpbXZzBF9TAzk3NDc2NTkwBGdycElkAzk2Mjk0NzYEZ3Jwc3BJZAMxNzA1MDA3NzA5BHNlYwNmdHIEc2xrA3N0bmdzBHN0aW1lAzEyNTgzMTE1MDA-";>Change
settings via the Web</a> (Yahoo! ID required) <br>
Change settings via email: <a href="mailto:xAP_developer-digest@xxxxxxx?subject=Email
Delivery: Digest">Switch delivery to Daily Digest</a> <a
href = "mailto:xAP_developer-fullfeatured@xxxxxxx?subject=Change
Delivery Format: Fully Featured">Switch to Fully Featured</a>
<br>
<a href="http://groups.yahoo.com/group/xAP_developer;_ylc=X3oDMTJkamNwcG10BF9TAzk3NDc2NTkwBGdycElkAzk2Mjk0NzYEZ3Jwc3BJZAMxNzA1MDA3NzA5BHNlYwNmdHIEc2xrA2hwZgRzdGltZQMxMjU4MzExNTAw";>
Visit Your Group
</a>
<a href="http://docs.yahoo.com/info/terms/";>
Yahoo! Groups Terms of Use
</a>
<a href="mailto:xAP_developer-unsubscribe@xxxxxxx?subject=Unsubscribe";>
Unsubscribe
</a>
<br>
</div>
<br>
<!-- **end egp html banner** -->
<div style="color: white; clear:
both;"/>__,_._,___</div>
</body></html>
--Apple-Mail-14-831416575--
xAP_Development Main Index |
xAP_Development Thread Index |
xAP_Development Home |
Archives Home
|