ToyKeeper, closed source is requirement from Noctigon. I think, you can ask Hank to give you source codes too. Or you can collaborate together for next beatiful version of this (or another) Noctigon light!
And yes, it is assembler .
Inferion always share sourсe code of previous version of his projects (and often last version too). And not only sourсe cobe but also PCB, schemes, etc. But this time it’s commercial project and Inferion can’t share source cobe because of contract with flashlight supplier don’t permit this. Sourсe code of Indigo 5.2 is in this message Показать сообщение отдельно - Indigo 5.0, или "не совсем форумный" драйвер? (Часть 2) . But, of course, Meteor has significally modified firmware, much more automated and better working. Also I used Indigo 5.2 in my flashlight for a long time and it’s work not bad.
Inferion use assembly code because Tiny85 has small amount of memory and if compile firmware from C it can’t fit MCU. Using other MCU is difficult because Tiny85 is very-very good MCU for drivers like subject flashlight and has many useful things inside the chip.
Hey, thanks! I didn’t see any sources when I looked, but I also don’t read .ru very well.
I can’t do much if the source is closed, even if I had a copy, since an open license is required in order to share anything with the community. In general I’m less interested in producing a product, and more interested in empowering people to make their own products.
On a different note, it’s nice to have some Fonarevka folks on BLF now. I know language tends to keep the two sites separate, but we’re both crazy about shiny objects. 
BTW, if there is any open-source code available, I’d be happy to include it in the torch code repository I’m maintaining. The link is in my signature below.
Yes, the attiny chips are awesome, and I would love to use the attiny85 because it has 8192 bytes available.
I understand about trying to fit everything. I’ve been using the attiny13a (1024 bytes) and it’s very difficult to fit the features I want! C is not so bad though; even with C I managed to fit 20 modes in 3 mode pseudo-groups into 1024 bytes, including dual turbo step-down, low-voltage protection and step-down, eeprom wear-leveling, dual PWM, some tint management, offtime measurement, and it still has 70 bytes left. The interface works like this.
(BTW, moon on that light is 0.3 lumens, max turbo is 3300 lumens, it’s 24mm x ~124mm in size, and it can be built for about $50 using parts from RMM’s amazing shop… so many cool toys available these days!)
Firmware of Meteor control many parameters, not only UI. It control input and output voltage, input and output current, inductance, internal resistant of batteries, temperature and etc. (Inferion can explain more detail) and use many mathematics models, filters etc. for drive MOSFET. It’s not only DC-DC step-up with different current output and some user interfaces. I don’t know about Meteor, but Indigo 5.2 use three different methods for current regulation depending of current amount. Meteor use at least two different methods (I can see when one method change to another). Maybe it has three methods but with my eyes I can’t see it. Even when used assembler now no free memory and for add some new functions first you must make more optimisation of existing code.
Boy it sounds like I’ll have my work cut out for me trying to figure out and explain how to program this light, when I get it.
You’ll have it tomorrow. :bigsmile:
*sigh…after reading all this schematic modes… makes me reconsidering about purchasing this awesome light. :~
Maybe I should wait little longer, then they might put the new XP-L LED on the next Meteor 44 :bigsmile:
UI 3 looks okay. I’d probably set it to the three lowest levels such that a double-click would rotate through the three levels in increasing order (click once for moon, click twice for low, click then click-and-hold for med). It’d give me access to modes 1, 2, 3, and 7… and I would probably just not bother with 4, 5, or 6.
has to be the best light in your collection, no?
I’m waiting for the S3 3D emitter. Now he says ‘next week.’ I want a super flooder, so I need Carclo 10509. But Dales video makes me think I wouldn’t be able to replace the optics.
Anxious to see Marks video review! But like all his reviews, he will need some time 
My order for LG's new high drain LG HG2 cells were a no go. The seller didn't actually have any in stock. Instead, I've got some LG MH1 cells instead on their way. They're 10A max draw and have 3200mAh capacity. They're also quite cheap at $5.76 per cell when bought in a 10 pack.
The best light in my collection? probably not… some of the OL creations is probably one of the best ones… the smallest and the brightest maybe :bigsmile:
Can’t wait! Oh wait, I have to… doing a webcast out of town, so I have to wait to use it until Saturday evening… I will try and get this one cranked out fast… I want to shoot for a week to a week and a half before shipping it to the next victim!
In 10 days Hank will be sold out and moving on! 
lol
I wonder if Hank can have the spot of glue left off that one leg on the optics for those of us interested in possible changes in the future?
I’m pretty sure the Automotive 3M double stick tape will pull it out, glue or no glue. If mine won’t come out I’ll get serious with em and drill the legs out, put trits in the legs when I put it back together.
if Dale had had the light for a week, I wonder what he would have presented to us?
I wish Dale is the last guy on the list… so he can tore them apart and take a look if he can reprogram the driver into simple one and change the optics
My Stone White S4 2B has shipped, so I’ll be doing the full onslaught of testing pretty soon.
Haha, wow. I never thought of that.
I wonder what size tritium vial would best fit in the center of the optics, right between the incoming power wires and the three TIRs. I wonder if the heat would be an issue for it.
How did they seal off the ends of the glass tube to make the tritium vials?
ordered a stone white S2 1D D-D
now counting seconds….