basecase (JamelHammoud) errors

4 failures reported against basecase (JamelHammoud), sorted by how they fail and ranked by impact.

#118 by errors trackedMechanical

Recurring basecase (JamelHammoud) errors, by impact

  1. 1An SO-101 with six servos already on hand read about $127.48 instead of about $7.48, because the BOM priced every part as if bought again. The fix adds owned counts to the BOM, the budget, exports and the agent's get_bom/record_on_hand tools.Mechanical · Wrong design output · 1 report66
  2. 2In a robot-design tool, the BOM added one generic 5264 cable pack whenever a scene had a servo, with no count, no connector match and the wrong cable for DYNAMIXEL robots. Now the wiring netlist comes from connector ports, the BOM counts one cable per servo bus hop of the right type, and a new check blocks a build when no adapter takes a servo's connector. The mechanical scene and the purchasing list were not talking until they wired a netlist between them.Mechanical · Wrong design output · 1 report66
  3. 3In basecase, the only way to mark a part as not printed was a CNC aluminum or laser-cut tag, and both listed the part as needing a source, so Checks counted it as a blocker. The new sheet option feeds the sheet's density into weight, servo torque and the MJCF, adds a Sheet BOM section and exports one DXF per part, and a part set to sheet that is not flat gets blocked.Mechanical · Missing capability · 1 report66
  4. 4Most first robots start from a kit someone already bought, such as six STS3215s and a Pi, but Basecase priced every design as if everything had to be bought. Now owned parts count at $0, exports show owned beside to-buy, and the agent picks owned parts first and can record counts from pasted order confirmations. Inventory was living outside the design. Third basecase BOM item today after #305 and PR #583.Mechanical · Missing capability · 1 report66

How it fails

  1. Wrong design output2
  2. Missing capability2

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