#"ls: cannot access '/dev/serial/by-id; : No such file or directory"

68 messages · Page 1 of 1 (latest)

ashen wind
#

For some odd reason, even after flashing klipper.bin onto my Ender V3 SE, unplugged screen and pi, but I cannot reach the file. Could my klipper.bin be wrong? if so, what would the correct peramaters be?

image.png
#

I may have found the issue, but it doesn't help.

#

The "firmware/klipper.bin" is most likely wrote wrong.

#

I followed all parameters. Is this wrong?

#

based off of:

# 
# V3 SE. To use this config, during "make menuconfig" select the
# STM32F103 with a "28KiB bootloader" and serial (on USART1 PA10/PA9)
# communication.

# If you prefer a direct serial connection, in "make menuconfig"
# select "Enable extra low-level configuration options" and select
# serial (on USART3 PB11/PB10), which is broken out on the 10 pin IDC
# cable used for the LCD module as follows:
# 3: Tx, 4: Rx, 9: GND, 10: VCC

# Flash this firmware by copying "out/klipper.bin" to a SD card and
# turning on the printer with the card inserted. The firmware
# filename must end in ".bin" and must not match the last filename
# that was flashed.

# This also works for the GD32F303 based Creality 4.2.2 board.

# See docs/Config_Reference.md for a description of parameters.```
fluid vigil
#

Im the command you sent you wrote „serrial“ with 2 l

#

Pretty sure thats the issue

ashen wind
ashen wind
fluid vigil
#

Do you have kiauh installed?

ashen wind
fluid vigil
#

Klipper Installation and update helper

#

Pretty helpful for setting up klipper

#

Anyway what mainboard does your printer have?

#

Mine for example runs at a lower baud rate than the standard

ashen wind
#

no idea

#

idk the pinout

fluid vigil
#

Are you using a usb cable thats not just power

#

You need a data one

ashen wind
#

its in the printer

#

usbc

fluid vigil
#

And you are sure that the firmware flashed onto the printer?

ashen wind
#

no.

#

i have the .bin on the sd and all that

#

but idk if its actually on there

fluid vigil
#

Plug in the screen if it is stuck on the loading screen it flashed

ashen wind
#

its on this like

fluid vigil
#

Then it flashed

#

The screen runs its own firmware (usually) and if the printer doesnt communicate with the screen its just stuck on loading

ashen wind
#

how do i fix this

fluid vigil
#

okay write this
„cd“

ashen wind
#

ik coding things

#

dont dumb it down

#

cd goes to a file lcoation

fluid vigil
#

Just do it and try again

ashen wind
#

do what

#

flash

#

it?

fluid vigil
#

No the ls /dev/serial…

ashen wind
fluid vigil
#

One more thing i could think of is add a /* at the end

#

But idk if that makes sense

ashen wind
#

samme issue

fluid vigil
#

Before dev add a /
/dev/…

ashen wind
#

same issue

fluid vigil
#

Show me what you wrote

ashen wind
fluid vigil
#

And add a * at the end if that doesnt work idk

ashen wind
#

bro

#

same issue

#

as i asked, is my klipper.bin wrote wrong

fluid vigil
#

Apparently not

ashen wind
#

btw this is whats supposed to happen

image.png
ashen wind
fluid vigil
ashen wind
#

no clue?

fluid vigil
#

No

ashen wind
#

damnit

#

that was my last hope

fluid vigil
#

In the information about what to set the firmware to it said the extra low level configuration was optional

#

Before that you could also try by-path instead of by-id but i dont think thats it

ashen wind
fluid vigil
#

On the top of the makemenu config thingie there is a low level smth config, maybe disable that