-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Print does not start when print=true if file is upload using API (Slic3r) #5
Comments
Came here to report same issue. If I send a job to Octoprint with Slic3r (Prusa Edition 1.41.2) it uploads correctly but the print does not start automatically even if I select the "Start printing after upload" option in slic3r. It is possible to fix this behaviour in AutoSelect? |
I'm seeing the same thing when uploading GCODE from Simplify3D, i.e. the print isn't started. It doesn't seem to actually start a print :-( I'm happy to provide any info needed to fix this issue. Are there any conditions under which this does work? |
I uploaded from cura, but this does not seem to be working, might be the same? |
Wanted to report the same issue when uploaded using curl via Simplify3D. See the following link it if provides any context. Would be great for it to either FILTER all other prints except the one uploaded or auto select it. https://all3dp.com/2/simplify3d-octoprint-how-to-make-them-work-together/ |
@foosel do you think the problem lies with this plugin, or in OctoPrint itself by ignoring the API instruction to start the print? |
Could be a race condition maybe? |
Slic3r has the hability to upload files to OctoPrint server:
and to mark it to start printing automatically after upload it, but when Autoselect plugin is enabled, print doesn't start, but the file is only selected.
The text was updated successfully, but these errors were encountered: