Why this matters
Do not make the bed “bigger” in $130/$131 to silence the alarm. First compare job bounds, Start From, MPos/WPos, homing and real travel.
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
Do not make the bed “bigger” in $130/$131 to silence the alarm. First compare job bounds, Start From, MPos/WPos, homing and real travel.
Common mistakes
- Changing several settings at once and then not knowing which change affected the result.
