BDsensor M not workng with Octopus Max EZ board

[scrappys-garage]

I was getting no communication at all with the BLTouch port. I moved the SDA and SCL lines to the TFT port and now I get No data or corrupt data from BDsensor(V�.�c ��n��pi3d ), Please check connection. Delay is set to 40, and it worked briefly, then went back to this error message. If I swap in a regular BDsensor (not M) it works just fine. Communication is happening but it's just being garbled.

Every time I do M102 S-1 I get the above error and the light starts flashing quickly. and it won't connect any longer. Putting metal near the sensor does change the LED as expected.

Suggestions?

[markniu]

it seems the communication of the I2C is not stable, how about also swap the cable in a regular BDsensor(not M)?
you can try to increase the delay value in the [BDsensor]section from 10 to 15

[terri1769]

Out of town right now so I'll test delay change Saturday.

I've tried it with 2 different cables and also swapped in a regular BDsemsor. That one works fine.

Delay is currently set to 40 based on some googling. I'll try 10 and 20 when I get home.

Thanks

[scrappys-garage]

Not at home yet but I have done some testing. I set Delay back to 20 and still got the corrupt data message. I set it back to 10 and now I correctly get the expected output from m102 s-1. BDsensorVer:V1.2c pandapi3d ,switch_mode=1,collision_homing=1,collision_cal=1

I've tested homing now several times. I got it to work properly once. Allother times I get a crash with "Endstop stepper_z still triggered after retract". Attached is klippy.log. Since the communication issue appears to be fixed let me know if you want me to open a different ticket or put it under an existing one.

klippy.log

[markniu]

You can try to increase the homing_retract_dist from 2 to 4,
or add the following into the [BDsensor] senction

activate_gcode: 
    M400
    G4 P300

I've tested homing now several times. I got it to work properly once. Allother times I get a crash with "Endstop stepper_z still triggered after retract". Attached is klippy.log. Since the communication issue appears to be fixed let me know if you want me to open a different ticket or put it under an existing one.

klippy.log

[terri1769]

Changing the retract distance seems to have fixed it. Thanks!