Jump to content

ahoeben

Ambassador
  • Posts

    5,024
  • Joined

  • Last visited

  • Days Won

    359

Everything posted by ahoeben

  1. This is untrue. The location that you mention/found is where default profiles are stored, not where user-created configuration data is stored. Cura cannot even write to the location you mention (unless you launch Cura with administrator privileges, which you should not do). The user-created configuration data is stored where it has been stored since Cura 2.5: %APPDATA%\cura, in a folder with the name of the Cura version. So in most cases, for Cura 5.0, that would be C:\Users\[your username]\AppData\Roaming\cura\5.0 I cannot stress enough that it is inadvisable to change files in the Program Files\Ultimaker Cura 5.0\ folder.
  2. The Gcode postprocessing is not performed until you save the gcode, so it is not showing on the preview tab. The plugin does not affect all the F-values in the gcode after the change, but inserts a single M220 gcode command to instruct the printer to "multiply" the F-values internally: https://marlinfw.org/docs/gcode/M220.html
  3. Or use the "Search..." box on top of the custom settings and search for "Z offset".
  4. If that geometry is flat, then exporting it as an SVG and using the SVGToolpathReader plugin (in Cura 4.13) will go what you want.
  5. It is rather hard to see what you want to do from these images, but perhaps you are interested in this plugin: https://github.com/Ghostkeeper/SVGToolpathReader It does not yet seem to have a release for Cura 5, so you would have to use Cura 4.13 to use it.
  6. That list (http://files.fieldofview.com/cura/Replacement_Patterns.html) just shows the descriptions defined in fdmprinter.def.json and fdmextruder.def.json, which are the same descriptions as shown in the tooltips inside Cura. Only the "Application defined pattern" descriptions are my texts. Not all descriptions are great explainations of what each setting does. The {extruder_nr} replacement pattern only makes sense in the "Extruder Start G-code" and "Extruder End G-code". Here {extruder_nr} will point to the extruder that is starting resp. ending (ie the extruder mentioned in the tab for the extruder start/end gcode you are editing in the Machine Settings). In the "Start G-code" and "End G-code", {extruder_nr} is undefined (or at best it might return 0).
  7. The Ultimaker S5 is not compatible with OctoPrint; there is no way for OctoPrint to talk with the UM S5. So if your currently active printer is an Ultimaker S5, the "Connect to OctoPrint" button is not shown. If you activate the Anycubic printer in Cura, the "Connect to OctoPrint" button will show.
  8. If you remove an instance of a setting from a container, a signal is emitted to update the container, which causes other signals to emit, and a whole set of effects start to happen. If you want to remove multiple instances, then it would cause a lot of unnecessary signals being emitted inbetween. The postpone_emit option basically tells Cura to perform the change to the container, but wait before telling the rest of Cura until you are done with the last manipulation of the container.
  9. It appears you have an "essentials" or "enterprise" subscription. If you do, you are only offered a subset of Cura plugins which have been "approved" to be "secure". That does not mean that the other plugins are in any way "not secure", but they have not been inspected and approved (and for many of them Ultimaker does not plan to have them approved either, AFAIK). I must say I am a bit mystified by the logic of this "pay to have less functionality" model, but it is out of my control. Please try the following: * In the marketplace, uninstall the OctoPrint Connection plugin * Restart Cura (this is important!) * Back in the marketplace, install the OctoPrint Connection plugin again * Restart Cura again. It is important not to skip the second step! If these steps do not fix your issue, I need to see you cura.log, which can be found via Help -> Show configuration folder.
  10. Yes, those are your only options at this point.
  11. The latest version of the Material Settings plugin has removed the menuitem from the Extensions menu and instead adds a button to the Print Settings tab in the Material preferences: Also see the updated instructions in the readme here: https://github.com/fieldOfView/Cura-MaterialSettingsPlugin
  12. Two problems: * It seems like op has a UM2+ Connect, which is a more complex machine than the UM2+, especially when it comes to firmware * Even with a UM2+, it can be hard to install the firmware onto a non-functioning board with Cura; Cura 2 and newer need to detect the printer as a printer before it will allow updating the firmware.
  13. The Ultimaker originally came without a controller, and for a period the controller was sold as an optional accessory for the Ultimaker (before it was even called the Ultimaker Original). It would typically be connected and controlled via USB. Changing filament can be done by preheating the extruder (on the Monitor tab in Cura), then opening the extruder on the printer and gently pulling out the material. You can then replace the spool, and feed new material in. Another good option to check out is using OctoPrint, which integrates well into Cura by using a plugin from the Marketplace.
  14. The path hasn't gotten prettier, has it? Anyway, the better location to use would be the configuration folder (%APPDATA%\cura\5.0).
  15. That's the problem. You have to not set anything in the quality profile. Once it is in the quality profile, you cannot easily unset it in Cura. The material settings plugin has an option to use the value from the material. Right click on the flow setting in the (custom) print settings.
  16. Firmware-wise, there is no reason there would be a difference in z-offset after homing. You could compensate for what you see with the Z Offset plugin from the Marketplace.
  17. You are going to have to be more descriptive. What exactly is the problem? What do you do, and what happens? It is also useful to know what OS you use.
  18. It is small and subtle, but there's a small "x" to remove the script next to the up/down arrows:
  19. Heb je TinkerCAD al eens bekeken? Dat is gemaakt voor dit soort toepassingen: https://www.tinkercad.com/3d-design Je moet alleen wel bedenken wat je wilt maken, maar dat is met een zaag of een soldeerbout niet anders.
  20. Cura normally stores the last location you opened a 3d model from. However, Cura uses the file dialog provided by the OS, and if that file dialog does not accept the stored last location, then (re)setting that location in cura.cfg will likely not do you any good. So in short: there is no way to change that (other than fixing this slight incompatibility between Cura and your OS)
  21. Cool! (one plugin idea to scratch off my todo-list, thanks!)
  22. I think the watertight message you get is from the Mesh Tools plugin, not from Cura itself. Mesh Tools uses a different method than what you can see in X-ray view. X-ray view highlights "unmatched" faces, ie a front that does not have a back. See the figures here: https://github.com/Ghostkeeper/SettingsGuide/blob/master/resources/articles/troubleshooting/missing_parts.md#non-manifold-meshes Mesh Tools checks if all edges defined in the mesh are part of exactly two faces. This is a much more "exact" way of testing for watertightness, but for the purposes of slicing with Cura it can lead to false positives when a model includes multiple copies of the same vertex so some "touching" faces don't "connect" on the same edge. In the case of this model, 3D Builder agrees that it is "invalidly defined" and can repair it, but MeshMixer says there's nothing wrong with it. Different methods of checking. If you find that Mesh Tools often has false positives for the type of models you print, you can turn off its check after loading models in Extensions -> Mesh Tools -> Mesh Tools Settings...
  23. If uninstalling and reinstalling Cura works, you might want to try unchecking the "Restore window position on start" in the General pane of the preferences.
  24. It looks like this is a known issue with Cura 5 (and Arachne before it): https://github.com/Ultimaker/Cura/issues/11877
  25. Arachne has been merged into Cura 5. There will be no more Arachne builds, but Cura 5 will get continued development. Use Cura 5 now, instead of the Arachne test builds.
×
×
  • Create New...