Sure you can add it, but managing version releases on the repository is something I won’t do. If I release a new version I’ll just switch out the zip file in my link.
What kind of license? I don’t know much about those things… as it’s for my own specific drivers I’d hope no one edits it and sends it off… But if someone actually builds any of my drivers they might want to change the code so they should. To be honest, with all the other cool driver projects floating around I don’t expect must interest in mine. I’m mainly releasing this stuff because I promised I would a long time ago
I wouldn’t expect you to manage the copy in the repository. I’m going with a model similar to Linux distros, where independent authors do their own thing and someone else pulls it all together into a curated collection.
Oh, the licensing thing can unfortunately be complicated. Most of that doesn’t really matter or apply unless it gets really popular though.
Copyrightable works default to all rights reserved. So, nobody can really do anything with it except personal stuff covered by fair use. Making it open requires at least a minimal license statement.
The opposite is public domain, when someone disclaims their copyright so that absolutely anyone can do anything with it. Although normally simple, this can be weirdly complicated in Europe.
The next simplest is a BSD-style license, which basically says anyone can do almost anything, as long as they preserve the copyright, license, and attribution. That’s the bare minimum required for it to really count as a license. Some argue this makes it the most free of all licenses. In practice, however, BSD code tends to get eaten by companies like Microsoft and Apple, who keep taking what the community provides but never give anything back.
I usually go for a GPL-style license, which adds the additional requirement that people must share alike. I.e. anyone who distributes the work (or derivative works) in binary form must also provide the sources. It keeps people from taking without giving back — they can use it, but they have to share their improvements. It also adds protections against a few abuses seen in the wild, such as Tivo-ization and patent trolling (see SCO vs IBM).
There are also quite a few others, each with their own quirks.
I know it’s a thing people don’t generally want to deal with (and it can be done later), but people can’t really use or share it without something giving them permission to do so.
Well, I don’t really consider it open for anyone to do what they want with it and send it on the others, but the people here seem to respect this no matter what license, and the ones that don’t respect it don’t really care about licenses anyway. I guess GPL sounds fair. Do I need to write something in the firmware for that?
Oh, and since you own the copyright, you can change or cancel the license any time you want.
I’ll grab the updated version before adding it.
You’re also welcome to change a branch of the repository and propose merges if you want. It’s extra effort and overhead though, so I normally do that part. And I’m still considering moving it from Launchpad (bzr) to Github (git), since git is more popular. Any preference?
If you are offering to do that part I certainly don’t mind not doing it… I can spend that time on firmware… or writing instructions for it (more work than one would think).
Just to make it clear, it's configured for a FET+1 driver, with a 350 mA 7135 (not 380 mA). This is an important detail for the ramping to work properly. Other ramping tables can be built and used easy enough to support 380 mA chips, or only FET, using TK's utility. In fact I need to modify it myself to work well on one of RMM's SRK 7135 drivers. Also moon mode would need to be changed/tweaked based on what you can use as the lowest PWM value, depending on the driver (FET, 7135 350 or 7135 380).
TK - if you get a chance, you can post it in the repository - your same GPL license that you use is fine. Think it's just an update anyways.
I think it's a 350 but not sure. Easy test is in Narsil, set a fixed mode (there are many sets with a max 7135 mode), then measure amps. Of the 350's and 380's we use (most bought from FastTech), the 380 is clearly labeled as 380 while the 350 is not.
I just flashed the new Narsil with ramp and replaced R1 & R2 with 220K & 47K resistors. Those 0805’s are some little pieces to solder!
Firmware is great. Ramping is a really nice feature!
I have a few issues though…
On battery check mode, I now get 1-1 blink (1.1V?). On the “old” Narsil before the resistor mod, it worked really accurate.
Also the parasitic drain still reads 0.01A on my UT210E.
Maybe some resistor has got a bad solder joint? Or won’t the driver work at all in that case?
Edit: On 100% 7135 the tailcap measures 350mA, so that should be O.K.
The 1.1V blink means an error happened and it couldn’t measure voltage. If you flash battcheck.c onto it, it’ll probably blink out 255 every time. It’s almost certainly a physical problem somewhere on the driver, but I’m not sure where exactly.