Proposed Improvements to Convoy's user interface(s).

34 posts / 0 new
Last post

Pages

tactical_grizzly
tactical_grizzly's picture
Offline
Last seen: 8 hours 37 min ago
Joined: 11/08/2020 - 14:54
Posts: 280
Location: North Texas
Proposed Improvements to Convoy's user interface(s).

I posted this over on Reddit several months ago but another user recently pushed me to post it here too, and then send it on to Simon.

On the 12 Group/4 Mode firmwares: Almost all of Convoy’s tailswitch lights are available with the “12 Mode Group” firmware that’s heavily based on Biscotti. It’s good, but I find it lacking in a few areas. I wanted to share and discuss some ideas for how I think it can be improved. I think all of these changes would add a lot to the UI and without any negative effects.

1: Add shortcuts
The biggest gripe I have with Biscotti is the lack of shortcuts. I think it would be great to have a quick double-tap function that can jump to 100% or to tactical strobe, and can be enabled or disabled. Right now the firmware’s main menu only has 2 sections: mode group configuration and mode memory configuration. I think it would be good to have a 3rd section for shortcut configuration. In this menu, a single tap should disable the shortcut. A double tap should enable/change the double-tap shortcut to 100%. A triple tap should enable/change the double-tap shortcut to tactical strobe. It should come with the shortcut disabled by default for ease of use, just like how Convoy’s 4-Mode firmware doesn’t have blinkies.

2. Move blinky modes
Right now there are several duplicate mode groups whos only difference is the presence or absence of blinky modes. I think the duplicate mode groups should be removed and the blinky modes should be added as a 4th option in the programming menu. A single tap in this menu should toggle blinkies on/off, just how the 2nd programming option toggles mode memory on/off. They should come disabled by default for ease of use, and if they’re enabled they should just be added to the end of whatever mode group you’re currently using.

3. Add more mode groups & discontinue the 4 mode driver
Assuming blinkies are moved to a programming menu like I suggested in #3, that opens up room for more mode groups. With room for more mode groups, I think it makes sense to add the 4 mode group found in the 4 mode firmware and make it the default mode group. With mode memory enabled, shortcuts disabled, and blinkies disabled, and the 4 mode group set all by default, there’s no need for a separate 4 mode firmware anymore. I think the 4 mode firmware should be discontinued.

This will simplify buying options, eliminating questions for Simon and existing enthusiasts. It won’t make the light’s any harder to use for muggles either, because the stock configuration will be virtually identical to the existing 4 mode firmware. It will also retain (and add to) the customization possibilities found in the current 12 group firmware for enthusiasts. Finally, it will allow muggles who become enthusiasts to customize their lights down the line, rather than locking them into the 4-mode firmware they purchased with the light.

4: Add thermal limit adjustment
In all three of the Convoy 12 Group lights I’ve had the chance to test, when set to 100% mode, once they are thermally saturated they are just too hot to hold. I would like the ability to adjust the thermal limit in Convoy lights. I think adding a 5th programming menu option would be an appropriate solution. I believe the current thermal limit is 55C, and I’d like to see two more options: 45C and 65C. One tap should set the thermal limit to 45C, two should be the default and should set it to 55C, and three taps should set it to 65C. This would allow users to lower it on lights that get too hot like the M2, and would allow other users to maximize sustained output. More steps could be added, but at the very least there should be a cooler setting and a hotter setting, in addition to the 55C stock setting.

5: Add a battery check shortcut, make it blink out the voltage, and remove it from the blinky group
I don’t love Convoy’s current implementation of battery check. The 1-5 blinks is OK, but I would rather it blink out the first digit of the voltage, pause, then blink out the second digit (exactly like Anduril or Convoy’s e-switch UI). I would also prefer it NOT be tied in with the other blinky modes. I think there should be a 10-half-press shortcut to get to battery check. It’s not something you need quick access to, and 10 will keep it clear of users who will quickly tap several times to change to a particular mode in their selected mode group. It also won’t cause any problems for muggles, as the battery check mode won’t change any settings. If you enter it by accident, just turn off the light and no harm is done.

6: add mode reversing and eliminate duplicate mode groups
Rather than having two mirrored mode groups with the same modes (1-20-100% and 100-20-10%, for example) just have one group. Then add a mode-order-reverse toggle in the programming menu. This would eliminate the need for duplicate mode groups and it would allow users to have reversed versions of groups that currently aren’t available.

On Convoy’s E-switch UI

Use Anduril 2
The E-switch UI used on Simon’s electronic side switch lights leaves a bit to be desired. I could go into the issues and how to fix them, but I think a better solution would be to use Anduril 2, which is already basically perfect. In the past, Simon has expressed openness to use Anduril, but he needs to talk with his driver manufacturer more, and some of his Chinese customers find Anduril too complicated. I think now that Anduril 2 exists and defaults to the Simple UI, the complexity is no longer an issue since Anduril 2’s simple UI is less complicated than Simon’s own E-switch UI. I hope that he will reconsider Anduril 2, as I have heard from several users that they don’t buy his e-switch lights because of the sub-par UI.

On some minor hardware improvements

Lower the lowest mode
This is a hardware issue and not a firmware issue, so it’s harder to impliment I think. I wanted to mention it nonetheless. On every Convoy light I’ve tried so far, the lowest mode has been very bright, like in the tens of lumens range. I would be delighted to see real moonlight modes (less than 1 lumen) in Convoy’s higher-powered models.

Add forward clickies as an official option in the store
Right now, Simon will usually install a forward clicky switch in most lights if you ask nicely, but I’d love to be able to just spec a light with a forward clicky on the product page.

Use ATTiny microcontrollers
Using these popular microcontrollers and standard reflashing pads on the exposed side of the driver would allow enthusiasts to easily reflash whatever firmware they like onto a Convoy light, as well as perform easy firmware updates if features are added. This should absolutely be done on e-switch lights, but might it be possible to do on mechanical switch lights too? Hank’s pin layout should be used and/or Simon should carry a reflashing kit on his Aliexpress store.

What do you think about these changes? Are there any other changes you’d like to see? I’ll make sure to send this post to Simon soon.

Edited by: tactical_grizzly on 10/24/2021 - 23:03
Scallywag
Scallywag's picture
Offline
Last seen: 7 hours 44 min ago
Joined: 01/11/2018 - 22:23
Posts: 2280
Location: Ohio, United States

I’d settle for a way to convert the E-switch drivers to Anduril. Whether that’s with flashed MCUs, MCU swaps… I’d love the L7 with Anduril, and others as well.

If Simon was using ATTinys we’d be able to easily flash whatever firmwares we wanted.

tactical_grizzly
tactical_grizzly's picture
Offline
Last seen: 8 hours 37 min ago
Joined: 11/08/2020 - 14:54
Posts: 280
Location: North Texas

Scallywag wrote:
I’d settle for a way to convert the E-switch drivers to Anduril. Whether that’s with flashed MCUs, MCU swaps… I’d love the L7 with Anduril, and others as well.

If Simon was using ATTinys we’d be able to easily flash whatever firmwares we wanted.

I agree. That would be excellent. I’ve added it to the hardware changes section.

L7 with Anduril would be interesting. The tailswitch would be rendered useless except for mechanical lockout, but I’d be happy with that. It bugs me that L7 current requires two hands to operate since it’s so large and the switches are so far apart.

id30209
id30209's picture
Offline
Last seen: 1 hour 12 min ago
Joined: 05/17/2018 - 12:20
Posts: 2111
Location: Croatia

All sounds good TG, no complaints.

WTB Titanium 4sevens 2xAA tube

Scallywag
Scallywag's picture
Offline
Last seen: 7 hours 44 min ago
Joined: 01/11/2018 - 22:23
Posts: 2280
Location: Ohio, United States

tactical_grizzly wrote:
Scallywag wrote:
I’d settle for a way to convert the E-switch drivers to Anduril. Whether that’s with flashed MCUs, MCU swaps… I’d love the L7 with Anduril, and others as well.

If Simon was using ATTinys we’d be able to easily flash whatever firmwares we wanted.

I agree. That would be excellent. I’ve added it to the hardware changes section.

L7 with Anduril would be interesting. The tailswitch would be rendered useless except for mechanical lockout, but I’d be happy with that. It bugs me that L7 current requires two hands to operate since it’s so large and the switches are so far apart.


Anduril has a compile-time option to enable dual-switch.
tactical_grizzly
tactical_grizzly's picture
Offline
Last seen: 8 hours 37 min ago
Joined: 11/08/2020 - 14:54
Posts: 280
Location: North Texas

Scallywag wrote:
tactical_grizzly wrote:
Scallywag wrote:
I’d settle for a way to convert the E-switch drivers to Anduril. Whether that’s with flashed MCUs, MCU swaps… I’d love the L7 with Anduril, and others as well.

If Simon was using ATTinys we’d be able to easily flash whatever firmwares we wanted.

I agree. That would be excellent. I’ve added it to the hardware changes section.

L7 with Anduril would be interesting. The tailswitch would be rendered useless except for mechanical lockout, but I’d be happy with that. It bugs me that L7 current requires two hands to operate since it’s so large and the switches are so far apart.


Anduril has a compile-time option to enable dual-switch.

Oh, now that’s interesting! L7 would be incredibe with that firmware then!

Engond
Offline
Last seen: 2 months 4 weeks ago
Joined: 01/19/2021 - 19:37
Posts: 5
Location: UK

I’m a big fan of Convoy flashlights but my biggest problem with the convoy drivers is that they seem to be unreliable. In my experience i’d say there’s about 70% chance you’ll get one that works properly. I had to replace the 4*7135 in my s2’s multiple times because of issues like it getting stuck in the config mode or stuck with the mode memory enabled or just randomly behaviour with the mode groups.
I ordered a packet of 5 drivers and 2 out of 5 had problems with config mode.
I love how easy it is to fix the S2 if it breaks (especially with the 4*7135 driver or the 5A driver because you have a retaining ring and don’t need to solder the driver to the pill) but I really would love it if the drivers were as reliable as the hosts.

As for the 12 group driver interface, I think the battery checker mode is really nice but there are only 3 groups that have it, it would be nice if there was a shortcut for battery checker from any group.

The mode spacing for the 5A driver could be better I think, with Lh351D and SST40 I think there is too much of a difference between mode 2 and 3. It seems like it goes from around 16 lumens on mode 2 (1%) to like 160 lumens on mode 3 (10%). A group that has a mode with 5% brightness would be really nice as a balance between brightness and runtime for general use.

I’m thinking maybe 1%, 5%, 10%, 35% and a shortcut for 0.1% moonlight, 100% turbo and battery checker but realistically I’d be happy if the current drivers were just consistently reliable.

stephenk
stephenk's picture
Online
Last seen: 8 min 48 sec ago
Joined: 01/30/2016 - 05:09
Posts: 1901
Location: Australia

I quite like 12 group/Biscotti. It is nice and simple. The most pressing change to 12 Group/Biscotti is to change the strobe from the terrible alternating frequency strobe back to to constant frequency (anywhere between 10 to 20Hz with 50/50 on/off time would be good. Also strobe HAS to be able to memorized so that it is instantly accessible from off with a single click*. This would make it the best budget light for light painters.

  • sadly so many flashlights now make it so difficult to access strobes, that 95% of flashlights are useless for those who actually need to access strobes. It is possible to make firmware so that strobes might need the (what seems to now be usual) double or triple click to access from on, but after strobe is selected, it should then me memorized. This would mean that those who don’t need to access strobes should never enter strobe mode, but those who do use can have it memorized at the next turn on.

If Convoy does go down the Anduril route, a tail e-switch S2+ style light would be great.

tactical_grizzly
tactical_grizzly's picture
Offline
Last seen: 8 hours 37 min ago
Joined: 11/08/2020 - 14:54
Posts: 280
Location: North Texas

Engond wrote:
I’m a big fan of Convoy flashlights but my biggest problem with the convoy drivers is that they seem to be unreliable. In my experience i’d say there’s about 70% chance you’ll get one that works properly. I had to replace the 4*7135 in my s2’s multiple times because of issues like it getting stuck in the config mode or stuck with the mode memory enabled or just randomly behaviour with the mode groups.
I ordered a packet of 5 drivers and 2 out of 5 had problems with config mode.
I love how easy it is to fix the S2 if it breaks (especially with the 4*7135 driver or the 5A driver because you have a retaining ring and don’t need to solder the driver to the pill) but I really would love it if the drivers were as reliable as the hosts.

As for the 12 group driver interface, I think the battery checker mode is really nice but there are only 3 groups that have it, it would be nice if there was a shortcut for battery checker from any group.

The mode spacing for the 5A driver could be better I think, with Lh351D and SST40 I think there is too much of a difference between mode 2 and 3. It seems like it goes from around 16 lumens on mode 2 (1%) to like 160 lumens on mode 3 (10%). A group that has a mode with 5% brightness would be really nice as a balance between brightness and runtime for general use.

I’m thinking maybe 1%, 5%, 10%, 35% and a shortcut for 0.1% moonlight, 100% turbo and battery checker but realistically I’d be happy if the current drivers were just consistently reliable.

I have no way of confirming this suspicion, but I think most driver issues I’ve heard of have been with 7135 based drivers. So, in theory, the newer linear drivers may be more reliable? Either way, unreliable drivers are certainly an issue.

I updated the post with details about how I think a battery check should be implimented.

After moving the blinky modes to a toggle-able option rather than having duplicated mode groups, there should definitely be space for another mode group with a 5% mode instead of 10%.

How do you suggest the 0.1% moonlight shortcut should work? The way I would do that is by selecting a mode group with 0.1% as a mode, and disabling mode memory. It’s not really a shortcut, but the light would always turn on at 0.1% mode. Do you have an alternative solution? Moonlight shortcuts are usually implemented on e-switch lights where holds are a possible action. Holds aren’t an option with mechanical switches really.

Tom E
Tom E's picture
Offline
Last seen: 3 days 13 hours ago
Joined: 08/19/2012 - 08:23
Posts: 15042
Location: LI NY

I added Anduril2 to the 3X21A, but had to lose the charging. Benefit was more power as well, 4 FET's replaced by one good one:

I know, it's cheating smile

tactical_grizzly
tactical_grizzly's picture
Offline
Last seen: 8 hours 37 min ago
Joined: 11/08/2020 - 14:54
Posts: 280
Location: North Texas
Tom E wrote:

I added Anduril2 to the 3×21A, but had to lose the charging. Benefit was more power as well, 4 FET’s replaced by one good one:



I know, it’s cheating smile

That’s pretty incredible. I would be extatic to have Anduril on my 4×18A, even if it meant losing built in charging.

Scallywag
Scallywag's picture
Offline
Last seen: 7 hours 44 min ago
Joined: 01/11/2018 - 22:23
Posts: 2280
Location: Ohio, United States

Tom E wrote:

I added Anduril2 to the 3×21A, but had to lose the charging. Benefit was more power as well, 4 FET’s replaced by one good one:



I know, it’s cheating smile


There ya go with the piggyback again!
Tom E
Tom E's picture
Offline
Last seen: 3 days 13 hours ago
Joined: 08/19/2012 - 08:23
Posts: 15042
Location: LI NY

I'm working on another one now for someone. Added a 3rd 20 AWG ground, and on mine I used two pair of 18 AWG wires, but for the new one, I'm using 1 pair of 16 AWG's. Every time I do a mod again, always make some improvements.

Engond
Offline
Last seen: 2 months 4 weeks ago
Joined: 01/19/2021 - 19:37
Posts: 5
Location: UK

Yea I do think the 5A driver is more reliable, I only had one of them fail, I had my 5000k LH351D on mode 3 (10% brightness) and the beam started to turn angry blue and it got super hot so I had turn it off, not sure what went wrong but the lower brightness modes stopped working completely. I replaced driver and Led and it’s fine now though.
I just like the mode spacing and runtime of the 4*7135 drivers but I’d pick the 5A driver for reliability and nice output.

Well I think it’s probably good if the light always comes on in moonlight, just need to find a good balance between the mode spacing and having too many modes to tap through. Most of the groups are too similar in terms of mode spacing. Adding a toggleable option to be able to choose whether you want ascending or descending mode order would further reduce the amount of groups needed, pretty much like the Reylight driver.

I like the idea of being able to disable/enable a true low moonlight, like the way you can disable it in Reylights or the way you can disable mode memory in the current convoy drivers.

So for example an S2+ with 5A driver and SST40 (take these number with a large grain of salt)

Mode 1 (0.1%) 1.8 Lumens

Mode 2 (1%) 18 Lumens

Mode 3 (10%) 180 Lumens

Mode 4 (35%) 630 Lumens

Mode 5 (100%) 1800 Lumens

Modes 1 and 2 are fine.
There’s a big difference between 2 and 3.
Most of the time Mode 5 will look very similar to mode 4 because it will step down due to heat.

So I think adding a mode with 5% would give a nice brightness of around 90 lumens maybe in this example. And 20% could give around 360 lumens maybe.

I don’t like how the current drivers have 20% separate from any of the groups that have moonlight or 10% so all of my convoys just have the default group 1 selected, the other groups are just too similar with minor differences.

Also for your suggestion of 10 taps for battery indicator, I think that would be good as long as you don’t accidently go into config mode and yea i’d love too see accurate voltage read outs rather than the current indicator.

tactical_grizzly
tactical_grizzly's picture
Offline
Last seen: 8 hours 37 min ago
Joined: 11/08/2020 - 14:54
Posts: 280
Location: North Texas
Engond wrote:
Well I think it’s probably good if the light always comes on in moonlight, just need to find a good balance between the mode spacing and having too many modes to tap through. Most of the groups are too similar in terms of mode spacing. Adding a toggleable option to be able to choose whether you want ascending or descending mode order would further reduce the amount of groups needed, pretty much like the Reylight driver.

Agreed. I think having several groups starting at moonlight and ending with 100% would be good. Probably five total, ranging from two to 6 modes, with an even multiplier between the modes so the spacing looks consistent. For example, the 4-mode group would look like 1 – 10 – 100 – 1000 lumens, where the multiplier is 10x.

Being able to reverse the mode order is a great idea. That would eliminate a few duplicate mode groups and it would also allow for more total configurations.

Engond wrote:
I like the idea of being able to disable/enable a true low moonlight, like the way you can disable it in Reylights or the way you can disable mode memory in the current convoy drivers.

That strikes me as crossing the line from adding complexity for the sake of improvement, to adding complexity for the sake of complexity. I don’t see a need for moonlight mode to be toggle-able because I think most users who would not want moonlight would be served just fine by a mode group that doesn’t have it.

Engond wrote:
Mode 1 (0.1%) 1.8 Lumens

Mode 2 (1%) 18 Lumens

Mode 3 (10%) 180 Lumens

Mode 4 (35%) 630 Lumens

Mode 5 (100%) 1800 Lumens

Modes 1 and 2 are fine.
There’s a big difference between 2 and 3.
Most of the time Mode 5 will look very similar to mode 4 because it will step down due to heat.

Keep in mine we perceive brightness logarithmically. Jumping from 1.8lm to 18lm is visually the same increase as jumping from 18lm to 180lm. Out of those particular lumen numbers you provided as an example, mode 4 seems out of place to me because it breaks the otherwise consistent 10x lumen increase multiplier between modes.

Engond wrote:
Also for your suggestion of 10 taps for battery indicator, I think that would be good as long as you don’t accidently go into config mode and yea i’d love too see accurate voltage read outs rather than the current indicator.

Yeah, I would not want the 20 taps for programming to be changed, so 10 taps for battery check should not get anywhere near the programming mode.

Hoop
Hoop's picture
Offline
Last seen: 1 hour 2 min ago
Joined: 12/20/2012 - 05:33
Posts: 1076
Location: Spokane, WA

tactical_grizzly wrote:
Keep in mine we perceive brightness linearly. Jumping from 1.8lm to 18lm is visually the same increase as jumping from 18lm to 180lm. Out of those particular lumen numbers you provided as an example, mode 4 seems out of place to me because it breaks the otherwise consistent 10x lumen increase multiplier between modes.

It is not accurate to say “we perceive brightness linearly.” We perceive it logarithmically. 2 lumens does not appear twice as bright as 1 lumen. But you are comparing relative increases in terms of percentage and saying equal % increases will be perceived equally.
tactical_grizzly
tactical_grizzly's picture
Offline
Last seen: 8 hours 37 min ago
Joined: 11/08/2020 - 14:54
Posts: 280
Location: North Texas
Hoop wrote:
tactical_grizzly wrote:
Keep in mine we perceive brightness linearly. Jumping from 1.8lm to 18lm is visually the same increase as jumping from 18lm to 180lm. Out of those particular lumen numbers you provided as an example, mode 4 seems out of place to me because it breaks the otherwise consistent 10x lumen increase multiplier between modes.
It is not accurate to say “we perceive brightness linearly.” We perceive it logarithmically. 2 lumens does not appear twice as bright as 1 lumen. But you are comparing relative increases in terms of percentage and saying equal % increases will be perceived equally.

You are absolutely right. That was a typo and has been corrected.

Engond
Offline
Last seen: 2 months 4 weeks ago
Joined: 01/19/2021 - 19:37
Posts: 5
Location: UK

That’s great if the number of groups can be reduced and added more variation for users. Like if you preferred a different multiplier for the mode spacing. I don’t know if it’s possible to make the brightness of the mode groups this specific (I have rounded up and down some of the numbers) but it would allow for a lot more customization of brightness and personally I think the x3 multiplier could be really nice.

0.1%, 0.4%, 3%, 17%, 100% (x6 multiplier) 0.1%, 0.8%, 4%, 20%, 100% (x5 multiplier) 0.4%, 1.5%, 6%, 25%, 100% (x4 multiplier) 1.2%, 4%, 11%, 33%, 100% (x3 multiplier) 0.4%, 1.2%, 4%, 11%, 33% (x3 multiplier)
stephenk
stephenk's picture
Online
Last seen: 8 min 48 sec ago
Joined: 01/30/2016 - 05:09
Posts: 1901
Location: Australia

Engond wrote:
That’s great if the number of groups can be reduced and added more variation for users. Like if you preferred a different multiplier for the mode spacing. I don’t know if it’s possible to make the brightness of the mode groups this specific (I have rounded up and down some of the numbers) but it would allow for a lot more customization of brightness and personally I think the x3 multiplier could be really nice. 0.1%, 0.4%, 3%, 17%, 100% (x6 multiplier) 0.1%, 0.8%, 4%, 20%, 100% (x5 multiplier) 0.4%, 1.5%, 6%, 25%, 100% (x4 multiplier) 1.2%, 4%, 11%, 33%, 100% (x3 multiplier) 0.4%, 1.2%, 4%, 11%, 33% (x3 multiplier)
There needs to be a 35% mode as that is where the S2+ tends to thermo-regulate.
tactical_grizzly
tactical_grizzly's picture
Offline
Last seen: 8 hours 37 min ago
Joined: 11/08/2020 - 14:54
Posts: 280
Location: North Texas

stephenk wrote:
Engond wrote:
That’s great if the number of groups can be reduced and added more variation for users. Like if you preferred a different multiplier for the mode spacing. I don’t know if it’s possible to make the brightness of the mode groups this specific (I have rounded up and down some of the numbers) but it would allow for a lot more customization of brightness and personally I think the x3 multiplier could be really nice. 0.1%, 0.4%, 3%, 17%, 100% (x6 multiplier) 0.1%, 0.8%, 4%, 20%, 100% (x5 multiplier) 0.4%, 1.5%, 6%, 25%, 100% (x4 multiplier) 1.2%, 4%, 11%, 33%, 100% (x3 multiplier) 0.4%, 1.2%, 4%, 11%, 33% (x3 multiplier)
There needs to be a 35% mode as that is where the S2+ tends to thermo-regulate.

That depends heavily on the emitter used. A super efficient emitter like SST40 is going to sustain a higher drive current than a lower efficiency emitter like an SST20 4000K. Since sustained output varies based on emitter efficiency, I don’t think that should be a deciding factor when determining output levels.

stephenk
stephenk's picture
Online
Last seen: 8 min 48 sec ago
Joined: 01/30/2016 - 05:09
Posts: 1901
Location: Australia

tactical_grizzly wrote:
stephenk wrote:
Engond wrote:
That’s great if the number of groups can be reduced and added more variation for users. Like if you preferred a different multiplier for the mode spacing. I don’t know if it’s possible to make the brightness of the mode groups this specific (I have rounded up and down some of the numbers) but it would allow for a lot more customization of brightness and personally I think the x3 multiplier could be really nice. 0.1%, 0.4%, 3%, 17%, 100% (x6 multiplier) 0.1%, 0.8%, 4%, 20%, 100% (x5 multiplier) 0.4%, 1.5%, 6%, 25%, 100% (x4 multiplier) 1.2%, 4%, 11%, 33%, 100% (x3 multiplier) 0.4%, 1.2%, 4%, 11%, 33% (x3 multiplier)
There needs to be a 35% mode as that is where the S2+ tends to thermo-regulate.

That depends heavily on the emitter used. A super efficient emitter like SST40 is going to sustain a higher drive current than a lower efficiency emitter like an SST20 4000K. Since sustained output varies based on emitter efficiency, I don’t think that should be a deciding factor when determining output levels.


Actually they both regulate at approx. 35% in the S2+ but have different drivers suited for the emitter’s max output – 5A and 2.8A respectively.
tactical_grizzly
tactical_grizzly's picture
Offline
Last seen: 8 hours 37 min ago
Joined: 11/08/2020 - 14:54
Posts: 280
Location: North Texas

stephenk wrote:
tactical_grizzly wrote:
stephenk wrote:
Engond wrote:
That’s great if the number of groups can be reduced and added more variation for users. Like if you preferred a different multiplier for the mode spacing. I don’t know if it’s possible to make the brightness of the mode groups this specific (I have rounded up and down some of the numbers) but it would allow for a lot more customization of brightness and personally I think the x3 multiplier could be really nice. 0.1%, 0.4%, 3%, 17%, 100% (x6 multiplier) 0.1%, 0.8%, 4%, 20%, 100% (x5 multiplier) 0.4%, 1.5%, 6%, 25%, 100% (x4 multiplier) 1.2%, 4%, 11%, 33%, 100% (x3 multiplier) 0.4%, 1.2%, 4%, 11%, 33% (x3 multiplier)
There needs to be a 35% mode as that is where the S2+ tends to thermo-regulate.

That depends heavily on the emitter used. A super efficient emitter like SST40 is going to sustain a higher drive current than a lower efficiency emitter like an SST20 4000K. Since sustained output varies based on emitter efficiency, I don’t think that should be a deciding factor when determining output levels.


Actually they both regulate at approx. 35% in the S2+ but have different drivers suited for the emitter’s max output – 5A and 2.8A respectively.

That’s true that there are two different drivers. I believe it’s just a matter of older versions coming with the older 2.8A driver though, as all of the newer releases (except for 219B which can’t handle 5A) come with the newer 5A driver and newer 12 group firmware.

The efficiency of the emitters doesn’t appear to correlate with the drivers either, as the 2.8A driver comes with a few high efficiency emitters (xpl-hi, SST20 5000K+, XPG2) and a few low efficiency emitters (219C, LH351D, SST20 4000K-), so the stable outputs don’t appear to correlate with the driver choice as you’re suggesting.

Regardless, in my proposed UI changes, you could simply choose a mode group that includes a level near 35% like you prefer. Or, you could adjust the thermal limit up or down to achieve the stable output you want.

Sirius9
Sirius9's picture
Offline
Last seen: 10 hours 17 min ago
Joined: 03/04/2012 - 19:23
Posts: 4652
Location: South Europe

Use ATTiny microcontrollers

Not really big fan of Convoy’s 12 mode group UI here but I mostly use custom UI anyway but since Simon changed MCU those drivers become totally worthless for me which is a huge hassle because now I have to find them from other suppliers so you have a big YES from me for returning Tiny13a MCU.

 

pennzy
pennzy's picture
Offline
Last seen: 10 hours 6 min ago
Joined: 12/10/2017 - 19:45
Posts: 4156
Location: United States , Pa.

I would like to see a way back to last used level from turbo in the 4 mode UI.

tactical_grizzly
tactical_grizzly's picture
Offline
Last seen: 8 hours 37 min ago
Joined: 11/08/2020 - 14:54
Posts: 280
Location: North Texas
pennzy wrote:
I would like to see a way back to last used level from turbo in the 4 mode UI.

That’s super easy to do already. You just have to know what mode you were in, then it’s a quick 1-3 taps to return to that mode. I can’t think of a simpler way to do it than that.

pennzy
pennzy's picture
Offline
Last seen: 10 hours 6 min ago
Joined: 12/10/2017 - 19:45
Posts: 4156
Location: United States , Pa.
tactical_grizzly wrote:
pennzy wrote:
I would like to see a way back to last used level from turbo in the 4 mode UI.

That’s super easy to do already. You just have to know what mode you were in, then it’s a quick 1-3 taps to return to that mode. I can’t think of a simpler way to do it than that.


Anduril has spoiled me. Also some UIs double tap to turbo, single tap back to last used level. You can sort of do this double tap back if you do it slowly but you are turning the light off first then the second tap turns it back on to memorized level. After going to turbo with the Convoy, you have to cycle through L, M, H to get back. Low seems like off practically after turbo.
tactical_grizzly
tactical_grizzly's picture
Offline
Last seen: 8 hours 37 min ago
Joined: 11/08/2020 - 14:54
Posts: 280
Location: North Texas
pennzy wrote:
tactical_grizzly wrote:
pennzy wrote:
I would like to see a way back to last used level from turbo in the 4 mode UI.

That’s super easy to do already. You just have to know what mode you were in, then it’s a quick 1-3 taps to return to that mode. I can’t think of a simpler way to do it than that.


Anduril has spooled me. Also some UIs double tap to turbo, single tap back to last used level. You can sort of do this double tap back if you do it slowly but you are turning the light off first then the second tap turns it back on to memorized level. After going to turbo with the Convoy, you have to cycle through L, M, H to get back. Low seems like off practically after turbo.

Oh yeah I get that. It’s just dependent on the switch type. For e-switches I want Anduril 2 of course. But, most of their lights use mechanical switches and I can’t think of a great way to do a “return to last used mode from turbo” function on a mechanical switch.

pennzy
pennzy's picture
Offline
Last seen: 10 hours 6 min ago
Joined: 12/10/2017 - 19:45
Posts: 4156
Location: United States , Pa.

Sorry, I should have said with their side switch lights.

tactical_grizzly
tactical_grizzly's picture
Offline
Last seen: 8 hours 37 min ago
Joined: 11/08/2020 - 14:54
Posts: 280
Location: North Texas
pennzy wrote:
Sorry, I should have said with their side switch lights.

Oh yeah totally. As I said in the first post, rather than improving Convoy’s existing e-switch UI, I think it would be better to go ahead and adopt Anduril 2.

pennzy
pennzy's picture
Offline
Last seen: 10 hours 6 min ago
Joined: 12/10/2017 - 19:45
Posts: 4156
Location: United States , Pa.
tactical_grizzly wrote:
pennzy wrote:
Sorry, I should have said with their side switch lights.

Oh yeah totally. As I said in the first post, rather than improving Convoy’s existing e-switch UI, I think it would be better to go ahead and adopt Anduril 2.


I wish so too. As long as he keeps his boost driver with it.
Josh V
Offline
Last seen: 3 weeks 6 days ago
Joined: 11/05/2020 - 01:20
Posts: 12

tactical_grizzly those are nice ideas, I would like simon to replace the 4 modes driver into a 5 or 7 friendly groups without tactical strobe, something like this:

Pages