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.
39 Replies
Does the error go away when you disconnect the adxl?
Post a pic on the backside of the ADXL as well
continuing-cyan•2y 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
I never could get my adxl to work with those Dupont connectors
continuing-cyan•2y ago
I just attached logs in case it comes in handy.
continuing-cyan•2y ago
Why not ? what are you using ?
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
continuing-cyan•2y 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.
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.
continuing-cyan•2y 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 ?
continuing-cyan•2y ago
continuing-cyan•2y ago
@miklschmidt Can this be the problem ?
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
continuing-cyan•2y ago
But thye manual stats that whjen using 5160 Pro than jumpers must be on all of them.
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.
continuing-cyan•2y ago
sounds good, at least we found the issue and hopefully others can avoid.
thank you once again
It's not an issue
At least it shouldn't be
continuing-cyan•2y ago
agreed, its my mistake.
i followed the manual
Oh i think i'm misunderstanding something. What's the mistake?
continuing-cyan•2y ago
And you did this for X/Y right?
continuing-cyan•2y ago
yes
That's not a mistake. That's correct.
continuing-cyan•2y ago
hmm, i think im confused a little, so we use SPI for both X/Y as per the manual using 4 jumpers but make the changes in RatOS ?
Advanced Stepper Configuration | RatOS
RatOS V1.1 introduced modularized stepper and driver configuration, this can be used for more fine grained control of your steppers. In your printer.cfg you might have noticed a section like this:
None of this would cause your board to stop booting.
continuing-cyan•2y ago
continuing-cyan•2y ago
i think i did already configure that.
you did indeed. You did everything correct.
I'd contact BTT
continuing-cyan•2y ago
thank you again, i have now shifted to the Octupus pro, hopefully this time things work out.
I also did contact them but that what they had to say. Therefore I’m over to Octupus pro until bugs get ironed out and things are more stable with this new board.
continuing-cyan•2y ago
Right, i'll have to reproduce it and get a hold of my BTT contact
I'll create an issue, and get to the bottom of it sometime after v2 is released.
quickest-silver•12mo ago
Hey, I just encountered the same issue, I guess you probably didn't have the time to reproduce it @miklschmidt
I've also noticed that there is at least one issue on github for it now: https://github.com/bigtreetech/Manta-M8P/issues/49 Probably this one is similar/the same issue: https://github.com/bigtreetech/Manta-M8P/issues/27 (I think they are probably duplicates, the #27 has a lot more information)
What do you think about it? Do we have to wait for a resolution by bigtreetech or do you think you will be able to take a deeper dive? I want to avoid using workarounds but of course it's not a critical issue so I could try some of the suggested workarounds e.g. using another SPI port with the overrides 😅
GitHub
ADXL on SPI1 will not allow boot · Issue #49 · bigtreetech/Manta-M8P
With ADXL345 connected to SPI1 the board will not boot showing error: mcu 'mcu': unable to connect Massive troubleshooting with Oliver Jean Eifler on the BTT Facebook but no resolution. Lot...
GitHub
Manta M8P Boot Loop on SPI1 with ADXL345 · Issue #27 · bigtreetech/...
Connecting an ADXL345 to SPI1 on my Manta M8P causes the MCU to not boot. It seems like the bootloader is conflicting with some other device on SPI1 on boot. Can anyone confirm if there is any othe...
I haven't had a chance to look into this yet, also i only have a 1.0. There's not much i can do about it other than wait for BTT to say something.
Interesting, I used the adxl attached to the 1.1 following the wiring diagram and it worked. Is that not using SPI1?
It is. Either some folks are miswiring or it's only an issue on some boards.
quickest-silver•12mo ago
Could it be an issue with the connection between the board and the sensor? Which kind of wiring do you use, a network cable or just a ribbon cable? 🤔 Maybe I can try a different one
continuing-cyan•12mo ago
We are “not” mis-wiring, you see I posted multiple images of the connection and it’s correct.
Yes i know, i'm just listing the possibilities.
There are several people in those github threads as well, some of them were miswiring.
Maybe? I wouldn't think that could cause a boot loop though.