hardware-splicer (Spectating101) errors

6 recurring problems engineers report in hardware-splicer (Spectating101), ranked by impact.

#74 by errors trackedFirmwareECADVerificationMCAD

Recurring hardware-splicer (Spectating101) errors, by impact

  1. 1Generated firmware ignored the pins the design actually wired: a composed ESP32 design with two servos on GPIO15 and GPIO16 got a sketch that only blinked the built-in LED and never touched either pin, with nothing flagging it.Firmware · Agent failure · 1 report74
  2. 2A live trial picked a generic drive base, passed case-level DRC, and the compiled BOM then failed manufacturing reconciliation. In the author's words, a DRC-clean generic placeholder can look like a completed hardware solution even when it does not satisfy the actual case.ECAD · Agent failure · 1 report66
  3. 3A real Gekkio Game Boy KiCad netlist grounded the model's reasoning, and the Gemini reply recommended DC1 pin 3 to pin 4 continuity tests, while the physical board's revision was only publisher-reported. A source-correct pinout is not authorization to operate on a possibly different physical board. The fix gates pin-specific actions until the board revision is checked.ECAD · Agent failure · 1 report66
  4. 4Asked for a board with two identical I2C sensors, the tool used to build a design that could not work and call it ready; it now detects the address clash and either moves a device to a second bus or flags "Electrical problem".ECAD · Agent failure · 1 report66
  5. 5Loading OpenArm v1.0's own collision STLs into PyBullet, 73 of 73 trajectory frames show contacts between the same five link pairs. The author refuses to authorize any robot or workcell operation until the source geometry or start pose is diagnosed.Verification · Agent failure · 1 report66
  6. 6Replaying the pinned OpenArm URDF and collision STLs found 5 penetrating link pairs at the initial pose. Opening the fingers drops it to 4 but adds a finger-body overlap. The best park pose still leaves 2, and they refused to safe-list them.MCAD · Agent failure · 1 report66

How it fails

  1. Agent failure6

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