Eryone ER20 not working

General Discussion
1

Basic Information:

Printer Model: Eryone ER20
MCU / Printerboard: Ery32 mini TMC2209
Host / SBC: HP ThinClient T620 with Debian Linux
klippy.log

klippy.log (108.9 KB)

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:

I cant set up my Klipper. I flashed my printer, connected the client with an usb cable, set up the thinclient and used the printer.cfg file from github for my model. i changed the serial to my current serial and inserted the prompt [include mainsail.cfg]. Everything i tried does not work. i changed the config and checked every detail on the flashing firmware. Everytime it keeps telling me printer is not ready and after some time it changes to mcu : unable to connect. Can someone help me to resolve that issue?**Basic Information:**

- **Printer Model:** Eryone ER20

- **MCU / Printer Board:** Ery32 Mini TMC2209

- **Host / SBC:** HP ThinClient T620 with Debian Linux

I have attached the klippy.log file (108.9 KB) for your reference.

Before proceeding, please check our “Knowledge Base” category first, as most relevant items, including error messages, are covered there.

**Issue Description:**

I’m having trouble setting up my Klipper. I flashed my printer, connected the client using a USB cable, set up the ThinClient, and used the printer.cfg file from GitHub for my model. I changed the serial number to my current serial and included the prompt `[include mainsail.cfg]`.

Despite these attempts, I keep encountering issues. The printer status shows “printer is not ready,” and after some time, it changes to “MCU: unable to connect.” I have thoroughly checked my config and reviewed every detail related to flashing the firmware.

Can someone please help me resolve this issue? Thank you!

2

Hi @L0SB34N0S ,

According to your log:

serialhdl.error: mcu 'mcu': Serial connection closed

This indicates the board didn’t send a response back to Klippy, which is usually a sign of a flashing issue.

Can you please explain how you flashed the firmware to the board?

3

Hey, i have used the original tool for the flash. It’s called FlashTool_STM32.exe. It was on the original SD card and the tool I watched on YouTube. I connected the printer with an usb b to usb a kabel. used the new made firmware for the klipper and started the flash. i also tried flashing with the sd card but that didnt work.

4

How did you find the address?

My thought is your board has a separate USB <> Serial converter. It tells Linux serial port is available but when Klippy looks for the MCU on that port it is not responding.

5

when i have connected the thinclient i searched the serial with the prompt “ls /dev/serial/by-id/*”. the only thing im worried about is that it is the same id like the id from the printer.cfg file from github. it is literaly the exact same, nothing different

6

It is not at all uncommon for the “device_by_id” to be the same. My concern is the MCU has improper firmware but the USB<>Serial is “confusing” things by attaching to the Pi as a device

In Fluidd (system tab) usb shows the converter.

image
image1203×726 40.3 KB

And serial shows the port the converter created.
image
image1179×784 43.8 KB

Mainsail looks like this

image
image1122×814 34.1 KB

and
image
image1102×1069 46.9 KB

You can get the same info via SSH but it’s easier to edit printer.cfg in a WebUI.

IF your board is like this one Linux doesn’t check to see if anything is listening on that port and Klippy launches THEN tries to communicate with the MCU. If Klipper firmware isn’t running (with the correct pin mapping for serial communication) You get the error you are seeing.

609a4b71677b32af0f7df-6ffe-473a-9cfc-5fb224947430
609a4b71677b32af0f7df-6ffe-473a-9cfc-5fb2249474301200×1200 417 KB

Shows a CH340 right next to the USB connector.

TLDR Reflash your firmware. Guide

If it doesn’t connect rebuild the firmware specifying

image
image1801×847 46.7 KB

Diagnostic trick- load Printrun (http://www.pronterface.com/) on a PC and connect to printer and see if it locates Marlin firmware.

7

can you help me to flash with the sd card? i cant figure out how to do that. i dont know how to get the eryone er20 into flash mode. when i plug in the sd card with the new firmware on it, the printer does nothing. the only method that worked for me is flashing with the usb cable.

also i have edited the printer.cfg file on the webui, i also found the path like you showed me on the mainsail site like you. for me it was the same so i do had the prove that it is correct i guess.

8

See edited post above

Flash via USB using tool from

9

Thank you for your help. Now it worked. I gues it was the wrong communication interface all along. The only problem now is my input shaping sensor. I think it is broken. I wanted to calibrate my printer. Everything was coded and connected but when i give the prompt to calibrate the x or y achs it stops and tells me that the chip or the wires are broken. I know have ordered a new one and do hope it will be fixed on monday.

10

Unless you have added one I’m pretty sure your printer doesn’t have an accelerometer.

With a thin client you don’t have GPIO pins typically used to connect an accelerometer.

I use one similar to this:
https://a.co/d/01U0FZOt
(But from AliExpress) for my old bedslinger that I run off a Microsoft Surface.

11

I bought one weeks ago. But know it seems that the accelorator is broken. So i bought a new one.

Thats mine: Amazon.de

12

Have you added it to printer.cfg similar to this?

[mcu btt_adxl345]
serial: /dev/serial/by-id/usb-Klipper_rp2040_btt_acc-if00

[adxl345]
cs_pin: btt_adxl345:gpio9
spi_bus: spi1_gpio8_gpio11_gpio10
#spi_software_sclk_pin: btt_adxl345:gpio10
#spi_software_mosi_pin: btt_adxl345:gpio11
#spi_software_miso_pin: btt_adxl345:gpio8
axes_map: -x,-y,-z

[resonance_tester]
probe_points: 100, 100, 20
accel_chip: adxl345

Klipper isn’t plug and play you have to define a new MCU and tell Klipper where to find it.