Printer is not readyThe klippy host software is attempting to connect.

[limpid tusk]

I am so stuck. I updated everything and then started to upgrade to Can using a u2c board and ebb sb2209 (RP2040). I had multiple problems along the way and havnt finished switching my printer.cfg over to can setup but I beleive I am completely stuck before I can even begin to see errors in config. Any help would be so greatly appreciated.

[blazing forum]

Why is there a /dev/serial/by-path in your config?

[limpid tusk]

Printer was working well over a year ago and then an update broke it. I followed a guide and changing to by-path got it working again. I just tried going back to by-id and it is still having the same problem.

[blazing forum]

By-id does a couple of very important things.

1. It doesnt get confused if a usb cable gets moved
2. It shows the id of the device, which includes useful information like the fact that it's running klipper.

Anyway. What is `ls /dev/serial/by-id showing right now?

[limpid tusk]

lrwxrwxrwx 1 root root 13 Mar 10 08:52 usb-Klipper_stm32f446xx_0F0034001550335331383520-if00 -> ../../ttyACM0

[blazing forum]

Okay, and can I see a log when you're trying to use that?

[limpid tusk]

now its rpi mcu serial problems it looks like

[blazing forum]

Ah.

Yes, not not what you think

Something weird is happening here, that I can't quite see in the log

I think either something else is commented out that shouldn't be, or that set of coordinates should be commented out, one

Since I'm not sure what it is, I'm not completely sure which

[limpid tusk]

[mcu rpi]
serial: /tmp/klipper_host_mcu

##[adxl345]
##cs_pin: rpi:None

##[resonance_tester]
##accel_chip: adxl345
##probe_points:
175, 175, 20 # an example

[blazing forum]

Right, so you missed the last line when you decided to comment out the adxl and resonance tester sections

[limpid tusk]

ahh i see that now

[blazing forum]

And since its an indented line, klipper thinks its a continuation of the line above it