One of the best things of this KNX bus interface, is that it includes all in one single chip. Using the Microchip PIC hardware peripheral it can perform the job of at least two layers. It interfaces the electrical signals, decodes the signal level changing into bits and bits into bytes in a full telegram packet, organized in a way easy to understand.
The same in the opposite direction encoding telegrams down to the signal levels.
Using just simple commands many operations can be executed.

The purpose of this project is to create a Graphical User Interface that enables the end user to control the devices on the bus and analyze the telegrams exchanged between other devices. Recycling the experience achieved in a previous robotic project, I've used node.js as application server. This allows a data exchange via web sockets with the remote client, obtaining a very good user experience because of it quick response to the given commands. More details on this method can be grabbed on that project pages
node.js application server runs on most of the existing operating systems. The code is written in javascript and it is really portable to any platform. Once installed the correct version of the node.js itself and the modules required the code can be simply copied.
I've used a dedicated Cubieboard 2 Single Board Computer to have a system always on, but whatever else SBC or other computer running Linux, OSX or Windows operating system, with one serial port available, can be used.
In contrast to other KNX bus interfaces, most of the dirty job is done by the MCU itself, even buffering a discrete number of telegrams. This enables the usage of standard OS without any strict real time requirements.
In addition to the standard node modules used to publish a web server within the same javascript application, we need the widely used serialport, module to connect the KNXgate, and module, to establish a web socket connection with the HTML5 client.
update on 26-08-2016


Interconnections. From bus to GUI