Can someone explain the difference between 2 fast clicks or long press from off?
(green lines from off in the UI diagram)
They both point to the same spot in the ramp box. And what are the dotted line separators the box?
I understand it this way:
Dotted Lines in the Ramp:
Bottom and top line are the Moon/Low Level and the top off the ramp=ceiling. You can reach the top for ceiling by double click. (a second double click brings you to turbo)
Middle line is the maximum from the 7135.
Two fast clicks brings you to the ceiling (green solid)
The click, release, hold (green dashed) ramps downward from TURBO Edit: ceiling
But I should probably shut up, because I haven’t Andúril running on a lamp.
One suggestion for the thermal rampdown: Can we add a cap to how far it ramps down?
One problem I’ve notice with my Emisar D4 is that it starts 4300 lumens, but within a minute it ramps down to about 50 lumens, which is way too far. Then it takes forever to ramp itself back up again.
It would be nice if it stopped ramping down at 500 lumens instead of keeping going. Maybe have the rampdown stop when the light reaches 25-30% of max power no matter what the temperature sensor says.
Can someone explain the difference between 2 fast clicks or long press from off?
(green lines from off in the UI diagram)
They both point to the same spot in the ramp box. And what are the dotted line separators the box?
I understand it this way:
Dotted Lines in the Ramp:
Bottom and top line are the Moon/Low Level and the top off the ramp=ceiling. You can reach the top for ceiling by double click. (a second double click brings you to turbo)
Middle line is the maximum from the 7135.
Two fast clicks brings you to the ceiling (green solid)
The click, release, hold (green dashed) ramps downward from TURBO
But I should probably shut up, because I haven’t Andúril running on a lamp.
So the the top off the ramp (ceiling) is not Turbo?
Or is the ceiling programmable and double click goes to the level you pre-set as the ceiling?
Like this:
Single click = memory pre-set (or max 7135 level if memory off) remains steady
Can someone explain the difference between 2 fast clicks or long press from off?
(green lines from off in the UI diagram)
They both point to the same spot in the ramp box. And what are the dotted line separators the box?
…
Ramping is auto-ramp? (you don’t have to hold in the button) click to stop.
It sounds like you got it in a later post, but I’ll try to answer all the questions at once.
The bottom dotted line in the ramp is the floor level. The top dotted line is the ceiling level. The middle dotted line is the 1×7135 level. Floor and ceiling are configurable.
Click from off: Memorized level. Defaults to 1×7135 after disconnecting power.
Hold from off: Floor level, then ramp up until button is released.
Double click from off: Ceiling level.
Click, release, hold from off: Ceiling level, then ramp down until button is released.
Ramping only happens when the button is held. If it ramps while not holding the button, something went wrong with the button connection, and the light should probably be loosened/tightened to reset the contact. I have seen this happen on occasion if the light gets knocked sideways and moves the position of the inner tube far enough to contact ground.
gravelmonkey wrote:
does the gap under the clip (towards the tail) allow the light to “flop” about when it’s clipped to a pocket?
Depends on the pocket.
gravelmonkeye wrote:
I would love a tiny red (or amber) LED on the MPCB in lieu of a lighted tailcap.
There isn’t currently a free pin to drive an indicator LED, since the pin it would normally use is allocated for the third main-emitter power channel instead. There is also no pad for a fourth LED on the MCPCB, nor room to route another wire there.
Firelight2 wrote:
Can we add a cap to how far it ramps down?
One problem I’ve notice with my Emisar D4 is that it starts 4300 lumens, but within a minute it ramps down to about 50 lumens, which is way too far.
There is a compile-time option in Anduril for this. The default is set to the 1×7135 level or ~150 lm, which is about 3X as high as what the D4 firmware used. The regulation algorithm is also completely different.
#define MIN_THERM_STEPDOWN MAX_1x7135 // lowest value it'll step down to
chadvone wrote:
Does memory remember everything????
I think it should remember what ever you were in last.
It remembers almost everything, but when it’s off it is mostly stateless… ish. Like, if you were in candle mode when you shut it off, a single click will not return to candle mode. It’ll go to the regular ramp instead. But if you were in muggle mode when turning it off, it’ll return to muggle mode on the next click.
There are effectively four different “off” states:
Normal operating mode.
Soft lockout mode.
Momentary mode.
Muggle mode.
Most settings are remembered after a battery change. However, a battery change resets a few things:
Reset to normal operating mode, unless muggle mode was active. (cancels lockout and momentary)
A tiny locator led can be always on, it then does not need a pin, just a 10K resistor on the driver, and pads on the MCPCB. You can not use it to signal things then, and it can only be switched off with a mechanical lockout. The tiny led could also be at the tail (but there’s no hole there for the light coming out, it would be there but nobody ever sees it ).
The optic nerve pin might also be usable to drive an indicator LED, if the sensing function was sacrificed. I haven’t checked the attiny docs to see if that pin has the relevant functions, but it probably does. And the optical programming stuff hasn’t been written yet.
I’ve kinda been waiting on the second prototype to arrive since I’ll have to mod the light to do any optical programming development on it, and it won’t be usable for non-development purposes any more.
Oh, that one is not an error. The list has the correct number (1) for kahvitahra. To check this, look in the right column of the list, which shows requests per person).
kahvitahra should enter and publish how many lights he wants
. In Interest List, Post # 4 Page 1, it only has one “1” . 2nd cancelled.
.
Oh, that one is not an error. The list has the correct number (1) for kahvitahra. To check this, look in the right column of the list, which shows requests per person).
OK, TK does it remember the Last Blinky and the Last Strobe ??
What are the default Blinky and Strobe modes ? After a power cycle?
It remembers the last-used mode in the strobe group. However, the blinkies always start at battcheck.
This can be partially inferred by the arrows from “off” in the diagram, since one points directly to battcheck and the other points only to the strobe group.
OK, TK does it remember the Last Blinky and the Last Strobe ??
What are the default Blinky and Strobe modes ? After a power cycle?
It remembers the last-used mode in the strobe group. However, the blinkies always start at battcheck.
This can be partially inferred by the arrows from “off” in the diagram, since one points directly to battcheck and the other points only to the strobe group.
I understand people’s tastes are personal, but I really like the current design compared to the original.
Possibly a stupid question, but does the gap under the clip (towards the tail) allow the light to “flop” about when it’s clipped to a pocket?
I know it’s not realistic, but I would love a tiny red (or amber) LED on the MPCB in lieu of a lighted tailcap.
There is a thread for drilled optics that can fit 3x tritium in your color choice that can serve this purpose. It’s quite a bit more expensive than your suggestion but it also glows with no drain on the battery.
I saw recently that Oveready is using optical programming on their Boss lights. I wonder if that stemmed from discussions on BLF or if they have berm doing it a while. They also use the same optical sensor as a safety feature against their light turning on in your pocket somehow and cooking your leg.
I saw recently that Oveready is using optical programming on their Boss lights. I wonder if that stemmed from discussions on BLF or if they have berm doing it a while. They also use the same optical sensor as a safety feature against their light turning on in your pocket somehow and cooking your leg.
http://lux-rc.com makes their drop ins and they have been doing optical programming for a while, along with some other very advanced features.
I saw recently that Oveready is using optical programming on their Boss lights. I wonder if that stemmed from discussions on BLF or if they have berm doing it a while. They also use the same optical sensor as a safety feature against their light turning on in your pocket somehow and cooking your leg.
http://lux-rc.com makes their drop ins and they have been doing optical programming for a while, along with some other very advanced features.
Interesting, thanks for pointing that out. I guess I assumed when I saw it discussed here that it hadn’t been done yet.
I saw recently that Oveready is using optical programming on their Boss lights. I wonder if that stemmed from discussions on BLF or if they have berm doing it a while. They also use the same optical sensor as a safety feature against their light turning on in your pocket somehow and cooking your leg.
The Lux-RC people did it first, but I didn’t know they existed until I made my proof of concept last year. When I told people what I did, they asked me if it was like Lux-RC, and I was like “lux who?”
The differences in my implementation are:
No optical sensor required.
No special MCPCB required.
Works with reflector-based lights too, not just TIR.
Can’t sense anything while the main emitters are on.
Can someone explain the difference between 2 fast clicks or long press from off?
(green lines from off in the UI diagram)
They both point to the same spot in the ramp box. And what are the dotted line separators the box?
Please put me down for 1.
The latest iteration looks amazing!
Thier ain’t no bones in a hot dog. F. York
I understand people’s tastes are personal, but I really like the current design compared to the original.
Possibly a stupid question, but does the gap under the clip (towards the tail) allow the light to “flop” about when it’s clipped to a pocket?
I know it’s not realistic, but I would love a tiny red (or amber) LED on the MPCB in lieu of a lighted tailcap.
I understand it this way:
Dotted Lines in the Ramp:
Bottom and top line are the Moon/Low Level and the top off the ramp=ceiling. You can reach the top for ceiling by double click. (a second double click brings you to turbo)
Middle line is the maximum from the 7135.
Two fast clicks brings you to the ceiling (green solid)
The click, release, hold (green dashed) ramps downward from
TURBOEdit: ceilingBut I should probably shut up, because I haven’t Andúril running on a lamp.
One suggestion for the thermal rampdown: Can we add a cap to how far it ramps down?
One problem I’ve notice with my Emisar D4 is that it starts 4300 lumens, but within a minute it ramps down to about 50 lumens, which is way too far. Then it takes forever to ramp itself back up again.
It would be nice if it stopped ramping down at 500 lumens instead of keeping going. Maybe have the rampdown stop when the light reaches 25-30% of max power no matter what the temperature sensor says.
So the the top off the ramp (ceiling) is not Turbo?
Or is the ceiling programmable and double click goes to the level you pre-set as the ceiling?
Like this:
Ramping is auto-ramp? (you don’t have to hold in the button) click to stop.
Beam0 I believe it ramps until you release button.
Now I have a question.
Does memory remember everything????I think it should remember what ever you were in last.
I’d be interested in one as well!
You are number No. #1109 on: Interest list , Post # 4 , Page 1 “:http://budgetlightforum.com/comment/1120496#comment-1120496
.
+1, I put it in the number #1176 on: Interest list updated by pepinfaxera, View page 71, ,
http://budgetlightforum.com/comment/1255477#comment-1255477 ,
For a total of 2 lights .
How many lanterns do you want in total? … x … units? .
.
Sorry for my bad English
(google translator) , (https://www.deepl.com/translator)
Updated list : … Post moved to Page 111 . http://budgetlightforum.com/comment/1329701#comment-1329701
-
-
Sorry for my bad English
(google translator) , (https://www.deepl.com/translator)
It sounds like you got it in a later post, but I’ll try to answer all the questions at once.
The bottom dotted line in the ramp is the floor level. The top dotted line is the ceiling level. The middle dotted line is the 1×7135 level. Floor and ceiling are configurable.
Ramping only happens when the button is held. If it ramps while not holding the button, something went wrong with the button connection, and the light should probably be loosened/tightened to reset the contact. I have seen this happen on occasion if the light gets knocked sideways and moves the position of the inner tube far enough to contact ground.
Depends on the pocket.
There isn’t currently a free pin to drive an indicator LED, since the pin it would normally use is allocated for the third main-emitter power channel instead. There is also no pad for a fourth LED on the MCPCB, nor room to route another wire there.
There is a compile-time option in Anduril for this. The default is set to the 1×7135 level or ~150 lm, which is about 3X as high as what the D4 firmware used. The regulation algorithm is also completely different.
It remembers almost everything, but when it’s off it is mostly stateless… ish. Like, if you were in candle mode when you shut it off, a single click will not return to candle mode. It’ll go to the regular ramp instead. But if you were in muggle mode when turning it off, it’ll return to muggle mode on the next click.
There are effectively four different “off” states:
Most settings are remembered after a battery change. However, a battery change resets a few things:
A tiny locator led can be always on, it then does not need a pin, just a 10K resistor on the driver, and pads on the MCPCB. You can not use it to signal things then, and it can only be switched off with a mechanical lockout. The tiny led could also be at the tail (but there’s no hole there for the light coming out, it would be there but nobody ever sees it
).
link to djozz tests
The optic nerve pin might also be usable to drive an indicator LED, if the sensing function was sacrificed. I haven’t checked the attiny docs to see if that pin has the relevant functions, but it probably does. And the optical programming stuff hasn’t been written yet.
I’ve kinda been waiting on the second prototype to arrive since I’ll have to mod the light to do any optical programming development on it, and it won’t be usable for non-development purposes any more.
Please put me down for 1!
Please, put me down for one.
kahvitahra should enter and publish how many lights he wants.
In Interest List, Post # 4 Page 1, it only has one “1”.2nd cancelled..
Sorry for my bad English
(google translator) , (https://www.deepl.com/translator)
The right column, not the left column.
Three posts: Two requests, one cancellation. Total of 1 light. Currently #809 on the list.
Because of the accidental second request, I used kahvitahra as a test case for the code which handles cancellations.
.
.
I apologize
My mistake
Now I have to edit Post 2128 and 2129 Page 71.
Sorry.
.
Sorry for my bad English
(google translator) , (https://www.deepl.com/translator)
OK, TK does it remember the Last Blinky and the Last Strobe ??
What are the default Blinky and Strobe modes ? After a power cycle?
Sounds great.
It remembers the last-used mode in the strobe group. However, the blinkies always start at battcheck.
This can be partially inferred by the arrows from “off” in the diagram, since one points directly to battcheck and the other points only to the strobe group.
Great. i love it
please add 2 more for me for a total of 4. thanks
I’m liking this flashlight even more. I’m interested in getting a second one (my first one is #983).
There is a thread for drilled optics that can fit 3x tritium in your color choice that can serve this purpose. It’s quite a bit more expensive than your suggestion but it also glows with no drain on the battery.
I saw recently that Oveready is using optical programming on their Boss lights. I wonder if that stemmed from discussions on BLF or if they have berm doing it a while. They also use the same optical sensor as a safety feature against their light turning on in your pocket somehow and cooking your leg.
http://lux-rc.com makes their drop ins and they have been doing optical programming for a while, along with some other very advanced features.
Interesting, thanks for pointing that out. I guess I assumed when I saw it discussed here that it hadn’t been done yet.
The Lux-RC people did it first, but I didn’t know they existed until I made my proof of concept last year. When I told people what I did, they asked me if it was like Lux-RC, and I was like “lux who?”
The differences in my implementation are:
Interested. Please put me down for one.
Interest list updated.
- TK
FW3A thread – contact Neal on BLF or email for FW3A questions and support
Pages