Category: VSCP
New German VSCP user project
A German guy just started a new VSCP project recently. Will be nice to follow.
The second release candidate of the VSCP & Friends Sodium release for Windows is available for test here https://sourceforge.net/projects/m2m/files/VSCP%20Software/1.1.0%20Sodium/
Please test to install and report any problems.
Cheers
/Ake
The first release candidate of the VSCP & Friends Sodium release for Windows is available for test here https://sourceforge.net/projects/m2m/files/VSCP%20Software/1.1.0%20Sodium/
Please test to install and report any problems.
Cheers
/Ake
quiet != no business
Not much info other than links recently on this channel but that does not mean that noting is happening. As usual there is +16h/day passes here at the Paradise of the Frog AB and we are working hard to get the Sodium release of VSCP out. YES it has been delayed and this is due to some findings in the serial driver which lead to some other changes in there to. Took some time but are fixed now. It is an amazing and useful driver now I must tell you.
At the moment we are adding some last BIG things and then a release candidate will be available for download.
One of the big questions at the moment is to decide if Lua or Javascripts should be used for the internal script engine in the VSCP daemon. If you have thoughts on this feel free to comment. This same scripting support will eventually also come to VSCP Works. But this is a life decision. Not easy to change after a decision is taken.
Why a scripting engine in VSCP daemon? Well with it you can execute a scripts when an event is received. Thus doing a lot of dynamic things or just if/then handling or simple things like OpenHAB for example do. If we ever get some active UX development this can be extended to a drag and drop interface to make things happen. A bit like node red if you like.
On the hardware side three boards still is in the pipe. Accra, Vilnius needs some final code and are next in line. Frankfurt Eth prototypes are on the way to us at this very moment and will be done after that. Kelvin 1-wire Frankfurt BT will come next. And I can tell you we have a lot more brewing.
So now you know that we are still working here in the north of Sweden. We will be back with more info soon.
Can’t promise you fame and fortune. But it can be nice to just be part of something that will change the world.
There is a lot to do of course. It always is. But bindings to different languages (also to languages not in the list) is something that we really need and gives other people a chance to do great things. Yes we can do with libs. that is not based on the VSCP helper lib and interface the REST or the websocket interface of the VSCP daemon.
There is a list here with things that we think it would be nice to see. But there is million of other things you can contribute with. Its fin. Its valuable. Its a world changer.
JOIN US!
Python bindings available for VSCP
Salvo Musumeci has made Python bindnings available for the VSCP helper library. Great work Salvo! You can find his work here.
We need bindings for PHP, Java, C#, Perl, node.js etc also so if you want something to do this fall this is a task to take on.
We have got new sponsoring for the VSCP project. Thank you Iain and Steve for your kind and valuable support to this work.
Important change to the VSCP Specification
I made an important change to the VSCP specification today.
The CLASS1_INFORMATION, Type = 9 (0x09) Node Heartbeat has previously not been mandatory to implement for a node. But this has changed and it is now mandatory as the only exception of a mandatory event to implement outside of the CLASS1.PROTOCOL class. The same is true for the Level II event CLASS2_INFORMATION, http://www.vscp.org/docs/vscpspec/doku.php?id=class2.information#type_2_0x0002_level_ii_node_heartbeat
The recommended interval is 30-60 seconds between heartbeats bur exception can be made for nodes that have to sleep for a longer time.
The reason for this change is that it makes it easier for wireless nodes to announce there presence as they are harder to scan as wired modules.
Changes to the VSCP specification is as always listed here.
A new class has also been added today. This is the Level II class Class=1060 (0x424) Measurement float. This class is a companion class to the Class=1040 (0x410) Measurement string. Both follow the CLASS1_MEASUREMENT class types except that it allow for more sensors (0-256) and more units (0-256). Obviously the Level I definition is the interchangeable one.
NOT ANOTHER MEASUREMENT CLASS you might scream.
Yes there is plenty of them already. But this double precision floating point class can make some order again and I will add translators from all other classes to this class in the daemon and in the CAN4VSCP driver. So for all work at higher levels these to classes are the one that should be used. At least if not communicating things down to Level I nodes.
Be Hungry – Stay Foolish!
/Ake
Oooooops, wrong day!
Ops! Wrong day. VSCP birthday is today. Oh well another day of celebrations does not hurt. “Hand me the cake…” 😉