UltiMaker uses functional, analytical and tracking cookies. Tracking cookies enhance your experience on our website and may also collect your personal data outside of Ultimaker websites. If you agree with the use of tracking cookies, click “I agree, continue browsing”. You can withdraw your consent at any time. If you do not consent with the use of tracking cookies, click “Refuse”. You can find more information about cookies on our Privacy and Cookie Policy page.
I just had the same issue. Because you mentioned about Cura 2.6.2, I was able to find a workaround for my problem. Hope this helps you as well, if you haven't already figured it out.
This happens only for the 'custom printer' profile. If you select any of the existing machines included in the software, you won't get this error. I tried changing the 'machine settings' of my new custom machine, but no luck.
But the custom machines which I had added a long time ago in the previous versions of Cura (which then were automatically migrated to the newer version when I installed one) were still working fine. I was using Cura 3.0, I tried Cura 2.7 but got same error.
Then I downloaded Cura 2.6.2 and it worked fine!
So the workaround is, create your custom machine profile in Cura 2.6.2 and then install the latest version. The new version will automatically import the profiles from 2.6.2 and they work perfectly fine with all the latest features!
But this is just a workaround and I hope the Cura team fixes this issue. Can't keep uninstalling newer version simply to add a machine profile and then install the new version again.
Sid.
1
Link to post
Share on other sites
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Cura 5.7 is here and it brings a handy new workflow improvement when using Thingiverse and Cura together, as well as additional capabilities for Method series printers, and a powerful way of sharing print settings using new printer-agnostic project files! Read on to find out about all of these improvements and more.
S-Line Firmware 8.3.0 was released Nov. 20th on the "Latest" firmware branch.
(Sorry, was out of office when this released)
This update is for...
All UltiMaker S series
New features
Temperature status. During print preparation, the temperatures of the print cores and build plate will be shown on the display. This gives a better indication of the progress and remaining wait time. Save log files in paused state. It is now possible to save the printer's log files to USB if the currently active print job is paused. Previously, the Dump logs to USB option was only enabled if the printer was in idle state. Confirm print removal via Digital Factory. If the printer is connected to the Digital Factory, it is now possible to confirm the removal of a previous print job via the Digital Factory interface. This is useful in situations where the build plate is clear, but the operator forgot to select Confirm removal on the printer’s display. Visit this page for more information about this feature.
Recommended Posts
sidnaique 2
I just had the same issue. Because you mentioned about Cura 2.6.2, I was able to find a workaround for my problem. Hope this helps you as well, if you haven't already figured it out.
This happens only for the 'custom printer' profile. If you select any of the existing machines included in the software, you won't get this error. I tried changing the 'machine settings' of my new custom machine, but no luck.
But the custom machines which I had added a long time ago in the previous versions of Cura (which then were automatically migrated to the newer version when I installed one) were still working fine. I was using Cura 3.0, I tried Cura 2.7 but got same error.
Then I downloaded Cura 2.6.2 and it worked fine!
So the workaround is, create your custom machine profile in Cura 2.6.2 and then install the latest version. The new version will automatically import the profiles from 2.6.2 and they work perfectly fine with all the latest features!
But this is just a workaround and I hope the Cura team fixes this issue. Can't keep uninstalling newer version simply to add a machine profile and then install the new version again.
Sid.
Link to post
Share on other sites