EasyAVR
EasyAVR copied to clipboard
dhowland
Add RGB LED (WS2812B) and 62/60 support
Adds RGB LED support.
The process is fairly convoluted, but works decently well. Since setting RGB values in the GUI is tedious (there isn't a good way to select multiple keys at once), the task is delegated to keyboard-layout-editor instead. After some setup in the board file (described in RGB_README.md), a configurator like this one can be used. The raw data is then imported into EasyAVR and parsed.
Current limitations: 160 RGB LEDs (due to power draw, no board is likely to hit this number ever), solid colors only (no effects), only port C is guaranteed to work, and KLE is required.
Additionally, support for the 62/60 keyboard is added, including RGB configuration.
Yep- works perfectly on my 62/60 boards. Every LED is correct and brightness is limited correctly (which means current is limited).
Any updates on this? I'd be willing to distribute this separately if you could help me out with py2exe.
Yeah, uhh.... I've been away from this project for a while because DOOM came out last week. Sorry, I will get to this.
Hate to bring this up again, but it's been a very long time. If you don't have time to review the commit, I'm willing to package & distribute this fork myself.
This patch, as it exists now, appears to be insufficient for general inclusion in the project. It looks great for your particular board, however the port and pin (C7) is permanently configured in ws2812_config.h and this could not be changed with the keymapper tool for other boards that do not use this pin.
Okay, I see, it's not restricted to C7 for all applications, just PORTC like you said. I wonder if there is a way around that, though.
guys not to be weird about it - but is this going to happen or is this diamond not going to be cut?
The project is dead at this point, so I'm okay with keeping this as a fork. @dhowland can do whatever he wants.
@dkave I already commented on this patch (see above, Feb 12th). This project covers many different boards with varying hardware. Anything in the firmware itself must be made general-purpose. This patch isn't. I kept the pull request open in case @edfan wanted to continue to work the code. It appears he does not.
You can still use his fork for the 62/60 support.
@edfan + @dhowland i understand your point and would do it but cant code worth a %^&* too bad guys - would have been a very cool addition