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
1.3.11rc2 disconnect/connect issue #3111
the disconnect is ok, every time I "disable motors" the usb drops, that's a bug in electronic on this printer, normally after that I click connect and it connects...
what happens now with this RC2, it disconnects on M84 (as expected) but is totally ignoring my clicks on the "Connect" button :D ..
only thing that happens when I click "connect" is
and iirc 400 is "bad request" ... so I reload the interface
and click connect again, and now it works
referenced this issue
Apr 5, 2019
It looks like there is some information missing from your bug report that will be needed in order to solve the problem. Read 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 but wanted to request a feature or brain storm about some kind of development, please take special note of the title format to use as described in the Contribution Guidelines.
Please do not abuse the bug tracker as a support forum - that can be found at discourse.octoprint.org. Go there for any kind of issues with network connectivity, webcam functionality, printer detection or any other kind of such support requests or general questions.
Also make sure you are at the right place - this is the bug tracker of the official version of OctoPrint, not the Raspberry Pi image OctoPi nor any unbundled third party OctoPrint plugins or unofficial versions. Make sure too that you have read through the Frequently Asked Questions and searched the existing tickets for your problem - try multiple search terms please.
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 2019-04-19 19:00 UTC) 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.
I don't even need to print anything, just send M84 for usb connection to drop, click Connect and there it is 400 again :(
shift reload - connect now works
but the problem is - it does not happen like this "every time"
Can you please provide
I have one idea what could be happening.
If you have
To test this theory, I'd like you to do the following:
And also test what happens if you trigger the issue and - instead of doing a full UI reload - you only click the little refresh link in the top right corner of the connection pane. My money would be on the connect working then since things should be refreshed properly.
referenced this issue
Apr 11, 2019
sorry for not replying earlier I was AFK for few days... just updated my octoprint with rc3, tried and first test show that issue is fixed. running a print now, should finish in 5 hours and I'll retest it then but initial test show the issue was done.
now, wrt ports ... port do go away and then is back with same name, dunno if that makes sense, but that never got to be a problem before and here we see in the octoprint.log the 400 error from http server .. so no errors in octoprint.log, print finishes normally, and then when I click connect I get that "tornado.access - WARNING - 400 POST /api/connection" error in octoprint log
anyhow if I manage to reproduce it with rc3 I'll get all the snapshot of the js console and log and will try other refresh and .. :D . but so far it looks like it's fixed