7135 … is a decent compromise of efficiency, cost, complexity, ease of design.
Personally I wish the 7135 had never been invented. It has stifled innovation for so many years because it works and scales so well, and is inexpensive.
What’s wrong with having things which are good, cheap, and easy? A thing doesn’t have to be difficult or expensive to be worthwhile.
One could also argue that it enabled hobbyists to innovate because it lowered the barrier to entry; without it we might not have any of the cool stuff we have today. Or one could argue that aluminum shouldn’t exist because it’s too good at too many things, and it’s cheap, so it has stifled innovation of more interesting materials.
Tom Tom wrote:
OSHpark and the various open source software models are fine, but not something that I particularly embrace. Engineers should be paid for their efforts …
Open-source doesn’t mean not getting paid. It’s free software because it’s free as in speech, not free as in beer. Here’s a summary of the two main models for these things:
With proprietary software, you get what you pay for.
With open-source software, you get what you pay for, everyone gets what you pay for, and you get what everyone pays for. More people get more value without individually having to pay more, and its openness reduces the risk for everyone involved.
Tom Tom wrote:
If they simply re-purpose derivative works from others, that’s down to their conscience as to whether they also acknowledge their inspiration.
Conscience… and the license. Attribution is legally required in almost all free software licenses, because it’s a necessary part of making copyrights work.
7135 … is a decent compromise of efficiency, cost, complexity, ease of design.
Personally I wish the 7135 had never been invented. It has stifled innovation for so many years because it works and scales so well, and is inexpensive.
What’s wrong with having things which are good, cheap, and easy? A thing doesn’t have to be difficult or expensive to be worthwhile.
One could also argue that it enabled hobbyists to innovate because it lowered the barrier to entry; without it we might not have any of the cool stuff we have today. Or one could argue that aluminum shouldn’t exist because it’s too good at too many things, and it’s cheap, so it has stifled innovation of more interesting materials.
Tom Tom wrote:
OSHpark and the various open source software models are fine, but not something that I particularly embrace. Engineers should be paid for their efforts …
Open-source doesn’t mean not getting paid. It’s free software because it’s free as in speech, not free as in beer. Here’s a summary of the two main models for these things:
With proprietary software, you get what you pay for.
With open-source software, you get what you pay for, everyone gets what you pay for, and you get what everyone pays for. More people get more value without individually having to pay more, and its openness reduces the risk for everyone involved.
Tom Tom wrote:
If they simply re-purpose derivative works from others, that’s down to their conscience as to whether they also acknowledge their inspiration.
Conscience… and the license. Attribution is legally required in almost all free software licenses, because it’s a necessary part of making copyrights work.
This
—
That Canadian flashlight guy & Lantern Guru -Den / DBSARlight
If they simply re-purpose derivative works from others, that’s down to their conscience as to whether they also acknowledge their inspiration.
Conscience… and the license. Attribution is legally required in almost all free software licenses, because it’s a necessary part of making copyrights work.
There is no equivalent to the software model licences as regards hardware.
Which, I think, is why there is this reluctance to put up schematic diagrams and BOMs here. Most seem to be copies of application note circuits, when studied. At most we get a link to an OSHpark layout to reverse-engineer.
Circuit designs cannot be protected the same way as code, AFAIK. Certainly not the type of drivers we have, even the most esoteric, it has all been done before, they really are not very complicated.
By the way, with all the SW open-source models, has anyone ever exercised their rights if they thought they were being ripped off ? Perhaps they have, maybe they got somewhere, I don’t know, not my area.
And, to be frank, it is the hardware that costs actual money and is the most important thing for manufacturers to optimise. Just saving a few pence by removing or using lower spec. (but still satisfactory) components, or innovative circuit design, intelligently is of great interest to manufacturers.
If the code source is given away for free (but, hopefully you get paid for adapting it to the device) that’s fine by me.
But hardware design, component selection, PCB layout, prototyping, testing, requires expensive tools, skills, knowledge, time, expert materials procurement etc. to do it properly, and is a rather rigid discipline. Not something to be dipped in and out of.
Or done remotely, from a WiFi laptop anywhere in the world. You actually have to check in to the Lab and use the (very expensive) kit to see what’s actually going on.
Quite different from simply connecting a clip and having a few goes until you have something workable.
The PogoPin connector will be transformational I hope.
If the code source is given away for free (but, hopefully you get paid for adapting it to the device) that’s fine by me.
But hardware design, component selection, PCB layout, prototyping, testing, requires expensive tools, skills, knowledge, time, expert materials procurement etc. to do it properly, and is a rather rigid discipline. Not something to be dipped in and out of.
I’ve seen code written by engineers. So I can say with some authority that software is not something to be dipped in and out of either. Just because you don’t know how difficult it is to do correctly does not mean you can dismiss it as trivial. Good software is what makes or breaks a lot of products these days. For example, put bad software in a car and you no longer have a car.
If they simply re-purpose derivative works from others, that’s down to their conscience as to whether they also acknowledge their inspiration.
Conscience… and the license. Attribution is legally required in almost all free software licenses, because it’s a necessary part of making copyrights work.
There is no equivalent to the software model licences as regards hardware.
Which, I think, is why there is this reluctance to put up schematic diagrams and BOMs here. Most seem to be copies of application note circuits, when studied. At most we get a link to an OSHpark layout to reverse-engineer.
Circuit designs cannot be protected the same way as code, AFAIK. Certainly not the type of drivers we have, even the most esoteric, it has all been done before, they really are not very complicated.
By the way, with all the SW open-source models, has anyone ever exercised their rights if they thought they were being ripped off ? Perhaps they have, maybe they got somewhere, I don’t know, not my area.
And, to be frank, it is the hardware that costs actual money and is the most important thing for manufacturers to optimise. Just saving a few pence by removing or using lower spec. (but still satisfactory) components, or innovative circuit design, intelligently is of great interest to manufacturers.
If the code source is given away for free (but, hopefully you get paid for adapting it to the device) that’s fine by me.
But hardware design, component selection, PCB layout, prototyping, testing, requires expensive tools, skills, knowledge, time, expert materials procurement etc. to do it properly, and is a rather rigid discipline. Not something to be dipped in and out of.
Or done remotely, from a WiFi laptop anywhere in the world. You actually have to check in to the Lab and use the (very expensive) kit to see what’s actually going on.
Quite different from simply connecting a clip and having a few goes until you have something workable.
The PogoPin connector will be transformational I hope.
The pogo pin connector is already ordered by me
the topic is also public as well as the pattern for drivers
who says this is a fully open source project?
Even open source firmware or driver design can be under open source rights
for example forbid the commertial use of it without making an agreement with the programmer or designer
also open source for code means usually laying the source code open, but noone is forcing Toykeeper not just to make the hex file public
on the other side having just the Gerber uploaded to Oshpark means you do not get the design file
this is still the decision of the one who makes the design, if I do not want to post it the only way to get a driver is reverse engeneerring from a lantern BLF do not nessesarely means open source for everything, or the guys developing not getting payed
But making it open source is a tribute for the community,
you forget how much effort in some things like Toykeepers firmwares is spent
like someone wrote if you are not happy with the driver make your own design and see how many hours you will spend,
even reverse engeneer a driver takes hours in the complexity of the current FET driver
If they simply re-purpose derivative works from others, that’s down to their conscience as to whether they also acknowledge their inspiration.
Conscience… and the license. Attribution is legally required in almost all free software licenses, because it’s a necessary part of making copyrights work.
There is no equivalent to the software model licences as regards hardware.
Which, I think, is why there is this reluctance to put up schematic diagrams and BOMs here. Most seem to be copies of application note circuits, when studied. At most we get a link to an OSHpark layout to reverse-engineer.
Circuit designs cannot be protected the same way as code, AFAIK. Certainly not the type of drivers we have, even the most esoteric, it has all been done before, they really are not very complicated.
By the way, with all the SW open-source models, has anyone ever exercised their rights if they thought they were being ripped off ? Perhaps they have, maybe they got somewhere, I don’t know, not my area.
And, to be frank, it is the hardware that costs actual money and is the most important thing for manufacturers to optimise. Just saving a few pence by removing or using lower spec. (but still satisfactory) components, or innovative circuit design, intelligently is of great interest to manufacturers.
If the code source is given away for free (but, hopefully you get paid for adapting it to the device) that’s fine by me.
But hardware design, component selection, PCB layout, prototyping, testing, requires expensive tools, skills, knowledge, time, expert materials procurement etc. to do it properly, and is a rather rigid discipline. Not something to be dipped in and out of.
Or done remotely, from a WiFi laptop anywhere in the world. You actually have to check in to the Lab and use the (very expensive) kit to see what’s actually going on.
Quite different from simply connecting a clip and having a few goes until you have something workable.
The PogoPin connector will be transformational I hope.
The pogo pin connector is already ordered by me
the topic is also public as well as the pattern for drivers
who says this is a fully open source project?
Even open source firmware or driver design can be under open source rights
for example forbid the commertial use of it without making an agreement with the programmer or designer
also open source for code means usually laying the source code open, but noone is forcing Toykeeper not just to make the hex file public
on the other side having just the Gerber uploaded to Oshpark means you do not get the design file
this is still the decision of the one who makes the design, if I do not want to post it the only way to get a driver is reverse engeneerring from a lantern BLF do not nessesarely means open source for everything, or the guys developing not getting payed
But making it open source is a tribute for the community,
you forget how much effort in some things like Toykeepers firmwares is spent
like someone wrote if you are not happy with the driver make your own design and see how many hours you will spend,
even reverse engeneer a driver takes hours in the complexity of the current FET driver
indeed well said all these projects take hours, days & months of work.
—
That Canadian flashlight guy & Lantern Guru -Den / DBSARlight
So I spent time at lunch today updating the interest list. huey18 spent some time and effort automating this, but not all folks wanting a lantern are following his instructions for request, and also there is a problem with the listbot updating last I saw. Anyway, I added another 25 lights to the interest list since I took a short break, the total is up to 1004. I know there is an error of at least one, but hopefully everyone that wants one or more will get the code or whatever once this goes live. Don’t hold your breath for that, but things are moving these days.
how much effort in some things like Toykeepers firmwares is spent
This is something we can quantify, though. At a glance…
The firmware repository has a total of 723 revisions, or 622,556 lines of patches (including everyone’s code, not just mine), committed over a period of about 4 years.
According to sloccount, the FSM project has 9,171 lines of code, which it estimates would take one average programmer 2.05 years to write, or would take a team 8.4 months, for an estimated cost of $115,336 (or $276,808 including corporate overhead). I think it has a tendency to estimate high though.
Some other projects according to sloccount (without overhead costs):
BLF-A6: 18 days, $2,846.
Bistro: 2 months, $9,268.
Crescendo: 2.8 months, $13,048.
Just a ballpark idea of the amount of effort involved in these things.
Batteries get charged with 2A as we do not use the chips internal bus
OK, something to bear in mind if I’m only running the light with one cell – not all cells are rated for that.
Two or more cells should be fine, though. I haven’t seen any 18650s that wouldn’t accept a 1A charging current.
ToyKeeper wrote:
Lexel wrote:
how much effort in some things like Toykeepers firmwares is spent
[commercial cost estimates]
Just a ballpark idea of the amount of effort involved in these things.
Believe me, I appreciate those efforts. The majority of the lights I use nowadays run firmware ToyKeeper wrote. I’ve also benefitted from things like the BLF A17DD driver designed by Wight, and it looks like I’m going to benefit from Lexel’s driver for this lantern.
how much effort in some things like Toykeepers firmwares is spent
This is something we can quantify, though. At a glance…
The firmware repository has a total of 723 revisions, or 622,556 lines of patches (including everyone’s code, not just mine), committed over a period of about 4 years.
According to sloccount, the FSM project has 9,171 lines of code, which it estimates would take one average programmer 2.05 years to write, or would take a team 8.4 months, for an estimated cost of $115,336 (or $276,808 including corporate overhead). I think it has a tendency to estimate high though.
Some other projects according to sloccount (without overhead costs):
BLF-A6: 18 days, $2,846.
Bistro: 2 months, $9,268.
Crescendo: 2.8 months, $13,048.
Just a ballpark idea of the amount of effort involved in these things.
Wow!!……. Is now a good time to ask for a loan?
—
Im not a Pessimist …. just an Optimist with a lot of experience
Those are only estimates, the amount that a standardized tool thinks it would cost to develop the same thing at a traditional software company. But that’s not how the code was created.
Would be nice if I was actually paid what sloccount estimated though.
Those are only estimates, the amount that a standardized tool thinks it would cost to develop the same thing at a traditional software company. But that’s not how the code was created.
Would be nice if I was actually paid what sloccount estimated though.
If i had the spare cash i would pay Lexel to build a prototype to sent to you for testing your firmware, but right now with my financial crisis i am in a red-zone for extra money to pay for anything.
—
That Canadian flashlight guy & Lantern Guru -Den / DBSARlight
Those are only estimates, the amount that a standardized tool thinks it would cost to develop the same thing at a traditional software company. But that’s not how the code was created.
Would be nice if I was actually paid what sloccount estimated though.
If i had the spare cash i would pay Lexel to build a prototype to sent to you for testing your firmware, but right now with my financial crisis i am in a red-zone for extra money to pay for anything.
I’m sure enough of us would pitch in to get it done if that’s what you guys wanted to do. I don’t have a lot of extra money to spend right now, but I would pitch in a little. If you want to get Lexel to make a driver board for TK to test with, just make it known and set up some way for us to contribute.
—
The Cycle of Goodness: “No one prospers without rendering benefit to others”
- The YKK Philosophy
Those are only estimates, the amount that a standardized tool thinks it would cost to develop the same thing at a traditional software company. But that’s not how the code was created.
Would be nice if I was actually paid what sloccount estimated though.
If i had the spare cash i would pay Lexel to build a prototype to sent to you for testing your firmware, but right now with my financial crisis i am in a red-zone for extra money to pay for anything.
I’m sure enough of us would pitch in to get it done if that’s what you guys wanted to do. I don’t have a lot of extra money to spend right now, but I would pitch in a little. If you want to get Lexel to make a driver board for TK to test with, just make it known and set up some way for us to contribute.
If Lexel can make the board, then ship it to Toykeeper to test the firmware, (then maybe i can test that in the V2 prototype,) then it would help refine and get it right before it goes into production.
Right now Barry had an issue being able to read the .gbr files from the software that Lexel uses to design the driver with, but the Engineers Barry mentioned they need the driver files in a .pcb format, ( a different driver design software) so that part is at a hiccup at the moment getting the driver design information from Lexel to Barry for his engineers to read and build a prototype driver.
—
That Canadian flashlight guy & Lantern Guru -Den / DBSARlight
Those are only estimates, the amount that a standardized tool thinks it would cost to develop the same thing at a traditional software company. But that’s not how the code was created.
Would be nice if I was actually paid what sloccount estimated though.
If you remember, I pushed for a ‘permanent’ Toykeeper donation thread but you politely refused…… I donated then but you definitely deserve more ‘beer’ for what you do.
—
Im not a Pessimist …. just an Optimist with a lot of experience
Well, we kinda need AT LEAST Lexel and ToyKeeper to agree, since they would be committing to doing the stuff, and somebody to set a price, so we know when we hit the goal.
—
The Cycle of Goodness: “No one prospers without rendering benefit to others”
- The YKK Philosophy
Well, we kinda need AT LEAST Lexel and ToyKeeper to agree, since they would be committing to doing the stuff, and somebody to set a price, so we know when we hit the goal.
Indeed. Right now Toykeeper & Lexel are key members of the team helping to push this lantern project to become a reality.
—
That Canadian flashlight guy & Lantern Guru -Den / DBSARlight
if we could even raise enough funds to have Lexel build the driver prototype to send to Toykeeper to do the Firmware test on would probably give is some idea & starting point to establish what is planned for the BLF LT1 lantern project. I would pay for it myself but in a situation where my financial stability is in the red zone.
BlueSwordM sent me a small donation out of his appreciation for what myself and the lantern team are doing, & i will donate that to Lexel to build the driver when he gets back to me on the cost of it.
—
That Canadian flashlight guy & Lantern Guru -Den / DBSARlight
What’s wrong with having things which are good, cheap, and easy? A thing doesn’t have to be difficult or expensive to be worthwhile.
One could also argue that it enabled hobbyists to innovate because it lowered the barrier to entry; without it we might not have any of the cool stuff we have today. Or one could argue that aluminum shouldn’t exist because it’s too good at too many things, and it’s cheap, so it has stifled innovation of more interesting materials.
Open-source doesn’t mean not getting paid. It’s free software because it’s free as in speech, not free as in beer. Here’s a summary of the two main models for these things:
Conscience… and the license. Attribution is legally required in almost all free software licenses, because it’s a necessary part of making copyrights work.
Thanks TK. I wanted to say something but I knew I couldn’t do it justice. I was hoping you’d come along.
The Cycle of Goodness: “No one prospers without rendering benefit to others”
- The YKK Philosophy
Im not a Pessimist …. just an Optimist with a lot of experience
A little John Prine
This
That Canadian flashlight guy & Lantern Guru -Den / DBSARlight
There is no equivalent to the software model licences as regards hardware.
Which, I think, is why there is this reluctance to put up schematic diagrams and BOMs here. Most seem to be copies of application note circuits, when studied. At most we get a link to an OSHpark layout to reverse-engineer.
Circuit designs cannot be protected the same way as code, AFAIK. Certainly not the type of drivers we have, even the most esoteric, it has all been done before, they really are not very complicated.
By the way, with all the SW open-source models, has anyone ever exercised their rights if they thought they were being ripped off ? Perhaps they have, maybe they got somewhere, I don’t know, not my area.
And, to be frank, it is the hardware that costs actual money and is the most important thing for manufacturers to optimise. Just saving a few pence by removing or using lower spec. (but still satisfactory) components, or innovative circuit design, intelligently is of great interest to manufacturers.
If the code source is given away for free (but, hopefully you get paid for adapting it to the device) that’s fine by me.
But hardware design, component selection, PCB layout, prototyping, testing, requires expensive tools, skills, knowledge, time, expert materials procurement etc. to do it properly, and is a rather rigid discipline. Not something to be dipped in and out of.
Or done remotely, from a WiFi laptop anywhere in the world. You actually have to check in to the Lab and use the (very expensive) kit to see what’s actually going on.
Quite different from simply connecting a clip and having a few goes until you have something workable.
The PogoPin connector will be transformational I hope.
The Cycle of Goodness: “No one prospers without rendering benefit to others”
- The YKK Philosophy
The pogo pin connector is already ordered by me
the topic is also public as well as the pattern for drivers
who says this is a fully open source project?
Even open source firmware or driver design can be under open source rights
for example forbid the commertial use of it without making an agreement with the programmer or designer
also open source for code means usually laying the source code open, but noone is forcing Toykeeper not just to make the hex file public
on the other side having just the Gerber uploaded to Oshpark means you do not get the design file
this is still the decision of the one who makes the design, if I do not want to post it the only way to get a driver is reverse engeneerring from a lantern
BLF do not nessesarely means open source for everything, or the guys developing not getting payed
But making it open source is a tribute for the community,
you forget how much effort in some things like Toykeepers firmwares is spent
like someone wrote if you are not happy with the driver make your own design and see how many hours you will spend,
even reverse engeneer a driver takes hours in the complexity of the current FET driver
[Reviews] Miboxer C4-12, C2-4k+6k, C2, C4 / Astrolux K1, MF01, MF02, S42, K01, TI3A / BLF Q8 / Kalrus G35, XT11GT / Nitefox UT20 / Niwalker BK-FA30S / Sofirn SF36, SP35 / Imalent DM21TW / Wuben I333 / Ravemen PR1200 / CL06 lantern / Xanes headlamp
[Mods] Skilhunt H03 short / Klarus XT11GT, XT12GTS / Zebralight SC50+ / Imalent DM21TW / colorful anodisation
[Sale]
Drivers: overview of sizes and types
DD+AMC based drivers Anduril or Bistro OTSM 12-24mm, S42, 24-30mm L6, Q8, MF01(S), MT03, TN42
Anduril or Bistro 8A buck driver for 20-30mm, MF01/02/04, TN40/42, Lumintop GT, MT09R
UVC and UVC+UVA drivers
programming key
Remote switch tail DD board with FET
Aux boards:
Emisar D1, D1S, D4, D4S, D18, Lumintop FW3A, Fireflies ROT66, Astrolux MF01, Tail boards like S2+
indeed well said
all these projects take hours, days & months of work.
That Canadian flashlight guy & Lantern Guru -Den / DBSARlight
So I spent time at lunch today updating the interest list. huey18 spent some time and effort automating this, but not all folks wanting a lantern are following his instructions for request, and also there is a problem with the listbot updating last I saw. Anyway, I added another 25 lights to the interest list since I took a short break, the total is up to 1004. I know there is an error of at least one, but hopefully everyone that wants one or more will get the code or whatever once this goes live. Don’t hold your breath for that, but things are moving these days.
interest list sorted by entry number
interest list sorted by user names
PocketSammich wrote: I don’t need this, but I want it. Please sign me up.
I noticed I’m not on the list (I had expressed interest for one in post 1776). Could you add me for one?
Acebeam L18, Armytek Prime C1 Pro, Armytek Prime C2 Pro, Armytek Tiara C1 Pro, Astrolux MF01 Mini, BLF Q8, BLF A6, BLF FW1A, BLF FW3A, BLF FW3C, BLF LT1, Convoy L6, Convoy C8+ , Convoy S3, Emisar D4, Fireflies E07, Jaxman E2L, Manta Ray C8.2 long version, Olight S1R Baton II special edition series, S2R Baton II, Olight Baton 3, Olight Warrior Mini, Olight M2R Pro Warrior.
Most of them have been modded! =)
https://photos.app.goo.gl/JaJaDv4V838AEJf39
This is something we can quantify, though. At a glance…
Just a ballpark idea of the amount of effort involved in these things.
OK, something to bear in mind if I’m only running the light with one cell – not all cells are rated for that.
Two or more cells should be fine, though. I haven’t seen any 18650s that wouldn’t accept a 1A charging current.
Believe me, I appreciate those efforts. The majority of the lights I use nowadays run firmware ToyKeeper wrote. I’ve also benefitted from things like the BLF A17DD driver designed by Wight, and it looks like I’m going to benefit from Lexel’s driver for this lantern.
Thank you.
I definitely missed you, sorry TheShadowGuy. You are on the list now.
PocketSammich wrote: I don’t need this, but I want it. Please sign me up.
I updated the OP interest list up to # 971 with the last .rtf update you sent me.
That Canadian flashlight guy & Lantern Guru -Den / DBSARlight
Wow!!……. Is now a good time to ask for a loan?
Im not a Pessimist …. just an Optimist with a lot of experience
A little John Prine
Those are only estimates, the amount that a standardized tool thinks it would cost to develop the same thing at a traditional software company. But that’s not how the code was created.
Would be nice if I was actually paid what sloccount estimated though.
If i had the spare cash i would pay Lexel to build a prototype to sent to you for testing your firmware, but right now with my financial crisis i am in a red-zone for extra money to pay for anything.
That Canadian flashlight guy & Lantern Guru -Den / DBSARlight
I’m sure enough of us would pitch in to get it done if that’s what you guys wanted to do. I don’t have a lot of extra money to spend right now, but I would pitch in a little. If you want to get Lexel to make a driver board for TK to test with, just make it known and set up some way for us to contribute.
The Cycle of Goodness: “No one prospers without rendering benefit to others”
- The YKK Philosophy
Same thing for me.
My very own high current Beryllium Copper springs Gen 3:
http://budgetlightforum.com/node/67401
Liitokala Aliexpress Stores Battery Fraud: http://budgetlightforum.com/node/60547
If Lexel can make the board, then ship it to Toykeeper to test the firmware, (then maybe i can test that in the V2 prototype,) then it would help refine and get it right before it goes into production.
Right now Barry had an issue being able to read the .gbr files from the software that Lexel uses to design the driver with, but the Engineers Barry mentioned they need the driver files in a .pcb format, ( a different driver design software) so that part is at a hiccup at the moment getting the driver design information from Lexel to Barry for his engineers to read and build a prototype driver.
That Canadian flashlight guy & Lantern Guru -Den / DBSARlight
If you remember, I pushed for a ‘permanent’ Toykeeper donation thread but you politely refused…… I donated then but you definitely deserve more ‘beer’ for what you do.
Im not a Pessimist …. just an Optimist with a lot of experience
A little John Prine
+1 DavidEF
Me too ….. lets get er done
Im not a Pessimist …. just an Optimist with a lot of experience
A little John Prine
Well, we kinda need AT LEAST Lexel and ToyKeeper to agree, since they would be committing to doing the stuff, and somebody to set a price, so we know when we hit the goal.
The Cycle of Goodness: “No one prospers without rendering benefit to others”
- The YKK Philosophy
Indeed. Right now Toykeeper & Lexel are key members of the team helping to push this lantern project to become a reality.
That Canadian flashlight guy & Lantern Guru -Den / DBSARlight
Lets show some love for Toykeeper & Lexel
Problemes d'erection [url=https://www.viagrasansordonnancefr.com/]viagrasansordonnancefr.com[/url] meilleure pharmacie
I’m in if they agree
if we could even raise enough funds to have Lexel build the driver prototype to send to Toykeeper to do the Firmware test on would probably give is some idea & starting point to establish what is planned for the BLF LT1 lantern project. I would pay for it myself but in a situation where my financial stability is in the red zone.
BlueSwordM sent me a small donation out of his appreciation for what myself and the lantern team are doing, & i will donate that to Lexel to build the driver when he gets back to me on the cost of it.
That Canadian flashlight guy & Lantern Guru -Den / DBSARlight
I’m willing to donate as well. My currency is just a but useless against the USD and Euro.
Acebeam L18, Armytek Prime C1 Pro, Armytek Prime C2 Pro, Armytek Tiara C1 Pro, Astrolux MF01 Mini, BLF Q8, BLF A6, BLF FW1A, BLF FW3A, BLF FW3C, BLF LT1, Convoy L6, Convoy C8+ , Convoy S3, Emisar D4, Fireflies E07, Jaxman E2L, Manta Ray C8.2 long version, Olight S1R Baton II special edition series, S2R Baton II, Olight Baton 3, Olight Warrior Mini, Olight M2R Pro Warrior.
Most of them have been modded! =)
https://photos.app.goo.gl/JaJaDv4V838AEJf39
Pages