-
Notifications
You must be signed in to change notification settings - Fork 24
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
Communication timeout after N38/N39 with Octoprint 1.4.0 and DisplayLayerProgress version 1.18.1 #128
Comments
Hi @Kelly12612, which Python-Version do you use? |
This was an upgrade, so it appears to still be running the older python: |
Hi @Kelly12612 Because it is just an assumption, please test and give me a feedback. Thx, in advance |
The problem is still happening for me with the new release. I've attached a smaller gcode file that reproduces the problem. If I try to copy this to the SD card through Octoprint with this plugin enabled, it gets partway through then I get a communications error/reset (failed 3 times in a row). |
I tested it and updated the ticket (still a problem), but forgot to respond
to this email until now.
-Kelly
…On Wed, Apr 8, 2020 at 3:11 PM OllisGit ***@***.***> wrote:
Hi @Kelly12612 <https://github.com/Kelly12612>
in the newest release 1.19.0 I changed the behaviour (switching to async)
of processing the gcode during print. I think this was your issue, because
the gcode was not send fast enough to the printer.
Because it is just an assumption, please test and give me a feedback.
Thx, in advance
Olli
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#128 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AI5NADMGNPFYDHOS6HYZWVLRLTK7VANCNFSM4LUJCHSQ>
.
|
To be honest, currently I have no idea how to analyse this....but I want to mention one point: local vs sd card-upload Local |
One idea: I looked into your Serial log again and some printers had issues with "special-characters" for the M117 display command.
and
Maybe the printer can't handle |
No problem with those commands.
-Kelly
…On Sat, Apr 18, 2020 at 10:02 AM OllisGit ***@***.***> wrote:
One idea: I looked into your Serial log again and some printers had issues
with "special-characters" for the M117 display command.
Try to send the following commands to your printer via terminal to
reproduce the error.
M117 INDICATOR-Layer1
and
G92 E0.0
Maybe the printer can't handle - and the next command could not be
send.....just an idea!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#128 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AI5NADJFQFQO5EHRQOZ3HOLRNG6J3ANCNFSM4LUJCHSQ>
.
|
Hi @Kelly12612, last idea: Try latest development version https://github.com/OllisGit/OctoPrint-DisplayLayerProgress/releases/download/1.20.1dev/master.zip This version use queing-hook and is not interfering the communication between OP and Printer. |
How to update to 1.20.1dev from octoprint? |
Still no joy, I'm afraid, failed while copying to SD, log below, version
displayed in plugin manager
was: DisplayLayerProgress Plugin (1.20.1.dev0)
Send: N39 G92 E0.0*99Recv: okSend: N40 G1 E-0.80000
F2100.00000*9Communication timeout while printing, trying to trigger
response from printer. Configure long running commands or increase
communication timeout if that happens regularly on specific commands
or long moves.Send: N41 M105*18Communication timeout while printing,
trying to trigger response from printer. Configure long running
commands or increase communication timeout if that happens regularly
on specific commands or long moves.Send: N42 M105*17Communication
timeout while printing, trying to trigger response from printer.
Configure long running commands or increase communication timeout if
that happens regularly on specific commands or long moves.Send: N43
M105*16Communication timeout while printing, trying to trigger
response from printer. Configure long running commands or increase
communication timeout if that happens regularly on specific commands
or long moves.Send: N44 M105*23Communication timeout while printing,
trying to trigger response from printer. Configure long running
commands or increase communication timeout if that happens regularly
on specific commands or long moves.Send: N45 M105*22No response from
printer after 6 consecutive communication timeouts, considering it
dead. Configure long running commands or increase communication
timeout if that happens regularly on specific commands or long
moves.Changing monitoring state from "Sending file to SD" to "Offline
(Error: Too many consecutive timeouts, printer still connected and
alive?)"Connection closed, closing down monitor
…On Fri, Apr 24, 2020 at 8:53 AM OllisGit ***@***.***> wrote:
Hi @Kelly12612 <https://github.com/Kelly12612>,
last idea: Try latest development version
https://github.com/OllisGit/OctoPrint-DisplayLayerProgress/releases/download/1.20.1dev/master.zip
This version use queing-hook and is not interfering the communication
between OP and Printer.
The values in the display are now a little bit behind.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#128 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AI5NADNWEFV5FKW44G6WUATROGKV5ANCNFSM4LUJCHSQ>
.
|
@Minglarn use the plugin-manager http://docs.octoprint.org/en/master/bundledplugins/pluginmanager.html and enter the above master.zip-url into "from URL" and press install. |
Hi @Kelly12612 , hmm..short Summary: Two problems
Lets focus on issue 1)
|
Sorry, I guess I wasn't clear, all the logs I've uploaded have been about
the upload issue.
Yes, I drag the file to the right side of the octoprint web page.
I've uploaded to the ticket, a zip file that has logs from uploading the
same file, with and without DisplayLayerPlugin.
-Kelly
…On Sat, Apr 25, 2020 at 3:18 PM OllisGit ***@***.***> wrote:
Hi @Kelly12612 <https://github.com/Kelly12612> ,
hmm..short Summary: Two problems
1. Upload to printers SD-Card is not possible, if plugin enabled
2. Sending gcode during print from OP-RasPI-FlashCard throws
communication-error.
Lets focus on issue 1)
- You upload the gcode via Browser-UI und choose SD-Card (Drag&Drop
right-side), right?
- What error do you receive if upload failed? Please attach the
OctoPrint-Log.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#128 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AI5NADLHLI77UFDDHTZTN4TRONATBANCNFSM4LUJCHSQ>
.
|
Short status update:
Do me a favour and test uploading files with disabled "exclude-plugin". Thx, in advance |
This issue has been automatically marked for closing, because it has not had activity in 30 days. It will be closed if no further activity occurs in 10 days. |
My printer is a Prusa MK3s firmware 3.8.1-2869 with MMU2s firmware 1.0.6-372.
After upgrading to octoprint 1.4.0, my first two prints aborted with a communication error.
I did some testing and found that the same thing happened if I just uploaded a gcode file to the SD card.
I did a lot more testing and found that the problem only occurs if the DisplayLayerPlugin is enabled, if I disable that, everything works, even with all my other plugins enabled.
It happens with gcode files from PrusaSlicer versions 2.1.1 and 2.2.0 (ga).
I've attached a terminal log from a failed send, and the octoprint.log file from a failed send.
The problem always seems to occur after an N38 or N39 command, one example is:
Recv: ok
Send: N39 G92 E0.0*99
Communication timeout while printing, trying to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
Let me know if there is any other information you'd like, it's pretty easy to reproduce.
terminal_log_march_26_0940.txt
octoprint.log
The text was updated successfully, but these errors were encountered: