ADXL345 on software SPI

[hardlock]

@monkeyfist

When you say “SPI0 is busy by 3,5 inch TFT screen and touchscreen.”

This is not true, SPI is a multi device port. You can plug as many devices into it as you like, all you need is individual CS pins. And CS pin can be any pin you like. So you can plug your accelerometer into the same port as what the TFT uses, and just define a separate CS pin.

1. the clipper cannot work with accelerometers that are connected to CS1/CS2/CS3. it’s writen in the documentation.
2. I didn’t find any information how to use CS2 or CS3 on raspberry.

@monkeyfist

Also, why aren’t your connecting the accelerometer into your printers board? Why connect it into the raspberry pi?

There is no free hardSPI on the printer board

@monkeyfist

Why are you defining CS pin as none in the first place? Why not just connect the CS pin? It needs it to start and end the communication, that’s why you would constantly need to ground it and disconnect it.
If this is a linux issue, i would again recommend connecting the accelerometer directly to the printers board, this way you avoid these issues. And can define the CS pin freely.

I wrote about this problem in the second post. Link from it:

ADXL345 Raspberry pi4 multi SPI

On the rpi machines specifying a cs_pin causes confusion. Use cs_pin: rpi:None, as the Linux kernel spi device driver will automatically drive the CS pin associated with the given SPI device. Also, I’ve found that if you did use a config that tried to manually alter the GPIO pin, it can put the machine in a confusing state. Remove any references to GPIO18 from the config and then perform a full hardware reboot of the rpi. Finally, I’ve not tested using SPI1 on the rpi, so I can’t say if it …