Issue #245: Allow control of more than one on-board pixel via `led` commands

Development
12

Yes, the firmware has a mandatory divisor, and you can’t bypass it via manually editing the configuration file. This is why I scaled by 81 / 255 in the table. And as you discovered, the config file stores the color directly … you can set any RGB value.

It seems you confirmed the values for full-on / white / 0x00FFFFFF aligned with the expected 0.12mA per LED (0.36mA per pixel). :tada:

I believe that you did do this, Ian. :slight_smile:

  • 18x pixels on white, with 1/3 limiter ~= 218mA (see table in first post / github).
  • BP5 idle uses ~120mA
  • Default current limiter for W is 300mA

Thus, with default settings, a BP5 might pull >640mA from the USB port for its current limiter kicks in…

Options (long-term):

  1. Have W/w commands announce its current limiter changes (before raising / after lowering), and have rgb.c dynamically adjust.
  2. Reduce limit in rgb.c to ~150mA.
  3. Do nothing.
2 Likes