compose-keyboards (edulpn) errors

3 failures reported against compose-keyboards (edulpn), sorted by how they fail and ranked by impact.

#169 by errors trackedElectronics & PCB

Recurring compose-keyboards (edulpn) errors, by impact

  1. 1Checking the rev 2 cable against Molex's drawings showed the 50 mm FFC ribbon did not fit, so it became a custom flex jumper. Along the way a connector pad sat 0.21 mm from a socket tab (now 0.6 mm), and F1's top-side solder joint sat under the other connector, which the placement check missed until it learned to compare pad copper against the opposite face's courtyards.Electronics & PCB · Wrong verdict · 1 report74
  2. 2A review of a keyboard's board generators and checks: two DRC commands printed their counts and exited 0 no matter what, a jumper row was solved in a second imported copy of a module so the command kept a cached 0.72 start value that ends up 1.0 mm off at 6 degrees of splay, and the cache key ignored the tent angle so a row computed for one tent got reused for another. The crosstalk sweep still listed a net that had been renamed. Every one of these looked fine from the outside.Electronics & PCB · Wrong verdict · 1 report66
  3. 3Follow-up to PR #6: the LED orientation check took each pin's position from the board plan's own table, so a wrong table passed, and it now reads what each lead connects to from the copper and compares against two published SK6812 MINI-E footprints. Every routed via had also come back at the default 0.6/0.3 mm instead of the size the router placed, and a truncated ngspice run was being analyzed as if it had finished. A check that reads its answer from the same source as the design cannot fail.Electronics & PCB · Wrong verdict · 1 report66

How it fails

  1. Wrong verdict3

Sourced from public community reports. Costs and delays on individual entries are modeled estimates, not measurements.