What is the problem?
This happened now the second time:
I printed a part, which finished fine. Stepper, heated bed and hotend get turned off as expected.
After some time I recognized that my bed is heating again. So I reseted the printer.
The second time, I was again printing a part till it finished. 20min after the print, when I was assembling the parts my printer started to home all axis, the bed was already at printing temperature again and the hotend started heating to print the last part again. (I was not touching my PC at this time)
What did you already try to solve it?
Don't know where to start, since this happens randomly.
Have you tried running in safe mode?
No
Did running in safe mode solve the problem?
No
Complete Logs
octoprint.log, serial.log or output on terminal tab at a minimum, browser error console if UI issue ... no logs, no support! Not log excerpts, complete logs.)
{u'python': '2.7.16', u'os': u'linux', u'ram': 917016576, u'octopi_version': u'0.17.0', u'version': u'1.5.3', u'plugins': u'simpleemergencystop:1.0.4,gcodeeditor:0.2.10,preheat:0.5.1', u'pip': '19.3.1', u'cores': 4, u'freq': 1200.0, u'pi_model': u'Raspberry Pi 3 Model B Rev 1.2', u'bits': 32}
2021-01-23 19:25:03,200 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2021-01-23 19:25:03,421 - octoprint.plugins.tracking - INFO - Sent tracking event ping, payload: {'octoprint_uptime': 19}
2021-01-23 19:25:10,801 - octoprint.server.preemptive_cache - INFO - ... done in 13.69s
2021-01-23 19:28:45,914 - octoprint.filemanager.analysis - INFO - Starting analysis of local:beyerdynamic_dt770_mount2.gcode
2021-01-23 19:28:45,917 - octoprint.filemanager.analysis - INFO - Invoking analysis command: /home/pi/oprint/bin/python2 -m octoprint analysis gcode --speed-x=6000 --speed-y=6000 --max-t=10 --throttle=0.0 --throttle-lines=100 /home/pi/.octoprint/uploads/beyerdynamic_dt770_mount2.gcode
2021-01-23 19:28:52,657 - octoprint.server.util.flask - INFO - Passively logging in user octo from ::ffff:192.168.178.20
2021-01-23 19:28:52,661 - octoprint.access.users - INFO - Logged in user: octo
2021-01-23 19:28:54,066 - octoprint.server.util.flask - INFO - Passively logging in user octo from ::ffff:192.168.178.20
2021-01-23 19:28:54,068 - octoprint.access.users - INFO - Logged in user: octo
2021-01-23 19:28:54,717 - octoprint.server.util.sockjs - INFO - New connection from client: ::ffff:192.168.178.20
2021-01-23 19:28:54,814 - octoprint.server.util.flask - INFO - Passively logging in user octo from ::ffff:192.168.178.20
2021-01-23 19:28:54,815 - octoprint.access.users - INFO - Logged in user: octo
2021-01-23 19:28:55,112 - octoprint.plugins.softwareupdate - INFO - Fetching check overlays from https://plugins.octoprint.org/update_check_overlay.json
2021-01-23 19:28:55,131 - octoprint.filemanager.analysis - INFO - Analysis of entry local:beyerdynamic_dt770_mount2.gcode finished, needed 9.22s
2021-01-23 19:28:56,644 - octoprint.server.util.sockjs - INFO - User octo logged in on the socket from client ::ffff:192.168.178.20
2021-01-23 19:28:57,212 - octoprint.plugins.announcements - INFO - Loaded channel _important from https://octoprint.org/feeds/important.xml in 0.21s
2021-01-23 19:28:57,625 - octoprint.plugins.announcements - INFO - Loaded channel _releases from https://octoprint.org/feeds/releases.xml in 0.18s
2021-01-23 19:28:57,869 - octoprint.plugins.announcements - INFO - Loaded channel _blog from https://octoprint.org/feeds/octoblog.xml in 0.17s
2021-01-23 19:28:58,119 - octoprint.plugins.announcements - INFO - Loaded channel _plugins from https://plugins.octoprint.org/feed.xml in 0.17s
2021-01-23 19:28:58,406 - octoprint.plugins.announcements - INFO - Loaded channel _octopi from https://octoprint.org/feeds/octopi.xml in 0.18s
2021-01-23 19:29:00,315 - octoprint.util.pip - INFO - Using "/home/pi/oprint/bin/python2 -m pip" as command to invoke pip
2021-01-23 19:29:00,318 - octoprint.util.pip - INFO - pip installs to /home/pi/oprint/lib/python2.7/site-packages (writable -> yes), --user flag needed -> no, virtual env -> yes
2021-01-23 19:29:00,318 - octoprint.util.pip - INFO - ==> pip ok -> yes
2021-01-23 19:29:00,585 - octoprint.plugins.softwareupdate - INFO - Saved version cache to disk
2021-01-23 19:29:00,844 - octoprint.plugins.pluginmanager - INFO - Loaded plugin repository data from https://plugins.octoprint.org/plugins.json
2021-01-23 19:29:02,864 - octoprint.plugins.pluginmanager - INFO - Loaded plugin notices data from https://plugins.octoprint.org/notices.json
2021-01-23 19:29:04,113 - octoprint.printer.standard.job - INFO - Print job selected - origin: local, path: beyerdynamic_dt770_mount2.gcode, owner: octo, user: octo
2021-01-23 19:29:06,340 - octoprint.util.comm - INFO - Starting job on behalf of user octo
2021-01-23 19:29:06,353 - octoprint.util.comm - INFO - Changing monitoring state from "Operational" to "Starting"
2021-01-23 19:29:06,368 - octoprint.printer.standard.job - INFO - Print job started - origin: local, path: beyerdynamic_dt770_mount2.gcode, owner: octo, user: octo
2021-01-23 19:29:06,513 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2021-01-23 19:29:06,524 - octoprint.util.comm - INFO - Changing monitoring state from "Starting" to "Printing"
2021-01-23 19:29:06,658 - octoprint.plugins.tracking - INFO - Sent tracking event print_started, payload: {u'origin': u'local', u'throttled_now': False, u'throttled_mask': 327680, u'file': 'bb79865fb3757d749f677288b21f98e4ecd5d3ca', u'throttled_past': True}
2021-01-23 19:29:08,583 - octoprint.util.comm - INFO - Printer seems to support the busy protocol, will adjust timeouts and set busy interval accordingly
2021-01-23 19:31:43,159 - octoprint.util.comm - INFO - Telling the printer to set the busy interval to our "communicationBusy" timeout - 1s = 2s
2021-01-23 19:40:03,202 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2021-01-23 19:40:03,405 - octoprint.plugins.tracking - INFO - Sent tracking event ping, payload: {'octoprint_uptime': 919}
2021-01-23 19:51:25,595 - octoprint.util.comm - INFO - Finished in 1339.244 s.
2021-01-23 19:51:25,598 - octoprint.util.comm - INFO - Changing monitoring state from "Printing" to "Finishing"
2021-01-23 19:51:25,618 - octoprint.printer.standard.job - INFO - Print job done - origin: local, path: beyerdynamic_dt770_mount2.gcode, owner: octo
2021-01-23 19:51:25,742 - octoprint.util.comm - INFO - Changing monitoring state from "Finishing" to "Operational"
2021-01-23 19:51:25,880 - octoprint.plugins.tracking - INFO - Sent tracking event print_done, payload: {u'origin': u'local', u'throttled_mask': 327680, u'elapsed': 1339, u'file': 'bb79865fb3757d749f677288b21f98e4ecd5d3ca', u'throttled_now': False, u'throttled_past': True}
2021-01-23 19:55:03,211 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2021-01-23 19:55:03,505 - octoprint.plugins.tracking - INFO - Sent tracking event ping, payload: {'octoprint_uptime': 1819}
2021-01-23 20:10:03,230 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2021-01-23 20:10:03,434 - octoprint.plugins.tracking - INFO - Sent tracking event ping, payload: {'octoprint_uptime': 2719}
2021-01-23 20:16:06,635 - octoprint.util.comm - INFO - Starting job on behalf of user octo
2021-01-23 20:16:06,648 - octoprint.util.comm - INFO - Changing monitoring state from "Operational" to "Starting"
2021-01-23 20:16:06,662 - octoprint.printer.standard.job - INFO - Print job started - origin: local, path: beyerdynamic_dt770_mount2.gcode, owner: octo, user: octo
2021-01-23 20:16:06,818 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2021-01-23 20:16:06,834 - octoprint.util.comm - INFO - Changing monitoring state from "Starting" to "Printing"
2021-01-23 20:16:07,015 - octoprint.plugins.tracking - INFO - Sent tracking event print_started, payload: {u'origin': u'local', u'throttled_now': False, u'throttled_mask': 327680, u'file': 'bb79865fb3757d749f677288b21f98e4ecd5d3ca', u'throttled_past': True}
2021-01-23 20:18:47,094 - octoprint.util.comm - INFO - Cancelling job on behalf of user octo
2021-01-23 20:18:47,105 - octoprint.util.comm - INFO - Changing monitoring state from "Printing" to "Cancelling"
2021-01-23 20:18:47,145 - octoprint.printer.standard.job - INFO - Print job cancelled - origin: local, path: beyerdynamic_dt770_mount2.gcode, owner: octo, user: octo
2021-01-23 20:18:47,587 - octoprint.plugins.tracking - INFO - Sent tracking event print_cancelled, payload: {u'origin': u'local', u'throttled_mask': 327680, u'elapsed': 160, u'file': 'bb79865fb3757d749f677288b21f98e4ecd5d3ca', u'throttled_now': False, u'throttled_past': True}
2021-01-23 20:18:47,752 - octoprint.plugins.tracking - INFO - Sent tracking event print_failed, payload: {u'origin': u'local', u'throttled_mask': 327680, u'elapsed': 160, u'reason': u'cancelled', u'file': 'bb79865fb3757d749f677288b21f98e4ecd5d3ca', u'throttled_now': False, u'throttled_past': True}
2021-01-23 20:18:59,928 - octoprint.server.util.sockjs - INFO - Client connection closed: ::ffff:192.168.178.20
2021-01-23 20:18:59,978 - octoprint.server.util.flask - INFO - Passively logging in user octo from ::ffff:192.168.178.20
2021-01-23 20:18:59,980 - octoprint.access.users - INFO - Logged in user: octo
2021-01-23 20:19:01,060 - octoprint.server.util.flask - INFO - Passively logging in user octo from ::ffff:192.168.178.20
2021-01-23 20:19:01,061 - octoprint.access.users - INFO - Logged in user: octo
2021-01-23 20:19:01,762 - octoprint.server.util.sockjs - INFO - New connection from client: ::ffff:192.168.178.20
2021-01-23 20:19:01,800 - octoprint.server.util.flask - INFO - Passively logging in user octo from ::ffff:192.168.178.20
2021-01-23 20:19:01,800 - octoprint.access.users - INFO - Logged in user: octo
2021-01-23 20:19:03,407 - octoprint.server.util.sockjs - INFO - User octo logged in on the socket from client ::ffff:192.168.178.20
2021-01-23 20:19:11,624 - octoprint.util.comm - INFO - Force-sending M112 to the printer
2021-01-23 20:19:11,631 - octoprint.util.comm - WARNING - Received an error from the printer's firmware: Printer halted. kill() called!
| Last lines in terminal:
| Recv: T:143.39 /240.00 B:75.07 /75.00 @:127 B@:0
| Recv: T:144.11 /240.00 B:75.07 /75.00 @:127 B@:15 W:?
| Recv: T:147.81 /240.00 B:75.07 /75.00 @:127 B@:17 W:?
| Recv: echo:busy: processing
| Recv: T:150.73 /240.00 B:75.04 /75.00 @:127 B@:16
| Recv: T:151.52 /240.00 B:75.04 /75.00 @:127 B@:23 W:?
| Recv: T:155.24 /240.00 B:75.00 /75.00 @:127 B@:64 W:?
| Recv: echo:busy: processing
| Recv: T:158.11 /240.00 B:74.96 /75.00 @:127 B@:70
| Recv: T:158.84 /240.00 B:74.96 /75.00 @:127 B@:51 W:?
| Recv: T:162.50 /240.00 B:74.96 /75.00 @:127 B@:41 W:?
| Recv: echo:busy: processing
| Recv: T:165.44 /240.00 B:75.00 /75.00 @:127 B@:16
| Recv: T:166.10 /240.00 B:74.96 /75.00 @:127 B@:71 W:?
| Send: M112
| Send: N13 M112*19
| Send: N14 M104 T0 S0*20
| Send: N15 M140 S0*81
| Closing serial port due to emergency stop M112.
| Recv: Error:Printer halted. kill() called!
2021-01-23 20:19:11,635 - octoprint.util.comm - INFO - Changing monitoring state from "Cancelling" to "Error: Printer halted. kill() called!"
2021-01-23 20:19:11,643 - octoprint.util.comm - INFO - Changing monitoring state from "Error: Printer halted. kill() called!" to "Offline (Error: Printer halted. kill() called!)"
2021-01-23 20:19:11,650 - octoprint.util.comm - INFO - Force-sending M112 to the printer
2021-01-23 20:19:11,788 - octoprint.plugins.action_command_notification - INFO - Notifications cleared
2021-01-23 20:19:11,990 - octoprint.plugins.tracking - INFO - Sent tracking event commerror_firmware, payload: {u'throttled_now': False, u'throttled_past': True, u'commerror_text': u'Printer halted. kill() called!', u'throttled_mask': 327680}
2021-01-23 20:20:00,701 - octoprint.util.comm - INFO - Changing monitoring state from "Offline" to "Opening serial connection"
2021-01-23 20:20:00,713 - octoprint.util.comm - INFO - Connecting to port /dev/ttyACM0, baudrate 115200
2021-01-23 20:20:00,743 - octoprint.util.comm - INFO - Changing monitoring state from "Opening serial connection" to "Connecting"
2021-01-23 20:20:00,753 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2021-01-23 20:20:00,759 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2021-01-23 20:20:00,765 - octoprint.util.comm - INFO - Changing monitoring state from "Connecting" to "Operational"
2021-01-23 20:20:00,827 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2021-01-23 20:20:00,839 - octoprint.util.comm - INFO - Printer reports firmware name "Marlin bugfix-2.0.x (GitHub)"
2021-01-23 20:20:00,863 - octoprint.util.comm - INFO - Firmware states that it supports temperature autoreporting
2021-01-23 20:20:01,304 - octoprint.plugins.tracking - INFO - Sent tracking event printer_connected, payload: {u'printer_baudrate': 115200, u'printer_port': u'/dev/ttyACM0', u'firmware_name': u'Marlin bugfix-2.0.x (GitHub)'}
2021-01-23 20:25:03,246 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2021-01-23 20:25:03,438 - octoprint.plugins.tracking - INFO - Sent tracking event ping, payload: {'octoprint_uptime': 3619}
2021-01-23 20:25:31,158 - octoprint.server.util.sockjs - INFO - Client connection closed: ::ffff:192.168.178.20
2021-01-23 20:25:31,393 - octoprint.server.util.sockjs - INFO - New connection from client: ::ffff:192.168.178.20
2021-01-23 20:25:31,447 - octoprint.server.util.flask - INFO - Passively logging in user octo from ::ffff:192.168.178.20
2021-01-23 20:25:31,449 - octoprint.access.users - INFO - Logged in user: octo
2021-01-23 20:25:31,548 - octoprint.server.util.sockjs - INFO - User octo logged in on the socket from client ::ffff:192.168.178.20
2021-01-23 20:26:07,006 - octoprint.server.util.sockjs - INFO - Client connection closed: ::ffff:192.168.178.20
2021-01-23 20:26:07,215 - octoprint.server.util.sockjs - INFO - New connection from client: ::ffff:192.168.178.20
2021-01-23 20:26:07,314 - octoprint.server.util.flask - INFO - Passively logging in user octo from ::ffff:192.168.178.20
2021-01-23 20:26:07,317 - octoprint.access.users - INFO - Logged in user: octo
2021-01-23 20:26:07,369 - octoprint.server.util.sockjs - INFO - User octo logged in on the socket from client ::ffff:192.168.178.20
I didn't capture the serial log yet.
Additional information about your setup
OctoPrint version, OctoPi version, printer, firmware, browser, operating system, ... as much data as possible
OctoPrint 1.5.3 Python 2.7.16 OctoPi 0.17.0 on a Raspi 3 B
I am printing on a Anycubic Kossel Plus, but there is not much left stock, e.g. the board is a skr1.4 with Marlin 2.
My OS is Linux and I am using Firefox 84.
As I wrote:
"2021-01-23 20:16:06,635 - octoprint.util.comm - INFO - Starting job on behalf of user octo"
At this time I was not touching my PC, so I don't know why this happened. I also printed a couple of parts where this issue did not happen. After this happened the first time, I recognized in the log that my power supply was not sufficant so I replaced it with another one so that's why the warning doesn't show up later in the log.