# FYSETC adxl345 - Invalid adxl345 id (got ff vs e5) **URL:** \ **Category:** General Discussion\ **Created:** [September 28, 2024, 1:53am UTC](https://klipper.discourse.group/t/fysetc-adxl345-invalid-adxl345-id-got-ff-vs-e5/19059 "2024-09-28T01:53:47Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![obsidianwraith](https://avatars.discourse-cdn.com/v4/letter/o/d78d45/32.png) [@obsidianwraith](https://klipper.discourse.group/u/obsidianwraith)\ **Post date:** [September 28, 2024, 1:53am UTC](https://klipper.discourse.group/t/fysetc-adxl345-invalid-adxl345-id-got-ff-vs-e5/19059/1 "2024-09-28T01:53:47Z")
### Basic Information: Printer Model: Custom Ender 3 pro MCU / Printerboard: BTT SKR Mini E3 V3 Host / SBC: Raspberry pi 4 / klippy.log [klippy.log](https://klipper.discourse.group/uploads/short-url/pZpUxVlnKbKA3JfZwpX9na0wwIT.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](https://klipper.discourse.group/uploads/short-url/cjEaTAoLGPQvI26uqPaYou0eENZ.cfg) (564 Bytes) [printer.cfg](https://klipper.discourse.group/uploads/short-url/yW8uhJ6klN2F5YB5NLeYF2jgyKE.cfg) (4.1 KB) ---
**Author:** ![obsidianwraith](https://avatars.discourse-cdn.com/v4/letter/o/d78d45/32.png) [@obsidianwraith](https://klipper.discourse.group/u/obsidianwraith)\ **Post date:** [September 28, 2024, 2:29am UTC](https://klipper.discourse.group/t/fysetc-adxl345-invalid-adxl345-id-got-ff-vs-e5/19059/2 "2024-09-28T02:29:18Z")
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](https://biqu.equipment/products/adxl-345-accelerometer-board-for-36-stepper-motors?variant=40446852759650&sscid=91k8_16bmce&)) what I used > **[FYSETC Portable Input Shaper with RP2040 Upgraded 3D Printer Parts Su](https://www.fysetc.com/products/fysetc-portable-input-shaper-with-rp2040-upgraded-3d-printer-parts-support-klipper-for-voron-2-4-0-1-trident)** > > FYSETC Portable Input Shaper with RP2040 Upgraded 3D Printer Parts Support Klipper for Voron 2.4 0.1 Trident   Aboout the Product: Base on popular RP2040 chip Portable and you can use it on multiple Klipper firmware based 3D printer with same... ---
**Author:** ![Sineos](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/sineos/32/18_2.png) [@Sineos](https://klipper.discourse.group/u/Sineos)\ **Post date:** [September 28, 2024, 1:54pm UTC](https://klipper.discourse.group/t/fysetc-adxl345-invalid-adxl345-id-got-ff-vs-e5/19059/3 "2024-09-28T13:54:35Z")
From your description it is not clear what IMU board you really have. Please clarify and post a recent log. ---
**Author:** ![obsidianwraith](https://avatars.discourse-cdn.com/v4/letter/o/d78d45/32.png) [@obsidianwraith](https://klipper.discourse.group/u/obsidianwraith)\ **Post date:** [September 28, 2024, 7:56pm UTC](https://klipper.discourse.group/t/fysetc-adxl345-invalid-adxl345-id-got-ff-vs-e5/19059/4 "2024-09-28T19:56:11Z")
Sorry. The imu (I think that’s the a accelerometer right?) Is the > **[FYSETC Portable Input Shaper with RP2040 Upgraded 3D Printer Parts Su](https://www.fysetc.com/products/fysetc-portable-input-shaper-with-rp2040-upgraded-3d-printer-parts-support-klipper-for-voron-2-4-0-1-trident)** > > FYSETC Portable Input Shaper with RP2040 Upgraded 3D Printer Parts Support Klipper for Voron 2.4 0.1 Trident   Aboout the Product: Base on popular RP2040 chip Portable and you can use it on multiple Klipper firmware based 3D printer with same... I’ll get a log for ya as soon as i can. Thank you so much for your patience with me. ---
**Author:** ![obsidianwraith](https://avatars.discourse-cdn.com/v4/letter/o/d78d45/32.png) [@obsidianwraith](https://klipper.discourse.group/u/obsidianwraith)\ **Post date:** [September 29, 2024, 6:38am UTC](https://klipper.discourse.group/t/fysetc-adxl345-invalid-adxl345-id-got-ff-vs-e5/19059/5 "2024-09-29T06:38:43Z")
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](https://klipper.discourse.group/uploads/short-url/A2pPu1bufx3a99iKluHt7SYWblw.log) (679.0 KB) ---
**Author:** ![obsidianwraith](https://avatars.discourse-cdn.com/v4/letter/o/d78d45/32.png) [@obsidianwraith](https://klipper.discourse.group/u/obsidianwraith)\ **Post date:** [September 29, 2024, 6:40am UTC](https://klipper.discourse.group/t/fysetc-adxl345-invalid-adxl345-id-got-ff-vs-e5/19059/6 "2024-09-29T06:40:04Z")
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 ---
**Author:** ![obsidianwraith](https://avatars.discourse-cdn.com/v4/letter/o/d78d45/32.png) [@obsidianwraith](https://klipper.discourse.group/u/obsidianwraith)\ **Post date:** [September 29, 2024, 7:32am UTC](https://klipper.discourse.group/t/fysetc-adxl345-invalid-adxl345-id-got-ff-vs-e5/19059/7 "2024-09-29T07:32:43Z")
changed the adxl345.cfg to exactly what was in [here](https://github.com/FYSETC/FYSETC-PortableInputShaper/blob/main/PIS.cfg) 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? ---
**Author:** ![obsidianwraith](https://avatars.discourse-cdn.com/v4/letter/o/d78d45/32.png) [@obsidianwraith](https://klipper.discourse.group/u/obsidianwraith)\ **Post date:** [September 29, 2024, 7:38am UTC](https://klipper.discourse.group/t/fysetc-adxl345-invalid-adxl345-id-got-ff-vs-e5/19059/8 "2024-09-29T07:38:25Z")
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! ---
**Author:** ![system](https://global.discourse-cdn.com/free1/uploads/klipper/original/1X/64419bf2aac6639e6ef5cef200dcd456b0a01ac3.png) [@system](https://klipper.discourse.group/u/system)\ **Post date:** [October 29, 2024, 5:39pm UTC](https://klipper.discourse.group/t/fysetc-adxl345-invalid-adxl345-id-got-ff-vs-e5/19059/9 "2024-10-29T17:39:15Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.