Mcu Unable to connect and Printer is not ready, klippy host is attempting to connect, Ender 3 S1 Pro, Follow up to previous post

General Discussion
1

Basic Information:

Printer Model: Ender3 S1 Pro
MCU / Printerboard: Rasp pi 3, USB C into front port
Host / SBC Klipper/Mainsail
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:

…

I’ve tried all three options for the MCU in the config file. I’ve changed USB. I’ve power cycled everything. I’m also kind of an idiot but I’m like right at the doorstep getting this thing to run and I keep getting beat at the last point.

Pasted from another board

Alright, 3 months after making a bunch of progress then getting stuck, I’m trying to piece together where I was. I followed this guide that was suggested, https://3dprintbeginner.com/install-klipper-on-ender-3-s1-pro/ . Everything is going well. The printer is definitely flashed, as the screen no longer works. Good. I copied the config files, and I can log into Mainsail fine. Good.

I’m no longer getting the red MCU unable to connect business. Extra good. EDIT* This is false, after disappearing on restart, it comes back to the Klipper reports MCU Unable to connect. I’ve tried all three device paths in the mcu config line

But now, i keep getting the above mentioned error, Printer is not ready. The klippy host software is attempting to connect.

Not even sure which log files would be helpful at this point, so i’ll fire off some stuff

STM32F401 chip

USB C on front panel connected

Raspberry pi 3

Getting the Moonraker can’t connect to Klipper issue. Please let me know what other info i can put up.

2

Please attach it to your next post.

3

klippy (1).log (455.1 KB)

sorry about that, thought I included it. Here you go

4

Your klippy.log shows you have a valid serial port defined but messages to that port get no reply

Probably a bad firmware flash on the MCU.

Long shot - you’ve pointed klippy at a valid port but not your printer MCU.

5

What are some proposed solutions for that? Can I just reflash the firmware with the same SD card? The flash seems to work ok, as the screen does not load (as it said would happen in the instructions). As far as the mcu, I’ve cycled through all three options and they all don’t really communicate.

6

I would recompile the firmware after double checking settings.

# This file contains pin mappings for the stock 2022 Creality Ender 3
# S1 Plus. To use this config check the STM32 Chip on the Mainboard,
# during "make menuconfig" select accordingly either the
# STM32F103 with "28KiB bootloader" or the STM32F401 with
# "64KiB bootloader" and serial (on USART1 PA10/PA9) for both.
7

1st I would choose a shorter topic name :wink:

Regarding the printer and Klipper. Is the hardware of your Ender 3 S1 Pro not modified?

This is a very good guide.
Only I would choose the KIAUH way Installation - Klipper documentation. Much more comfortable!
All you need is this:

Klipper-Ender-3-S1-Pro-Config
Klipper-Ender-3-S1-Pro-Config567×449 19.1 KB

from your guide
and
https://3dprintbeginner.com/wp-content/uploads/2022/05/Ender-3-S1-Pro-3DPrintBeginner-Klipper-Config.zip.
Just follow the GitHub - dw-0/kiauh: Klipper Installation And Update Helper instructions and do it. Good luck.

Regarding your klippy.log error
line 279: mcu ‘mcu’: Unable to open serial port: [Errno 2] could not open port /dev/serial/by-id/: [Errno 2] No such file or directory: ‘/dev/serial/by-id/’
This setting is wrong in your current printer.cfg
line 261: serial = /dev/serial/by-id/

See How-To Trouble-Shoot how to fix that.

3 Likes
8

If you look “later” in the log the serial address is “correct” but fails to return data.

9

Ok, which line in the log?

10

Line 4777 has the correct serial/by-id
Then 4898 shows “timeout” instead of “No such file or directory”

1 Like
11

@strikingtwice

“serial = /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0”

Looks good.

“mcu ‘mcu’: Timeout on connect”

See https://klipper.discourse.group/t/mcu-serial-connection-closed-timeout-on-connect-wait-for-identify-response how to fix that.

Do you have a fresh klippy.log? If yes, please post it here.

12

Thanks all.

@hcet14 Yes, other than the other configurations, I actually did do everything through kiauh. Good point about the topic name, I was spiraling and just dumping my feelings into the title line.

The hardware is not modified. It is the stock Ender 3 S1 Pro to my knowledge. I will look into your timeout on connect tip and see if it helps.

@cardoc , Thank you for helping clarify some of this stuff.

13

dmesg.txt (34.9 KB)

klippy.log (9.8 KB)

@hcet14 I checked the mcu timeout page you sent me, i kinda have no idea what i’m reading, but the one thing that it appeared i could do was run dmesg, and I included that here along with a fresh klippy log.

1 Like
14

Ok, but I warn you. I’m not that good with Linux.

I have an idea, what might go wrong. But I’m not sure!

Any help analyzing the “dmesg.txt” from strikingtwice is very appreciated!

dmesg.txt

  • Line 450: [Jan21 23:37] WARN::dwc_otg_hcd_urb_dequeue:639: Timed out waiting for FSM NP transfer to complete on 3

Sorry I’m also just a www (no AI) searcher.

Any help here is very, very appreciated :anxious_face_with_sweat:!

See also https://klipper.discourse.group/t/klipper-architecture-ecosystem.

I don’t think RPi3 has an USB-C port. Do you have a 64bit OS on your RPi?

15

Sorry I meant that the usb C cable was in the front of the Ender 3, regular usb from rasp pi. I don’t know if it’s a 64bit os, how would I check that?

16

Just do a quick www search for “linux system info” or something similar. There are many commands to get that info from a Linux terminal.