Why this matters
Validate dash/gap at final physical scale; very short segments may be limited by machine acceleration or material behavior.
How to think about it
Define the result you actually need, then confirm the active machine profile, units and operating mode before changing parameters.
Practical workflow
- Define the result you actually need, then confirm the active machine profile, units and operating mode before changing parameters.
- Change one meaningful variable at a time and use Preview/Frame or offline analysis before running a real job.
- If the issue repeats, keep evidence: Console output, a G-code sample, the exact settings used and material context. Evidence makes troubleshooting reproducible.
If the result is wrong
Validate dash/gap at final physical scale; very short segments may be limited by machine acceleration or material behavior.

