UltiMaker uses functional, analytical and tracking cookies. Tracking cookies enhance your experience on our website and may also collect your personal data outside of Ultimaker websites. If you agree with the use of tracking cookies, click “I agree, continue browsing”. You can withdraw your consent at any time. If you do not consent with the use of tracking cookies, click “Refuse”. You can find more information about cookies on our Privacy and Cookie Policy page.
The Creality slicer itself is an early version of Cura with some cosmetic changes to make it look different.
The Creality definition files within this version (the official Ultimaker version up to 4.13.1) are essentially all the same except for the build plate size. All those definition files were submitted to Ultimaker for inclusion into Cura by either Creality or by the author of the files (who is noted as "Trouch.com").
Neither the Creality version nor the Ultimaker version ever tell a printer to go below "Initial Layer Height". If the bed is properly leveled and is at Z=0 then the nozzle should never hit it. (That should be true for any slicer.)
But if you have an ABL then things may be different. The ABL command in the StartUp Gcode that calls the firmware routine to check the bed may need some parameters adjusted (like the Z-Offset).
If you slice a calibration cube with both slicers and then post both of the gcode files here then a comparison may give a clue as to what is going on. Also let us know what ABL setup (BLTouch, CRTouch, whatever) might be on the printer.
My printer is an Ender 3Pro that I manually level with my trusty piece of parchment paper. I've never had a problem with it hitting the bed and I've never seen a Cura gcode file (either Creality or Ultimaker) with negative Z values.
Link to post
Share on other sites
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
S-Line Firmware 8.3.0 was released Nov. 20th on the "Latest" firmware branch.
(Sorry, was out of office when this released)
This update is for...
All UltiMaker S series
New features
Temperature status. During print preparation, the temperatures of the print cores and build plate will be shown on the display. This gives a better indication of the progress and remaining wait time. Save log files in paused state. It is now possible to save the printer's log files to USB if the currently active print job is paused. Previously, the Dump logs to USB option was only enabled if the printer was in idle state. Confirm print removal via Digital Factory. If the printer is connected to the Digital Factory, it is now possible to confirm the removal of a previous print job via the Digital Factory interface. This is useful in situations where the build plate is clear, but the operator forgot to select Confirm removal on the printer’s display. Visit this page for more information about this feature.
A year after the merger of Ultimaker and MakerBotQQ, we have unlocked the ability for users of our Method series printers to slice files using UltiMaker Cura. As of this release, users can find profiles for our Method and Method XL printers, as well as material profiles for ABS-R, ABS-CF, and RapidRinse. Meaning it’s now possible to use either Cura or the existing cloud-slicing software CloudPrint when printing with these printers or materials
Recommended Posts
GregValiant 1,141
The Creality slicer itself is an early version of Cura with some cosmetic changes to make it look different.
The Creality definition files within this version (the official Ultimaker version up to 4.13.1) are essentially all the same except for the build plate size. All those definition files were submitted to Ultimaker for inclusion into Cura by either Creality or by the author of the files (who is noted as "Trouch.com").
Neither the Creality version nor the Ultimaker version ever tell a printer to go below "Initial Layer Height". If the bed is properly leveled and is at Z=0 then the nozzle should never hit it. (That should be true for any slicer.)
But if you have an ABL then things may be different. The ABL command in the StartUp Gcode that calls the firmware routine to check the bed may need some parameters adjusted (like the Z-Offset).
If you slice a calibration cube with both slicers and then post both of the gcode files here then a comparison may give a clue as to what is going on. Also let us know what ABL setup (BLTouch, CRTouch, whatever) might be on the printer.
My printer is an Ender 3Pro that I manually level with my trusty piece of parchment paper. I've never had a problem with it hitting the bed and I've never seen a Cura gcode file (either Creality or Ultimaker) with negative Z values.
Link to post
Share on other sites