Thank you Tom E for sharing your latest WIP. I as hoping to install and try it out this weekend but things came up. Hopefully, I will by the end of the week.
Ok, no prob. Couply of things for you and T_K (anyone else for that matter) on eswitch_NOINIT:
e-switch and power button share the same mode table, default is 5 modes with 1st 3 modes using the 7135
strobe is not accessible from the power switch - it's not in the table, special only for the e-switch
changing modes on the e-switch does not effect the stored mode, so the power switch saved mode is unaffected. I'm not sure if this is a good thing or bad thing, might be more confusing, but seems nice for some usages like tactical - you can program the power button to come up in Hi/turbo if you want, then change modes from the tail, and that will set a new default, including OFF. For now, I'm gonna leave it this way but not sure if this is the best. Might make a nice user configurable option.
I'm also thinking about more functionality, like using the long press to get strobe now, but treat is as an advanced mode set, so another long hold might be battery check, slow strobe, beacons, etc. A good thing I could do, for safety, is if the e-switch is permanently stuck, I could cycle thru the advanced modes and end it with OFF.
We use Git @work, but we have our own server repository. Been using github, but not for my own stuff. I know, really should... I gotta get better organized, overall. I'm off in way too many directions.
I really need to spend some serious time with git. It’s functionally almost identical to bzr, but everything has different names and options and defaults. And git officially won the DVCS wars, so I should get on board with it. Even Launchpad supports it now, though it’s not widely used there yet.
That’s a good point. It might be a good idea to add a “noinit” attribute to the timer variable, and only set it to zero on boot if the offtime capacitor (or noinit-based offtime sensor) says it was a long press. This would allow the timer to keep counting after a short press or brief interruption.
RMM - yes this the timer on this light had been working. Since I posted yesterday it has failed once again. I’ll test again today to see if it continues to fail.
Toy - as always thanks for the suggestion. I may reach out for a bit of clarification on the specifics of implementing this.
Hi. I am building a driver fet + 7135. I want to flash the firmware of toykeeper blf a6. I want to achieve around 100 lumens on low mode using the 7135 but i don’t have equipment to measure the lumens. Anyone knows what value should should i put ex. 150/255?
Ok, so according to Match, you get 100 lumens at around 200ma. He tested a T6, but lets assume that the extra gain from the U2 is cancelled out by losses in the lens and reflector.
So 200ma/380ma*255pwm = 134pwm. That should get you close.
That emitter, at 350mA, should put out about 140 or 150 OTF lumens. So, for 100 lumens you’ll want the 7135 chip running at about 69%, or about 175/255.
This is a very rough guess though.
You can get the PWM levels from bin/level_calc.py, if you have the ability to run python scripts. For example, this calculates 9 evenly-spaced levels from 0.5 lm to 1400 lm on a FET+1 driver:
Do I understand correctly, the only way to get mode reversing is with a light built around a momentary switch? So a partial press of a tail cap switch will not work to reverse? Please explain this if you can… I am trying to get reversing on a 105c.
I have compiled and flashed standard Star and it does not seem to back up…