Pretty much all PWM-based lights will whine, especially on medium modes. However, the fast PWM setting is a high enough pitch that most humans can’t hear it. If you can hear a faint 19 kHz tone, you must have truly exceptional hearing.
One other possibility is perhaps you’ve flashed it with the wrong fuse settings? That will change the MCU speed and thus the PWM speed. It should be “-Ulfuse:w:0x75:m -Uhfuse:w:0xFF:m” for a low fuse of 0x75 and high fuse of 0xFF.
As a child my doctor thought I was partly deaf. Looked at my mom like “Poor woman, doesn’t realize her child can’t hear”.
Test results, exceptional hearing. Beyond the average range. The doctor had been pretty sure but I wasn’t deaf, I was just ignoring him. Likely wasn’t saying anything that interested me. My mom knew it but it was more amusing to let the results inform him.
As long as its faint, 19 kHz isn’t too annoying. For me at least, high frequencies lose much of their volume if an ear isn’t actually facing toward the source.
This is not final; it’s just what we’re working with so far. At the very least, all the hardcoded values will be recalibrated to fit the production samples when they arrive, and there may be other changes as well.
At that link, the .txt file describes the interface in detail. There is also a .png with a UI diagram, but it’s a bit out of date.
As for getting to the battery check mode, the sequence is: Fully click to turn the light on, medium tap (turbo), med tap (strobe), med tap (battcheck). The reason they are in this order is because it gives the fastest access to turbo, which gets used a lot. After that, the fastest access is strobe, which tends to be needed quickly when it’s used. Battery check / beacon is usually less urgent.
I doubt it, that is quite a different undertaking, once someone starts doing that he/she can count on quite a mass-production. Led4power can not keep up with the demand for his LD1 driver either. Ledsmoke has a too busy life to continue his BLFDDdriver service.
Perhaps Richard will pick up this driver with this firmware once it is finished?
Personally I would happily settle for pre-flashed Attiny's, that should be a lot less work. But if needed, Richard does that service too.
It sounds likely that there may be a group buy for a firmware tool kit, and the code is available, so if anyone wants to change the modes or UI it should be reasonably straightforward to do.
I’m not interested in selling drivers. Aside from never having actually built one, I think selling stuff would take the fun out of this hobby. But I’m happy to keep making code for people to use.
In any case, the mode groups in the current version are:
No production samples have been made or tested yet, so we don’t have any confirmation on final specs. All info so far is about prototypes and what we hope to build.
Nope, that’s it. The group buy is over. You had to go and mention “the dress”, the symbol of everything wrong with the modern world. Now we’re doomed to an eternity of stock 2.8A nanjg drivers with on-time memory and blinkies in the main sequence.
As usual I don't know what is going on in the last few posts. I would suggest that if you all readdress the problem that the problem will be addressed.