Man, just think of the WHOLE LOTTA FUN you are going to have when it arrives, it will help you bear the waiting 
1 Thank
Thanks for the link to TK’s repo! We already knew it, but it’s always good to have confirmation.
What we need now is the Convoy-specific files – there should be at least two new files, eg hwdef-Convoy_M21E.h and cfg-Convoy_M21E.h, plus any other files you may have needed to modify and/or add for the M21E Anduril driver (unless of course you have built it using an equivalent pair of already existing files).
Can you please post those, or tell us which one of the pre-existing pair of hwdef/cfg files you used for the M21E?
Thanks in advance!
2 Thanks
It works!
1 Thank
So… I hate to say this, but we have(or I do anyway) a glitch in the 8c aux off mod, on my wurkkos ts11.
It will not let me turn off Aux in lockout mode.
Well, ok it will do it. It just wont stay that way.
Either way: 8c to aux off, or 7c through to aux off works fine.
But 30 seconds later it unlocks, and the aux goes straight to whatever mode it is set for in “standby”(off, not locked), without displaying the voltage check flash–I never turned that off, I like it. If I lock/unlock it displays the voltage flash fine.
Re-lock and aux is still off, and 30 seconds later it will unlock again. (Literally… I’m timing it each time. It actually seems to varry from 28 to 32 seconds; but that might be my error factor watching my watch… ).
Now, with an auto lock timer set, with aux in lockout off, it will lock, and then aux stays off, and the light stays locked( I waited like 5 minutes anyway) .
But as soon as you touch the button(momentary moon), 30 seconds after the last button press it will unlock the light again.
Unlocks to standby, like a 3C from lock would be.
I can put it in Any aux on mode or brightness level in lockout, and it will stay lit for hours.
Tried a fresh battery. No different.
Simple ui or advanced, both the same.
Weird, huh?
Soooo… basically when you turn off the aux, what is the mcu doing/ checking on at 30 seconds, and in this case waking the light up?
I’ve tried to be as clear as I can… by all means, ask questions if I’m not!
I’m avoiding doing a “factory reset”, and seeing what happens… I just got everything set up again after flashing it lol. Its not a lot of setting… but… I’m lazy. I’ll probably try it when I get home today just to see if it changes this.
1 Thank
I don’t know if I understood.
To display the voltage with the Aux you have to jump to that mode with 7C.
The 8C is full Off.
I don’t understand about the blocking.
Just to say that locked only flashes if you try to turn it on but it will not change mode.
Is it like that?
1 Thank
No, I dont think you understood, but I have the same issue with your posts… language barriers are terrible…
With the current multi channel branch, voltage can be displayed for a few seconds by the aux/switch led at every button press, on, off, locking and unlocking, and displays constantly at the switch if the main LED is on.
But this glitch is with any aux mode while the light is locked, not just voltage. I only mentioned that because it is preventing that voltage display that the above feature would show as it unlocks normally.
The light will not stay locked if you turn aux off. It unlocks itself, that is the main problem.
1 Thank
@AK-Adventurist, Thanks for the detailed report, and @Litris, thanks for stepping in to help.
I’m on traffic right now on a long errand, but in a few hours I will be back home and at my computer and will then respond properly.
EDIT: back home but totally bushed. Will have a look at that when I wake up tomorrow.
EDIT2: So I did and just posted my conclusion below. Thanks again to @AK-Adventurist for the additional tests and for the find that the problem doesn’t happen with a fully-charged battery.
1 Thank
Now I understand you.
It is the voltage function that only lasts for a few seconds and then shuts off if it is set to turn off.
Or it stays on if it is set to on.
But in the first few seconds the battery status color appears.
@dmenezes will have to see it since I compile the code.
I used the translator and I didn’t understand almost anything 
sorry.
1 Thank
I think you are referring to your TS11, saying the dmenezes hex for 8C Aux toggle, makes lockout not work properly.
on my TS10 the dmenezes hex for 8C Aux toggle, messed up the 3C battery check, it reads 5 Volts. more details here
fwiw, I use the dmenezes hex on my TS25 and it does not unlock itself with Aux off like your TS11, it also does not mess up the battery voltage check like on my TS10.
On my TS25 everything seems to work as intended when using the dmenezes hex file with 8C aux toggle.
1 Thank
Perfect, thanks for commenting, I have a TS25 as well.
Yes thanks, I too have a TS25 on the way, so thats nice to know.
I’m tempted to flash the TS25 hex to the TS11 and see what it does.
@dmenezes A factory reset on the TS11 didn’t help or change anything. 
So, did you change the build/hex for the TS11 when you did this update to the full Zip?
I thought, “well, why not, maybe he will re-compile all of them” so I re-downloaded the Zip and used that TS11 hex to re-flash mine.
The issue I had before is gone!
it will now stay locked, if I turn off Aux in lockout mode!
Whatever you changed(if anything…If you didn’t change it, them I’m confused… lol) fixed it!
1 Thank
Nevermind! 
It worked fine for the first few cycles, lasting several minutes without unlocking, I swear. Now its back to a 25 to 30 second delay, and then unlocks itself.
Now I’m verry confused.
@dmenezes I already have the programmer!
@thefreeman I got it much sooner than I thought, it arrived in perfect condition but I have not tested it.
Thank you very much for your effort, for europe it is an advantage.
Edit: Of course thanks @gchart thanks for your work on the design, but as you know and advise, for Europe it is not a good option to ship from USA.
4 Thanks
@dmenezes
You are going to get tired of me lol… 
I think I figured part of it out.
I swapped to the custom build @wolfgirl42 built me a while back,
I didn’t want it for this light, but she did all the hex, so I figured why not try it out. It was doing the same thing; I lock the light, and after 25 seconds it would unlock, but only with the aux set on bright. Never on low, flash, or off.
So I got to thinking, and wanted to try anything. Was about to swap to @Toykeepers rev721 hex file, and see what stock multichannel does, when I decided to swap to a fresh battery again, just for good measure.
Bingo! No issues.
Swap battery back, problems…
So I flashed back to your 8C aux mod, and its also fine with the fresh battery.
pop the other battery on the charger for a bit, up to 4.0v, and now it works fine with it too!
SO either I have a flaky battery(Its a brand new ~3 or 4 weeks since I got it 18650 direct from Sofirn, thats been charged twice) OR it has to do with the software reacting to battery voltage? ((OR its something that has to do with voltage and invoking 8C functionality, since both mods do that, but the one @wolfgirl42 built me is manual memory mods, nothing to do with aux modes; I am assuming the 8C similarity is coincidence…))
I’m gonna use the light a lot and see, if once the batt hits 3.9 volts it starts doing it again.
Is there something that periodically checks the batt voltage, even with the light “off” and locked in the multichannel branch? All I can find is
““When a light has a single-color aux LED and no RGB, it fast-blinks the
aux LED in “off” modes when voltage is low.””
But that shouldn’t apply to this hardware, and that should be below like 3.0v or lower IIRC, not 3.9v… I’d think. I mean, 3.9v is still like a “half full” or more battery, right?
2 Thanks
Sure, 4v 3.9v is still correct for your use.
I would try the standard firmware.
1 Thank
No way On the contrary, thanks for your persistent efforts in trying to pin down this issue.
Oh my, thanks for that! I’ve read and re-read your original description of the problem, and even tried ‘chinese-tracing’ the code by hand to try and see what could be happening, to no avail. Specially puzzling was that the problem also manifested itself with 7C – and my mod didn’t touch the 7C code.
A flaky battery (more about that below) really explains everything.
More than half-full – 3.9V is kinda 70% full or even more, depending on the exact battery model. But anyway you’re correct, 3.9V is way too high for that kind of behavior.
What could perhaps be happening is voltage sag: when you check the battery it’s showing 3.9V, but just a few seconds earlier it could have been much lower, perhaps even lower than 3.0V. I’ve seen that with flaky batteries. This is not easy to diagnose as by the time you pull the battery out to check with a multimeter, or even press 3C from off to have the light itself blink you the voltage, it could have climbed back to 3.9V.
Do you have access to an analyzing battery charger? Chargers capable of that will discharge the battery while monitoring the voltage and will flag the battery as having low capacity if a voltage sag happens during the analysis.
This is the best approach. I would also suggest that you mark the original battery with which the problem manifested itself so as not to get it mixed with the others. I would also try with a different brand/model of battery just to be sure.
If the problem repeats itself in all the above cases, then I would say to try with the original TK rev 721 multichannel code; perhaps it’s something in her original code and we can get her a bug report – I really can’t see how my mod could be causing that specially since it also manifests with 7C which my mod has not touched.
Looking forward to your further reports, and thanks again!
2 Thanks
Excellent! Congrats! Looking forward to your first adventures in flashland
2 Thanks
Seems we are already on the way to diagnosing this issue as not being connected to my mod (as per yours and mine later posts), but to not let your question unanswered: no, only the FC13 and TS10 were updated in the full zip (to correct my having built them with my own configuration by mistake).
1 Thank