Re: A VSCP schema for xAP

[YAP <x112358@xxxxxxxxx>]

Thanks Kevin.

I promissed a long time a go to make a link between xAP and VSCP and
now its finally time to do it. The question is if I should incorporate
a xAP HUB in the canal/VSCP daemon or rely on external stuff or maybe
do both and make it user selectable. The good thing is that the daemon
runs on both Linux and Windows.

You have a point about the source. It probably should be eurosource
even if this is in some way officially VSCP stuff.

I will try to do some mappings to BCS and other schemas where it makes
sense. VSCP is very event oriented. There is an event. It has a class
and a type and some data that are specific to the event.

So when you xAP folks say
...
source=some-sorece
target=some-target-group.*
}
...
...
output.state.2
{
ID=1B
state=off
}

VSCP send its data binary with

class=30,  The control class
type=05, TurnOn event
A reserved byte.
zone = 0x1B, A byte id for the zone that this event is intended for.
subzone = 0x00, A byte id for the sub-zone this event is intended for.

Normally nothing is addressed in VSCP.

This could also be sent as

VSCP.level1
{
vscp-class=30
vscp-type=5
priority=7
data=001B00
}

So in this case BCS will map perfectly.

Our measurement class is a bit different

A counter value from a S0 pulse counter on a power meter can be sent as

VSCP.level1
{
vscp-class=10
vscp-type=1
priority=7
data=C0aabbccdd
}

where aabbccdd is the counter value (KW/h)


A temperature value could be received as

VSCP.level1
{
vscp-class=10
vscp-type=6
priority=7
data=880208BF
}

Taken from one of the Kelvin sensors in my house now. Here 08BF is the
temperature (2239 which is 22.39 degrees celsius) 88 tells how the
data should be interpreted( In this case a normalized integer) and 02
tells how many decimals is in the number.

This would also be easy to map to the weather schema.

What I  would like to illustrate with this is that both forms ( a
maped and a VSCP schema) have a use IMHO.

Cheers
/Ake





On 8/5/05, Kevin Hawkins <lists@xxxxxxx> wrote:
>  Hi Ake,
>
>       Nice to have you back.. !
>
>      The intent is that the vendor name is the actual author
(providor)
>  of the application, in your case 'Eurosource' I guess. If the VSCP
group
>  were writing it then it would be VSCP .  The VSCP part is the device
>  type really isn't it (?) so you should end with an address something
> like...
>
>       Source=EuroSource.VSCP.<instance>
>
>     If you were writing it officially on behalf of the VSCP group then
>  you might want the vendor ID of VSCP I guess. Not sure how VSCP is
>  formalised as a group. Theoretically a 'device' once standardised
could
>  also be provided by another vendor so there could be a ERSP.X10 and a
>  KCSoft.X10 and  mi4.X10 or whatever.
>
>     Getting BSC working transparently with VSCP will be really  nice
:-)
>  - looking forward to that,. Some of the more complex things I realise
>  will take more effort but maybe we can learn and adapt from each
other
>  here, perhaps even creating  'standard' more involved xAP schemas if
you
>  have such devices mapped out in VSCP. I don't know enough about VSCP
to
>  know if you have these all defined already.  ( mental note ... must
read
>  that spec).   Certainly it would be nice to have some more complex
>  'standard' schema to bridge transparently between the two. The intent
>  with xAP schema was focus on modelling types of functionality eg
>  'heating' 'lighting' and generic devices eg 'audio player'' etc but
>  inevitably people created specific device schema too eg 'Meteor' and
to
>  an extent 'X10', it's much easier (but less useful) to do the latter
as
>  everything is contained of course..  Getting broader functional
>  definitions correct eg 'security' is quite an onerous task. UPNP have
>  many  large teams of people with each team focussing on one area.  
At
>  another level it will of course be possible to have a 'VSCP' schema
to
>  'send a VSCP message' or something although this  is more a
programatic
>  link than a  bridge ,  of course very useful (essential) but less
>  'bridged' if you see what  I mean.
>
>    Like Stuart I recommend you wade in and just 'post' your thoughts
and
>  ask questions, everyone learns from this sort of interaction.  
You'll
>  only really meet resistance if you try to suggest something that
breaks
>  the xAP spec or impacts other existing applications.  In areas where
we
>  know we should have "xAP official" ways of  doing things
(eg config ,
>  groups, scenes) etc then we may want to get a small working group to
>  thrash out a proposal that can later be adopted as the xAP standard.
>  This in practice can be quite lively.  The joys of an open protocol.
>
>      Kevin
>
>
>  YAP wrote:
>
>  >Stuart,
>  >
>  >thanks. I have a go at it and post it here so you can put me on
the right
> track.
>  >
>  >Why I would like to use "VSCP" is because the vendor in
this case is
>  >the VSCP group, not me nor my company "eurosource". The
events coming
>  >in can originate from different vendors products. If I did a
>  >"eurosource" variant of this it could be something
different. Would
>  >that be OK?
>  >
>  >/Ake
>  >
>  >On 8/5/05, Stuart Booth <lists@xxxxxxx> wrote:
>  >
>  >
>  >> On Fri, 5 Aug 2005 12:16:38 +0200, YAP
<x112358@xxxxxxx> wrote:
>  >>
>  >> >I would very much like to design a VSCP (http://www.vscp.org) schema
>  >> >for xAP and add support for xAP to the VSCP daemon. Can
I do a
>  >> >proposal for this myself or do I have to go through a
some kind of
>  >> >steering group to have it done?
>  >>
>  >> Oh, just have a go yourself! Post up to the list and get
some
>  >> comments/suggestions from others, that's what I normally do.
>  >>
>  >>
>  >>
>  >
>  >
>  >
>  >
>  >> There are a few components of schemas often done in what you
might
>  >> call standardised ways now - certainly I have a few patterns
I tend to
>  >> follow in my own efforts, which I tend to wrap in my own xAP
code.
>  >>
>  >> >Also I need a vendor id ("VSCP" preferred).
How do I get this?
>  >>
>  >> I think you just did. Normally it's a case of reserve an ID
here, it
>  >> gets added to a list somewhere, job done. However, that
seems more of
>  >> a protocol name rather than a vendor name. There might in
future be a
>  >> few different implementions from different vendors under
this same
>  >> general banner if you see what I mean??
>  >>
>  >> S
>  >> --
>  >> Stuart Booth <stuart@xxxxxxx>
>  >> xAPFramework.net - a xAP software development framework for
.net
>  >>
>  >> http://www.xapautomation.org/     
 http://www.xapframework.net/
>  >>
>  >>
>  >>
>  >> ________________________________
>  >> YAHOO! GROUPS LINKS
>  >>
>  >>
>  >> Visit your group "xAP_developer" on the web.
>  >>
>  >> To unsubscribe from this group, send an email to:
>  >> xAP_developer-unsubscribe@xxxxxxx
>  >>
>  >> Your use of Yahoo! Groups is subject to the Yahoo! Terms of
Service.
>  >>
>  >> ________________________________
>  >>
>  >>
>  >>
>  >
>  >
>  >
>  >
>  >Yahoo! Groups Links
>  >
>  >
>  >
>  >
>  >
>  >
>  >
>  >
>  >
>  >
>
>
>
>
>  ________________________________
>  YAHOO! GROUPS LINKS
>
>
>
>  Visit your group "xAP_developer" on the web.
>
>  To unsubscribe from this group, send an email to:
>  xAP_developer-unsubscribe@xxxxxxx
>
>  Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
>
>  ________________________________
>