Solved Some strange things with Superslicer and Duet.
-
Can you share the gcode file?
-
@phaedrux Yes
JusterRatt_0.15mm_PLA_MK2.5_1h25m.gcode
And the STL
JusterRatt.stlWhy cant I upload it as a ZIP-file?
-
@tomasl look here, line 40342, filament specific end gcode
G1 Z33.95 ; Move print head up
So that's where that comes from. And peeking at the HEIGHT comments, 33.95/0.15 = 226
So that's that.
-
@oliof
I found this row in the "Printer Setting Custom G-codes"M107 ; turn off fan {if max_layer_z < max_print_height}G1 Z{z_offset+min(max_layer_z+30, max_print_height)}{endif} ; Move print head up G1 X0 Y200 F3000 ; home X axis
Should it be commented out?
-
@tomasl said in Some strange things with Superslicer and Duet.:
{if max_layer_z < max_print_height}G1 Z{z_offset+min(max_layer_z+30, max_print_height)}{endif} ; Move print head up
Just add an "E" at the beginning of the comment, then the line will be ignored, eg:
{if max_layer_z < max_print_height}G1 Z{z_offset+min(max_layer_z+30, max_print_height)}{endif} ;E Move print head up
Ian
-
@tomasl said in Some strange things with Superslicer and Duet.:
Why cant I upload it as a ZIP-file?
The forum software doesn't allow it. Possibly because you never know what's actually inside a zip file.
-
i noticed on my new RatRig printer, any STL i slice with SuperSlicer, the Duet Web Interface always says 1 of 900 layers printing. the 900 never changes, no matter which Gcode i load to the Duet 3 Mini 5+. Its weird but i just assumed it was a bug in the slicer.
-
@rogerpodacter said in Some strange things with Superslicer and Duet.:
i noticed on my new RatRig printer, any STL i slice with SuperSlicer, the Duet Web Interface always says 1 of 900 layers printing. the 900 never changes, no matter which Gcode i load to the Duet 3 Mini 5+. Its weird but i just assumed it was a bug in the slicer.
Can you share an example gcode file?
-
@phaedrux I should have clarified, this is on the mobile web version when i connect with my iPhone 11 Pro. Attached gcode and screenshot. y_max_endstop_slider_3.1 Extended Direct Mount_0.2mm_PLA_6m.gcode
-
@rogerpodacter I think it's the same issue as above. Z moves in the end gcode that don't have
;E
in the comment so they are getting picked up as normal print Z moves.G1 Z10 F600 ; Move print head up G1 X5 Y240 F15000 ; present print G1 Z78 F600 ; Move print head further up G1 Z180 F600 ; Move print head further up
Add
;E
to the comments on those Z moves in the slicer end gcode and those Z moves will be ignored by DWC. -
@phaedrux thanks, i revised my custom end gcode which is where those lines were coming from and seems to fix the issue.
{if max_layer_z < max_print_height}G1 Z{z_offset+min(max_layer_z+2, max_print_height)} F600 ;END Move print head up{endif} G1 X5 Y{print_bed_max[1]*0.8} F{travel_speed*60} ;END present print {if max_layer_z < max_print_height-10}G1 Z{z_offset+min(max_layer_z+70, max_print_height-10)} F600 ;END Move print head further up{endif} {if max_layer_z < max_print_height*0.6}G1 Z{max_print_height*0.6} F600 ;END Move print head further up{endif} M140 S0 ; turn off heatbed M104 S0 ; turn off temperature ;M107 ; turn off fan M84 X Y E ; disable motors
-
-