Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Spontaneous start of SD print when browsing Ultimaker 2 file list via printer rotary button #1407
What were you doing?
When using an Ultimaker 2 and going into
This is recognized and updates the "File" that is selected within the Octoprint UI. So far, this is what can be expected.
What did you expect to happen?
I expect the OctoPrint + printer combination only to start printing when button is pressed, not when scrolling through a menu.
What happened instead?
While starting to scroll through the menu I experience a sudden start even without pressing the button on the printer nor pressing Print within Octoprint. The serial conversation continues like this:
Branch & Commit or Version of OctoPrint
Version: 1.2.9 (master branch)
Printer model & used firmware incl. version
Ultimaker 2+ with firmware 2.1 of May 11 2016 13:14:07.
Browser and Version of Browser, Operating System running Browser
Chrome 51.0.2704.103 (64-bit) on OS X.
Link to octoprint.log
Around the event, nothing new happens.
Link to contents of terminal tab or serial.log
Relevant bits show above. If needed I'd happily provide more.
No JS errors
I'm using Octoprint with the API, but to be sure nothing external is starting the job, I disable the API access under settings. I don't see data from my client accessing Octoprint anymore as soon as I do this and the print still starts suddenly (at byte 0 and without the startup sequence that the Ultimaker 2 normally starts an SD card print with (UltiGcode)).
It looks like there is some information missing from your bug report that will be needed in order to solve the problem. Please take a look at the Contribution Guidelines which will provide you with a template to fill out here so that your bug report is ready to be investigated (I promise I'll go away then too!).
If you did not intend to report a bug, please take special note of the title format to use as described in the Contribution Guidelines.
I'm marking this one now as needing some more information. Please understand that if you do not provide that information within the next two weeks (until 2016-07-25 16:40) I'll close this ticket so it doesn't clutter the bug tracker. This is nothing personal, so please just be considerate and help the maintainers solve this problem quickly by following the guidelines linked above. Remember, the less time the devs have to spend running after information on tickets, the more time they have to actually solve problems and add awesome new features. Thank you!
PS: I'm just an automated script, not a human being, so don't expect any replies from me :) Your ticket is read by humans too, I'm just not one of them.
Hi @foosel, we updated to 1.2.13 yesterday and we saw the same issue. This was the output we got:
I don't see the
Also please provide the list of installed plugins (it might be a plugin that is starting the print once a file gets selected, hence I'm asking for that - it's all listed in
IF you set the
A first solution is pushed into the
To reproduce I first sent an upload request to the server, making sure to have
Can you test this against your setup?
Hi @foosel. Finally I can spend some more time on tracking down this issue.
I cherry picked the fix (2cc9631) on master (1.2.13) and could still reproduce the problem. I did the following:
I'm using an OctoPi image.
Later, I did the following to really switch to
My fear is that I'm still running on
This is a more complete serial log:
My octoprint.log is found here: http://pastebin.info/?paste=5
I'll try to run more tests today if you can tell me what to try.
Hi @ErikDeBruijn, from the log it indeed looks like you are still running regular
Btw, the list of plugins can also be found in the log (which is one of the reasons I ask for it in every ticket):
After checking out
If you are running a manual install which followed the official installation instructions:
and restart OctoPrint's process. Also note that you might have to adjust
When you start up, OctoPrint should print
to the log. Or
if you cherry picked. If it still says
@ErikDeBruijn @foosel I am using Ultimaker 2+ with Octopi 0.15.1. When I connect my printer to the octoprint, insert my sd card, and start the file nagivation by rotatory wheel, the print automatically starts without me pressing the button.
This is my Log
No, it's not, not even remotely, since what's happening here can only happen since 1.3.7 ;)
It's OctoPrint thinking you started a print since your printer reported that you selected a file for printing. OctoPrint doesn't do anything on its own here, it basically "leaves the field" for your printer controller since you are using that to select files and most likely also print it. Note how it says "SD printing byte 0/7041501" there - the file isn't actually printing yet.
The problem is that there's no way to know when the printer actually starts printing the file (at least on most firmwares) so all OctoPrint can do is rely on "file got selected" messages. I'll take a look though if I can only switch to printing state once the byte position starts increasing. Most likely won't make it into 1.3.9 though.
@foosel Thank you for the quick reply. Two things....
Will really appreciate any kind of help in this regard.
Not if every single use of the rotary wheel on your printer immediately selects the file and has the printer produce a corresponding message on the serial interface (which btw kinda surprises me and certainly doesn't match the behaviour I've seen from other printers).
I have something prepped on
I was using OctoPrint to monitor my Ultimaker 2+ some time ago and due to memory card failure, I stopped for a few months. Now, finally I got time to fix the issue and I have a very similar problem as @massvoice . When I want to print from the SD card, I enter 'Print' menu and then it kind of automatically is starting to print some file with info on the printers display 'Printing from USB' or sth like that (I don't remember a right now exact message, but can get it tomorrow).
Any suggestions on how I could track down what is causing this behaviour?