Implement ADXL355 support

entemomoh · March 4, 2026, 11:46am

Fellow printer nerds!

If you are interested in using ADXL355 accelerometers for input shaper (and I am sure there are dozens of us ), then I have a solution

I opened a pull request after adding support for the sensor to my own printer running klipper; see here:

github.com/Klipper3d/klipper

Add ADXL355 accelerometer support over SPI (#7215)

master ← entemomoh2:feature/adxl355-upstream

opened 12:00PM - 02 Mar 26 UTC

entemomoh2

+440 -19

# Summary This PR adds ADXL355 accelerometer support over SPI for Klipper reson…ance measurement and input shaper workflows. ## It includes: - MCU-side ADXL355 bulk sampling support - Host-side [adxl355] module with standard ACCELEROMETER_* commands - Documentation updates for config, G-codes, API endpoint, and resonance guide - A compatibility fix for boards where POWER_CTL.STANDBY reads back as 0 ## What’s Included 1) MCU support Added src/sensor_adxl355.c Added MCU commands: config_adxl355 query_adxl355 query_adxl355_status Wired build/config: src/Makefile: CONFIG_WANT_ADXL355 src/Kconfig: new WANT_ADXL355 option and NEED_SENSOR_BULK dependency update 2) Host module Added klippy/extras/adxl355.py Uses bulk_sensor.FixedFreqReader + BatchBulkHelper pattern Supports: ACCELEROMETER_QUERY ACCELEROMETER_MEASURE ACCELEROMETER_DEBUG_READ ACCELEROMETER_DEBUG_WRITE Supports axes_map and ADXL355 ODR rate values Validates device IDs (DEVID_AD, DEVID_MST, PARTID) 3) Robustness fix Handles ADXL355 variants that always read POWER_CTL.STANDBY back as 0 Keeps strict register write verification for all other cases 4) Documentation Updated: - docs/Config_Reference.md - docs/G-Codes.md - docs/API_Server.md - docs/Measuring_Resonances.md Validation ## Test environment: OctoPi / Raspberry Pi host MCU ([mcu rpi]) ADXL355 connected via SPI (spidev0.0) ## Build/runtime checks performed: make -j4 successful (including sensor_adxl355.c) Host module import/compile sanity check successful RPi host MCU updated and restarted with ADXL355 commands present Command checks: ```ACCELEROMETER_DEBUG_READ CHIP=adxl355 REG=0x00 -> 0xad``` ```ACCELEROMETER_DEBUG_READ CHIP=adxl355 REG=0x01 -> 0x1d``` ```ACCELEROMETER_DEBUG_READ CHIP=adxl355 REG=0x02 -> 0xed``` ```ACCELEROMETER_QUERY CHIP=adxl355``` returns live XYZ values ```ACCELEROMETER_MEASURE``` start/stop generates CSV data (/tmp/adxl355-smoketest.csv) ## Notes This series follows existing accelerometer bulk-sensor architecture and command conventions. The standby readback quirk handling is intentionally narrow (only REG_POWER_CTL, only standby-bit mismatch) to avoid weakening register verification behavior. Please let me know if there are any issues/bugs right away. This is my first PR but I hope it's useful and done right :) **Heads-up:** I created the initial driver as a derivative of adxl345 because I only had a 355 on hand and finished proper integration using AI. I tested the features on my Ender 2 Pro and validated everything there.

Have a nice day!

Topic		Replies	Views
No adxl345 measurements found error General Discussion	5	4893	August 10, 2024
Adding adxl345 to printer.cfg fails General Discussion	5	2326	May 18, 2025
ADXL345 inputshaper not working General Discussion	5	849	September 24, 2023
Raspberry Pi Pico + ADXL345: Portable resonance measurement Configs	26	63573	February 25, 2024
ADXL345 Connection Help! General Discussion	30	7133	April 24, 2024

Implement ADXL355 support

Related topics