Right after your response I looked again at the pictures trying to figure what I didn’t get. My brain froze with confusion…how could it be 6 cm ?!? 
Ah yes, I remember we discussed about it in PMs.
All of the 14 7135s will be soldered in.
However, only 4 per channel will be activated at the same time.
I would love one. Thanks!
That’s awesome that all the 7135s will be populated and that we just have to make solder bridges to bring the others “online”. Very smart and thoughtful of you all. 
That’s what we are planning.
We are planning to limit power via firmware, with only 4x7135 per channel being activated initially.
Edit: See, this is what happens when I’m confused.
I don’t believe that is correct. The plan was to populate all 14 7135s (2 channels, 7 per channel), and allow folks to connect in additional ones by shorting pads. On the prototype all the pads came shorted. Like I think DBSAR said recently only 4 or 5 would be connected as “stock”.
correct, that is the original plan. Have 4 or 5 connected from the factory by default, and the rest left open for those who want to push more output at a sacrifice of run times. I will be testing the maximum run times & amp draw loads with all 7 connected at first, then desoldering a couple of the 7135 bridges on each channel to get amp readings and run time comparisons then. The extra AMC chips are to be on the board for user modifications. (increase in output)
Nope. The control chip doesn’t have the physical ability to activate individual 7135 chips.
There are two ways for the user to adjust the highest power level:
- Physically connect or disconnect 7135 chips by adding or removing solder bridges on the battery side of the driver. This changes how much power is considered “100%”.
- Use firmware to adjust the ceiling level lower than 100, if desired. The firmware allows configuring the ceiling level, but it is set to 100 by default. If the user lowers it, 100% will still be available… but it is treated as “turbo” and is only accessible with a double click while already on a lower level.
Today there has also been some discussion of a “turbo plus” which would only work at 4000K color temperature… but I wasn’t planning to add anything like that.
Please place me on the interest list.
I’m already on the list for two, 688 and 689. Please add two more for a total of four.
I plan to pick up 4 full sets: lantern, batteries, case, etc, etc.
The first two are mine. Mine mine mine. The new ones are planned gifts. Depending on overall price, I can see picking up a couple more than four.
Amazing work, thank you.
One side note. I’ve been going out to Burning Man since the late 90s and have rigged up a ton of led solutions over the years. I’m the ‘light dude’ in our camp. This is exactly what I’ve been trying to make as far as a portable lantern goes. I’m not sure I want to be responsible for the possible carnage, but I think a post or three in BM forums would yield a great deal more initial orders. If that’s desired. At a risk of drastically lowering the S/N of this thread.
I’m interested in one.
There is no doubt this LT1 lantern can be a big interest outside for the general public eventually, as it fills a gap for a good quality area light/lantern that has recharability along with battery replacing, high CRI tint, functional design. portability, long-term off-grid uses, great modes, built out of metal (wont blow off the camp table like some plastic ones do i seen) the list goes on.
Awesome, thanks everyone! Man this is cool. Put me down for 2 more, for a total of 4 please.
On the note of bringing in burning man people, I’m torn. I don’t want to bring more noise into this thread, but I do want people to appreciate this light. Maybe sofirn would be happier with us if we let the BM people pay full price? That sounds mean and selfish now that I say it. But I kind of feel that way, anyone else?
Also, just my opinion, I don’t think we should have a turbo+ mode. I don’t think there and be any mode that can overheat the head of this lamp. Because there is no efficient way to get heat to the MCU, correct? People could burn themselves. Unless we added a turbo timer? It’d have to be real short.
Maybe make it a config option in the source code? People adventurous enough to compile their own code, or find someone to do it, can be trusted with the extra power. In my opinion. I’m just worried about the people I plan on gifting these to.
Yeah, I agree with BM people having to pay the full price.
We have to respect Sofirn, and BLF itself.
No arguments, that’s why I tossed it out for discussion.
If you’re going to BM and are even remotely interested in leds, then you’ve most likely already found this place. If not, it’ll be a pleasant surprise.
Add me for a third as well as the accessory kit with it. 1055 1056 are my first two. (Are you even tracking the accessory kits?)
Correct.
The plan is to put a temperature sensor in the LT2, if there is one. Also, a constant current driver. This would require more pins though, so the driver would use attiny1634 instead of attiny85. Two pins per channel to control power, or four PWM pins total. Another for the e-switch. Another to control the button LED. Another for the temperature sensor. Another for a voltage sensor, since both the temp sensor and the constant current parts are incompatible with measuring voltage on the VCC pin. Plus ground, VCC, and reset. Etc. At least 11 pins needed.
I’m not looking forward to doing the math and the code involved in making tint ramping work with four power channels. It’ll be a bit tricky. I suppose the tiny1634 will have plenty of space though, so I can actually afford to do the math on the device itself instead of needing low-tech trickery to make it fit.
But first we need to finish the LT1. 
Yeah. The code is getting pretty messy with all the compile-time options though, and a “turbo plus” feature doesn’t easily fit into the abstractions the code uses. It all assumes the maximum power is 100, with no means of going beyond that… but in this case, 200 is possible. So I probably need to figure out a clean way of enabling model-specific quirks like this which make no sense on other hardware. I also need to clean up the code in general.
Definitely not at this point.
It wouldn’t be a lot of work to track accessory kits since it’s just an additional column in the table I created for the lantern buy. But as slider said it’s not being tracked and I have no plans to do so.
Once we get the lantern ready for orders, we can start another topic GB I’m guessing for the accessory kit, as i still have to test some of the accessories I’m working on for the sample lantern.