microsoft / microsoft/pxt-maker
RGB+W NeoPixel strip error
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 130
- Forks
- 90
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 1
Description
Setting a NeoPixel strip to RGB+W seems to create errors in simulator and hardware.
strip.setMode(NeoPixelMode.RGBW)
let short = strip.range(0, 1)
let long = strip.range(2, 1)
short.setAll(0x0000ff)
long.setAll(0x00ff00)
This should show pixel 0 green, pixel 2 blue, but instead shows pixels 0-1 both blue.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the example using light.createStrip, setMode(NeoPixelMode.RGBW), range, and setAll in both the simulator and on hardware. Trace RGBW range handling and verify that pixel 0 becomes green while pixel 2 becomes blue, rather than pixels 0–1 both becoming blue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- embedded-iot
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 40/100