New Convoy C8 – Clearly better

You need to fix PWM level in current firmware version. Now they are too high.

Could you explain? What is too high? The amps?

Now sure how the PWM would be too high. high = better since it won’t produce any while or visible flicker?

My personal lights are usually loaded up with stop-motion strobes because I like the effect it has on moving water and other motions. I don’t generally include any tactical strobes at all.

Yes, which is why it was initially called bistro-mini. :slight_smile: It was as much of bistro as I could fit on a tiny13. Actually, I still need to merge some changes back into bistro itself, since I found a few extra ways to save space.

I picked a default bike mode based on what I liked, not based on actual research. If anyone has studies or polls showing that a different behavior would be better, I’d be happy to change it.

I don’t understand either.

The attiny13a can generally do PWM from about 128 Hz to 16 kHz. The lower speeds make visible flashes, while faster speeds sometimes make an audible whine. Ideal would be about 22 kHz — fast enough to look smooth, too high to hear, and otherwise as slow as possible for efficiency reasons.

The PWM speed can be fine-tuned on a single-channel driver like Convoy uses, but I didn’t attempt to make it faster than 16 kHz because people usually seem pretty happy with that speed. By setting the PWM ceiling to 180 instead of 255, the pulses would be about 22 kHz. However, this would only work on medium and high modes because the moon and low modes actually had to be slowed down to make the pulses long enough to activate the LED. It could be an option for later though.

As is, the default 5 modes run at 1 kHz / 8 / 16 / 16 / none. With a few extra lines of code it could be made to run at 1/8/22/22/none. On nicer drivers (RMM FET+1) I’d normally do 8/16/none/16ish/none. (by “ish” I mean half PWM where it alternates between medium and maximum without ever turning off) But the code this time was a compromise to maximize compatibility on a wide range of hardware.

How awesome would it be , if it had the bistro batt check instead of strobe (for me at least) :wink: .

Replied in the firmware thread to keep this thread semi-on topic. Flashlight Firmware Repository

Sorry, the volts+tenths method uses more room, and Simon wanted something simpler for a wider audience. So it does the 4-blink method instead. Otherwise, I agree.

I love it , even with the current setup.
Already using it in 2 fet drivers and 1 8x7135(+4 7135 chips).

I didn’t say anything about the PWM frequency :wink: I was talking about the levels of the PWM.

Now you use the following values:

With them, the driver has the output power levels 0.2% / 1.5% / 12.5% / 25% / 46% / 48% / 100% (instead 0.1 / 1 / 10 / 20 / 35 / 50 / 100)
I propose to change the values on

With them, the power levels will be closer to stated values.

ToyKeeper, you did a brilliant software, thank you. I now use it in all my flashlights.

Oh, I had it closer to that initially… but then I measured the power draw on each mode and adjusted the PWM values until the power measurements matched the spec. The PWM-to-power-usage curve was less linear than I expected, and it was consistently non-linear on the drivers I tested.

I’ll measure again when I get a production light, and adjust the levels if they’re not right. Maybe even make a new slow-ramp testing mode which goes through each PWM level one at a time while I log the measurements, so I can graph the shape of the curve.

On drivers with a more linear response, the default PWM levels will be a bit weird.

Still no option to buy with 8-10x 7135 chips yet huh?

8x is already available, didn’t know there was going to be a 10x. Chip number can be selected where it says Emitting Color.

Thanks for the info/clarification regarding the authenticity of the Nitecore D4 charger… did helped me alot! :smiley:

10x would have to be stacked chips and a DIY job. Although honestly at that point you would be better off getting a host and swapping the driver for something more advanced.

Lol, I’m sure I still have lights here with 20-32 7135 chips on the Qlite….

First post…I’m wondering if anyone knows for sure if the KeepPower 3500 cells will fit this flashlight. I have read a few conflicting posts - either a tight fit or not fitting. This light is on the way and I’m wondering if this battery will work or if I should order a different battery (suggestions?). Thanks in advance.

If the advertised measurements of that battery, 68.90mm (L) x 18.60 mm (D) are correct; they should fit just fine.

Welcome to BLF……… :+1:

:slight_smile:

Welcome to BLF.

The Sanyo NCR18650GA http://www.illumn.com/batteries-chargers-and-powerpax-carriers/18650-sanyo-ncr18650ga-3500mah-high-discharge-flat-top.html, is the same battery that’s inside the Keeppower in you link, It’s not protected like the Keeppower, but the flashlight have build in protection.
I don’t know about you knowledge with Lithium-ion battery safety but here is a great tread to get some info Lithium-ion battery safety 101

I am using the NCR18650GA is basically everything but my show lights now days. Great battery for general purpose use.

I agree that the NCR18650GA is a great general purpose cell if you don’t need crazy high drain. Just keep in mind if you’re buying the protected version of that cell it may be too tight a fit. I have the EVVA protected version and it’s too fat for many of my Convoy lights. The unprotected version should fit fine though. KeepPower is slimmer than EVVA sometimes on the same base cell so they may be fine too. EVVA protected cells are sometimes double wrapped where KP are not.

With any modern driver that has LVP there is really no need to use protected batteries anymore. I have actually never owned or used a protected battery, but then i might be a tad more capable of knowing how to use them then some people.