armature (rioharper) errors

5 recurring problems engineers report in armature (rioharper), ranked by impact.

#88 by errors trackedMCADVerification

Recurring armature (rioharper) errors, by impact

  1. 1Close the loop names no source for an off-the-shelf part's mass and center of mass, so a torso that is 2.4 kg vendor parts in 4.6 kg total has no honest COM.MCAD · Agent failure · 1 report74
  2. 2The armature-cad skill tells the agent to confirm 'the fabrication reality', meaning in-house machining envelope, printer, sheet stock, bend capability and minimum drill sizes, but it names a file only for an outside shop's questionnaire. The in-house limits and a shop's published limits have no home, so each project invents one.MCAD · Agent failure · 1 report74
  3. 3The SOLIDWORKS equations file mirrors the project ledger, but nothing fails when it falls behind, so a changed entry can merge with the old value still in the file.MCAD · Agent failure · 1 report74
  4. 4An agent skill set routes findings that move a requirement, part or BOM number back to the spec, but the spec skill only knows how to write a first spec. On one project "two revisions, each improvised." One wrote its account in a closing comment, the other in a side report that maps each routed item to spec text and lists deferred ledger edits.MCAD · Agent failure · 1 report66
  5. 5Running the spec plugin end to end on a test project turned up a list of gaps, each with the workaround used now. The drive envelope says 'winding hot' but reads the winding at starting temperature when the motor has no thermal model. A source's overvoltage trip stops both sourcing and sinking, while a real BMS opens only its charge path. The motor has no peak torque field, so stall is computed as Kt times peak current, past the printed peak.Verification · 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.