Author: admin

The following hardware modules will be closed source from today

can4vscp_accra – Counter module.
can4vscp_sanfrancisco_barometer  – Barometer module.
can4vscp_humidity – humidity and temperature module.can4vscp_beijing – I/O- module.
can4vscp_vilnius – AD- module.
can4vscp_odessa – Expansion module.
can4vscp_kelvin_1wire – 1-wire temperature module.
can4vscp_frankfurt_rs232 – RS-232 interface to CAN4VSCP
can4vscp_frankfurt_gprs – GPRS interface to CAN4VSCÅ
can4vscp_newyork_lcd_display_controller – Display controller
can4vscp_frankfurt_eth – Ethernet <->CAN4VSCP
zeus_expansion_roma – Ethernet controller.
zeus_expansion_moscow
can4vscp_power_injector
zeus
zeus_expansion_napoli
zeus_expansion_leicester
zeus_expansion_kiev
zeus_expansion_budapest
zeus_expansion_brussels
blitz
thunder
can4vscp_frankfurt_ble
can4vscp_frankfurt_bridge CAN4VSCP <-> CAN4VSCP
can4vscp_frankfurt_rs485 RS485 <-> CAN4VSCP
can4vscp_frankfurt_usb  USB <-> CAN4VSCP
can4vscp_kelvin_9700
can4vscp_kelvin_multisensor
can4vscp_kelvin_smt160
can4vscp_kelvin_thermocouple
can4vscp_Loos_temp_control

Paris and Kelvin NTC will be open and free as before for reference as will one or two RF modules resp.Ethernet modules.

Someone may ask why? The answer is that open source has not been working for these modules and I just don’t want to throw away the 1000h of work I put into them.

It’s been quite some time now since the last release of VSCP & Friends. Sorry to say it will be a few months more until the release is out. Why? Mostly because there is a lot to do and if Google and the likes can do a man year in a week a man year is a man year for someone working alone on a project as I am.  But there is a lot of nice functionality coming so it is hopefully worth the wait.

Of course you can use the head code. But beware that database structures will change still for some time and if you use head code please remove all configuration data including databases so it get built from scratch. This will of course be taken care of automatically when the release is out.

And again of course if someone want to take part in the project (there is many tasks) or sponsor it please let me know.

Now it is possible to use execution of JavaScript as a result from a triggered action in the decision matrix of the VSCP Daemon.  Things that is triggering an action can typically be events from external nodes or internal VSCP daemon generated events.  For example a measurement value can be sent to a remote cloud service or an ON event can enable some special on-board functionality or just toggle a pin on some output. The possibilities are endless.

With the VSCP decision matrix escape functionality dynamic data can be written into the JavaScript before it is executed. This includes the triggering event data as well as environment information.

File, encryption and socket functionality is available from inside the script plus functions to send event, receive events, handle VSCP remote variables, handle measurements and more.

As a script can be stored in a VSCP remote variable it can be externally edited and functionality can therefore be dynamic.

The new functionality is described here.

Callback functions for VSCP functionality is described here.

LUA scripting will be added later making it possible to do slightly more complicated scripting.