Bed_Distance_sensor
Bed_Distance_sensor copied to clipboard
markniu
No data or corrupt data from BDsensor(), Please check connection
My setup was broken. So i had to reinstall everything. I am having an issue with katapult not being able to access after flashing the ebb42. So I have to flash klipper via stm32 programmer. I connected bdsensor to the ebb42 when flashing klipper after installing bdsensor. Now I get this error all the time. Im using BD Sensor v1. Everything was working including the bd sensor yesterday. klippy (27).log printer.txt
Ive checked continuity on the lead from the sensor to the board. OK Canboard communicating via CAN0. I just tried rolling back klipper to the previous version but no change.
Got katapult and klipper working still no chnage for bd sensor.
you can test BDsensor with the gpio on the Pi. for example: https://github.com/markniu/Bed_Distance_sensor/issues/111#issuecomment-2046685001 connect the bdsensor to the gpio on the PI like gpio17 and gpio27.
[mcu host] serial: /tmp/klipper_host_mcu
[BDsensor] .... scl_pin: host:gpio17 sda_pin: host:gpio27
compile and flash firmware: https://www.klipper3d.org/RPi_microcontroller.html
Ok. Got it working somewhat by flashing the beta firmware. M102 s-1 returns nothing M102 s-6 calibrates successfully However when I go to home z I get "Bed Distance Sensor data error:10.24" When I first started klipper up I got "collision_homing in printer.cfg invalid". So I commented out both collison homing lines.
What about this Mark? However when I go to home z I get "Bed Distance Sensor data error:10.24"
for finding out what's the problem hardware or software, I think you can try the gpio on the pi.
you can test BDsensor with the gpio on the Pi. for example: #111 (comment) connect the bdsensor to the gpio on the PI like gpio17 and gpio27. [mcu host] serial: /tmp/klipper_host_mcu [BDsensor] .... scl_pin: host:gpio17 sda_pin: host:gpio27 compile and flash firmware: https://www.klipper3d.org/RPi_microcontroller.html
host: Current version v0.12.0-124-g09a78c31 Up-to-date MCU(s):
Once the underlying issue is corrected, use the "RESTART" command to reload the config and restart the host software.
mcu 'host': Unknown command: I2C_BD_send
I connected the BD Sensor to my main board, recompiled and reflashed both EBB and M5P and got the same result. I used probe port PC15 and PC13 on the BTT M5P. Couldnt use RPI. Would have to setup as secondary MCU. :(
how about use the gpio in the EXP1? E.g. PB6 PB7
Im going to try the RPI.
3.2 40 Pins GPIO When Manta series motherboard work with CB1, 40 pins GPIO is a custom IO arrangement, as shown in the figure below, Pin 7 is CB1's "PC7", and Pin 11 is CB1's "PC14". The GPIO number of CB1 corresponds to (Px–PA)*32 + Pin For example: PC7 = (PC–PA)*32 + 7 = 2 * 32 + 7 = 71 PH10 = (PH–PA)*32 + 10 = 7 * 32 + 10 = 234 PC7 is numbered in Klipper as pin: host: gpio71, PH10 as pin: host: gpio234
WTH. Trying to make sense of this. I am using pin 11 and pin 15.
OMG. Finally worked it out. GPIO78 and GPIO74 Same error on CB1 GPIO.
worked on RPI GPIO?
OMG. Finally worked it out. GPIO78 and GPIO74 Same error on CB1 GPIO.
worked on RPI GPIO?
No. Same error. No data or corrupt data from BDsensor(), Please check connection
there is a version text on the sensor on the other side of the white connector, like v1.3 or v1.1
does the led on the sensor work? it will light on if it detects the metal else off.
does the led on the sensor work? it will light on if it detects the metal else off.
Yes led lights up when metal is brought nearby
then from the hardware, we can only to find if the problem is from the dead mcu or the cable. do you have one more cable to replace the old one for the bdsensor?
then from the hardware, we can only to find if the problem is from the dead mcu or the cable. do you have one more cable to replace the old one for the bdsensor?
No I dont. I checked the cable with the multimeter.
if you have a solder tool you can try to connect to a serial model, there will be many useful data output from the serial com port.
Would a ST LINK work?
No, the MCU on the v1.1 is not stm32
Would you be able to send me another bd sensor please? Ill get the USB>UART converter and debug this one for you.