Connection Timeout over USB with Anycubic Vyper

General Discussion
1

Basic Information:

Printer Model: Anycubic Vyper
MCU / Printerboard: STM32F103
klippy.log

klippy.log (43.5 KB)

Fill out above information and in all cases attach your klippy.log file. Pasting your printer.cfg is not needed

Describe your issue:

I’m running klippy / mainsail on a x86 laptop that I set up using kiauh.

My printer seems to have flashed correctly according to other threads I’ve listed as I do see it listed under /dev/serial/by-id/ when I connect the usb cable.

However, as you can see in the logs, whenever I try to restart the firmware I get an error:

mcu 'mcu': Timeout on connect
mcu 'mcu': Wait for identify_response
Traceback (most recent call last):
  File "/home/dustin/klipper/klippy/serialhdl.py", line 68, in _get_identify_data
    params = self.send_with_response(msg, 'identify_response')
  File "/home/dustin/klipper/klippy/serialhdl.py", line 259, in send_with_response
    return src.get_response([cmd], self.default_cmd_queue)
  File "/home/dustin/klipper/klippy/serialhdl.py", line 317, in get_response
    cmd_queue)
  File "/home/dustin/klipper/klippy/serialhdl.py", line 251, in raw_send_wait_ack
    self._error("Serial connection closed")
  File "/home/dustin/klipper/klippy/serialhdl.py", line 61, in _error
    raise error(self.warn_prefix + (msg % params))
error: mcu 'mcu': Serial connection closed

So unfortunately I’m not really sure where to go from here.

Thanks so much in advance!

2

What is the mcu/[serial]statement in your printer.cfg file? It might be helpful if you posted that.

I presume that you are connecting via USB, how are you identifying the printer?

3

Hi!

So, to identify the printer, I only have a single printer connected (and only a single usb device connected)

dustin@dustin-XPS-12-9Q33:~/klipper$ ll /dev/serial/by-id/
total 0
drwxr-xr-x 2 root root 60 Oct 19 09:07 ./
drwxr-xr-x 4 root root 80 Oct 19 09:07 ../
lrwxrwxrwx 1 root root 13 Oct 19 09:07 usb-1a86_USB_Serial-if00-port0 -> ../../ttyUSB0

the mcu section of my printer.cfg is:

[mcu]
serial: /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0 
restart_method: command
4

I just figured it out. When I originally created the klipper firmware I had chosen USB as the interface instead of Serial.

It just connected fine!

2 Likes