Error message with installing ADXL345 board.
I am getting this error message:
Invalid adxl345 id (got ff vs e5).
This is a known good board I have used before with my SKR Pro 1.1 board
I am now using and Octopus Pro (446) board and I wired it up as per this diagram.
I then used the RatOS configurator to enable ADXL345 as the accelrator board
13 Replies
I found it is really sensitive to wiring. Instead of wiring it using the 3v shown I also wire it with the 5v header instead which helps.
An easy way is to use the 4 twisted pairs in CAT5/6 cable so that each of the high speed lines (CLK, SDO, SDA) are in a separate twisted pair, with a ground wire in each pair. This is how I have wired it: Pair 1 - Orange/White is 5V, Orange CS; Pair 2 - Green/White Ground, Green SDA; Pair 3 - Blue/White Ground, Blue SDO; Pair 4 - Brown/White Ground, Brown CLK
My main concern is whether that diagram is showing the right wiring to the right pins on the Octopus board?
I am using the same wire cable I used for this on my SKR board and it did work OK on that.
yes, it is showing correctly as that is what I used for mine (with the exception of switching the 3v to 5v pin)
Many thanks. Did you have to change anything in Klipper when you changed to the 5v pin
nope
Many thanks for helping.
I will have another shot at it today.
Using the 5V pin now. Still same error.
Now going to play with wiring.
But this wire loom I am using is the same one that worked fine with the SKR Pro 1.2 board so niggling in the back of my mind is that I am doinsg something else wrong.
BTW cat 5/6 and their variants use the twist for common mode rejection ratio and to remove the cross talk between pairs....oh god I hardly remember that stuff.
But by using the other wire in each pair as a ground you are effectively shielding each wire, clever.
It seems that in RatOS 2.1 they are connecting the ADL sensor to the Pi instead of the MCU even for the V-Core 3 where the electronics diagram shows it connected to the MCU rather than the Pi?
that is only for when you need to have multiple ADXLs at once. The default is still to use the mainboard and not the PI
I have just wired it up to the Pi as per the Klipper instructions and wiring using a cat 5 USB cable and it still doesn't work. I have double checked my wiring and I am confident it is good.
https://www.klipper3d.org/Measuring_Resonances.html#installation-instructions
I am still getting
Invalid adxl345 id (got ff vs e5).
Invalid adxl345 id (got ff vs e5).
This is generally indicative of connection problems
(e.g. faulty wiring) or a faulty adxl345 chip.
I have used the RatOS configurator to select that I am using Beacon as the Z proble and an ADXL345 board.
I do have the Beacon one so I guess I have multiple ones.
The Beacon is connected to the Pi (as well) bvia USB.
I am finding it hard to find the instruction on how to do this.
At this stage I just want to get the ADXL345 board working but it would be nice to be able to compare IS results from both of them.
OK I managed to get it working by adding this to printer.cfg overides
[resonance_tester]
accel_chip: adxl345
#Increasing accelerations used for Input Shaper. 75 is stock in Klipper
#accel_per_hz: 50
#probe_points:
#150,100,20 # 300mm printer
[adxl345]
cs_pin: rpi:None
I also had to do this i RatOS.cfg
#[adxl345 controlboard]
#cs_pin: PA15
#spi_bus: spi3
[resonance_tester]
#accel_chip_x: adxl345 controlboard
#accel_chip_y: adxl345 controlboard
I suspect my changes in RatOS.cfg will be overwritten the next time I update RatOS and this is not the right way to go about this.
There must be a more elegant way to do this and also to be able to swap between Beacon resulst and ADXL results?
Also the way I have things operating at the moment realtime abnalysis does not work.
@miklschmidt ? I am not as well versed in 2.1 yet to say what needs to be done
You chose the adxl you want to use in the hardware configurator.
When are you getting this error? All the chips are named, so you need to specify a chip name or you're not querying what you think you're querying 😄
MFBS OP — Today at 05:32 OK I managed to get it working by adding this to printer.cfg overides [resonance_tester] accel_chip: adxl345 #Increasing accelerations used for Input Shaper. 75 is stock in Klipper #accel_per_hz: 50 #probe_points: #150,100,20 # 300mm printer [adxl345] cs_pin: rpi:None I also had to do this i RatOS.cfg #[adxl345 controlboard] #cs_pin: PA15 #spi_bus: spi3 [resonance_tester] #accel_chip_x: adxl345 controlboard #accel_chip_y: adxl345 controlboardNo you're just querying the wrong chip and getting errors for the wrong connection. You don't need any of this, delete it. Querying an accelerometer connected to the spi port of your MCU:
ACCELEROMETER_QUERY CHIP="controlboard"
Querying an accelerometer connected to the Raspberry Pi: ACCELEROMETER_QUERY CHIP="rpi"
Querying an accelerometer connected to the toolboard on T0: ACCELEROMETER_QUERY CHIP="toolboard_t0"
Querying an accelerometer connected to the toolboard on T1: ACCELEROMETER_QUERY CHIP="toolboard_t1"
Querying the accelerometer on the Beacon: ACCELEROMETER_QUERY CHIP="beacon"
ACCELEROMETER_QUERY will always return an error unless you configured a default [adxl345] yourself.
This change was made because people don't read documentation and keeps plugging in USB ADXL's and misconfiguring them overriding the default (which was the MCU connection in 2.0) and getting errors.
See aboveyup, I'm following now
tangent -> I really should finish that vcore 200 and install ratos 2.1 on it
Thanks for some reason I missed the option in the Configurator for the ADXL345 to be connected to the Raspberry.