New Convoy C8 – Clearly better

?huh ,tnuoc ym fo emos ecuder ot redro ni sdrawkcab gnihtyreve gniyas trats ylbaborp dluohs I

I don’t think it works that way :partying_face:

(man, after a bit of Sobieski, that took a minute to process!)

ROFLMAO!

I had the standard text on standby, just in case. :stuck_out_tongue:

Y’all are soon to be on vacation from my ever present wit so enjoy it while you can. :wink:

So, the eeprom is rated for 100,000 erase/write cycles minimum per byte… but in actual testing people tend not to encounter any failures until more like 10 million write cycles. So take 100k as a lower bound and 10M as an upper bound.

With only 32 bytes used for wear-leveling, let’s find out how many times a day you’d have to press the button to make it fail in 1000 years or less:

  • 100,000 * 32 / 365.24 / 1000 = 8.76
  • 10,000,000 * 32 / 365.24 / 1000 = 876

So… to make it fail in 1000 years, you’d have to press the button at least 8.76 times per day (every day) or potentially up to 876 times per day. I’m pretty sure some other part of the light would wear out first, like … the switch.

I didn’t care for it either. You can reflash it with a different firmware like guppydrv for instance or swap to a driver that has different firmware on it.

Both my S2+ and black C8 have guppydrv and it’s great.

guppydrv lacks low voltage protection though, something to be aware of….

Really? This is the first I’m hearing of it.

For example, on MTNs website for the Qlite driver it says the driver has low voltage protection then it says guppydrv is an option. It doesn’t say you lose the LVP with this firmware.

Maybe Richard should point this out as I had no idea.

In my 2 lights that have guppydrv I use protected cells. The one I’m working on right now, I had planned to use an unprotected one. I guess I can switch to a protected battery for it. Ah wait, that one was gonna use 2 26350 which are unprotected only. I may need to switch to a different firmware.

Thanks for the heads up.

Richard DOES point that out. He states that the light will downshift but will not turn off.

Which means that it’ll run in the lowest mode till the battery is dead.

If you use the newest Bistro you’ll have a similar number of mode choices, it’s on the list as 9 but by changing H-L/L-H you’re doubling the list. Bistro allows you to set it up as you like, at will, including changing memory by toggling it on or off. You decide if it has 2 levels or 3 or 4 or 5 or 6 or 7 or 8 or 9, at will. You decide if it has moon or not. Also gives you choices with strobes, in a hidden group you back into. And the ability to reverse to a lower mode can go a LONG way towards saving battery life. Bistro is also on an FET+1 driver, so your lower modes are more efficient, pulling from a single 7135 chip instead of 8 or the FET.

Okay, so guppydrv has more of a low voltage warning as opposed to low voltage protection. You’ll know when the battery gets too low, but if the light gets turned on by accident and you don’t realize it, then it can drain the battery dangerously low. Is that correct?

Pretty much, yeah.

When the light is on a higher level and the cell is draining you can usually see that and you’ll know, but by shifting down to lower modes you don’t notice the dimming, so say it shifts down and you’re still fishing, still using the low to bait hooks and what not. The light stays on, you forget it’s on low by it’s own device and in the morning you find your cell at a shocking 2.1V. Oops! Some chargers will accept this, some won’t. An isolated occurrence like this shouldn’t do harm to the cell, but there ya go, it’s up to you to monitor it where true low voltage protection will shut the light off at a safe cell level.

It’s a plus in some cases, you don’t have total darkness without warning, but of course you’re supposed to stop and swap cells when it drops down… you DO have a spare with you, don’t you? :wink:

Spare cells?
Shoot, I got spare flashlights!
3 or 4 spare lights just in case.

Three generations of Convoy C8 flashlights

Gotta love em!

I’m betting on Simon having some new stuff for us, he’s alwys on top of things and seems to like lights as much as we do!

Take my money Simon, please! :smiley:

I agree with you Dale, i am always excited when i see something new from Convoy because: a) it is not going to cost an arm and a leg; b) it is going to be very good quality; c) when properly modded it is going to put to shame everything in that price range.

Anyways i do really like to see proper thrower from Convoy, not that the L2 or even the L6 when modded are bad but i do want something that can push 500kcd or even more :slight_smile:

I would love to see future lights start to be available with 20mm+ driver sizes. I have a project right now to try to modify a convoy C8 to fit the 20mm H1-A boost driver to run an XHP50.2.

Hello all, I am hoping I can get some help. When I compile the .c to .hex in avrstudio 5.0 it is successful. However when I try to write the flash to the attiny13 avrdude gives me an error (ERROR: address 0x0410 out of range at line 65) it then has the path to my .hex file. Can anyone please tell me what I am doing wrong?

Thank you!

EDIT: When I build the .hex file in atmelstudio 7.0 it gives an error stating the 1084 bytes 105.9% Full. What gives?

I’m not familiar with that error. But it might help to post it to the firmware howto thread. Plenty of firmware-knowledgeable folks watching that one.

In both cases, the .hex file is too big. You’re probably missing some compiler options, like -Os and -std=gnu99 , which tell it to optimize for size. See bin/build.sh for the full set of recommended compiler options.

its only SMO based L6 eqipped with a good dded S5 makes 500+k easy…yet its a chunky light and kinda heavy too…and the hotspot is only “hunting scope” worthy

What emitter do you mean ? And what driver/batteries etc setup ?