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!
I'm excited because I've personally produced this showcase event, so if you are curious what else I'm up to nowadays, come check it out and say hi in the chat! It would mean a lot!
Often getting started is the most difficult part of any process. A good start sets you up for success and saves you time and energy that could be spent elsewhere. That is why we have a onboarding course ready for
Ultimaker S5 Pro Bundle, Ultimaker S5, Ultimaker S3 Ultimaker 2+ Connect.
They're ready for you on the Ultimaker Academy platform. All you need to do to gain access is to register your product to gain free access.
Ready? Register your product here in just 60 seconds.
Recommended Posts
GregValiant 697
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