Hi all,
Sorry for the radio silence, I was out all last week and I’ve been fighting a migraine the last three days. I take full responsibility and humbly apologize to anyone who is upset by the run time situation. Also, Got_Lumens is just helping me out on the forums because he's a good guy, so no one should be looking to him for any apologies or action on my behalf. I also want to thank you for reporting your feedback and helping us identify a totally unexpected problem. Yes the numbers originally posted to the site were incorrect (see below) and there does seem to be a legitimate efficiency issue with the driver (also see below).
Along with your forgiveness, I'm asking for a little bit of understanding as well. I totally get some of you guys are upset. What you might not realize is that it's also upsetting on this end. I would wager I'm actually more troubled by the current situation than you good folks. You might have bought one or more Preons that you aren't happy with, but I have 500. I lose sleep over it. I'm frustrated by the situation. It's incredibly demoralizing. It's one more thing on my plate that shouldn't really be there. I just want you to keep in mind there are two sides to this.
If you are familiar with Prometheus, you know I pride myself on being accurate and transparent. Due to my workload, run time testing was not a priority compared to the other priorities that exist in the business, particularly when I had no reason to suspect a significant problem. Mea Culpa.
Pre-Production Lights:
As stated on the product page, this was a "pre-production" run. I talked about the coatings (specifically) because that was the primary intention of the test run. This is the "unknown" that I "knew" I was testing for. The Preon has been around for years, and frankly I wasn't expecting any problems with the driver. We changed the UI, drive levels, and the PWM frequency. None of these changes created a big red run time flag. The factory's engineer didn't see any theoretical issues with the driver either. Unfortunately I'm not an electrical engineer so I don't know if this is a component issue, software issue, or something else. I don't know if the problem is the result of one of those changes...or something else entirely. I'm currently working with the factory to sort this out.
I did intentionally call this a "pre-production" run because (by definition) that means that it's not full production, and I felt that was being sufficiently transparent. Again, I had no reason to suspect there would be any driver problems so there was no reason to call that out...but the entire purpose of pre-production is to detect any problem before full production. And there are always problems in manufacturing. Always. Even when you've been making the same thing the same way for years. Unknown issues are the hardest to account for.
Why didn't I test more?
To be honest, if I waited till I thought everything was perfect no product would ever make it to market. Primarily because nothing is ever perfect. Secondarily because problems don't always arise when you are reviewing samples. It's production that screws things up, and the only way to find production problems is by running production and getting product in the hands of users. Unfortunately, we found a problem...but this is entirely normal.
We tested a lot (a lot) of things during sample production. Run time was perhaps the only thing that didn’t get thoroughly tested. Thanks Murphy. Regarding run time specifically, I think I already said it, and I'll say it again later, but I didn't have any reason to suspect a problem. We tested output, mechanical design, the UI, the new switch boot, coatings, pocket clip, etc. Most of these changes went through between 2-5 revisions in the last few months. Unfortunately run time slipped through the cracks.
Posted Run Time Numbers:
This is an excuse, but bear with me: I don’t put much stock on run time in general (this is a personal thing) because run times are (in practice) exceedingly vague and inaccurate to begin with. Also, running a light on a single setting for the life of the battery is a bench test, but not typically how lights are used in the field. I've been using the MKIII daily for quite a while, and I never observed anything out of the ordinary in normal use.
Based on my measured numbers for the Beta, the actual run time on medium (15 lumens for both lights) should be about 4 hours. Right now the MKIII is hitting about 2 hours as reported. I won't know the actual expected run time until we identify the problem, correct it, and test. It might still be 4 hours, it might not.
I made the assumption (based on Foursevens' previous stated 1 hour run time on high for the old Preon) that we'd get roughly the same run time at the same drive current. I plugged those numbers into a spread sheet, along with the mA drive level numbers the factory supplied, in order to calculate the run time on medium and moonlight. In retrospect it appears that the mA settings I received from the factory (used in my calculations) are incorrect when cross referenced with my numbers from the Beta...bearing in mind they are different drivers with different designs. The erroneous 10 hour number was the result of bad data. What I failed to recognize at the time, is that the calculated 10 hour run time was significantly higher than what the Beta tests at...and I failed to notice that.
At this time there does appear to be a legitimate efficiency issue with the driver and I'm working on it. I'll also let you know when I have more information.
What now?
Realistically I think 4 hours "should" be decent estimate for run time on Medium, so the MKIII is missing that by about 50%. Once the issue is resolved (assuming it can be) you can send in your light and we'll fix it when we have the parts. You could also just use the light and not worry about it too much. Finally you can return the light for a refund.
I have changed the figures on the product page to match the Beta, which I believe is a reasonable estimate. I have also marked the run time table as "Estimated (Under Review)," though this is largely irrelevant at this point.
A few things to consider:
Totally my bias here: I'm a pragmatist – focused on real world use and not testing in controlled environments. Even at two hours on medium, the light is still quite usable under normal conditions. People who are actually using the light appear to be quite happy with it. I’m taking the issue very seriously, but it’s also not catastrophic functional issue. At the same time, I get it if that just doesn’t work for you.
Every light is a tool, and like all tools, they are suitable for different jobs. My point being, yes the light is eating batteries too fast, but for me it’s just not a deal breaker for a AAA pocket light. One, the battery is rechargeable and I charge/change mine frequently. Two, if I need more than what the Preon can deliver (run time or otherwise), I choose a different light for that situation. I'm still carrying the Preon daily and knowing the battery life is not what it should be won't prevent me from using/enjoying the aspects that make it awesome, and intermittent use greatly extends the effective run time. If your opinion differs feel free to send the light back or wait for a repair solution.
Again, my apologies if anyone feels put out by this. I was never my intention to deceive or deliver a product that wasn't performing correctly. We don't live in a world where everything happens by the book or as we plan it. Almost everything else went right, but sometimes it feels like I only get credit for the things that go wrong. Dealing with that comes with the job but I do want people to know, running a product company is by far the hardest thing I've ever done. It's hard every day. It doesn't get easier. In fact, it only gets harder. At the end of the day I'm just a regular person trying to do the best I can with what I've got.
As always, thanks for your understanding and support.
Jason