[BUG] Filament Runout Sensor - Random False Positives #501

New Issue

2023-11-27T12:02:20-06:00

spaelectronics commented

2023-11-27 12:02:20 -06:00

(Migrated from github.com)

I keep getting random false positives on the Filament Runout Sensor.

I thought it was the switch went bad, so I replaced the switch, but I'm still having the same issue.

Tested with version MEGA_X_DGUS_v1.5.2

I keep getting random false positives on the Filament Runout Sensor. I thought it was the switch went bad, so I replaced the switch, but I'm still having the same issue. Tested with version MEGA_X_DGUS_v1.5.2

👍 1

fatalyzm commented

2023-11-30 06:00:13 -06:00

(Migrated from github.com)

Same here, the filament sensor runs me crazy.
Unfortunately i have to disable it statically.

I'm now on v1.5.2 - problem still there.

Anycubic Mega X DGUS TMC
Trigorilla 0.0.2

Same here, the filament sensor runs me crazy. Unfortunately i have to disable it statically. I'm now on v1.5.2 - problem still there. Anycubic Mega X DGUS TMC Trigorilla 0.0.2

NoClue11 commented

2023-12-24 06:41:17 -06:00

(Migrated from github.com)

Same problem here.
Anycubic Mega X with Mega X TMC BLT10 1.5.2

Same problem here. Anycubic Mega X with Mega X TMC BLT10 1.5.2

elodur commented

2024-01-02 12:39:30 -06:00

(Migrated from github.com)

Same problem, but I'm not Sure if it's a software bug. When I bridge the switch with a wire there is no problem any more. Maybe it just is the cheap switch.

stklcode commented

2024-01-02 13:25:09 -06:00

(Migrated from github.com)

I can also confirm this, printing occasionally stops with runout warning. Unfortunately, I didn’t investigate yet, but I would also suspect the hardware.

One idea would be tweaking the runout settings, e.g. enable soft-pullup/down, if there is no hardware equivalent or extended the debounce logic programmatically.

Configuring FILAMENT_RUNOUT_DISTANCE_MM could also make sense, there are at least 50-100mm that can safely be ignored, before the extruder fails in default setup. I didn’t check the internal logic, if the state is re-checked in the loop, even a small value may sufficient to debounce a faulty switch.

I will definitely try to tweak the config on next print, but this could probably take a couple of weeks. Workaround is disabling the feature temporarily with a M412 S0 command (if there is enough filament)

I can also confirm this, printing occasionally stops with runout warning. Unfortunately, I didn’t investigate yet, but I would also suspect the hardware. One idea would be tweaking the runout settings, e.g. enable soft-pullup/down, if there is no hardware equivalent or extended the debounce logic programmatically. Configuring `FILAMENT_RUNOUT_DISTANCE_MM` could also make sense, there are at least 50-100mm that can safely be ignored, before the extruder fails in default setup. I didn’t check the internal logic, if the state is re-checked in the loop, even a small value may sufficient to debounce a faulty switch. I will definitely try to tweak the config on next print, but this could probably take a couple of weeks. Workaround is disabling the feature temporarily with a `M412 S0` command (if there is enough filament)

spaelectronics commented

2024-01-02 18:00:43 -06:00

(Migrated from github.com)

I can also confirm this, printing occasionally stops with runout warning. Unfortunately, I didn’t investigate yet, but I would also suspect the hardware.

I thought it was a faulty switch too, so I replaced the switch with a new one, however I still have the same issue.

One idea would be tweaking the runout settings, e.g. enable soft-pullup/down, if there is no hardware equivalent or extended the debounce logic programmatically.

I too was thinking it could be a pullup/down issue. I haven't tried it yet, as I can't compile it myself as I don't know the proper configuration settings for the Mega X.

> I can also confirm this, printing occasionally stops with runout warning. Unfortunately, I didn’t investigate yet, but I would also suspect the hardware. I thought it was a faulty switch too, so I replaced the switch with a new one, however I still have the same issue. > One idea would be tweaking the runout settings, e.g. enable soft-pullup/down, if there is no hardware equivalent or extended the debounce logic programmatically. I too was thinking it could be a pullup/down issue. I haven't tried it yet, as I can't compile it myself as I don't know the proper configuration settings for the Mega X.

stklcode commented

2024-01-06 07:38:22 -06:00

(Migrated from github.com)

Just compiled a FW with #define FIL_RUNOUT_PULLUP.

Doesn't seem to make much of a difference, 2 false positives before leveling started and one in the second layer... Disabled the sensor for the current print job. 😞

Next I will try to extend the default debounce threshold from 5 to something higher like ... maybe 10 or 20.

#define FILAMENT_RUNOUT_THRESHOLD 5

If that also does not help, I'll switch from debounced to delayed trigger by setting the distance to something >0, like

#define FILAMENT_RUNOUT_DISTANCE_MM 25

Just compiled a FW with `#define FIL_RUNOUT_PULLUP`. Doesn't seem to make much of a difference, 2 false positives before leveling started and one in the second layer... Disabled the sensor for the current print job. :disappointed: Next I will try to extend the default debounce threshold from 5 to something higher like ... maybe 10 or 20. ```c #define FILAMENT_RUNOUT_THRESHOLD 5 ``` If that also does not help, I'll switch from debounced to delayed trigger by setting the distance to something >0, like ```c #define FILAMENT_RUNOUT_DISTANCE_MM 25 ```

stklcode commented

2024-01-07 04:04:23 -06:00

(Migrated from github.com)

I did a second test with

#define FILAMENT_RUNOUT_THRESHOLD 20

No false-positive runout trigger during a 3h print job 🎉

When I pull he sensor cable, it claims runout. Little sluggish, but the feature still works and we have at least 100mm buffer, before the extruder runs empy on default setup, so I'd say that's fine.

I did a second test with ``` #define FILAMENT_RUNOUT_THRESHOLD 20 ``` No false-positive runout trigger during a 3h print job :tada: When I pull he sensor cable, it claims runout. Little sluggish, but the feature still works and we have at least 100mm buffer, before the extruder runs empy on default setup, so I'd say that's fine.

github-actions[bot] commented

2024-11-02 20:31:13 -05:00

(Migrated from github.com)

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: wp/Marlin-2-0-x-Anycubic-i3-MEGA-S#501