I’m in need of help for a new-ish UI (unless somebody already has one that would work.) It is for an LEO, he wants a dual-switch light (traditional click-switch + e-switch). I just don’t know where to start. Is STAR dual-switch the best jumping point?
Yes, and by default you can toggle mode memory by entering config mode then turning it off between the second two blinks. Here’s a visual summary of the default interface:
STAR dual-switch is probably the best starting point. I haven’t attempted to make a dual-switch firmware, and I’m not aware of many which already exist. However, you’ll probably need to change a fair amount of the code to get the features you described.
If you don’t mind it resetting to the first mode each time, any e-switch firmware can be used on a dual-switch light. However, I doubt that’s desirable for what you described.
I think the memory parts should be relatively easy; mostly just copy and paste some code from other projects. It’s the UI changes which pose more of a challenge. E-switches need considerably more UI code than clicky switches.
If I skip the Beacon part it should be easy. Just start with STAR Momentary, add the memory bit, and change long press to mean strobe instead of reverse mode
Thank you ToyKeeper for hosting these shared FW’s.
I haven’t been keeping up with this area. Is there a place that has the UI’s and operating perimeters of the various FW’s and variations?
The closest thing is the repository index file, which is mostly intended for searching, not so much for reading. Beyond that, once you’ve found something compatible with your switch type and driver type, it’s mostly a matter of reading the text files included with the matching projects to figure out which ones sound best.
Is there any way to program the generic micros that look the same as the Atiny13A? I have seen these on some drivers before, but not ever tried to program one.
A generic SOIC8 chip could be anything. Attiny13 is only one of many chips which look like that, and each one works differently. The details probably vary for each type of chip.
Which should give me mode memory? Correct? But I still don’t seem to have it. I’m using a zener modded board could this be affecting it?
Also when I start again it gives me my lowest mode. Even in the second group it gives me my lowest of the first. It starts with the lowest of second group then after a second goes to lowest of first group then I can cycle through the modes on the second group like normal.
No, that only controls how that option gets configured. With CONFIG_STARS defined, you can enable mode memory by grounding pin 3. With it not defined, you can enable mode memory by pressing the switch a bunch of times and then turning it off between the second set of two blinks. Neither method turns it on by default.
If you want mode memory hardcoded as on, you’ll need to change some other part of the sources, or use tk-otc.c (which drops the config mode entirely in favor of hard-coding options, but provides more space to add features).
Yesterday I flashed my first driver (stacked 105C, 12x7135) with the S7 firmware, worked fine, very nice firmware. I used the ready to use .hex-file.
Today I wanted to try star_noinit. Therefore I had to create a hex file. I have to say I’m a total newbie to all of this flashing/coding stuff.
I have Atmel Studio 6.2 installed. Finally I’ve been able to get a hex file, but it’s 2685 bytes.
The way I did it was: file~~new>project-> GCC C ExecutableATtiny13A, then deleted that automatically created stuff, copied and pasted in the code,>projectproperties>toolchainOptimization(under AVR/GNU C Compiler)~~>optimize for size (Os), then build>build solution
I just installed AS6.2 without making any changes to whatever settings.
The hex file size isn’t so important; it’s the size of what the hex file represents.
I have .hex files at 2893 bytes which still fit. When I run avr-size on it, it tells me how big the file actually is, and that limit can go up to 1024 bytes. I’m not sure where to get the avr-size data in Atmel Studio though.
In blf-a6, how do I get the tactical strobe into the main loop? I see it is given 253 as a convenience code, but I can’t see anywhere that it’s actually used?
Can I just transplant the code I’ve used in STAR_OT?
//mode_idx254 is the Strobe Mode
if (modes[mode_idx]254) {
while (1) {
PWM_LVL = 255;
_delay_ms(50);
PWM_LVL=0;
_delay_ms(175);
Edit: Just gave it a try, all it takes is to put the convenience code into the normal mode order. easy as pie. Now i feel silly for flapping my lips before switching on my iron. :zipper_mouth_face:
Not sure what you and TK talked about, but that’s all that’s needed.
As it sits, and modes under pwm level 8 will use the 7135 channel only, and anything above 8 will use both the 7135 and the FET. (you’ll need to un-comment it [remove the // ])