Ghostkeeper 0a84a181c4
Track cfg version numbers with major-minor, sorta
We now have a (format) version and a setting version. Ideally we'd like major-minor version numbers in our profiles. However, introducing major-minor version numbers requires substantial changes to the version upgrade manager to compare version numbers, find a path towards the current version, or even keeping track of the current version. Therefore we just collapse the two version numbers into one: Multiply the major version number by a million and you'll never exceed it in the minor versioning. The only problem is that we now have to update the versioning for all of our three upgrade plug-ins, because they all need to know locally how to find the version number of their file types (because the upgrade manager has no knowledge of the file types) and they have no access to each other because a plug-in may be disabled.

Contributes to issue CURA-3427.
2017-05-11 17:31:37 +02:00
2015-09-17 17:05:01 +02:00
2017-05-09 12:59:16 +02:00
2017-05-09 14:45:39 +02:00
2015-06-24 12:06:00 +02:00
2017-03-18 09:57:09 +01:00
2016-01-25 18:47:00 +01:00
2015-09-03 10:18:10 -07:00
2016-04-29 11:32:33 +02:00
2017-03-05 14:16:36 +01:00

Cura

This is the new, shiny frontend for Cura. daid/Cura is the old legacy Cura that everyone knows and loves/hates.

We re-worked the whole GUI code at Ultimaker, because the old code started to become a unmaintainable.

Logging Issues

Use this template to report issues. New issues that do not adhere to this template will take us a lot longer to handle and will therefore have a lower pirority.

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
    • $User/AppData/Local/cura/cura.log (Windows)
    • $User/Library/Application Support/cura (OSX)
    • $USER/.local/share/cura (Ubuntu/Linux)
  • The Cura Engine log, using Help -> Show Engine Log

Dependencies

  • Uranium Cura is built on top of the Uranium framework.
  • CuraEngine This will be needed at runtime to perform the actual slicing.
  • PySerial Only required for USB printing support.
  • python-zeroconf Only required to detect mDNS-enabled printers

Configuring Cura

  • Link your CuraEngine backend by inserting the following line in home/.config/cura/config.cfg : [backend] location = /[path_to_the..]/CuraEngine/build/CuraEngine

Build scripts

Please checkout cura-build

Third party plugins

Making profiles for other printers

There are two ways of doing it. You can either use the generator here or you can use this as a template.

  • Change the machine ID to something unique
  • Change the machine_name to your printer's name
  • If you have a 3D model of your platform you can put it in resources/meshes and put its name under platform
  • Set your machine's dimensions with machine_width, machine_depth, and machine_height
  • If your printer's origin is in the center of the bed, set machine_center_is_zero to true.
  • Set your print head dimensions with the machine_head_shape parameters
  • Set the nozzle offset with machine_nozzle_offset_x_1 and machine_nozzle_offset_y1
  • Set the start and end gcode in machine_start_gcode and machine_end_gcode
  • If your printer has a heated bed, set visible to true under material_bed_temperature

Once you are done, put the profile you have made into resources/definitions, or in definitions in your cura profile folder.

Description
No description provided
Readme 1.8 GiB
Languages
Python 71.3%
QML 25.6%
GLSL 1.4%
Rich Text Format 0.9%
Jinja 0.5%
Other 0.1%