Jump to content

CanBus communication time-out possible solution plus question for Linux guru.


mbunjes

Recommended Posts

here's a solution that (at least for me) worked, I experienced no more communication time-out after this mod.

Use WINSCP or similar and open the file "/home/pi/klipper/klippy/mcu.py" 

Find "TRSYNC_TIMEOUT" and change the value from 0.025 to 0.050.

Save and try.

Edited by mbunjes
Link to comment
Share on other sites

  • mbunjes changed the title to CanBus communication time-out possible solution plus question for Linux guru.

To elaborate , this fix seems to make your Klipper install "dirty" and you won't be able to update Klipper through the update manager in Mainsail/Fluidd anymore.

I found a fix for this in the form of a script :

https://github.com/rootiest/zippy-klipper_config/blob/master/scripts/mcu_timing.sh

but...I'm not knowledgeable enough to know how to install and implement this.

Is there a Linux guru here willing to explain how to use this ?

 

Link to comment
Share on other sites

  • 2 weeks later...
On 7/15/2023 at 9:59 PM, mbunjes said:

Is there a Linux guru here willing to explain how to use this ?

I am NOT a guru but to run the script:

Download the script (mcu_timing.sh) to a directory of your choice. I created a scripts directory in my Pi folder (home/pi/scripts)

Then

 

Steps to write and execute a script

Open the terminal.

Go to the directory (home/pi/scripts)  where you downloaded the script.

Make the script executable with command chmod +x mcu_timing.sh

Run the script using ./mcu_timing.sh install       -----> to install the script

Run the script using ./mcu_timing.sh update.    -----> to   restore the original file to update Klipper 

Run the script using ./mcu_timing.sh patch       ----->    to update the klipper repo and modify the new mcu.py file

 

Hope this helps

 

  • Like 1
  • Thanks 1
Link to comment
Share on other sites

I was getting this error as well plus other ones. Turn out to be the /etc/network/interfaces.d/can0 file was set to auto Can0 and needed to be allow-hotplug Can0. My setup is a BTT Manta 8P V1.0 (no Canbus on the motherboard) connected to a BTT U2C Canbus adapter. No errors since I made the changes, the solution was suggested by Tom White on the BTT Official Facebook page. The printer was shutting down after every print plus a bunch of different communication errors. I know this is not your typical setup but if someone has a similar setup this may be a solution because the U2C documentation tells you to use Auto Can0.

 

 

Screenshot 2023-07-24 at 11.39.51 AM.png

Edited by PFarm
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...