search

markniu / Bed_Distance_sensor

Auto bed level with High resolution distance sensor
271 stars 26 forks source link

Z does not follow the mesh (motors stopped) #177

Open Liquidus-tech opened 2 weeks ago

Liquidus-tech commented 2 weeks ago

Good afternoon, I have this problem that I can't figure out: the z motors don't follow the created mesh, they are practically stationary... Can you help me solve this? Thank you klippy.log

luco85 commented 2 weeks ago

with klipper?

Liquidus-tech commented 2 weeks ago

Yes

luco85 commented 2 weeks ago

If you make a bed mesh on every print start is strange, otherwise if you save it check if in you start macro load the mesh created. Klipper do not load default mesh as in the past image

dronecz commented 2 weeks ago

Where do you have your sensor connected? Did you follow this?

Liquidus-tech commented 2 weeks ago

Hi, yes, I think I've done everything. In the meantime I updated to version 1.2c via Slink and Continue not following the mesh (I use Ideamaker). Home and QGL works fine. Launching commands

G28 BDSENSOR_SET REAL_TIME_HEIGHT=0.3 G1Z0.2

I received the following error:

Unable to get response "I2CBDr".

from .cgf I changed the delay from 20 to 11or 8 but nothing changed.

At this point I don't know how to proceed anymore... klippy.log

markniu commented 2 weeks ago

Hi, the real time level and the mesh bed level can not be work together, so you can remove the BDSENSOR_SET REAL_TIME_HEIGHT and use the normal mesh bed level first by using BED_MESH_CALIBRATE

Hi, yes, I think I've done everything. In the meantime I updated to version 1.2c via Slink and Continue not following the mesh (I use Ideamaker). Home and QGL works fine. Launching commands

G28 BDSENSOR_SET REAL_TIME_HEIGHT=0.3 G1Z0.2

I received the following error:

Unable to get response "I2CBDr".

from .cgf I changed the delay from 20 to 11or 8 but nothing changed.

At this point I don't know how to proceed anymore... klippy.log