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.
Save to removable saves on HDD anyway... Cura 5.1 and 5.2
Posted
(edited)
· Save to removable saves on HDD anyway... Cura 5.1 and 5.2
Hello again!
I use Windows 11 x64. Yes, my operating system is not English language. Yes, SD card worked before. This happened during one session with the program. I don't remember exactly how it happened, but something like: I saved gcode to the SD card - OK. A moment of work, I saved the gcode, this time to disk - OK. Another moment of work and saving again on the SD card, but... This time, gcode was written to the computer, same drive I was saving to before. And it's always been like that ever since. No, I have no more devices in the card reader, if that's what you mean.
I think it might be caused by one of the plugins. I have to check it out. I use "custom printjob naming".
Edit:
I'm back home and checked. Thank you MariMakes!
Your questions led me to the idea of checking plugins. And that was indeed the reason. No idea how, but one setting of plugin "printjob naming" was set to save to path D:/. This plugin catches saving process and replacing the name. And the path in this case. Now all works as before.
Edited by nepcior New information
2
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!
In the Cura 5.8 stable release, everyone can now tune their Z seams to look better than ever. Method series users get access to new material profiles, and the base Method model now has a printer profile, meaning the whole Method series is now supported in Cura!
We are happy to announce the next evolution in the UltiMaker 3D printer lineup: the UltiMaker Factor 4 industrial-grade 3D printer, designed to take manufacturing to new levels of efficiency and reliability. Factor 4 is an end-to-end 3D printing solution for light industrial applications
Recommended Posts
GregValiant 1,357
Hello @nepcior.
@MariMakes should be able to help with this when she gets a moment. She will need to know more about your computer and operating system.
Cura makes calls to the operating system to handle file writes so maybe something is going on between them.
Is the "lock tab" on the memory card in the "write" position?
Link to post
Share on other sites
MariMakes 203
Hey @nepcior,
Welcome to the Ultimaker Community 🎉
That's odd. 🤔 It reminds me of this github issue but it seems different.
I have a bunch of questions!
Which operating system are you running?
Is your operating system in a non English language?
Did this SD card work before?
Do you have more devices plugged in?
Link to post
Share on other sites
nepcior 2
Hello again!
I use Windows 11 x64. Yes, my operating system is not English language. Yes, SD card worked before. This happened during one session with the program. I don't remember exactly how it happened, but something like: I saved gcode to the SD card - OK. A moment of work, I saved the gcode, this time to disk - OK. Another moment of work and saving again on the SD card, but... This time, gcode was written to the computer, same drive I was saving to before. And it's always been like that ever since. No, I have no more devices in the card reader, if that's what you mean.
I think it might be caused by one of the plugins. I have to check it out. I use "custom printjob naming".
Edit:
I'm back home and checked. Thank you MariMakes!
Your questions led me to the idea of checking plugins. And that was indeed the reason. No idea how, but one setting of plugin "printjob naming" was set to save to path D:/. This plugin catches saving process and replacing the name. And the path in this case. Now all works as before.
New information
Link to post
Share on other sites