Jump to content
Ultimaker Community of 3D Printing Experts
  • Sign Up

schpongo

Member
  • Content Count

    13
  • Joined

  • Last visited

Community Reputation

1 Neutral
  1. Hi, I have a quick question, I would like to know how Cura handle layer changes. Based on looking at some sample gcode I would say that a layer change in Cura is always performed without extruding any material. Is this correct? Are there any special cases where this might not be the case? Greetings Daniel
  2. I was able to solve the problem by changing the changing the version number in the metadata section to 13: [metadata] setting_version = 13
  3. Thanks for the reply but the problem persists. I've attached the changed files. resources.zip
  4. Hey, I've written my own definition, extruder and variant files for my printer. This morning I upgraded to 4.6 and now my variants are gone. To make sure that it was "caused" by the update I reverted to 4.5 and there I can still chose my different variants. I'll attach one of the variant files, the definition file and the extruder file. I'm glad to receive any suggestions Greetings Daniel Archive.zip
  5. Thanks for the answer, that worked perfectly. But I must admit I found a simpler solution to my problem. I was frustrated by using skirts because it took away too much from my build area. But this was only due to the fact that I had set the skirt distance to 10 mm. should work out perfectly: "adhesion_type": { "default_value": "skirt"}, "skirt_brim_minimal_length": { "default_value": 750, "value": "60/(layer_height_0*line_width)", "minimum_value": "0", "minimum_value_warning": "25", "maximum_value_warning": "4000" }, "skirt_gap": { "default_value": "1`", "value": "3*wall_line_width_0" },
  6. Hey, I'm in the process of making a custom definition file for my delta printer, I also have variant files for different nozzle sizes. For priming my nozzle I used to use skirts because that was easy. I experimented a bit and was able to determine that my printer needed about 60mm^3 of filament to fully prime my nozzles. This allowed me to calculate my minimal skirt length, for different layer heights and nozzle/line_widths, in the "overides":{...} section of my definition file: "skirt_brim_minimal_length": { "default_value": 750, "value": "60/(layer_height_0*line_width)", }, The problem with using skirts is that my maximum build area is reduced. So I'm looking at other ways of priming my nozzle which have a minimal influence on my printing area and which I don't have to worry about removing during the print because the might interfere with the print it self. I thought of using a G2 arc command in the start code of my machine. This way I can print at the very outside of my bed and the gcode itself is very small. The problem I'm encountering during the implementation ist that I would ne to insert calculated values into the start code. And I'm not sure on how to achieve this. Here is an example of what I would like to do but what sadly doesn't work: "platform_adhesion": { "children": { "_prime_arc_start_x": { "label": "Prime arc start point in x", "description": "The starting point in x-axis direction of the priming arc", "unit": "mm", "type": "float", "default_value": "0" }, } } }, "overrides": { "default_value": "G1 X + '_prime_arc_start_x'" } I've played around quite a bit with this but haven't been successful. I've tried: - changing the type from "float" to string" - using python syntax to put variable into the string (link) Even if I get this to work I'm not sure on how this would behave if I change my nozzle/variant once cura has been started. Does anyone have any ideas on how I could either put values into my start code or have any other suggestions on how to prime my nozzle in a good way using the priming volume of 60mm^3? Greetings Daniel
  7. Sad. Do you think this would be a desirable feature? I don't not a lot of people are creating their on definition files but it would definitely help those people out how do.
  8. Hey I have a quick question, because I have many entries in the "overrides": {...} section of my definition file I was wondering if it is possible to organise these in section life it is done in the fdmprinter.def.json. What I would like to have is something like this: "overrides": { "machine_settings":{ "machine_shape": { "default_value": "elliptic" }, "machine_width": { "default_value": 270}, "machine_depth": { "default_value": 270} } } By doing this I could keep the overrides all in their corresponding sections, an the sections would be collapsable in my editor. I tried what I posted above but that sadly doesn't work. Does anyone have any ideas? Thanks for the help! Daniel
  9. I've spent some more time trying to accomplish this, but so far I've been unsuccessful. I used your example and copy pasted it into the "overrides":{...} section of my definition. I did not add anything to my variants file because I wanted to check if this worked before. But what you suggested simply does not work for me. The "Printing temperature" is always marked red (see image). So I tried adjusting you code. I add and removed the following fields: - "unit": "°C", - "type": "float", - "value": 210, - "enabled": true, - "settable_per_extruder": true, - "settable_per_mesh": false, I also tried moving the definition of "_material_print_temperature_maximum_value" to the "metadata": {...} section or creating my own section before or in "overrides": {...} named "own_values": {...} which then contained the definition of "_material_print_temperature_maximum_value". But this all didn't work. I also tried using "_material_print_temperature_maximum_value" in other places (e.g. "material_print_temperature_layer_0") as the actual value and not just to calculate the warning. This lead to the values turning to zero (disabled?). Last I copied your code into the definition file from the original Ultimaker: "overrides": { "_material_print_temperature_maximum_value": { "label": "Maximum Printing Temperature", "description": "This is a private setting, please ignore", "type": "float", "default_value": 222, "enabled": false, "settable_per_extruder": true }, "material_print_temperature": { "minimum_value": "0", "maximum_value_warning": "_material_print_temperature_maximum_value - 5", "maximum_value": "_material_print_temperature_maximum_value" }, But this also leads to the "Printing Temperature" being marked red (see image). To me it seems my definition of the new value is not working as I also can't use it as a value for other predefined definitions.
  10. Hey thanks for the answer! I'm sorry that it took me so long to reply. I tried what you suggested but didn't have any luck. It seems like I can't define new values in cura. Did you try you code?
  11. Thanks for the answer. I like the approach, but I would need to be able to get the current variant name in the definition file. I'm not sure how much python code I can actually use but I'm thinking of something like this: "material_print_temperature": { "minimum_value": "0", "minimum_value_warning": "0", "maximum_value_warning": "230 variant_name.find('PTFE') > 0 else 300", "maximum_value": "235 if variant_name.find('PTFE') > 0 else 300" }, But this doesn't work, I guess because the variable "variant_name" doesn't exit. Does anyone have any input on this? Greetings Daniel
  12. Hey, I have a printer with one extruder and two different hotends. One of them is an all metal hotend which supports temperatures of up top 300°C. The second hotend is a PTFE lined one which only supports temperatures of up to 245°C. In my printer definition file I've set: "default_material_print_temperature": { "minimum_value_warning": "0", "maximum_value_warning": "230", "maximum_value": "235", "minimum_value": "0" } Now I would like the variants file for the all metal hotend to change the warning and min/max values. But since the variants file has a different format I'm not sure how to do that. I've tried: [values] machine_nozzle_size = 0.4 material_print_temperature_maximum_value = 300 but this didn't work. How would I go about achieving this? Greetings Daniel
×
×
  • Create New...