The datapaths inside the node had been revised, so one step closer to the presentable POC.
Currently, on the testbed, there are 3 RPi nodes, one of set to MASTER, the other two are SLAVEs. The forth node, the webassembly node at https://hyperborg.com/demo is not yet updated, so it does not connect to the mesh yet.
Some thoughts about MASTER/SLAVE (This would be updated to Initiator/Target later on): The main concept of HyperBorg is to be decentralized, thus one centralized node that controls all the others does not fit into the future plan. Although, in the pre-POC era it certainly helps debugging communication issues.
As you might know, the mesh maintenance and discovery is done in the lower level (CS and Beacon), so it should not be a big issue to switch from master/slave to virtual token ring or other more balanced, more decentralized approach.
But for now, we are at a master/slaves setup, as follows: – the master loads up the n8i8op modules and the ws3500. This way, the light switching relay board is controlled by the main HyperBorg Node. This node has no graphical output. – the two other slaves are also RPis having TFT display.
Currently, the WS3500 weather station sends all the weather data to the main node, which instantly distributes the information to all the slaves.
The path of the measured variables could be tracked and arriving into the slaves, but they are discarded at the Slotter (the highest) level, since the GUI is not yet capable of using them.
In short: the communication is now established between all three nodes (and maintained if any of the nodes are drop out from the mesh) and all Slotter levels are capable of communicating with each other.
The next step is to create some buttons and weather tiles/widgets for the GUI. When that is achieved, the POC level is complete!