d87c7a70cb
While testing I noticed that the movement after the pause will first move the head down and then move to the position before the pause. This could result in noticeable artifacts or accidentally push thin towers from the bed.) See the code below. ```gcode ;TYPE:CUSTOM ;added code by post processing ;script: PauseAtHeight.py ;current z: 5 ;current height: 5.0 M83 ; switch to relative E values for any needed retraction G1 F300 Z6 ; move up a millimeter to get out of the way G1 F9000 X190 Y190 G1 F300 Z20.0 M84 E0 @pause now change filament and press ; Do the actual pause G1 F300 Z5 G1 F9000 X30.759 Y30.759 G1 F1800 ; restore extrusion feedrate ``` I have switched the lines in the script such that it will first move to the correct X, Y and then move down ```python prepend_gcode += self.putValue(G = 1, X = x, Y = y, F = 9000) + "\n" prepend_gcode += self.putValue(G = 1, Z = current_z, F = 300) + "\n" ``` As shown in the code below ```gcode ;TYPE:CUSTOM ;added code by post processing ;script: PauseAtHeight.py ;current z: 5 ;current height: 5.0 M83 ; switch to relative E values for any needed retraction G1 F300 Z6 ; move up a millimeter to get out of the way G1 F9000 X190 Y190 G1 F300 Z20.0 M84 E0 @pause now change filament and press ; Do the actual pause G1 F9000 X30.759 Y30.759 G1 F300 Z5 G1 F1800 ; restore extrusion feedrate ```
Cura
Ultimaker Cura is a state-of-the-art slicer application to prepare your 3D models for printing with a 3D printer. With hundreds of settings and hundreds of community-managed print profiles, Ultimaker Cura is sure to lead your next project to a success.
Logging Issues
For crashes and similar issues, please attach the following information:
- (On Windows) The log as produced by dxdiag (start -> run -> dxdiag -> save output)
- The Cura GUI log file, located at
%APPDATA%\cura\<Cura version>\cura.log(Windows), or usuallyC:\Users\<your username>\AppData\Roaming\cura\<Cura version>\cura.log$HOME/Library/Application Support/cura/<Cura version>/cura.log(OSX)$HOME/.local/share/cura/<Cura version>/cura.log(Ubuntu/Linux)
If the Cura user interface still starts, you can also reach this directory from the application menu in Help -> Show settings folder
For additional support, you could also ask in the #cura channel on libera.chat. For help with development, there is also the #cura-dev channel.
Dependencies
- Uranium Cura is built on top of the Uranium framework.
- CuraEngine This will be needed at runtime to perform the actual slicing.
- fdm_materials Required to load a printer that has swappable material profiles.
- PySerial Only required for USB printing support.
- python-zeroconf Only required to detect mDNS-enabled printers.
For a list of required Python packages, with their recommended version, see requirements.txt.
This list is not exhaustive at the moment, please check the links in the next section for more details.
Build scripts
Please check out cura-build for detailed building instructions.
If you want to build the entire environment from scratch before building Cura as well, cura-build-environment might be a starting point before cura-build. (Again, see cura-build for more details.)
Running from Source
Please check our Wiki page for details about running Cura from source.
Plugins
Please check our Wiki page for details about creating and using plugins.
Supported printers
Please check our Wiki page for guidelines about adding support for new machines.
Configuring Cura
Please check out Wiki page about configuration options for developers.
Translating Cura
Please check out Wiki page about how to translate Cura into other languages.
License
Cura is released under the terms of the LGPLv3 or higher. A copy of this license should be included with the software.