Nice Drdanke. I will definitely try making a rig like that soon.
Great tip Comfy. I've been using that same clip since I started flashing chips. It's still holding up well, but I do have to be very precise positioning it every time.
Nice Drdanke. I will definitely try making a rig like that soon.
Great tip Comfy. I've been using that same clip since I started flashing chips. It's still holding up well, but I do have to be very precise positioning it every time.
@drdanke
easy and simple, I like it.
If you add 2 more contact wires, for + and - and one emitter you will be able to flash and test the driver in matter of seconds
Very good idea. I have been meaning to make a complete external testing setup with an emitter on a heatsink, and having 2 contacts to test a driver right away would be sweet. I will definately work with that.
I had an idea to add battery and switch and make all that as a flashing/testing unit, just pop in the driver, flash, test -> not like -> reflash -> test and so on but…. I was to lazy to do that
Im totally with you on this one. It's amazing what JohnnyC and others can do on these drivers. Jon has a great head on those shoulders of his. Now I have to buy some more hosts and buy some of those drivers to put them in. Great work guys.
Thanks to all who have contributed and freely shared their code.
I’m anxious to try out the Star program.
Since others have commented on connection methods in this thread, I thought I’d share my method.
I purchased a pack of 12 mini pin grabbers from a fleabay seller, and they seem to work well on these driver boards - with one minor exception:you can’t attach them to adjacent pins on the Tiny13a (namely 5-6-7).
My solution was to solder a short stiff piece of wire to Vdd of one of the 7135’s (which are all connected to pin 6 of the Tiny13a). This provides an alternate connection point for pin 6 of the Atmel.
So…the mini pin grabbers easily connect to pins 1, 4, 5, & 7 on the Atmel, plus the additional “pin 6” on one of the 7135’s.
Works well for me-ymmv.
Kudos to JonnyC!
I like the Star1.1 firmware very, very much. IMHO - it is well written and well documented. Enough so, in fact, that a hack like myself was easily able to change a few things to better suit my personal preferences.
For instance, I changed the warning flashes to “soft” blinks instead of on/off blinks by changing the appropriate PWM=0 statements to PWM=13. Since I used PWM=15 for low mode, a value of 13 is still easily distinguishable as a warning flash.
I also changed the timing of the warning flashes from 250ms/500ms to 500ms/500ms.
I believe the soft blinks combined with equal dim/bright timing makes the light more usable while the warning is active. This is actually a lot like the warning Willie Hunt programmed into his LVR incandescant regulators many years ago (which is where I got the idea). Many of his regulators were used for bicycle lights, so an on/off warning flash might have been a bit unnerving when travelling at speed on a bike.
While I was at it, I changed the number of flashes announcing eminent shut-off from 10 to 20 to give a bit more time to react.
There are more changes I’d like to make to the low battery step-down and warning code, but I won’t go into that now.
The ability to customize the low battery and critical low battery points is rather nice.
I should mention that the code compiled perfectly using Atmel Studio 6.1 with no errors or warnings at all.
The only real downside I can see is that I now have several lights to tear apart so I can re-flash them
Thanks for sharing this with us!
Absolutely BRILLIANT!
How does ADC_LOW 130 and ADC_CRIT 120 translate into volt?
Well, from the luxdrv source, looks like 125 is 3.0v and 5 is 0.1v. I added comments as follows:
#define ADC_LOW 130 // When do we start ramping (3.1v)
#define ADC_CRIT 120 // When do we shut the light off (2.9v)
I've been working with the e-switch version. Added more comments, re-formatted the code a bit, moved all the configurable settings up top with the rest of the settings.
Possible Mod/Enhancement to the e-switch version:
I'm debating adding a 2-4 second time-out (maybe longer) to add a one click OFF. The way it would work is if the light is ON and no clicks for the configured time (2-4 secs roughly), one click turns the light OFF. This means the OFF time-out acts as a lock mode, so you can change modes all you want since turning the light ON, but if left idle, you no longer can change modes. Anyone else see an advantage to this?
Why not just assign some dedicated command for turning off? Double-click, for example?
It would requre adding another check after first click, of course (no click in, say, 0.3 seconds -> next mode; another short click -> off)
Could do that, but you would get the flicker of the temporary mode change (brighter). If you pause and wait to process the single-click to see if a double-click is coming, you introduce a response delay. Double-clicks are great when they simply continue, or feed off the single-click operation.
Then extra-long press (>1s) for off?
There’s a lot of options there, we just need to find the most convenient.
Well with the current design, as soon as a long press exceed 512 msecs, it acts on a long press action (mode decrement), so you have the same mode flash issue. Also, I would prefer one simple single click to turn it OFF.
I just want to say “Thanks” again to JonnyC (and anyone else who contributed to the Star1.1 code) for sharing this with the rest of us.
With a little more fiddling around today, I was easily able to customize it to provide exactly the functionality I’ve been looking for:
This code accommodates my needs (and my limited programming skills) quite nicely.
Sincerely, Thanks - again,
JW
Me Too! Thanks double JonnyC and RMM!! Just programmed my customized version of STAR Momentary into a ZY-T11 clone (here), UltraFire. Here's what I did:
So for me, I like the Idle Lock feature because with the quicker long press because:
The behavior is more like Dr Jones' lumodrv, but not exactly the same. Also the one-click-OFF feature is really nice with a higher numbers of modes, like 5 or 6.
If anyone is interested, I can publish the modified source code - let me know.
Other details of the mod build:
I can post it, somewhere, maybe on Google Driver like RMM did. But, I pm'ed JonnyC with a question/issue yesterday, waiting for a response. I'd like to get his response first to be sure the code is ok... Also I'd like to hear from RMM if this is ok to do?
Thanks JohnnyC and RMM sharing the code. Also, Tom E enrich the features of convenient option.
Please publish the code to let us the AVR dummies can learn and experience the new customized features.
Here is updated source code: https://drive.google.com/file/d/0B1IxYZuk4Djcc09STnlITjh5OW8/edit?usp=sharing
Few Notes: