The STEP importer never reads LENGTH_UNIT, so a metre file imports 1000 times too small and an inch file 25.4 times too small, with no message either way. Such a part generates, verifies and posts a correct-looking CAM program at the wrong size, and no import scale command exists to fix it after the fact.

Recurring agent failure issue in Camcraft (NeoTech)

Camcraft (NeoTech)MCADAgent failureMedium confidence

What engineers report

A recurring agent failure problem in Camcraft (NeoTech) that mostly hits the mechanical designer.

Failure pattern: agent / failure

Analyst note

From the Grok pain-radar digests, Nov 8-9 2026 (Nov 8 8:41 AM ET through Nov 9 6:41 AM ET digests plus the Haitch editions). Verified live 2026-11-09: issue/PR read; title and state confirmed.

What it costs a team

Modeled annual cost

$30,000

For a team of 5

Prototype delay

3 days

Modeled schedule slip per occurrence

Time lost

240 min

Per engineer per month, about 1 incidents

How the cost is modeled

240 min/month × 5 engineers × 12 months = 240 hours × $125/hour = $30,000

A modeled estimate with medium confidence. Swap in your own team size and loaded rate to size it for your team.

Engineering tools that address it

No engineering tool profile lists this error yet. Browse tools that connect to Camcraft (NeoTech).

Evidence

  1. 1NeoTech/Camcraft Issue #306: STEP import ignores the file's length unit: a part saved in inches or metres imports 25.4x or 1000x too smallgithub.com

More recurring errors in Camcraft (NeoTech)

See all 7 Camcraft (NeoTech) errors

Sourced from public community reports. Costs and delays are modeled estimates, not measurements. Know a better source or a fix? Tell us at hello@productflo.io.