EBB
EBB copied to clipboard
bigtreetech
Communication timeout during homing probe
Did you find a solution in the meantime? I ran into ai similar timeout but with x homing.
Looking at when your issue was opened i don't believe BTT is very active here. sigh
I had the same issue and ended up increasing my CAN baud rate to 500000. I still have the error once in a while but it is far more stable. I was also not able to run an resonance test successfully before increasing the rate.
I had the same issue and ended up increasing my CAN baud rate to 500000. I still have the error once in a while but it is far more stable. I was also not able to run an resonance test successfully before increasing the rate.
Hi, I have the same issue but it’s happening quite frequently! I’m at 500,000 baud right now & not able to complete a single z-tilt! Which version do you have on the U2C? The one on BTT github?
I had the same issue and ended up increasing my CAN baud rate to 500000. I still have the error once in a while but it is far more stable. I was also not able to run an resonance test successfully before increasing the rate.
Hi, I have the same issue but it’s happening quite frequently! I’m at 500,000 baud right now & not able to complete a single z-tilt!
Which version do you have on the U2C? The one on BTT github?
I believe I said that wrong. I set it to 500000 in the device tree setup but then ran my boards at 250000. I reflashed my firmware today at 500000 and the issue came back.
I am also just running a generic CAN to SPI breakout board.
I'm not really sure what the solution was for me but this is what i did:
- Complete fresh install
- Orange Pi 3 lts instead of rpi zero
- Other higher quality usb cables
Be sure to watch this this video . The can software mentioned in the btt manual is crap and installation is a pain in the ass. The can software mentioned in the video didn't used to support the Gb0 chip but now it should support it.
I have this error when my bed is too out of level. Try doing a manual level first.
Also give the z min travel -5. Sorry don't have exact parameter name on phone.
I could be wrong and am mixing it up with probe failed to deploy error.
I ended up following this reply here and I have not had another timeout error while trying to home.
Basically changing TRSYNC_TIMEOUT value in “/home/pi/klipper/klippy/mcu.py” file from 0.025 to 0.050
I got this and it got worse over time. I was tearing my hair out. I kept getting undervoltage errors on my PI which was causing it to throttle. I was using a tablet plugged into one of the USB ports on the PI as a screen. Unplugging that seems to have fixed it. I've ordered a better power supply, hopefully that will fix it.
I ended up following this reply here and I have not had another timeout error while trying to home.
Basically changing TRSYNC_TIMEOUT value in “/home/pi/klipper/klippy/mcu.py” file from 0.025 to 0.050
Tried that, didnt help for me.
My problem was bad plug conection. If you wiggle it and the light goes off...
On Mon, Feb 6, 2023, 3:43 PM Emerson Corder @.***> wrote:
I ended up following this reply here https://klipper.discourse.group/t/canbus-communication-timeout-while-homing-z/3741/3 and I have not had another timeout error while trying to home.
Basically changing TRSYNC_TIMEOUT value in “/home/pi/klipper/klippy/mcu.py” file from 0.025 to 0.050
Tried that, didnt help for me.
— Reply to this email directly, view it on GitHub https://github.com/bigtreetech/EBB/issues/3#issuecomment-1419953223, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGZGGVJORKO5V77HLXYKFLTWWGEANANCNFSM5XVMHOHQ . You are receiving this because you commented.Message ID: @.***>
I ended up following this reply here and I have not had another timeout error while trying to home.
Basically changing TRSYNC_TIMEOUT value in “/home/pi/klipper/klippy/mcu.py” file from 0.025 to 0.050
This seems to have resolved my issue. Thank you for posting about it. :)
Edit: literally right after posting this, it happened again :(
I had the same today. But I am not using can. I Am using just the usb connection. My problem was also a bad connection! A little bit of hot glue on the dupont plug resolved the problem
