search

markniu / Bed_Distance_sensor

Auto bed level with High resolution distance sensor
281 stars 28 forks source link

MCU 'EBBCan' shutdown: Invalid oid type - Seems linked to realtime level #162

Open feral42 opened 4 months ago

feral42 commented 4 months ago

This happens when I try to enable realtime leveling. I follow the instructions to enable and test:

G28
BDSENSOR_SET REAL_TIME_HEIGHT=0.3
G1 Z0.3

as soon as the nozzle gets to the 0.3 mark it crashes with:

Klipper reports: SHUTDOWN

MCU 'EBBCan' shutdown: Invalid oid type
Once the underlying issue is corrected, use the
"FIRMWARE_RESTART" command to reset the firmware, reload the
config, and restart the host software.
Printer is shutdown

and I get this in the console:

2:21 AM
Klipper state: Shutdown
2:21 AM
Curent z:0.30 (gcode_z:0.30 - (z_offset:0.00 - z_offset_adj:0.00))
2:21 AM
Real time leveling height:0.30 ( 0.30 - z_offset:0.00 )
2:21 AM
Collision: 1.7280 mm, Bed: 22.0C
2:21 AM
g1 z.3
2:20 AM
BDSENSOR_SET REAL_TIME_HEIGHT=0.3
2:20 AM
BDsensorVer:V1.2c,switch_mode=1,collision_homing=1,collision_cal=1
2:20 AM
g28

I have a Manta M8p V2.0 with CB2 installed on it. It has a SB2240 attached using usb, and that is what the BDSensor is hooked to.

I've attached my relevant configs and logs.

klippy-48.log EBBCan.txt printer.txt

Thanks for any insight you can provide!

markniu commented 4 months ago

the reason is that the realtime level only support the BDsensor and z motors are connected in the same MCU. here needs to connect the bdsensor to the M8p board.