PAD 7 connection to BTT MMB via Can bus

Hello,

i try to connect the MMB to the Pad7 via Can.

The instruction i got from https://canbus.esoterical.online/ and the Instruction from MMB and PAD 7.
When i Flash the Board wit Katapult i got:

dfu-util: Warning: Invalid DFU suffix signature
dfu-util: A valid DFU suffix will be required in a future dfu-util release
Opening DFU capable USB device...
Device ID 0483:df11
Device DFU version 011a
Claiming USB DFU Interface...
Setting Alternate Interface #0 ...
Determining device status...
DFU state(2) = dfuIDLE, status(0) = No error condition is present
DFU mode device DFU version 011a
Device returned transfer size 1024
DfuSe interface name: "Internal Flash "
Downloading element to address = 0x08000000, size = 4304
Erase [=========================] 100% 4304 bytes
Erase done.
Download [=========================] 100% 4304 bytes
Download done.
File downloaded successfully
Submitting leave request...
Transitioning to dfuMANIFEST state
dfu-util: can't detach
Resetting USB to switch back to Run-Time mode
make: *** [src/stm32/Makefile:65: flash] Error 251

after that i connect the MMB to the PAD with the 120R Resistor insert via CAN and when i try to Flash Klipper on the Board i get no UUID.

biqu@BTT-Pad7:~/katapult/scripts$ python3 flash_can.py -i can0 -q
Resetting all bootloader node IDs...
Checking for Katapult nodes...
CANBus UUID Query Complete

any Idea what i am doing wrong or does the PAD not working with MMB via CAN?

Thanks

Start with src/stm32/Makefile and katapult/scripts/flash_can.py, then compare the reported dfu-util output with the linked CAN-bus and MMB/PAD 7 instructions. Reproduce the flash and `python3 flash_can.py -i can0 -q` steps; done means the supported CAN setup is identified and the expected board UUID is returned, or the incompatibility is documented.

Written by the indexing model from the issue text.