UWB DWM1001 dev

Development Board #

  • DWM1001C Module
  • STM32F072 as J-Link OB debugger
  • USB and battery conenctors
  • Raspberry PI Header connector
  • User Leds buttons

DWM1001C Module #

  • DW1000 Transciever
  • TWR-RTLS : Two Way Ranging - Real Time Location System
  • nRF52832 for a Bluetooth API
  • LIS2DH12TR STM 3-Axis Motion Detector

The product page includes datasheets, schematics, firmware,…

DW1000 Transciever #

  • IEEE 802.15.4-2011 UWB
  • 6 RF bands : 3.5 GHz - 6.5 GHz
  • Datarates : 110 kbps, 850 kbps, 6.8 Mbps
  • Voltage 2.8 V - 3.6 V
  • sleep 1 uA - deep sleep 50 nA
  • TWR, TDOA : Two Way Ranging, Time Difference Of Arrival
  • Location precision : 10 cm
  • Range : 290 m

Software #

Gallery #

  • 01 Unboxing : A cable and x4 usb angles provided that can keep x4 Anchors up right.
  • 06 Additional Passive Tag as serial listener : Make sure that the listener is configured with the app to join the Network intended to be listened to

FAQ - Discussion #

How difficult is it to setup a demo ?
It’s actually surprisingly easy. The hardest step is to install the App which I could not find on the appstore and Android prevents installing .apk by default, a trick was to long press “save link as” as simple click does not work, then in the settings the ip of the server has to be set as trusted. The rest is very well documented in the Quick Start guide.
What to do if the localization in the app is terribly wrong ?
By default the refresh rate of stationary tags is set to 10 sec, and the algorithm has an additional filter that prevents the tag position from moving to a new absolute measure and rather only improving by a given percentage. By incrinsing the “Stationary update rate” within the range of ~ 2 sec, it’s possible to get an expected user experience with a tag visibly converging to the correct location.
Is it possible to communicate between DWM1001C and DMW1004C ?
Yes, given that they both use the same DW1000 tranceiver. But they have two different Host microcontrollers so algorith,s have to be ported on both targets nRF52 and STM32 and calibration has to be done accordingly.