Reverse.
If by good C8 you mean a direct drive one like this light is then the C8 will have longer throw.
Thanks
But this one is more compact and feels better. And this driver plus firmware is superb.
Seems like a good choice of emitter too. Fantastic light, I need a forward clicky though with momentarily half press to last used ramp.
Would be great if these lights could be offered with a forward clicky option for people who need a tactical style light.
Forward clicky makes it a few mm longer and IMO makes a lot of the modes more difficult to transition between. I donāt mind them on some lights though.
I see you said ārampā, none of the lights with only one mechanical switch will ārampā. However, there are dual switch lights that can work like you describe (Sofirn C8F). A bit bigger light though.
Depends. If a driver uses a attiny 13 and up MCU (best with attiny25 or higher) it could be flashed with Toykeepers Crescendo, which ramps. Reverse clicky mechanical switch is easiet to use.
I should have known a senior member would mention this, lol. That is hardly a solution for 2 month member with forward switch request. BUT, yes technically correct. 
Thanks for all the advice 
This is probably getting way off topic butā¦
Here is a link to a Convoy C8+ with ramping
Convoy C8 with ramping driver
Will this work with a forward switch?
I have a C8G and it works great (I realise that it has two switches as mentioned, just saying). Set the ramp and then just use the half press to access it. Fantastic for night patrols. Only gripe is the CW tint else it would have been perfect for me. Hence me looking at the BLF-D80v2 which seems like a awesome light. Another user suggested that I could swap the emitter of the C8G but Iāll rather look for a stock light that meets my needs before resorting to modding.
Sofirn SP35/IF25 clip fits very well 
Nice! Thank you.
1 x sst40 (no ano)
This is an old message, but I just saw the question now. Will share my experience with regards to Convoy āramping driverā and a forward switch.
When the Convoy M21A was first released, it only had SST40 LED option, and uses a forward-clicky tailswitch.
Iāve tried the Convoy C8+ with SST40 LED and the Convoy ārampingā driver (which uses a reverse-clicky tailswitch).
I wanted to try the same on the M21A (the M21A is basically a C8, but uses a 21700 battery instead of 18650 battery), so I asked Simon of Convoy to install an M21A for me, but uses the āramping driverā instead of the default ā4-mode driverā (back then, the ānew 12-mode driver Biscotti clone driverā had not yet been developed, so thereās only the 4-mode driver and the ārampingā driver available for the SST40 LED with Convoyās offering.
What I had not expected was that Convoy M21A used a forward-clicky tailswitch for the M21A flashlight.
And thus, the āramping driverā does not work as expected ā as it requires a āhalf-pressā and āseveral half-pressesā to get to the configuration settings.
With the forward-clicky tailswitch, ārampingā function wonāt activate for the M21A. 
I had asked Simon if there is a reverse-clicky tailswitch available for the M21A, but he said that only forward-clicky tailswitch is available for the M21A model (I think that was in the earlier stages of production).
Since I preferred reverse-clicky tailswitch, I stayed away from the M21A model, but a longer time later, I decided to order the M21A again when it was introduced with different LED variants.
When I received the M21A, I notice it was now using a reverse-clicky tailswitch now. So I swapped this reverse-clicky tailswitch on the M21A with āramping driverā and it works now. The earlier forward-clicky tailswitch then went to the new M21A I got that uses the 4-mode driver (which works OK enough with forward-clicky tailswitch).
Uh. Youāre late buddy.
Is there a good explanation of the UI? The image on AE is turning my head inside out.
Dead topic reactivation award 
Nonetheless one of my best hosts even beating C8.
Currently running on L4P 9A driver with SFT-40. A real pocket - rocket 
Hi all. Just thought I'd pop back in from the dead to necro this old thread. I've just had no time for light things Iām afraid. Cool to see that bistro HD/OTSM was useful for it, and good for Lexel for getting that setup! Sorry I couldnāt support questions about this firmware more, although it still works.
For what it's worth. I did not configure a version of bistro-HD specifically for this light, and the manual was a modders manual, not a muggle manual. A modder selling a light might want to deliver a muggle manual. Bistro-HD does have many versions pre-configured but I donāt know if thatās what was used or which one. I wasnāt involved in this light specifically.
Here are a few things that may help with issues I saw come up in this thread, if anyone still cares about this old light and has questions about bistro-HD... I didnāt read this whole thread and much may have been eventually answered, years ago nowā¦
Mode groups...
The default modegroup files for bistro-HD are all here:
I don't know which one was selected during compilation for this light, or if one was customized or added. If they are the v1.3+ groups (95% by Texas Ace and those before him) then hodorās post #1234 on the previous page has things about right.
Other Bistro HD features that MIGHT be included with/helping this light or might not.
Thermal control:
Bistro HD 1.7.1 (which may or may not be the version in this light) has an optional (build option, not UI option) thermal control mode that is different.
It bumps down to a preset level (default build set to level 10) after overheating. A short press bumps it back to turbo (or I think whatever mode you were in) for 10 seconds minimum, or longer if itās not overheated. Itās not meant to be a thermally regulated output. Itās meant to optimize ability to use turbo reliably to see something when needed, to cool-off to be ready to do it again while still providing useful light in the meantime, and to allow brief override. As a bonus it doesnāt create frequent random brightness shifts. I donāt know if lexel enabled this thermal control method or not, or if he customized the turbo standby level well for this light.
OTSM and standard bistro
I think OTSM timing is understood here. The OTSM CAP, and probable lack of OTC cap, may interfere with mentioned attempts to modify a standard (not bistro-HD) bistro firmware to use OTC or OTC-less (noinit) behavior on this light, but it may be possible (and may be documented in this thread already). Itās probably easier to just tweak HD configuration to taste, and keep OTSM than to do that, but to each as they like of course.
Reverse clicks
Someone mentioned the āmediumā presses being a bit too long. This is easily configurable in the main configuration file that one should create a customized version of for each light/driver. For example in 1.7.1 I reduced it for the Q8 driver configuration as I found shorter timing is better on e-switches. Of course I have no idea how lexel configured it for this light. The default in HD isnāt super fast. But anyway, this is an issue for the light seller.
Menus
As I recall I think I made the menu options in HD always included, even for unused features. This means you donāt have to count blinks. The 5th option is always option 5 (I think).
By default they are:
1: muggle mode
2: memory
3: enable moon
4: reverse modes
5: Modegroup-select
6: Enable medium click
7: Temp cal
8: reset
9: never mind about 9
Extended moon mode
If the light components are selected well, and PWM tables set well for the light, depending on the emitter, HD powersaving (if compiled in) allows the lowest moon mode (or firefly really) to last over a month in theory on a single cell (I never tested that long, but Iāve left it many days.)
About the firmware code:
ToyKeeper correctly pointed out that almost every line of code has changed or been reorganized from original bistro. That said, many, or most parts are still quite recognizable as bistro and evolved directly from it. Many of the modifications were optimizations and organization, for saving memory, adding OTSM control, and for allowing more comprehensive compile-time configuration (programming what the program will be really) and easier calibration, all allowing it to build so many different pre-configured drivers from the compilation script (Makefile) alone. Its soul is still very much bistro, and of course to a user it seems pretty much like bistro, but yes, from a sense of things like āis this vetted on some light,ā itās certainly not just a distribution of bistro.
Iāve been using 1.7.1 happily for real world use on a Q8 (e-switch) and a clicky OTSM light, and will use it again on e-switch lights too if I get a chance. I had ambitions to add some new features, but I havenāt touched it at all, but also havenāt needed to.
Thank you yes I would guess many of us have a soft spot for this āno nonsenseā light.
Is this still a attractive light today? Or is it old technology. As you know, lights are technology.
Looks nice to me, but the price is too much.
I appreciate that it was built with 5+1 and not 6 or 7+1. I would actually consider building a single cell light with probably 3 or 4 +1. Even 2+1 is ok, and so is FET+3 (higher moon).
The reason is this: Once the battery gets too low to support all the 7135s, every mode between 1 and N 7135s becomes unregulated anyway, even levels that could still be supported if there were fewer 7135s. That's because it's still using all of them, at full power, and just PWMing them. It either can support them all or it can't. If it can't, it dims continuously as the battery continues to drain. You still have some of the efficiency advantage of least not PWMing the FET, (Edit: Nah, even that isn't true at that point).
I prefer a light where I could just set it at say 500 lumen level and it will last there until it can't. To me, the right place for that level is probably about whatever can run for close to 3 hours, so maybe a bit over an amp, and certainly not more than it can thermally sustain. But that's personal as each user may have a different opinion on how long they need to use the light before recharging, and it's easy to desolder a 7135 on these drivers. Of course this is an advantage of buck drivers, with the downside that they don't direct-drive very well.