thopiekar

One difference should be quickly visible. The SolidWorks plugin was benefiting for a long time of a self-test, which ensured that SolidWorks is correctly installed. This one I extracted, cleaned up and moved into a common application library, called "CadIntegrationUtils" (short: CIU). That one consisted of no user-interface for a very long time. Since the library seemed to work fine for a long time, I decided to give it and all the other plugins a face. Long story short: The self-test was one of two tabs in the preferences dialog. Now you can find the self-test at: All you can find exactly the same menu entry at all the other Windows automation based plugins, too. These include the SolidWorks plugin, Autodesk Inventor and shortly the CATIA plugin. That's why the checks based on this technology are often just the same and therefore all the plugins can benefit from that. So if you can find this entry in the plugins menu, then you managed to install the plugin successfully. If you are noticing any issues as before, - well - then even better! 😃 Thank you for taking the time! PS: As soon as I get the CATIA plugin reviewed, I'll roll out updates for all the other plugins, too. Don't want to postpone it for much longer. Want to keep it in the release face of Cura. (As long as there are no issues of course.)

A new plugin is joining the plugin family! The CATIA plugin comes basically with the features you know from the others (if you had a chance to use them before).[1] The plugin can be easily downloaded and installed on my website. You can find a very basic checklist of what needs to be done here: https://thopiekar.eu/cura/cad/catia/ Enjoy and happy designing! -------------------------------------------- [1] https://thopiekar.eu:5443/cura-cad-integration/CuraCatiaPlugin/commit/9413a9961f0782a152b9bd878adcb23ade342cbb --------------------------------------------

Could someone give this build a try? https://thopiekar.eu:5443/cura-cad-integration/CuraBlenderPlugin/-/jobs/1298 There are no major changes, but I worked on some features for the SolidWorks and Inventor plugin, which could have influenced this plugin, too. Thanks! - Thomas

New testing release: https://thopiekar.eu:5443/cura-cad-integration/CuraFreeCadPlugin/-/jobs/1300/artifacts/browse I just touched some minor things when working on the SolidWorks and Inventor plugin. Would be great if you could give it a try. Thanks!

It is a testing version. So eventually something might not work. As far as I could test it works good enough that I believe it can be tested by the community. 😊 The needed steps are basically described here: https://thopiekar.eu/cura/plugins/installation/#ManualInstall (This section of the instruction is not well formatted I have to admit.) If you face issues and you have too much trouble, simply uninstall the plugin via the marketplace and reinstall it via marketplace again, too. If Cura fails to uninstall the plugin (for whatever reason I don't know) you can find a guide about the manual uninstallation here: https://thopiekar.eu/cura/plugins/uninstallation/ Finally, the plugin I'm offering for testing will use default settings. Because I use a new "namespace" in the preference storage in Cura. So if you like to do a migration you need to rename "cura_solidworks" into "CuraSolidWorksPlugin" in the cura.cfg. But I would only recommend advanced users to touch that file. If you have any other questions or feedback, like missing steps or confusing explanations in the guides, please let me know! Thank you for your early interest, @XYZDesignPro!

Made many cleanups, fixed minor issues, make some sections of the code stronger against bugs and redesigned the UI a bit. The Autodesk Inventor plugin and this one will share the same functionality of the service checker (previously called Troubleshooter in the configuration window). By sharing the same code across both plugins, I want to minimize the needed time on fixing bugs and make all similar plugins benefit from the same features. Additionally, note the package for Cura 4.1.0 (SDK 6.1.0). Haven't tested the plugin so far with that version since it is beta still. Any testing is highly appreciated! https://thopiekar.eu:5443/cura-cad-integration/CuraSolidWorksPlugin/-/jobs/1258/artifacts/browse Thanks! - Thomas

Dear community, here are some updates! 🙂 I began to clean up a lot of code in the common library called CadIntegrationUtils (CIU). At the moment I've got a test application working for the Inventor plugin, which only was provided with the SolidWorks plugin: Additionally, I added a popup message including a button which brings you to this window, so you can see where your Inventor installation might be broken. Along with these changes, I noticed that the code could be organized much better, so I will keep track of getting it cleaner. Getting this functionality working with the Inventor and SolidWorks plugin at once, will be the next step. Regards! - Thomas Karl Pietrowski PS: Work done: https://thopiekar.eu:5443/cura-cad-integration/CuraInventorPlugin/-/jobs/1278/artifacts/browse

As promised from my side, but nothing new for you here anymore, I got confirmed by a trustable source via mail, that you got heard already and people are trying to fix your problems asap. First of all, before I continue on some statements here, I have to say that I'm pretty much disappointed by the exposure done on the Ultimaker team by some people in this thread. I think the correct place to let someone know of your disappointment is not a public place like this. I could continue investing more of my energy into telling what I think (will do this later), but I want to make it short by saying: This way of blaming the whole company in public next to other community members, hobbyists and end users from the industry, is neither fair nor professional at all! Yes, you can be frustrated and you might be correct in many of your points, but are you really sure that it would have been better with a different manufacturer? Nevertheless, even if you thank the community for their help, blaming on Ultimaker makes me personally feel really bad. I'm really limited in time every day, but reading all the messages here made me getting active on this. Wanted to prevent this situation and wanted to calm you all down, but see that I missed my goal on some people here. Generally, have the opinion that many of you misunderstood the purpose of the forums. Resellers are responsible for local services and satisfaction. The forums are for announcements and a place created by Ultimaker for 3D printing enthusiasts to share their designs, problems and solutions. Yes, it is a place for support, but not too much on industrial level. Before something gets considered as a solution by Ultimaker it must be tested before (which should correspond with your industrial thinking, because a bad solution is like having no solution). Additionally, backward compatibility is never guaranteed to work since it is never (and probably will never be) tested (logically - since testing and doing downgrades now, would eat valuable time of an engineer to fix the actual problem). As I said before, what counts at the moment, is that a solution will be found soon. I'm sure Ultimaker as a company learned a lesson from that. (I'm allowed the say the following since I'm neither employed by Ultimaker nor making money with neither Ultimaker nor someone else right now.) Please, take some of your time, find a quiet and enjoyable place and think about how you communicate here. I know from my experiences with industrial (incl. automotive) companies that life can be stressing, but that's no excuse to be like this. Getting no answer from someone in time doesn't necessarily mean that someone is lazy and not doing her/his best to come back with a (real!) solution. Everyone who knows me can tell for sure that I could continue at this point and end up in a book. In any case, I'm convinced of Ultimaker products and trust their work! Thanks - Thomas Karl Pietrowski

Have you ever tried to downgrade as described before and tried again. I mean if you can really prove that this is firmware related that would be great. Otherwise, people could say that you just have bad luck and the sensor itself could get broken accidentally during this time too. Well, I remember that there were several tests done together with PVA, so dual printing is definitely included here. But as I said, it's already more than a year ago that I had a foot in the R&D building. But even if I would know something more in detail what went wrong, I wouldn't mention too much (diplomatically). I think what really counts right now, is that your problems get corrected. Thank you for your great summary! I will redirect this one, if I hear something from the UM side. I agree. Also it depends on what is currently in the planning of the different individuals (companies and hobbyists). Might be that they already have a good calibration and didn't switch the cores. Anyway, more people will notice these issues soon for sure. Think that makes it more important to prevent that these people will ever know of these bugs, so they won't get disappointed, too. Will keep you posted as soon as I know something new.

No problem! 😉

Ein Sunon Lüfter war wohl auch zuvor verbaut oder? Ist das nicht vielleicht ein üblicher 80x80 lüfter? Von denen findet man einige bei ebay, aber bei 75x75 sieht es sogar über ebay hinaus sehr mager aus. Denke nicht, dass es sich Ultimaker in den frühen Jahren leisten konnte einen Lüfter nach eigenem Maß anfertigen zu lassen 😉

Found the bug. Made the changes on the script with FreeCAD 0.18, but some functions are not backwards compatible to 0.17. Made it working for both now.

Have you tried the same test cube with the printers original software? If this print works, I would suggest comparing the G-code of both slicers. Maybe you can trace back from where wrong parameters come from. 😉

Could someone with an Apple laptop do me a favour and test the unreleased plugin above? Thanks!

Sent an email to some people. Will keep you posted about any feedback I get. I'm convinced that Ultimaker will give answers soon! Until then, I'm crossing fingers for you all! Even if this solution is not the most user-friendly one, I think it might be the only promising one for now. Thank you @mikkermik for sharing this document!

I'll drop this do some of my former co-workers. I don't believe that Ultimaker is not aware of that. Additionally, it could take some time until the fixes are fully tested. They have a great QA team, which takes the job seriously. Personally, I have no explanation of how it could come to this situation since Ultimaker is taking quality very serious (saw it myself) and (normally) communicates very well. But I can also understand you guys here that a minimum of communication must be given - doesn't matter what the situation is internally. Hope that a solution will be found for you soon!

Haha. Enjoyed exactly this at Ultimaker, too. Was a great time! 😊

Yes, would save them in the settings storage and recover them on each load of a file. Within a settings window in the menu, they could get changed or reset. Think that might be something interesting for all commandline-based plugins (Blender and OpenSCAD), too.

Haha, no problem. I think I need to think about adding a window for overwriting the path to the executable and overwriting the executable name 😅

Could be. I'm using the stable PPA. Does an "freecadcmd-daily" exist, too? The plugin is using the freecadcmd command line application to do the conversion from FCstd to STL automatically. If another name is used, then it won't be recognized.

@UbuntuBirdy Personally, I prefer the second answer (modifying .bashrc): https://askubuntu.com/questions/60218/how-to-add-a-directory-to-the-path PS: The new version is on its way:

From my intern days at Ultimaker, I know that the general material properties must be there if I don't remember wrong what I saw in the firmware. I have no explanation of why the wrong temperature is applied during this procedure. I feel sorry to hear this ☹️

Well, if it is not too difficult for you, then add the binary directory of your installation to the $PATH environment variable. Or (as I do) upgrade FreeCAD using the FreeCAD PPA. Currently, they deliver version 0.18.0 in it.

Hmm, so there could be two ways of importing something into Cura, right? Once by using an active object, as I do now, or by looking for visible bodies. I guess the method with the visible bodies could get interesting when printing with multiple extruders.

I guess, you are using Linux, right? PS: The bug fix works for you?