This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
doc:lps:twr-tdma [2017-07-18 15:37] arnaud [Abstract] |
doc:lps:twr-tdma [2017-07-18 15:41] arnaud [System performance] |
||
---|---|---|---|
Line 11: | Line 11: | ||
The disadvantage is that the tag has to actively send packets, it means that two tag cannot range at the same time and so some synchronization mechanism has to be put in place to allow multiple tag to use TWR measurement concurrently. | The disadvantage is that the tag has to actively send packets, it means that two tag cannot range at the same time and so some synchronization mechanism has to be put in place to allow multiple tag to use TWR measurement concurrently. | ||
- | With TWR-TDMA | + | TWR-TDMA |
===== Compiling Crazyflie for TWR-TDMA ranging ===== | ===== Compiling Crazyflie for TWR-TDMA ranging ===== | ||
Line 32: | Line 32: | ||
===== System performance ===== | ===== System performance ===== | ||
- | TWR-TDMA is currently implemented with time slots of 4ms. Each time slot is used by one tag to range with one anchor. This means that the ranging rate is of //1/(0.004 * (2^TDMA_NSLOTS_BITS)// | + | TWR-TDMA is currently implemented with time slots of 4ms. Each time slot is used by one tag to range with one anchor. This means that the ranging rate is of //1/(0.004 * 2^TDMA_NSLOTS_BITS)// |
- | The more timeslots, the less often measurements can be used to estimate the tag position and so the performance of the position estimate will deteriorate. For a great number of tag the [[doc: | + | The more timeslots |