Adxl345 issue with Manta8P

Hello all, I finally got my RR up and running and everything works well except whenever I connect the Adxl”as per the diagram” it seems I get errors in Klipper. "mcu 'mcu': Unable to connect" or sometimes "printer not ready". I have tested two different Adel’s and 2 wiring and I’m sure of my connection as I probably checked it out at least a dozen times. So any support would be appreciated.
No description
No description
No description
No description
No description
39 Replies
blacksmithforlife
Does the error go away when you disconnect the adxl?
miklschmidt
miklschmidt2y ago
Post a pic on the backside of the ADXL as well
deep-jade
deep-jade2y ago
Yes it does, here are some images from the backside, I also checked with a multimeter to make sure no short circuit and all cables are fine
No description
No description
blacksmithforlife
I never could get my adxl to work with those Dupont connectors
deep-jade
deep-jade2y ago
I just attached logs in case it comes in handy.
deep-jade
deep-jade2y ago
Why not ? what are you using ?
blacksmithforlife
I directly solder good silicone wire and then just jst-sm connectors to connect the silicone wire to a Ethernet cable that I used because the twisted pairs makes for better connection over distance
deep-jade
deep-jade2y ago
I might give that a try but something tells me this is not my problem here, I’m trying to diagnose the issue otherwise I’ll have to settle for adxl on the RP gpio directly.
miklschmidt
miklschmidt2y ago
I don't think so either, wiring and soldering looks fine. Your manta simply doesn't connect when your ADXL345 is connected. Wiring in the diagram is correct (and confirmed working). So i'm not sure what's going on.
deep-jade
deep-jade2y ago
Thank you, I guess I’m gonna have to ask bigtreetech directly and see what they have to say, otherwise I’m going with RR gpio and also ordered the Octupus pro board. I contacted their customer service and here is their reply incase someone faces the same issue. “Hello, this error is a problem of unable to communicate. Please check your ADXL connection pins are correct, and the firmware configuration of the M8P motherboard. If the pins and configuration are normal, but still can not be connected, it may be a problem with the ADXL module or port.” I doubt it’s an issue with my ADXL since I tested two new ones so it’s probably the port itself. I just bought a new Manta board and again I’m facing the same issue and I think I know the problem, at least that’s what I think, basically I’m using 5160pro for X/Y with external power 48v and I have the jumpers for these two drivers set for SPI mode as per the Manta manual where you short all 4 jumpers and the problem here is that PA6 (MISO) is shared with the adxl connector. So can this be the problem ?
deep-jade
deep-jade2y ago
No description
No description
deep-jade
deep-jade2y ago
@miklschmidt Can this be the problem ?
miklschmidt
miklschmidt2y ago
Yes, but this would be solved by using software_spi (such is the case on the Octopus Pro) And that's what RatOS does, if that wasn't clear There's nothing inherently wrong in running multiple SPI devices on the same bus
deep-jade
deep-jade2y ago
But thye manual stats that whjen using 5160 Pro than jumpers must be on all of them.
miklschmidt
miklschmidt2y ago
Yes Doesn't matter which driver it is, if it needs SPI, the jumpers need to be in the SPI configuration. So 2130, 5160, 5160 Pro etc.
Want results from more Discord servers?
Add your server