Bed Visualizer Probing Failed Printer killed Please Reset

ichmagpizza119 · February 17, 2023, 5:24pm

Sorry for the late reply. I was busy, had a lot of things going on.

I used the Billinear Bed Leveling.
So should I take this gcode?

M140 S60 ; starting by heating the bed for nominal mesh accuracy
G28      ; home all axes
M420 S0  ; Turning off bed leveling while probing, if firmware is set
         ; to restore after G28
M190 S60 ; waiting until the bed is fully warmed up
M155 S30 ; reduce temperature reporting rate to reduce output pollution
@BEDLEVELVISUALIZER	; tell the plugin to watch for reported mesh
G29 T	   ; run bilinear probing
M155 S3  ; reset temperature reporting
M140 S0 ; cooling down the bed
M500 ; store mesh in EEPROM

jneilliii · February 17, 2023, 6:29pm

yes, try those commands from the terminal tab one line at a time and see which one kills the printer.

ichmagpizza119 · February 18, 2023, 12:14pm

Okay,
I have sent M155 S30 and this error came:

Send: M155 S30
Communication timeout while idle, trying to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
Recv:   TT::19.9219.92  //0.000.00  BB::60.0060.00  //60.0060.00  @@::00  BB@@::5858
Recv: 
Recv: ok
No response from printer after 3 consecutive communication timeouts, considering it dead. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
Changing monitoring state from "Operational" to "Offline after error"
Connection closed, closing down monitor

And Octoprint said: "There was an error communicating with the printer. Please consult the terminal output and
octoprint (3).log (84.6 KB)
for details. Error: Too many consecutive timeouts, printer still connected and alive?"

Octoprint has never said that before. But the LCD Display has no Error.

ichmagpizza119 · February 18, 2023, 1:29pm

I have now sent G29 T and then the error happened, which was also the error before.

Send: G29 T
Recv:   TT::20.6620.66  //0.000.00  BB::60.0060.00  //60.0060.00  @@::00  BB@@::5252
Recv: 
Recv: echo:busy: processing
Printer seems to support the busy protocol, will adjust timeouts and set busy interval accordingly
Recv:   TT::20.5920.59  //0.000.00  BB::60.0160.01  //60.0060.00  @@::00  BB@@::4747
Recv: 
Recv: echo:busy: processing
Recv:   TT::20.6220.62  //0.000.00  BB::60.0260.02  //60.0060.00  @@::00  BB@@::4141
Recv: 
Recv: echo:busy: processing
Recv:   TT::20.6220.62  //0.000.00  BB::60.0160.01  //60.0060.00  @@::00  BB@@::4343
Recv: 
Recv: echo:busy: processing
Recv:   TT::20.5920.59  //0.000.00  BB::60.0060.00  //60.0060.00  @@::00  BB@@::4646
Recv: 
Recv: echo:busy: processing
Recv:   TT::20.6220.62  //0.000.00  BB::60.0160.01  //60.0060.00  @@::00  BB@@::4141
Recv: 
Recv: echo:busy: processing
Recv:   TT::20.6220.62  //0.000.00  BB::60.0260.02  //60.0060.00  @@::00  BB@@::3737
Recv: 
Recv: echo:busy: processing
Recv:   TT::20.6220.62  //0.000.00  BB::60.0060.00  //60.0060.00  @@::00  BB@@::4444
Recv: 
Recv: echo:busy: processing
Recv:   TT::20.6620.66  //0.000.00  BB::60.0160.01  //60.0060.00  @@::00  BB@@::3939
Recv: 
Recv:   TT::20.6620.66  //0.000.00  BB::60.0160.01  //60.0060.00  @@::00  BB@@::3838
Recv: 
Recv: echo:busy: processing
Recv:   TT::20.6220.62  //0.000.00  BB::60.0060.00  //60.0060.00  @@::00  BB@@::4242
Recv: 
Recv: echo:busy: processing
Recv:   TT::20.6220.62  //0.000.00  BB::60.0060.00  //60.0060.00  @@::00  BB@@::4141
Recv: 
Recv: echo:busy: processing
Recv:   TT::20.6220.62  //0.000.00  BB::60.0060.00  //60.0060.00  @@::00  BB@@::4141
Recv: 
Recv: echo:busy: processing
Recv:   TT::20.6220.62  //0.000.00  BB::60.0060.00  //60.0060.00  @@::00  BB@@::4141
Recv: 
Recv: echo:busy: processing
Recv:   TT::20.6220.62  //0.000.00  BB::59.9959.99  //60.0060.00  @@::00  BB@@::4545
Recv: 
Recv: echo:busy: processing
Recv:   TT::20.6220.62  //0.000.00  BB::59.9659.96  //60.0060.00  @@::00  BB@@::5555
Recv: 
Recv: echo:busy: processing
Recv:   TT::20.6220.62  //0.000.00  BB::59.9959.99  //60.0060.00  @@::00  BB@@::4848
Recv: 
Recv: echo:busy: processing
Recv:   TT::20.5920.59  //0.000.00  BB::59.9959.99  //60.0060.00  @@::00  BB@@::5050
Recv: 
Recv: echo:busy: processing
Recv:   TT::20.6220.62  //0.000.00  BB::60.0060.00  //60.0060.00  @@::00  BB@@::4747
Recv: 
Recv: echo:busy: processing
Recv:   TT::20.5920.59  //0.000.00  BB::59.9959.99  //60.0060.00  @@::00  BB@@::5252
Recv: 
Recv: echo:busy: processing
Recv:   TT::20.6620.66  //0.000.00  BB::60.0760.07  //60.0060.00  @@::00  BB@@::2424
Recv: 
Recv: echo:busy: processing
Recv: echo:busy: processing
Recv:   TT::20.5920.59  //0.000.00  BB::60.0260.02  //60.0060.00  @@::00  BB@@::3838
Recv: 
Recv: echo:busy: processing
Recv:   TT::20.5920.59  //0.000.00  BB::60.0060.00  //60.0060.00  @@::00  BB@@::4242
Recv: 
Recv:   TT::20.6220.62  //0.000.00  BB::60.0160.01  //60.0060.00  @@::00  BB@@::3636
Recv: 
Recv: echo:busy: processing
Recv:   TT::20.6220.62  //0.000.00  BB::60.0060.00  //60.0060.00  @@::00  BB@@::3939
Recv: 
Recv: echo:busy: processing
Recv:   TT::20.6220.62  //0.000.00  BB::60.0060.00  //60.0060.00  @@::00  BB@@::3838
Recv: 
Recv: echo:busy: processing
Recv:   TT::20.6220.62  //0.000.00  BB::59.9959.99  //60.0060.00  @@::00  BB@@::4242
Recv: 
Recv: echo:busy: processing
Recv:   TT::20.6220.62  //0.000.00  BB::60.0060.00  //60.0060.00  @@::00  BB@@::3838
Recv: 
Recv: echo:busy: processing
Recv:   TT::20.6220.62  //0.000.00  BB::59.9359.93  //60.0060.00  @@::00  BB@@::6262
Recv: 
Recv: echo:busy: processing
Recv:   TT::20.6220.62  //0.000.00  BB::59.9659.96  //60.0060.00  @@::00  BB@@::5757
Recv: 
Recv: echo:busy: processing
Recv:   TT::20.6220.62  //0.000.00  BB::59.9659.96  //60.0060.00  @@::00  BB@@::6161
Recv: 
Recv: echo:busy: processing
Recv:   TT::20.6220.62  //0.000.00  BB::59.9959.99  //60.0060.00  @@::00  BB@@::5454
Recv: 
Recv: echo:busy: processing
Recv:   TT::20.6220.62  //0.000.00  BB::59.9959.99  //60.0060.00  @@::00  BB@@::5757
Recv: 
Recv: echo:busy: processing
Recv:   TT::20.6220.62  //0.000.00  BB::60.0060.00  //60.0060.00  @@::00  BB@@::5555
Recv: 
Recv: echo:busy: processing
Recv:   TT::20.6220.62  //0.000.00  BB::59.9959.99  //60.0060.00  @@::00  BB@@::6161
Recv: 
Recv: echo:busy: processing
Recv: echo:busy: processing
Recv:   TT::20.6220.62  //0.000.00  BB::60.0060.00  //60.0060.00  @@::00  BB@@::5858
Recv: 
Recv:   TT::20.6220.62  //0.000.00  BB::60.0060.00  //60.0060.00  @@::00  BB@@::5858
Recv: 
Recv: echo:busy: processing
Recv: echo:busy: processing
Recv:   TT::20.6220.62  //0.000.00  BB::59.9959.99  //60.0060.00  @@::00  BB@@::6363
Recv: 
Recv: echo:busy: processing
Recv:   TT::20.6220.62  //0.000.00  BB::60.0060.00  //60.0060.00  @@::00  BB@@::5959
Recv: 
Recv: echo:busy: processing
Recv:   TT::20.6220.62  //0.000.00  BB::60.0060.00  //60.0060.00  @@::00  BB@@::5959
Recv: 
Recv: echo:busy: processing
Recv:   TT::20.6220.62  //0.000.00  BB::60.0560.05  //60.0060.00  @@::00  BB@@::4242
Recv: 
Recv:   TT::20.6220.62  //0.000.00  BB::60.1360.13  //60.0060.00  @@::00  BB@@::1111
Recv: 
Recv: echo:busy: processing
Recv:   TT::20.6220.62  //0.000.00  BB::60.0360.03  //60.0060.00  @@::00  BB@@::3636
Recv: 
Recv: echo:busy: processing
Recv:   TT::20.6220.62  //0.000.00  BB::60.0160.01  //60.0060.00  @@::00  BB@@::4040
Recv: 
Recv: echo:busy: processing
Recv:   TT::20.6220.62  //0.000.00  BB::60.0260.02  //60.0060.00  @@::00  BB@@::3434
Recv: 
Recv: echo:busy: processing
Recv:   TT::20.7020.70  //0.000.00  BB::60.0360.03  //60.0060.00  @@::00  BB@@::2828
Recv: 
Recv: echo:busy: processing
Recv:   TT::20.7420.74  //0.000.00  BB::60.0260.02  //60.0060.00  @@::00  BB@@::3030
Recv: 
Recv: echo:busy: processing
Recv:   TT::20.7020.70  //0.000.00  BB::60.0160.01  //60.0060.00  @@::00  BB@@::3333
Recv: 
Recv: echo:busy: processing
Recv:   TT::20.6620.66  //0.000.00  BB::60.0060.00  //60.0060.00  @@::00  BB@@::3636
Recv: 
Recv: echo:busy: processing
Recv:   TT::20.7420.74  //0.000.00  BB::60.0060.00  //60.0060.00  @@::00  BB@@::3535
Recv: 
Recv: echo:busy: processing
Recv: echo:busy: processing
Recv:   TT::20.8620.86  //0.000.00  BB::60.0060.00  //60.0060.00  @@::00  BB@@::3535
Recv: 
Recv:   TT::20.7820.78  //0.000.00  BB::60.0060.00  //60.0060.00  @@::00  BB@@::3535
Recv: 
Recv: echo:busy: processing
Recv: Error:Probing Failed
Changing monitoring state from "Operational" to "Error"
Send: M112
Send: N2 M112*35
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

This was at the End of the Probing. Does this have anything to do with the printer?

Ewald_Ikemann · February 18, 2023, 1:48pm

Sorry, the what?

ichmagpizza119 · February 18, 2023, 1:53pm

The display on the printer

Ewald_Ikemann · February 18, 2023, 1:58pm

But you know what LCD stands for?

ichmagpizza119 · February 18, 2023, 2:21pm

Liquid Crystal Display. But I still need help with my printers.

Ewald_Ikemann · February 18, 2023, 3:25pm

A reason for a failed probing can be an obstacle in the way of the probe.

ichmagpizza119 · February 18, 2023, 3:36pm

No, that isn't the problem. And the bed is new.

Ewald_Ikemann · February 18, 2023, 3:39pm

You may have a look on this thread:

jneilliii · February 18, 2023, 5:38pm

ok, that means your firmware probably doesn't support the command. remove those M155 lines from the gcode.

try the G29 line without the T

ichmagpizza119 · February 18, 2023, 7:35pm

I have already tried. Exactly the same error.

Ewald_Ikemann · February 18, 2023, 7:58pm

So it does all the probing points and fails with the last?

ichmagpizza119 · February 18, 2023, 8:13pm

Yes, the one in the top right corner.

Ewald_Ikemann · February 18, 2023, 8:21pm

I assume you have a Creality printer.

Is the printbed manually levelled as flat as possible? So that none of the corners is higher than the others?

ichmagpizza119 · February 19, 2023, 9:44am

I just screwed the pressure board all the way down. And now the same error happened at the first point.

ichmagpizza119 · February 19, 2023, 10:11am

I have now screwed all screws one turn upward. And it works again. Strange Bug. But thank you both for helping me.

Charlie_Powell · February 19, 2023, 11:27am

Often if the bed is too far out of level when it goes to probe a point (I can't remember what the distance is off the top of the bed) then this error will be triggered.

system · May 20, 2023, 11:27am

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