Report Mechanical Crash via MQTT

Get Help
1

What is the problem?

I have an Prusa MK3S with an OctoPi connected to it via USB.
Also I have integrated OctoPi into Home Assistant.
Everything works fine so far: I get noticed when there is an error or the print is finished.
Recently I noticed that the printer correctly stopped after detecting a mechanical crash/collision during printing and was waiting for user action. So far so good.
But I didn't get any notification and found my printing being idle waiting for me for several hours.
It would be great to get notifications about problems like that as well.

What did I already try to solve it?

I reproduced the mechanical crash with the same outcome.
I tried out the MQTT plugin for OctoPrint, but it seems not to send information about this problem to the broker. (Everything else worked finde.)

I disconnected the OctoPi and logged the output from the USB COM Port from the MK3S.
The MK3S is reporting mechanical crashes so the OctoPi would basically have the data about it.

Have I tried running in safe mode?

n/a

Did running in safe mode solve the problem?

n/a

Systeminfo Bundle

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

octoprint-systeminfo-20230604104404.zip (90.5 KB)

Additional information about your setup

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

My Questions in descending order of importance are:

  • Basically: Is the octopi just ignoring the data about mechanical crashes? Or have I overseen something?
  • Specifically: What would be best practice to make OctoPi processing data about mechanical crashes? If possible.
  • Plugin specific: How can this be achieved via the MQTT plugin?

Best regards and thank you in advance
erichstuder

2

Hello @erichstuder !

Question is: Does the printer report that crash as an error or just as an "User Maintenance Needed" issue?

If it is the latter one, what action command is sent to OctoPrint?
If it is not known by OctoPrint, OctoPrint can't react as expected.

BTW: You may have a look on your power supply:

2023-06-03 08:19:00,340 - octoprint.plugins.pi_support - WARNING - This Raspberry Pi is reporting problems that might lead to bad performance or errors caused by overheating or insufficient power.
!!! UNDERVOLTAGE REPORTED !!! Make sure that the power supply and power cable are capable of supplying enough voltage and current to your Pi.

|      throttle_state: '0x50005'

Edit:

You may can obtain that action command when you enable serial.log and trigger that mechanical issue again.

3

Hello @Ewald_Ikemann

The following log shows 3 consecutive mechanical crashes.
The 1st and 2nd one the printer handled by its own and continued.

The 3rd one resulted in the printer stopping and waiting for the user.
Some interesting lines from the attached log:
#513 2023-06-04 12:01:09,732 - Recv: echo:enqueing "CRASH_DETECTEDX"
#531 2023-06-04 12:01:17,749 - Recv: echo:busy: paused for user
#539 2023-06-04 12:01:25,369 - Recv: echo:enqueing "CRASH_RECOVER"

I'm not sure if it is reported as an error.
What do you think?

serial.log (57.2 KB)

4

Errors are reported as errors.

With that report from the printer

Recv: echo:enqueing "CRASH_DETECTEDX"

further action should be possible.

I'm not in with MQTT, maybe @foosel knows more.

5

Further information on the topic: paused-for-user-support

6

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.