Why this matters

Separate “LightBurn is not commanding power” from “controller commands power but hardware does not emit” using Preview/G-code/Console and manufacturer-safe tests.

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

Separate “LightBurn is not commanding power” from “controller commands power but hardware does not emit” using Preview/G-code/Console and manufacturer-safe tests.