Duet 3 - Moves really slow?
-
@Martin1454 said in Duet 3 - Moves really slow?:
Moves a little bit slower than jogging, but still way faster than when homing
and when you issue this command on its own.
G1 H1 X-325 F4000 ; move quickly to X axis endstop and stop there (first pass)
? -
Can you add M400 before your M913 commands to change the motor current?
-
@Veti said in Duet 3 - Moves really slow?:
@Martin1454 said in Duet 3 - Moves really slow?:
Moves a little bit slower than jogging, but still way faster than when homing
and when you issue this command on its own.
G1 H1 X-325 F4000 ; move quickly to X axis endstop and stop there (first pass)
?It steps 1 step towrds -x, but not 325mm
@Phaedrux said in Duet 3 - Moves really slow?:
Can you add M400 before your M913 commands to change the motor current?
I did now - still no change
-
@Martin1454 said in Duet 3 - Moves really slow?:
It steps 1 step towrds -x, but not 325mm
I'm not sure what you mean by that.
Can you post your current config.g and all your homing files? bed.g if used.
Jogging moves will happen at the defined feed rate in config.g unless otherwise specified with an F parameter.
The feed rate of the homing moves is defined in the homing file, so jogging and homing is going to look different unless they have the same feed rate specified.
-
@Phaedrux
The stepper takes 1 step - like it moves to the left a tiny bit. (I think 1 full step, not microstep)The current config.g
; Configuration file for Duet 3 (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.1.4 on Mon Oct 12 2020 17:14:31 GMT+0200 (Centraleuropæisk sommertid) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"Duet 3" ; set printer name M669 K1 ; select CoreXY mode ; Drives M569 P0.1 S1 ; physical drive 0.1 goes forwards M569 P0.2 S1 ; physical drive 0.2 goes forwards M569 P0.3 S1 ; physical drive 0.3 goes forwards M569 P0.0 S1 ; physical drive 0.0 goes forwards M584 X0.1 Y0.2 Z0.3 E0.0 ; set drive mapping M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X200 Y200 Z800.00 E415.00 ; set steps per mm M566 X1500.00 Y1500.00 Z12.00 E120.00 ; set maximum instantaneous speed changes (mm/min) M203 X8400.00 Y8400.00 Z180.00 E1200.00 ; set maximum speeds (mm/min) M201 X800.00 Y500.00 Z20.00 E250.00 ; set accelerations (mm/s^2) M906 X1200 Y1200 Z800 E800 I40 ; set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout ; Axis Limits M208 X0 Y0 Z0 S1 ; set axis minima M208 X320 Y290 Z480 S0 ; set axis maxima ; Endstops M574 X1 S3 ; Set endstops controlled by motor load detection M574 Y1 S3 ; Set endstops controlled by motor load detection M574 Z0 ; Set endstop Z to be probe M915 X Y H200 S0 R0 F0 ; set X and Y to sensitivity , do nothing when stall, unfiltered ; Z-Probe M950 S0 C"io7.out" ; create servo pin 0 for BLTouch M558 P9 C"^io7.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds G31 P500 X0 Y0 Z2.5 ; set Z probe trigger value, offset and trigger height M557 X15:215 Y15:195 S20 ; define mesh grid ; Heaters M308 S0 P"temp0" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin temp0 M950 H0 C"out0" T0 ; create bed heater output on out0 and map it to sensor 0 M307 H0 B1 S1.00 ; enable bang-bang mode for the bed heater and set PWM limit M140 H0 ; map heated bed to heater 0 M143 H0 S120 ; set temperature limit for heater 0 to 120C M308 S1 P"temp2" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin temp2 M950 H1 C"out1" T1 ; create nozzle heater output on out1 and map it to sensor 1 M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit ; Fans M950 F0 C"out7" Q500 ; create fan 0 on pin out7 and set its frequency M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off M950 F1 C"out5" Q500 ; create fan 1 on pin out5 and set its frequency M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on ; Tools M563 P0 D0 H1 F0 ; define tool 0 G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C ; Custom settings are not defined ; Miscellaneous T0 ; select first toolbed.g
; bed.g ; called to perform automatic bed compensation via G32 ; ; generated by RepRapFirmware Configuration Tool v3.1.4 on Mon Oct 12 2020 17:14:31 GMT+0200 (Centraleuropæisk sommertid) M561 ; clear any bed transform G29 ; probe the bed and enable compensationAnd homex.g
; homex.g ; called to home the X axis ; ; generated by RepRapFirmware Configuration Tool v3.1.4 on Mon Oct 12 2020 17:14:31 GMT+0200 (Centraleuropæisk sommertid) G91 ; relative positioning M400 ; M913 X30 Y30 ; Drop current to 70% G1 H2 Z3 F6000 ; lift Z relative to current position G1 H1 X-325 F4000 ; move quickly to X axis endstop and stop there (first pass) G1 X5 F6000 ; go back a few mm G1 H1 X-325 F500 ; move slowly to X axis endstop once more (second pass) G1 H2 Z-3 F200 ; lower Z again G90 ; absolute positioning M913 X100 Y100 ; return current to 100% -
@Martin1454 said in Duet 3 - Moves really slow?:
The stepper takes 1 step - like it moves to the left a tiny bit. (I think 1 full step, not microstep)
That sounds like stall detection has triggered prematurely. Does it show the axis as homed after it stops?
I guess I'm a bit confused, is it a case of movement being slower than requested or is it stalling before it should?
Have you gone through any of the stall detection tuning?
https://duet3d.dozuki.com/Wiki/Stall_detection_and_sensorless_homing
-
@Martin1454 Can you post your homeall as well if you're using it? Or are you only testing home x at the moment?
Mostly just curious to see if there are any other gcode commands being executed to change the values between config.g being executed at startup and when executing homex.
-
@Phaedrux said in Duet 3 - Moves really slow?:
@Martin1454 said in Duet 3 - Moves really slow?:
The stepper takes 1 step - like it moves to the left a tiny bit. (I think 1 full step, not microstep)
That sounds like stall detection has triggered prematurely. Does it show the axis as homed after it stops?
I guess I'm a bit confused, is it a case of movement being slower than requested or is it stalling before it should?
Have you gone through any of the stall detection tuning?
https://duet3d.dozuki.com/Wiki/Stall_detection_and_sensorless_homing
Thats what im trying to do - Im trying to setup the stall detection, but I never get it moving fast enough to try to tune it.
But Maybe I should try to add in a comment it post when it triggers, and see if it triggers prematurely and that is why it vibrates/stalls in the begining.
-
Can you test movement with M915 commented out?
Send G92 X100 to mark it as homed and try and jog it around.Have you calculated what your H value should be yet?
Have you tried different sensitivity values yet?
-
@Phaedrux said in Duet 3 - Moves really slow?:
Can you test movement with M915 commented out?
Send G92 X100 to mark it as homed and try and jog it around.Have you calculated what your H value should be yet?
Have you tried different sensitivity values yet?
So I tested a bit around - I added an M117 and found out it moves slow due to stall detection was triggered as soon as it starts, and it tries to do the small "second" pass that is slow.
After playing with motor current + sensitivity I found S2 and 40% power works - I still have no idea why the motor made the stall/vibration sound when I started the homing, but with those 2 excact values it works.
Thanks for the support everyone!
-
Glad you figured it out. Stall detection tuning can be tricky.
