You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
With the recent unpleasaness, I'm trying to remove as much of the Bambu pipeline as possible. So my preferred workflow would be STL -> Orcaslicer -> Sliced .3mf -> Octoprint -> Bambu p1p.
Right now this mostly works if you select the Octo/Klipper as a 3rd party host and poke it into octoprint. However at this point the file (obviously) is on the octoprint server, not the sd card, and for the life of me I can't see how to transfer it over without downloading and reuploading to SD within octoprint. Apparently Orcaslicer hard codes it as a 'local' upload instead of a 'sdcard' upload, and the simple file manager in Octoprint doesn't seem to have a 'upload local file to SD Card' option, just 'upload new file to SD card'. If you print a local file, octoprint tries (apparently) to interpret the local file as gcode and eats itself.
Describe the solution you'd like
When a local file is printed using the Octoprint Bambu plugin, it should first upload the file to the SD card, wait for the upload to finish, and then continue with the print. Alternatively, perhaps it could force all uploads to be treated as uploaded to origin 'sdcard' instead of origin 'local'.
This will probably be changed with the next release of OctoPrint. There are some needed changes in the underlying core to allow this type of workflow and I was already planning on making it work with local files.
Is your feature request related to a problem? Please describe.
With the recent unpleasaness, I'm trying to remove as much of the Bambu pipeline as possible. So my preferred workflow would be STL -> Orcaslicer -> Sliced .3mf -> Octoprint -> Bambu p1p.
Right now this mostly works if you select the Octo/Klipper as a 3rd party host and poke it into octoprint. However at this point the file (obviously) is on the octoprint server, not the sd card, and for the life of me I can't see how to transfer it over without downloading and reuploading to SD within octoprint. Apparently Orcaslicer hard codes it as a 'local' upload instead of a 'sdcard' upload, and the simple file manager in Octoprint doesn't seem to have a 'upload local file to SD Card' option, just 'upload new file to SD card'. If you print a local file, octoprint tries (apparently) to interpret the local file as gcode and eats itself.
Describe the solution you'd like
When a local file is printed using the Octoprint Bambu plugin, it should first upload the file to the SD card, wait for the upload to finish, and then continue with the print. Alternatively, perhaps it could force all uploads to be treated as uploaded to origin 'sdcard' instead of origin 'local'.
Additional context

https://docs.octoprint.org/en/master/api/files.html#upload-file-or-create-folder
The text was updated successfully, but these errors were encountered: