node-js node-red node-red-contrib-socketca VSCP

Update 1.2.8 to node-red-contrib-socketcan

A new version of the package node-red-contrib-socketcan (1.2.8) was published at 2022-06-10T15:36:37.310Z

- Fixed problem with dlc when sending remote frames.
node-red node-red-contrib-socketca node-red-contrib-socketcan socketcan VSCP

New version 1.2.7 of node-red-contrib-socketcan

A new version of the package node-red-contrib-socketcan (1.2.7) was published at 2022-06-10T11:44:12.391Z

- Fixed problem with sending of RTR frames.
node-canal node-js node-red node-red-contrib-canal node-red-contrib-socketca node-red-contrib-socketcan node-red-contrib-vscp node-red-contrib-vscp-tcp node-red-contrib-vscp-tcp node-vscp node-vscp-class node-vscp-helper node-vscp-tcp node-vscp-type VSCP

VSCP Update: node & node-red

All node and node-red nodes hav had there dependencies updated.


State of VSCP

Sometimes you walk and walk and still never seem to arrive at the destination. The development of the new VSCP Works is like that sometimes. It takes time.


There is working session handling and working configuration handling and almost working discovery. Next up is the bootloading.

So one day I will announce a release… maybe…

I currently work with some demo code that uses the VSCP tcp/ip link protocol on embedded hardware. I do an implementation of the level II protocol handling with it so there is a lib to use if someone wants to implement it. This work is needed for me to test full level II functionality in VSCP works . For me, to work on the low-level hardware again, is a real treat. Love it! That is the place where I enjoy life the most.

Summer is coming and I will be out of the office for vacation for most of Juli. I hope all of you reading this will have a very nice summer.

Have fun friends!

node-js node-red node-red-contrib-vscp node-red-contrib-vscp-tcp VSCP

New version 1.2.10 of node-red-contrib-vscp

npx npm-check-updates -u
A new version of the package node-red-contrib-vscp (1.2.10) was published at 2022-05-17T16:22:29.576Z
node-red node-red-contrib-canal VSCP

New version 1.0.12 of node-red-contrib-canal

A new version of the package node-red-contrib-canal (1.0.12) was published at 2022-05-17T16:12:53.273Z
node-red node-red-contrib-socketcan VSCP

New version 1.2.6 of node-red-contrib-socketcan

A new version of the package node-red-contrib-socketcan (1.2.6) was published at 2022-05-17T14:54:34.787Z

VSCP Works +

Though I should share some screen dumps of the upcoming VSCP Works +.

Main window
Session window – With event info.
Session window – Event count
Session windows – Event timing
Remote device configuration window – Registers
Remote device configuration window -Remote variables
Remote device configuration window – Files

New version of the #VSCP specification

A new version 1.13.0 of the VSCP Specification is available.

  • Added proper description of JSON formatted MDF files.
  • Two new standard register positions has been added for ‘firmware code’
  • Updated MDF info. ‘abstraction’ has been changed to ‘remotevar’. ‘abstraction’ can still be used. ‘name’ attribute is not language dependent anymore.
node-red Raspberry Pi VSCP

Interesting phenomena

The picture above show readings from furnace in our house (the HULK). The first diagram show the boilers water temperature. One can see when the stove is active. As seen it failed to start this morning. Alarming me with SMS, email and telegram so I could handle it.

The second diagram show the temperature in the core of the warm water reservoir. This is the supply of hot water.

Third picture is hot water temperature measured on the pipe out to the house from the hot water reservoir. When no water is taped the temperature will fall. When hot water is taped the temperature will rise to the hot water temperature as expected.

The interesting part here is the sensor connected to the boiler container. It does not do aging very well and will go more an more of over time showing a higher temperature then it should. The sensor is a 10K NTC sensor. I have changed this sensor several times now over the years and I probably have done this twice a year.

I use many NTC sensors and this is the only one that behaves in this way. No idea why!?

The setup here is a Kelvin NTC 10K connected to a Raspberry Pi running the latest version of the VSCP Daemon which send the data to three MQTT brokers. This data is in one place handled by a node-red setup and the UI above is shown on that machine.

Investigation of this continues…