Jump to content

MarcusWolschon

Member
  • Posts

    135
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by MarcusWolschon

  1. Does it contain anything that shall not be public (names of model files, ...)?
  2. It was the same ID in Cura 3.0.4 and 2.5 and 2.2 and ... So I highly doubt that. Probably some incompatible change in the profiles this machine type has to inherit from or something that didn't copy over from 3.0.4.
  3. "Could not deserialize container Ultimaker 2 Extended 1.0mm" "ERROR - UM.Logger.logException [80]: Exception: When trying to deserialize Ultimaker 2 Extended 1.0mm, we received an unknown ID (ultimaker2_extended_1.0) for container" Comparing 3.0 and 3.1, everything seems to be there. The printer just doesn't load and thus never shows up. Again, where do you want this log to be sent to? It's way too long to quote it. (44.4MB)
  4. Where does the Windows version store it's logs and logs of what time period do you need? Log of the installer? Of a 3.1 startup? ... Where do you want me to send that log to?
  5. I have an Ultimaker 2 with Olsson block and Reprap g-code defined and it has custom materials and printing profiles. However after installing Cura 3.1 only the 2 other (less relevant) printers show up. There was no warning during the installation process that something could not be imported. Of cause Printers in Cura have no "export"/"import" functionality, so I can't get it into Cura 3.1 using the GUI. These are not beta-versions. These are stable releases.
  6. I meant in the Program Files folder. Thanks. What do you do when the next Cura update comes?
  7. You would have to add a "variant" definition file. Create a copy of resources/variants/ultimaker2_extended_0.8.inst.cfg and replace 0.8 by 1.0. I don't seem to have a "resources" directory in "C:\Users\\AppData\Roaming\cura\2.6". There is a "variants" directory but it contains the 3 defined printers Custom+FDM+printer_variant.inst.cfg Ultimaker+2+Extended_variant.inst.cfg Ultimaker+2+Extended+1.0mm_variant.inst.cfg No files for the individual nozzle sizes a printer can have. The last file contains [general] version = 2 name = Ultimaker 2 Extended 1.0mm_variant definition = ultimaker2_extended [metadata] type = variant [values] machine_nozzle_size = 1 machine_gcode_flavor = RepRap (Marlin/Sprinter) but only "Automatic", "0.25", "0.4", "0.6" and "0.8" can be selected in Cura 2.6 Beta.
  8. I cannot find it. Do you mean "Fuzzy Skin"?
  9. With the Cura 2.6 Beta I can now select the nozzle size for my Ultimaker II extended with Olsson block... but how can I add the fact that I have a 1.0mm nozzle that I use most of the time for large, mechanical parts?
  10. The produced G-Code for the E axis is in mm, isn't it? So the geared down extruder in an UM2+ make no difference when the produced g-code is executed on a UM2. I don't see a way to export machines and materials in Cura2.3, so I guess I have to do this on MacOS and then again when I switch from MacOS to Windows?
  11. So Cura 2.3 is a minor, compatible upgrade (still a 2.x). However it doesn't seem to see any of my machine definitions, printing profiles, material definitions and no longer have a "nozzle size" parameter that can be made visible. Is there any user-documentation about how to migrate your settings?
  12. The title says it all. Cura 2.3 ignores all machines, printing profiles and custom materials I have in my home directory in .cura and the directory structure inside the Cura.app MacOS executable is very different. I tried to set up a new "custom FDM printer" using the new GUI dialog for that but * most settings are not in that GUI (e.g. disallowed areas) * it asks for some "printhead settings" with X+Y min+max but doesn't explain what that refers to and the "online documentation" doesn't work in Firefox on MacOS as it loads without any stylesheet and is thus unusable. I can no longer make a "nozzle size" setting visible. With an Olsson Block on my Ultimaker II with Reprap G-Code flavor (to run it via Octoprint) I often swap nozzles.
  13. MarcusWolschon, You may be aware of this trick. If you print PLA at 210 C on a 60 C bed, as is the Ultimaker 2+ default, and you let the bed cool to 30 C after printing, the item will just twist or slide right off of the glass easily. Therein lies the way! Les As long as you print in PLA....
  14. Has anyone tried taking the glass bed and replacing it with a fresh one automatically? I guess you'd need to * apply gluestick automatically * possibly auto-level the bed * possibly change the way the fasteners work.
  15. Anything that works for pause and resume? On resume I'd like to extrude, then go to the last XY position, then lower the head again. Of cause in the resume-script for Octoprint I have no idea what the last XY positon was.
  16. Cura 2.1.x often forgets the height of the build volume of my Ultimaker II extended. Then the maximum height is some kind of default. See attached picture. The only thing that helps is to remove all machine_instances and re-create the printer. Did anyone else experience this? This happens with the default printer profiles that have not been modified in any way. I created a GitHub issue with a screenshot: https://github.com/Ultimaker/Cura/issues/870
  17. has the temperature settings of the parent Ultimaker profile an "uneditable" or "hidden" settings that overrides the material? I'm just guessing.
  18. look if it shows two PLA materials now. mine aggregate both directories, so I can add but not overwrite materials.
  19. Murphy: It seems that no issue ticket existed for that behavior. I created https://github.com/Ultimaker/Cura/issues/850 and for a related issue https://github.com/Ultimaker/Cura/issues/849 I cloned the sources to my local machine but I doubt that I'll have the time to dig deep enough into them to find the issue myself. But educated guessing came up with a solution for you: When you copy fdmprinter.json, ultimaker2.json ... from ..../Cura 2.1.2.app/Contents/Resources/cura/resources/machines into ~/.cura/machines then everything works. Aparently it looks for the parent files only in the same directory, where it got the json file given by the UI. You can also add additional materials to ~/.cura/profiles/materials but be careful, the file structure is identical to the MATERIALS.txt that the firmware imports from an SD card but the property and section names inside are different. Strange design decision. I haven't checked overriding fan_speed or diameter yet (I override these in MATERIAL.TXT). I updated by Octoprint+UM2 guide at http://marcuswolschon.blogspot.de/2016/06/getting-started-with-raspberry-pi-3.html accordingly and should now be able to use Octoprint for my ultimate filament monitor and avoid modifying the firmware to pause prints.
  20. https://github.com/Ultimaker/Cura/issues/847#issuecomment-230454073 apparently that secondary location for json files exists. It just wasn't documented and nobody here knew about it.
  21. So you WOULD support an Ultimaker USB printing profile my merging a pull request if someone else was to write the json and create such a pull request? I thought you just said that you're don't support Ultimaker USB printing. I can do that one of these days but obviously merging it would mean for it took end up in the selection dialog. Visible for each user. Still, why not allow reading machine definitions from a secondary location outside the '.app' package in addition to the ones supplied with the app? Wouldn't that be a far more reasonable change? That would allow for defining machines that have no point in being part of the selection dialog of every single Cura out there. (e. g. 'Marc's custom machine #12')
  22. but the. json files are not in the user home directory or in the /Library/application support directory. They are part of the application. They exist separately for every version of Cura that is on a Mac computer and are contained again with every updated version that will ever be downloaded. Each version in turn will ignore all such files contained in any other version. The are simply stored in the wrong place if they are to be modified on this platform. If there was a secondary directory in /Library/application support/Cura/2.1.2 or something, I'd be happy to do so. Currently it means that the only PROPER way for me to add a custom printer (apart from a pull request that will never get merged as you officially don't support my two printers) is to maintain a fork at GitHub and build and cryptographically sign my own cura.app packages.
  23. Found the material settings but without recursive entries I can't do something like material->settings->material_print_temperature->visible=true Obviously no clue how to enable a way to choose betwen any of the materials defined in /Users/marcuswolschon/Desktop/Cura 2.1.2.app/Contents/Resources/cura/resources/profiles/materials or how to add a new one to that list. As these are the same, strange .ini files, I guess creating a new directory "materials" in my home directory in .cura/ and placing one there would work. ..this is all just terribly frustrating guessing and reverse engineering while it should have been right up there at https://ultimaker.com/en/resources/20511-change-machine-settings as everyone with a machine that's not in the list has to do this.
  24. Major breakthrough! I found out how to do multi-line entries. So start- and end- gcode work now. For some readon it does remove every line that is only a comment....except the first. So I can't have a nice delimiter at the end of start_gcode and at the start of end_gcode or any comments to make it more human readable for debugging. machine_height is still ignored. No idea what I could even try about that one. has_materials = true enables a new section but I can't add any temperature entries to it (all greyed out, so I can't make them visible) and no selection of an actual material although Cura does include a very short list of material definitions. # [general]name = Ultimaker 2 Extended (Octoprint)type = ultimaker2_extendedactive_profile = Normal Qualityversion = 1[machine_settings]machine_height = 315uses_materials = truemachine_end_gcode = ;Gcode commands to be executed at the very endM104 S0M140 S0G92 E1G1 E-1 F300G28 X0 Y0M84machine_start_gcode = ;Gcode commands to be executed at the very startG28 ; HomeG1 Z15.0 F6000G92 E0G1 F200 E3G92 E0machine_gcode_flavor = RepRap
×
×
  • Create New...