Simblee => BLE and Low Level Development => Topic started by: danlsk on December 01, 2016, 12:37:40 PM
While BLE Mesh is about to debut soon (not dependent on Bluetooth Core 5.0 (http://rethinkresearch.biz/articles/bluetooth-5-0-on-the-horizon-but-still-playing-catch-up-in-mesh/)) , both SimbleeCom and NRF Open Mesh are supporting unlimited of devices.
NRF Open Mesh is considered connection-less, theoretical limit is perhaps 500 devices. Latency is based on latency per hop (https://devzone.nordicsemi.com/question/102401/nrf-openmesh-node-to-node-latency/) you set.
SimbleeCom: unlimited connection, 3ms latency.
1. Which is more superior e.g. maximum connection, latency by comparison,development time? Or why should one consider SimbleeCom vs the others?
2. Develop now or wait for official Bluetooth Mesh? I supposed how soon your customer wants it.
3. Based on SimbleeCom & NRF Open Mesh, how is the compatibility and migration toward official Bluetooth Mesh? I supposed the consideration is interoperability with upcoming Bluetooth Mesh products if a product choose to do so. Sometimes, you wonder just OTA DFU will help to upgrade to support that. Btw, Bluetooth mesh is meant to support 4.0 as well.
Just for discussion. Of course, those who have experienced Open Mesh and SimbleeCom development can tell more about the differences.