RGB+W NeoPixel strip error

Open
#299 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
40/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript
Domain
embedded-iot

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.

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.

https://forums.adafruit.com/viewtopic.php?f=64&t=163743

Dominant language
TypeScript
Stars
130
Forks
90
Avg merge
1d 14h
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/pxt-maker

All issues in microsoft/pxt-maker

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.