| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
instead of my janky forced phase-reset workaround
(gchart found the solution but couldn't reproduce the issue,
so I tried his method and confirmed it seems to be fixed)
|
| |
|
|
|
|
|
| |
reset to ~6 lm (level 50/150) after being off for 10 minutes
This sets the factory-reset default settings and affects Simple UI,
so it will likely need confirmation from Sofirn.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
made party strobe pulses much faster
Reduced max PWM TOP to 3072, because 2048 wasn't enough and 4096 was more than necessary.
Also, Ch1 lumens / 256 / ch2 lumens = 6, so 256 * 6 * 2 is the lowest value
which allows ch1 to start at half of ch2's power. I tried 1536 initially, but it made the
ramp visibly malformed at the channel boundary. However, 3072 seems about right.
Implemented a non-linear PWM_TOP ramp-down in level_calc,
to allow it to converge faster and reduce the number of levels with visible pulses.
Added an option to keep the regulator chips on between strobe pulses,
by keeping the LEDs at moon instead of turning completely off.
This allows the SP10 party strobe to use much shorter, more consistent pulses.
|
| |
|
|
| |
more until ch2 activates
|
| |
|
|
|
|
| |
(reduced PWM_TOP minimum timing window to 32 cpu cycles,
to allow TOP value of 64 to work better)
|
| |
|
|
|
|
|
| |
also fixed random ramp stuttering, by adding phase-reset register to hwdef
(though it still has a brief stutter sometimes while ramping down across the channel boundary,
at least it always seems to be smooth while going up now)
|
| |\ |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
(Off->9H option 1, 0=smooth, 1=toggle)
|
| | |
| |
| |
| |
| |
| | |
(is basically identical to D4Sv2-tintramp, but with the switch on a different pin,
and no button LED)
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
from ramp step 141 to 150
(0 to 100% power from 1 to 130, 101% to 200% from 131 to 150, and +DD FET from 141 to 150)
also calibrated candle mode a bit better
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Normal ramp from 0% to 100% power on levels 1 to 130,
then 101% to 200% power at levels 131 to 150
using both channels at maximum for turbo.
When either channel would go over 100%, the extra
spills over to the other channel.
|
| |\ \ |
|
| | |\| |
|
| | | |
| | |
| | |
| | |
| | | |
(old wording was confusing people)
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
(2021-09-10 r619.1.11)
The gradual_target var was getting clobbered and causing thermal regulation to stop
until the next thermal warning event, every time it reached a new ramp step.
So... save/restore it to prevent it from getting clobbered.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
(use the same value as LVP; easier to configure if it's in only one place)
|
| | | |
| | |
| | |
| | |
| | | |
(because it's kind of important to know which MCU each light uses,
and because this will be helpful later when the build system is rewritten)
|
| | | |
| | |
| | |
| | | |
the new 2C_STYLE defines
|
| | | | |
|
| |\| |
| |/
|/|
| |
| | |
(minus the change to version.h)
|
| | |
| |
| |
| | |
tweak party strobe & LVP level
|
| | |\
| |/
|/| |
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | |
| | | |
(which also changed the way tint ramping is implemented,
to make things generally cleaner and more flexible)
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
(apparently Hank liked the D4Sv2-tintramp demo/experiment so much that
he decided to use it in production for the K9.3... so it need its own
builds since it's a pretty different light even if the driver is almost identical)
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
by turning off one more of the recent extra features
(can turn it back on later if the build size goes down)
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
(can't test because I have no hardware, but it at least compiles)
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
initial turbo drop,
on 3-channel drivers like FW3A and ROT66
(as shown here: http://toykeeper.net/torches/fw3a/therm-2019-05-22.1.png )
What happened was... the FET would start to drop, but gradual adjustments noticed that
the Nx7135 channel needed to go from 0 to 255, so it would then slowly ramp that up,
and then afterward, the FET drop could finally continue... because the code didn't
jump straight from 0 to 255 like it was supposed to.
Simple, easy fix: Make channel 2 go up immediately just like channel 1 does. This makes
the thermal response several seconds faster than it was before, so it doesn't get as hot,
and is less likely to overshoot and bounce later.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
turbo modes
(it's weird, but Hank wants it)
also reworked gradual tint adjustment a bit, so some complex parts go in set_level() instead
(probably needs more testing)
|
| | | |
| | |
| | |
| | |
| | |
| | | |
(suggested by solrize)
(doesn't seem to reduce size of t85 builds though)
|
| | | |
| | |
| | |
| | |
| | |
| | | |
to make its thermal regulation smoother and generally increase tint ramp resolution in middle modes
(also, tried thermal regulation, and it works)
|
| | | | |
|
| | | |
| | |
| | |
| | | |
thermal regulation)
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
and (maybe) thermal regulation (untested)
(also broke BLF LT1 in the process; need to fix that now)
Rewrote how tint ramping works, so it provides a virtual "PWM1_LVL" for other code to use,
and it translates that internally into actual hardware controls. This should, in theory,
allow smooth thermal regulation (gradual_tick) to work on tint-ramp lights.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
(initial rev, will almost certainly need changes later)
|
| | | | |
|
| | | | |
|
| |/ / |
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
+ runtime option for smooth ramp speed
+ runtime option for whether hold-from-off should ramp up or stay at the floor
+ runtime option to select turbo style / 2C style in Advanced UI
+ same thing, but for Simple UI
* sped up the auto-reverse timing window; it was too slow
|
| | | | |
|