Category Archives: VSCP

State of #VSCP

It’ been quiet on all VSCP fronts for a while.  Well VSCP is anyway probably the least written about project in the world in relation to time alive and efforts put into it. And that is OK as long as things move forward (and they do – slowly).

We approach 18 years of VSCP now in August. I never could see that coming when I started this project.  I think I have worked almost daily during this time on the project. Crazy if you think about it.

A lot of other projects has emerged (and died) now with the buzz of IoT.  It’s a bit like waves of knowledge coming to people unused to embedded development who never ask questions to people that has been into embedded development for ages. First everything  should connect to the cloud, then people realised that that was not the best solution, it was impossible to realize actually,  border routers was introduced, we called them (home) gateways before, then web standards where abandoned for binary protocols and so on. Soon someone will realize that things will we both wireless and connected with cables and that small devices really have limited resources and then we probably end up in something like what VSCP has been about all the time. Well, it’s the way things work in our industry. Hype, hype, hype. Happy, happy, sad.

Here is the current state.

TSL/SSL

OK VSCP. Changes has been made to the VSCP daemon. The mongoose tcp/ip code is on the way out and is replaced with some code derived from the Civetweb project.  A fun thing is that this derived code is also the ancestor to the Mongoose code to. Good thing is that now all the VSCP Daemon code will be MIT licensed.  Freedom for you.

The derived code is published as a separate project sockettcp (still needs to be documented) and this is code that makes it easy to code tcp clients/servers that use TSL/SSL or unsecure connections. Works on Windows and Linux.

The VSCP Daemon tcp/ip interface will therefore be fully TLS/SSL from the next version.

Encryption will also be introduced in another layer to both the winsock and the tcp/ip interfaces. Much like what is available today in the multicast and UDP interfaces. This makes it possible for clients that don’t have the ower to use full TSL/SSL to still implement secure connections.

VSCP Daemon

Yes I changed the name to “VSCP Server” for a while. Just like “VSCP Dameon” better. so I changed back. Probably will use the term  “Border Router” for this piece of software more in the future.

Documentation

Most if the documentation (still some work left to do on VSCP Works) has now been moved to Markdown and is available on Gitbook (old paths work). Docs are licensed under Creative Commons BY 4.0 now. Search and pdf/ebook availabilities is the good things that come with this change. Source for the docs are available on Github (vscp-doc-….) and it is now easy to post corrections and changes as for all Git projects.

Specs

To add classes and types has been something that has been getting harder and harder over time. The defines for them are all over the place. A change/addition means editing all these places. This has been changed now so all files are auto-generated including the class/type part of the VSCP spec. JSON/XML/sql… and other formats will be available soon for dynamic downloads.

Well there is a lot more changes in the code and it will all be included in the next release that will be available later this summer.

Snap

VSCP will use the snap package system. Easy install. Easy use. Debian packages is still in the pipeline to.

Help

I will not ask directly for help here any more. It’s been a useless question to ask all times I tried (many now… 😉 ). That is OK.  If you been hanging around the project you know you are welcome to contribute. The ever growing todo list is here.

That’s all for now. Midsummer here tomorrow.  A day without any VSCP related work all together.

Have fun!
/Ake

#VSCP interfaces howto

Something that may confuse new users of VSCP is the GUID of interfaces. Looking at the interface above the CAN4VSCP driver have GUID set to

FF:FF:FF:FF:FF:FF:FF:FE:B8:27:EB:0A:00:02:00:00

which means nodes connected to this interface will come in with GUID’s

FF:FF:FF:FF:FF:FF:FF:FE:B8:27:EB:0A:00:02:00:01
FF:FF:FF:FF:FF:FF:FF:FE:B8:27:EB:0A:00:02:00:02
FF:FF:FF:FF:FF:FF:FF:FE:B8:27:EB:0A:00:02:00:03
FF:FF:FF:FF:FF:FF:FF:FE:B8:27:EB:0A:00:02:00:04
....

If we look at the GUID’s if this machine we see that they all start with

FF:FF:FF:FF:FF:FF:FF:FE

As of  the spec we know that this is a GUID constructed from an Ethernet address. In this case only four of the six MAC digits is used. The

00:02

is the interface id as set by the VSCP daemon and the last two digits are the nickname id for a connected node.

The problem that can occur here is that the interface digits can be different at different runs of the VSCP daemon. The number is just set when the interface is set up and from time to time this setup can happen in different order. So sometime

00:02

can be

00:03

or even

00:11

One can’t tell beforehand.

This is a problem if one want to use the GUID to identify a node. Problematic as this is just what we want in most cases. To trigger on an event from a specific node in a decision matrix the GUID is the item to filter on. Just as in this case

Here we store a temperature measurement in a variable if it comes from a node with GUID

FF:FF:FF:FF:FF:FF:FF:FE:B8:27:EB:0A:00:02:00:01

and measurement index = 1

If the interface ordinal  becomes something else like

00:03

we are in trouble here as the action (store measurement value in variable) will not be triggered.

If we look at the current driver for this setup it is set to

 

<!-- The can4vscp driver -->
<driver enable="false" >
    <name>can4vscp</name>
    <config>/dev/ttyUSB1</config>
    <path>/srv/vscp/drivers/level1/vscpl1drv-can4vscp.so</path>
 <guid>00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00</guid>
    <flag>>0</flags>
</driver>

The “problem” is solved by changing the <guid> tag from an all zero value (or not defined) to a valid GUID.  If not defined or all zero the VSCP daemon will assign a GUID as of above. But if a valid GUID is set this value will always be used.

In my case I can use

01:00:00:00:00:00:00:00:00:00:00:00:01:02:00:00

as I have some assigned GUIDs.  The two LSB’s is still used for the nicknames.

After that change the “problem” is no more and I can filter on the new GUID instead which alway will be the same.

 

 

#VSCP measurement visualization #IoT #m2m

I just want to present some new stuff I have been working on during the last week. It is still initial work but still quite useful. Also beware. This is JavaScript, PHP and MySQL and I am an embedded programmer. But I have asked for help from people who know these things but got no response so here I go and do it myself as usual. If someone wants to step in and help or even take over this project he/she is more than welcome, I have tons of other things to attend to.

There will be a proper howto and a manual at a later stage.  This document is just some information and a demo.

First: Why?

Answer: I need this for my own use. Actually I needed it because I have two compost containers where I have temperature sensors and I was curious of the temperature in them now in the winter when it is cold. Well I have some other temperature sensors around the house and the office that maybe can tell me something also.

If you know VSCP you also know about the VSCP ux framework. It is really a nice set tools that allows for building fast, reliable, secure and responsive user interfaces with live data. It uses the websocket and the REST interfaces of the VSCP daemon to communicate between ux elements and the VSCP subsystem. We talk state of the art security here, at least if SSL is used. But sometimes it may feel awkward to export interfaces of an in operation/house critical piece of computer hardware anyway. This is therefore another way you can share data. A cloud solution if you like. But something you are in charge of yourself.

To use VSCP mv (VSCP measurement visualization) you need an Internet server provider that gives you a mysql/mariadb database. Most does, at least here in Europe. Well you can have your own server that do this also of course.

Secondly you setup the VSCP daemon to send the data you want to share. This you do by adding a decision matrix element to your local VSCP daemon.

Third you configure what data you want to share by adding some entries in the database.

Your are ready to go.

Now you can visualize your data

This is the temperature outside at my place. With the “select source” at the bottom you can look at the temperature in my office and in the mentioned compost containers. The interface works on different hardware, phones, tablets and computers.  Using iframes you can include it in other web pages. This is live and dynamic data.

This is another way to look at the same information. Some more variants of this may come in the future.

If you instead wants a diagram you have that here for the current day, which is the default. The diagram will update as time goes.  If you prefer to see the temperature 2018-03-16 between 00 and 03 you can of course.

And if you rather want to see the current temperature in my office  it is possible or in the compost 1 container or in the compost 2 container.

But if you rather just want to investigate data this collecting interface may be the best place to get a hold on it.

And there are all temperature measurements here. But don’t be fooled.  Any of the VSCP’s measurement values can be shown.

But…

you say. I want to use my own diagram/Table tool to visualize data. I will not stop you. It’s a free world. If you can read JSON your on

Read the defined seco devices.  SECO = SEnsor, COntrol. Or read the current value for a SECO.  Or read data in a date/time range for a seco.

As I said I will come back with a manual and a howto at a later point. Well a link to the software also of course.

For me the info that the microorganisms in the compost container holds it at zero degrees Celsius or just above was worth the effort in constructing this.

/Ake