Octoprint sending start command and making print fail

Get Help
1

What is the problem?
Octoprint is sending out a gcode command to start the printer right before the mmu2 unit is supposed to load the filament. This is causing the printer to restart and the print to fail.

What did you already try to solve it?
I updated prusa and mmu firmware, had a long conversation with prusa support, tried printing directly from printer sd card (and it worked thus octoprint is definitely the issue), tried restarting, tried factory reset on printer and mmu2, tried changing slicer settings to many different combinations

Logs (octoprint.log, serial.log or output on terminal tab at a minimum, browser error console if UI issue ... no logs, no support!)

Send: N35 G1 X240.0 E25.0 F2200.074
Recv: ok
Send: N36 G1 Y-2.0 F1000.028
Recv: ok
Send: N37 G1 X55.0 E25 F1400.0101
Recv: fsensor_stop_and_save_print
Recv: echo:Enqueing to the front: "PRUSA fsensor_recover"
Recv: echo: 3.8.1-2869
Recv: echo: Last Updated: Oct 24 2019 17:11:58 | Author: (none, default config)
Recv: Compiled: Oct 24 2019
Recv: echo: Free Memory: 2123 PlannerBufferBytes: 1392
Recv: echo:Hardcoded Default Settings Loaded
Recv: adc_init
Recv: CrashDetect ENABLED!
Recv: FSensor ENABLED
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: N38 M10528
Recv: echo:SD card ok
Recv: Error:Line Number is not Last Line Number+1, Last Line: 0
Recv: Resend: 1
Recv: ok
Send: N1 M73 P0 R19525
Recv: NORMAL MODE: Percent done: 0; print time remaining in mins: 195
Recv: SILENT MODE: Percent done: 255; print time remaining in mins: -1
Recv: ok
Send: N2 M73 Q0 S20021
Recv: NORMAL MODE: Percent done: 0; print time remaining in mins: 195
Recv: SILENT MODE: Percent done: 0; print time remaining in mins: 200
Recv: ok
Send: N3 M201 X1000 Y1000 Z1000 E8000*52
Recv: ok

Additional information about your setup (OctoPrint version, OctoPi version, printer, firmware, browser, operating system, ... as much data as possible)
octoprint 1.3.12, octopi 0.16, prusa mk3s with mmu2s with latest firmware.

2

RESOLVED
Found this since posting:

1 Like
3

I'm not able to get OctoPrint and MMU2S to work together.
Works fine via SD Card.
I have the profile setup for 5 extruders with 1 shared nozzle.
I'm on OctoPrint 1.4

Recv: echo:busy: processing
Recv: MMU => 'ok'
Recv: mmu_get_response() returning: 1
Recv: fsensor_stop_and_save_print
Recv: echo:Enqueing to the front: "PRUSA fsensor_recover"
Recv: start
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: N31 M10521
Printer sent 'start' while printing. External reset? Aborting job since printer lost state.
Send: N0 M110 N0125
Changing monitoring state from "Printing" to "Cancelling"
Recv: echo: 3.8.1-2869
Recv: echo: Last Updated: Oct 24 2019 17:11:58 | Author: (none, default config)
Recv: Compiled: Oct 24 2019
Recv: echo: Free Memory: 2123 PlannerBufferBytes: 1392
Recv: echo:Stored settings retrieved
Recv: adc_init
Recv: CrashDetect DISABLED
Recv: FSensor ENABLED
Recv: echo:SD card ok
Recv: Error:No Line Number with checksum, Last Line: 0
Send: N0 M110 N0*125
Recv: Resend: 1octoprint.log (22.4 KB) serial.log (148 Bytes)

4

That's not "OctoPrint sending start commands", that's your printer crashing and rebooting out of the blue. Looks to be caused by the filament sensor.