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.
It depends on how complex you need it to be, in this case you would almost certainly need to make a plugin for Cura to handle the settings. Plugins aren't too hard, they're written in Python (one of the easiest programming languages to learn for someone without much experience) for the part which actually does stuff and the interface is made in QML (which is a bit convoluted, although designing a UI in a plaintext format usually is, but it's something you should be able to pick up just by looking at files for things that are already in Cura and figure out the relationship between the markup and the display). There's an example plugin available on GitHub.
I have no idea how different the gcode for an SLM printer would be, but if it's different enough that you need to edit CuraEngine, then you're in for a lot of pain. CuraEngine is written in C++, which is a much less friendly language than something like Python. There are far fewer built in functions to do things and you have to worry about memory management and stuff like that.
But if your SLM printer gcode can be mathematically/programmatically derived from FDM code then you might be able to get away with making a post-processor script. These are written in Python and can go over the gcode produced by CuraEngine line by line and change it (or just use the code created by CuraEngine as as a base then ditching it entirely and rewriting it its own way). Doing this much with it has a little bit of a learning curve but nowhere near as bad as editing CuraEngine would be (if you have no programming knowledge to start with, it would probably take you at least a few months to be able to try and change CuraEngine and not break it in the process).
I hope this helps.
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
Slashee_the_Cow 274
It depends on how complex you need it to be, in this case you would almost certainly need to make a plugin for Cura to handle the settings. Plugins aren't too hard, they're written in Python (one of the easiest programming languages to learn for someone without much experience) for the part which actually does stuff and the interface is made in QML (which is a bit convoluted, although designing a UI in a plaintext format usually is, but it's something you should be able to pick up just by looking at files for things that are already in Cura and figure out the relationship between the markup and the display). There's an example plugin available on GitHub.
I have no idea how different the gcode for an SLM printer would be, but if it's different enough that you need to edit CuraEngine, then you're in for a lot of pain. CuraEngine is written in C++, which is a much less friendly language than something like Python. There are far fewer built in functions to do things and you have to worry about memory management and stuff like that.
But if your SLM printer gcode can be mathematically/programmatically derived from FDM code then you might be able to get away with making a post-processor script. These are written in Python and can go over the gcode produced by CuraEngine line by line and change it (or just use the code created by CuraEngine as as a base then ditching it entirely and rewriting it its own way). Doing this much with it has a little bit of a learning curve but nowhere near as bad as editing CuraEngine would be (if you have no programming knowledge to start with, it would probably take you at least a few months to be able to try and change CuraEngine and not break it in the process).
I hope this helps.
Link to post
Share on other sites