Echo:enqueueing "M600" as soon i start a job

Get Help
1

I have a CR-10S with RAMPS and Marlin firmware 1.1.8. When i run a job i immediatly see this line in terminal
"Recv: echo:enqueueing "M600"" and after the bed is heated up i have an error of communication because "Recv: Error:M600 Hotend too cold to change filament" and the hotend won't heated up.
Where is this M600 in the GCODE!?!?

I have already try this
https://discourse.octoprint.org/t/octoprint-keeps-running-into-communication-errors-and-timeouts/227

Octoprint 1.3.6
OctoPi 0.14
this is the serial.log https://pastebin.com/v9gL9viS

2

i'm a moron!
I have #define FILAMENT_RUNOUT_SENSOR activated but i don't wiring up the sensor!

3

@brunosso so that was the reason? I'd If so please mark it as the solution to your problem so that others may easily find it.

4

The reason is that the firmware have the check for the filament runout, but i don't connect the filament sensor. So the servo pin is always open and after bed heating up try to do an M600 to change filament. But the hotend is cold... and so on..

sorry but the problem is not related to OctoPrint!!!

5

Head -> DESK.

I had FIL_RUNOUT_INVERTING set wrong and was having the exact same problem. Sigh. Sometimes the printer is smarter than me.

Thanks both for pointing me in the right direction!

6

I’m having the same issue, octoprint enques the M600 command and continuesly does filament change. Printing from SD card works fine. Tried resetting the octopi and computer with no luck.

7

OctoPrint never enqueues commands on its own. Check a) installed plugins, b) your firmware, especially FIL_RUNOUT_INVERTING as mentioned by @jameswood.

8

If it was a firmware issue then why does it work with SD card?

9

Your printer doesn't necessarily behave the same printing from SD card as it does getting commands streamed. It will handle things differently, do internal stuff differently etc. But also note that I said "a) installed plugins" - stock OctoPrint won't happily send M600 on its own, but you might have a third party plugin installed that does that.

If your checks don't help unearth any reason, you'll definitely need to share more information (e.g. logs) to allow others to help you though.

10

Marlin 1.1.9 ... I get the same error:

Send: N6 M113 S2*103
Recv: Error:Hotend too cold
Changing monitoring state from "Printing" to "Error: Hotend too cold"
Changing monitoring state from "Error: Hotend too cold" to "Offline (Error: Hotend too cold)"
Connection closed, closing down monitor

How do I fix it? I followed this tutorial (https://youtu.be/f_-FIHq4WxE) and defined:
// define digital pin 4 for the filament runout sensor. Use the RAMPS 1.4 digital input 4 on the servos connector
#define FIL_RUNOUT_PIN 2

But still receive the message. Sensor is connected and lights up ...

11

ah seems like I had to change:

#define FIL_RUNOUT_INVERTING false
to
#define FIL_RUNOUT_INVERTING true

... for the CR10S