What should the next Foursevens QK16L UI look like?

8 posts / 0 new
Last post
Got Lumens
Got Lumens's picture
Offline
Last seen: 12 hours 51 min ago
Joined: 01/18/2012 - 23:18
Posts: 75
Location: Champlain Valley
What should the next Foursevens QK16L UI look like?
Option #1 Just change Medium(~100lm) to a lower ~40lm setting(Jason's Preference)
0% (0 votes)
Option #2 Add a fourth mode ~25lm between Medium(100lm) and Low(~1lm) {Might not be possible with limited driver memory}
33% (2 votes)
Option #1A Lower Medium(~100lm) to ~40lm and Lower High(400lm) to ~350lm for better mode spacing
67% (4 votes)
Total votes: 6

Neutrālisflashaholic

Edited by: Got Lumens on 08/27/2019 - 19:47
Got Lumens
Got Lumens's picture
Offline
Last seen: 12 hours 51 min ago
Joined: 01/18/2012 - 23:18
Posts: 75
Location: Champlain Valley

Hi Fousevens Fam,

I've heard your feedback on the Quark UI. Our first production run on QK16L lights sold out on Kickstarter and we are about to begin the next batch, so I may have an opportunity to revise the UI to make it more nerd friendly. A term of endearment of course!

First, let's acknowledge that no one ever agrees on UI and the ONLY solution to make everyone happy is fully programmable. That's not an option at this time. So, the new Fourseven's UI (in general) is intended to be as simple as possible while capturing the preference of a majority of flashlight users...not just enthusiasts I would also point out that those two goals are in conflict, and the final solution must strike a middle ground. Given all that:

Should the next Quark UI stay the same but lower the medium output to 40 lumens, or should a 4 mode UI be implemented? My main hesitation with adding a 4 mode is the need to add two additional configurations, bringing the total from 6-8. 6 is easy enough to memorize long term. 8 configs and you better not lose your user manual. I'm also not sure there is enough memory left on the chip to add two more configurations.

Notes on the current UI spacing:

  1. High mode is set to 60% of Max/Burst (100%) output because this is roughly "one step" in brightness. Burst is a battery conservation measure because the change in perceived brightness is not very drastic, but the extension of battery life is.
  2. Medium mode is set to 1/4 the output of High mode because a 4x change in output is equivalent to doubling the perceived brightness. This is a nice spacing (seemed good on paper) but I agree, a resulting 100 lumens is a little bright...especially for us flashlight nerds. I don't think civilians will care.


My personal inclination (proposed UI #1) is to keep the UI the same, but drop medium mode to 40 lumens. This equates to a 10x change in output between medium and high instead of 4x. This is basically the same as the current Mini/Turbo MKIII settings and no one has taken issue with that yet

Existing UI

  • Config. 1: High - (Burst)
  • Config. 2: Max - Strobe
  • Config. 3: Medium - High - (Burst)
  • Config. 4: Low - Medium - High - (Burst)
  • Config. 5: High - Medium - Low - (Burst)
  • Config. 6: Low - Med - High - Strobe - SOS - Beacon - (Burst)
  • Output Max/Burst: 700 lumens (100%)
  • Output High: 400 lumens (60%)
  • Output Medium: 100 lumens (15%)
  • Output Low: 1 lumen


Proposed UI #1 (just change medium to lower output - my personal preference)

  • Config. 1: High - (Burst)
  • Config. 2: Max - Strobe
  • Config. 3: Medium - High - (Burst)
  • Config. 4: Low - Medium - High - (Burst)
  • Config. 5: High - Medium - Low - (Burst)
  • Config. 6: Low - Med - High - Strobe - SOS - Beacon - (Burst)
  • Output Max/Burst: 700 lumens (100%)
  • Output High: 400 lumens (60%)
  • Output Medium: 40 lumens (6%)
  • Output Low: 1 lumen


Proposed UI #2 (add a 4 mode option where the difference between low and medium is also 4x - may not be possible due to memory constraints - seems overly complicated - I get dizzy just looking at the options)

  • Config. 1: High - (Burst)
  • Config. 2: Max - Strobe
  • Config. 3: Medium - High - (Burst)
  • Config. 4: Low - Medium - High - (Burst)
  • Config. 5: High - Medium - Low - (Burst)
  • Config. 6: Moon - Low - Medium - High - (Burst)
  • Config. 7: High - Medium - Low - Moon (Burst)
  • Config. 8: Low - Med - High - Strobe - SOS - Beacon - (Burst)
  • Output Max/Burst: 700 lumens (100%)
  • Output High: 400 lumens (60%)
  • Output Medium: 100 lumens (15%)
  • Output Low: 25 lumens (4%)
  • Output Moonlight: 1 lumen

 

Cheers
Jason

 

PS Please cast your vote for the GAW here.

Neutrālisflashaholic

MascaratumB
MascaratumB's picture
Offline
Last seen: 1 hour 53 min ago
Joined: 10/29/2016 - 12:12
Posts: 4011
Location: Portugal

Being interested in getting one of these lights (that I “had to miss” from the KS project), and being an “enthusiast”, of course my preferred UI would be the #2, always having the possibility to enter the Lowest mode first and “double clicking” for Burst.

But the mode spacing proposed in #1 that would have 1 – 40 – 400 – (700), is not completely out or order to me.

HOWEVER, if this suggestion prevails, wouldn’t it be a good option to lower the “High” mode a little bit so that it didn’t get that bigger leap (from 40 to 400)?! It is just a suggestion, as I also think that jumping from a lower High to a 700lumens Burst mode would be felt with more impact than from a higher High (400 lumens).

Thanks for the openness to our suggestions Wink

[REVIEWS] AMUTORCH: S3 / S3 vs 219c / AM30 / AX1 / VG10 /// SOFIRN: SF14 + SP10A / SP32A / SP10B /// NITEFOX: UT20 / ES10K / K3 /// ODEPRO: KL52 / B108 /// ACEBEAM: H20 / TK16 /// BLITZWOLF: BW-ET1 /// DQG: AA Slim Ti /// HC-LIGHTS: SS AAA /// XTAR: PB2 Charger /// OLIGHT: M2R Warrior /// WUBEN: TO10R / E05 / T70 / E10 /// ON THE ROAD: M1 / i3 / M3 Pro /// ROVYVON: A2 + A5R / E300S / A8 /// KLARUS: XT1C /// LUMINTOP: Tool AA V2.0 + Tool 25 /// LIVARNOLUX: 314791 /// SKILHUNT: M150

Tricks: 1 / 2 / 3 / 4 / 5 / 6 / 7 / 8 /// TIR Lenses: 1 / 2 /// Others: Biscotti 3 + 1*7135 / Triple TIR w/ XP-G2 ///// My Collection ///// My Review's Blog (PT)

GIVEAWAY: 1

Got Lumens
Got Lumens's picture
Offline
Last seen: 12 hours 51 min ago
Joined: 01/18/2012 - 23:18
Posts: 75
Location: Champlain Valley

MascaratumB wrote:
Being interested in getting one of these lights (that I "had to miss" from the KS project), and being an "enthusiast", of course my preferred UI would be the *#2*, always having the possibility to enter the Lowest mode first and "double clicking" for Burst. But the mode spacing proposed in #1 that would have 1 - 40 - 400 - (700), is not completely out or order to me. HOWEVER, if this suggestion prevails, wouldn't it be a good option to *lower the "High" mode* a little bit so that it didn't get that bigger leap (from 40 to 400)?! It is just a suggestion, as I also think that jumping from a +lower High+ to a 700lumens Burst mode would be felt with more impact +than from a higher High+ (400 lumens). Thanks for the openness to our suggestions Wink
I too suggested lowering the High and Medium using option 1. I think the spacing between burst and High could be a tad bit more.

Neutrālisflashaholic

MascaratumB
MascaratumB's picture
Offline
Last seen: 1 hour 53 min ago
Joined: 10/29/2016 - 12:12
Posts: 4011
Location: Portugal

Got Lumens wrote:
I too suggested lowering the High and Medium using option 1. I think the spacing between burst and High could be a tad bit more.

Yup, that is it, lowering medium and high would be a good compromise between the existing UI and the new UI without having to mess with driver memory to introduce more modes!! Low would still be low and Burst would still 700, but the in-between would be more balanced Wink

If this becomes an option, maybe you can add it to the voting Poll so we can vote according to that “new” option Wink

[REVIEWS] AMUTORCH: S3 / S3 vs 219c / AM30 / AX1 / VG10 /// SOFIRN: SF14 + SP10A / SP32A / SP10B /// NITEFOX: UT20 / ES10K / K3 /// ODEPRO: KL52 / B108 /// ACEBEAM: H20 / TK16 /// BLITZWOLF: BW-ET1 /// DQG: AA Slim Ti /// HC-LIGHTS: SS AAA /// XTAR: PB2 Charger /// OLIGHT: M2R Warrior /// WUBEN: TO10R / E05 / T70 / E10 /// ON THE ROAD: M1 / i3 / M3 Pro /// ROVYVON: A2 + A5R / E300S / A8 /// KLARUS: XT1C /// LUMINTOP: Tool AA V2.0 + Tool 25 /// LIVARNOLUX: 314791 /// SKILHUNT: M150

Tricks: 1 / 2 / 3 / 4 / 5 / 6 / 7 / 8 /// TIR Lenses: 1 / 2 /// Others: Biscotti 3 + 1*7135 / Triple TIR w/ XP-G2 ///// My Collection ///// My Review's Blog (PT)

GIVEAWAY: 1

Got Lumens
Got Lumens's picture
Offline
Last seen: 12 hours 51 min ago
Joined: 01/18/2012 - 23:18
Posts: 75
Location: Champlain Valley

I just changed the poll.
Everyone please revote.

Your previous votes were nullified. 

Neutrālisflashaholic

MascaratumB
MascaratumB's picture
Offline
Last seen: 1 hour 53 min ago
Joined: 10/29/2016 - 12:12
Posts: 4011
Location: Portugal

Got Lumens wrote:

I just changed the poll.
Everyone please revote.


Your previous votes were nullified. 


Thank you Wink Vote “voted” Wink

[REVIEWS] AMUTORCH: S3 / S3 vs 219c / AM30 / AX1 / VG10 /// SOFIRN: SF14 + SP10A / SP32A / SP10B /// NITEFOX: UT20 / ES10K / K3 /// ODEPRO: KL52 / B108 /// ACEBEAM: H20 / TK16 /// BLITZWOLF: BW-ET1 /// DQG: AA Slim Ti /// HC-LIGHTS: SS AAA /// XTAR: PB2 Charger /// OLIGHT: M2R Warrior /// WUBEN: TO10R / E05 / T70 / E10 /// ON THE ROAD: M1 / i3 / M3 Pro /// ROVYVON: A2 + A5R / E300S / A8 /// KLARUS: XT1C /// LUMINTOP: Tool AA V2.0 + Tool 25 /// LIVARNOLUX: 314791 /// SKILHUNT: M150

Tricks: 1 / 2 / 3 / 4 / 5 / 6 / 7 / 8 /// TIR Lenses: 1 / 2 /// Others: Biscotti 3 + 1*7135 / Triple TIR w/ XP-G2 ///// My Collection ///// My Review's Blog (PT)

GIVEAWAY: 1

Got Lumens
Got Lumens's picture
Offline
Last seen: 12 hours 51 min ago
Joined: 01/18/2012 - 23:18
Posts: 75
Location: Champlain Valley

67 reads and 3 votes hmmm.

What about a vote to enter a GAW for a Foursevens Preon P1 MKIII Black?

Neutrālisflashaholic