Hello fellow Knowledgable Klipper Enthusiasts,
Thank you for taking the time to read this post and any valuable information that I may receive as a result.
I recently built this printer and until last night i was getting acceptable resulting prints, granted I was still dialing in the calibration setting however that may not be relevant to the issue I am having.
Mid way through a print I got the error MCU cant connect. After the usual bout of frustration and cursing, I set out to address the cause.
I Built the electronic side using an Octopus Pro 1.01 (USB to Can bridge), and an ebb36 v1.2 and for Bed levelling I use BTT Eddy Duo (Communicating through Can).
I started off Checking all wiring as per CAN troubleshooting,
Everything seemed fine so I checked the Klippy log and everything looks fine to me until the loss of communication. Now my knowledge is limited But from my understanding it appears that on the can bus It is only the octopus that is having trouble connecting and the eddy and ebb are starting just fine, This confuses me because I am using the usb can bridge on the octopus board to run the can bus.
I was thinking that my next step would be to reflash and set up the Can Bus again, I wanted to run this by the community and get some input from someone more knowledgeable than myself before I Move forward.
Oh yes I also though this may help someone else in the future that is experiencing the same thing, as i have not seen anyone else have similar issues.
Thank you again for Your time and valuable knowledge, without the people in this community I would still be poking a pile of extrusions and electronics with a stick pretending to build a 3d printer.
Thank you for taking the time to help, it is not the timeout error that I am experiencing. I have encountered the timeout error before, and I was able to correct the issue by changing my bit rate to 128 and switching to Raspbian Lite 32-bit. Please let me know if you see something in my Klippy file that helps you make this conclusion. I am basing my uneducated guess on the little knowledge I have of translating Klippy logs and of course the message I see immediately when Klipper fails. After I put my toolhead back together and try to start Klipper, I will post a screenshot of that message in a minute. I have been checking all the connections and checking resistances on the CAN bus TX/RX in case I missed something.
Thank you for taking the time to help, however, my situation does not seem to be related to the timeout error that I previously experienced. I have already resolved a timeout issue by switching to the Raspbian Lite 32-bit operating system and by changing the bitrate to 128. Please let me know if you see anything in my Klippy file that supports your conclusion. My speculation is based on my limited understanding of Klippy logs and the message I see when Klipper fails. After I reassemble my toolhead and try to start Klipper, I will post a screenshot of the failure message.
As an addendum, I should also mention that I lost communication with my octopus mcu midway through a recent print and have been unable to boot the system due to the inability to connect with said mcu. This is not an intermittent issue. I had a good connection for several days before it completely failed, and I haven’t been able to connect since.