thopiekar

The problem with the XY calibration is that it's not un-/retracting. Cura's default setting is to do exactly this. So that's why the filament is too far away from the nozzle. Anyway, the XY calibration is actually a gcode that is stored in the firmware. It assumes the scenario that the printcore is ready to be used. So what Ultimaker needs to do (or you if you know how to hack your printer) is to add the instruction for the printer in this gcode to do the un-/retraction. That should be it if I'm not wrong.

Is there a reason you are still using 3.6? Would suggest retrying with 4.0 and see whether it still occurs. Personally, I doubt that you will still get support for 3.6. Even if someone finds a bug in this release, there will be never an updated version of it, e.g. version 3.6.1. It is normally not intended by Ultimaker to release bugfixes for older versions.

Stimmt so. Daran hat sich in den Einstellungen nichts geändert.

No problem. At the moment I'm about to correct an issue around the conversion process in the plugin, too. You probably noticed issues with that already. Feel free to join the general discussion all around the plugin here:

@RobyRob You can find the macro (Python script) for the conversion inside the plugin here: https://thopiekar.eu:5443/cura-cad-integration/CuraFreeCadPlugin/blob/master-updating-conversion-script/CuraFreeCADPlugin/scripts/convertIntoSTL.py This is the one I use in the latest unreleased package. As far as I understand, after opening the file I should be able to get the active object via native_file.ActiveObject, no? So the differences you probably see, is that you have unsaved changes. The plugin runs FreeCAD and the mentioned macro in the background. It doesn't know anything about the unsaved changes someone made inside FreeCAD's window at the moment.

That is correct. In the object tree (where you see all steps, which have been done to build your body) you will see the active object in bold letters. Normally, this is the state which you can see in the 3D view at the same time. So what you see after opening FreeCAD, should be what you get in Cura. 🙂

Yes, it is the same, but it is a nightly build. In short: The package has been built automatically without increasing the version. It will be 0.3.1 in the future if nothing comes in between. If someone else could also confirm that everything works great, I'll care about uploading it to the marketplace as soon as possible. If there is anything else like other remaining problems or missing features, please share them in the other thread I mentioned above! 😉 Regards - Thomas

@MadCooper There seems to be something missing in your code for your pyd file. Cura (actually the embedded Python interpreter) should be able to pick it up normally. I've embedded PyWin32 into my CAD plugins and it comes with many pyd files and works fine. You probably want to take a look into SWIG or Cython to be able to code with fewer hassles and let one of these projects generate the C/C++ code you need. Maybe this is something for you! 🙂

Here another thread, but for the OpenSCAD plugin. Would be great if we as a community could come together here and discuss new features and current problems with the plugin. Looking forward to interesting conversations! 🙂 Website: http://thopiekar.eu/cura/cad/openscad/

Hello @RobyRob and @WielGeraats, I don't know why, but I either overlooked the notifications about your posts in this thread in my inbox or I never got them. Anyway, I added an official thread as for all the other plugins. Now something that might be interesting for you: I also faced the problem in the meantime and fixed it for me. It would be great if at least one of you could test the unreleased plugin. The download link and an (updated!) installation guide can be found in the official thread soon! Regards - Thomas

Here another thread regarding one of my plugins. As I see not too many discussions about the FreeCAD plugin so far, I would like to advertise to use only this thread for discussion. This way many users can meet at one place and help themselves or I can give support of course, too. PS: I noticed a bug in the plugin that will merge all bodies of all objects in a CAD file. If someone is interested to test, please let me know. Website: https://thopiekar.eu/cura/cad/freecad/ Installation guide: https://thopiekar.eu/cura/plugins/installation/

This should work now. Just update to Cura 3.7.0 or 4.0.0 and update the plugin.

No problem 🙂 Grad to hear that it works!

Any chance to get ticket voucher still(, too)? Would like to inform myself more about the most recent technologies in manufacturing! 🙂 PS: For 2019 of course 😇

No problem. By the way, since I often don't have the time to check the forum for issue reports of the plugins I maintain, please write me either a mail or check the main thread you can find via search function. Thanks!

Is it possible to share the project file and the gcode with us? Is there an error message shown on the display? Thanks!

@imonsei Hmm, that sounds strange. Could be the case that you need to use a registry cleanup tool. When programming the plugin I had to write algorithms to look for installations in at least 3 locations. With Windows 10 (or slightly earlier) there is even a new place for file assignments (1 of those three mentioned before). So after changing the assignment it works now? Does the model show up? --- Another topic.. MACOS USERS: I need testers for my current macOS support. That also includes FreeCAD and OpenSCAD, but would need to prepare the plugin packages first. Therefore doing it by request. https://thopiekar.eu:5443/cura-cad-integration/CuraBlenderPlugin/-/jobs/935/artifacts/browse The principle is the same as on Windows: The plugin within Cura will determine the path of application your file (here .blend) is assigned to. As you can see above it works with my test file, even without 3D acceleration in my virtual machine. By the way, Blender doesn't run within this VM, because of the missing 3D acceleration, but the plugin works, because it is running Blender "headless". Short instructions for Cura 4.0.0 users: Download the .curapackage file from the link above and drag+drop it into Cura. Finally, restart the application. In any case, please give feedback otherwise I'm NOT going to publish any of this progress via Cura Marketplace. Thanks! ---

The latest stable version. If I'm not wrong the betas are distributed in zip files, right? How is your beta installed? Please make sure that all blender files are assigned to the executable within your unpacked files. The plugin inside Cura looks which file is assigned to .blend files and runs a command using this installation. Please keep me posted about your problem. Would like to understand how it comes 😉

Hmm, still empty on my side 😕

Hello @imonsei, thank you for contacting me here 😃 I looked into your files and when opening "hook_bathroom.blend" I can also find no model inside. Or am I missing something? 🙄 Thanks! 🙂

Just reserving this thread for questions between plugin users here. Additionally, feel free to add ideas for improvements, which are important for you as issues to the project page. Looking forward to stimulating and inspiring ideas! Thanks! Website: https://thopiekar.eu/cura/cad/blender/

Oh, ok. Didn't know that there are restrictions on this. Question is always how often multi-beta release occur and how often it will happen in the future. Guess it's a special case at the moment, because a lot of things are changing from 3.x to 4.x. Never mind 🙂 It is not like it burned a lot of time 😉

Would be great if you could call it "Cura 4.0 (beta2)". Checked your website for a new version about every 1-2 weeks and only got known of a new version by newly reported bugs on Github. Additionally, on the "View all versions" page it still mentions "Release date: Dec 18, 2018". That's not correct.

Hast du das Model noch da? Hab heute etwas Zeit damit verbracht eine automatische Korrektur einzubringen. Es gibt eine Funktion in Blender die die Normalen korregieren soll. Habe dies in mein Plugin eingebettet und würde es gern mit deinem Model testen.

Langsam frage ich mich ersthaft, ob blender es einfach nicht drauf hat in STL zu exportieren. Ich kenne das Problem selbst von der Arbeit am Blender plugin und Feedback anderer Leute dazu. Ob manuell in der Anwendung oder via Skript bekommt man oft Salat raus.