Printer was running with no issues without EBB42 but also was well overdue an update so cant be sure whats lead to the new issue.
following re-wiring printer to allow dual z control and a fresh klipper install, MCU would connect successfully after commenting out functions removed from creality v2.4 board that have been moved to the EBB but before CAN/EBB42 was setup
after several issues, CAN/EBB42 seems to be up and running but now get a new error ‘mcu ‘mcu’: Unable to connect’
[mcu]
serial = /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A10K2YA3-if00-port0
baud = 1000000
Why did you change the default baud rate? 1M is not a valid baud for AVR (or any serial connection). You need to reflash the board with the default 250k setting and update your printer.cfg to match.
EBB42 has got an accelerometer and the advice I found online was to use either 500000 or 1000000 for everything. I’ve also ordered an eddie current level sensor which advises to use 1000000 so thats what I went with.
Thanks for the comments above. As I was writing about the baud rate I thought it should only be can…flashed the board to 250000 and edited the printer.cfg and it’s all working lovely.
…well that bits working, just got to troubleshoot a couple of new build type problems.