Klipper reports: ERROR

General Discussion
1

Basic Information:

Printer Model: Voron 2.4 R2
MCU / Printerboard: Octopus Pro STM32F446
Host / SBC
klippy.log

Fill out above information and in all cases attach your klippy.log file (use zip to compress it, if too big). Pasting your printer.cfg is not needed
Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there

Describe your issue:

… It was fine, until I decided to bring my printer offline to install PT1000 as a chamber thermistor, redo or just upgrade some mods into my printer like adding a piano wire so that the wire won’t jiggle, etc.

I made sure the wires are correctly oriented but oh boy, I’m out of options. Please help
klippy.log (130.7 KB)
moonraker.log (31.0 KB)

2

Hello @Shazklebolt !

You may check another time the CAN connection to the MCU:

serialhdl.error: mcu 'mcu': Unable to connect

Are you sure the metal won’t influence the connection capabilities for the CAN cable?

3

I suspect the issue may be with the controller board, but I may be wrong, as all I did was disconnect my RJ 11 to the CAN cable, and my 3D printer turned off after I turned the host off.

Here are the steps I took:

Are you sure the metal won’t influence the connection capabilities for the CAN cable?

  1. I cleaned up my piano wire attached to the PG7 connector and my SB. It was messy before, so I cut it into the right length and added a clip for support. I am sure it won’t affect the connection capabilities of the CAN cable.
  2. I organised the wires in my Z cable chain, which included the CAN cable, A + B motor wires, and Y-axis cable.
  3. I tightened the belts running through my X carriage, as they were 4 to 6 grooves short.
  4. I performed a gantry deracking.

I did some troubleshooting, and I hope this information is helpful. I disconnected the CAN cable linked to my EBB SB2209 CAN board (RP2040) for my Stealthburner. Then, I entered my PuTTY terminal and entered a command, resulting in an error.

Finding the canbus_uuid for new micro-controllers
~/klippy-env/bin/python ~/klipper/scripts/canbus_query.py can0

Result
biqu@BTT-CB1:~$ ~/klippy-env/bin/python ~/klipper/scripts/canbus_query.py can0
Traceback (most recent call last):
  File "/home/biqu/klipper/scripts/canbus_query.py", line 64, in <module>
    main()
  File "/home/biqu/klipper/scripts/canbus_query.py", line 61, in main
    query_unassigned(canbus_iface)
  File "/home/biqu/klipper/scripts/canbus_query.py", line 20, in query_unassigned
    bus = can.interface.Bus(channel=canbus_iface, can_filters=filters,
  File "/home/biqu/klippy-env/lib/python3.9/site-packages/can/interface.py", line 127, in __new__
    return cls(channel, *args, **kwargs)
  File "/home/biqu/klippy-env/lib/python3.9/site-packages/can/interfaces/socketcan/socketcan.py", line 594, in __init__
    bind_socket(self.socket, channel)
  File "/home/biqu/klippy-env/lib/python3.9/site-packages/can/interfaces/socketcan/socketcan.py", line 459, in bind_socket
    sock.bind((channel,))
OSError: [Errno 19] No such device

Also, I think it should be

biqu@BTT-CB1:~$ ~/klippy-env/bin/python~/klipper/scripts/canbus_query.py can0
Total 0 uuids found

Instead of the above error correct?

I hope this information is useful. Thanks for the reply @EddyMI3D

4

It looks like that the CAN interface on the host side is not working, i.e. Linux is not exposing the can0 interface.
Check against CANBUS - Klipper documentation

5

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.