| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
| |
fixes #85
The Simple UI is meant to be relatively child-safe, and the strobe modes
are not. Users who want unsafe features enabled should use the full UI
instead... and the strobe + mood modes should also have some safety
features added, on drivers which have enough ROM to hold extra code.
|
| | |
|
| | |
|
| |\
| |
| |
| |
| |
| |
| |
| | |
Added fireflies-pl47g2-219 from jim-p.
* pr43-jim-p-ff-pl47g2-219:
Forgot to update model count after the last couple additions
Add Fireflies PL47G2-219 variant.
|
| | | |
|
| |/|
| |
| |
| |
| |
| |
| | |
pr43-jim-p-ff-pl47g2-219
* 'ff-pl47g2-219' of github.com:jim-p/anduril:
Add Fireflies PL47G2-219 variant.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Same as PL47G2 but with FET PWM levels safe for 219 emitters.
Same as difference between PL47 and PL47-219.
PL47G2 base allows low mode for aux LEDs, PL47 does not.
|
| |\ \
| | |
| | |
| | |
| | | |
* pr47-aslotnick-as/low-chan-aux:
use low aux for chan-aux level 0
|
| |/| |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
pr47-aslotnick-as/low-chan-aux
Aux LEDs should be off/low/high at level 0/1/2+, instead of off/high at 1-/2+.
* 'as/low-chan-aux' of github.com:aslotnick/anduril:
use low aux for chan-aux level 0
|
| | | | |
|
| | | | |
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Added support for new Emisar D3AA torch.
* emisar-d3aa:
d3aa: fixed voltage calculation to use 0.02V units instead of 0.025V
d3aa weak battery test: blink 3x instead of 2x, and omit number readout
weak battery detection: use different thresholds for AA and Li-Ion (also, fixed bug where a totally empty li-ion didn't get limited)
d3aa: got weak battery detection actually working, and not letting the magic smoke out of updi adapters any more (probably)
dammit, got alkaline detection half working and then my flashing adapter died (saving progress here so I can work on a different branch)
d3aa fine-tuning: - new ramp - production style config defaults (simple mode, Hank config) - candle tuning - fixed way-too-fast thermal regulation (might still be a bit fast, but it's a lot better)
d3aa: fixed voltage measurement
d3aa: made it easy to switch between vddio2 and external voltage divider
emisar-d3aa: new model number, since this is a new product line
added initial code for emisar-d3aa torch
|
| | | | | |
|
| | |\ \ \
| |/ / /
|/| | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
FIXME: The d3aa's voltage calculator needs to be fixed after this merge.
* trunk:
use smooth steps in lockout mode, if enabled
fixed Tactical Mode's strobes when Momentary Mode not enabled
increased voltage precision from 0.025V to 0.02V (so 0 to 255 now goes from 0.00V to 5.10V)
fixed inaccurate comment (thanks to xikteny for spotting it)
Allow manually running GitHub actions workflows
Bugfix: Prevent switching channel modes when in tactical mode
Bugfix: Tactical mode has a dependency on momentary mode
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Based on [SammysHP's patch](https://github.com/ToyKeeper/anduril/pull/18),
but only for lockout mode, not tactical.
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
* pr52-SiteRelEnby-manual-actions:
Allow manually running GitHub actions workflows
|
| |/| | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
pr52-SiteRelEnby-manual-actions
* 'manual-actions' of github.com:SiteRelEnby/anduril:
Allow manually running GitHub actions workflows
|
| | | |/ /
| |/| |
| | | |
| | | | |
https://docs.github.com/en/actions/using-workflows/manually-running-a-workflow
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Allows user to disable Momentary Mode at compile time,
while keeping Tactical Mode.
* pr46-SiteRelEnby-bugfix-tacmode-without-momentary:
fixed Tactical Mode's strobes when Momentary Mode not enabled
Bugfix: Tactical mode has a dependency on momentary mode
|
| | | | | | |
|
| |/| | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
github.com:SiteRelEnby/anduril into pr46-SiteRelEnby-bugfix-tacmode-without-momentary
* 'bugfix-tacmode-without-momentary' of github.com:SiteRelEnby/anduril:
Bugfix: Tactical mode has a dependency on momentary mode
|
| | |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Use case 1: Updating a t85 light, where tactical mode is useful but
takes some squeezing, and momentary is less useful
Use case 2: Custom builds for people who don't like/want momentary mode
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Fixes [bug #40](https://github.com/ToyKeeper/anduril/issues/40)
Don't change channel during 3C in Tactical Mode.
* pr49-SiteRelEnby-tactical-mode-3c-fix:
Bugfix: Prevent switching channel modes when in tactical mode
|
| |/| | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
pr49-SiteRelEnby-tactical-mode-3c-fix
* 'tactical-mode-3c-fix' of github.com:SiteRelEnby/anduril:
Bugfix: Prevent switching channel modes when in tactical mode
|
| | |/ / /
| | | |
| | | |
| | | | |
Fixes issue https://github.com/ToyKeeper/anduril/issues/40
|
| | | | |
| | | |
| | | |
| | | | |
(so 0 to 255 now goes from 0.00V to 5.10V)
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
(also, fixed bug where a totally empty li-ion didn't get limited)
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
and not letting the magic smoke out of updi adapters any more (probably)
The alkaline detection might be a little too lenient though; it
could potentially fail to activate limits when the cell is completely
full or stronger than an average alkaline. One of my test cells
measured at 72 / 75, so if it was just a little stronger it'd pass...
but most alkalines I tried were in the 40 to 60 range and failed easily.
OTOH, if I make it easier to fail, it's likely to trip on normal li-ion
cells, and I don't want that.
So as a future enhancement idea, maybe it should have a smaller sag
threshold for AA and a larger threshold for li-ion. That would reduce
false negatives for AA, while still preventing false positives for li-ion.
|
| | | | |
| | | |
| | | |
| | | | |
(saving progress here so I can work on a different branch)
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- new ramp
- production style config defaults (simple mode, Hank config)
- candle tuning
- fixed way-too-fast thermal regulation
(might still be a bit fast, but it's a lot better)
|
| | | | | |
|
| | | |\ \
| |_|/ /
|/| | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
* trunk:
enabled eeprom read/write stabilization by default on recent MCUs, to prevent corrupt data
thefreeman-avr32dd20-devkit: enable boost bypass at boot, so AA/NiMH can boot
avr32dd20-devkit: use unimplemented "CH" pin as a boost bypass control
added "emisar-2ch-fet-joined" build, for D4S w/ lighted switch
documented FW3X swapped pins better
documented Wurkkos TS25/TS11/FC13 distinctions
build.sh: don't require DFPs, newer avr-libc doesn't need them
use BLIP_LEVEL instead of 0 for "blip"s
clarified which-hex-file.md a bit; make sure the model number matches
fw3x: reduced pulsing on low modes
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
to prevent corrupt data
This was enabled on more build targets before, but the *_ENABLE_PIN
definition names changed and the eeprom code didn't, so it was not
compiled in for a few months on some lights which probably needed it.
To fix that, it's now enabled by default on everything bigger than
attiny85, since it doesn't really hurt anything if it's enabled when
not needed.
|
| |/ / / |
|
| | |/
|/|
| |
| |
| |
| |
| | |
For 3V LEDs on a boost/buck dual fuel driver, this allows
routing power around the boost converter in li-ion mode,
to reduce resistance and increase maximum output.
The AA/NiMH mode is unaffected, and boosts as normal.
|
| | |
| |
| |
| | |
(it's an odd case with a 2 channel driver which only uses 1 set of LEDs)
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
This helps when using a regulator which doesn't like being turned off
and back on quickly.
|
| | | |
|
| | | |
|
| | |\
| |/
|/|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* trunk:
moved version string calculation to bin/version-string.sh
forgot one item in the ChangeLog
ChangeLog: added 2023-12-03 release notes, converted @modelname to &modelname
docs: expanded / reorganized info on Version Check formats
updated MODELS, bin/models.py, and hw/BRANDS...
fw3x: document how it ships with the wrong fuse values, and how to fix it
github CI: fetch history too, to allow detection of version tags
build-all: handle the case where "git describe" can't get any tags
run CI on all branches, not just on trunk
fetch tags on CI checkout, so 'git describe' can work
added docs/battery-rainbow.png from old repo, since it's still relevant
added bin/make-release.sh to generate a .zip file ready for release
build-all.sh: re-indented, started organizing code into functions
changed version number to use the latest release tag instead of build date
|
| | |
| |
| |
| |
| |
| | |
Also updated the format slightly, so this rev is: `2023-12-03+2#1`
+N for commits since tag
#1 for dirty
|
| | | |
|
| | |
| |
| |
| |
| | |
(because the @ was causing people to get tagged when their username
happened to be the same as a brand or model name)
|
| | | |
|