[3.6.0-beta.3+1] Extruder stall detection

[Leonard03]

Hello everybody!
Can anyone please confirm that extruder stall detection works on 3.6.0-beta.3 or +1 on a Duet2 WIFi?

M915 P3 S-64 H10 or M915 E S-64 H10 should rise a stall event with virtually no movement, right?
Move command is G1 H1 E70 F600, extruder is a Bondtech BMG, around 415 esteps
Reducing motor current during this phase I tried from 10 to 80 percent
Acceleration 3000mm/min
Acceleration during homing move 1000mm/s

[Leonard03]

Remapping driver 3 from the extruder to an axis (V axis in my case) seems to rise the stall event. So it seems to be a bug with extruder stall detection in this version.
By the way, during a move, M122 shows that the extruder SG is not available..

[Leonard03]

I am sorry.. Only now I've seen on GitHub issue/feature request #930.
Is there any chance that this feature request to be part of rc.1 ? Or it will be implemented after 3.6.0 stable?

[T3P3Tony]

@Leonard03 its currently flagged for After 3.6.0. Once we have 3.6rc1 or 3.6.0 stable out we will have a better idea of what will be in 3.7.

[Leonard03]

@T3P3Tony Understood. Thank you for the clarification. I will wait

[dc42]

@Leonard03 did extruder stall detection work for you in firmware 3.5.x ?

[dc42]

@Leonard03 for clarification: extruder stall detection does work for the purposes of using an extruder stall to load filament using a G1 H1 Exxx command. Such a use of stall detection does not raise an event.

[dc42]

I have updated https://github.com/Duet3D/RepRapFirmware/issues/930 with info on how to determine whether a G1 H1 E move was terminated by an extruder stall or not.

dc42 created this issue in Duet3D/RepRapFirmware

closed Feature request: when using stall detection filament loading (G1 H1 Exx) flag whether a stall occurred #930