Printer stopt moving

Veti

@stienfromarden said in Printer stopt moving:

I use interpolation, but the 4 nema23 z axis motor are powered from 4 external stepper drivers (1/16)

M350 X16 Y16 U16 E16 I0 ;

this says no interpolation for X Y U E.

M350 Z16 E16 I1 ; Configure microstepping with interpolation

This says interpolation for Z and E

Veti

M204 S5000
G1 F540
G1 X411.326 Y408.547 E0.64352

did you set reprap instead of marlin in prusaslicer?

540 is 9mm/sec

stienfromarden

ok changed that, but still no movement when printing...

Veti

@stienfromarden
and when you cancel the print you can issue move commands via the web ui?

stienfromarden

@Veti

When I cancel the the print I cannot issue a move with the web ui. It also keeps clicking the Z axis when I cancel the print.

stienfromarden

@Veti said in Printer stopt moving:

M204 S5000
G1 F540
G1 X411.326 Y408.547 E0.64352

did you set reprap instead of marlin in prusaslicer?

540 is 9mm/sec

Jes I did. I try to change that!

stienfromarden

ok, so when I choose marlin firmware in my PrusaSlic3r it moves very slow when homing before printing an then it stops, same problem as with reprap..

Veti

@stienfromarden said in Printer stopt moving:

When I cancel the the print I cannot issue a move with the web ui

what is the error on the console?

stienfromarden

This post is deleted!

stienfromarden

No errors on the console weirdly, but I'm also not able to cancel the print, only pause it..

Veti

can you issue the commands M201 till M205 and post the outputs

stienfromarden

I just updated the firmware, and now I have some other issues... trying to fix that first and than I will issue m201 till m205

thanks so far, keep you updated

stienfromarden

I get this error now

Screenshot 2020-01-07 at 14.25.52.png

droftarts

From your gcode file:

M107
M104 S200 ; set temperature
G28 X0
G28 Y0
M561 ; Clear any bed transform that might be in place
G30 ; Do a single probe
M375 P"2020begin1.csv" ; Load my custom heightmap.
G21 ; set units to millimeters
G90 ; use absolute coordinates
M83 ; use relative distances for extrusion
; Filament gcode
G1 E-5.00000 F3600.00000
G1 Z2.000 F18000.000
G1 X409.730 Y410.094
G1 Z0.500
G1 E8.00000 F4800.00000
M204 S5000
G1 F540
G1 X411.326 Y408.547 E0.64352
G1 X414.329 Y405.936 E1.15176

You said it stops after the probe (G30). Does it do the filament retraction? The next move after that is a Z move at F18000 (300mm/s), too fast for you Z axis.

Ian

Veti

@stienfromarden
its just a warning. but in the homing files change S1 to H1

stienfromarden

ok, got it updated now and I looks like this;

Firmware Name: RepRapFirmware for Duet 2 WiFi/Ethernet
Firmware Electronics: Duet WiFi 1.02 or later
Firmware Version: 2.05 (2019-12-13b1)
WiFi Server Version: 1.23
Web Interface Version: 1.22.6

droftarts

Ignore those warnings for now. You can change them, in your home.g files, later, but the S is still supported in 2.05.

The "tube-marlin.gcode" file is different from the one you posted? Most likely, if the firmware is set to Marlin in PrusaSlicer, the slicer is adding the motor speed/acceleration/jerk codes. The main problem with that is that Marlin specifies these in mm/s, while RRF specifies them in mm/minute, so they are very low values for RRF.

Ian

stienfromarden

@droftarts

Thanks, it does the retraction! So it's probably the 300mm/s Z travel, but where do I change that?

I tried the same gcode file and now zy moved for 20cm aprox.

Veti

@droftarts said in Printer stopt moving:

The next move after that is a Z move at F18000 (300mm/s), too fast for you Z axis.

his config limits the max speed to Z400

stienfromarden

@droftarts said in Printer stopt moving:

Ignore those warnings for now. You can change them, in your home.g files, later, but the S is still supported in 2.05.

The "tube-marlin.gcode" file is different from the one you posted? Most likely, if the firmware is set to Marlin in PrusaSlicer, the slicer is adding the motor speed/acceleration/jerk codes. The main problem with that is that Marlin specifies these in mm/s, while RRF specifies them in mm/minute, so they are very low values for RRF.

Ian

Jes, I degraded back to 2.05 now, the warnings are gone, but first it didn't home when the warning turned on. That is fixed now!