Hi, we need to develop an industrial application with more than 150 nodes.
Each nodes is solenoid actuator and a sensor
There is no concurrent actuation of those devices, in fact I've to connect sequentially to each of them at startup, than activate some of them during the process and read the sensor data.
The data rate is very slow, and I've not power supply problems (I've a permanent supply rail).
We need to design the entire solution, the slaves devices (actuator and sensor) and the central master unit that manage the operations.
The single slave units has to be repleceable, if possibile without using a "dip switch" like addressing, so we have to implement a dinamic addressing of new devices (using a push button for example to put them in "addressing mode"). I think a Star network will be simpler.
What is the Silabs suggestion to design this product, for slaves and central unit ? BLE, or proprietary stack?
We would like to use some certified module with integrated antenna, 2.4GHz .
Thanks in advance
The following application note will give bigger insight to the available possibilities:
Thanks for the reply!
I've read the document, It's mainly focused on Zigbee protocol and the difference between NCP e Soc.
But my concern is more about the right choice of protocol for high number of nodes, with no current consumption problem.
Bluetooth has frequency hopping (in the same facilities it's possible to have more equipment, each with 200 nodes) and it has probably the best support I think, but need royalties.
Moreover is it suitable for so many nodes (although only few of them transmit the information during work)?
As I don't have power concern, could also wifi be a solution?
What I'm searching is more the right choice of protocol / device to have a fast time to market product, with no hassles , few certification problem (i've opted for 2.4 GHz to be worldwide), as my devices work in a closed condition. The Slaves talk only with a proprietary master board so i have the maximum flexibility on choosing the best protocol.
Sorry for this lately reply, I just missed your previous post.
Unfortunately, I do not have too much experience with Bluetooth, so I cannot compare it to the other protocols in your use-case. Yes, I know the basic attributes, regarding bandwidth, etc, but if you power the device from the line, then it should not matter. But you mentioned, for Bluetooth "but need royalties": as I know it is not 100% true. So if you make a Bluetooth device and if you would like to use the Bluetooth logo on this device, certified with Bluetooth SIG, then you have to pay royalties for the Bluetooth. If you use the Bluetooth protocol as "proprietary" protocol, so the PHY, the data format, and everything is same, just the device will not certified with Bluetooth SIG, then it is free. But you cannot sell it as Bluetooth compatible device, but my guess it is no problem in your case.
My guess, in this case, if you familiar with one of the available protocols, and you have idea how could you do with it, this protocol will be the fastest solution.
Externded star topology also achievable with: Zigbee, Connect protocols, (maybe with Bluetooth or Bluetooth MASH, but I am not familiar with BL protocols). Zigbee and Connect basing on 802.15.04 standard, so the lowest level of the communication should not be implemented. (this level implemented by the stack)