-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Can't control or send file to printer, no live status feedback (but I can connect and see the printer-startup dump) #4059
Comments
Can you send m110 s0 with manual gcode in slic3r?
|
It echoes |
As @lordofhyphens suggested, I enabled serial debug and rebuilt. I connected to the printer, saw the status dump in the log on the right. Tried to home-X, didn't respond. Tried to send M110 S0 followed by G28, no response. Disconnected, closed Slic3r. Here is serial.txt in its entirety:
It seems to be as I suspected - Slic3r disconnects from the printer after receiving the status dump. As you can see, my home-X, M110, and G28 commands do not appear in the log. Pronterface log shows almost exactly the same text after a printer reset, except there is no "N0 M105*39" in the log. For comparison, here's that log, with "debug" enabled:
|
Not sure what changed, but this feature works now (commit 21eb603). |
Version
1.3.0-dev, commit 13f121e
Printer runs Marlin firmware, bugfix-1.1.x branch, commit
ae7c6020
, configured withthese settings
.Operating system type + version
Debian 9 "Stretch"
Behavior
The "Test" function under Printer Settings tells me the connection is okay, and I can indeed connect to the printer inside the Controller tab, after which I am shown the printer's usual status/info dump.
However, none of the Manual Control dialog's functions actually work - there is no reaction of any kind at all from the printer for anything I try.
If I try to jog without homing first, Slic3r will warn me, but trying to home doesn't actually do anything. If I use the "Send manual command" function, it echoes the command I sent, to the log, but again produces no reaction from the printer.
Attempting to print a sliced object adds the print job to the queue, but clicking that queued job's "print" button does nothing.
If I close the Manual control dialog and disconnect from and then re-connect to the printer, I am again shown the printer's status dump. I find this odd, because that doesn't happen in Pronterface - it only shows me the status dump if I reset the printer and then disconnect/reconnect to it. Is Slic3r resetting the printer on connect?
Thing is, this worked recently - at least, the manual jog-by-dragging-the-mouse feature did. I last tried that particular feature (which is really neat, by the way) some time before July 2. I can't tell for sure when it broke; I've tried a few other commits, going back as far as 67d42f9, with no success.
Sometimes, I get live hotend/bed temperature readings to show up, but that's pretty rare, but manual control does not work in any case.
I think Slic3r is failing to keep the connection "alive"/"open", because if I connect with it, and then connect with Pronterface (while Slic3r is still "connected"), neither program shows any errors and I can even manually control the printer with Pronterface at that point.
If I try it the opposite way, that is connecting with Pronterface first, then connecting with Slic3r, I get the sort of behavior I would expect: Pronterface throws a couple of bad line number errors in its log, and Slic3r reports a connection failure.
STL/Config (.ZIP) where problem occurs
Doesn't matter if a model is loaded or not.
Slic3r config: config.ini.zip
The text was updated successfully, but these errors were encountered: