Difference between revisions of "Remove A1"

From iagent
Jump to: navigation, search
Line 1: Line 1:
Remove is an accellerometer for doing input shaping with Klipper.
+
Remove is an accelerometer for doing input shaping with Klipper.
 
<div class="res-img">
 
<div class="res-img">
 
[[File:Remove A0 iso.jpg|center]]
 
[[File:Remove A0 iso.jpg|center]]
Line 29: Line 29:
  
 
</pre>
 
</pre>
 +
 +
 +
=== Klipper usage ===
 +
 +
At this time there is an issue with the A1 board where the initialization can fail in Klipper.
 +
 +
If you follow the klipper documentation and run the expected commands you may get the following error:
 +
<pre>
 +
Invalid adxl345 id (got f2 vs e5).
 +
This is generally indicative of connection problems
 +
(e.g. faulty wiring) or a faulty adxl345 chip.
 +
</pre>
 +
 +
This does '''not''' mean your Remove is faulty. Try running the command again, it is a known initialization error, and will go away once the initial message happens. It will happen again next time you restart klipper though, as it re-initializes the ADXL345 again.

Revision as of 10:09, 14 December 2022

Remove is an accelerometer for doing input shaping with Klipper.

Remove A0 iso.jpg

Pinout diagram

Remove pinout.png

Klipper configuration

# The Remove resonance tester mcu
[mcu rp2040]
serial: /dev/ttyACM0
baud: 1500000

[adxl345]
cs_pin: rp2040:gpio5
spi_bus: spi0a

[resonance_tester]
accel_chip: adxl345
probe_points:
    100, 100, 20  # an example

[static_digital_output remove_leds]
pins: rp2040:gpio17, rp2040:gpio18


Klipper usage

At this time there is an issue with the A1 board where the initialization can fail in Klipper.

If you follow the klipper documentation and run the expected commands you may get the following error:

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

This does not mean your Remove is faulty. Try running the command again, it is a known initialization error, and will go away once the initial message happens. It will happen again next time you restart klipper though, as it re-initializes the ADXL345 again.