RE: Prusa Slicer on Ultimaker - first layer problem
Ok had a look at your settings from the 3mf. The reason it moved the bed first was you had a G28 command as the very first line in your start gcode under printer settings. G28 means home all axis, so it moved your bed to start position. The G28 command doesn't need a number like the cura profile uses. For example G28 on its own moves x,y,z to zero for all 3. G28 X Y moves x and y to their zero home positions, G28 X Y Z is the same as just doing G28.
You then had wait for temp commands but hadnt added the set temp commands in there from my example. Both the cura profile and my example have both set and wait commands. I've added them back into the start gcode section.
Also you had custom gcode in the layers area to do a temperature tower, basically depending on the height it would have changed the extruder temperature as it gets higher. It over rides the settings configured by your filament profile. I assume you dont want that on every model so I removed it from the profile.
The model itself is causing something very weird, you had vase mode enabled which for some reason is making slicer generate over 10200 layers, if I turn off vase mode it goes back to being the expected 125 layers. Dont know if this is a model issue or a bug in Slicer though. While testing things out I would leave vase mode turned off.
Load in the attached .3mf and try slicing and then printing the output gcode. If it does what you want then save the printer profile to some new preset and tweak things from there.
Oh one last point I would double check the Machine limits set in Printer Settings > Machine Limits actually match what your printer is capable of as Slicer is adding those settings into the output gcode (the M2xx values from your attached slicer gcode)
RE: Prusa Slicer on Ultimaker - first layer problem
Stupid edit timer limit on posts 🙂
Just been doing a bit of research on your printer. Looks like it uses a custom gcode flavour naturally which is why you may be seeing weirdness. Apparently the machine is supposed to handle start and end gcode itself and not have it in the code file. However it is supposed to be smart enough to switch to the old style, which might be why the cura output includes the ";FLAVOR:Marlin" comment at the top. If thats the case then the slicer profile I did you will need that adding in as the very first line of the start gcode section to let the printer know that the gcode file is in Marlin format.
RE: Prusa Slicer on Ultimaker - first layer problem
Good morning neo,
just tried it. Unlikely the same behavior, the hotend is pushed into the filament by the bed and then the hotend moves to start.
You say I should manually manipulate the gcode file with the start entry "Marlin" ? I 'll give it a try.
RE: Prusa Slicer on Ultimaker - first layer problem
No I said it might need the marlin line added to the start gcode. Under Printer Settings>Start Gcode add the marlin line to the top. That will put it at the start of every gcode export from prusa slicer that uses that printer profile. No need to do it manually each time.
I still think posting on one of the ultimaker groups is your best bet as they will all have the printers so can try things out.
RE: Prusa Slicer on Ultimaker - first layer problem
Good Morning,
asked for help inside the Cura Forum, got a interesting answer.
is this a possible Prusa Code ?
G1 X[next_position_x] Y[next_position_y] Z[next_position_z] F9000
with a new opject I could finaly finde the G-Code differences
Cura:
;LAYER:0
M107
G0 F4320 X122 Y70.418 Z0.27
Prusa:
; Filament gcode
G1 Z0.250 F7800.000
G1 E-2.00000 F2400.00000
G92 E0
G1 X120.588 Y67.783 F7800.000
RE: Prusa Slicer on Ultimaker - first layer problem
Is there a page where I can have a look on the supported [xxx] Codes ?