Clean and align the sensor path, inspect its connector, confirm filament diameter and flexibility, and adjust debounce or sensitivity only within the manufactur.
Start hereClean and align the sensor path, inspect its connector, confirm filament diameter and flexibility, and adjust debounce or sensitivity only within the manufacturer workflow.
First safe actionRun the first safe check and change one variable at a time.
Proof targetA small representative test no longer shows the original symptom.
Match the failed area to the visual before changing a setting.
Repair progress0 of 8 complete
Step 1 of 8
Unload filament and clean the sensor using the approved method.
Keep the problem and target visual open while you make this change.
Why this matters
Optical or mechanical movement is obstructed.
Setting or checkRunout distance
Set enough movement after detection for the printer workflow, not as a false-trigger workaround.
Expected result
The original symptom no longer appears during a representative calibration or short test print.
Step 2 of 8
Check the inlet, outlet, PTFE tube, and sensor mount are aligned.
Keep the problem and target visual open while you make this change.
Why this matters
The filament does not fully engage the switch or beam.
Setting or checkDebounce
Use a modest value if the manufacturer supports it.
Expected result
Measurements, temperatures, motion, feed, or exposure remain stable through the complete test.
Step 3 of 8
Inspect the cable and connector while gently moving the harness.
Keep the problem and target visual open while you make this change.
Why this matters
Motion causes intermittent state changes.
Setting or checkAutomatic unload
Confirm the path can unload without snagging.
Expected result
No new warning, collision, leak, electrical smell, unusual heat, or material damage appears.
Step 4 of 8
Test the sensor state in printer diagnostics if available.
Keep the problem and target visual open while you make this change.
Why this matters
Transparent, flexible, or small-diameter filament may be difficult to sense.
Setting or checkRunout distance
Set enough movement after detection for the printer workflow, not as a false-trigger workaround.
Expected result
The successful change is recorded with printer, material, slicer, nozzle or resin, and date.
Step 5 of 8
Try a straight piece of known-good standard filament.
Keep the problem and target visual open while you make this change.
Why this matters
Firmware interprets the state incorrectly.
Setting or checkDebounce
Use a modest value if the manufacturer supports it.
Expected result
The original symptom no longer appears during a representative calibration or short test print.
Step 6 of 8
Confirm the configured sensor type and active-high/active-low logic.
Keep the problem and target visual open while you make this change.
Why this matters
Optical or mechanical movement is obstructed.
Setting or checkAutomatic unload
Confirm the path can unload without snagging.
Expected result
Measurements, temperatures, motion, feed, or exposure remain stable through the complete test.
Step 7 of 8
Use manufacturer-supported debounce or sensitivity settings only.
Keep the problem and target visual open while you make this change.
Why this matters
The filament does not fully engage the switch or beam.
Setting or checkRunout distance
Set enough movement after detection for the printer workflow, not as a false-trigger workaround.
Expected result
No new warning, collision, leak, electrical smell, unusual heat, or material damage appears.
Step 8 of 8
Complete a monitored runout test before relying on the feature.
Keep the problem and target visual open while you make this change.
Why this matters
Motion causes intermittent state changes.
Setting or checkDebounce
Use a modest value if the manufacturer supports it.
Expected result
The successful change is recorded with printer, material, slicer, nozzle or resin, and date.
Controlled test log
Change one variable, then record what happened
This keeps temperature, retraction, speed, mechanical, and material tests from blending together. The history stays private in this browser.