markniu/Bed_Distance_sensor

Internal error on command:"BED_MESH_CALIBRATE"

Opened this issue · 7 comments

04srt10 commented

while attempting to perform a heightmap,

6:16 PM
Internal error on command:"BED_MESH_CALIBRATE"
6:16 PM
Klipper state: Shutdown
6:16 PM
probe at 10.000,190.000 is z=0.000000

also, with NO_STOP_PROBE enabled, it still stops at every point.

This is on a E3NG with an SKR MINI E3 V2 with a bd sensor.

markniu commented

hello, need to more message from the klippy.log, please attach the klippy.log file.

04srt10 commented

We resolved the issue with a manual klipper update! please close my ticket! thank you Mark

harlequincirrus commented

Hi there, i still have the same issue. I've updated all components, reinstalled klipper and the BD Sensor. But nothing seems to Work.
I'm as well using an e3ng with an skr 3 ez.

markniu commented

What's the first error message in the klippy.log?

the klipper should be update to the latest too if the error is same as o4srt10's klippy.log :

image

Hi there, i still have the same issue. I've updated all components, reinstalled klipper and the BD Sensor. But nothing seems to Work. I'm as well using an e3ng with an skr 3 ez.

harlequincirrus commented

Hi Mark,

thanks for the reply.

My first Error seems to be this one: BlockingIOError: [Errno 11] Resource temporarily unavailable

I'll attach the newest klippy.log. Sorry for the zip file but the log is 26mb, so to large to attach.
klippy-log.zip

markniu commented

the error is gcode.CommandError: Bed Distance Sensor data error0:10.24 this is a communication problem. and the klipper read a wrong data from bdsensor, Secure the cables with cable ties, especially around the connector, you can also increase the delay value in the BDsensor section from 10 to 15.

Hi Mark,

thanks for the reply.

My first Error seems to be this one: BlockingIOError: [Errno 11] Resource temporarily unavailable

I'll attach the newest klippy.log. Sorry for the zip file but the log is 26mb, so to large to attach. klippy-log.zip