Can someone please help me I am trying to get my adxl345 accelerometer to work with my raspberry pi 3b+ and no matter what I try I still get Invalid adxl345 id (got 0 vs e5). I have tried 3 different sensors and 3 different types of wire. I have tried cat5 twisted pair and regular single strand wire and nothing works. I am long and cant figure this out I have searched and searched please help
Ideal thing would be to put the cable’s shield on protective earth. I’m running a 75cm Cat5E without this and it works reliably (self crimped Dupont pins).
I tried a lot of cables before and all failed but now it is really working good. There are a lot of similar reports and all boil down to cable quality.
I have one on my V2.4 that came from Magicphoenix. It has a 4B2K 3.3 V regulator on board, so it will not run from 3.3 V. I use 5 V (pin 2 or 4 from Raspberry Pi header) and it works fine. I’m using a shielded cable, but not twisted pair about 1 m long.
I tried 3.3v and 5v and still nothing, I also tried single wires and cat6 cable and still had no luck I ordered a raspberry pi Pico today figured I’d give that a shot maybe it’s because I am using a raspberry pi 3b+ I really don’t know
Interesting. I have around 6 or 7 different boards. With and without voltage regulator. Have not seen any that would not run with 3.3V.
Yes they do have voltage regulator but this only allows them to run of 5V as well. You can see a short discussion on them in the link I posted above.
Be especially careful with models that have voltage regulators and level shifters. If supplied with 5V they may fry your board.
The ADXL board I have only has one connection for power. There is no way to provide 3.3 V directly. I don’t know of any 3.3 V regulators that will work with 0 V headroom. The one in the image you liked looks like it has connection points at both the regulator input (5 V) and output (3.3 V).
So i decided to try out the MPU-9250 sensor and now im getting this error and klipper restarts
MCU ‘rpi’ shutdown: Unable write i2c device
Once the underlying issue is corrected, use the
“FIRMWARE_RESTART” command to reset the firmware, reload the
config, and restart the host software.
Printer is shutdown
Yup I have done both of those things tried 2 different wires one long wire and one really short wire, also i enabled i2c in raspberry config and made sure to set the baud rate 400000… Ah why is this being so difficult i feel like this should be a super simple setup.