Niklas Casaril

I may have been a bit too quick to tag this issue in my PR. Whilst it's relevant, I suspect that this issue has a hal_timer enabled in the bootloader...

Hi Horst, The DS nrange does take a bit longer so I'm not sure if it would fit in the tdma slot length without adjusting the number of anchors or...

Also, ttk1000 isn't the bsp for the trek1000 board. We currently do not have a bsp for the trek-kit in this repo. The trek has an older stm32 mcu.

Just a note that I'm able to reproduce the issue using Timer 0 at 16MHz after a couple of hours. I don't think the dw1000 dump with be very informative...

#9 Solves tofdb test requirement.

If you're adding sleep you will need to add wakeup before the next operation. But, as the timing of the next range exchange depends on the timer in the decawave...

The ntwr example sends out a blink every 1s. Every time a node/tag needs to resync you need to receive two of these blinks. So, it'll take about 2s after...

You need to do a bit more work to tear down the tdma and ccp stacks and then restart them. Something like this: ``` static void low_battery_mode(void) { tdma =...

When changing the preamble length and datarate you effectively change the length of the packet. The nrange example is quite a tuned example and have from memory hard set timeouts...

The _HOLDOFF parameter is in us, essentially it should be the length of the packet plus the turnaround time for the board to go from receiving the request to sending...