half-watt
Flashlight Enthusiast
Let's start this Thread off really simple.
Standard terminology has the 'P' model as having a Primary output setting, a Secondary output setting, a Maximum output setting, and a Minimum output setting.
These are NOT cast in concrete as to how much light they put out as the user may program each of them for different output.
However, the NAMING of each output setting might be a little misleading. How so?
Well, think of them *NOT* as Primary, Secondary, Max, and Min, but rather just think of them conceptually as First, Second, Third, and Fourth settings.
For my purposes, i wanted the lowest light output setting that i would program to be the first one that is activated when the light is turned on, but i wanted it to also put out, relatively speaking to MIN, a LOT of light. So, i programmed it to turn on at the Mfr. claimed 15 Lumen level.
Next, i wanted the 2click operation to increase the light output. So, my "secondary" or second mode, is brighter. In my case, the Mfr. claimed 30 Lumens.
Next, i wanted the 3click operation (normally bringing up the Factory Default MINIMUM 0.3 Lumen output) to bring up an even brighter output level. So, mine is programmed to output the Mfr. claimed 60 Lumen output level.
Finally, i left the MAXIMUM (i think of it as the FOURTH output level) level alone and it outputs a Mfr. claimed 120 Lumen output via either the LONG PRESS (no release) MOMENTARY mode, or the single CLICK-PRESS constant, latched MAX output mode.
So, in my case here's how i could progress through all four modes from dimmest to brighest that i've programmed into the four memorized levels: [Note: keep in mind that levels can be skipped and engaged in different orders which are NOT necessarily sequential; this is NO different from how the light functions with the factory default output levels. the programming doesn't affect how the light is controlled, just the output levels produced in response to the control sequences of clicks and/or presses.]
1click = turn light on to 15 Lumen (my lowest personally programmed level)
2clicks = secondary level (30Lumen in my case)
3clicks = the next brightest level (know as the Factory Default MINIMUM) which is, in my case, currently 60Lumen
1click-press (or press and hold) = Maximum
going back down...
2clicks returns me to 15lumen (primary) or 30lumen (secondary) mode - whichever was last activated in whatever sequence of mode changing i happen to be doing.
...and...
2clicks, of course, still toggles back and forth between Primary (15lumen for me) and Secondary (30lumen in my case) modes, just like the Factory Defaults function, but, of course, with different output levels.
So, in a nutshell, if someone's needs are different than the fine Factory Default chosen output levels, DON'T let the standard terminology confuse how the light can be programmed. The setting termed MINIMUM does NOT have to be used for the lowest programmed output level (in my case its the second brightest as i've stated above).
Just some thoughts of mine put on display for all to see that there is a madness to my method!! YMMV.
Standard terminology has the 'P' model as having a Primary output setting, a Secondary output setting, a Maximum output setting, and a Minimum output setting.
These are NOT cast in concrete as to how much light they put out as the user may program each of them for different output.
However, the NAMING of each output setting might be a little misleading. How so?
Well, think of them *NOT* as Primary, Secondary, Max, and Min, but rather just think of them conceptually as First, Second, Third, and Fourth settings.
For my purposes, i wanted the lowest light output setting that i would program to be the first one that is activated when the light is turned on, but i wanted it to also put out, relatively speaking to MIN, a LOT of light. So, i programmed it to turn on at the Mfr. claimed 15 Lumen level.
Next, i wanted the 2click operation to increase the light output. So, my "secondary" or second mode, is brighter. In my case, the Mfr. claimed 30 Lumens.
Next, i wanted the 3click operation (normally bringing up the Factory Default MINIMUM 0.3 Lumen output) to bring up an even brighter output level. So, mine is programmed to output the Mfr. claimed 60 Lumen output level.
Finally, i left the MAXIMUM (i think of it as the FOURTH output level) level alone and it outputs a Mfr. claimed 120 Lumen output via either the LONG PRESS (no release) MOMENTARY mode, or the single CLICK-PRESS constant, latched MAX output mode.
So, in my case here's how i could progress through all four modes from dimmest to brighest that i've programmed into the four memorized levels: [Note: keep in mind that levels can be skipped and engaged in different orders which are NOT necessarily sequential; this is NO different from how the light functions with the factory default output levels. the programming doesn't affect how the light is controlled, just the output levels produced in response to the control sequences of clicks and/or presses.]
1click = turn light on to 15 Lumen (my lowest personally programmed level)
2clicks = secondary level (30Lumen in my case)
3clicks = the next brightest level (know as the Factory Default MINIMUM) which is, in my case, currently 60Lumen
1click-press (or press and hold) = Maximum
going back down...
2clicks returns me to 15lumen (primary) or 30lumen (secondary) mode - whichever was last activated in whatever sequence of mode changing i happen to be doing.
...and...
2clicks, of course, still toggles back and forth between Primary (15lumen for me) and Secondary (30lumen in my case) modes, just like the Factory Defaults function, but, of course, with different output levels.
So, in a nutshell, if someone's needs are different than the fine Factory Default chosen output levels, DON'T let the standard terminology confuse how the light can be programmed. The setting termed MINIMUM does NOT have to be used for the lowest programmed output level (in my case its the second brightest as i've stated above).
Just some thoughts of mine put on display for all to see that there is a madness to my method!! YMMV.
Last edited: