OpenSkyhawk (OpenSkyHawk) errors

6 recurring problems engineers report in OpenSkyhawk (OpenSkyHawk), ranked by impact.

#77 by errors trackedFirmwareECAD

Recurring OpenSkyhawk (OpenSkyHawk) errors, by impact

  1. 1CAN interrupts were never enabled at the NVIC, so RX was polled behind a 3-frame FIFO, overran 656 times in one run, and lost about 14% of inputs on the wire.Firmware · Agent failure · 1 report74
  2. 2A doc-check tying file:line citations to firmware code skipped anything not shaped exactly like file.ext:N, so a broken row passed CI and a comma-list citation had drifted 4 lines and no longer pointed at the guard it named.Firmware · Agent failure · 1 report66
  3. 3An agent skill told every session to use STM32F103CB for PanelBridge though every build target has been the C8 since PR #368, and the stale part number had spread into the KiCad scaffold command, a README, and protocol docs.Firmware · Agent failure · 1 report66
  4. 4board rev 0.2.0 was fabricated with 33 Ω UART series resistors, so whichever chip is unpowered gets back-fed tens of mA through its ESD diode; the PCB file also had no title block at all, so the sheet frame never showed a revision.ECAD · Agent failure · 1 report66
  5. 5the RP2040 gateway's USB link wedges and only a replug fixes it; the board runs only from USB-C, so the replug is a power cycle and all in-RAM evidence is lost. Seen on two boards, pointing at firmware, not one PCB.Firmware · Agent failure · 1 report66
  6. 6Status LEDs on every 3.3 V board were too dim next to the PDU's, forcing a cross-board series-resistor change from 3.3k to 1k.ECAD · Agent failure · 1 report58

How it fails

  1. Agent failure6

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