The Bandwich system’s network is extremely modular and flexible and it can meet all the needs of modern IoT ecosystems. Its protocols and frequencies allow it to achieve great and small distances and to communicate at the same time with standard devices such as smartphone, tablet or PC. This is made possible by three communication protocols: 868 Mhz radio module, Wi-Fi module, BLE 4.2 module.
The network is designed starting from a two-level star topology, or working point-to-point without using different hardwares.
Devices that can be configured directly from a smartphone by using a wizard after setting the hardware parameters.
Cloud or Local
You can shift the communication on a local or cloud server in a few steps.
Depending on the configuration of the device it is possible to guarantee a battery life consistent with its operation.
Radio Module Configurations: Wi-Fi, BLE 4.2, 868 Mhz
The Radio module can be configured differently according to its function within the network. According to its nature, it will use one or more radio protocols to discharge its functions.
Configured as Master, the Radio module is able to communicate with all other players in the network using 802.15.4, with mobile devices via BLE and submit endpoint data via Wi-Fi. The Master can equip up to 8 add-on expansions.
In Slave mode, the Radio module establishes a bidirectional connection with a Master and it is able to communicate with mobile devices via BLE. In this mode, the Wi-Fi is turned off and the module can equip up to 2 add-on expansions.
In the Tag mode, the Radio module turns off all radio protocols except the 802.15.4 used to send Broadcast Messages that can be received from any Master reached by the message sent. The module can only equip the Environment add-on (soon also the Expansion add-on).
In the Bridge mode, the Radio module acts as a bridge between two Masters. The most external Master, however, can not have Slaves associated with it, but it can equip up to 8 add-on modules.
The Device can communicate with nearby devices via Bluetooth Low Energy. It is possible to develop a native mobile app to create ad hoc services of proximity.
The End-Point is a MQTT Broker. You can set any cloud Broker or use a Broker in a local server at the ecosystem created.
Each network player can be equipped with one or more add-on modules, where each of them, among the settings, has a time window (min 200 ms, max 9 min) within which the device reads the sensors that it is equipped for 10 times. Discarded the two extreme values, it makes an average of the remaining 8 and the data is entered in the network: reading will then be as stable and reliable as possible. A device may have add-on modules that work with a different temporal frequency between them.
For each message that the Master receives and forwards to the MQTT Broker, whether it is sent by a Slave or Tag, the RSSI value of the message, the timestamp and an indication showing whether the device that has generated the message is powered via cable or battery and, in the latter case, the charge level of the battery itself.