We have understood the System architecture for MDEK1001 based nodes and gone through “DWM1001 System Overview.pdf”. ALso have gone through the BLE API under “DWM1001 Firmware API Guide”.pdf. As a part of gateway offering the recommendation is to use a Raspberry Pi B(RPi) board interfaced with DWM1001 (acting as a bridge node). The following are the queries:-
- What was the rationale to use UWB as the communication means to Gateway rather than BLE? We have used nRF52832 separately in other products and were able to achieve a range of >100m inside buildings. Why wasn’t BLE selected as the communication technology to Gateway? Are we missing any reasons/advantages to UWB tech for communication?
- If we want to use BLE as the communication medium for Anchors & Tags to configure, commission and send 2-way data with a nRF52832 board(same chip nRF52832 used in DWM1001) (nRF52-DK: https://www.nordicsemi.com/Software-and-Tools/Development-Kits/nRF52-DK), is there any BLE Central software/firmware that can be loaded onto nRF52-DK and test for commissioning, configuring and retrieving the position information at periodic intervals?
- The other advantage of using BLE is we can make any third party gateway supporting BLE as the Gateway (unlike RPi which needs a DWM1001 Bridge). This will help for commercial solutions as we cannot use RPi. Am i missing anything? Please advise.
Please revert back.