| Commit message (Collapse) | Author | Files | Lines |
|---|
|
(still need to update file contents afterward,
but doing it in a separate commit so git can detect renames easier)
|
|
(also modified the build scripts to work with the new file structure)
|
|
(just moved files, didn't change the contents yet,
and nothing will work without updating #includes and build scripts and stuff)
|
|
with the regulated-to-direct-drive boundary at a more appropriate spot
|
|
to multi-channel, and removed old K9.3 builds which aren't relevant any more,
and old D4Sv2-tintramp builds
|
|
(also reduced avg standby power by about 15 uA)
(also fixed oscillating voltage mode colors, I think)
The bug happened because sometimes sleep LVP would get triggered, because the
ADC would read zero under some conditions.
This in turn happened because the ADC needs the MCU to be at least partially
awake in order to finish a measurement. So in standby mode, with the MCU only
waking up very briefly to send a sleep tick and go back to sleep, the ADC
required several cycles (like 375ms to 625ms) to finish a single measurement.
This varied depending on how many instructions the MCU executed while it was
awake. In the single-color mode, so few instructions were being executed that
the ADC seemed to time out and abort its measurement, returning a zero. Then a
low voltage warning was sent, which knocked the light back into "Off" mode.
Adding no-op instructions inside the single-color clause was sufficient to
prevent the ADC from timing out, because it kept the MCU awake just barely long
enough. But it was a kludge, and it still took like half a second to finish a
measurement, and the measurements were noisy. It also used more power, because
it required keeping the ADC powered on far too long.
This fix puts the MCU into "ADC Noise Reduction" mode instead, when a voltage
measurement is needed during sleep. It reduces noise to make measurements more
stable... but more importantly, it lets the measurement finish in like 0.5ms
instead of 500ms. So it uses less power and isn't dependent on the number of
calculations the MCU does during each "sleep tick".
As a bonus, this can also measure voltage much more often, while still using
less total energy than before. It was once every 8 seconds, and now it's once
per second.
Avg power use in aux low mode, on a D4Sv2: (avg of 30k samples each)
- before: 101 uA
- after: 86 uA
|
|
instead of full GPL headers (or all too often, nothing at all)
There are a few "FIXME" entries where I'm not sure about the correct copyright.
|
|
- use fancy blinking mode by default
(define USE_OLD_BLINKING_INDICATOR if old slow mode is wanted)
- remove TICK_DURING_STANDBY from all cfg-*.h files because it's
enabled automatically by other features anyway (autolock, memory timer)
- remove STANDBY_TICK_SPEED from cfg-*.h because all the values
matched the default anyway so it was redundant
- set rot66 button LED to high+blinking instead of high+off
(it was only "off" because it ran out of space, and that was resolved)
- enabled fancier indicator by default on fireflies-ui and rampingiosv3,
since its other #define clauses were removed
(not sure if those older UIs still compile, but if so, it's worth
at least trying not to break it)
|
|
- use cycling rainbow mode by default on lights with RGB LEDs
(instead of voltage, because it's better for impressing new users)
- use 2C turbo instead of 2C ceiling (Anduril 1 style instead of Anduril 2 style)
also some other minor housekeeping...
- make all K1 models use consistent rainbow cycling speed
- enable auto-lock and manual memory timer on Emisar D1v2
- remove redundant RGB config on Lume1 (it had incorrect comments anyway)
|
|
because of what appears to be compiler jank or a race condition or
some other highly unusual issue
(fixed by eating up extra clock cycles in the affected code path)
|
|
|
|
(unsure if I'll keep it this way though, or if the old way was better)
|
|
|
|
made blink_once() more configurable (and more reliable on K9.3)
|
|
added a way to include per-model code overrides
added an override mechanism for logic inside set_level()
wrote K9.3's set_level() function
added TINT_RAMP_TOGGLE_ONLY mode for tint ramping
|
|
(main LEDs work now; 2nd LEDs not yet)
(aux and button LEDs work too, plus switch)
|
|
|
|
(patch to aux-leds.c contributed by SammysHP as "acid" mode)
(also removed RGB config for a few lights because they were
just duplicating the defaults, and were redundant)
|
|
|
|
(the idea is "high but not crazy", or around 100% to 150% of thermally-sustainable level)
... and set the default steps to 5 instead of 3
|
|
USE_TENCLICK_THERMAL_CONFIG
(the tenclick thermal thing isn't relevant ever since factory reset was added)
|
|
(because they're close enough that they can use the same code)
|
|
|
|
updates, because it worked well on many hosts before...
|
|
vars, made KR4 rainbow mode faster
|
|
rainbow to be default instead of voltage mode.
|
|
milestone levels
|
|
reliable level
(moon level 1 flickers or doesn't work at all on some hardware)
|
|
|
|
|
|
|
|
|
|
(not complete, but far enough that it installs and runs)
New hardware support features:
- allow using PCINT other than 0 (PCINT1, PCINT2, etc)
- option to ignore voltage ADC while the button is pressed
(because my prototype shorts the voltage divider to 0 while the button is down)
|
|
|
|
|
|
|
|
|
|
LEDs in blinky modes, fixed user feedback when changing aux LED mode, refactored voltage-to-auxled-color code
|
|
(it compiles, but most likely doesn't actually work because it's far from finished)
|
