workbench-mobile-home-robot (Quchaosheng) errors

5 recurring problems engineers report in workbench-mobile-home-robot (Quchaosheng), ranked by impact.

#109 by errors trackedVerificationMCADECAD

Recurring workbench-mobile-home-robot (Quchaosheng) errors, by impact

  1. 1A robot BSP readiness gate counted as PASS as soon as its evidence path pointed at any file in the repo, so README.md could mark all nine gates PASS and set physical_release_ready to true.Verification · Agent failure · 1 report74
  2. 2Six safety-critical nets, including GND_PWR, MOTOR_ENABLE_SAFE, and both e-stop returns, could be marked physically VERIFIED with hardware/pcb/README.md as the evidence, because the only check was that the file existed.MCAD · Agent failure · 1 report74
  3. 3The release-gate check accepted any status string and accepted pass: false, so a package truthfully saying it was not complete was read as valid approval evidence. The fix gives each package its own status vocabulary and requires pass to be true.MCAD · Agent failure · 1 report74
  4. 4Simulation runs got a random uuid as identity, so two runs of the same world could not be compared, and the path a caller asked for and the world actually loaded could silently differ.Verification · Agent failure · 1 report66
  5. 5The robot's generated controller schematic and PCB still carry a CH32V307 (7 matches in the schematic), and the electrical spec budgets a "CH32V307 and logic" load on 3V3. The BSP manifest has already moved to an STM32G474RET6 and lists the MCU change as unresolved. The generators will keep producing the old part until the part data changes, so the release-readiness gate is reporting on a board nobody plans to build.ECAD · Agent failure · 1 report66

How it fails

  1. Agent failure5

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