[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: Thu, 5 Jun 2008 23:49:33 -0700 (PDT)
--0-1283344508-1212734973=:15543
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
the xAPBSC now passes the correct 1-wire temperature through to Homeseer.
In the attached word document the changed text is highlighted. The device
status displays correctly. the DeviceString contains the temperature in
resolution of .1 degrees celcius ie 23.1. However the DeviceValue contains
a rounded integer degree celcius ie 23. For higher accuracy control in
HSconvert the DeviceValue to variable.
Change the extention from .doc to .bas to tokenize.
--- On Wed, 6/4/08, Kevin Hawkins <yahoogroupskh@xxxxxxx>
wrote:
From: Kevin Hawkins <yahoogroupskh@xxxxxxx>
Subject: Re: [xap_automation] Barionet xAP code
To: xap_automation@xxxxxxx
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
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
floating
> 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>/*
> wrote:
>
> From: Kevin Hawkins <yahoogroupskh@ googlemail. com>
> Subject: Re: [xap_automation] Barionet xAP code
> To: xap_automation@ yahoogroups. 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.
Quite
> 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 info
> from
> you as to which Barionet firmware you are running. Then you posted
> a HomeSeer plugin issue question and so I tried it out here and it
> 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
v1.2
> version still. You can of course use the previous BSC v1.3 version
> 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
version
> '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
provides
> 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
custom
> 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
> >
> >
>
>
>
--0-1283344508-1212734973=:15543
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>the =
xAPBSC now passes the correct 1-wire temperature through to Homeseer. In
th=
e attached word document the changed text is highlighted. The device
status=
displays correctly. the DeviceString contains the temperature in resolutio=
n of .1 degrees celcius ie 23.1. However the DeviceValue contains a
rounded=
integer degree celcius ie 23. For higher accuracy control in HSconvert the=
DeviceValue to variable.</P>
<P> </P>
<P>Change the extention from .doc to .bas to
tokenize.<BR><BR>--- On <B>Wed=
, 6/4/08, Kevin Hawkins
<I><yahoogroupskh@xxxxxxx></I></B> wro=
te:<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: Wednesday, June 4, 2008, 11:07
PM<BR><BR>
<DIV id=3Dyiv475109855>
<DIV id=3Dygrp-text>
<P>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>I progress. It's likely I'll release
an up=
date in a week or so any <BR>changes you want let me know - if you
can high=
light the actual code <BR>changed that would be great. Please use
copious c=
omments too.<BR><BR>Re the decimal values - BSC doesn't support
these eithe=
r - nor does <BR>it support negative values. What you can do however
is to =
report them <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 =
then create <BR>a string and insert the decimal
point<BR><BR>displaytext=3D=
51.24=B0c<BR><BR>Or you could abandon the level based BSC
device altogethe=
r and use a <BR>text one instead
text=3D-11.25=B0F<BR><BR>Actually, and mor=
e approriately for such 'telemetry' data we have <BR>another schema
called =
TSC , it's not as universal as BSC yet but we hope <BR>eventually it
will
become so. - the spec for BSC and TSC are on the xAP <BR>website
<BR><BR><=
A href=3D"http://www.xapautomation.org/index.php?title=3DSchema";
target=3D_=
blank rel=3Dnofollow>http://www.xapautom ation.org/ index.php?
title=3DSche=
ma</A><BR><BR>Kevin<BR><BR>Andre Van Der
Merwe wrote:<BR>><BR>> Hi Ke=
vin,<BR>><BR>>
<BR>><BR>> no you answered my questions. i have =
just not checked this email recently.<BR>><BR>>
<BR>><BR>> the =
system is now working and i am getting the 1-wire temperatures out
<BR>>=
fine. Unfortunately the Barionet BCL code does not support floating
<BR>&g=
t; point variables, so I can only get integer degree celcius out. If is
<BR=
>> use the correct xAP schema , typically 23degC corresponds to
368/4096=
.. <BR>> this works great.<BR>><BR>>
<BR>><BR>> Now i am wor=
king on getting the 368/4096 to make some sence in
homeseer.<BR>><BR>>=
; <BR>><BR>> I made some changes to the code to
achieve the above. Al=
so
in the code <BR>> it refers to a "config.txt" file
which should change =
to "xapcfg.txt" . <BR>> Shall i send the update
?<BR>><BR>> --- On=
*Tue, 6/3/08, Kevin Hawkins /<<A href=3D"mailto:yahoogroupskh%40googlem=
ail.com" target=3D_blank rel=3Dnofollow>yahoogroupskh@ googlemail.
com</A>&=
gt;/* <BR>> wrote:<BR>><BR>> From:
Kevin Hawkins <<A href=3D"ma=
ilto:yahoogroupskh%40googlemail.com" target=3D_blank
rel=3Dnofollow>yahoogr=
oupskh@ googlemail. com</A>><BR>> Subject: Re:
[xap_automation] Bario=
net xAP code<BR>> To: <A href=3D"mailto:xap_automation%40yahoogroups.com=
" target=3D_blank rel=3Dnofollow>xap_automation@ yahoogroups.
com</A><BR>&g=
t; Date: Tuesday, June 3, 2008, 11:58
AM<BR>><BR>> Andre,<BR>><BR>=
> Phew....We seem to have a communication
problem..<BR>><BR>> I re=
sponded to a post you made a few days back in the xAP mi4<BR>>
plugin ar=
ea on the HomeSeer BBS where you were actually using the
mcs<BR>> plugin=
-
fortunately Michael saw it anyway. Also on the Barix<BR>>
Barionet<BR>&=
gt; 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 sure as=
it's a great device on xAP and I<BR>> shall<BR>>
be using it now goi=
ng forwards :-)<BR>><BR>> Since then, with
Edwards permission, I have=
updated the code<BR>> slightly to fix a couple of issues I
spotted and =
I have sent you two<BR>> revised versions by email . I also
sent you dir=
ectly 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 you are running. Then you posted<BR>>
a HomeSee=
r plugin issue question and so I tried it out here and it<BR>>
worked fi=
ne 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 can do... Pl=
ease can you check your<BR>> email and try those most recent
versions I =
sent you. They work<BR>> perfectly well here. You seem to be
using an ol=
d xAP v1.2 / BSC v1.2<BR>> version still. You can of course
use the prev=
ious BSC v1.3 version<BR>> direct from Edward but you will
manually have=
to fix a couple of<BR>> issues<BR>> that I have
already corrected in=
my version. You will need to address<BR>> the 'state =3D' vs
'state=3D'=
parameter name and also levels are<BR>>
mistakenly<BR>> reported in =
the state=3D parmeter eg state=3D100/1024 . In my version<BR>>
'12b' 1.1=
2 this is already fixed for you.<BR>><BR>> Over
the next few weeks I
shall be revising the code to hopefully<BR>> support new
features that =
later Barionet firmward now offers eg<BR>>
counters<BR>> and more 1-w=
ire sensors, maybe threshold settings for the state=3D<BR>>
parameter in=
level devices. The revision I already released provides<BR>>
compliance=
with both xAP v1.3 and BSC v1.3. Please let me know<BR>>
anything you w=
ould like to have added here, although for any custom<BR>>
changes you a=
re free to adapt the source code
anyway.<BR>><BR>> Let us know how yo=
u want to move forward.....<BR>><BR>>
Kevin<BR>><BR>> andrevdm =
wrote:<BR>> ><BR>> > Hi
Edward,<BR>> ><BR>> > on yo=
u blueyonder website you invite to contact you if interested
in<BR>> >=
; your .bas code for the xAP version 1.3.<BR>>
><BR>> > is it s=
till available ?<BR>> ><BR>> >
regards<BR>> ><BR>> >=
; Andre<BR>> ><BR>>
><BR>><BR>><BR>>
<BR><BR></P></DIV></DIV></BLOCKQUOTE></td></tr></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=3D3911/stime=3D1212748238" 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=
3oDMTJmNm12MDh0BF9TAzk3NDc2NTkwBGdycElkAzk2NzQzNDMEZ3Jwc3BJZAMxNzA1MDA3NzA5=
BHNlYwNmdHIEc2xrA3N0bmdzBHN0aW1lAzEyMTI3NDgyMzg-">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=
3oDMTJkcTFtZ2hhBF9TAzk3NDc2NTkwBGdycElkAzk2NzQzNDMEZ3Jwc3BJZAMxNzA1MDA3NzA5=
BHNlYwNmdHIEc2xrA2hwZgRzdGltZQMxMjEyNzQ4MjM4">
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-1283344508-1212734973=:15543--
xAP_Automation Main Index |
xAP_Automation Thread Index |
xAP_Automation Home |
Archives Home
|