[Message Prev][Message
Next][Thread Prev][Thread Next][Message
Index][Thread Index]
Re: {Disarmed} Re: Sorted!!
--000e0cd214d2a82ef40463d539f1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Nice work Dave! It is worth mentioning that there have been reports of
memory leaks with my OCX. I never got to the bottom of it, it's far from
universal, but some people definitely reported problems.
Patrick
2009/2/26 Kevin Hawkins <yahoogroupskh@xxxxxxx>
> The code doesn't replace the OCX - it's just based around a different
> OCX although you could adapt back and continue with Patricks.
>
> xAP uses 'schema' which are the message descriptions for various
> devices/data. I am not sure if you are using an existing schema or at
> this stage just push parameter data out and receive it into HomeSeer
as
> a custom schema (no problem with that either).
>
> One of our schema called Basic Status and Control or 'BSC' is very
> popular and creates great interoperability between devices. It
handles
> simple data for binary, level and text based devices. There's also a
> matching schema called 'TSC' for telemetry/sensor data. Should you
> decide to use BSC then the Framework can help implement it. BSC is a
> two way schema allowing status to be requested, commands to be sent
and
> it provides realtime events if anything changes. It also periodically
> reports known status. The framework helps you implement this as well
as
> providing code for wildcard source/target address matching etc. Just
> avoids you having to reinvent the wheel. I'll dig some code out and
> you can see if any of it is useful - give me a bit of time to dig it
out.
>
> Cheers Kevin
>
> Dave McLaughlin wrote:
> >
> > Hi Kevin
> >
> >
> >
> > Is pretty good that I got it working. Really is amazing how easy
it is
> > with the OCX and only took me a few hours to get the Zigbee
working
> > with some test code. Just now it is requesting the count of KWh
from
> > the unit I hung off the electric meter and is now displaying the
value
> > and the cost in Homeseer Touch.
> >
> >
> >
> > I am indeed using C for the Atmel. I use the excellent Codevision
AVR
> > compiler and have done for many years. I keep it updated each
year and
> > the support and capabilities are worth every penny.
> >
> >
> >
> > I would certainly be interesting in looking at your code to see
how
> > it hangs together instead of using the OCX.
> >
> >
> >
> > Dave...
> >
> > ---
> > Very funny Scotty, now beam down my clothes!!!
> > ---
> > http://www.embeddedcomputer.co.uk
<http://www.embeddedcomputer.co.uk>
> > ---
> >
> >
> >
> > *From:* xap_automation@xxxxxxx
> > [mailto:xap_automation@xxxxxxx] *On
Behalf Of *Kevin Hawkins
> > *Sent:* 26 February 2009 20:18
> > *To:* xap_automation@xxxxxxx
> > *Subject:* {Disarmed} Re: [xap_automation] Sorted!!
> >
> >
> >
> > Just thought...
> >
> > The xAP BSC schema is a particularly useful one to implement and
is
> > very simple yet powerful and gives great 'plug and play'
compatibility.
> > Implementing it thoroughly as a two way schema takes a bit of
work. IT
> > may be applicable to your project.
> >
> > I do have an 'in progress' xAP BSC Framework that I started to
> > write in VB6 and although it originally used Patricks OCX I
changed it
> > to James' Intranet OCX (mi4) . I never finished this to a release
level
> > but it's pretty complete and fairly self explanatory and may help
you
> > with your project. You're welcome to that (VB6) code if you wish.
> >
> > BTW Are you using C to program the onboard Atmel devices ?
> >
> > Cheers Kevin
> >
> >
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>
--000e0cd214d2a82ef40463d539f1
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<head>
<style type=3D"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=20
a,
div.photo-title a:active,
div.photo-title a:hover,
div.photo-title a:visited {
text-decoration: none;=20
}
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;
}
p span {
color: #628C2A;
}
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>
<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>
Nice work Dave! It is worth mentioning that there have been reports of
memo=
ry leaks with my OCX. I never got to the bottom of it, it's far
from un=
iversal, but some people definitely reported
problems.<br><br>Patrick<br>
<br><div class=3D"gmail_quote">2009/2/26 Kevin
Hawkins <span dir=3D"ltr">&l=
t;<a href=3D"mailto:yahoogroupskh@xxxxxxx";>yahoogroupskh@googlemail.=
com</a>></span><br><blockquote
class=3D"gmail_quote" style=3D"border-lef=
t: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left:
1=
ex;">
The code doesn't replace the OCX - it's just based around a
differe=
nt<br>
OCX although you could adapt back and continue with Patricks.<br>
<br>
xAP uses 'schema' which are the message descriptions for
various<br=
>
devices/data. I am not sure if you are using an existing schema or
at<br>
this stage just push parameter data out and receive it into HomeSeer
as<br>
a custom schema (no problem with that either).<br>
<br>
One of our schema called Basic Status and Control or 'BSC'
is very<=
br>
popular and creates great interoperability between devices. =A0It
handles<b=
r>
simple data for binary, level and text based devices. =A0There's
also a=
<br>
matching schema called 'TSC' for telemetry/sensor data. =A0
Should =
you<br>
decide to use BSC then the Framework can help implement it. =A0BSC is
a<br>
two way schema allowing status to be requested, commands to be sent
and<br>
it provides realtime events if anything changes. It also
periodically<br>
reports known status. =A0The framework helps you implement this as well
as<=
br>
providing code for wildcard source/target address matching etc. =A0
Just<br=
>
avoids you having to reinvent the wheel. =A0 =A0I'll dig some code
out =
and<br>
you can see if any of it is useful - give me a bit of time to dig it
out.<b=
r>
<br>
Cheers Kevin<br>
<div class=3D"Ih2E3d"><br>
=A0 Dave McLaughlin wrote:<br>
><br>
> Hi Kevin<br>
><br>
><br>
><br>
> Is pretty good that I got it working. Really is amazing how easy
it is=
<br>
> with the OCX and only took me a few hours to get the Zigbee
working<br=
>
> with some test code. Just now it is requesting the count of KWh
from<b=
r>
> the unit I hung off the electric meter and is now displaying the
value=
<br>
> and the cost in Homeseer Touch.<br>
><br>
><br>
><br>
> I am indeed using C for the Atmel. I use the excellent Codevision
AVR<=
br>
> compiler and have done for many years. I keep it updated each year
and=
<br>
> the support and capabilities are worth every penny.<br>
><br>
><br>
><br>
> I would certainly be interesting in looking at your code to =A0see
how=
<br>
> it hangs together instead of using the OCX.<br>
><br>
><br>
><br>
> Dave...<br>
><br>
> ---<br>
> Very funny Scotty, now beam down my clothes!!!<br>
> ---<br>
</div>> <a href=3D"http://www.embeddedcomputer.co.uk";
target=3D"_blank">=
http://www.embeddedcomputer.co.uk</a>
<<a href=3D"http://www.embeddedcom=
puter.co.uk" target=3D"_blank">http://www.embeddedcomputer.co.uk</a>><br=
>
<div class=3D"Ih2E3d">> ---<br>
><br>
><br>
><br>
> *From:* <a href=3D"mailto:xap_automation@xxxxxxx";>xap_automati=
on@xxxxxxx</a><br>
> [mailto:<a href=3D"mailto:xap_automation@xxxxxxx";>xap_automati=
on@xxxxxxx</a>] *On Behalf Of *Kevin Hawkins<br>
> *Sent:* 26 February 2009 20:18<br>
> *To:* <a href=3D"mailto:xap_automation@xxxxxxx";>xap_automation=
@yahoogroups.com</a><br>
> *Subject:* {Disarmed} Re: [xap_automation] Sorted!!<br>
><br>
><br>
><br>
> Just thought...<br>
><br>
> The xAP BSC schema is a particularly useful one to implement and
is<br=
>
> very simple yet powerful and gives great 'plug and
play' compa=
tibility.<br>
> Implementing it thoroughly as a two way schema takes a bit of
work. IT=
<br>
> may be applicable to your project.<br>
><br>
> I do have an 'in progress' xAP BSC Framework that
I started to=
<br>
> write in VB6 and although it originally used Patricks OCX I
changed it=
<br>
> to James' Intranet OCX (mi4) . I never finished this to a
release =
level<br>
> but it's pretty complete and fairly self explanatory and
may help =
you<br>
> with your project. You're welcome to that (VB6) code if
you wish.<=
br>
><br>
> BTW Are you using C to program the onboard Atmel devices
?<br>
><br>
> Cheers Kevin<br>
><br>
><br>
<br>
<br>
<br>
</div>------------------------------------<br>
<br>
xAP_Automation Main Index |
xAP_Automation Thread Index |
xAP_Automation Home |
Archives Home
|