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.
the points are that Sc31pro driver haven’t regulated output, work with pwm and provide too much current for 3535 Leds at high modes. If I’m not wrong Sc21mini is regulated, no pwm and 1000lm max. Enought for lh351d or 519a powered by 18350 cell
I’m pretty sure the SC21 Pro driver is direct-drive as well. That small battery can’t provide a high enough current to damage the LED. Zeroair measured 2.5 A maximum.
Very much looking forward to seeing the results of getting Anduril 2 running on these!
As for regulated/non-regulated output. here’s my output measurement of the pro using ceilingbounce in case you missed it: Sofirn SC21 mini - #161 by Verodin
I haven’t kept up with Anduril firmware for all the various lights. Hence the if so part of my post.
Since it doesn’t seem to be Anduril 2, we will have to wait for someone to compile one. At least we know anduril.2021-08-31.sofirn-sp36-t1616.hex can be used to create an Anduril 2 firmware since Sofirn seemed to use their own version for this light
I think what SammysHP is trying to say is that Sofirn should be using anduril.2021-12-13.sofirn-sp36-t1616.hex since that is the latest official build of Anduril 2 that will work
gChart, any chance that you could design a Programming Key for the SC21 Pro? If I understand correctly, it only needs three pins, but the key has to be five pins wide: (GND) (VCC) (blank) (blank) (UPDI). Too bad Sofirn didn’t put them together so that your UPDI key could be used.