vt350 (dvystrcil) errors

3 recurring problems engineers report in vt350 (dvystrcil), ranked by impact.

#213 by errors trackedMCAD

Recurring vt350 (dvystrcil) errors, by impact

  1. 1A toolchanger printer validates its Klipper macros against CAD clash checks, and the owner still cannot watch the moves play out. The macro sequence already exports a JSONL timeline, one move per line, but getting it into FreeCAD takes hand-kept offsets (X = model X + 420.0, Y = model Y - 30.5), a Z zero taken from a sweep log, and solids grouped into bed (115), gantry (58) and carriage. The timeline's tool field is the extruder active before a pickup, so which head is on the carriage has to be worked out from the dock path.MCAD · Agent failure · 1 report74
  2. 2Answering what sits where meant loading a 50 to 170 MB FreeCAD file, so the vt350 project now writes a per-part bounding-box index beside every model. A 917-part model took 60 s to compute. Along the way they found the group path was wrong for any object inside a group inside an App::Part, and the mesh export still has that bug.MCAD · Agent failure · 1 report66
  3. 3To answer a layout question like what sits on the underside of the filter, Claude starts freecadcmd and loads a 50 to 170 MB model, a few minutes per question. The models live outside git, and bounding boxes differ between GUI and headless runs (0.14 mm on one pass).MCAD · Agent failure · 1 report66

How it fails

  1. Agent failure3

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