Skip to content

Releases: thotro/arduino-dw1000

Maintenance release

12 Jun 14:54
dc07760
Compare
Choose a tag to compare

see git log for changelog

Maintenance release

12 Jun 14:31
2b3f1ba
Compare
Choose a tag to compare

skipped version 0.7 to clarify that there are a lot of changes since 0.6

for changelog see git log

Stable ranging (with room for optimization)

21 Jul 10:57
Compare
Choose a tag to compare
  • Bugfixes in tuning
  • Power management, antenna delay
  • Received message stats (quality, power levels)
  • Good ranging results, but still with room for optimization

Arduino library (1.5 conforming)

06 Jul 14:33
Compare
Choose a tag to compare
  • Changed project structure to be conforming with Arduino library format (v1.5)
  • Corresponding refactorings

Support for timing and different operation modes

03 Jul 22:39
Compare
Choose a tag to compare
  • Stable transmission at all modes: 110kbps, 850kbps, 6.8Mbps, different frequencies and preamble length.
  • DW1000Time for convenient timestamp handling (i.e. conversion to actual time or distance)

Stable RX/TX

20 Jun 00:36
Compare
Choose a tag to compare

Stable transmission/reception of messages with tuned (and also not-tuned devices, if in default mode) devices. Tuning code still needs to be checked and different configurations thoroughly tested.

Application reference codes like sender/receiver and ping-pong work without any troubles. Two-way ranging still needs a better (i.e. more fault-tolerant) message exchange protocol to work as expected (will be a main focus for v0.4).

Custom event callbacks and static DW1000 object

27 May 00:19
Compare
Choose a tag to compare
  • Interrupt handling and configuration is removed from Arduino user code and instead callback functions can be provided to react on certain events. At the moment only successfully sent and received messages can be handled via callbacks. Error handling, other device status changes will shortly follow.
  • Now there is just one DW1000 object and no construction of (arbitrary many) ones is intended anymore. From a design perspective code gets easier to use this way, because the proper management of multiple fully operational devices could be tough - and is very likely not even an actual use case.

Basic RX/TX

19 May 23:04
Compare
Choose a tag to compare

Basic RX/TX support with some options configurable. Still sometimes unstable, since proper error/exception state handling is missing.