ADXL345 Stops working after being connected for a few seconds

API Dump Helper start callback error
...
gcode.CommandError: Invalid adxl345 id (got 0 vs e5).
This is generally indicative of connection problems
(e.g. faulty wiring) or a faulty adxl345 chip.
Invalid adxl345 id (got 0 vs e5).
This is generally indicative of connection problems
(e.g. faulty wiring) or a faulty adxl345 chip.
...
TMC 'stepper_z' reports DRV_STATUS: c0170101 otpw=1(OvertempWarning!) t120=1 cs_actual=23 stealth=1 stst=1
...
b'Got EOF when reading from device'
Timeout with MCU 'adxl' (eventtime=10674.997399)
Transition to shutdown state: Lost communication with MCU 'adxl'

You have errors like above in your log. This indicates some hardware issues:

  • Either multiple ones, i.e. the errors are independent OR
  • Consequential ones: One initial error is dragging other components into an error state, which is possible on faulty SPI buses.

See:

and
https://www.klipper3d.org/Measuring_Resonances.html#wiring
and
https://www.klipper3d.org/Measuring_Resonances.html#checking-the-setup
and
https://www.klipper3d.org/TMC_Drivers.html#tmc-reports-error-ot1overtemperror