[Message Prev][Message
Next][Thread Prev][Thread Next][Message
Index][Thread Index]
Re: Barionet xAP code
- Subject: Re: Barionet xAP code
- From: Andre Van Der Merwe <andrevdm@xxxxxxxxx>
- Date: Fri, 6 Jun 2008 05:56:29 -0700 (PDT)
--0-224642887-1212756989=:10642
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Brilliant, i replaced the "Text=3D" with
"DisplayText=3D" and the info goes=
correctly through to Homeseer. the device status is now still
displays&nbs=
p;"24.5 C" and the DeviceString is 24.5 C BUT the DeviceValue is
392 which =
conforms to the Level=3D392/4095 BSC schema. This is really handy for
accur=
ate control in HS.=20
thanks
--- On Fri, 6/6/08, Kevin Hawkins <yahoogroupskh@xxxxxxx>
wrot=
e:
From: Kevin Hawkins <yahoogroupskh@xxxxxxx>
Subject: Re: [xap_automation] Barionet xAP code
To: xap_automation@xxxxxxx
Date: Friday, June 6, 2008, 11:35 AM
Hi Andre,
I just had a quick look over the code and we need to tweak it a=20
little...
In xAP BSC there are three types of endpoints, binary, level and=20
text and an endpoint can only be of one type, although all level and=20
text devices carry a state parameter. Should a device/endpoint be more=20
complex then it is presented as two or more independent endpoint values=20
(or you use a different schema). In your adaption you have presented a=20
1-wire sensor as both level based and text based which is not=20
supported. All devices must carry a binary state=3D parameter and so the=20
mixed level/text device happens to be the only combination that can't be=20
used. However , conveniently - you can present a text string within a=20
level based device by including a displaytext=3D parameter :-)=20
I believe the mcs xAP HomeSeer plugin supports this same mapping of=20
this parameter value into device values . As you wish to transfer both=20
the level and the text I think it's best for your usage to change the=20
text=3D to displaytext=3D , rather than drop the level and create a pure=20
text device. Maybe you could try it within HomeSeer and confirm this=20
works ok for you ??
Not supported as it is a hybrid level/text device.
input.state
{
State=3D
Level=3D
Text=3D
}
This is OK and recommended
input.state
{
State=3D
Level=3D
DisplayText=3D
}
and this is OK
input.state
{
State=3D
Text=3D
}
and so is this should you wish
input.state
{
State=3D
Text=3D
DisplayText=3D
}
I'm sure you will have found it but the xAP BSC v1.3 schema is=20
documented at
http://www.xapautom
ation.org/ index.php? title=3DBasic_ Status_and_ Contro=
l_Schema
Cheers Kevin
Andre Van Der Merwe wrote:
>
> the xAPBSC now passes the correct 1-wire temperature through to=20
> Homeseer. In the attached word document the changed text is=20
> highlighted. The device status displays correctly. the
DeviceString=20
> contains the temperature in resolution of .1 degrees celcius ie
23.1.=
=20
> However the DeviceValue contains a rounded integer degree celcius
ie=20
> 23. For higher accuracy control in HSconvert the DeviceValue to
variab=
le.
>
>=20
>
> Change the extention from .doc to .bas to tokenize.
>
> --- On *Wed, 6/4/08, Kevin Hawkins /<yahoogroupskh@
googlemail. com=
>/*=20
> wrote:
>
> From: Kevin Hawkins <yahoogroupskh@ googlemail. com>
> Subject: Re: [xap_automation] Barionet xAP code
> To: xap_automation@ yahoogroups. com
> Date: Wednesday, June 4, 2008, 11:07 PM
>
> Glad it's working Andre ,
>
> I'm finding a few issues with the code and I'm adding a few bits
as
> I progress. It's likely I'll release an update in a week or so any
> changes you want let me know - if you can highlight the actual
code
> changed that would be great. Please use copious comments too.
>
> Re the decimal values - BSC doesn't support these either - nor
does
> it support negative values. What you can do however is to report
them
> as a displaytext parameter within a BSC block - and you can form
the
> decimal number by using scaled integer arithmetic in BCL and then
> create
> a string and insert the decimal point
>
> displaytext=3D 51.24=B0c
>
> Or you could abandon the level based BSC device altogether and use
a
> text one instead text=3D-11.25=B0F
>
> Actually, and more approriately for such 'telemetry' data we have
> another schema called TSC , it's not as universal as BSC yet but
> we hope
> eventually it will become so. - the spec for BSC and TSC are on
> the xAP
> website
>
> http://www.xapautom ation.org/ index.php?
title=3DSchema
> <http://www.xapautom ation.org/ index.php?
title=3DSchema>
>
> Kevin
>
> Andre Van Der Merwe wrote:
> >
> > Hi Kevin,
> >
> >
> >
> > no you answered my questions. i have just not checked
this email
> recently.
> >
> >
> >
> > the system is now working and i am getting the 1-wire
> temperatures out
> > fine. Unfortunately the Barionet BCL code does not
support floati=
ng
> > point variables, so I can only get integer degree celcius
out.
> If is
> > use the correct xAP schema , typically 23degC corresponds
to
> 368/4096..
> > this works great.
> >
> >
> >
> > Now i am working on getting the 368/4096 to make some
sence in
> homeseer.
> >
> >
> >
> > I made some changes to the code to achieve the above.
Also in
> the code
> > it refers to a "config.txt" file which should
change to
> "xapcfg.txt" .
> > Shall i send the update ?
> >
> > --- On *Tue, 6/3/08, Kevin Hawkins
/<yahoogroupskh@ googlemail=
..
> com <mailto:yahoogroups kh%40googlemail.
com>>/*
> > wrote:
> >
> > From: Kevin Hawkins <yahoogroupskh@ googlemail.
com
> <mailto:yahoogroups kh%40googlemail.
com>>
> > Subject: Re: [xap_automation] Barionet xAP code
> > To: xap_automation@ yahoogroups. com
> <mailto:xap_
automation% 40yahoogroups. com>
> > Date: Tuesday, June 3, 2008, 11:58 AM
> >
> > Andre,
> >
> > Phew....We seem to have a communication problem..
> >
> > I responded to a post you made a few days back in the xAP
mi4
> > plugin area on the HomeSeer BBS where you were actually
using
> the mcs
> > plugin - fortunately Michael saw it anyway. Also on the
Barix
> > Barionet
> > forum last week I responded too and you said you already
had the
> > code..
> > I have taken a look at the Barionet xAP code (the BSC
v1.3
> > version) and
> > so I dusted off my own Barionet, re-tokenized it and it
loaded
> > fine. I
> > posted some detailed instructions there as to how to do
this. Qui=
te
> > why it was dusty I'm not sure as it's a great device on
xAP and I
> > shall
> > be using it now going forwards :-)
> >
> > Since then, with Edwards permission, I have updated the
code
> > slightly to fix a couple of issues I spotted and I have
sent you =
two
> > revised versions by email . I also sent you directly by
email the
> > .cob
> > file so you could load it directly into your Barionet -
assuming =
you
> > have the latest firmware - but I haven't been able to get
any inf=
o
> > from
> > you as to which Barionet firmware you are running. Then
you poste=
d
> > a HomeSeer plugin issue question and so I tried it out
here and i=
t
> > worked fine but I noticed you were still not using the
latest
> > firmware I
> > sent you :-(
> >
> > So I don't know what more we can do... Please can you
check your
> > email and try those most recent versions I sent you. They
work
> > perfectly well here. You seem to be using an old xAP v1.2
/ BSC v=
1.2
> > version still. You can of course use the previous BSC
v1.3 versio=
n
> > direct from Edward but you will manually have to fix a
couple of
> > issues
> > that I have already corrected in my version. You will
need to
> address
> > the 'state =3D' vs 'state=3D' parameter name and also
levels are
> > mistakenly
> > reported in the state=3D parmeter eg state=3D100/1024 .
In my ver=
sion
> > '12b' 1.12 this is already fixed for you.
> >
> > Over the next few weeks I shall be revising the code to
hopefully
> > support new features that later Barionet firmward now
offers eg
> > counters
> > and more 1-wire sensors, maybe threshold settings for the
state=
=3D
> > parameter in level devices. The revision I already
released provi=
des
> > compliance with both xAP v1.3 and BSC v1.3. Please let me
know
> > anything you would like to have added here, although for
any cust=
om
> > changes you are free to adapt the source code anyway.
> >
> > Let us know how you want to move forward.....
> >
> > Kevin
> >
> > andrevdm wrote:
> > >
> > > Hi Edward,
> > >
> > > on you blueyonder website you invite to contact
you if
> interested in
> > > your .bas code for the xAP version 1.3.
> > >
> > > is it still available ?
> > >
> > > regards
> > >
> > > Andre
> > >
> > >
> >
> >
> >
>
>
>=20
=20
=20=20=20=20=20=20
--0-224642887-1212756989=:10642
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<html><head>
<style type=3D"text/css">
<!--
#ygrp-mkp{
border: 1px solid #d8d8d8;
font-family: Arial;
margin: 14px 0px;
padding: 0px 14px;
}
#ygrp-mkp hr{
border: 1px solid #d8d8d8;
}
#ygrp-mkp #hd{
color: #628c2a;
font-size: 85%;
font-weight: bold;
line-height: 122%;
margin: 10px 0px;
}
#ygrp-mkp #ads{
margin-bottom: 10px;
}
#ygrp-mkp .ad{
padding: 0 0;
}
#ygrp-mkp .ad a{
color: #0000ff;
text-decoration: none;
}
-->
</style>
</head>
<body>
<table cellspacing=3D'0' cellpadding=3D'0' border=3D'0'
background=3D'none'=
style=3D'font-family:arial;font-size:10pt;color:#000000;background-color:#=
ffffff;width:100%;'><tr><td valign=3D'top' style=3D'font:
inherit;'><P>Bril=
liant, i replaced the "Text=3D" with "DisplayText=3D"
and the info goes cor=
rectly through to Homeseer. the device status is now still
displays "2=
4.5 C" and the DeviceString is 24.5 C BUT the DeviceValue is 392 which
conf=
orms to the Level=3D392/4095 BSC schema. This is really handy for accurate
=
control in HS. </P>
<P><BR>thanks<BR>--- On <B>Fri, 6/6/08, Kevin
Hawkins <I><yahoogroupskh@=
googlemail.com></I></B> wrote:<BR></P>
<BLOCKQUOTE style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px;
BORDER-LEFT: rgb(=
16,16,255) 2px solid">From: Kevin Hawkins
<yahoogroupskh@xxxxxxx&=
gt;<BR>Subject: Re: [xap_automation] Barionet xAP code<BR>To:
xap_automatio=
n@xxxxxxx<BR>Date: Friday, June 6, 2008, 11:35 AM<BR><BR>
<DIV id=3Dyiv1399347317>
<DIV id=3Dygrp-text>
<P>Hi Andre,<BR><BR>I just had a quick look over the code
and we need to tw=
eak it a <BR>little...<BR><BR>In xAP BSC there are three
types of endpoints=
, binary, level and <BR>text and an endpoint can only be of one type,
altho=
ugh all level and <BR>text devices carry a state parameter. Should a
device=
/endpoint be more <BR>complex then it is presented as two or more
independe=
nt endpoint values <BR>(or you use a different schema). In your
adaption yo=
u have presented a <BR>1-wire sensor as both level based and text
based whi=
ch is not <BR>supported. All devices must carry a binary state=3D
parameter=
and so the <BR>mixed level/text device happens to be the only
combination =
that can't be <BR>used. However , conveniently - you can present a
text str=
ing within a <BR>level based device by including a displaytext=3D
parameter=
:-) <BR><BR>I believe the mcs xAP HomeSeer plugin supports this
same mappi=
ng of <BR>this parameter value into device values . As you wish to
transfer both <BR>the level and the text I think it's best for your
usage =
to change the <BR>text=3D to displaytext=3D , rather than drop the
level an=
d create a pure <BR>text device. Maybe you could try it within
HomeSeer and=
confirm this <BR>works ok for you ??<BR><BR>Not supported
as it is a hybri=
d level/text
device.<BR>input.state<BR>{<BR>State=3D<BR>Level=3D<BR>Text=3D=
<BR>}<BR><BR>This is OK and
recommended<BR>input.state<BR>{<BR>State=3D<BR>=
Level=3D<BR>DisplayText=3D<BR>}<BR><BR>and this is
OK<BR>input.state<BR>{<B=
R>State=3D<BR>Text=3D<BR>}<BR><BR>and so is this
should you wish<BR>input.s=
tate<BR>{<BR>State=3D<BR>Text=3D<BR>DisplayText=3D<BR>}<BR><BR>I'm
sure you=
will have found it but the xAP BSC v1.3 schema is <BR>documented
at<BR><A =
href=3D"http://www.xapautomation.org/index.php?title=3DBasic_Status_and_Con=
trol_Schema" target=3D_blank rel=3Dnofollow>http://www.xapautom ation.org/ =
index.php? title=3DBasic_ Status_and_
Control_Schema</A><BR><BR>Cheers Kevi=
n<BR><BR>Andre Van Der Merwe
wrote:<BR>><BR>> the xAPBSC now passes the
correct 1-wire temperatur=
e through to <BR>> Homeseer. In the attached word document the
changed t=
ext is <BR>> highlighted. The device status displays
correctly. the Devi=
ceString <BR>> contains the temperature in resolution of .1
degrees celc=
ius ie 23.1. <BR>> However the DeviceValue contains a rounded
integer de=
gree celcius ie <BR>> 23. For higher accuracy control in
HSconvert the D=
eviceValue to variable.<BR>><BR>>
<BR>><BR>> Change the extenti=
on from .doc to .bas to tokenize.<BR>><BR>> ---
On *Wed, 6/4/08, Kevi=
n Hawkins /<<A href=3D"mailto:yahoogroupskh%40googlemail.com";
target=3D_=
blank rel=3Dnofollow>yahoogroupskh@ googlemail. com</A>>/*
<BR>> wrot=
e:<BR>><BR>> From: Kevin Hawkins <<A
href=3D"mailto:yahoogroupskh%=
40googlemail.com" target=3D_blank rel=3Dnofollow>yahoogroupskh@
googlemail.=
com</A>><BR>> Subject: Re: [xap_automation]
Barionet xAP code<BR>>=
; To:
<A href=3D"mailto:xap_automation%40yahoogroups.com";
target=3D_blank rel=3D=
nofollow>xap_automation@ yahoogroups. com</A><BR>>
Date: Wednesday, June=
4, 2008, 11:07 PM<BR>><BR>> Glad it's working
Andre ,<BR>><BR>>=
; I'm finding a few issues with the code and I'm adding a few bits
as<BR>&g=
t; I progress. It's likely I'll release an update in a week or so
any<BR>&g=
t; changes you want let me know - if you can highlight the actual
code<BR>&=
gt; changed that would be great. Please use copious comments
too.<BR>><B=
R>> Re the decimal values - BSC doesn't support these either -
nor does<=
BR>> it support negative values. What you can do however is to
report th=
em<BR>> as a displaytext parameter within a BSC block - and
you can form=
the<BR>> decimal number by using scaled integer arithmetic in
BCL and t=
hen<BR>> create<BR>> a string and insert the
decimal point<BR>><BR=
>> displaytext=3D 51.24=B0c<BR>><BR>>
Or you could abandon the lev=
el
based BSC device altogether and use a<BR>> text one instead
text=3D-11.=
25=B0F<BR>><BR>> Actually, and more approriately
for such 'telemetry'=
data we have<BR>> another schema called TSC , it's not as
universal as =
BSC yet but<BR>> we hope<BR>> eventually it will
become so. - the spe=
c for BSC and TSC are on<BR>> the xAP<BR>>
website<BR>><BR>> <A=
href=3D"http://www.xapautom/";
target=3D_blank rel=3Dnofollow>http://www.xa=
pautom</A> ation.org/ index.php? title=3DSchema<BR>>
<<A href=3D"http=
://www.xapautomation.org/index.php?title=3DSchema" target=3D_blank
rel=3Dno=
follow>http://www.xapautom ation.org/ index.php?
title=3DSchema</A>><BR>=
><BR>> Kevin<BR>><BR>> Andre
Van Der Merwe wrote:<BR>> ><=
BR>> > Hi Kevin,<BR>>
><BR>> ><BR>>
><BR>> > =
no you answered my questions. i have just not checked this
email<BR>> re=
cently.<BR>> ><BR>>
><BR>> ><BR>> > the system
is n=
ow working and
i am getting the 1-wire<BR>> temperatures
out<BR>> > fine. Unfort=
unately the Barionet BCL code does not support floating<BR>>
> point =
variables, so I can only get integer degree celcius out.<BR>>
If is<BR>&=
gt; > use the correct xAP schema , typically 23degC corresponds
to<BR>&g=
t; 368/4096..<BR>> > this works
great.<BR>> ><BR>>
><BR>&=
gt; ><BR>> > Now i am working on getting the
368/4096 to make some=
sence in<BR>> homeseer.<BR>>
><BR>> ><BR>>
><BR>> =
> I made some changes to the code to achieve the above. Also
in<BR>> =
the code<BR>> > it refers to a "config.txt"
file which should change =
to<BR>> "xapcfg.txt" .<BR>> >
Shall i send the update ?<BR>> &g=
t;<BR>> > --- On *Tue, 6/3/08, Kevin Hawkins
/<yahoogroupskh@ goog=
lemail.<BR>> com <mailto:yahoogroups kh%40googlemail.
com>>/*<B=
R>> > wrote:<BR>> ><BR>>
> From: Kevin Hawkins
<yahoogroupskh@ googlemail. com<BR>> <mailto:yahoogroups kh%40goo=
glemail. com>><BR>> > Subject: Re:
[xap_automation] Barionet xA=
P code<BR>> > To: xap_automation@ yahoogroups.
com<BR>> <mailto=
:xap_ automation% 40yahoogroups. com><BR>> >
Date: Tuesday, June 3=
, 2008, 11:58 AM<BR>> ><BR>> >
Andre,<BR>> ><BR>> >=
Phew....We seem to have a communication problem..<BR>>
><BR>> >=
; I responded to a post you made a few days back in the xAP
mi4<BR>> >=
; plugin area on the HomeSeer BBS where you were actually
using<BR>> the=
mcs<BR>> > plugin - fortunately Michael saw it anyway.
Also on the B=
arix<BR>> > Barionet<BR>> > forum
last week I responded too and=
you said you already had the<BR>> >
code..<BR>> > I have taken=
a look at the Barionet xAP code (the BSC v1.3<BR>> >
version) and<BR=
>> > so I dusted off my own Barionet, re-tokenized it and
it
loaded<BR>> > fine. I<BR>> > posted
some detailed instructions=
there as to how to do this. Quite<BR>> > why it was
dusty I'm not su=
re as it's a great device on xAP and I<BR>> >
shall<BR>> > be u=
sing it now going forwards :-)<BR>> ><BR>>
> Since then, with E=
dwards permission, I have updated the code<BR>> >
slightly to fix a c=
ouple of issues I spotted and I have sent you two<BR>>
> revised vers=
ions by email . I also sent you directly by email the<BR>>
> .cob<BR>=
> > file so you could load it directly into your Barionet -
assuming =
you<BR>> > have the latest firmware - but I haven't
been able to get =
any info<BR>> > from<BR>> > you as
to which Barionet firmware y=
ou are running. Then you posted<BR>> > a HomeSeer
plugin issue questi=
on and so I tried it out here and it<BR>> > worked fine
but I noticed=
you were still not using the latest<BR>> > firmware
I<BR>>
> sent you :-(<BR>> ><BR>> >
So I don't know what more we c=
an do... Please can you check your<BR>> > email and try
those most re=
cent versions I sent you. They work<BR>> > perfectly
well here. You s=
eem to be using an old xAP v1.2 / BSC v1.2<BR>> >
version still. You =
can of course use the previous BSC v1.3 version<BR>> >
direct from Ed=
ward but you will manually have to fix a couple of<BR>>
> issues<BR>&=
gt; > that I have already corrected in my version. You will need
to<BR>&=
gt; address<BR>> > the 'state =3D' vs 'state=3D'
parameter name and a=
lso levels are<BR>> > mistakenly<BR>>
> reported in the state=
=3D parmeter eg state=3D100/1024 . In my version<BR>> >
'12b' 1.12 th=
is is already fixed for you.<BR>> ><BR>>
> Over the next few we=
eks I shall be revising the code to hopefully<BR>> >
support new feat=
ures that later Barionet firmward now offers eg<BR>> >
counters<BR>&g=
t;
> and more 1-wire sensors, maybe threshold settings for the
state=3D<BR=
>> > parameter in level devices. The revision I already
released prov=
ides<BR>> > compliance with both xAP v1.3 and BSC v1.3.
Please let me=
know<BR>> > anything you would like to have added here,
although for=
any custom<BR>> > changes you are free to adapt the
source code anyw=
ay.<BR>> ><BR>> > Let us know how
you want to move forward.....=
<BR>> ><BR>> >
Kevin<BR>> ><BR>> > andrevdm
wrote:<=
BR>> > ><BR>> > > Hi
Edward,<BR>> > ><BR>> &g=
t; > on you blueyonder website you invite to contact you
if<BR>> inte=
rested in<BR>> > > your .bas code for the xAP
version 1.3.<BR>>=
> ><BR>> > > is it still available
?<BR>> > ><BR>&=
gt; > > regards<BR>> >
><BR>> > > Andre<BR>>
>=
; ><BR>> > ><BR>>
><BR>> ><BR>>
><BR>><BR>><BR>>
<BR><BR></P></DIV></DIV></BLOCKQUOTE></td></t=
r></table><br>
=20=20=20=20=20=20
<span width=3D"1" style=3D"color:
white;"/>__._,_.___</span>
<!-- Start Recommendations -->
<!-- End Recommendations -->
<!-- **begin egp html banner** -->
<img src=3D"http://geo.yahoo.com/serv?s=3D97476590/grpId=3D9674343/grpspI=
d=3D1705007709/msgId=3D3914/stime=3D1212757971" width=3D"1"
height=3D"1"> <=
br>
<!-- **end egp html banner** -->
=20=20
<!-- **begin egp html banner** -->
<br>
<div style=3D"font-family: verdana; font-size: 77%; border-top: 1px
s=
olid #666; padding: 5px 0;" >
Your email settings: Individual EmailTraditional <br>
<a href=3D"http://groups.yahoo.com/group/xap_automation/join;_ylc=3DX=
3oDMTJmY2JwZGdpBF9TAzk3NDc2NTkwBGdycElkAzk2NzQzNDMEZ3Jwc3BJZAMxNzA1MDA3NzA5=
BHNlYwNmdHIEc2xrA3N0bmdzBHN0aW1lAzEyMTI3NTc5NzE-">Change settings
via the W=
eb</a> (Yahoo! ID required) <br>
Change settings via email: <a href=3D"mailto:xap_automation-digest@ya=
hoogroups.com?subject=3DEmail Delivery: Digest">Switch delivery to
Daily Di=
gest</a> <a href =3D "mailto:xap_automation-fullfeatured@xxxxxxx?=
subject=3DChange Delivery Format: Fully Featured">Switch to Fully
Featured<=
/a> <br>
<a href=3D"http://groups.yahoo.com/group/xap_automation;_ylc=3DX=
3oDMTJkbHRoYW1sBF9TAzk3NDc2NTkwBGdycElkAzk2NzQzNDMEZ3Jwc3BJZAMxNzA1MDA3NzA5=
BHNlYwNmdHIEc2xrA2hwZgRzdGltZQMxMjEyNzU3OTcx">
Visit Your Group=20
</a>
<a href=3D"http://docs.yahoo.com/info/terms/";>
Yahoo! Groups Terms of Use
</a>
<a href=3D"mailto:xap_automation-unsubscribe@xxxxxxx?subject=
=3DUnsubscribe">
Unsubscribe=20
</a>=20
<br>
</div>
<br>
<!-- **end egp html banner** -->
<span style=3D"color: white;"/>__,_._,___</span>
</body></html>
--0-224642887-1212756989=:10642--
xAP_Automation Main Index |
xAP_Automation Thread Index |
xAP_Automation Home |
Archives Home
|