I have heard it works but I have all the windows store and other tracking features disabled. removed, deleted, and annihilated from my systems, at least as much as you can do without messing up the basic functionality. so I can’t use it.
Everytime I use a full fat version of windows 10 I get creeped out in a major way.
Exactly the same reason that I can’t switch, that and Adobe.
Not to mention the insistence on using the terminal for even basic tasks in Linux. Once they have reached windows levels of GUI integration it will be a lot more practical to switch. I just don’t have time to memorize all the terminal commands.
Oh, I love having the Terminal in linux, just like the command prompt in windows.
What I hate is the requirement to use the terminal for even basic things in linux. It is 2018, it should be like windows where you can do basically everything with the GUI but have the option of using the terminal if you want.
For example I have quite a few batch files and scripts for tasks that I do a lot along with commands memorized for those tasks. But for anything I only do every now and then, I just use the GUI, it is easier then trying to memorize the commands.
For the record, I started out using DOS on an 8088, I know the power of a terminal interface but I also know the memorization and time it requires to be used fluidly. GUI is simply quicker and simpler for 98% of users and even advanced uses it doesn’t make sense to memorize commands that you might use once a year. Better to just use the GUI.
Mine compiles fine with the #if in VS 7.0. This is why I always distribute the full source with the associated solution and project files so it's all set to go in VS 7.0.
I have been compiling and flashing for good part of the day. Did some minor code changes(reduce brightness on momentary) just to see if I could. Getting ready to put Anduril into a Wowtac A2. My TA driver from Lexel should be here early next week. I am really having a good time with this. I am a long way from writing my own code but this is getting me one step closer.
My first post here. First of all, I would like to say big thanks to all the people behind the BLF A6 project, especially ToyKeeper for providing the firmware source and pin diagrams.
As I was looking for a good mountain biking helmet light, most of the ones I found were either too expensive ( eg. Exposure ) or weak/large/heavy/poor quality/inpractical… you name it. I found the BLF A6 which looked perfect, although I found it a bit hard to use while riding and hated the time limit of the turbo mode, so I decided to fork, refactor and heavily modify the original firmware.
I would like to give something back to the community there, so I decided to publish this firmware and share it with you. You can find the features, source code, build & flash instructions etc. on my GitLab: Patrik Gajdoš / A6-MTB · GitLab
I imagine it should be possible to just move the candle mode EV_tick handler into the main loop somewhere and put a 16ms delay at the end to keep the timing close to the original.
It could also be interesting to try to get FSM working on clicky-switch lights, but I’m not sure how much it would really help. It’s weird having the controller suddenly reboot all the time.
Using the “bzr diff” command might show a few possible reasons. It sounds like something changed, but it’s hard to say what.
It might also be useful to increase the THERM_WARNING_SECONDS to a higher number to make it trigger overheat events less often. For a big light with a lot of thermal mass, the default of 5 seconds might be too fast.
I’ve got several patches to merge, including this one. Hopefully I’ll get to that soon.
In general, make a copy which mirrors the upstream trunk, and don’t edit that copy. Then branch that into a copy you do development in. Check in changes as you go along in the development process. Then when you want updates from upstream, go into trunk and do a “bzr pull”. And then to merge that into your dev branch, go to the dev branch and use “bzr merge …/trunk” to get it to merge the upstream changes along with your changes. Most of the time it should merge cleanly and then you should be able to commit the merge immediately.
If there are any conflicts though, things get more interesting. Gotta look for the conflict markers in any files listed as a problem, the fix the problem, and tell it “bzr resolved foo.c”. Then it should be able to be committed.
Calibration is not optional.
I tried to set the default calibration toward the safe end of the range of expected values though, so in general it should be stepping down early by default instead of late.
That’s on my list too. I should be able to test it on a FW3A driver.
The minimum number of supported modes is 2. It doesn’t even try to handle the case of only one mode. I’m not really sure what would even make sense for it to do when it only has one mode, since the floor and ceiling are generally not the same number. Maybe it could set floor and ceiling to the same value, using whatever is halfway between the two?
Fireflies worked with some BLF people to make lights. After releasing the ROT66, Fireflies contacted me to see if I could make a simplified version of NarsilM for their next light, so I told them I already did and it’s called Anduril. So they started using that.
About Mateminco, I have no idea. I think they probably just bought stock BLF-X6 drivers from Banggood. I’d like it if I can get them to comply with the license requirements, but I haven’t spent much time yet trying to get in contact about it. There are always too many license issues to chase down.
While it’s largely a matter of personal preference, I have similar complaints about GUIs. It doesn’t make sense to bother learning a completely new way of doing everything every year or two when I can learn a CLI method once and never have to care about it again. The GUI methods for things seem to change a lot for no reason, while most CLI tools pick a rational method once and then stick with it for decades.
That’s always good to hear. It’s what BLF is all about.
Thanks! I’ll add this to my list. Also, welcome to BLF!
BTW, if the forum tells you anything about having a “reported post”, it probably just means someone felt the need to report swearing. There’s a rule against that here. I think it’s a bit silly, but these things really bother some people.