Re: RE: Wattson

["Martyn Wendon" <martynwendon@xxxxxxxxxxx>]

Hi Kevin,

Well your xAPP sounds better than mine!

I just made up a Schema (power.usage) and made it replicate the exact data
that the device sends in the xml packet.  I like to try and keep things
simple with this type of connector and just have them present the data with
other xAPPs deciding what to do with it.

Having said that thought the fixed time slots and xLobby integration sound
good.....

I've also noticed the slightly inconsistent readings too, but wasn't sure
of
the cause.  It's interesting that the xml also shows 3 channels of data, so
I wonder if additional clamps can be obtained to connect to the
transmitter?

My incoming power is split between the house and node zero, so it would be
good to be able to get data from each "segment".  Although at
only £28 each
it's not too much of a stretch to buy another couple!


Cheers,

Martyn (off to investigate xLobby)


----- Original Message -----
From: "Kevin Hawkins" <yahoogroupskh@xxxxxxx>
To: <ukha_d@xxxxxxx>
Sent: Friday, August 22, 2008 5:32 PM
Subject: Re: [ukha_d] RE: Wattson


> Hi Martyn,
>
>    Snap - I've also (half) written a xAP connector for it which
reports
> BSC level devices with display text information  that reflect the time
> period stats that the device reports and also current usage.  The
> periods are converted from the rolling time slots of the XML into
fixed
> time slots .
>
>      The BSC level device outputs are useful in that this then allows
> you to easily draw realtime  graphs for the past 24 hours (2 hour
> intervals) or the last minute in 6 second intervals.  I implemented it
> in xLobby using level sliders to draw bar graphs...which update in
> realtime.
>
>    Of course as you have done the xAP data could go into a DB via say
> xAP Floorplan or OPNMax - which can draw very detailed graphs.
>
>    One issue I'm experiencing is that the device does not give
> consistent readings.  Turning a kettle on for example shows a 3KW jump
> but then turning it off only shows a 200W drop.  I believe this is
> because other wires are adjacent to the clamp but I need to
investigate
> further.
>
>     I had envisaged a way of checking that light bulbs hadn't blown by
> switching lamps on very briefly in a 'check cycle' and double checking
> the expected increase in current usage.  Perhaps  doing this during
> times when the building was unoccupied eg when the alarm was set. 
This
> alongside a check that watched when the automation system turned
things
> on/off and monitored the expected current changes.  Idratek's Cortex
for
> example already allows associating a wattage to each light you create.
>
>    I understand that later versions of the current cost are planned
and
> may offer a USB interface....   On the existing Current Cost a special
> cable is orderable direct from the company for around a tenner. +
P&P
>
>     K
>
> Martyn Wendon wrote:
>> ....which is a TTL->USB cable and comes up as a comm port under
>> Windows.....then a quickly hacked together xAP to chuck the xml
data over
>> xAP.
>>
>> xAP Floorplan is currently logging the data for me and when I get
a
>> chance
>> I'll whip up a web page to display statistics and such.
>>
>>
>> Not bad for £28!
>>
>>
>> Cheers,
>>
>> Martyn
>>
>>
>
>
> ------------------------------------
>
> **** Sponsored By http://www.Berble.com ****
> ****       Computers You Carry          ****
>
>
>
>
>
>



------------------------------------