Jump to content

ahoeben

Ambassador
  • Posts

    4,966
  • Joined

  • Last visited

  • Days Won

    342

Everything posted by ahoeben

  1. Are you perhaps trying to run Cura through an RDP connection? This is not supported, because RDP "hides" the opengl capabilities of the GPU of the host computer.
  2. A gcode file contains instructions to move around a print head and heat up a hotend. It generally does not include any "settings". It could be that the settings are included as comments in the gcode file. Some settings, such as temperatures can be inferred from the gcode file. But there is no general way to go from a gcode file back to settings and a model.
  3. These settings are meant to be used with the "Per model settings" tool. They would have no function in the Print settings list, which is why you cannot make them visible there. The "support mesh" setting automatically gets set for settings you mark the be printed as support.
  4. Hi wrong. Sure. But you need external software to do so. Typically, timelapse recording software that works with "ip cameras" or "network cameras" works with the camera in your UM S5, as long as the computer running that software is on the same network as the printer. You would use an address like this: http://192.168.0.137:8080/?action=snapshot You would have to look up the ip address of your UM S5 printer on the network.
  5. Cutting objects at an arbitrary cutting plane is surprisingly more complex than you might think. It is not just a matter of removing all points on one side of the plane; it is very likely that the plane cuts halfway through a lot of faces. New vertices need to be added and connected into new faces, and the model needs to be kept "watertight" by adding caps to all now open areas and then still manual repairs might be necessary. It is a task that really needs to be done in an application with a much firmer grasp on the geometry than the Cura frontend has.
  6. This has nothing to to with the OctoPrint plugin, but with the naming of gcode files (or "job names" in Cura terminology). Jobnames are prefixed by default by an acronym of sorts derived from the printer model name (eg Ultimaker S5 becomes UMS5, Custom FFF Printer becomes CFFFP). You can turn off this automatic prefix in the General preferences. Because this is a bit inflexible (either a prefix that cannot be changed, or no prefix at all), I wrote another plugin called "Custom Printjob Prefix", which lets you set a custom prefix. If you have that plugin installed, you can change the prefix for the current printer via Extensions -> Custom Printjob Prefix -> Set prefix. You can set any text you wish there to be used as a prefix (or turn the prefix off if you want). Some special replacement patterns are available to be automatically replaced the current values. An important thing to realise is that the plugin will set the prefix for the current printer only. So if you have two printers configured in Cura, you would need to set the prefix for each printer individually.
  7. Go to the General pane of the Preferences. It is one of the top-most options. Personally I find the autoslicing mostly useful, but sometimes I find it annoying. That's why I made a plugin to quickly toggle the option. That plugin is available as "Automatic Slicing Toggle" in the Cura Marketplace. It adds a "pause/resume" toggle next to the "Slice"/"Save" button.
  8. I have made a small plugin for Cura that will let you export material cost information for a list of materials to a CSV file. This file can be easily edited in a spreadsheet application, shared with other users, and imported back into Cura. Price per roll and weight per roll information is not included with the XML file that defines a material in Cura; prices vary country-to-country and probably retailer-to-retailer too, and a single material may be available in different spool-sizes but still print with the same print settings. However, this leaves the material costing in Cura with a bit of a gap that a material manufacturer can not easily pass price information to its customers. With this plugin, they can. The plugin is available from the Marketplace in Cura. Some more information can be found here: https://marketplace.ultimaker.com/app/cura/plugins/fieldofview/MaterialCostTools The source of the plugin is available here: https://github.com/fieldOfView/Cura-MaterialCostTools Issues and feature requests can be posted here, or on the github issue queue for the plugin: https://github.com/fieldOfView/Cura-MaterialCostTools/issues
  9. Cura is not limited to any maximum nozzle size; the printer definition you selected probably is. If you add a new printer to Cura, and start with a Custom FFF printer, you can set any nozzle size you want in the Machine Settings.
  10. One major difference is that the Ultimaker releases all use a different configuration folder per version, so you can keep different versions of Cura installed and they do not interfere with eachother. Your builds (as far as I know) all use the "master" folder, so once you used a newer version of your builds chances are older versions of your builds will no longer be able to use the same settings because those have been upgraded for a newer version. You probably mention that in the readme, but since using different versions next to eachother is the subject of this thread, I thought it would be worth a mention.
  11. This is the list of current replacement patterns: http://files.fieldofview.com/cura/Replacement_Patterns.html
  12. One of the productive cool features in Cura is the postprocessing plugin. Extensions -> Post processing -> Modify G-Code. Especially the Search and Replace script is a very powerful tool; you can eg replace M140 S0 with M140 S50 if you wanted.
  13. You could try to increase the "Skin Overlap" (in the Shell catagory)
  14. Sorry, the definition for the private "_material_print_temperature_maximum_value" setting must be in a "settings" section, like so: "settings": { "material": { "children": { "_material_print_temperature_maximum_value": { "label": "Maximum Printing Temperature", "description": "This is a private setting, please ignore", "type": "float", "default_value": 230, "enabled": false, "settable_per_extruder": true } } } }, "overrides": { "material_print_temperature": { "minimum_value": "0", "maximum_value_warning": "_material_print_temperature_maximum_value - 5", "maximum_value": "_material_print_temperature_maximum_value" }, ... }
  15. I like how you "censored" that mesh 😉
  16. Best advice is don't bother trying. It works for some people, but chances of clogging the system, or worse flooding your whole printhead with solidified ABS are significantly greater than zero.
  17. Try printing at a lower speed. It could be you are asking too much from your bed-flinger printer.
  18. You did not have to go find them, they are included with Cura. If you want to compile it yourself, your best start-off point is https://github.com/Ultimaker/Marlin/tree/Marlin_UM_Original_Plus
  19. I have not yet gotten round to implementing the functionality of matching the reversedness of the axes with OctoPrint.
  20. You tossed (https://github.com/Ultimaker/Cura/issues/7359), I bit:
  21. I tried my code, but only with a different printer definition (the Ultimaker Original) because I don't have a complete definition for the FunMat printer.
  22. Cura already has variable layer height. But apparently, you want manually controllable variable layer height. It helps to be specific in your title.
  23. There's also a precompiled dual version for the UMO+ (sorry, I missed the +): MarlinUltimaker-UMOP-250000-dual.hex
  24. Looks like that site is no longer properly configured. There is nothing you can do about that, short of notifying the site owner. Cura comes with a precompiled dual extrusion firmware for the Ultimaker Original. Did you try if that works for you?
  25. A better place to store the plugin is inside the ````"plugins" folder in the Configuration Folder (See Help->Show configuration folder). Then you won't have this issue. A propos, that is why I asked (twice!) where you place the plugin files.
×
×
  • Create New...