carbon (crbnos) errors

4 recurring problems engineers report in carbon (crbnos), ranked by impact.

#118 by errors trackedPDMMCADPLM

Recurring carbon (crbnos) errors, by impact

  1. 1A follow-up PR reports that an assembly push exported only the assembly's own STEP, child items got a link and no file, and nothing tied a drawing to the part it shows. Known limits stay: a Variable Studio or derived Part Studio can change a part without changing its own Part Studio, and drawings kept in a separate document are not found.PDM · Agent failure · 1 report74
  2. 2Carbon is an open-source ERP/MES. In its Onshape push, a chosen Item column that was blank on a line made that line read as the root, and the push deleted BOM lines. A blank or non-numeric Quantity column wrote 1, and a release push could export a model onto a revision held by a locked change notice.MCAD · Agent failure · 1 report74
  3. 3The Carbon ERP Onshape panel read part number, revision and the BOM's Item and Quantity columns by hard-coded labels, so a company whose BOM template relabels a column, or keeps part numbers in a custom property, had no way to point it there. This is a CAD-to-ERP handoff that breaks on each company's own conventions.PDM · Agent failure · 1 report74
  4. 4Onshape push into Carbon's ERP now exports a STEP for every BOM row and attaches drawing PDFs to the items they show. Part-defining elements are hashed separately from assemblies, drawings and BOM tables, because before this a drawing edit read as a change to every part.PLM · Agent failure · 1 report66

How it fails

  1. Agent failure4

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