Thanks!
Iāll keep fiddling with AmtelStudio. Iāll report back if I end up with a successful build.
Thanks!
Iāll keep fiddling with AmtelStudio. Iāll report back if I end up with a successful build.
Iāve had some success getting closer to a build!
Turns out I mixed up some header files and somehow got an anduril.c file filled with XML code. :person_facepalming: No wonder it looked so different!
At this point Iām getting an error indicating that āregion ātextā overflowed by 154 bytesā when attempting a build for the Q8.
The only changes Iāve made were to comment out the blinks at ramp floor, ramp ceiling, and channel boundaries.
I had that same āregion ātextā ā¦ā error when trying to compile Narsil a few months ago. If I recall, changing the configuration from ādebugā to āreleaseā solved the problem. Must be some strange accidental modification in the config manager. Perhaps debug isnāt using any optimization?
FWIW, Iām also having trouble building Anduril in Atmel Studio 7. I might be overlooking something obvious, but I have all of the dependencies in place, and the only change I made for this first test was a #define for the hardware type.
All the settings I use are in the bin/build-85.sh script. In theory, it should work by plugging those values into Atmel Studio, but Iām not sure where it puts them.
Exactly, and particularly no size optimation in stock configuration. This is the purpose of debug mode.
Success! My Q8 is happily running Candle Mode in celebration. :partying_face: Thanks for the tip!
Thanks again to ToyKeeper for the excellent AndĆŗril UI, and for the ongoing improvements and tech support. :+1:
When flashing the Emisar D1 and D1S, should I use the ā#define FSM_EMISAR_D4_DRIVERā line? How about on an EagleEye X6R running a Texas Avenger driver and single emitter? I think the version of AndĆŗril Iām running on them now predates the driver options.
Iāll wait to reflash my D4 until you are more confident in the thermal regulation.
Looks like all of those settings match what AS7 is doing already, but there are a lot of errors to sift through. Something tells me my linker is missing some random flag, etc. The strange part is that Iāve been able to compile all of your other firmwares that Iāve tried straight OOTB. Iāll have to dig a little deeper later on, but in the meantime the Q8 *.hex works great! I really like that anyone who picks it up can intuitively use the light, but more interesting features are hidden. A very nice analogue to Bistroās Muggle Mode.
No problem!
The D4, D1, D1S, and D4Ti all use the same driver. The #define for the D4 will work for all of them. The TA uses 3 power channels, so the #define for the FW3A might work.
Edit: formatting
AndĆŗrilās five-click Momentary mode is awesome, especially because you canāt exit accidentally. I use it frequently on my Emisars and Q8s.
Last September, ToyKeeper added dual-switch support to AndĆŗril. Iāve generally avoided dual-switch lights, but AndĆŗril makes them awesome.
Itās been working great on my EagleEye X6R with a forward-clicky tailswitch and a TA driver piggybacked onto the stock driver PCB.
I hike with a floody headlamp on and a small thrower at the ready. Momentary is perfect for identifying trail markers, landmarks, and the sources of spooky noises.
With two switches, momentary brightness can be adjusted on the fly instead of exiting momentary, changing the output level, and re-entering momentary.
Activating the tailswitch while holding the e-switch overrides memory and turns the light on in moon.
Iāve noticed that the indicator LED on my Q8 doesnāt illuminate while the light is off in momentary mode.
Should momentary share the indicator LED setting for lockout?
BTW, Candle Mode is very convincing! Iāve been enjoying it on a Q8 with a yellow spray-paint cap acting as a diffuser.
Thatās a good question. Should momentary use the same setting as lockout? Would it bother the tactical crowd to have a glowing button interfering with their stealth in momentary blast mode?
TBH, I donāt know who uses momentary mode or what their needs are, so any light people can shed on the topic would be helpful.
Hmm, I hadnāt considered that.
Iāve used momentary for light painting, where an indicator would actually be a bad thing.
I often use momentary on a second light while hiking with a floody headlamp.
I sometimes enable momentary when lending lights to young users. I can set the output based on the situation, and it prevents a light from being left on unattended. Kids seem to enjoy āmanual strobe.ā :laughing:
Perhaps there could be separate indicator settings for:
This is getting out of hand pretty quickly. The indicator config would need its own UI diagram. I think you also mentioned the possibility of a blinking/breathing indicator at some pointā¦
OTOH, Iād be happy with indicator settings for just two states, main emitters on and main emitters off.
ToyKeeper, I am loving Candle mode! I keep a Q8 with a diffuser burning on the coffee table in the evenings.
Would it be possible to add a sleep timer to Candle mode? Iād love to use it on my nightstand and while camping.
Ideally, it would retain brightness adjustment and run for an hour before simply āburning out,ā rather than dimming gradually like Sunset.
Perhaps it could be named Votive, Tealight, or CandleStub?
Hmmā¦ timed candle mode might be interesting. It wouldnāt be easy to make it dim over time, since it fluctuates across a fairly wide range and the low end doesnāt have sufficient resolution, but it could still stop more abruptly after a while.
The main difficulty there is just whether to spend the extra bytes or not.
Perhaps I could refactor some code to make all config-type modes use a single function and thus be smaller overall. This would free up space and reduce the cost of making modes configurable. Probably not today, but Iāll put it on the listā¦
Yes, abruptly āburning outā is what I was thinking.
I meant itād be neat to retain Candle modeās adjustable flame brightness without interfering with the countdown.
Iād be the envy of the camp with a diffused light hanging over my hammock burning Candle mode with a sleep timer.
Great! Can we have a peek at what else is on your list? :partying_face:
Aw geez. I have so many listsā¦ Um. Letās see. At least part of it is visible. And at least some of whatās visible is published. To see that part, check āanduril.txtā in the repository, which was initially a todo list but is now mostly doneā¦ Also, try āegrep āTODO|FIXMEā anduril.c
ā to see some other itemsā¦
But I also have a variety of other lists which arenāt public. So many, in fact, that I wrote an aggregator system to merge the entire hierarchy together into a single flattened list with scores and priorities and recurring due dates and even a snooze button. Itās called āTKDOā.
And then another aggregator to merge that together with some other systems and data sources, to boil it all down to a single number plus some randomized convenience hints about what sorts of productive things I could be doing right now. That one is called, um, something I canāt say here without violating profanity rules. Letās call it a āscrewometerā since the number shows, in percent, how āscrewedā I am. It even graphs the status over time.
The graph is a relatively recent addition, so it hasnāt had time to populate much history, and Iām still tweaking the factors and coefficients, but hereās a sample of the past 24 hours:
Lower is better. If itās dropping, that means Iām getting stuff done. If itās rising, that means Iām probably either slacking or asleep or doing something it canāt automatically measure. Currently rising since Iām chatting on BLF.
This may have all scrolled off by the time anyone sees this post (edit: nevermind, I linked to a frozen copy instead of a live version), but at the moment it shows me a graph starting at about 38, which then drops to about 20, then rises again to 34% or so. Then it starts dropping again but hasnāt gone far yet. This suggests that I got stuff done yesterday, tasks piled up while I was asleep, and now Iām starting again. But todayās peak is lower than yesterdayās, which means Iām doing something right.
If things go well, Iām hoping to build a USB nixie-style clock I can use to display the current number and trendā¦ but for now Iāve got it displaying on an old 20x4 LCD, the same one I wrote LCDproc for back in the 90s. I donāt have a serial port any more though, so I kinda hacked together a couple of AVR reflashing cables plus some floating wires to give the display power and data. Still havenāt figured out exactly why itās getting inverted and bitshifted data, but I can work around that (ā1 + (254 - (byte << 1))
ā) until a proper usb-serial adapter shows up.
Is this enough of a peek?
I just took a moment to contemplate the stacks and stacks of paperwork and books and techno-toys and Post-It notes and tools and electronic parts in this room.
Whenever something new arrives, it lands on top, then gradually settles to its natural depth within the geological strata as I pull more interesting things out from lower down and put them on top instead. Visitors can assess my priorities by noting that the books, parts and techno-toys are normally on top.
[performs an ironic bow, as from one engineer to another ]
Ah cool, I didnāt realize this existedā¦ I had started fooling with stock D4 firmware for fun. Iāll have to try switching anduril as starting point.
Not super interesting or anyting, but I dunno I find UIs interesting so:
Presets: LOW/NORMAL/HIGH/TURBO
No auto-saved mode-memory but LOW/NORMAL/HIGH levels can all be explictly saved.
From off:
LongPress -> Turn on at LOW and rampā¦
Click -> Turn on at NORMAL.
Click-Press -> Momentary TURBO while Press is held, then back to off.
Click-Click -> Turn on to HIGH.
From on:
Click -> Turn off.
LongPress -> Ramp up.
Click-Press -> Momentary TURBO while Press is held, then back previous level.
Click-Click -> Jump to HIGH unless in HIGH then jump to NORMAL.
Click-Click-Press -> Jump to LOW and ramp.
Click-Click-Click -> Save current level to active preset.
(Comparing master...RampingPresets Ā· bexamous/flashlight-firmware Ā· GitHub)
Iām starting to sound like a broken record, but AndĆŗril is, by far, my favorite UI.
Your UI looks good. I like the momentary turbo while on.
Be sure to also check out TKās DarkHorse UI, a clone of the Zebralight UI.
Quite! :partying_face:
Please share photos of your Nixie project when you get to it!