I compiled a recent version of bugfix 2.0 and it started crashing during prints. So I grabbed the very latest and it is still crashing.

Octoprint log below but I don't think it tells me much.
What can I do to find out why it is crashing?


2021-01-24 12:10:14,435 - octoprint.printer.standard.job - INFO - Print job started - origin: local, path: CE3_3DBenchy.gcode, owner: _api, user: _api
2021-01-24 12:10:14,524 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2021-01-24 12:10:14,560 - octoprint.util.comm - INFO - Changing monitoring state from "Starting" to "Printing"
2021-01-24 12:10:15,751 - octoprint.plugins.DisplayLayerProgress - INFO - Store layer count in MetaFile
2021-01-24 12:10:16,140 - octoprint.plugins.DisplayLayerProgress - INFO - File select-event processing done!'
2021-01-24 12:10:16,153 - octoprint.plugins.DisplayLayerProgress - INFO - Printing started. Detailed progress started.{u'origin': u'local', u'name': u'CE3_3DBenchy.gcode', u'user': u'_api', u'owner': u'_api', u'path': u'CE3_3DBenchy.gcode', u'size': 2066719L}
2021-01-24 12:10:16,829 - octoprint.util.comm - INFO - Printer seems to support the busy protocol, will adjust timeouts and set busy interval accordingly
2021-01-24 12:13:14,383 - octoprint.util.comm - INFO - Telling the printer to set the busy interval to our "communicationBusy" timeout - 1s = 2s
2021-01-24 12:19:23,144 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2021-01-24 12:34:23,146 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2021-01-24 12:34:50,708 - octoprint.util.comm - WARNING - Received an error from the printer's firmware: Printer halted. kill() called!
| Last lines in terminal:
| Recv: uStep count 788 696 248 296
| Recv: DRVSTATUS X Y Z E
| Recv: sg_result 0 0 0 0
| Recv: stallguard *
| Recv: fsactive
| Recv: stst * * *
| Recv: olb *
| Recv: ola * *
| Recv: s2gb
| Recv: s2ga
| Recv: otpw *
| Recv: ot *
| Recv: Driver registers:
| Recv: X 0x20:17:00:00
| Recv: Y 0x00:12:00:00
| Recv: Z 0xE1:12:00:00
| Recv: E 0x06:19:00:00
| Recv:
| Recv:
| Recv: Errorrinter halted. kill() called!
2021-01-24 12:34:50,711 - octoprint.util.comm - INFO - Changing monitoring state from "Printing" to "Error: Printer halted. kill() called!"
2021-01-24 12:34:50,722 - octoprint.filemanager.analysis - INFO - Starting analysis of local:CE3_3DBenchy.gcode
2021-01-24 12:34:50,727 - 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/CE3_3DBenchy.gcode
2021-01-24 12:34:50,737 - octoprint.util.comm - INFO - Force-sending M112 to the printer
2021-01-24 12:34:51,003 - octoprint.util.comm - INFO - Changing monitoring state from "Error: Printer halted. kill() called!" to "Offline (Error: Printer halted. kill() called!)"
2021-01-24 12:34:51,216 - octoprint.plugins.DisplayLayerProgress - INFO - Printing stopped. Detailed progress stopped.

If this were your problem, what you you try to figure out what is going on?

Attaching configs in case anyone wants to look.
any help is appreciated.

Disable MONITOR_DRIVER_STATUS - it should be only enabled for debug purposes as it can negatively affect print quality and cause major problems. The messages shown in the terminal are coming from this setting.
Note that you do not have to enable MONITOR_DRIVER_STATUS to get full output from M122 for your TMC drivers - that's controlled by TMC_DEBUG which does not have the bad effects that MONITOR_DRIVER_STATUS has.

thank you. I'll try that and post back. Very helpfull.

3 prints in and no failures. that seems to have been the problem. Thank you much.

Edited 1 time(s). Last edit at 01/26/2021 04:07PM by EricE555.