Printer prints at constand slow speed no matter what I adjust

Phaedrux

@bayvan said in Printer prints at constand slow speed no matter what I adjust:

But from there including bed mesh and printing something is capping the speed to 40mm.

including travels?

Share your other files like homing and bed.g.

Do you have a start.g file?

Where are you seeing 40mm/s for the speed?

bayvan

@Phaedrux When homing and bed leveling, including travel, everything is ok. On bed mesh and printing, everything is slow. I printed a test without bed mesh. Homing and bed level is again working as it should. When printing starts, everything is slow, including travel movement. Speed is reported in the Duet Web Control readout.

bed.g

M290 R0 S0    ;  clear baby stepping
M561          ;  reset all bed adjustments
M400          ;  flush move queue

if !move.axes[0].homed || !move.axes[1].homed || !move.axes[2].homed
  echo "not all axes homed, homing axes first"
  G28
 
G30 P0 X30 Y30 Z-99999 ; probe near a leadscrew
G30 P1 X245 Y470 Z-99999 ; probe near a leadscrew
G30 P2 X470 Y30 Z-99999 S3 ; probe near a leadscrew and calibrate 3 motors
echo "Current rough pass deviation: " ^ move.calibration.initial.deviation


while move.calibration.initial.deviation > 0.005
        if iterations >= 5
            echo "Error: Max attemps failed. Deviation: " ^ move.calibration.initial.deviation
			break
        echo "Deviation over threshold. Executing pass" , iterations+1, "deviation", move.calibration.initial.deviation
        G30 P0 X30 Y30 Z-99999 ; probe near a leadscrew
		G30 P1 X245 Y470 Z-99999 ; probe near a leadscrew
		G30 P2 X470 Y30 Z-99999 S3 ; probe near a leadscrew and calibrate 3 motors
        echo "Current deviation: " ^ move.calibration.initial.deviation
        continue
echo "Final deviation: " ^ move.calibration.initial.deviation
G0 X250 Y250 Z10 F12000
; rehome Z as the absolute height of the z plane may have shifted
G28 Z

homeall.g

G91                     ; relative positioning
;G1 H2 Z10 F6000          ; lift Z relative to current position

G1 H1 Y505 F6000 		; move quickly to Y axis endstops and stop there (first pass)
G1 Y-5 F6000     		; go back a few mm
G1 H1 Y505 F360  		; move slowly to Y axis endstops once more (second pass)

G1 H1 X-515 F6000 		; move quickly to X axis endstops and stop there (first pass)
G1 H2 X5 F6000          ; go back a few mm
G1 H1 X-515 F360  		; move slowly to X endstops once more (second pass)
 
G90                     ; absolute positioning
G1 X250 Y250 F6000     ; go to Center of 500 bed
G30                     ; home Z by probing the bed
 
G91                    	; relative positioning
G1 Z10 F1800            ; lift Z relative to current position
G90                    ; absolute positioning

deckingman

@bayvan The last thing in your bed.g file is G28 Z. This will home just the Z axis by calling the macro homez.g. Can you post the contents of homez.g - maybe there is something in that file which is capping the speeds. Also, can you post the contents of config-override.g if you use it - just in case there is something in there which is limiting print speed.

droftarts

@bayvan The code you posted shows a speed of F3600, which is 3600mm/minute, or 50 60mm/second.

On a CoreXY, diagonal moves (ie ones that use only one motor) are limited to 1/1.414 of the speed set, so a move commanded at 50 60mm/s will run at ~~35.36~~ 42.43mm/s.

This is because CoreXY machines are capable of higher speeds in X and Y directions than 45deg diagonal moves, because both motors contribute to pure X or pure Y motion, whereas just one motor is used to perform diagonal motion. RepRapFirmware makes use of this to maximise performance. So on a CoreXY machine, in RRF the maximum XY speeds and accelerations can be set to 1.4 times the 'normal' X and Y values.

Ian

oliof

also make sure acceleration control is off in your slicer

deckingman

@droftarts said in Printer prints at constand slow speed no matter what I adjust:

.............@bayvan The code you posted shows a speed of F3600, which is 3600mm/minute, or 50mm/second.

The last time I looked, there were 60 seconds in a minute and 3600/60 came out at 60 not 50. Either way, if the OP is to be believed, he stated that homing moves are normal but printing moves in DWC are showing 40 mm/sec, so something else is capping the speed like an erroneous M203 or M220 for example.

droftarts

@deckingman said in Printer prints at constand slow speed no matter what I adjust:

The last time I looked, there were 60 seconds in a minute and 3600/60 came out at 60 not 50.

Thanks, edited. Also makes more sense for the speed he's seeing, perhaps.

Ian

bayvan

@deckingman Thank you. It was a single line of code in homez.g. I feel so stupid. This is my 3rd printer, and they all use Duet hardware I should've seen that. Thank you all for the help.

deckingman

@bayvan said in Printer prints at constand slow speed no matter what I adjust:

@deckingman Thank you. It was a single line of code in homez.g. I feel so stupid. This is my 3rd printer, and they all use Duet hardware I should've seen that. Thank you all for the help.

Don't feel stupid - we all make mistakes from time to time. Out of curiosity, what was the offending line?

bayvan

@deckingman I deleted it, and I don't recall the exact values, but it was M203 that was capping the speed.

oliof

@bayvan can't say that never happened to me (-: