diff options
| author | Selene ToyKeeper | 2025-04-29 00:10:31 -0600 |
|---|---|---|
| committer | Selene ToyKeeper | 2025-04-29 00:10:31 -0600 |
| commit | 04f43399041029b9d5a03160be6ba0588325fad0 (patch) | |
| tree | 53bfb6e033c42665b8ab7b5221e85cb969d6a041 /hw/hank/lume-x1/readme.md | |
| parent | memester egg (diff) | |
| parent | changed hank-lume-x1 model number back on 2024-09-28 (diff) | |
| download | anduril-04f43399041029b9d5a03160be6ba0588325fad0.tar.gz anduril-04f43399041029b9d5a03160be6ba0588325fad0.tar.bz2 anduril-04f43399041029b9d5a03160be6ba0588325fad0.zip | |
Merge branch 'hank-lume-x1' into trunk
Finally remembered to merge this. Thought I had done it months ago...
Anyway, now that I've been able to test it on production hardware,
everything seems fine. The super-low firefly modes are a bit more
usable on production hardware too. Level 1/150 is dimmer than the low
aux LEDs, while level 2/150 is about as bright as low aux.
* hank-lume-x1:
changed hank-lume-x1 model number back on 2024-09-28 for some reason, and didn't commit... saving now to change branches, but should delete this commit if it turns out there was no reason for it
hank-lume-x1: minor calibration and cleaning - calibrated party strobe - removed duplicate or commented-out code - added a basic readme
hank-lume-x1 cleanup and calibration, part 1: - changed model number from 0281 to 0171 - cleaned up blink_negative and AUXLED_RGB_DIFFERENT_PORTS a little (but the latter needs a complete refactor, as soon as the hardware abstraction code can handle aux LEDs better) - cleaned up USE_LONG_BLINK_FOR_NEGATIVE_SIGN a little - removed USE_OTG_IN_MOMENTARY since it's not actually used - moved hw/loneoceans/lume-x1-avr32dd20/* files into hw/hank/lume-x1/ - superficial cleanup on hank/lume-x1/hwdef.* - removed some of the extra stuff from hank/lume-x1/anduril.h - adjusted calibration (especially ramp table) on hank-lume-x1 (ramp shape is pretty close to a D4K-boost now, but with more firefly modes) (calibration is based on a sample size of 1, further testing needed)
cherry-picked hank-lume-x1 code from https://github.com/loneoceans/anduril/commit/d83ebb75dab8c462b7efa841bccc00a136ff15a2
Diffstat (limited to 'hw/hank/lume-x1/readme.md')
| -rw-r--r-- | hw/hank/lume-x1/readme.md | 34 |
1 files changed, 34 insertions, 0 deletions
diff --git a/hw/hank/lume-x1/readme.md b/hw/hank/lume-x1/readme.md new file mode 100644 index 0000000..eba5949 --- /dev/null +++ b/hw/hank/lume-x1/readme.md @@ -0,0 +1,34 @@ +# Hank / loneoceans Lume X1 40W + +Regulated boost driver for Hank lights (Emisar / Noctigon) by loneoceans. + +Second Hank light to use the new avr32dd20 MCU. Performs better than older +MCUs and provides more space for extra features and future firmware updates. + +Originally from https://github.com/loneoceans/anduril + +Features UDR (Ultra Dynamic Range) for smooth dimming all the way down to +*literally zero*, meaning an effectively infinite dimming ratio: + +- 3 power paths or "gears" for the regulator chip's sense resistors: + - Firefly "gear": 0 to ~0.1 lm + - Low "gear": ~0.1 to ~40 lm + - High "gear": ~40 lm to full power (2k or 3k lm?) +- Internal resolution of 2500 steps per "gear" allows very precise control over + brightness. Anduril's 150 step ramp does not fully take advantage of this. +- Constant current, no pulsing or flicker or ripple +- No preflash +- No need for jump start; regulator has a quick response at all levels + +The firefly part of the ramp is compressed to just a few levels, to avoid +making the rest of the ramp artificially low. It aims to be reasonably +consistent compared to the ramp shape of Hank's other lights, but a few levels +at the bottom are set aside for moon and firefly modes. + +The regulator can go much, much lower than the brightness of the button LEDs, +but there isn't much point because the glowing button overpowers the main LEDs. +The button and aux LEDs (on low) also use significantly less power despite +being brighter, because they do not require the MCU to be awake. So that part +of the ramp is mostly omitted. However, it can be added with a firmware +modification if desired. + |
