Adaptive sensitivity: auto-tune LiDAR Lite mode based on signal strength
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- arduino, cpp
- Domain
- embedded-iot
Research direction
First verify NorthernWidget/Project-Apis#18 and the 32-byte register map redesign, since both are prerequisites. Then trace the library's ranging cycle and SensitivityMode handling, using register 0x0A for signal strength and 0x0B for configuration. Done means an opt-in adaptive mode with hysteresis that preserves the default behavior and switches modes only when warranted.
Written by the indexing model from the issue text.
Description
Summary
Once signal strength is exposed by the firmware (see NorthernWidget/Project-Apis#18), the library should optionally use it to automatically select the optimal SensitivityMode for current conditions.
Motivation
Conditions that affect LiDAR Lite return quality (target reflectivity, range, ambient light) vary in the field. Static sensitivity settings are a compromise. An adaptive loop could improve range and reduce false positives without manual reconfiguration.
Proposed approach
- Add an opt-in
autoSensitivitymode (off by default to preserve existing behaviour). - After each ranging cycle, read the signal strength value from firmware register 0x0A.
- Apply a simple hysteresis scheme to switch between
SensitivityModevalues — avoid hunting between modes on noisy boundaries. - Write the new mode to firmware register 0x0B (config, writable) when a switch is warranted.
Notes
- The feedback loop runs at the firmware's ~200 ms cadence; mode changes take effect on the next firmware cycle, so there is inherent lag. Keep the hysteresis wide enough to avoid oscillation.
- A firmware-side implementation would be more responsive (direct LiDAR Lite register access), but the library approach is easier to iterate on without a firmware flash.
Dependencies
- Requires firmware support: NorthernWidget/Project-Apis#18 (signal strength at register 0x0A).
- Requires the 32-byte register map redesign to be in place (config at 0x0B, not 0x01).
- Dominant language
- C++
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from NorthernWidget/Apis_Library
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
All issues in NorthernWidget/Apis_Library
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Sensor initialization takes very long when `--initial-sim-time` is set to current UNIX timestamp Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
gazebosim/gz-sensors#662 · 1 comment ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
LadybirdBrowser/ladybird#12123 ·