FYSETC adxl345 - Invalid adxl345 id (got ff vs e5)

General Discussion
1

Basic Information:

Printer Model: Custom Ender 3 pro
MCU / Printerboard: BTT SKR Mini E3 V3
Host / SBC: Raspberry pi 4 /
klippy.log

klippy.log (664.1 KB)

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:

…

Invalid adxl345 id (got ff vs e5).

trying to get my FYSETC adxl345 to work on my Klipper install, but get said error

adxl345.cfg (564 Bytes)
printer.cfg (4.1 KB)

2

looking at the adxl.cfg

it looked like it was configured for use on a BTT pi or something like that.

the guide i used was technically for a BTT adxl, not the fysetc one i have.

(what the guide used
BIGTREETECH ADXL345/S2DW Accelerometer Board for Running Klipper – Biqu Equipment)

what I used

3

From your description it is not clear what IMU board you really have. Please clarify and post a recent log.

4

Sorry.

The imu (I think that’s the a accelerometer right?)

Is the

I’ll get a log for ya as soon as i can.

Thank you so much for your patience with me.

5

I used ChatGPT to help figure a few things out.

in Klipper i can see via mainsail that the

mcu btt_adxl345 rp2040

is

Version: v0.12.0-307-g9426485bb

Load: 0.00, Awake: 0.00, Freq: 12 MHz,

So my pi detects the fystec board.

in my adxl345.cfg

i have

[mcu btt_adxl345]
serial: /dev/serial/by-id/usb-Klipper_rp2040_E6635C469F665C39-if00

[adxl345]
cs_pin: gpio13
spi_bus: /dev/spidev0.1

[resonance_tester]
probe_points: 100, 100, 20
accel_chip: adxl345

but i get error

Unknown spi_bus ‘/dev/spidev0.1’

I guess im trying to resolve that part now.

attached is a new klippy
klippy (1).log (679.0 KB)

6

here some exrta info that klipper was able to tell me about the Fysetc board

Constants

ADC_MAX

4095

BUS_PINS_i2c0a

gpio0,gpio1

BUS_PINS_i2c0b

gpio4,gpio5

BUS_PINS_i2c0c

gpio8,gpio9

BUS_PINS_i2c0d

gpio12,gpio13

BUS_PINS_i2c0e

gpio16,gpio17

BUS_PINS_i2c0f

gpio20,gpio21

BUS_PINS_i2c0g

gpio24,gpio25

BUS_PINS_i2c0h

gpio28,gpio29

BUS_PINS_i2c1a

gpio2,gpio3

BUS_PINS_i2c1b

gpio6,gpio7

BUS_PINS_i2c1c

gpio10,gpio11

BUS_PINS_i2c1d

gpio14,gpio15

BUS_PINS_i2c1e

gpio18,gpio19

BUS_PINS_i2c1f

gpio22,gpio23

BUS_PINS_i2c1g

gpio26,gpio27

BUS_PINS_spi0a

gpio0,gpio3,gpio2

BUS_PINS_spi0b

gpio4,gpio7,gpio6

BUS_PINS_spi0c

gpio16,gpio19,gpio18

BUS_PINS_spi0d

gpio20,gpio23,gpio22

BUS_PINS_spi1a

gpio8,gpio11,gpio10

BUS_PINS_spi1b

gpio12,gpio15,gpio14

BUS_PINS_spi1c

gpio24,gpio27,gpio26

CLOCK_FREQ

12000000

MCU

rp2040

PWM_MAX

255

STATS_SUMSQ_BASE

256

STEPPER_BOTH_EDGE

1

Last stats

mcu_awake

0

mcu_task_avg

0.000004

mcu_task_stddev

0.000003

bytes_write

3823

bytes_read

13422

bytes_retransmit

9

bytes_invalid

0

send_seq

610

receive_seq

610

retransmit_seq

2

srtt

0

rttvar

0

rto

0.025

ready_bytes

0

upcoming_bytes

0

freq

12000210

adj

12000479

7

changed the adxl345.cfg to exactly what was in here

and a little chat GPT later and whoohoo. different error lol. now i get

mcu ‘btt_adxl345’

should I just start a new thread or keep going here?

8

had an extra line of code in the ADXL.cfg

got rid of

[adxl345]
cs_pin: gpio13
spi_bus: /dev/spidev0.1

now it all works. WOOHOO!

9

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