After entering a decimal value, leave the field and read back the number the software actually retained. Include the unit. A comma or point can be interpreted differently across applications, versions, and regional settings, so a familiar-looking entry is not enough evidence to release an X1S Pro job.
The LightBurn 2.2.00 RC1 early-access changelog identifies changes to decimal parsing and thousands display. That version-specific note is a reason to verify numeric interpretation; it is not a universal rule that either separator is always accepted.
Use a harmless geometry value first
For a new workstation or changed software environment, open a disposable copy of a project without starting machine output. Enter a distinctive noninteger dimension on a simple rectangle. Move focus away from the field, select the object again, and inspect the retained width. Compare the measured geometry with the intended value.
For example, an intended width of twelve and a half millimeters is easy to distinguish from twelve, one hundred twenty-five, or twelve thousand five hundred millimeters. This is a dimension example, not a recommended speed, power, or machine-control value. Use the application's supported notation once you have established how it behaves.
| Job record item | What to write |
|---|---|
| Intended quantity | Number expressed unambiguously |
| Unit | Millimeters, seconds, or the actual field unit |
| Retained display | Value shown after leaving the field |
| Software environment | Application version and relevant locale |
| Saved-file result | Value displayed after reopening the copy |
Do not combine an application update, locale change, and process-setting revision into one acceptance test. If the result changes, you need to know which change caused it. Keep production settings untouched while establishing entry behavior in the harmless geometry example.
Carry the units through the handoff
A screenshot can show the field and unit together, but an operator still needs the saved project and the exact version used. For multiple project pages, add the active-page output record. This prevents an accurately entered value from being associated with the wrong output page.
Small dimensional adjustments deserve the same attention. The generated kerf path check distinguishes a value applied by a layer from one already embedded in geometry. A correct separator cannot repair compensation applied twice.
Use the TYVOK X1S Pro product information to confirm the selected machine and supported workflow. Do not infer safe processing settings from numeric-entry examples. If communication fails during a real job, follow the safe-state-first status recording procedure before troubleshooting values.
Questions about numeric entry
Can I paste a value directly from a spreadsheet?
Only after verifying what the receiving field retains. Spreadsheet formatting may include separators, spaces, or units that are interpreted differently. Read back the saved value and compare a harmless geometry example before transferring production parameters.
Is a rounded display proof that the stored value was rounded?
Not necessarily. Display precision and stored precision can differ. Use the application's documented controls and a saved-file readback to establish the behavior. If the needed tolerance cannot be verified, hold the job rather than guessing from the visible digits.
