Jump to content

ahoeben

Ambassador
 View Profile  See their activity

  • Posts

    4,962

  • Joined

  • Last visited

  • Days Won

    342

 Content Type 

Everything posted by ahoeben

  1. ahoeben
    The memory issue that I reproduced is fixed, in both 3.5 and 3.6 (the new version of the OctoPrint plugin is compatible with both). But there could be another (or a new) leak that I don’t yet know about, so please test and let me know.
  2. ahoeben
    Marketplace should have an updated OctoPrint plugin.
  3. ahoeben
    I think in this particular case, the new minor release was pushed forward a bit to get the support for CC cores out.
  4. ahoeben
    Once a branch is made for a minor version (3.x), no new feature is allowed in that branch; in revision releaes (3.5.x) only fixes are allowed. The new beta contains new features, so a new minor version is needed.
  5. ahoeben
    Note that these orphaned tray icons by themselves are very much harmless. Yes, the not exiting cleanly part may be indicative of something else also not being cleaned up properly, but don't focus too much on the tray icons.
  6. ahoeben
    A more proper description would be that Cura does not close cleanly, leaving behind systray icons when you quit Cura (if I understand you correctly). The "silent crash" name was just me trying to separate this from a "memory leak", which this is not. What seems to be happening is that Cura exits ("crashes") before cleaning up the tray icon, without showing an error message ("silently")
  7. ahoeben
    And a few old things that are new: * a memory leak in Cura Connect and OctoPrint was fixed. Note that the Toolbox contains a new OctoPrint plugin that works in both 3.5 and 3.6 which includes the fix. * a couple of issues related to USB printing are fixed (temperature updating during heatup sequence, and extraneous "Press to resume" messages during printing with Marlin 1.1.8+
  8. ahoeben
    123d catch used “the cloud” for computation, and the servers have bee shut down 1.5 years ago. Even if you still have the software, it will not work.
  9. ahoeben
    https://ultimaker.com/en/products/ultimaker-cura-software/list
  10. ahoeben
    Cura 2.3 isn't very good at printing over USB to non-Ultimaker printers. It has improved some since two years ago, but it is still problematic for some printers (simply because Ultimaker does not support USB printing anymore). The printer you select from the list of printer models does not influence USB connectivity at all. If you really want to print over USB from a 32 bit Cura, perhaps it is better to use the "legacy" Cura 15.04.
  11. ahoeben
    A "resolve function" is used when a setting is defined per extruder, but a global value is needed. An example of such a setting is the material_bed_temperature; each extruder can have a different material, and each material prescribes a bed temperature. So which temperature should be used if the material need a different temperature? extruderValues is a function which returns a list of (evaluated) values, one for each extruder. You would have to pick one of these values.
  12. ahoeben
    In Extensions -> Post Processing -> Modify G-Code, add a "Search and Replace" script. For Search, enter ;.* (ie: semicolon dot asterisk) For Replace, enter nothing Turn on Use Regular Expressions
  13. ahoeben
    The latest 32 bit compatible version that was released by Ultimaker is Cura 2.3.1. That version is about 2 years old, so my memory is a bit foggy. You should be able to add your printer as a "Custom FDM Printer" (from the Other category). But realize that a lot has been changed in the past 2 years!
  14. ahoeben
    Aww, no love for the OctoPrint Connection plugin? The OctoPrint Connection plugin, available from the Toolbar, integrates OctoPrint into Cura so that you don;t have to save an intermediate gcode file. Just press "print" from inside Cura.
  15. ahoeben
    You could use the Search & Replace gcode postprocessing script and a simple regular expression pattern to remove a semicolon and everything following it. Or you could flash the printer with a decent firmware...
  16. ahoeben
    The plugin uses a similar (but different) trick to that, but adds a setting to the sidebar so you can edit the offset without having to go into Machine Settings to edit the start gcode. This setting can also be stored in profiles, so you can have different profiles with different amounts of "squish".
  17. ahoeben
    It is because the plugin specifically defines it as such: https://github.com/alekseisasin/SettingsGuide/blob/master/resources/qml/SettingsGuide.qml#L16
  18. ahoeben
    Unless someone wrote/writes a plugin for it, Cura does not support sending data over Wifi to your Davinci Pro. There is no (widely used) standard way to talk to 3d printers over wifi, so Ultimaker created their own for their printers. So did XYZ printing. The two "protocols" are not compatible. There's a plugin to print to most printers over the network using OctoPrint, but you would need a (small) computer connected to your printer over USB to run OctoPrint on (eg a Raspberry Pi).
  19. ahoeben
    @Msuurmond is the Product Owner of Cura. The forum is - and has been for a long time - a place for the Ultimaker Community to converse. As far as I know, it is not an official support channel.
  20. ahoeben
    It is provided by a plugin that has to be installed through the Toolbox.
  21. ahoeben
    Just to be sure it is not model-specific, can you post a link to a 123D Design model that exhibits the crash? Please go to Help -> Show configuration folder and locate cura.log. Now let Cura crash (by loading the model), and post the cura.log somewhere we can download it.
  22. ahoeben
    What version of Cura do you use? On what OS?
  23. ahoeben
    Cura only adds that heating sequence before the start gcode if it sees that you don’t have heating commands in the start gcode snippet. If you put M109 S{material_print_temperature} in your start gcode snippet, Cura will not have to add extruder heating by itself. Same with M190 S{material_bed_temperature} fir the bed. You could also use a postprocessing script to modify the gcode.
  24. ahoeben
    Without looking too much into the rest of the code, you are looking up the stacks in the __init__ method. That method gets called when the PostProcessing script discovers the available scripts, which might be before Cura has finished loading the printers from your configuration. Even if it worked, the information would also be incorrect once you changed to another printer in Cura. Don't do postprocessing things in __init__, but do them in execute.
  25. ahoeben
    Check cura.log in Help -> Show configuration folder. Search for the id (filename without .py) of your script, and it should give you a hint about why it is not loading. If not, I'm going to have to see the entire script.
×
×
  • Create New...