hello to all!

Github Issue #559 (https://github.com/Duet3D/RepRapFirmware/issues/559 same issue on Release 3.4.1 on my Duet2 Wifi.

If M915 was invoked with parameter R2 or R3 then no action was taken on a driver stall as if R0 had been used. R1 is working.

rehome.g and driver_stall.g are stored in the /sys/ folder. Stallguard parameter are calibrated (M915 X Y S9 H200 F0 R3). Homing is without stallguard. M915 is active during printing (started from SD-card). Printing speed is 100-200mm/s. Stepper are 1.8deg (200steps/rot) with 160 esteps.

M915 messages:

20.8.2022, 14:57:07 |

Driver 0: stall threshold 9, filter off, steps/sec 200 (39.9 mm/sec), coolstep 0, action on stall: run macro
Driver 1: stall threshold 9, filter off, steps/sec 200 (39.9 mm/sec), coolstep 0, action on stall: run macro
Driver 2: stall threshold 1, filter off, steps/sec 200 (8.0 mm/sec), coolstep 0, action on stall: none
Driver 3: stall threshold 1, filter off, steps/sec 200 (8.1 mm/sec), coolstep 0, action on stall: none
Driver 4: stall threshold 1, filter off, steps/sec 200 (40.0 mm/sec), coolstep 0, action on stall: none
-- | --
After these messages - no macro executing:

20.8.2022, 14:58:23 Warning: Driver 0 stall
20.8.2022, 14:58:15 Warning: Driver 0 stall Warning: Driver 0 stall Warning: Driver 0 stall
20.8.2022, 14:57:44 Warning: Driver 1 stall
20.8.2022, 14:57:40 Warning: Driver 1 stall Warning: Driver 1 stall
20.8.2022, 14:57:35 Warning: Driver 1 stall Warning: Driver 1 stall

my config.g:

config.g

Did I miss something?

Thanks for help!
wbr,
Karl

rockman256 created this issue in Duet3D/RepRapFirmware

closed [Bug]: Stall detection work only with R0 & R1 #559

actual version (download configs and pictures): http://www.kgolger.at/DueUI/V3.3.1.21/DueUI_V3.3.1.21_kgolger.zip

@phaedrux
"Can the console be cleared from gcode?"

In the meantime, a gcode for deleting the console content is included? I am currently working with DWC 3.4B5
Thanks!

wbr,
Karl

@gtj0; @all:

I would like to publish my setting here. It is a first, briefly tested version. Menu language is mainly german, but can be easily changed in dueui_config_default.json.
Here some screenshots:

Hardware:
Duet2 Wifi, FW3.3, DWC V3.4, DueUI V3.3.1
Pi4 B, Raspbian GNU/Linux 10 (buster), Kernel: 5.10.60-v7l+
firefox: Mozilla Firefox 78.14.0esr

Firefox initialization at Pi startup:

@firefox-esr --private-window --kiosk http://192.168.x.xxx/dueui.html?dueui_config_url=dueui_config_default.json

Touchscreen settings for Waveshare H 7" in /boot/config.txt:

hdmi_group=2
hdmi_mode=1
hdmi_mode=87
hdmi_cvt 1280 1024 60 6 0 0 0

DueUI Data (Dueui.html, dueui-bundle.js, dueui_config_default.json and my DWC data.g collection):

Download link: www.kgolger.at/DueUI/V3.3.1/DueUI_V3.3.1_kgolger_settings.zip

Suggestions for changes and improvements are welcome. I am a professional mechanic, not a programmer. for this reason I can not answer questions that go deeper into the system (Java, C++ ....).

Have fun testing and best regards,
Karl

@pcr

Does the adapter also work with a Duet2 Wifi (Ref. 1.04, Firmware 3.3)?