'Printer is not ready' Error

General Discussion
1

Basic Information:
Printer Model: Sovol SV06+
MCU / Printerboard: Manta E3EZ w/CB2

klippy.log (988.9 KB)
printer (1).cfg (4.7 KB)

This is my first time with anything this deep in programming… so please be gentle. lol

I was able to follow the manuals for the CB2 and the Manta E3EZ and do the following:

Imaged the CB2 firmware onto a fresh SD Card and installed on the CB2.
Found the address of the CB2 on my router.
PuTTY’d into the CB2 and changed things according to the manual.
PuTTY’d into the CB2 to create the firmware for the Manta E3EZ.
WinSCP’d the CB2 to copy the klipper.bin and rename it to firmware.
Put the renamed file onto a fresh SD card and into the Manta.
Starting with the generic Manta.cfg file created a specific Printer.CFG file.
Followed the guidance of the errors and corrected them.

Until I corrected the last error… now I have no guidance and no clue.

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

and if it sits for a bit…

mcu ‘mcu’: Unable to connect
Once the underlying issue is corrected, use the
“FIRMWARE_RESTART” command to reset the firmware, reload the
config, and restart the host software.
Error configuring printer

I have been trying off and on for the past 3 months to get Klipper on this printer. Tried first with Sovols Klipper Screen and that failed shortly after getting it working. Screen went black. I went back to Marlin and started tinkering with the mainboard of the SV06… in an attempt to control the fans. I messed up that board and decided to try Klipper and an upgraded mainboard at the same time. I have since fixed the printer and got it working on Marlin again to rule out anything on the printer itself… steppers, thermistors, and such. This is also my 2nd CB2 as the first one died shortly after startup.

2

Heya,

I think you’re almost there. When I look at your printer.cfg, you have:

[mcu]
# To obtain serial ID, SSH into printer and command: "ls -l /dev/serial/by-id/"
serial: usb-Klipper_stm32g0b1xx_4200190017504D4D36343020-if00
restart_method: command

You didn’t quite get the serial path correct, you need to tell Klipper where to find the device. Could you change the above to:

[mcu]
# To obtain serial ID, SSH into printer and command: "ls -l /dev/serial/by-id/"
serial: /dev/serial/by-id/usb-Klipper_stm32g0b1xx_4200190017504D4D36343020-if00
restart_method: command

As a hint for next time, use DFU for programming the MCU on the Manta card - with that there is no need to copy the firmware.bin file onto a PC and format an SD Card. Everything is done on the Manta and it is much faster and much less error prone.

Just looking over the Manta E3EZ User Manual and the instructions for using DFU are terrible but you can find much better instructions elsewhere.

Let us know how you make out.

2 Likes
3

THANK YOU SO MUCH!
This has been my hurdle for weeks… and you cleared it in moments.

3 Likes
4

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