Welcome! Log In Create A New Profile

Advanced

Filament motion sensor always triggers runout condition

Posted by nabbito 
Filament motion sensor always triggers runout condition
June 23, 2020 08:26AM
I'm trying to get a BTT Smart Filament Sensor working off the E0DET connector (pin 1.26) on an SKR 1.4 Turbo. I'm running TMC2209s and have removed the DIAG pins so they don't interfere with the switch inputs.

Here is the response to M412:

Send: M412
Recv: echo:Filament runout ON
Recv: Filament runout distance (mm): 8.00

and when I issue M119 I get:

Send: M119
Recv: Reporting endstop status
Recv: x_min: open
Recv: y_min: open
Recv: z_min: open
Recv: z_probe: TRIGGERED
Recv: filament: TRIGGERED

As expected, if I advance the filament a bit and issue M119, "filament" changes to "open"; this indicates to me that the sensor is connected properly and Marlin is able to read the sensor properly.

I have enabled "FILAMENT_MOTION_SENSOR".

The problem is that the filament runout condition keeps triggering - it doesn't even get past the purge line that Cura puts in the G-code. Even when I "resolve" the condition (i.e. I go through the motions of changing the filament), it triggers again (presumably after FILAMENT_RUNOUT_DISTANCE_MM).

I enabled FILAMENT_RUNOUT_SENSOR_DEBUG and this is the output:

Recv: Motion detected: 0
Recv: Remaining mm: 8.00
Recv: Motion detected: 0
Recv: Remaining mm: 6.33

Any suggestions on how to get this working?
Sorry, only registered users may post in this forum.

Click here to login