Klipper & Trigorilla Pro B No connection to the mainboard - 'Printer is not ready' in startup

General Discussion
1

Basic Information:

Printer Model: Anycubic Cobra Plus
MCU / Printerboard: Trigorilla Pro B v1.0.2
Host: Raspberry Pi 4B
klippy.log
klippy(2)(1).log (45.4 KB)

Describe your issue:

Background:
I have an anycubic cobra plus printer in use, running with klipper on a pi 4B. Recently there was a short circuit on the mainboard of the printer. As a replacement I did not get the old mainboard from the cobra plus (trigorilla pro A), but the new one which is also used in the cobra 2 plus (trigorilla pro B).

As a result, Klipper no longer works, of course.

What have I already done?
I have reflashed the firmware on the mainboard with the following settings:

  • Huada Semiconductor HC32F460
  • Serial (PA15 & PA9)
  • 0x010000
  • 168 MHz

I also compared the printer.cfg with the suggested one for the kobra 2 plus and adjusted some pins. I think the only real difference was the pin for the probe, which is now on the pin where the nozzle LED was on the old mainboard. Maybe someone already knows which pin it is now on?

I also had the serial address output again (ls /dev/serial/by-id/*) and checked this in the printer.cfg, but everything fits there too and i have tried diffrent usb cables.

Do i have to change settings in the raspi config because i heard the trigorilla B is not longer working with UART? And how would i do that?

The problem:
When starting the printer and klipper, only the following message appears:

Printer is not ready. The klippy host software is attempting to connect. Please retry in a few moments.

This results in an error when it times out.

The spedific part in the klippy.log:

mcu 'mcu': Starting serial connect
webhooks client 4127822008: New connection
webhooks client 4127822008: Client info {'program': 'Moonraker', 'version': 'v0.8.0-387-gb8ba6c0'}
mcu 'mcu': Timeout on connect
mcu 'mcu': Wait for identify_response
Traceback (most recent call last):
  File "/home/lucad/klipper/klippy/serialhdl.py", line 68, in _get_identify_data
    params = self.send_with_response(msg, 'identify_response')
  File "/home/lucad/klipper/klippy/serialhdl.py", line 262, in send_with_response
    return src.get_response([cmd], self.default_cmd_queue)
  File "/home/lucad/klipper/klippy/serialhdl.py", line 319, in get_response
    self.serial.raw_send_wait_ack(cmds[-1], minclock, reqclock,
  File "/home/lucad/klipper/klippy/serialhdl.py", line 254, in raw_send_wait_ack
    self._error("Serial connection closed")
  File "/home/lucad/klipper/klippy/serialhdl.py", line 61, in _error
    raise error(self.warn_prefix + (msg % params))
serialhdl.error: mcu 'mcu': Serial connection closed

Thanks for your help!

2

Hello @DerGrinch !

Please upload the klippy.log here. Not on a(nother) file server.

Upload

There are frequently access issues.

If too large, please proceed as described in the part of the template you have deleted.

2 Likes
3

Thanks for that hint, i have done it. Can somebody help me with my problem?

4

I am basically getting this exact same error. :frowning: (Same circumstances too)

5

Posting the klippy.log wouldn’t be bad though.

Just telling everyone that one has the same error does not help at all.

1 Like
6

klippy.log (15.5 KB)

7

Just for later readers, you can find the solution here:

Good luck for you.
This topic can be closed

1 Like