Stall detected on driver(s) 0 1
-
@savethepetko said in Stall detected on driver(s) 0 1:
M915 X Y S8 R2 ; sensitivity change on motors X and Y
As suspected, you've got stall detection enabled and set to pause when a stall is detected.
https://duet3d.dozuki.com/Wiki/Stall_detection_and_sensorless_homing
Is your intention to use stall guard for homing purposes only or also for stall detection during a print? You may need to tune separate values for each situation. You could move the M915 command into homeall so that it takes effect for the homing, and then either disable it at the end of homeall, or use a different value tuned better for actual printing.
@savethepetko said in Stall detected on driver(s) 0 1:
M401 ; Lower Z probe (BLTouch) G30 ; Calibrate Z-axis M402 ; Retract Probe
When using BLTouch you do not need to use M401 and M402. It will deploy and retract as needed.
@savethepetko said in Stall detected on driver(s) 0 1:
G1 H2 X5 F12000 ; go back a few mm G1 H1 X-250 F7000 ; move slowly to X axis endstop once more (second pass)
When using stall detection for X Y homing, you don't need the second pass at all. It's already stalled to the nearest full step of the motor. A slower pass won't be more accurate, and in fact moving slower may make it harder to detect a stall at all.
You may want to add T0 to the end of your config.g so that the tool is made ready at startup.
@savethepetko said in Stall detected on driver(s) 0 1:
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.1.1 running on Duet WiFi 1.02 or later
Time to update the firmware as well.
https://github.com/Duet3D/RepRapFirmware/releases/download/3.3/Duet2and3Firmware-3.3.zip
Upload that zip file as is to the system tab in DWC.
-
okay , i will change
M915 X Y S8 R2 to R1
remove m401 and m402
and remove the second pass for stall .
it will be okay ?If i update the firmware i lost my data ?
-
@savethepetko said in Stall detected on driver(s) 0 1:
If i update the firmware i lost my data ?
No, your configuration is totally separate.
-
-
Never hurts to make a backup of your SD card anyway.
-
@phaedrux
do you know something about BLTouch , i removed the M401 and M402 and now for start its dol home Z with error :G28
Error: Probe already triggered at start of probing move
Error: G0/G1: insufficient axes homed -
Does your BLtouch work if you send a single G30 command?
-
@phaedrux
Yes it works when i send G30 -
Please post your homeall.g as it is now.
It sounds like the BLtouch was in error state when you tried G28.
Is X and Y homing correctly first?
-
; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Sun Jun 27 2021 18:14:24 GMT+0200 (Central European Summer Time)
M400
M913 X70 Y70 ; drop motor current to 70%
M400 G91 ; relative positioning
G1 H2 Z5 F12000 ; lift Z relative to current position
G1 H1 X-270 Y-210 F10000 ; move quickly to X axis endstop and stop there
G90 ; absolute
G1 X67 Y148 F10000 ; move to middle of bed plus probe offsets
G30 ; home z0Sometimes going home okay when i start the printer and sometimes when i turn on the printer the bltouch wont light red and when i run homeall its go in the middle and stop with this error.
-
@savethepetko said in Stall detected on driver(s) 0 1:
Sometimes going home okay when i start the printer and sometimes when i turn on the printer the bltouch wont light red and when i run homeall its go in the middle and stop with this error.
Sounds like your pin might be getting stuck on the self-test?
At the start of your homeall and at the end of config.g try adding these commands to clear any errors on the bltouch and ensure the pin is retracted.
M280 P0 S160 ; Alarm Release and Push-Pin UP just in case it's in alarm and deployed G4 S1 M402 ; Retract probe just in case it's down
