adafruit / adafruit/Adafruit_Wippersnapper_Arduino
Support RGB status LED on the BitsyWing Airlift
- Dominant language
- C++
- Stars
- 54
- Forks
- 56
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 11
Description
Not quite sure what I'm asking for here, but it keeps reoccurring to me so sticking it here for now in undigested form.
Initially I wanted the status LED for wippersnapper to be pointed at the AirLift RGB LED instead of the ItsyBitsy RP2040 neopixel (which is stacked beneath). (There's support for using it easily built into the airlift library, and it doesn't feel too much of a stretch to add StatusRGBLED type, but unaware of other boards needing it).
I think I do want that too, and we currently don't support 4pin RGB LEDs for status LEDs, but this is probably more a ticket to do with beginning pondering about how to expose an RGB LED from a connected daughter-board to the components web interface too.
In effect having the RGB LED that's onboard the airlift as a usable RGB LED component for the user. (I wanted that for a project but will probably pick a QTPY instead as a result of the ItsyBitsy neopixel being obscured by the airlift, or switch to circuitpython)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading the AirLift library's existing RGB LED support and the current status LED and components web interface paths; the issue names no files or tests. Clarify whether the goal is only using the AirLift LED for WipperSnapper status, exposing it as a user RGB component, or both, then define completion and tests for the chosen scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- arduino, cpp
- Domain
- embedded-iot
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100