Why this matters

If power is capped or full power occurs too early, compare LightBurn S-value maximum with $30 before changing recipes.

GRBL/firmware behavior can differ between forks such as FluidNC and grblHAL; verify the exact firmware when a setting or status field differs.

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

  1. Define the result you actually need, then confirm the active machine profile, units and operating mode before changing parameters.
  2. Change one meaningful variable at a time and use Preview/Frame or offline analysis before running a real job.
  3. 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

If power is capped or full power occurs too early, compare LightBurn S-value maximum with $30 before changing recipes.