bdsensor is connected
When you issue the following command, the result is as follows:
m102 s-1 :
// BDsensorVer:V1.2c pandapi3d ,switch_mode=1,collision_homing=0,collision_cal=0
m102 s-2 :
0.0mm
This is the result of m102 s-2 when the nozzle is attached to the floor.
The settings of printer.cfg are as follows:
[BDsensor]
sda_pin: ^PE4
scl_pin: PE5
delay: 20
z_offset:0
x_offset: 0
y_offset: 23
samples:1
sample_retract_dist:2
no_stop_probe:
position_endstop: 0.5
speed:2
The result of m102 s-5 is
m102s-5 :
// 1024
BDSensor mounted too high!0.4mm to 2.4mm from BED atzero position is recommended
As shown in the photo, the result was high even though a bdsensor was attached.
Even if you attach a metallic object to the bdsensor, the result of m102 s-2 is 0.0m.
product : delta mainboard : btt skr2 (chip : STM32F429VGT6) klipper : lastest bdsensor: lastest
bdsensor is connected When you issue the following command, the result is as follows: m102 s-1 :
// BDsensorVer:V1.2c pandapi3d ,switch_mode=1,collision_homing=0,collision_cal=0 m102 s-2 : 0.0mm
This is the result of m102 s-2 when the nozzle is attached to the floor.
The settings of printer.cfg are as follows: [BDsensor] sda_pin: ^PE4 scl_pin: PE5 delay: 20 z_offset:0 x_offset: 0 y_offset: 23 samples:1 sample_retract_dist:2 no_stop_probe: position_endstop: 0.5 speed:2
The result of m102 s-5 is m102s-5 : // 1024 BDSensor mounted too high!0.4mm to 2.4mm from BED atzero position is recommended
As shown in the photo, the result was high even though a bdsensor was attached.
Even if you attach a metallic object to the bdsensor, the result of m102 s-2 is 0.0m.
I don't know what's wrong.