I updated my TS10 to the latest firmware and what a difference! I’m measuring 0.01lm now.
The max regulated level appears to have changed from level 65 to something else. Does anyone know what the max regulated level is for this updated firmware?
I updated my TS10 to the latest firmware and what a difference! I’m measuring 0.01lm now.
The max regulated level appears to have changed from level 65 to something else. Does anyone know what the max regulated level is for this updated firmware?
SammysHP made this ramp and I copied it. Looks like 90 is the max regulated.
https://bazaar.launchpad.net/~gabe/flashlight-firmware/anduril2/view/head:/ToyKeeper/spaghetti-monster/anduril/cfg-wurkkos-ts10.h
Any chance Wurkkos update their firmware to this latest?
when is red back in stock on wurkkos website?
Still can’t wait for the copper and brass version!
PMC just reply my “The red body would be available in August, but the specific time cannot be determined.”
my understanding is wurkkos tried the new hex and found another bug, so they’re going to use the original settings on the third batch too. (i think the third batch is already gone too.)
and they plan to “mass produce” the flashing pad for us…(because we’re all advanced programmers :P)
What was the new bug?
What was the new bug?
i am not sure, i just took the information from public facebook posts from a week ago.
Hi Wurkkos fans and friend, The aux bug has been solved by latest Anduril program. But we also found the new bug again on latest Anduril program. In the...
Wurkkos wrote there:
We make turbo mode from 150/150 ceiling change to perhaps 130/150. It is running perfect.
But when we performed the ‘Set Ceiling Level’ step and manually click 150 times, the lumens of the penultimate level will be chaos (as you saw in this video).
Also the temperature limit of the flashlight will also be affected.
We can obviously feel the body has become hotter than before.
They simply don’t know how Anduril works. In the ceiling config 1 click means level 150, 2 means 149, 11 means 140 and so on. There is no range check and when you set ceiling below floor, strange things will happen. It’s not a bug (although a range check on the user input might be a good idea, although it will increase the code size significantly).
“We make turbo mode from 150/150 ceiling change to perhaps 130/150. It is running perfect.
But when we performed the ‘Set Ceiling Level’ step and manually click 150 times, the lumens of the penultimate level will be chaos (as you saw in this video).
Also the temperature limit of the flashlight will also be affected.
We can obviously feel the body has become hotter than before.”
I think they misunderstand how to set the ceiling. He thinks you have to click 150 times to set a ceiling of 150. And when he does this there is “chaos”
@Wurkkos, please note that the ceiling becomes [151 - n] where n is the number of clicks.
1 click sets ceiling to level 150 (151-1 = 150)
21 clicks sets ceiling to level 130 (151-21 = 130)
55 clicks sets ceiling to level 96 (151-55 = 96)
Some of the Anduril diagrams which are circulating do not explain this clearly enough.
If you make 150 clicks you are telling it to set ceiling to level 1. I never tried this but I guess it could cause strange behaviour.
It turns out that there’s a big difference in wording between the 2021 version Wurkkos has versus the 2022 April version!
As a newbie to all this, the 2022 version makes a BIG difference in trying to make the UI do what you want it to do.
Question about battery type
is the Wurkkos 900mah 14500 Battery an ICR, IMR, or INR chemistry?
Difficult to know, but recent cells are usually INR/NMC or NCA. ICR is old stuff.
Difficult to know, but recent cells are usually INR/NMC or NCA. ICR is old stuff.
thanks for your guess
I ask because of the tendency to overdischarge when using High Bright Aux/button.
Although I have reflashed to add LVP… not everyone has
Im under the impression that recharging an unprotected IMR/INR that dropped below 2.4v is less risky than recharging an overdischarged unprotected ICR
Got my 2nd TS10 today. Black, orange aux 4000k.
Not buggy like my first red, red aux 4000k.
Booted in Anduril 2. Not Blinky like the first batch (the red one).
Like it a lot. I can live with the first batch software problems.
The first batch of TS10 I have is really wonky. Works fine,settles down. and then an hour later it doesn’t respond correctly to clicks.
Very weird.
My second TS10 is working fine.
They simply don’t know how Anduril works. In the ceiling config 1 click means level 150, 2 means 149, 11 means 140 and so on. There is no range check and when you set ceiling below floor, strange things will happen. It’s not a bug (although a range check on the user input might be a good idea, although it will increase the code size significantly).
Sorry my man.
Maybe I have some mistakes in wording.
I will ask Wurkkos tester to show me the complete test process.
Then I will repeat once in this post.
I think they misunderstand how to set the ceiling. He thinks you have to click 150 times to set a ceiling of 150. And when he does this there is “chaos”
@Wurkkos, please note that the ceiling becomes [151 - n] where n is the number of clicks.
1 click sets ceiling to level 150 (151-1 = 150)
21 clicks sets ceiling to level 130 (151-21 = 130)
55 clicks sets ceiling to level 96 (151-55 = 96)Some of the Anduril diagrams which are circulating do not explain this clearly enough.
If you make 150 clicks you are telling it to set ceiling to level 1. I never tried this but I guess it could cause strange behaviour.
At that time, the feedback I received was indeed 150C to release the ceiling limit of 130/150.
(PS: I doubt they have set both the ceiling and floor to 150C.)
Let me ask our tester for the complete answer now.
SammysHP:I’ve played a bit with dynamic PWM and got a really low low with usable lower steps. I’ve limited the PWM top to 2048 as higher values didn’t make much difference, but reduced the frequency unnecessarily. I had some trouble with visible steps from dynamic underclocking. Also it seems like the 7135 drops out of regulation at low levels because the pulse got too short. Will check next days with my oscilloscope and share the config file afterwards.
Well, just what I had expected.
I used this ramp:
level_calc.py 7.01 2 150 7135 1 0.5 130 FET 1 10 1200 —pwm dyn:64:2048:255First, the lowest level can be really low. I mean, ZebraLight low. Problem: It’s all in the undefined behavior region of the 7135 because the pulse length is just too short.
Here is an example ramping through levels 1 to ~45:
Level 2 is darker than level 1 because the frequency is doubled (dynamic underclocking, quarter speed below 2). There is another jump from level 4 to 5, again dynamic underclocking (half speed below 5). Then it starts increasing, but in an undefined ramp shape. At level 45 the 7135 starts turning fully on (maybe a bit earlier because my light sensor is too slow).
What’s next? I might try to start at level 16 where the slope changes. That might be the point where the error of my light sensor is most influencing. Or it’s just the non-linearity of the 7135. From there I might add one or two “special” levels with ultra low moonlight and from level three upwards it will be lot brighter, but more reliable. Not sure what to do with dynamic underclocking…
Anyone with an idea how this could be set up in a nice way? ToyKeeper, gchart, thefreeman?
What do you use as a light sensor?