Closed WeikangKong closed 2 years ago
If we choose option 2, how about e.g. 3.startMics
where 3
is the device number?
If we choose option 2, how about e.g.
3.startMics
where3
is the device number?
I think it is also a good option
Who define the define number? Do we need a command or should be hardcoded?
Who define the define number? Do we need a command or should be hardcoded?
How does BT protocol identify different nodes? I guess we can have a dictionary in the configuration file. Something like: {"Senor nodes": {"1":bt_id1, "2":bt_id2, "3":bt_id3}, to connect the number to actual device?
In terms of configuration file I would keep a single configuration fie, but add another top layer with keys as sensor nodes something like { "node_1":{
I'm closing this, the latest releases are stabilising this nicely.
Feature request
Add possibility to operate multiple sensor nodes with the single base base station,
Open questions:
Command in multi-device context
@JuliusPlindastus @tommasopolonelli @hmllr @time-trader Since we are extending the firmware to support multiple peripheral devices, it is a good time to discuss how you would like to issue commands in the multi-device context. To finalize the format of the command, the following questions need to be answered:
Configuration file
Configuration file contains sensor properties as well installation metadata. We should probably allow for possibility to have different sampling frequencies on different nodes. Should we keep a single configuration file?