Skip to content

fix: correct SK6812 RGB LED footprint mismatch - #49

Merged
thePunderWoman merged 1 commit into
mainfrom
fix/rgb-led-footprint-mismatch
Sep 12, 2026
Merged

thePunderWoman merged 1 commit into
mainfrom
fix/rgb-led-footprint-mismatch

Conversation

@thePunderWoman

Copy link
Copy Markdown
Owner

Summary

  • PCBWay rejected assembly of the 5 current boards: the D_RGB1 (SK6812MINI-E RGB LED) footprint didn't match the real component.
  • Root cause: the schematic still had a stale generic LED_SMD:LED_SK6812_PLCC4_5.0x5.0mm_P3.2mm footprint from before the design settled on the SK6812MINI-E — it never got updated when the part was chosen.
  • Added a custom footprint (SnipsControllers_Custom:SK6812MINI-E-012) built from the real OPSCO SK6812MINI-E-012 datasheet dimensions rather than trusting KiCad's stock library footprint.
  • Updated the schematic and yaml to reference it, and reworked the PCB placement/routing for the new pad geometry.

Test plan

  • kicad-cli sch erc clean
  • kicad-cli pcb drc — 0 violations, 0 unconnected items
  • Verified DIN track physically terminates at the new footprint's pad coordinates (not just net-name bookkeeping)
  • User to confirm physical fit against a real part sample before next fab run

🤖 Generated with Claude Code

…embly

D_RGB1 was still using a stale generic 5.0x5.0mm PLCC4 footprint left
over from before the design switched to the SK6812MINI-E, which is what
PCBWay's assembly check caught. Added a custom footprint sourced from
the real OPSCO SK6812MINI-E-012 datasheet, pointed the schematic at it,
and reworked the PCB placement/routing to match. DRC clean, 0 unconnected.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@thePunderWoman
thePunderWoman merged commit c764078 into main Sep 12, 2026
2 checks passed
@thePunderWoman
thePunderWoman deleted the fix/rgb-led-footprint-mismatch branch September 12, 2026 20:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant