If an X1S 2026 job frames but stops as output begins, preserve the first error and the surrounding console text before changing anything. Successful framing establishes only that the observed framing action occurred. It does not verify the output configuration, connection health or readiness to process material.
In an April 2026 LightBurn case, a Creality user reported framing followed by an immediate stream error. Their code and subsequent profile experiments are not X1S 2026 diagnoses or remedies. The transferable practice is retaining the first failure evidence before repeated attempts obscure it.
Preserve the failure in the order it happened
Leave the machine in a safe stopped state. Do not resend the job just to reproduce a message already available in the console. Save the visible text, a screenshot and the source file. If the console includes personal paths or customer information, keep a complete private copy and redact the version shared outside the support channel.
| Support record | What to capture | Why it matters |
|---|---|---|
| First error | Exact text, referenced line and preceding messages | Later messages may be consequences of the first failure |
| Time and operation | Timestamp; frame, start and stop observations | Distinguishes an immediate abort from a mid-job interruption |
| Software context | Application version and selected device/profile name | Records the configuration without changing it |
| Connection state | Connection method and displayed status | Shows what the application reported at failure |
| File identity | Filename, saved copy, intended layer and action | Lets support compare the same input |
| Machine identity | X1S 2026 configuration and installed module | Prevents advice for another controller or model |
Record uncertainty explicitly. “No visible mark observed” is more accurate than “the laser received no command” when you did not measure the command. Do not reach into the machine or look for emission at the head to settle that question.
When a control-file result is appropriate
Include a previous known-good file result if one already exists. A new control-file attempt is appropriate only when current TYVOK guidance permits it and the machine is safe to operate. It requires identified compatible sacrificial material, documented setup, extraction, operator protection, fire controls and continuous attendance. Do not clear an alarm or defeat a safety condition to obtain that result. Mark the field “not run; awaiting guidance” when those conditions are absent.
The X1S 2026 page still distinguishes product positioning from final launch specifications. It is not a basis for guessing controller flavor, firmware, wiring, limits or device settings. Give the preserved evidence to TYVOK support for the appropriate configuration-specific procedure.
Separate nearby symptoms
Output that ran and then lost its connection raises a different evidence question. The X1S Pro interruption record illustrates that distinction, but its recovery actions must not be transferred to X1S 2026. A paused long board raises a registration-trust question. Visible output that shifts sideways needs a placement comparison. Keep those histories distinct in the support record.
Should I try another controller profile from a forum?
No. A profile that helped another machine can change commands sent to yours. Preserve the current profile name and request the procedure appropriate to your actual configuration.
What if I closed the console before saving it?
Keep the file, versions and observations you still have. Report the missing error text honestly. Ask support how to capture further evidence safely instead of repeatedly restarting the job.
