Ok, thanks. This sounds even better. Would you like to share/explain which changes you made to Cura and OctoPrint?
First at all:
I'm not a python-coder, so some things may be not as "clean" as the could be
The changes are tested and work in my configuration / on my systems.
It's only tested on Ubuntu-Linux.
No gurantee that they will work also in other configurations.
In Octoprint are no changes needed, you have just to enable the API and CORS in "System -> API".
The API-Key is needed later on.
The changes in cura are in the "sceneview.py" (download here ) - on Linux to find in /usr/share/cura/Cura/gui/
All changes I made where commented ###.
In this file you have to adjust the following to meet your environment:
around line #143: url
around line #154: X-Api-Key
With this changes you have an additional button near the "YM" button that sends the actual file directly to Octoprint.
Have fun
Bernd
Edited by GuestThanks Bernd.
And don't worry, I am no Python coder either. But I am on a Mac. Let's see if this works.
Recommended Posts
berndjm 16
Hi Nico,
I tried it some month ago. As resume I would say:
- the slicing is not as slow as I thought (but even not very fast )
- the Raspi is not really that power machine for such tasks ...
- you must believe on the slicing profile and have no real control over that whats going on (o.k. you can review the sliced file in gcode viewer ...)
- for me a good workflow looks other
After that I decided to stay on my old workflow slicing with cura on desktop and send the files to octoprint - for that I tweaked the 15.04 cura in a way that I have a "Send to Octoprint" Button near the "Save toolpath". So I mustn't save the file locally and upload it to octoprint, it is send directly (using octoprints API). And as a bonus you can configure Octopint in an way that it starts printing new uploaded files immediatly (if no other print job is ongoing).
For me (so far) the easiset and fastest way ...
Regards Bernd
Link to post
Share on other sites