@Tom E
It worked now!
avrdude done. Thank you. 
priest77 did it install correctly?
Yes, now I have STARSTROBE1.0.c on my UF-T20.
I’ve tried to add STROBE as additional mode but it seems there is no room for it, I’ve got something like 100.2 % Memory Overflow.
Then I’ve just changed the Medium mode value to 254 and put it to be the last one, and I am using it like that.
Oh…make us a video it in operation please
This is the order I have:
Here is the video:
Is there any way to make STROBE some kind hidden?
You know you can change it so moon is default on so you dont need to have the star soldered, that makes it so you dont have so unsolder it every time you want to reflash.
this is the code to set it to default moon on (you can ignore my added comments, its so I remember what I change stuff from)
#ifdef MODE_MOON
if ((PINB & (1 << STAR2_PIN))> 0) { // Stock is ==, ( > for moon default to on, soldering star will disable moon)
modes[mode_cnt] = MODE_MOON;
}
There is no way that I know to make modes not in the normal cycle but if you change to memory off you wouldnt have to cycle threw it every time.
Thanks! That was giving me headache at the beginning I was trying to flash it with the star soldered…
This is much better than soldering and unsoldering every time.
Just noticed it changed that to a smiley, if you got quote my reply you can copy it from there correctly.
Add an extra space between the > and the ) otherwise it thinks you want a smiley
I’ve done it with “quote”
How can I disable the turbo time out? Should I just comment out #define TURBO_TIMEOUT ?
Yes
Just add // in front of the line then compile the .hex
Thanks for your reply.
The turbo_timeout can not be disable only by comment out the line. My build failed with this error.
…/STAR_V11.c:205:22: error: ‘TURBO_TIMEOUT’ undeclared (first use in this function)
You need to comment out the turbo mode, not the turbo_timeout.
Microa, “timeout” is part of the turbo concept. I don’t see why you would want a “turbo” mode if it did not have a timeout. I suspect that you just need a “high” mode.
In order to do that, simply comment out:
#define MODE_TURBO
When MODE_TURBO is not defined the compiler will skip any sections relating to a turbo timeout due to conditional statements (#ifdef MODE_TURBO). Simply set High to your desired maximum brightness, probably 255.
Oh! I see. Thanks a lot.
I have a few lights with drivers that have STAR firmware and have noticed on one of them I get a small quick flicker about every 4 to 5 seconds. As the interval is constant I’d assume it’s something written in the code? If so, what is it? If not, this is not the right thread for this question and I’ll post it elsewhere.
Note: I haven’t switched the battery or tried the battery in another light (if it has something to do with voltage monitoring). Will test it in other lights with identical driver with same firmware tonight.
Ditto…I am beginning to think there might be “problems” with some 7135’s that are being assembled in drivers…one driver same exact firmware…no flash, soldered in, the one right next to it…flickers
Other people have been complaining about that flickering too
We are talking about Chinese IC’s remember, what is to say they didn’t buy a HUGE lot of defects and just start slapping em in.
Google “AMC7135 flickers” about 8 hits on the first page from many different forums
Thanks for the tip, I’ll do some research. As it does not appear to be a feature within the code I will discontinue discussing it in this thread.