That depends, altering the output of the engine on the spot where gcode is generated in the first place isn't possible at the moment via plugins, as the plugin system doesn't cover the engine (yet, and even then, it would probably lack the capability to go 'per layer').
A way to post-process gcode is way easier to add. You don't even have to write a full plugin for that, but 'just' have to add a python script to the already existing (bundled) post-processing plugin. That might get messy in it's own way (especially since a model might've different top-layers) but since we output when layers start, you mostly just want to alter the speeds, it should be possible. It would depend on the precise application how easy that would be.
- 1
Recommended Posts
rburema 26
Not as such no. There are the 'Top Surface Skin ___' settings (which are a bit separate of the `Top/Bottom` settings) but I don't think those affect speed or walls (as opposed to skin).
I suppose what you could do is make a modifier mesh that only intersects the very top layer, and set those settings in the 'modify settings for overlap' side menu, but that can get tedious, especially if the model doesn't have all of its top on the same layer.
If you're just after a better quality finish top-layer though, you could also look into ironing & iron only top layer.
Link to post
Share on other sites
shoe 1
Thanks! I wonder how difficult and powerful the Add-On/Plug-In API of Cura is. Could one easily modify such things via this extension mechanism?
Link to post
Share on other sites