Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BUG - Slicing Error with Cura 5.6.0 #18170

Closed
digidiver11 opened this issue Jan 29, 2024 · 1 comment
Closed

BUG - Slicing Error with Cura 5.6.0 #18170

digidiver11 opened this issue Jan 29, 2024 · 1 comment
Labels
Status: Triage This ticket requires input from someone of the Cura team Type: Bug The code does not produce the intended behavior.

Comments

@digidiver11
Copy link

Cura Version

5.6.0

Operating System

Win10

Printer

My Printer

Reproduction steps

I had incomprehensible crashes when slicing my workpieces. After a long search, I found the cause in my self-written printer file.
As there is unfortunately no good documentation for this, I had taken many entries from other printer files and thus copied a faulty entry.

Many errors of this kind are in the file (and others) "ultimaker2.def.json":

Lines like this are wrong :

    "gantry_height": { "value": "48" },
    "material_bed_temperature": { "maximum_value": "110" },
    "material_bed_temperature_layer_0": { "maximum_value": "110" },

Probably also wrong:

    "machine_name": { "default_value": "Ultimaker 2" },

Das Problem sind "" bei den Werten !
Richtig müsste es wie folgt heißen:

    "gantry_height": { "value":  48  },
    "material_bed_temperature": { "maximum_value":  110  },
    "material_bed_temperature_layer_0": { "maximum_value":  110  },

Presumably too:
"machine_name": { "default_value": Ultimaker 2 },

Since I removed this "", my Cura has been running correctly again!

However, I was shocked at how often this error can be found in the printer files and other files.

I have a few requests, which unfortunately I can't answer myself yet, as I haven't been working with Cura for very long:

  1. Finally a proper documentation, also with explanations on how to create a printer file CORRECTLY. I notice that a lot seems to have been put together here and that many users just copy the files together.

  2. A possibility or simply a short guide to really remove ALL superfluous printer and filament files and much more.
    Many files unfortunately also contain many errors.

Thank you and I hope I was able to contribute to troubleshooting.

Actual results

Since I removed this "", my Cura has been running correctly again!

Expected results

Since I removed this "", my Cura has been running correctly again!

Add your .zip and screenshots here ⬇️

Temp.zip

@digidiver11 digidiver11 added Status: Triage This ticket requires input from someone of the Cura team Type: Bug The code does not produce the intended behavior. labels Jan 29, 2024
@HellAholic
Copy link
Contributor

Hey @digidiver11 ,
Nice to hear that you managed to figure out the problem in your printer definition.
Please note there is a wiki section containing documentation such as https://github.com/Ultimaker/Cura/wiki/Definition-Files-Explained, beyond that you can always engage and ask the community for help.

As the document states, it's best practice to use fdmprinter.def.json as your reference. If you would like to participate in creating definition files you can always create a PR and the community will be there to test and provide feedback.
see #17576 as an example.

If you would like to have a custom version of Cura with only your desired printers and materials, you can do so by modifying and building your own personal version as Cura is open source. You can follow the wiki for how to get started. https://github.com/Ultimaker/Cura/wiki/Getting-Started

Hope that helps.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Triage This ticket requires input from someone of the Cura team Type: Bug The code does not produce the intended behavior.
Projects
None yet
Development

No branches or pull requests

2 participants