CR10Max - -mcu 'mcu': Unable to connect

Basic Information:

Printer Model: CR10Max
MCU / Printerboard: Creality V2.4 + EBB42
klippy.log

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’

Anyone able to offer any advice as to resolution?

Thanks in advanced


klippy.log (89.7 KB)

[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.

1 Like

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.

Is that likely to be causing my issue?

This refers to the CAN bus speed, not the serial baud rate of the board.

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.

Thanks for the input!

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.