`Invalid adxl345 id (got f2 vs e5)` error running `ACCELEROMETER_QUERY` for the first time

Question

`Invalid adxl345 id (got f2 vs e5)` error running `ACCELEROMETER_QUERY` for the first time

hakimio opened this issue 2 years ago · comments

I understand that Invalid adxl345 id (got f2 vs e5) error is documented but instead of ignoring it, it should be fixed. This doesn't happen with FYSETC Portable Input Shaper and should not happen with KUSBA.

Isik · Answer 1 · Tue Dec 13 2022 13:33:21 GMT+0800 (China Standard Time)

This happens with a Raspberry Pi Pico with ADXL345 too, not just KUSBA. This is a Klipper problem and there is nothing I can do to fix it.

Tomas Rimkus · Answer 2 · Tue Dec 13 2022 16:26:07 GMT+0800 (China Standard Time)

Why doesn't this happen with FYSETC Portable Input Shaper which also uses RP2040?
If it's Klipper bug, where is the bug report and, if you know what's causing the issue, why don't you create a PR for Klipper?

Tomas Rimkus · Answer 3 · Tue Dec 13 2022 16:29:55 GMT+0800 (China Standard Time)

I guess you were referring to this closed bug report: Klipper3d/klipper#4712

Isik · Answer 4 · Tue Dec 13 2022 17:24:57 GMT+0800 (China Standard Time)

I have no idea why FYSETC PIS doesn't have this problem. Me and other people (simple discord searches can find some recent examples) had the invalid ID issue on the first query with Pi Picos too, not just KUSBA. This indicates a software issue.

One difference between the KUSBA vs PIS is, PIS uses different GPIO pins for the SPI bus to the ADXL, could be related. But the pins the KUSBA use are full HW SPI pins too, and they should work the same. Again, the only possible explanation I can think of for this is a Klipper bug, even if it is not reported on GitHub.

Tomas Rimkus · Answer 5 · Tue Dec 13 2022 17:45:00 GMT+0800 (China Standard Time)

Can you create a bug report on Klipper repo and link it here?

Fragmon · Answer 6 · Wed Jan 04 2023 21:46:13 GMT+0800 (China Standard Time)

I found a solution:

Use this:
[adxl345]
cs_pin: adxl:gpio1
#spi_bus: spi0a
spi_software_sclk_pin: adxl:gpio2
spi_software_mosi_pin: adxl:gpio3
spi_software_miso_pin: adxl:gpio0

Isik · Answer 7 · Thu Jan 12 2023 10:03:02 GMT+0800 (China Standard Time)

Ideally I prefer hardware SPI over software SPI, but I'll test it and if this fixes the issue without producing worse results I'll add it as an option to the .cfg.

Witawat · Answer 8 · Fri Feb 24 2023 13:35:22 GMT+0800 (China Standard Time)

Invalid adxl345 id (got f2 vs e5).
This is generally indicative of connection problems
(e.g. faulty wiring) or a faulty adxl345 chip.

how to fix ?
or use klipper version ?

Isik · Answer 9 · Fri Feb 24 2023 13:38:38 GMT+0800 (China Standard Time)

It is covered in the instructions: https://github.com/xbst/KUSBA#note-the-first-reading-from-the-accelerometer-will-be-invalid-usually-f2-vs-e5-this-is-expected-and-your-kusba-will-still-work-fine-after-the-first-query-run-accelerometer_query-once-before-starting-measuring-resonances
First reading will be invalid, should work fine after that.