Filament Out Triggers not Clearing After Reloading Material

[BMMal]

Sometimes when an extruder runs out of filament, the trigger does not clear after reloading the filament. The machine runs the pause and resume scripts as it should but immediately after resuming, it pauses again due to filament out. Disabling the sensor, resuming, and then reenabling seems to be ok though.

I have also noticed that if an extruder runs out of filament and DWC disconnects at some point, the Filament out message will reappear every time DWC is reconnected even though I had closed the message window.

I am running:

Firmware Name: RepRapFirmware for Duet 2 WiFi/Ethernet
Firmware Electronics: Duet Ethernet 1.02 or later + DueX5
Firmware Version: 2.01beta1(RTOS) (2018-06-23b1)
Web Interface Version: 1.21.2-b2

[T3P3Tony]

@bmmal I assume you are using a simple filament out switch type sensor? What does M119 say about the e0 endstop when its operating normally (filamnt present, filament not present and then what does it say when its has the glitch?

@chrishamm can you look into the DWC issue reported about filament out message repeating?

[BMMal]

@t3p3tony

Yes. M119 does not give any information about the filament switches. Only X, Y, Z, Zprobe.

With filament present, the machine properties tab does properly indicate that they have not been triggered with "No" though. I can't really check with filament absent right now since the machine is printing but last time I checked the statuses when figuring out how to configure the switches it did work properly.

[BMMal]

I am now seeing filament triggers occurring when the filament does not actually run out. Doing nothing other than hitting resume seems to palate it for a while. How long is unpredictable. I thought it might be related to my Tool Change gcode including the filament sensor config on every tool change but that does not seem to be the case...

It only happens on one extruder and not the other that is being used. Best I can tell the switch is properly closed and even biased beyond closed so even if the filament moves around a bit it could not conceivably open the switch.

The only times I've observed these issues are when I do not reset the machine between prints that have completed, but not necessarily every time.

My start.g has this section:

;Disable the filament out triggers
M591 D0 S0
M591 D1 S0
M591 D2 S0
M591 D3 S0

then the slicer tool change gcode calls a macro for the proper filament trigger when a tool is selected, this is redundantly repeated at every tool change. M98 P/macros/<EXT>_Config_T<EXT>_Trigger

;Configure the E3 Endstop input

M591 D2 P2 C5 S1
;M591 D2 S0