Octoprint keeps disconeccting.
Whenever I start a print, whether I start it from Octoprint, or from the SD card on the printer the Raspberry Pi Zero with get disconnected from the Prusa (Connected through the Rambo board directly) with an error message about too many timeouts, is the printer still awake(or something like that). And then I can reconnect it if I like, but it doesn't do any good at that point lol.
This is making me rather sad as I really would like to use it to both capture time lapses, and to monitor and print with.
Here is the output I get from the seriallog file:
(I am leaving out all the good messages, and starting with a small section of goo recv messages just before it goes bad.)
2018-05-24 08:19:16,033 - Recv: T:238.75 E:0 B:80.0
2018-05-24 08:19:17,307 - Recv: T:238.8 E:0 W:?
2018-05-24 08:19:18,303 - Recv: T:239.2 E:0 W:2
2018-05-24 08:19:19,310 - Recv: T:239.1 E:0 W:1
2018-05-24 08:19:20,305 - Recv: T:239.6 E:0 W:0
2018-05-24 08:19:22,041 - Recv: 0 step=30 mscnt= 481
2018-05-24 08:19:22,058 - Recv: tmc2130_goto_step 0 29 2 1000
2018-05-24 08:19:22,401 - Recv: echo:busy: processing
2018-05-24 08:19:24,546 - Recv: echo:busy: processing
2018-05-24 08:19:26,644 - Recv: echo:busy: processing
2018-05-24 08:19:26,682 - Recv: 0 step= 2 mscnt= 32
2018-05-24 08:19:26,693 - Recv: tmc2130_goto_step 1 1 2 1000
2018-05-24 08:19:28,797 - Recv: echo:busy: processing
2018-05-24 08:19:31,466 - Recv: echo:busy: processing
2018-05-24 08:19:33,565 - Recv: echo:busy: processing
2018-05-24 08:19:35,678 - Recv: echo:busy: processing
2018-05-24 08:19:37,769 - Recv: echo:busy: processing
2018-05-24 08:19:39,958 - Recv: echo:busy: processing
2018-05-24 08:19:42,055 - Recv: echo:busy: processing
2018-05-24 08:19:44,154 - Recv: echo:busy: processing
2018-05-24 08:19:46,301 - Recv: echo:busy: processing
2018-05-24 08:19:48,400 - Recv: echo:busy: processing
2018-05-24 08:19:50,546 - Recv: echo:busy: processing
2018-05-24 08:19:52,641 - Recv: echo:busy: processing
2018-05-24 08:19:54,739 - Recv: echo:busy: processing
2018-05-24 08:19:56,853 - Recv: echo:busy: processing
2018-05-24 08:19:57,693 - Recv: Unknown M code: M900 K45
2018-05-24 08:19:57,712 - Recv: Unknown G code: G21
2018-05-24 08:20:18,795 - No 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.
2018-05-24 08:20:18,876 - Changing monitoring state from "Operational" to "Offline (Error: Too many consecutive timeouts, printer still connected and alive?)"
2018-05-24 08:20:19,022 - Connection closed, closing down monitor
Here are the logs from the regular logfile during the same time period:
2018-05-24 08:14:31,688 - octoprint.util.comm - INFO - Communication timeout while idle, trying to trigger response from printer.
2018-05-24 08:16:01,960 - octoprint.util.comm - INFO - Communication timeout while idle, trying to trigger response from printer.
2018-05-24 08:16:03,963 - octoprint.util.comm - INFO - Changing monitoring state from "Operational" to "Printing from SD"
2018-05-24 08:16:04,977 - octoprint.util.comm - INFO - Externally triggered heatup detected
2018-05-24 08:16:05,722 - octoprint.util.comm - INFO - Changing monitoring state from "Printing from SD" to "Cancelling"
2018-05-24 08:16:05,876 - octoprint.plugins.astroprint - WARNING - Error executing GCode Analyzer
2018-05-24 08:16:05,879 - octoprint.plugins.astroprint - ERROR - Fail to analyze Gcode: prusa_~2.gco
2018-05-24 08:17:34,876 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2018-05-24 08:18:21,703 - octoprint.util.comm - INFO - Changing monitoring state from "Cancelling" to "Operational"
2018-05-24 08:19:35,026 - tornado.access - WARNING - 404 GET /plugin/octopi_support/static/img/icon-sd-black-14.png (127.0.0.1) 31.62ms
2018-05-24 08:19:35,068 - tornado.access - WARNING - 404 GET /plugin/octopi_support/static/img/graph-background.png (127.0.0.1) 28.42ms
2018-05-24 08:19:37,563 - octoprint.server.util.sockjs - INFO - New connection from client: ::ffff:192.168.0.51
2018-05-24 08:20:03,731 - octoprint.util.comm - INFO - Timeout while in an active heatup, considering heatup to be over.
2018-05-24 08:20:18,791 - octoprint.util.comm - INFO - No response from printer after 6 consecutive communication timeouts, considering it dead.
2018-05-24 08:20:18,887 - octoprint.util.comm - INFO - Changing monitoring state from "Operational" to "Offline (Error: Too many consecutive timeouts, printer still connected and alive?)"
2018-05-24 08:20:33,825 - octoprint.server.util.sockjs - INFO - Client connection closed: ::ffff:192.168.0.51
Re: Octoprint keeps disconeccting.
Known issue in 3.2.1 (not sure if it was in 3.2.0). There is a fix in GitHub that will appear in next release. I use OctoPrint for steaming now while it stays disconnected from printer. I can monitor while away at least.
Re: Octoprint keeps disconeccting.
I am using whatever firmware comes on a Rambo I think it is 3.1.4 or something like that.
Here is what happens when I try to kick off a print from the Octoprint:
Recv: ok T:27.5 /0.0 B:27.1 /0.0 T0:27.5 /0.0 @:0 B@:0 P:30.5 A:34.8Send: M105Recv: ok T:27.5 /0.0 B:27.1 /0.0 T0:27.5 /0.0 @:0 B@:0 P:30.4 A:34.8Send: M105Recv: ok T:27.4 /0.0 B:27.1 /0.0 T0:27.4 /0.0 @:0 B@:0 P:30.4 A:34.8Send: M105Recv: ok T:27.5 /0.0 B:27.2 /0.0 T0:27.5 /0.0 @:0 B@:0 P:30.4 A:34.8Send: M105Recv: ok T:27.4 /0.0 B:27.3 /0.0 T0:27.4 /0.0 @:0 B@:0 P:30.4 A:34.8Send: M105Recv: ok T:27.5 /0.0 B:27.0 /0.0 T0:27.5 /0.0 @:0 B@:0 P:30.5 A:34.8Send: M105Recv: ok T:27.3 /0.0 B:27.0 /0.0 T0:27.3 /0.0 @:0 B@:0 P:30.5 A:34.7Send: M105Recv: ok T:27.4 /0.0 B:27.0 /0.0 T0:27.4 /0.0 @:0 B@:0 P:30.5 A:34.9Send: M105Recv: ok T:27.5 /0.0 B:27.2 /0.0 T0:27.5 /0.0 @:0 B@:0 P:30.5 A:34.8Send: M105Recv: ok T:27.4 /0.0 B:27.2 /0.0 T0:27.4 /0.0 @:0 B@:0 P:30.5 A:34.8Send: M105Recv: ok T:27.4 /0.0 B:27.1 /0.0 T0:27.4 /0.0 @:0 B@:0 P:30.6 A:34.9Send: M105Recv: ok T:27.5 /0.0 B:27.2 /0.0 T0:27.5 /0.0 @:0 B@:0 P:30.4 A:34.9Send: M105Recv: ok T:27.5 /0.0 B:27.2 /0.0 T0:27.5 /0.0 @:0 B@:0 P:30.4 A:34.7Changing monitoring state from "Operational" to "Printing"Send: N0 M110 N0*125Recv: okSend: N1 M115 U3.1.1-RC5*104Recv: okSend: N2 M201 X1000 Y1000 Z200 E5000*11Recv: okSend: N3 M203 X200 Y200 Z12 E120*15Recv: okSend: N4 M204 S1250 T1250*38Recv: okSend: N5 M205 X10 Y10 Z0.4 E2.5*60Recv: okSend: N6 M205 S0 T0*37Recv: okSend: N7 M83*31Recv: okSend: N8 M104 S[first_layer_temperature]*46Recv: okSend: N9 M140 S[first_layer_bed_temperature]*19Recv: okSend: N10 M190 S[first_layer_bed_temperature]*38Recv: okSend: N11 M109 S[first_layer_temperature]*27Recv: T:27.3 E:0 W:?Recv: T:27.4 E:0 W:?Recv: T:27.3 E:0 W:?Recv: T:27.4 E:0 W:?Recv: T:27.3 E:0 W:?Recv: T:27.3 E:0 W:?Recv: T:27.4 E:0 W:?Recv: T:27.4 E:0 W:?Recv: T:27.3 E:0 W:?Recv: T:27.5 E:0 W:?Recv: T:27.4 E:0 W:?Recv: T:27.4 E:0 W:?Recv: T:27.4 E:0 W:?Recv: T:27.4 E:0 W:?Recv: T:27.5 E:0 W:?Recv: T:27.5 E:0 W:?Recv: T:27.4 E:0 W:?Recv: T:27.3 E:0 W:?Recv: T:27.5 E:0 W:?Recv: T:27.4 E:0 W:?Recv: T:27.5 E:0 W:?
It basically does nothing. Says it is sending temperatures, but it isn't doing anything. The LCD on the printer says it is heating, but then the printer doesn't do anything 🙁
Re: Octoprint keeps disconeccting.
And when I hit cancel it just gets stuck on the canceling state. It doesn't actually cancel This is so very frustrating.
Re: Octoprint keeps disconeccting.
Well I got it working pretty consistently now.
I just changed to a higher quality (More expensive) SD card, and rebuilt the image. Now it seems to be working fine. Weird.
RE: Octoprint keeps disconeccting.
@jeffrey-s7
This will MAKE YOUR DAY! But it'll also piss you off you spent so many hours trying to fix it when it was a simple OFF click!