Standard Procedures · Workflow & Operations
Diagnose a failed print
Record the symptom. Change one thing. Compare the result.
In this procedure
The result
A fault record that supports a controlled retry or technician handover.
Before you start
- The machine has stopped safely; do not inspect moving or hot components.
- Access to the original project, material identification and the profile used.
- A known good result or a small representative test where available.
The essentials
A defect can have several causes. Changing several things at once may improve the print, but will not tell you which change helped.
Who it is for
Operators who can safely run the machine. Repairs and advanced calibration need the relevant training.
Follow the procedure
- 1.
Describe what happened
Record where the fault appeared and when. "Corner lifted" is an observation; "wrong temperature" is a possible cause.
Check: Another person could recognise the symptom from your description and photo.
- 2.
Capture the starting conditions
Save the project, profile and material details. Record the machine, nozzle and plate. Photograph the fault and copy any error text.
Check: The failed run can be distinguished from the next attempt.
- 3.
Check the preview and recent changes
Compare the print with the preview. List changes since the last good run: file, material, machine or settings.
Check: You have a short list of plausible causes, not a list of unrelated settings to change.
- 4.
Choose a single test
Choose one safe change and predict what it should affect. Use a small test if it reproduces the same issue.
Check: You know what result would support or weaken your hypothesis.
- 5.
Repeat and compare
Hold other conditions fixed. Record whether the symptom improves, stays or worsens. Return to the baseline before testing a different cause.
Check: You can compare the two runs without reconstructing settings from memory.
- 6.
Keep the result or hand it over
Save a working change and verify it on a suitable job. If the fault persists or needs service, hand over the record and photos.
Check: The next operator gets a repeatable setup or a clear account of what has already been tried.
If this happens
The sliced preview already contains the missing or unexpected feature.
Investigate the file and slicing choices before changing the physical machine.
The same job previously worked and one recorded condition changed.
Use that change to form a testable hypothesis. Keep the other conditions fixed.
The fault repeats, the machine is damaged, or the next action exceeds your training.
Stop testing and hand over the record with photos and the exact error message.
Check your result
- 01The record distinguishes what you observed from what you think caused it.
- 02A retry identifies one deliberate change and the conditions held constant.
- 03The result says whether the original symptom improved, stayed the same or worsened.
Check your understanding
Read the reasoning
Several changes confound the result. Record the working combination, then use controlled comparisons before claiming a particular cause.
Recognise a failed start and stop it safely.
Keep the conditions and results with each job.
Explore the wider diagnostic framework.
Get help when diagnosis reaches the limit of your training.
More in Workflow & Operations
Background reading
The theory behind these procedures, in STANDARD Knowledge.