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.
1. Cura 2.x does not add the name of the printer to the filename (aka "name of the file"). It prefixes a 2-3 letter abbreviation of the Printer Name so that those of us who own more than one 3D Printer can quickly determine which Printer that .gcode was generated for (just in case we save them and reprint them later - I do this a lot). Furthermore most printers don't even display the filename or the printer name when printing. So this is irrelevant.
2. Take a look at the end of the .gcode file. You're a IT Person, you should be able to view it.
You will notice that it contains the Quality Name, Printer Name and any variations of on those settings.
Now, take a look at Manage Profile / Import. In there you will find in the File Type drop-down that '.gcode' files can be imported. This only only restores your object to it location on the print bed, but also all the Meta data associated with it: Printer Name, Profile Name, Deviations of Settings, etc.
Also, note that Cura 2.3 is BETA. As an IT Manager for 35 years to an IT Person as yourself, I'm sure you understand what the term 'Beta' means. So not everything is going to be working 100% with this release. As a result, this particular import function appears to have an issue in importing .gcode files. Which according to the priorities put forth by the Managers and Applications Owners of said software, may or may not get corrected in the next release. Sometimes this does not always correlate with End User's wishes.
I'm a 30 year IT person and one thing I have noticed is that younger developer have lost the ability to empathize with the users of their software.
Wow. I can't even ... I'm at a loss for words...
As for your last statement: I am a user on this planet, and as I stated in #1 above, this can be quite useful.
If you have ideas and opinions, as an IT Manager of 35 years, I have found using a Carrot instead of a Stick gets more accomplished...
Note that in the 2.3 beta, the print job name prefix has been made optional. There were users on the plant that wanted the feature, others did not. We listened.
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!
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
DaHai8 74
1. Cura 2.x does not add the name of the printer to the filename (aka "name of the file"). It prefixes a 2-3 letter abbreviation of the Printer Name so that those of us who own more than one 3D Printer can quickly determine which Printer that .gcode was generated for (just in case we save them and reprint them later - I do this a lot). Furthermore most printers don't even display the filename or the printer name when printing. So this is irrelevant.
2. Take a look at the end of the .gcode file. You're a IT Person, you should be able to view it.
You will notice that it contains the Quality Name, Printer Name and any variations of on those settings.
Now, take a look at Manage Profile / Import. In there you will find in the File Type drop-down that '.gcode' files can be imported. This only only restores your object to it location on the print bed, but also all the Meta data associated with it: Printer Name, Profile Name, Deviations of Settings, etc.
Also, note that Cura 2.3 is BETA. As an IT Manager for 35 years to an IT Person as yourself, I'm sure you understand what the term 'Beta' means. So not everything is going to be working 100% with this release. As a result, this particular import function appears to have an issue in importing .gcode files. Which according to the priorities put forth by the Managers and Applications Owners of said software, may or may not get corrected in the next release. Sometimes this does not always correlate with End User's wishes.
Wow. I can't even ... I'm at a loss for words...
As for your last statement: I am a user on this planet, and as I stated in #1 above, this can be quite useful.
If you have ideas and opinions, as an IT Manager of 35 years, I have found using a Carrot instead of a Stick gets more accomplished...
Link to post
Share on other sites