More detailed logging?

What is the problem?

I'm getting M112 when connecting to printer

What did you already try to solve it?

I see this in the terminal/logs. I've also ran octoprint in safe mode, and connect without any issues. Clearly it's a plugin causing it (and it may be doing so for good reason) but without the details I'm unsure why, and how to fix if possible. I've checked through the logging settings, but not getting the detailed information I need.

Complete Logs

2020-08-03 13:39:49,820 - octoprint.plugin - DEBUG - Calling on_event on action_command_prompt
2020-08-03 13:39:49,821 - octoprint.plugin - DEBUG - Calling on_event on announcements
2020-08-03 13:39:49,822 - octoprint.plugin - DEBUG - Calling on_event on pluginmanager
2020-08-03 13:39:49,823 - octoprint.plugin - DEBUG - Calling on_event on printer_safety_check
2020-08-03 13:39:49,824 - octoprint.plugin - DEBUG - Calling on_event on softwareupdate
2020-08-03 13:39:49,825 - octoprint.plugin - DEBUG - Calling on_event on tracking
2020-08-03 13:39:49,826 - octoprint.plugin - DEBUG - Calling on_event on DisplayLayerProgress
2020-08-03 13:39:49,829 - octoprint.plugin - DEBUG - Calling on_event on PrintTimeGenius
2020-08-03 13:39:49,829 - octoprint.plugin - DEBUG - Calling on_event on dashboard
2020-08-03 13:39:49,830 - octoprint.plugin - DEBUG - Calling on_event on display_eta
2020-08-03 13:39:49,831 - octoprint.plugin - DEBUG - Calling on_event on dropbox_timelapse
2020-08-03 13:39:49,831 - octoprint.plugin - DEBUG - Calling on_event on filamentmanager
2020-08-03 13:39:49,832 - octoprint.plugin - DEBUG - Calling on_event on filamentsensorng
2020-08-03 13:39:49,833 - octoprint.plugin - DEBUG - Calling on_event on firmwareupdater
2020-08-03 13:39:49,833 - octoprint.plugin - DEBUG - Calling on_event on octorant
2020-08-03 13:39:49,834 - octoprint.plugin - DEBUG - Calling on_event on tplinksmartplug
2020-08-03 13:39:49,835 - octoprint.plugin - DEBUG - Calling on_event on webcamstreamer
2020-08-03 13:39:52,100 - octoprint.plugins.dashboard - INFO - cmd_results: 9V
2020-08-03 13:39:55,170 - octoprint.plugins.dashboard - INFO - cmd_results: 9V
2020-08-03 13:39:58,237 - octoprint.plugins.dashboard - INFO - cmd_results: 9V
2020-08-03 13:40:01,306 - octoprint.plugins.dashboard - INFO - cmd_results: 9V
2020-08-03 13:40:04,373 - octoprint.plugins.dashboard - INFO - cmd_results: 9V
2020-08-03 13:40:06,713 - octoprint.util.comm - INFO - Force-sending M112 to the printer
2020-08-03 13:40:06,723 - octoprint.util.comm - INFO - Changing monitoring state from "Operational" to "Offline (Error: Closing serial port due to emergency stop M112.)"

From the above, I thought it was .dashboard plugin, as these were some of the last cmds sent, so I disabled these, and got below.

Traceback (most recent call last):
File "/home/pi/OctoPrint/venv/local/lib/python2.7/site-packages/octoprint/plugin/init.py", line 224, in call_plugin
result = getattr(plugin, method)(*args, **kwargs)
File "/home/pi/OctoPrint/venv/local/lib/python2.7/site-packages/octoprint_filamentsensorng/init.py", line 129, in on_event
GPIO.remove_event_detect(self.pin)
RuntimeError: Please set pin numbering mode using GPIO.setmode(GPIO.BOARD) or GPIO.setmode(GPIO.BCM)
2020-08-03 13:49:02,329 - octoprint.plugin - DEBUG - Calling on_event on firmwareupdater
2020-08-03 13:49:02,329 - octoprint.plugin - DEBUG - Calling on_event on octorant
2020-08-03 13:49:02,330 - octoprint.plugin - DEBUG - Calling on_event on tplinksmartplug
2020-08-03 13:49:02,331 - octoprint.plugin - DEBUG - Calling on_event on webcamstreamer
2020-08-03 13:49:02,779 - octoprint.plugins.tracking - INFO - Sent tracking event print_failed, payload: {'origin': u'local', u'reason': u'error', u'commerror_text': u'Closing serial port due to emergency stop M112.', 'file': 'b68903b5e206ba4b8ed8bec6bb07570a1a6604ab', u'elapsed': 17}

Additional information about your setup

Using
OctoPrint 1.4.0
OctoPi 0.17.0
Snapmaker 2 A350
Firmware Version V1.9.0
Chrome

Could you please share complete octoprint.log and serial.log (the latter one may have to be enabled)

I actually think I figured it out and it's just me being an idiot.

I'm testing to confirm now, and will provide details either way.

So yeah looks like I'm just dumb.

I was using this, and somehow the settings either got reset, I messed with them on accident, or it's been running prints just fine with them and suddenly decided to utilize the plugin.

Either way, I'll bring it up with the creator of the plugin and see if we can nail down what went wrong there.

Regardless - thanks for the quick response and readiness to help @Ewald_Ikemann

1 Like