ADAR changelog image

Documentation and tools

ADAR Firmware changelogs

Public changelog for ADAR firmware

Each new entry in this changelog will be shared with our direct customers through a mailing list.

Want to test or deploy ADAR? Reach out to us at hello@sonair.com.

[v1.8.8] 2026-05-11

Compatibility

  • Hardware: v1.3
  • ADAR Designer: v2.0 or later
  • ADAR API: v2.0 or later.
  • User manual v1.1 except chapter 6.x: use the new ADAR Designer user manual instead of chapter 6. Furthermore, the appendix "A.E. Public API resources" is outdated; see the ADAR API repository for updated public API.

Added

  • Checksum on all network communication: All ADAR API resources now include a checksum on every request and response, providing integrity protection against transmission errors. As a consequence, all resources have been bumped from `v0` to `v1`. See the ADAR API repository for details.
  • Real-time validator subsystem: A dedicated validation subsystem continuously monitors the main processing pipeline, detecting and reacting to faults in real-time.
  • OSSD compliance: OSSD output monitoring is enabled. The device is compliant with the OSSD standard.
  • Secure device access: Modifying device behaviour now requires user login with authentication tokens.
  • Safe configuration management: Changing sensor configuration now requires login and a disabled device. The end user can verify that the configuration matches requirements. New resources: `config/report/v1`, `config/activate/v1`, `config/crc/v1`.
  • Reboot resource: Added `reboot/v1` command to the ADAR API for device restart via the CoAP protocol. This also enables the restart button in ADAR Designer.

Changed

  • Improved detection near the sensor: Detection performance in the region close to the sensor (the first ~40 cm) has been improved compared to the limitations documented in `v1.1.0`. In particular, this region no longer needs to be empty when the device boots up or when the transmission code is switched.
  • Improved handling of weak objects near strong reflectors: Tuning improvements reduce false negatives when weak scattering objects are located close to strong reflectors.
  • Distance to floor default: Increased the default value for distance to floor from 0.2 m to 4 m.
  • Safe input debouncing: Changes on safe input lines must now be stable for 5 ms before the new zone takes effect.
  • Recovery after panic: After a panic, the device now performs a cold reboot and resumes operation instead of remaining in a panicked state.
  • Performance optimizations: Various signal processing optimizations.

Fixed

  • Fixed a bug in interference detection.
  • Fixed CoAP state resource returning incorrect response code.
  • Fixed a bug that disrupted the factory reset LED indication.

[v1.1.1] 2025-11-3

Added

  • Processing that merges false detections in front of and behind a strong reflector.
  • Hostname support (set to adar-<serial-number>, e.g. adar-123). Can be used as an alternative to IP address on many modern networks.
  • Support for hardware version 1.3 (backward compatible with older version hardware).

Changed

  • The ADAR device will no longer remove network observers that time out. When the observer list is full, existing observers are replaced with the following priority: first,  observer with the same IP address; next, the most recently added observer.

Fixed

  • Improved signal processing.
  • Network stability improvements.

[v1.1.0] 2025‑09‑19

Added

  • Algorithms for detecting objects in close-range (0 cm - ~5 cm) and medium-range (~5 cm - 40 cm). For optimal performance, these areas must be empty when the device boots up and if you switch transmission code.
  • Objects in close-range can not be accurately positioned. The device will instead report that it is being obstructed.
  • Objects in medium-range will be positioned.
  • Algorithm that improves angular accuracy across different temperatures.
  • Additional device states: DISABLED and CONFIG. Using these is not required yet.
  • Automatic reboot if Ethernet communication freezes.

Changed

  • Various optimizations and performance improvements. The highest frame rate is increased from 10 Hz to 18 Hz.

Fixed

  • Corrected bug so that we now allow multiple sync servers.
  • Bug that caused CoAP transfers of large pointclouds to not time out properly.
  • Bug where the CoAP-server did not accept retransmission attempts during block-wise transfers.
  • General improvements and bugfixes

Known limitations

  • Ethernet communication can in rare cirumstances freeze. As a temporary workaround, the device will automatically reboot if communication freezes. Under normal traffic load, this event is expected to occur seldom and infrequently.
  • There is still a small blindspot within the medium-range volume (~5 cm - 40 cm) caused by the transmitter itself being detected, and having to be explicitly ignored. These detections may appear as false positives (outside of this blind-spot) in certain conditions. In previous firmware versions the entire close- and medium-range volumes were blind. See the ADAR User Manual for more information.
  • If a very strong acoustically reflective object enters the medium-range volume (~5 cm - 40 cm) the ADAR sensor may experience a drop in frame rate.

[v1.0.1] 2025‑07‑04

Fixed

  • Exclusion zones that extend to +/- 90 degrees always excludes points on this edge.

[v1.0.0] 2025‑07‑04

  • Initial ADAR firmware release.

No items found.

No items found.

Your questions, our answers

What is the angular resolution of your sensor?

This concept is not easily definable with ADAR because a pulse is not sent out in a discrete angle. If you are familiar with LiDARs, angular resolution is the angular distance (in degrees) between distance measurements of 2 beams.

This does not apply to ADAR because it does not emit beams.The angular precision is 2° straight ahead and 10° to the sides. The sensor is able to distinguish between multiple detected objects, if the objects are separated by more than 2 cm in range relative to the sensor or by more than 15° from each other.If the two objects are positioned closer than 2 cm or 15° from each other, they will be detected as 1 object.

Precision is a measure of the statistical deviation of repeated measurements on a single object’s position.

What is the maximum of points you have in the point cloud?

The maximum number of points is very rarely a limitation to the sensor’s performance, because the total number of points needed to fully sense a scene is low. The ADAR technology reports 1 point per surface on any object, making the total number of points low. This is opposite to what one might be used to from LiDARs.

The relative sparsity of the point cloud is a fundamental feature of sound-based sensing, but this is not a sensor limitation as the point cloud will always contain at least 1 point per object within line of sight from the sensor.

Can the sensor distinguish between humans and objects among detected obstacles?

ADAR does not do object classification. The sensor is for people and object detection.