Auxiliary feeder issue

Hi,

my first prints have repeatedly been paused due to a message indicating an auxiliary feeder blockage. Apparently, this is a recurring issue with this machine. Is there a solution? I’ve read that it might be necessary to disable the feeder blockage sensor in Klipper. What would be the best solution in your opinion?

Hi,

Have you tried with different filaments ?

No, for now I have only used ABS filament on this printer. The auxiliary feeder is connected to a dryer with a Bowden tube of about 80 cm. Could that create enough resistance to cause the feeder to malfunction?

I don’t know, I don’t own such a printer.

Try without dryer just to see.

Read through this thread:

1 Like

Some tubing introduces quite a bit of drag. I’ve had some the aux feeder wasn’t happy with. Is it clear tubing, by any chance? Try a different length of PTFE tube on it, or even just ditch the tubing between the drier & feeder temporarily, for testing.

The PTFE between the dryer and the feeder is a Capricorn.

I’ll try with the filament directly on the spool holder. Is it a problem if the filament is warm because the drying process isn’t finished yet?

If I’ve read the thread correctly, the solution mentioned is to install the “3dprintdemon Klipper Essentials Unified Macro Pack,” which helps better manage the feeder. I’ll try that if the problem isn’t coming from the PTFE between the dryer and the feeder.

I print from my dryers all the time with my other printers…I do not own a MAX.

Normally, a dryer “dries” the filament.

The temperature of the filament leaving the dryer is 60°C maximum and cools very quickly before reaching the nozzle.

Sorry, what I meant about this is that when I had print interruptions with a feeder blockage message, the dryer was still drying the ABS filament and was set to 80°C.

If the filament is hot, can it stick or create more friction in the PTFE tube, or does it expand and move more difficultly inside the tube?

I had the impression that once the drying finished And that the filament had cooled down there were no more auxiliary feeder errors.

I can’t be sure but 80° for PTFE it’s very low

I run into this a lot – especially with 3 kg spools on large prints. I’m feeding PLA directly into the buffer when I get these annoying “print paused due to jam” messages. If i select RESUME, the print carries on with no problem until the next “jam detection” – usually in about 5 minutes. How do I turn off jam detection to eliminate all these false positives? Or at least reduce the sensitivity?

I think there is a line to disable the feeder jam sensor in Klipper. Does anyone know it?

Here is ChatGPT’s response to the question. I’m personally not very familiar with Klipper — can someone confirm whether this is actually feasible?

On a Sovol SV08 Max running Klipper, the auxiliary feeder jam sensor is usually defined as either:

  • a filament_switch_sensor

  • a filament_motion_sensor

  • or integrated into a feeder management macro (auto-pause logic)

You can disable it directly in your printer.cfg.

:wrench: METHOD 1 — Simple (Clean & Reversible) Disable

This is the recommended method.

:one: Open your

printer.cfg

Via:

  • Mainsail → Machine → Configuration

  • or Fluidd → Configuration Files

Look for a section similar to:

[filament_switch_sensor aux_feeder]

pause_on_runout: True

switch_pin: ^PC15

or:

[filament_motion_sensor aux_feeder]

detection_length: 7.0

extruder: extruder

switch_pin: ^PC15

pause_on_runout: True

:two: Disable automatic pause

Simply change:

pause_on_runout: False

Restart Klipper.

:backhand_index_pointing_right: The sensor will remain active but will no longer pause the print.

:wrench: METHOD 2 — Completely Disable the Sensor

If you want to fully neutralize it:

Option A — Comment out the section

Add # in front of each line:

#[filament_switch_sensor aux_feeder]

#pause_on_runout: True

#switch_pin: ^PC15

Then restart Klipper.

Option B — Remove the call inside macros

Some SV08 Max configurations use a macro like:

[gcode_macro FILAMENT_RUNOUT]

or:

[gcode_macro AUX_FEEDER_CHECK]

In that case:

  • remove the PAUSE command

  • or replace the macro content with:

gcode:

M117 Runout detected (ignored)

:wrench: METHOD 3 — Disable via Variable (Sovol-modified firmware)

Some Sovol configurations include a variable such as:

variable_enable_aux_sensor: True

Just change it to:

variable_enable_aux_sensor: False

:warning: Important

If you completely remove the section and Klipper returns:

Unknown sensor

It means a macro is still referencing it.

In that case, keep the sensor section but simply set:

pause_on_runout: False

That’s the most stable solution.

:bullseye: Recommended Approach

On the SV08 Max, the safest method is:

:check_mark: Keep the sensor defined

:check_mark: Set pause_on_runout: False

:check_mark: Optionally increase detection_length (e.g., 15 mm) if it’s a motion sensor

This prevents false jam pauses without breaking the internal logic.

There is a post in the max forum with a better config for the feeder. That’s helped a lot of people. You could also join the Sovol discord for more help there too.