Jump to content

ahoeben

Ambassador
 View Profile  See their activity

  • Posts

    4,974

  • Joined

  • Last visited

  • Days Won

    343

 Content Type 

Everything posted by ahoeben

  1. ahoeben
    It does not
  2. ahoeben
    I am not an expert on this type of thing, but that connection carries a lot of current. It is the type of connection that can cause fires when it has a bit of resistance and/or partially disconnects during use. It is something you will want to be careful with.
  3. ahoeben
    It helps if you are a client that's about to buy 100 Ultimaker printers 😉 More seriously though, it has been an issue for a long time, and it never got enough traction to get it fixed unfortunately. I don't know who's the "product owner" of Cura these days. The product owner has a large say in what gets fixed and what will remain open for the foreseeable future because there is too much to do. You could chime in here: https://github.com/Ultimaker/Cura/issues/4427 As another, more permanent workaround, it should be possible to write a plugin that forces Cura to always start on the primary screen. Thing is I already have 10 plugins to maintain and update between versions...
  4. ahoeben
    Yes, by using the correct replacement patterns in your start gcode. If Cura sees the actual use of the replacement pattern {material_print_temperature} in your start gcode, it will not add its own extruder preheating. Same with {material_bed_temperature} for the bed. And I mean that actual text, including the curly braces.
  5. ahoeben
    Not as far as I know.
  6. ahoeben
    Remember that these are beta builds of the plugins; please install the version from Marketplace instead once it is available (when Cura 4 beta 2 launches)
  7. ahoeben
    Sorry, I forgot about that. https://community.ultimaker.com/topic/25967-plugins-for-cura-40-beta/
  8. ahoeben
    Could you try with Cura 4 beta 1? I just tried with what will become Cura 4 beta 2, and at least there it seems to be fixed.
  9. ahoeben
    The surrounding grey margins are added so that the printhead won't collide with prints already on the buildplate. In the first 15.04 screenshot you can just about see that it adds a similar margin, though it is smaller (and much less visible). This could be caused by a bug in the printer definition (which defines the size of the head), or a bug in Cura (which uses the defined head to calculate the safe margin). You did not mention what printer you use.
  10. ahoeben
    Try turning off one-at-a-time slicing.
  11. ahoeben
    ...and material, and even the type of model and what you define as "best quality". "Best quality" can mean best looking surface, or it can mean best achievable strength, or something else entirely. And sometimes improving one thing can negatively influence the other. If there were one profile that would give you "best quality" for all printers, configurations, materials and for all different models, Cura would surely ship with that profile (and there would be no reason for most of the 300+ settings that you can use to tweak your print).
  12. ahoeben
    Awesome! To be honest I don’t really know how you could have broken the bootloader without breaking the rest*, but logically it was the only thing that was left to try. Glad it worked! *: it is possible to flash Marlin to the atmega instead of the bootloader. This would have given you a working printer without a bootloader. But that is not something that happens accidentally.
  13. ahoeben
    Make sure Cura is on your primary screen when you close it.
  14. ahoeben
    It could be that it has never been properly grounded, and something else on the same group has recently started to leak some charge to the ground. Try plugging the printer in in another part of the house (eg the kitchen, which is usually on a group of its own)
  15. ahoeben
    Is the power socket you plug the power supply in properly grounded?
  16. ahoeben
    Compare the gcode output. Export a gcode for a small cube from both versions, and we can start to see what it different between the two. Cura has a LOT of settings. Not all settings are shown but they can still influence your print. It could be that the printer definition you used was changed ("improved") between 2.7 and 3.6. It could be that you forgot to install a plugin in 3.6 (Z Offset plugin?).
  17. ahoeben
    I think the default Atmega 2560 bootloader for Arduinos should do. And you would use an ISP device on the header marked ICSP1.
  18. ahoeben
    The "Add settings" dialog is a "modal" dialog. You can not interact with other elements of the application when a modal dialog is open. The Preferences window is also a modal dialog. Most of the "system-themed" dialogs that you encounter in Cura are. The support blocker tool is not called the "generic cubes tool". You can use the Per model settings tool on the created cubes, but it is not the intended use. Strangeness may ensue.
  19. ahoeben
    Sounds like the bootloader on your board is somehow broken, as you suspect. If you don't want to risk further mucking up the printer by replacing the bootloader, you could get a cheap chinese motherboard and keep the one with the broken bootloader as a spare.
  20. ahoeben
    In the Marketplace there is aplugin named MeshTools that adds the functionality (and some other tools).
  21. ahoeben
    Try 3.6. The plugin is available through the marketplace in that version.
  22. ahoeben
    When you start Cura with your printer connected over USB, does the printer reset? I was hoping for a log of the crash you mentioned.
  23. ahoeben
    I have created a version of the OctoPrint Connection plugin that is compatible with Cura 4.0 beta 1: http://files.fieldofview.com/cura/OctoPrintPlugin-v6.0.0-2019-01-28T16_19_16Z.curapackage Originally I planned to skip compatibility with Cura 4.0 beta 1, because changes that would be necessary for compatibility with beta 2 and beyond. The second beta was originally planned for halfway through januari. However, because the second beta still is not available, I have worked around this issue resulting in the version linked above.
  24. ahoeben
    Here's the best reference I can do: "It is not possible to do arithmetic in gcode snippets in Cura"
  25. ahoeben
    Can you share your cura.log? Help->Show configuration folder. It may be large, so please send it to yourself via wetransfer.com or so and post a link here.
×
×
  • Create New...