Custom SkyRay King SRK Driver

I just put in some hooks for the user to program their desired modes… if the button is pressed when power is applied to the light, it will erase the current configuration to the default and enter programming mode (indicated by three blinks). You then click through the default mode list to the desired mode and hold the button down for a second to store the mode. Repeat the mode selections for the modes you want then power down the light (loosen the tailcap) to exit programming mode.

I’m in too, if selling.

I'll finally get a SRK if you'll sell me this driver.

great work texaspyro

Im also try to do pcb layout 7135 based driver (used Tiny13A instead of 85)
sadly pcb manufacturing company here quoted me a cost which was higher than price of SRK

idea:
its better if you can add input capacitor and output capacitors (3)
new 7135 datasheet has input cap and another one between ground and output

Try OSHPARK.COM and Seeedstudio’s Fusion PC board services. OSHPARK will make you three boards for $5 a square inch ($1.67 per square inch per board). Price includes shipping(at least in the US).

Seedstudio is a bit less, but you need to buy more buy more boards.

I have the user mode programming code working.

You can set up the mode list in any order that you want (OK, the first mode is always set to OFF) and include any of the standard levels (currently moon, 10, 25, 50, 100) and patterns. The mode list is stored in EEPROM and is maintained between battery changes.

Sweeeeet…

BTW, moon mode on a SRK could be 50 lumens or so…

How low do you think moon mode could go?

Unknown at this time… AMC7135 chips require a certain minimum pulse width to turn on. At 15 kHz PWM, this is around 1.5-2% of the full PWM range. That produces a very dim output. Couple that with the capacitive load of driving 24 chips and you may need to boost the PWM some more to get the LEDs to light up. The minimum setting might vary depending up the LEDs and AMC7135 chips that are used. A setting that just lights one light could put 50 lumens out another one.

Once you get the width wide enough to turn on the LEDs, each PWM step should increase the output around 10-12 lumens.

I’m in for one if these become available

I was tempted to ask you for you a low moon mode, but it might be better to handle this with the ramping mode you're already planning on doing. It could start ramping at crazy low levels that might just barely light up one LED. That would be good enough if there's mode memory or if it's user programmable. Hell, I don't think I'd even care if you share the code. It'd finally motivate me to buy the tools to program the chips, and I could tweak your program to suit my needs perfectly. You're putting in a lot of special code though, so I would understand if you wanted to keep it to yourself.

I should buy three :slight_smile:

@texaspyro: How about turning on single LED for moonmode if there are individually addressed.

I have few to add

-Leads for MCU for easy programming if the real estate permits.
-Individually addressed AMC7135(guess it requires more than a double layer PCB and a different MCU)
-Individually addressed LED modes(also used for status).

I also wanted to suggest individually addressed LEDs like niteye E30-E40 has for low modes if it is poseable and leads from mcu for one smd led that could be mounted near the switch and used as status indicator led like with P25/TM26/EA4 etc.

But, I don't get the idea of ultra low "moon" modes, those are just unusable for me, minimal amount of lumens that I find usable are about 80-100lm, for anything less than that you could just use:

Nice work. Looks like it will be a real winner. I hoping that you’ll be selling these boards and and MCU’s. Wishing you the best of success on this endeavor.

Very nice I'd like one, too :)

C1, 1k and 8k3 are the voltage divider for battery monitoring?

Awesome work texaspyro! I might have to consider one of these too!

me want. at least just the board and some code. i have an avr programmer and can even source my own parts.

Yes. The values were chosen so that if I sum 10 ADC samples, the resulting value (plus a calibration offset value) is the battery voltage in millivolts. The voltage divider is driven by a processor pin (not directly off the battery) so that it can be turned off when not actually measuring the battery voltage… considerably reduces the driver parasitic drain.

Not enough pins on the processor for addressable LEDs…

There is a pin on the processor that is used to power strobe the battery voltage divider. It blips every 0.25 seconds when the light is off and at 60 Hz when it is on. One might be able to cobble a status LED onto that pin. I don’t know if the pulse width is wide enough to be visible…

It is rather difficult in the ramping modes to stop at the setting that is moon mode… the next tick up would be another 10 lumens. There are now two ramping modes available. Slow mode ramps up/down over 4 seconds and includes every available PWM value. Fast mode takes two seconds and skips every other PWM value.