TheStar - BLF driver firmware for a GB light - What options do you want to be selectable by stars?

Buy / Sell BudgetLightForum Deal Alerts
42

I don’t know about anyone else, but I like my beacons rather dim… like, on-time of 1ms and then off-time of 1999ms. Just so I can find the thing in the dark, mostly.

As for strobes, I’ve never used or needed a SOS. However, a high-visibility flasher can be useful for biking or signalling for assistance. The best ones I’ve seen stay on at a low mode and flash quickly a few times every second or so. Like, maybe run at ‘low’ or ‘low low’ and then quickly flash three times at ‘high’ or ‘turbo’, with a timing such as: 10ms high, 35ms low, 10ms high, 35ms low, 10ms high, 900ms low, repeat.

I might make a red one like that for the back side of my bike. I think 700mA through a red XP-E should work, alternating between ~3 and ~30 lumens. That would give me like 15 hours of run time from a 16340 battery, but it might be a little too bright so I’ll have to try it and find out.

43

got linkies for the conductive paint sir…that does sound very ingenious for sure!

44

This ^

45

May I ask why are you so eager to disable the turbo timeout? IMHO the timeout is really good to have because of the following reasons:

1. Not easily noticeable: In a XM-L2 based light, step down from 3A to 2A can't be easily noticed by eye (without comparing to 3A light side by side)

2. Protect the light from over heating (especially if modded to 4A, but useful also at 3A)

3. Saves batteries: Step down to 2A gives you 50% more runtime (compared to 3A)

Other than that, the current test version of TheStar FW supports your needs:

- Change mode order (L->H is on by default, H->L by shorting the star #3)

- Disable moonlight (yes, removed from main modes cycle by default - for this GB light - still accessible as the first hidden mode)

All in all, the current version supports quite many different needs:

1. Normal modes: L->M->T or T->M->L, with or without memory []

2. LL available if/when needed, but not in the main mode cycle (first hidden mode) []

3. Turbo without timer available if/when needed (as last hidden mode) []

4. Hidden blinky modes: Strobe, SOS, 1s Beacon (or Strobe, 1s Beacon, 10s Alpine Distress Beacon) []

5. Also hidden modes memorised (if memory enabled) []

+ Extra: Single mode config: Turbo (with hidden goodies) []

(can be replaced with Tacticool config: Strobe->Turbo->Low, without memory, only 0.5s time to change modes - but only if majority wants so!)


Are there still some useful configurations, which can't be catered with this FW?

Edit: Does anyone want to try out this FW (= help me in testing it)?

46

I agree with all that _the_ stated in the above post.

I've tried out version 0.1 and have say to the turbo timeout is my favorite. Even when I time it and watch it happen, it's very difficult to detect. I did verify that it works with a DMM.

_the_, thank you for sending me v0.2. I haven't had a chance to put it in an light and run it though it's paces yet, but the changes you made sound real good.

47

I’d love to try it… but the attiny-flashing tools I ordered still aren’t here, even though the post office marked the package as “delivered” two days ago. I’ll have to have a word with them about that…

48

Just want to point out why this build but based on off-time wouldn’t work.

Very simple actually; memory isnt selectable by star! It can only be changed in the coding (the additional cap is a valid point too).

_ the_ I have v01 installed in a pair of P60’s that I’ve loaned out to some folks, its fair week and we have several of our horses up there and have different lesson kids (and a few adults) using them and they need to be able to work on stuff / access the barns at night but there are no internal lights so they’re getting a lot of use and people seem to like them. I also have one other P60 loaner light up there [with one of my custom versions of Off-time] and from the people that have used both they do like the off-time better but they cant describe why (its obvious whats different to us but not to muggles) and there are no complaints about this version, they like the hidden strobes and stuff to play with.

Once I get them back I’ll be flashing v02

49

I have had the pleasure of trying the v03 and it is amazing, I love all the functions, the strobe and beacon accesible in the second cycle mode switches. The turbo timeout is really very good, I liked it because as ImA4Wheelr says is hard to see the decrease in output power.

I do not know the changes that will have the final version but this version seems very good. Thank the his great work he is doing in this driver firmware!

50

I use a pencil to connect stars... even easier to remove, just use the other end of the pencil, assuming you have a deluxe model with an eraser installed. Only costs $0.02 vs. $10+ for a conductive paint pen + thinner. No inhaling paint thinner, either. Can easily be done in the field, keep a pencil in your car, pocket, briefcase, even borrow a pencil most places. And you never have to sit around watching paint dry.

51

Thank you all for your valuable input!

The current version of the FW contains the following modes:
- LowLow (only in 4-mode config - GB light will most probably be 3-mode, but I have this 4-mode for my smaller lights)
- Low
- Med
- Turbo (step down after 2min to ~half of the max power)
—-Hidden Modes—-
- LowLow (only in 3-mode config)
- Strobe (randomly alternating between 8.5-16.5Hz)
- 1s Beacon with 10% background light (50ms blink, 950ms bg)
- 2.5s Slow beacon with 10% background light
- 1s Beacon (without any background light to save battery in case of emergency)’
- Alpine Distress Beacon (6 blinks with 10s delays + 60s delay)
- SOS
- Turbo that stays on

Additional goodies:
- Single mode turbo, with timer (+ hidden modes) (connect star #2)
- Tactical mode: Strobe, Turbo, Low – 0.5s time to switch modes, without memory (+ hidden modes) (connect stars #2 & #4)
- Change mode order, connect star #3
- Disable memory, connect star #4

..and of course it has high PWM and features low voltage protection as it has done from the beginning.

I’m pretty happy with it so far, but keep finding “nice to have” things or possible enhancements all the time.. Well.. All software developers are perfectionists..

52

Damn, that's a whole lot of stuff you managed to cram into a Attiny13a. Sounds great.

_the_ wrote:

The current version of the FW contains the following modes:
- LowLow (only in 4-mode config - GB light will most probably be 3-mode, but I have this 4-mode for my smaller lights)
- Low
- Med
- Turbo (step down after 2min to ~half of the max power)
—-Hidden Modes—-
- LowLow (only in 3-mode config)
- Strobe (randomly alternating between 8.5-16.5Hz)
- 1s Beacon with 10% background light (50ms blink, 950ms bg)
- 2.5s Slow beacon with 10% background light
- 1s Beacon (without any background light to save battery in case of emergency)’
- Alpine Distress Beacon (6 blinks with 10s delays + 60s delay)
- SOS
- Turbo that stays on

Additional goodies:
- Single mode turbo, with timer (+ hidden modes) (connect star #2)
- Tactical mode: Strobe, Turbo, Low – 0.5s time to switch modes, without memory (+ hidden modes) (connect stars #2 & #4)
- Change mode order, connect star #3
- Disable memory, connect star #4

..and of course it has high PWM and features low voltage protection as it has done from the beginning.

I’m pretty happy with it so far, but keep finding “nice to have” things or possible enhancements all the time.. Well.. All software developers are perfectionists..

Thank you all for your valuable input!

The current version of the FW contains the following modes:
- LowLow (only in 4-mode config - GB light will most probably be 3-mode, but I have this 4-mode for my smaller lights)
- Low
- Med
- Turbo (step down after 2min to ~half of the max power)
—-Hidden Modes—-
- LowLow (only in 3-mode config)
- Strobe (randomly alternating between 8.5-16.5Hz)
- 1s Beacon with 10% background light (50ms blink, 950ms bg)
- 2.5s Slow beacon with 10% background light
- 1s Beacon (without any background light to save battery in case of emergency)’
- Alpine Distress Beacon (6 blinks with 10s delays + 60s delay)
- SOS
- Turbo that stays on

Additional goodies:
- Single mode turbo, with timer (+ hidden modes) (connect star #2)
- Tactical mode: Strobe, Turbo, Low – 0.5s time to switch modes, without memory (+ hidden modes) (connect stars #2 & #4)
- Change mode order, connect star #3
- Disable memory, connect star #4

..and of course it has high PWM and features low voltage protection as it has done from the beginning.

I’m pretty happy with it so far, but keep finding “nice to have” things or possible enhancements all the time.. Well.. All software developers are perfectionists..

53

Wow! That is great. The strobe rates are supported by data from Grizzlyb out of Amsterdam and 7 or 8 years of research and field use of strobe lights to subdue individuals without escalating violence. The point light source does not induce seizures, but is disorienting to light source. So person trying to hit you can’t tell if you are 6 inches away or 3 feet away and when they put their hand up to shield their eyes they provide a wrist to grasp and place in a submission hold. Very nice in my line of work as most hospitals frown on the staff striking patients and we staff don’t like being struck.

54

Well. I'm well aware of Grizzlyb's research, but actually both of the alternating frequencies (especially the lower) are below Grizzlyb's recommendation (18-20Hz). I tried multiple different 18-20Hz strobes, but found them be significantly less disorienting. Maybe my eyes are damaged by too many bad budget lights, but 18-20Hz looks more like a bad PWM than a real strobe.. ;)

Grizzlyb's main finding is that 18-20Hz strobes are "still extremely disorienting", but have "less unwanted side effects" (for LEO: meaning that the opponent can't move his hand without LEO noticing it, unlike with 10Hz strobes).

As the frequencies are alternating (pseudo) randomly, the unwanted side effects are less than with normal constant 10Hz strobe.

So, the frequencies in TheStar driver are chosen based on lots of research and my own opinions. I may want to come back to this and continue tests with higher frequencies.. Maybe with lower duty cycles.. Let's see.

55

Can I assume that this is for use with a clickie switch? If so how can I get some of these or can we download the firmware?

56

Yes, for standard clickie switch.

The firmware is still on development. v0.7 is being tested by couple of volunteers (Thank you for helping me with this! You know who you are.. ;))

I can send the .hex file to you by email if you happen to be interested in helping in the testing. :)

57

Writing you a PM now.

58

With regard to the strobe that most don’t use, for those that use it to grapple with violent people, Grizzlyb wrote in their research and findings that strobe rates of 8-12 Hz were effective, the assailant was also able to move without giving the officers enough time to react so they chose a higher rate of about 18-20 Hz if memory serves me correctly. Strobe use by Grizzlyb

59

You remember right. I have been reading and re-reading that thread during the last two weeks. Very informative stuff, and totally worth reading, but not the whole truth.. They didn't test different duty cycles at all, and at least in my opinion that affects the characteristics of the strobe a lot.

60

Thanks. That wasn't easy, at all.. I spent days and nights basically thinking where to squeeze away 2 or 4 bytes, trying that in practice, noticing that the compiler had already optimized that part for me, moving to next spot, etc. Usually after adding a new feature or enhancing something I was left at 1028 or 1040 bytes (limit is 1024 bytes) and spent literally hours refactoring the code to fit in to the memory limits. (Luckily I know something about C.. ;))

61

Oh, yes, I know what you are talking about…