Thank you. -This is already Anduril 2 as far as I can see from disassembling and analyzing the file. But it’s a very early build. I guess it’s a development build from gchart with a SP36-like configuration as the tinyavr port was merged much later.
Very interesting. It acts so much like Anduril 1. No simple mode and 4C from on goes into ramp config. Is this consistent with early builds of Anduril 2?
This entire time I’ve been trying anduril.2021-12-13.sofirn-sp36-t1616.hex and getting the slow ramping, but I just tried anduril.2021-08-31.sofirn-sp36-t1616.hex and it works!!
Also, I recall the mid-ramp flash was intentionally programmed in. It is intended to alert the user when switching channels.
If you are comfortable with coding and compiling, you can probably edit the flash or flashes in the ramp out of any version of Anduril 1 or 2.
Personally, I agree that a smooth ramp without any flashes is best. The only point of knowing when you’re switching channels would be to get an idea of when efficiency drops as you go to FET. With that knowledge you could fine-tune your output to stop just before you hit that point. However, in practice this does not work as the default ramp speed of 2 seconds is far too fast to provide any meaningful fine-tuning around channel switches.
Another update: I’ve been specifying “-m flash” when erasing the MCU before writing and I thing this caused some settings from Anduril 1 to be saved in eeprom or something like that.
I flashed anduril.2021-12-13.sofirn-sp36-t1616.hex again and then immediately did a factory reset and now everything works as expected.
I have zero clue how to code, compile, and reflash… Im sure I could learn… given sufficient coaching
thanks for the link…
I have this programmer from gchart, for the SP10… but I sold the light before I got the programmer, so I have not used it. (I may get another SP10, but meanwhile I got the SC21… )
I do think I have all the software… gchart spent a lot of time coaching me and linking me to all the stuff with unfamiliar names like Python, Pip and PymCuProg… And I learned to use the Terminal in my iMac… Im expanding my vocabulary, but have not tried to connect the programmer to any flashlight yet…
I think my first question is where do I put the pins
but Im sure there are other considerations Im too ignorant to ask about… lol
Im willing to follow directions, if I may impose on your time
If you already have everything installed, then it’s not overly difficult. However, the pogo dongle for the SP10 Pro will not work on this light since it uses a different layout. You will either need to make your own dongle or solder wires directly to the board. But that programmer will work just fine
Here’s the gist of it:
1. wire up the programmer to the light:
pin2 => GND
pin6 => VCC
pin1 => TX/RX (depending on the programmer, you might need a 1kOhm resistor between TX and pin1)
2. figure out what your programmer is called on your system
mine was /dev/tty.usbserial-1420 but yours might be different
Edit: oops, I replied without checking for thread updates first. Glad it’s working!
Fuses are still a thing, but most of the settings can be done in firmware and don’t need manually setting if fuses. BOD (brown out detection) is an exception, but that wouldn’t affect ramp speed.
My thread here has some info on doing fuses with pymcuprog.
Could you try my hex file here I would check your tk-attiny.h file too. At some point I changed between 5 MHz clock and 10 MHz, so it’s possible that it might be using an old setting.