Moving to z0 after print, crash into model

Dretful · February 4, 2021, 6:17pm

What is the problem?

After completing a print my hot end descends to so and crashes into the model. I get a fail, and then a shutdown

What did you already try to solve it?

Looked at logs. Don’t understand. I have some lines in post print script.

Have you tried running in safe mode?

No, not sure it would help

Did running in safe mode solve the problem?

N/a

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.)</small

2021-02-03 17:30:31,633 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2021-02-03 17:30:31,642 - octoprint.server - INFO - --- Log roll over detected ---------------------------------------------------
2021-02-03 17:30:31,642 - octoprint.server - INFO - OctoPrint 1.5.3
2021-02-03 17:30:31,648 - octoprint.plugin.core - INFO - 24 plugin(s) registered with the system:
|  Action Command Notification Support (bundled) = /home/pi/oprint/lib/python2.7/site-packages/octoprint/plugins/action_command_notification
|  Action Command Prompt Support (bundled) = /home/pi/oprint/lib/python2.7/site-packages/octoprint/plugins/action_command_prompt
|  Announcement Plugin (bundled) = /home/pi/oprint/lib/python2.7/site-packages/octoprint/plugins/announcements
|  Anonymous Usage Tracking (bundled) = /home/pi/oprint/lib/python2.7/site-packages/octoprint/plugins/tracking
|  Application Keys Plugin (bundled) = /home/pi/oprint/lib/python2.7/site-packages/octoprint/plugins/appkeys
|  Backup & Restore (bundled) = /home/pi/oprint/lib/python2.7/site-packages/octoprint/plugins/backup
|  Bed Visualizer (1.0.0) = /home/pi/oprint/local/lib/python2.7/site-packages/octoprint_bedlevelvisualizer
|  Core Wizard (bundled) = /home/pi/oprint/lib/python2.7/site-packages/octoprint/plugins/corewizard
|  Creality Temperature (1.2.4) = /home/pi/oprint/local/lib/python2.7/site-packages/octoprint_CrealityTemperature
|  Creality-2x-temperature-reporting-fix (0.0.4) = /home/pi/oprint/local/lib/python2.7/site-packages/octoprint_ender3v2tempfix
|  Discovery (bundled) = /home/pi/oprint/lib/python2.7/site-packages/octoprint/plugins/discovery
|  Error Tracking (bundled) = /home/pi/oprint/lib/python2.7/site-packages/octoprint/plugins/errortracking
|  File Check (2020.8.7) (bundled) = /home/pi/oprint/local/lib/python2.7/site-packages/octoprint_file_check
|  Firmware Check (2020.9.23) (bundled) = /home/pi/oprint/local/lib/python2.7/site-packages/octoprint_firmware_check
|  GCode Viewer (bundled) = /home/pi/oprint/lib/python2.7/site-packages/octoprint/plugins/gcodeviewer
|  GPIO Shutdown (1.0.3) = /home/pi/oprint/local/lib/python2.7/site-packages/octoprint_GPIOShutdown
|  Logging (bundled) = /home/pi/oprint/lib/python2.7/site-packages/octoprint/plugins/logging
|  Pi Support Plugin (bundled) = /home/pi/oprint/lib/python2.7/site-packages/octoprint/plugins/pi_support
|  Plugin Manager (bundled) = /home/pi/oprint/lib/python2.7/site-packages/octoprint/plugins/pluginmanager
|  Pushover (0.3.8) = /home/pi/oprint/local/lib/python2.7/site-packages/octoprint_pushover
|  Software Update (bundled) = /home/pi/oprint/lib/python2.7/site-packages/octoprint/plugins/softwareupdate
|  Top Temp (0.0.0.4) = /home/pi/oprint/local/lib/python2.7/site-packages/octoprint_toptemp
|  TP-Link Smartplug (0.9.26) = /home/pi/oprint/local/lib/python2.7/site-packages/octoprint_tplinksmartplug
| !Virtual Printer (bundled) = /home/pi/oprint/lib/python2.7/site-packages/octoprint/plugins/virtual_printer
Prefix legend: ! = disabled, # = blacklisted, * = incompatible
2021-02-03 17:30:31,664 - octoprint.environment - INFO - Detected environment is Python 2.7.16 under Linux (linux2). Details:
|  hardware:
|      cores: 4
|      freq: 1500.0
|      ram: 1979641856
|  os:
|      bits: 32
|      id: linux
|      platform: linux2
|  plugins:
|      pi_support:
|          model: Raspberry Pi 4 Model B Rev 1.1
|          octopi_version: 0.17.0
|          throttle_state: '0x0'
|  python:
|      pip: 19.3.1
|      version: 2.7.16
|      virtualenv: /home/pi/oprint
2021-02-03 17:30:31,664 - octoprint.server - INFO - ------------------------------------------------------------------------------
2021-02-03 17:30:32,161 - octoprint.plugins.tracking - INFO - Sent tracking event ping, payload: {'octoprint_uptime': 83719}
2021-02-03 17:31:29,059 - octoprint.server.util.sockjs - INFO - New connection from client: ::ffff:192.168.0.51
2021-02-03 17:31:29,498 - octoprint.server.util.flask - INFO - Passively logging in user tony from ::ffff:192.168.0.51
2021-02-03 17:31:29,500 - octoprint.access.users - INFO - Logged in user: tony
2021-02-03 17:31:29,678 - octoprint.server.util.sockjs - INFO - User tony logged in on the socket from client ::ffff:192.168.0.51
2021-02-03 17:38:53,636 - octoprint.filemanager.analysis - INFO - Starting analysis of local:Front_LH_corner_v3.gcode
2021-02-03 17:38:53,640 - 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/Front_LH_corner_v3.gcode
2021-02-03 17:38:59,256 - octoprint.filemanager.analysis - INFO - Analysis of entry local:Front_LH_corner_v3.gcode finished, needed 5.62s
2021-02-03 17:39:13,819 - octoprint.util.comm - INFO - Changing monitoring state from "Offline" to "Detecting serial connection"
2021-02-03 17:39:13,847 - octoprint.util.comm - INFO - Serial detection: Performing autodetection with 1 port/baudrate candidates: /dev/ttyUSB0@115200
2021-02-03 17:39:13,847 - octoprint.util.comm - INFO - Serial detection: Trying port /dev/ttyUSB0, baudrate 115200
2021-02-03 17:39:13,848 - octoprint.util.comm - INFO - Connecting to port /dev/ttyUSB0, baudrate 115200
2021-02-03 17:39:13,864 - octoprint.util.comm - INFO - Serial detection: Handshake attempt #1 with timeout 2.0s
2021-02-03 17:39:13,866 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2021-02-03 17:39:13,874 - octoprint.util.comm - INFO - Changing monitoring state from "Detecting serial connection" to "Operational"
2021-02-03 17:39:13,880 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2021-02-03 17:39:13,934 - octoprint.util.comm - INFO - Printer reports firmware name "Marlin E3V2-2.0.x-16-3-Smith3D.M (Jan 13 2021"
2021-02-03 17:39:13,951 - octoprint.util.comm - INFO - Firmware states that it supports temperature autoreporting
2021-02-03 17:39:13,970 - octoprint.util.comm - INFO - Firmware states that it supports emergency GCODEs to be sent without waiting for an acknowledgement first
2021-02-03 17:39:14,197 - octoprint.plugins.tracking - INFO - Sent tracking event printer_connected, payload: {u'printer_baudrate': 115200, u'printer_port': None, u'firmware_name': u'Marlin E3V2-2.0.x-16-3-Smith3D.M (Jan 13 2021'}
2021-02-03 17:39:20,504 - octoprint.printer.standard.job - INFO - Print job selected - origin: local, path: Front_LH_corner_v3.gcode, owner: tony, user: tony
2021-02-03 17:39:25,706 - octoprint.util.comm - INFO - Starting job on behalf of user tony
2021-02-03 17:39:25,709 - octoprint.util.comm - INFO - Changing monitoring state from "Operational" to "Starting"
2021-02-03 17:39:25,728 - octoprint.printer.standard.job - INFO - Print job started - origin: local, path: Front_LH_corner_v3.gcode, owner: tony, user: tony
2021-02-03 17:39:25,821 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2021-02-03 17:39:25,847 - octoprint.util.comm - INFO - Changing monitoring state from "Starting" to "Printing"
2021-02-03 17:39:26,111 - octoprint.plugins.tracking - INFO - Sent tracking event print_started, payload: {u'origin': u'local', u'file': 'ba4d4623f1cc4cbc83a637c99b430d6b17ada000'}
2021-02-03 17:39:27,945 - octoprint.util.comm - INFO - Printer seems to support the busy protocol, will adjust timeouts and set busy interval accordingly
2021-02-03 17:40:10,920 - octoprint.util.comm - INFO - Telling the printer to set the busy interval to our "communicationBusy" timeout - 1s = 2s
2021-02-03 17:40:10,946 - octoprint.plugins.action_command_notification - INFO - Got a notification: Bed Heating...
2021-02-03 17:42:14,286 - octoprint.server.util.flask - INFO - Passively logging in user tony from fe80::44d:c995:e514:cbde
2021-02-03 17:42:14,289 - octoprint.access.users - INFO - Logged in user: tony
2021-02-03 17:42:18,760 - octoprint.server.util.sockjs - INFO - New connection from client: fe80::44d:c995:e514:cbde
2021-02-03 17:42:18,846 - octoprint.server.util.flask - INFO - Passively logging in user tony from fe80::44d:c995:e514:cbde
2021-02-03 17:42:18,849 - octoprint.access.users - INFO - Logged in user: tony
2021-02-03 17:42:19,418 - octoprint.plugins.softwareupdate - INFO - Fetching check overlays from https://plugins.octoprint.org/update_check_overlay.json
2021-02-03 17:42:22,734 - octoprint.server.util.sockjs - INFO - User tony logged in on the socket from client fe80::44d:c995:e514:cbde
2021-02-03 17:42:23,080 - octoprint.plugins.announcements - INFO - Loaded channel _important from https://octoprint.org/feeds/important.xml in 0.29s
2021-02-03 17:42:23,613 - octoprint.plugins.announcements - INFO - Loaded channel _releases from https://octoprint.org/feeds/releases.xml in 0.44s
2021-02-03 17:42:24,016 - octoprint.plugins.announcements - INFO - Loaded channel _blog from https://octoprint.org/feeds/octoblog.xml in 0.37s
2021-02-03 17:42:24,355 - octoprint.plugins.announcements - INFO - Loaded channel _plugins from https://plugins.octoprint.org/feed.xml in 0.31s
2021-02-03 17:42:25,014 - octoprint.plugins.announcements - INFO - Loaded channel _octopi from https://octoprint.org/feeds/octopi.xml in 0.25s
2021-02-03 17:42:25,658 - octoprint.plugins.pluginmanager - INFO - Loaded plugin repository data from https://plugins.octoprint.org/plugins.json
2021-02-03 17:42:26,940 - octoprint.plugins.pluginmanager - INFO - Loaded plugin notices data from https://plugins.octoprint.org/notices.json
2021-02-03 17:42:27,620 - octoprint.plugins.softwareupdate - WARNING - Unknown update check type for target smartfilamentsensor: <n/a>
2021-02-03 17:42:28,744 - octoprint.plugins.softwareupdate - INFO - Saved version cache to disk
2021-02-03 17:45:31,638 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2021-02-03 17:45:32,181 - octoprint.plugins.tracking - INFO - Sent tracking event ping, payload: {'octoprint_uptime': 84619}
2021-02-03 18:00:31,640 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2021-02-03 18:00:32,276 - octoprint.plugins.tracking - INFO - Sent tracking event ping, payload: {'octoprint_uptime': 85519}
2021-02-03 18:10:17,134 - octoprint.server.util.sockjs - INFO - Client connection closed: ::ffff:192.168.0.51
2021-02-03 18:15:31,642 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2021-02-03 18:15:32,149 - octoprint.plugins.tracking - INFO - Sent tracking event ping, payload: {'octoprint_uptime': 86419}
2021-02-03 18:18:13,069 - octoprint.server.util.sockjs - INFO - Client connection closed: fe80::44d:c995:e514:cbde
2021-02-03 18:26:55,309 - octoprint.server.util.flask - INFO - Passively logging in user tony from fe80::44d:c995:e514:cbde
2021-02-03 18:26:55,311 - octoprint.access.users - INFO - Cleaning up user session 35B87F82D0FD4144B11251181D9CABF5 for user tony
2021-02-03 18:26:55,315 - octoprint.access.users - INFO - Logged out user: tony
2021-02-03 18:26:55,320 - octoprint.access.users - INFO - Logged in user: tony
2021-02-03 18:27:09,936 - octoprint.server.util.sockjs - INFO - New connection from client: fe80::44d:c995:e514:cbde
2021-02-03 18:27:10,165 - octoprint.server.util.flask - INFO - Passively logging in user tony from fe80::44d:c995:e514:cbde
2021-02-03 18:27:10,167 - octoprint.access.users - INFO - Logged in user: tony
2021-02-03 18:27:13,597 - octoprint.server.util.sockjs - INFO - User tony logged in on the socket from client fe80::44d:c995:e514:cbde
2021-02-03 18:27:15,644 - octoprint.plugins.softwareupdate - WARNING - Unknown update check type for target smartfilamentsensor: <n/a>
2021-02-03 18:28:04,306 - octoprint.server.util.sockjs - INFO - Client connection closed: fe80::44d:c995:e514:cbde
2021-02-03 18:30:31,645 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2021-02-03 18:30:32,277 - octoprint.plugins.tracking - INFO - Sent tracking event ping, payload: {'octoprint_uptime': 87319}
2021-02-03 18:45:31,647 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2021-02-03 18:45:32,206 - octoprint.plugins.tracking - INFO - Sent tracking event ping, payload: {'octoprint_uptime': 88219}
2021-02-03 19:00:31,649 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2021-02-03 19:00:32,205 - octoprint.plugins.tracking - INFO - Sent tracking event ping, payload: {'octoprint_uptime': 89119}
2021-02-03 19:15:31,651 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2021-02-03 19:15:32,270 - octoprint.plugins.tracking - INFO - Sent tracking event ping, payload: {'octoprint_uptime': 90019}
2021-02-03 19:30:31,653 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2021-02-03 19:30:32,209 - octoprint.plugins.tracking - INFO - Sent tracking event ping, payload: {'octoprint_uptime': 90919}
2021-02-03 19:37:05,892 - octoprint.util.comm - WARNING - Received an error from the printer's firmware: Printer halted. kill() called!
| Last lines in terminal:
| Recv: ok
| Send: N58387 G1 X5 Y215*43
| Recv:  T:243.83 /244.00 B:60.01 /60.00 @:93 B@:25
| Recv: ok
| Send: N58388 G28 Z0*87
| Recv: echo:busy: processing
| Recv:  T:243.75 /244.00 B:60.00 /60.00 @:92 B@:28
| Recv: echo:busy: processing
| Recv:  T:243.75 /244.00 B:60.00 /60.00 @:91 B@:28
| Recv: echo:busy: processing
| Recv:  T:244.30 /244.00 B:60.00 /60.00 @:77 B@:28
| Recv: echo:busy: processing
| Recv:  T:245.00 /244.00 B:59.97 /60.00 @:61 B@:37
| Recv: echo:busy: processing
| Recv:  T:243.75 /244.00 B:59.99 /60.00 @:95 B@:33
| Recv:  T:243.75 /244.00 B:60.00 /60.00 @:92 B@:29
| Recv: echo:busy: processing
| Recv:  T:243.75 /244.00 B:60.00 /60.00 @:91 B@:30
| Recv: echo:busy: processing
| Recv: Error:Printer halted. kill() called!
2021-02-03 19:37:05,896 - octoprint.util.comm - INFO - Changing monitoring state from "Printing" to "Error: Printer halted. kill() called!"
2021-02-03 19:37:05,906 - octoprint.util.comm - INFO - Force-sending M112 to the printer
2021-02-03 19:37:05,955 - octoprint.util.comm - INFO - Changing monitoring state from "Error: Printer halted. kill() called!" to "Offline (Error: Printer halted. kill() called!)"
2021-02-03 19:37:06,365 - octoprint.plugins.tracking - INFO - Sent tracking event commerror_firmware, payload: {u'commerror_text': u'Printer halted. kill() called!'}
2021-02-03 19:37:21,046 - octoprint.plugins.tracking - INFO - Sent tracking event print_failed, payload: {u'origin': u'local', u'reason': u'error', u'commerror_text': u'Printer halted. kill() called!', u'file': 'ba4d4623f1cc4cbc83a637c99b430d6b17ada000', u'elapsed': 7060}
2021-02-03 19:37:22,543 - octoprint.plugins.action_command_notification - INFO - Notifications cleared
2021-02-03 19:37:22,550 - octoprint.plugins.action_command_notification - INFO - Notifications cleared
2021-02-03 19:44:00,079 - octoprint.server.util.sockjs - INFO - New connection from client: fe80::44d:c995:e514:cbde
2021-02-03 19:44:00,189 - octoprint.server.util.flask - INFO - Passively logging in user tony from fe80::44d:c995:e514:cbde
2021-02-03 19:44:00,192 - octoprint.access.users - INFO - Logged in user: tony
2021-02-03 19:44:00,345 - octoprint.server.util.sockjs - INFO - User tony logged in on the socket from client fe80::44d:c995:e514:cbde
2021-02-03 19:44:05,247 - tornado.access - WARNING - 400 POST /api/connection (fe80::44d:c995:e514:cbde) 37.34ms
2021-02-03 19:44:11,261 - octoprint.plugins.action_command_notification - INFO - Notifications cleared
2021-02-03 19:44:17,406 - octoprint.plugins.action_command_notification - INFO - Notifications cleared
2021-02-03 19:44:30,259 - octoprint.util.comm - INFO - Changing monitoring state from "Offline" to "Detecting serial connection"
2021-02-03 19:44:30,280 - octoprint.util.comm - INFO - Serial detection: Performing autodetection with 1 port/baudrate candidates: /dev/ttyUSB0@115200
2021-02-03 19:44:30,281 - octoprint.util.comm - INFO - Serial detection: Trying port /dev/ttyUSB0, baudrate 115200
2021-02-03 19:44:30,282 - octoprint.util.comm - INFO - Connecting to port /dev/ttyUSB0, baudrate 115200
2021-02-03 19:44:30,301 - octoprint.util.comm - INFO - Serial detection: Handshake attempt #1 with timeout 2.0s
2021-02-03 19:44:30,303 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2021-02-03 19:44:32,529 - octoprint.util.comm - INFO - Serial detection: Handshake attempt #2 with timeout 2.0s
2021-02-03 19:44:32,533 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2021-02-03 19:44:32,557 - octoprint.util.comm - INFO - Changing monitoring state from "Detecting serial connection" to "Operational"
2021-02-03 19:44:32,565 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2021-02-03 19:44:32,670 - octoprint.util.comm - INFO - Printer reports firmware name "Marlin E3V2-2.0.x-16-3-Smith3D.M (Jan 13 2021"
2021-02-03 19:44:32,688 - octoprint.util.comm - INFO - Firmware states that it supports temperature autoreporting
2021-02-03 19:44:32,700 - octoprint.util.comm - INFO - Firmware states that it supports emergency GCODEs to be sent without waiting for an acknowledgement first
2021-02-03 19:44:33,095 - octoprint.plugins.tracking - INFO - Sent tracking event printer_connected, payload: {u'printer_baudrate': 115200, u'printer_port': u'AUTO', u'firmware_name': u'Marlin E3V2-2.0.x-16-3-Smith3D.M (Jan 13 2021'}
2021-02-03 19:44:42,669 - octoprint.printer.standard.job - INFO - Print job selected - origin: local, path: top_corner.gcode, owner: tony, user: tony
2021-02-03 19:44:48,489 - octoprint.util.comm - INFO - Starting job on behalf of user tony
2021-02-03 19:44:48,500 - octoprint.util.comm - INFO - Changing monitoring state from "Operational" to "Starting"
2021-02-03 19:44:48,511 - octoprint.printer.standard.job - INFO - Print job started - origin: local, path: top_corner.gcode, owner: tony, user: tony
2021-02-03 19:44:48,626 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2021-02-03 19:44:48,656 - octoprint.util.comm - INFO - Changing monitoring state from "Starting" to "Printing"
2021-02-03 19:44:49,091 - octoprint.plugins.tracking - INFO - Sent tracking event print_started, payload: {u'origin': u'local', u'file': '245a654af8fd8f45bccadf76df7641c332bfed4f'}
2021-02-03 19:44:50,761 - octoprint.util.comm - INFO - Printer seems to support the busy protocol, will adjust timeouts and set busy interval accordingly
2021-02-03 19:44:58,173 - octoprint.server.util.sockjs - INFO - Client connection closed: fe80::44d:c995:e514:cbde
2021-02-03 19:45:20,749 - octoprint.util.comm - INFO - Telling the printer to set the busy interval to our "communicationBusy" timeout - 1s = 2s
2021-02-03 19:45:20,769 - octoprint.plugins.action_command_notification - INFO - Got a notification: Bed Heating...
2021-02-03 19:45:31,656 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2021-02-03 19:45:32,207 - octoprint.plugins.tracking - INFO - Sent tracking event ping, payload: {'octoprint_uptime': 91819}
2021-02-03 20:00:31,658 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2021-02-03 20:00:32,196 - octoprint.plugins.tracking - INFO - Sent tracking event ping, payload: {'octoprint_uptime': 92719}
2021-02-03 20:15:31,662 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2021-02-03 20:15:32,285 - octoprint.plugins.tracking - INFO - Sent tracking event ping, payload: {'octoprint_uptime': 93619}
2021-02-03 20:20:17,793 - octoprint.server.util.sockjs - INFO - New connection from client: fe80::44d:c995:e514:cbde
2021-02-03 20:20:17,950 - octoprint.server.util.flask - INFO - Passively logging in user tony from fe80::44d:c995:e514:cbde
2021-02-03 20:20:17,951 - octoprint.access.users - INFO - Logged in user: tony
2021-02-03 20:20:18,418 - octoprint.server.util.sockjs - INFO - User tony logged in on the socket from client fe80::44d:c995:e514:cbde
2021-02-03 20:23:18,061 - octoprint.server.util.sockjs - INFO - Client connection closed: fe80::44d:c995:e514:cbde
2021-02-03 20:30:31,664 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2021-02-03 20:30:32,218 - octoprint.plugins.tracking - INFO - Sent tracking event ping, payload: {'octoprint_uptime': 94519}
2021-02-03 20:44:30,277 - octoprint.util.comm - WARNING - Received an error from the printer's firmware: Printer halted. kill() called!
| Last lines in terminal:
| Recv: ok
| Send: N26635 G1 X5 Y215*46
| Recv: ok
| Send: N26636 G28 Z0*94
| Recv:  T:246.80 /247.00 B:69.99 /70.00 @:89 B@:48
| Recv: echo:busy: processing
| Recv:  T:247.50 /247.00 B:70.00 /70.00 @:74 B@:45
| Recv: echo:busy: processing
| Recv:  T:247.42 /247.00 B:70.00 /70.00 @:78 B@:45
| Recv: echo:busy: processing
| Recv:  T:246.95 /247.00 B:70.00 /70.00 @:90 B@:45
| Recv: echo:busy: processing
| Recv:  T:246.25 /247.00 B:70.00 /70.00 @:105 B@:45
| Recv: echo:busy: processing
| Recv:  T:246.33 /247.00 B:70.00 /70.00 @:101 B@:45
| Recv: echo:busy: processing
| Recv:  T:247.50 /247.00 B:70.00 /70.00 @:73 B@:45
| Recv:  T:247.50 /247.00 B:70.00 /70.00 @:75 B@:45
| Recv: echo:busy: processing
| Recv: Error:Printer halted. kill() called!
2021-02-03 20:44:30,279 - octoprint.util.comm - INFO - Changing monitoring state from "Printing" to "Error: Printer halted. kill() called!"
2021-02-03 20:44:30,289 - octoprint.util.comm - INFO - Force-sending M112 to the printer
2021-02-03 20:44:30,350 - octoprint.util.comm - INFO - Changing monitoring state from "Error: Printer halted. kill() called!" to "Offline (Error: Printer halted. kill() called!)"
2021-02-03 20:44:30,689 - octoprint.plugins.tracking - INFO - Sent tracking event commerror_firmware, payload: {u'commerror_text': u'Printer halted. kill() called!'}
2021-02-03 20:44:39,964 - octoprint.plugins.tracking - INFO - Sent tracking event print_failed, payload: {u'origin': u'local', u'reason': u'error', u'commerror_text': u'Printer halted. kill() called!', u'file': '245a654af8fd8f45bccadf76df7641c332bfed4f', u'elapsed': 3581}
*** truncated here***

Additional information about your setup

OctoPrint version, OctoPi version, printer, firmware, browser, operating system, ... as much data as possible
Latest octoprint. Ender 3v2. Pi4.

Ewald_Ikemann · February 4, 2021, 6:22pm

But logs would help...

BTW: What's in your slicer end gcode? And do you have a script in OctoPrint After print job completes:

grafik

Dretful · February 4, 2021, 6:27pm

Yeah just was trying to add logs, they are there now, was big. Will post octoprint scrips next

Dretful · February 4, 2021, 6:29pm

After print completes script

G91 ; Set to relative mode
G1 Z10 ; Move 10mm up
G90 ; Set to absolute mode again
G0 X1 Y1 ; get right out of the way

Dretful · February 4, 2021, 6:31pm

I am using mattercontrol slicer and as far as I can tell there isn’t any after print option there EDIT I was wrong - there is (I am exporting the Goode to the octopi server to print it, not using mattercontrol to manage the printer direct)

Dretful · February 4, 2021, 6:33pm

From another print log, last lines section

Ewald_Ikemann · February 4, 2021, 6:50pm

There is this in your logs:

Check the last lines of your gcode file for this sequence:

G28 Z0

This homes the Z-axes.

Dretful · February 4, 2021, 7:07pm

Thank you for your time Ewald. I will try to find what is causing this. I am assuming it must come from the slicer I controlmatters? The post of the octoprint after printing script presumably does not fet executed because there has already been a fail?
What does the *95 mean?

Ewald_Ikemann · February 4, 2021, 7:14pm

I assume the same.

That is indeed the case.

*95 is a checksum. It's for transmission verification.

Dretful · February 6, 2021, 4:29pm

Hello everyone.

I use the mattercontrol matterslicer. As advised above the problem is the line with a Z0 in it at the end of the print.

Looking in the mattercontrol slicer tab>G Code Tab > printer control section > End G code subsection,
there is (my emphasis)

G1 E-[retract_length] F[retract_speed]
G90
G0 X5 Y215 F[travel_speed]
G28 Z0 ; Retract and move away, then home Z axis

M104 S0 ; turn off temperature
M140 S0 ; turn off heat bed
M106 S0 ; turn off layer fan
M84 ; disable motors

BTW these settings that are 'out of the box' (being a newbie I've never found them before let alone changed them!)

This resulted in this bit of gcode in a sample of my print gcode files:

...
G1 X5 Y215
G28 Z0 ; Retract and move away, then home Z axis
M104 S0 ; turn off temperature
...

I don't use mattercontrol to actually control the printer, I prefer to export the gcode and then import it into the excellent octoprint.

But its clear that mattercontrol slicer end print settings are indeed added to the sliced gcode it creates regardless (of course!). Then I guess the octoprint end print gcode settings would be executed once these are done. So my take away is to put the end actions in one or the other but not try to use both places.

So thanks everyone for your guidance, I've located the problem and fixed it. edit - not so fast Dretful! - read on

Dretful · February 7, 2021, 12:25pm

Another problem with the above. Actually it seems the G28, by itself is also causing problem. I thought it was fixe but the printer still crashes after the same line of gcode. I'll take it out and see what happens then.

I'm assuming that G28 by itself = G1 X0 Y0 Z0?

Ewald_Ikemann · February 7, 2021, 12:26pm

Not quite. The G1 command only can go to the zero positions after they have been detected by the G28 command.

Try this:

In the OctoPrint terminal type in:

G28 X
G28 Y
G28 Z

line by line and see what happens.

Dretful · February 7, 2021, 12:40pm

Thanks Ewald.
I did this and I see each of those takes that axis to its 0 position

What I meant (didn't explain it well obviously) is that G28, (by itself) makes the print head move to X0 Y0 Z0

I just proved this by executing
G1 X40 Y40 Z40 ;to move it somewhere else then
G28 ;sure enough moves to X0 Y0 Z0

.. which is the root of my problem, because it then crashes into the just-printed model. Then the BLtouch throws an error and closes everything down (luckily)

In the beginning there was G28 Z0 on the same line
It seems therefore that the Z0 here was superfluous, because the G28 does that anyway, and its the G28 that causes the crash.

THANK YOU for introducing me to the Terminal. I think I'm learning a lot here.

Dretful · February 7, 2021, 1:02pm

so the full solution is

In the mattercontrol slicer tab>G Code Tab > printer control section > End G code subsection,
remove or comment out the whole of this line
G28 Z0 ; Retract and move away, then home Z axis

so it reads
**;**G28 Z0 ; Retract and move away, then home Z axis
(or you have deleted it)