Octoprint does not show print completed

What is the problem?

When I start a 3d print everything seems to work fine, but for some reason once the print is completed the web gui stay in "State: Printing from SD" and seems not to revert back to ready to print.

What did you already try to solve it?

Web client restart/page refresh (close reopen)
Waited 1 hours after print completion.

Have you tried running in safe mode?

No

Did running in safe mode solve the problem?

Not tried

Systeminfo Bundle

You can download this in OctoPrint's System Information dialog ... no bundle, no support!)

browser.user_agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.212 Safari/537.36
connectivity.connection_check: 1.1.1.1:53
connectivity.connection_ok: true
connectivity.enabled: true
connectivity.online: true
connectivity.resolution_check: octoprint.org
connectivity.resolution_ok: true
env.hardware.cores: 4
env.hardware.freq: 2415.7
env.hardware.ram: 8227274752
env.os.bits: 64
env.os.id: linux
env.os.platform: linux
env.python.pip: 21.1.1
env.python.version: 3.8.10
env.python.virtualenv: false
octoprint.safe_mode: false
octoprint.version: 1.6.1
printer.firmware: Marlin Ver 1.0.2
systeminfo.generator: systemapi

Additional information about your setup

OctoPrint version, OctoPi version, printer, firmware, browser, operating system, ... as much data as possible

Printer : ender3 v2
Station : gigabyte brix (celeron J1900) with ubuntu server 21.04 and docker setup
Docker setup : Docker version 20.10.6, build 370c289
Container setup : octoprint/octoprint (docker hub) Version 1.6.1

Actually to make the printer available again, i must power off printer and remove usb cable , then plug them back and do a reconnect. (cancel printing seems to be stuck)

Many thanks for your advise.
Olivier

Then please do so.

Also share a systeminfo bundle, not just the textual snippet but the full zip file. Make sure to enable serial.log first, reproduce the issue, then share the bundle.

1 Like

It's probably a firmware issue, not telling OctoPrint the print is finished. When the printer is printing from SD OctoPrint is locked out of the room and does not know what is going on besides what it is told.

This looks like Creality Stock Firmware, which the usual bug-ridden one. This would be my first point to change, is use a different firmware - we've had loads of random bugs from it, this is probably another one. Or you can also print from OctoPrint rather than the SD card to ensure that it knows fully what is going on.

1 Like

Hello,

Sorry for the misunderstanding, I did more testing today regarding the different replies.

  • Run in safe mode and printing from octoprint filesystem : Test OK
  • Run in normal mode and printing from octoprint filesystem : Test OK
  • Run in normal mode dans printing from SD : Test KO (problem reproduced)

It seems it is linked to the "printing from SD" mode.

octoprint-systeminfo-20210528014203.zip (168.0 KB)

Please find the systeminfo bundle from my latest fail (normal mode + print from SD, serial log enabled)

I had a quick look and found some older traces in traces. To be clear the faulty print start on 2021-05-27 23:48:57, it was finished around 05-28 01:28:30 and I see the tracking plugin still reporting printer_state = 'PRINTING' at 05-28 01:36:13

2021-05-27 23:48:57,913 - octoprint.util.comm - INFO - Changing monitoring state from "Operational" to "Starting print from SD"

2021-05-28 01:28:34,911 - Recv: SD printing byte 2819999/2820001
2021-05-28 01:28:34,912 - Recv: ok
2021-05-28 01:28:35,824 - Send: M27
2021-05-28 01:28:36,106 - Recv: TT::240.55240.55 //0.000.00 BB::79.8979.89 //0.000.00 @@::00 BB@@::00
2021-05-28 01:28:36,108 - Recv:

2021-05-28 01:36:13,263 - octoprint.plugins.tracking - INFO - Sent tracking event ping, payload: {'octoprint_uptime': 29707, 'printer_state': 'PRINTING'}

Best regards,
Olivier

Thanks for the info, I did a test printing from octoprint filesystem and it works ... so it seems it is somewhat linked to printing from SD.

And yes 1.0.2 is stock firmware, in fact I don't like to flash firmware (I bricked a video card 20 years ago doing that) but I may have to in this case ... I will check how I can do it on a 3d printer.

Olivier

1 Like

When printing from SD, OctoPrint has to rely on the firmware for progress reports. It will not be able to know the print has completed unless the firmware reports 100% progress and says "print finished". Neither happens here:

2021-05-28 01:28:34,823 - Send: M27
2021-05-28 01:28:34,911 - Recv: SD printing byte 2819999/2820001
2021-05-28 01:28:34,912 - Recv: ok
2021-05-28 01:28:35,824 - Send: M27
2021-05-28 01:28:36,106 - Recv:   TT::240.55240.55  //0.000.00  BB::79.8979.89  //0.000.00  @@::00  BB@@::00
2021-05-28 01:28:36,108 - Recv:
2021-05-28 01:28:38,106 - Recv:   TT::240.00240.00  //0.000.00  BB::79.7379.73  //0.000.00  @@::00  BB@@::00
2021-05-28 01:28:38,108 - Recv:
[...]

Your firmware reports 2 bytes as still missing on the second to last M27 (= get SD print status), and never ever even responds to the last one. That's broken behaviour on part of the firmware. Either flash mainline Marlin (a good anyhow since Creality broken is known to be all kinds of broken) or don't print from SD.

2 Likes

Hello,

Thanks a lot for your reply and your analysis, I will update firmware (or not print from SD).

Best regards,
Olivier