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.
The `.gz` extention indicates that the file is compressed, so that explains the small size.
I have a hunch (supported by a similar thread I found), that it might be a firmware issue (either missed updates or corrupted files), so you could try to update that as well.
If all else fails, for now, a workaround would be to uncompress the `.gcode.gz` file, and try to print that (or save to `.gcode` file, then print from that file)... though this is hardly ideal of course.
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!
Here comes Cura 5.9 and in this stable release we have lots of material and printer profiles for UltiMaker printers, including the newly released Sketch Sprint. Additionally, scarf seams have been introduced alongside even more print settings and improvements. Check out the rest of this article to find out the details on all of that and more
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
rburema 26
The `.gz` extention indicates that the file is compressed, so that explains the small size.
I have a hunch (supported by a similar thread I found), that it might be a firmware issue (either missed updates or corrupted files), so you could try to update that as well.
If all else fails, for now, a workaround would be to uncompress the `.gcode.gz` file, and try to print that (or save to `.gcode` file, then print from that file)... though this is hardly ideal of course.
Link to post
Share on other sites