MCU Connection issue after flashing ADXL345 v2.0

General Discussion
1

Basic Information:

Printer Model:
MCU / Printerboard:
Host / SBC
klippy.log

Fill out above information and in all cases attach your klippy.log file (use zip to compress it, if too big). Pasting your printer.cfg is not needed
Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there

Describe your issue:

… So i have tried adding the Adxl345 to do input shaper however i cannot connect to my printer mcu anymore now. After calling ls /dev/serial/by-id/, my printer mcu shows up so the Raspberry pi 4b is seeing the mcu, but will not connect. I have tried different cables, re-flashed the mcu, commented out everything to do with the adxl345 but still nothing. Im wondering if the pi is trying to connect to the adxl345 instead of the printer mcu?
Hope someone can help me as i am stumped…
Klipper.log.zip (3.0 MB)

2 
[mcu]
serial = usb-Klipper_lpc1769_2E500204E284D7955FE34662C42000F5-if00

This is the wrong path. It needs to be the full path as output by the ls command.

3

Also using BTT SKR1.4 Turbo, tried reflashing too and updated the Mcu iD but no luck.

4

ill try now and update you

5

usb-Klipper_lpc1769_2E500204E284D7955FE34662C42000F5-if00 is the id i get from my pi when calling ls /dev/serial/by-id/…

6

The correct command is:

ls /dev/serial/by-id/*
7

I think I need to be a little more observant, i see exactly where im going wrong. The BTT Adxl345 v2.0 instructions tell me to input ls /dev/serial/by-id/ not
ls /dev/serial/by-id/*. Thankyou for the help im connected again.

8

I think i used that same command to find my printer mcu again…

9

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