Bed Visualiser Disconnects the Printer From Octoprint

What is the problem?

3/4 of the way through bed visualisation the printer disconnects from octopring and reports "Your printer's firmware reported an error. Due to that OctoPrint will disconnect." It also says that Probing has failed

What did you already try to solve it?

I have tired restarting both the Octoprint and printer.

Have you tried running in safe mode?

Running in safe mode doesn't allow for the pluggin to run.

Systeminfo Bundle

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

octoprint-systeminfo-20231227084637.zip (79.2 KB)

Recv: T:24.18 /0.00 B:59.96 /60.00 @:0 B@:42
Recv: echo:busy: processing
Recv: echo:busy: processing
Recv: echo:busy: processing
Recv: echo:busy: processing
Recv: echo:busy: processing
Recv: echo:busy: processing
Recv: echo:busy: processing
Recv: echo:busy: processing
Recv: Error:Probing Failed
Changing monitoring state from "Operational" to "Error"
Send: M112
Send: N2 M11235
Send: N3 M104 T0 S0
34
Send: N4 M140 S0*97
Changing monitoring state from "Error" to "Offline after error"
Connection closed, closing down monitor

Additional information about your setup

OctoPrint version, OctoPi version, printer, firmware, browser, operating system, ... as much data as possible
OctoPrint 1.9.3, Ender 3 V2, Chrome, OctoPi 1.0.0, Creality's last Bl/Cr touch firmware, Windows 10

Hello @Miles_Flusche !

A plugin can't do that.

The complete error message is this:

2023-12-27 08:04:06,957 - octoprint.util.comm - WARNING - Received an error from the printer's firmware: Probing Failed
| Last lines in terminal:
| Recv: echo:busy: processing
| Recv: echo:busy: processing
| Recv: echo:busy: processing
| Recv: echo:busy: processing
| Recv: echo:busy: processing
| Recv: echo:busy: processing
| Recv: echo:busy: processing
| Recv: echo:busy: processing
| Recv: echo:busy: processing
| Recv: echo:busy: processing
| Recv:  T:23.09 /0.00 B:59.97 /60.00 @:0 B@:39
| Recv: echo:busy: processing
| Recv: echo:busy: processing
| Recv: echo:busy: processing
| Recv: echo:busy: processing
| Recv: echo:busy: processing
| Recv: echo:busy: processing
| Recv: echo:busy: processing
| Recv: echo:busy: processing
| Recv: Error:Probing Failed
2023-12-27 08:04:06,958 - octoprint.util.comm - INFO - Changing monitoring state from "Operational" to "Error"

The Probing Failed is reported by the printer. The printer disconnected itself from OctoPrint.

Check if the probing works without obstacles in the way. Can also occur is the bed is not levelled enough.


Please also have a look on the Pi's PSU:

|      throttle_state: '0x80008'
1 Like

probing failed error messages are typically from trying to use these commands prior to running through the process once from the printer directly.

It turned out that the bed wasn't leveled enough and apparently the printer doesn't like it.

1 Like

Yeah, too much difference can also trigger probing failure. I always recommend going through manual leveling process first. You might want to check out the AutoBIM plugin for that.

So I tried Autobim and according to a youtube video a arrow should be showing up on the printer screen but nothing is.

ah, you don't have a firmware that shows M117 messages. might be able to install one of my M117 plugins and see those in the OctoPrint UI.