diff options
| author | Selene ToyKeeper | 2021-09-10 00:48:01 -0600 |
|---|---|---|
| committer | Selene ToyKeeper | 2021-09-10 00:48:01 -0600 |
| commit | b8b6214b7e9c3f2bb86f7379995fb64c73736d11 (patch) | |
| tree | 4f48df3de32f9ec90cf12decb4ffa46f6d9c4e02 /tk.h | |
| parent | added D4Sv2-tintramp-FET build, which uses a FET on one set of LEDs for turbo... (diff) | |
| download | anduril-b8b6214b7e9c3f2bb86f7379995fb64c73736d11.tar.gz anduril-b8b6214b7e9c3f2bb86f7379995fb64c73736d11.tar.bz2 anduril-b8b6214b7e9c3f2bb86f7379995fb64c73736d11.zip | |
fixed ancient bug which caused a weird up-spike in thermal regulation during 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.
Diffstat (limited to 'tk.h')
0 files changed, 0 insertions, 0 deletions