M600 disconect octoprint

Get Help
1

[M600 disconnect octoprint/ filament runout sensor conected to printer board]

Hi,
When change filament (M600) - the octoprint disconnects.
When I put M702 to terminal (Unload filament) - Octoprint disconnects
When send to printer M701 (load filament), the octoprint is not disconnected and is displayed (Message from your printer Paused)
I added these lines in marlin
#define HOST_ACTION_COMMANDS
#if ENABLED (HOST_ACTION_COMMANDS)

  • #define HOST_PROMPT_SUPPORT*
  • // # define HOST_START_MENU_ITEM // Add a menu item that tells the host to start*
    #endif

I have the FIlament sensor connected to the printer board (SKR E3 mini). When the filament sensor activates, an M600 is sent
Thanks for help

I add log

2021-01-30 08:33:15,873 - octoprint.util.comm - INFO - Changing monitoring state from "Offline" to "Detecting serial connection"
2021-01-30 08:33:15,919 - octoprint.util.comm - INFO - Serial detection: Performing autodetection with 2 port/baudrate candidates: /dev/ttyACM0@115200, /dev/ttyS0@115200
2021-01-30 08:33:15,920 - octoprint.util.comm - INFO - Serial detection: Trying port /dev/ttyACM0, baudrate 115200
2021-01-30 08:33:15,921 - octoprint.util.comm - INFO - Connecting to port /dev/ttyACM0, baudrate 115200
2021-01-30 08:33:15,928 - octoprint.util.comm - INFO - Serial detection: Handshake attempt #1 with timeout 2.0s
2021-01-30 08:33:15,934 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2021-01-30 08:33:15,959 - octoprint.util.comm - INFO - Changing monitoring state from "Detecting serial connection" to "Operational"
2021-01-30 08:33:15,971 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2021-01-30 08:33:16,187 - octoprint.util.comm - INFO - Printer reports firmware name "Marlin bugfix-2.0.x (Jan 27 2021"
2021-01-30 08:33:16,260 - octoprint.util.comm - INFO - Firmware states that it supports temperature autoreporting
2021-01-30 08:33:16,295 - octoprint.util.comm - INFO - Firmware states that it supports emergency GCODEs to be sent without waiting for an acknowledgement first
2021-01-30 08:33:16,535 - octoprint.plugins.tracking - INFO - Sent tracking event printer_connected, payload: {'firmware_name': 'Marlin bugfix-2.0.x (Jan 27 2021', 'printer_port': 'AUTO', 'printer_baudrate': 115200}
2021-01-30 08:35:20,182 - octoprint.util.comm - INFO - Force-sending M600 to the printer
2021-01-30 08:35:22,194 - octoprint.util.comm - INFO - Printer seems to support the busy protocol, will adjust timeouts and set busy interval accordingly
2021-01-30 08:35:22,209 - octoprint.util.comm - INFO - Telling the printer to set the busy interval to our "communicationBusy" timeout - 1s = 2s
2021-01-30 08:35:45,493 - octoprint.util.comm - INFO - Communication timeout while idle, trying to trigger response from printer.
2021-01-30 08:35:48,503 - octoprint.util.comm - INFO - Communication timeout while idle, trying to trigger response from printer.
2021-01-30 08:35:51,508 - octoprint.util.comm - INFO - No response from printer after 3 consecutive communication timeouts, considering it dead.
2021-01-30 08:35:51,553 - octoprint.util.comm - INFO - Changing monitoring state from "Operational" to "Offline (Error: Too many consecutive timeouts, printer still connected and alive?)"
2021-01-30 08:35:51,604 - octoprint.plugins.action_command_notification - INFO - Notifications cleared
2021-01-30 08:35:51,820 - octoprint.plugins.tracking - INFO - Sent tracking event commerror_timeout, payload: {'commerror_text': 'Too many consecutive timeouts, printer still connected and alive?'}

2021-01-30 08:36:04,672 - octoprint.plugins.psucontrol - INFO - Switching PSU Off
2021-01-30 08:36:04,682 - octoprint.plugins.action_command_notification - INFO - Notifications cleared

2021-01-30 08:36:43,634 - octoprint.plugins.psucontrol - INFO - Switching PSU On

2021-01-30 08:38:16,865 - octoprint.plugins.tracking - INFO - Sent tracking event ping, payload: {'octoprint_uptime': 46815}

2021-01-30 08:40:10,369 - octoprint.plugins.psucontrol - INFO - Switching PSU Off
2021-01-30 08:40:10,386 - octoprint.plugins.action_command_notification - INFO - Notifications cleared

2021-01-30 08:40:23,635 - octoprint.server.util.flask - INFO - Passively logging in user jpokorny from ::ffff:192.168.5.109
2021-01-30 08:40:23,636 - octoprint.access.users - INFO - Logged in user: jpokorny
2021-01-30 08:40:23,782 - octoprint.server.util.sockjs - INFO - Client connection closed: ::ffff:192.168.5.109
2021-01-30 08:40:24,507 - tornado.access - WARNING - 409 GET /api/printer (::ffff:192.168.5.2) 14.37ms
2

Hello @jpokorny12!

If you need help, please use the proper sub-forum (the first in the list: Get Help)

So there are informations missing here that are asked for there.
And then, please share complete logs as files. That snippet here is just a part of the start-up sequence. Most important is the serial log. You have to enable it first.

3

In addition to what @Ewald_Ikemann says, please be more specific. You say "OctoPrint disconnects". From what? From the printer? From the network? Or from the web interface? What exactly do you mean by "disconnect"? What happens?

1 Like
4

Thanks, i change sub-forum
After M600 octoprint disconect from printer.

I attach the log.
I tried to enter via terminal M600, M701, M702 and turn on the filament sensor
serial (1).log (569.5 KB)
octoprint (1).log (86.9 KB)

5

Seems to be an issue with the printer, it stops responding to OctoPrint after the filament change:

2021-01-30 19:00:28,382 - Recv: //action:paused
2021-01-30 19:00:28,383 - Printer signalled that it paused, switching state...
2021-01-30 19:00:28,384 - Changing monitoring state from "Pausing" to "Paused"
2021-01-30 19:00:28,654 - Recv:  T:200.14 /200.00 B:51.28 /50.00 @:52 B@:127
2021-01-30 19:00:30,676 - Recv:  T:199.97 /200.00 B:51.58 /50.00 @:55 B@:0
2021-01-30 19:00:32,672 - Recv:  T:199.77 /200.00 B:51.82 /50.00 @:58 B@:0
2021-01-30 19:00:34,670 - Recv:  T:199.83 /200.00 B:51.82 /50.00 @:56 B@:0
2021-01-30 19:00:37,677 - 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.
2021-01-30 19:00:37,687 - Send: M105
2021-01-30 19:00:40,692 - 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.
2021-01-30 19:00:40,710 - Send: M105
2021-01-30 19:00:43,705 - No response from printer after 3 consecutive communication timeouts, considering it dead. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.

See it is responding with the temperatures, then it just stopped?

Try reporting it to Marlin, I see you are using the bugfix branch, which may have random issues from time to time. I have no problems with this feature on 2.0.7.2 (stable), maybe there is something broken in bugfix at the moment.

6

With the M600, the octoprint is disconnected from the printer. When the filament is replaced, the printer returns to place where was. The printer desnt prints, but the temperature is the same as when printing.

I'll try to upload a stable version of marlin
Thanks

7

I try with new build marlin, but it didnt help. Octoprint disconect after M600 and M702.
I attach log file and marlin config.

Thanks for advice
octoprint.log (165.4 KB) serial.log (6.3 KB)
Configuration - kopie.log (87.2 KB) Configuration_adv - kopie.log (141.3 KB)

8

In that log you have posted, I don't see any timeout issues...? I can see that you connected to the new Marlin build (2.0.7.2) but it doesn't go on to do much more.

9

When trigered filament sensor terminal shows this:

Changing monitoring state from "Pausing" to "Paused"
Recv: //action:paused
Printer signalled that it paused, switching state...
Recv: T:200.07 /200.00 B:48.44 /50.00 @:51 B@:0
Recv: T:200.10 /200.00 B:49.46 /50.00 @:51 B@:127
Recv: T:200.00 /200.00 B:49.87 /50.00 @:54 B@:127
Recv: T:200.03 /200.00 B:51.82 /50.00 @:53 B@:0
Recv: T:200.00 /200.00 B:51.82 /50.00 @:53 B@:0
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.
Send: M105
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.
Send: M105
No response from printer after 3 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 "Paused" to "Offline (Error: Too many consecutive timeouts, printer still connected and alive?)"
Connection closed, closing down monitor

octoprint.log (1.9 MB) serial.log (200.9 KB)

10

Can anyone help me?
Thank you