Yes, I wanted to sweep any unnecessary stuff and give it a cleaner look. :)
Factory default temperature is always 45°C if I am not mistaken. gchart probably knows way better than me. ;) I like a safe level for default since those people who ask for higher temperature limits are often those who can handle a complex UI quite well.
Agreed, but I am afraid it could turn the cleaner look into something more confusing. Instead, my intention is to offer detailed (yet essential) explanations for each function in the text manual of SP10 Pro. This manual needs to be kept short for Sofirn will offer it in not less than eight different languages.
OMG, how did I miss the fact that there was no switch button LED?
I will ask Barry if they plan to use the SP35 / IF22(A) switch which has an LED in the button. If I recall correctly, the original switch in SP10S was often reported to be mediocre. So, let‘s wait and see what they are going to use here. In the worst case, I will remove that part from the UI diagram and manual.
About auto-lock…
Good question, never checked before. According to ToyKeeper‘s text manual, auto-lock is a part of the Advanced UI only but maybe timer-settings are also being propagated to Simple UI as well?
Yup, it looks like it would be a simple add. The question though is: should it’s inclusion be made it universal? or should it be a compile-time config option? TK clearly designed it to not autolock in Simple UI. So I would think if it’s going to be added in, it should be a compile flag. The setup of autolock would definitely still happen in Advanced UI, but I could see it’s config carrying over to Simple UI. (sorry, kinda thinking out loud there)
ToyKeeper/spaghetti-monster/anduril/off-mode.c
#ifdef USE_AUTOLOCK
// lock the light after being off for N minutes
#ifdef USE_SIMPLE_UI
if (! simple_ui_active) { // no auto-lock in Simple UI
#endif
uint16_t ticks = autolock_time * SLEEP_TICKS_PER_MINUTE;
if ((autolock_time > 0) && (arg > ticks)) {
set_state(lockout_state, 0);
}
#ifdef USE_SIMPLE_UI
}
#endif
#endif // ifdef USE_AUTOLOCK
to be honest, I fear that both Sofirn and some (many?) BLF members / customers would rather like Simple UI to be really „K.I.S.S.“ (keep it simple, stupid). Some “muggle“ users could get confused if their light locks out automatically. On the other hand, if auto-lock is not active in the factory defaults of the Advanced UI, it should not be of any concern.
How about a quick poll (1 week runtime) to see what people want most? I can ask Barry to hold on using the current firmware for there might be another one coming with auto-lock working in Simple UI, too.
Auto lock probably won’t be a good idea. Hand a light to grandparents and they’d just think it were broken. Anyone given a light in simple UI should be able to figure out how to use it immediately.
Even as an enthusiast and huge fan of Anduril - I agree, I think auto-lock should be kept out of the simple mode. But I also agree with the suggestion to put it to a poll.
Remember - auto lock would still have to be set up in advanced UI for it to carry over to simple UI. There would be no danger of someone accidentally enabling auto lock from within simple UI.
First off, no one is saying that Simple UI won’t have lockout. I think you might have misread something. What we’re talking about is auto-lock in Simple UI, which I feel will probably just get confusing and is why it was excluded from Simple UI in the first place. The normal lockout mechanism will still exist in SP10 Pro’s Simple UI, and is shown as such in Lux-Perpetua’s diagram.
Secondly, if you’re worried about Simple UI having a 150/150 ceiling, then perhaps the SP10 Pro isn’t for you. But I don’t think there’s anything dangerous about it. No one is getting burnt from an SP10. It has no higher output than the stock SP10S that Sofirn has now been selling for years. If anything, it is now safer since it will have thermal regulation.
> First off, no one is saying that Simple UI won’t have lockout. I think you might have misread something. What we’re talking about is auto-lock in Simple UI
got it, youre right, I misunderstood
> Secondly, if you’re worried about Simple UI having a 150/150 ceiling, then perhaps the SP10 Pro isn’t for you.
youre right again,
I keep thinking the SP10 will have the same 150/150 of 1200 lumens on LiIon, like the FWAA
youve reminded me we covered this before,
and I concluded the Eneloop option in the SP10 PRO will eliminate any Fear of Turbo…
As far as I know there is only one readily available, user friendly Anduril flashing solution on the market: Hank’s adapter set with pogo pins. Can we please make this light compatible with it?
I know, maker have their own preference and opinion on how the pins should be arranged and some offer designs to make PCBs and solder pogo pins and all that, but for the average user that is not worth the hustle in my opinion. So, please, make it compatible with the only flashing solution that s readily available.