Wow, thats great, thank you so much! And I love where the source is uploaded, I can look at the previous srandard and those changes side by side!
Seeing where you added 8C along with 10C is cool, I now understand a bit more how that is defined.
I think I do indeed need it backported, since there is no Hex marked for a SC31 Pro, or the SP10 Pro, unless I missed something… and as far as I can tell neither supports multi channel?
Forgive me, a lot of this makes perfect sense to me, but then a lot is still beyond me.
BTW, is there a list somewhere of what lights currently do support the multi-channel branch? Or visa versa, modeks the branch supports? (Not sure which is more accurate way of looking at it)
I’ll use the difference I see on the SP10 as a reason to dig around and compare code/config files… Boyh lights were bought in Sept. Last year, so its not new new, but it does have some other newer feature differences to my SC31. (For instance the sc31 didn’t have 3C to unlock to off, but the SP10 does. ) I should have checked the version on both when I had them, and compared. Be interesting to see how the new SC31 I just ordered acts in comparison.
You are totally correct, I forgot to mentioned it because this always necessary in Unix if the folder with the build-all.sh is not contained in the path variable…
I have both a laptop that runs Ubuntu as well as a Virtual Machine that runs in Vmware Workstation on my Windows PC. The sucky part is my Windows PC just died today, I think the motherboard failed. Its over 10yo so its time to build a new one anyway. At least I have the firmware setup on the Linux laptop too. I mainly use my Windows PC and also use Windows at work, but sometimes I like to use Linux for things.
I guess I even have to thank the seller who sold me the “fake” SC21 Pro, I mean it was mentioned as Anduril2, it’s supposed to be Anduril2. turned out to be Anduril1.
so I was kinda mad but nothing could really be done about it (except reflashing?).
That was one of the the reasons that has motivated me to learn reflashing.
Beside the SC21 Pro, I bought a TS10 from another OL store. it’s Anduril2 and it’s fun!
But I like SC21 Pro so much, therefore I bought another one from another OL store and it’s a legit Anduril2 as well. but it came with a rather older version of A2. didn’t have Tactical Mode.
I’m sure it’s good to have more than one weapon and be able to operate those weapons properly. Giving you more chances of winning the battle two is one, one is none
I remember building my own Windows PC, and another one for my friend, it’s fun.
That’s before my laptops.
Now I only have one laptop, Windows 10. Ubuntu and Android have resided in it for some while, with dual-boot. But now it’s only Windows 10.
My current laptop is rather old too (I have gifted the newer one to my sister).
I think it originally came with Windows XP (XP’s last days before it’s discontinued) .
Upgraded to Win7,
then to Win10. Couldn’t upgrade to Win11 though;
incompatible/machine is too old I guess.
I often learn from people asking questions and the other giving answers/solutions,
IMO it’s a better way of learning, from real cases,
rather than solely reading the Manuals.
oftentimes what I read today I don’t understand it right away, but becomes very valuable info for tomorrow, or it’ll makes sense to me after a week later.
I haven’t done dual boot in a long time, but I’ve been floating the idea for when I rebuild my pc. Thinking instead of partitioning, using 1 nvme drive for Win10/11 (not sure if I want to go 11 yet) and another nvme for linux. I fully agree with having more than one weapon/tool for the job and being able to use them
More that the multichannel branch doesn’t support those lights yet. There’s a long list to port over, as the branch has breaking changes for per-model config from the old one. I converted one build but it was an easy one, I might have a go at doing some more if I can find some time this week. Didn’t get as much done as I hoped this last weekend due to some stuff.
No specific list, but my builds for your version were for every light currently supported (remember there’s a lot of reuse of firmware images for lights with the same MCU layout). If it’s just the SP10 Pro you want, it might be easier and faster to just add support for it to the new branch. As for the SC31 Pro, there isn’t a hardware-specific config file for it, so that probably shares firmware with another light. Can you post your model code form the last 4 digits of version check for it?
The SP10 is kinda a side thought here-- I dont carry it daily often enough to mind it not having the change. I wouldn’t mind it, but it eventually, but its no big deal. I could even play with thst myself now that I can see what you changed.
The SC31 is really what I’m after. I hadn’t realized it didn’t have a specific config since I really hadn’t looked at the code yet while waiting on a functional build environment.
I’ll have to get back to you in a couple weeks on the number… my current SC31 is at the bottom of a river right now, after an incident on Friday.
Sofirn just shipped the replacement but that’s at least two weeks time to get to me.
Completely forgot about doing this… - had a look into it, it’s a linear+FET so I’m going wait until there’s at least one similar light supported because I might be missing something here and can’t get it to work and don’t really feel like making changes to the actual code for a light I don’t have one to test with.
Hi to all…please, if is possible, a command for switch off the AUX rapidly. Every time we use low aux mode we do 21 clicks for switch off…
maybe too many clicks for me
Off the wall thought… what are the odds a L1ts build will flash to a SC31 pro and work? I mean, how similar is one Atiny 1616 based driver to the next?
Probably lots more hardware differences outside of the main 1616 chip, and I’m going to brick(or worse fry) the light is where I’m leaning… lol.