#Cant connect with MCU

93 messages · Page 1 of 1 (latest)

grim cosmosBOT
#

Ahoi @pine ember!
It looks like you did not provide all the necessary information we need to help you.
Please upload your logfiles and a detailed description of your problem.
For further information see: https://docs.mainsail.xyz/faq/getting-help/discord#provide-information
Note: We only accept .log and .txt files as log files.
This is an automated message

We are glad to help and chat with you on our Community Discord, but if you need help and want the best support possible you should, follow a few simple rules:

tame sparrow
#

Why do you delete your message in the other thread and start a new one?

#

We still need a log, opening a new post, won't change anything on that fact

#

Also this is no Mainsail issue, but Klipper, so please fix your tags.
Mainsail is only a webpage and the message on your screen clearly says, Klipper reports

#

Also this is no error but only some kind of current status message

#

So the information we have is literally the text you wrote.....

pine ember
#

witch log file is needed?

pine ember
tame sparrow
tame sparrow
pine ember
#

i think i found the problem i did not flash the BTT Pico board right

#

i will try reflashing it.

tame sparrow
#

In the log, it says wrong path. So check the apth with ls /dev/serial/by-id

#

If the device wouldn't be flashed there would be some different kind of error

pine ember
#

no i know that i flash it wrong i made a mistake while config the klipper.bin file

#

but it could be that the pi isent dedecting that and it shows this error

pine ember
tame sparrow
#

Yes with ssh

tame sparrow
pine ember
#

yeah sure

pine ember
#

i reflasht the board this time right, but the error message is still there

#

This was the message when i checkt with ls /dev/serial/by-id : usb-Klipper_rp2040_454741505B8CF9DA-if00 usb-STMicroelectronics_STM32F042F6P6_CDC_in_FS_Mode_A03A31434E56-if00

tame sparrow
#

Then change the serial path according to the stm path

#

So it should be:
/dev/serial/by-id/usb-STMicroelec... and so on

pine ember
#

okey and what now

#

again the error message is showing: mcu 'mcu': Unable to connect...

tame sparrow
#

Look in the log

#

Or just send it, if you want help with it

pine ember
#

Klippy?

tame sparrow
#

Yes

pine ember
tame sparrow
#

Did you read my message? I wrote /dev/serial/by-id/usb-STMicroelec... and not /dev/serial/by-id/usb-Klipper...

#

/dev/serial/by-id/usb-STMicroelectronics_STM32F042F6P6_CDC_in_FS_Mode_A03A31434E56-if00

#

That's the correct path

pine ember
#

ou sorry

tame sparrow
#

The path in there isn't even the same as the other one. It's just some random path that you copied from the internet(?)....

pine ember
#

no its from a config file i found on github for voron 0 i was thinking maybe this on will work.

tame sparrow
#

Don't copy random addresses. They won't work 🙈

pine ember
#

yeah i know now ...

#

my first time

#

its still showing: Klipper reports: STARTUP

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

tame sparrow
#

That is no error

#

That message will always pop up

#

It just says that Klipper is starting right now

#

After a while it will show you the correct error

#

If it shows the error (red panel), send a new log

pine ember
#

its loading like 5 min is this normal?

tame sparrow
#

It shouldn't. Did you press some button, or did you let it alone for 5mins now?

pine ember
#

i reloded the page

tame sparrow
#

That shouldn't interfere with it then

#

Just download the log and send it

pine ember
#

shoud i restrt the printer

tame sparrow
#

It cannot communicate correctly

#

Just restart the printer

pine ember
#

oke

#

its still showing this shoud i press the restart button?

tame sparrow
#

You can, but it shouldn't make a difference

#

Press it once and then just wait until it switches to a red error screen

pine ember
#

ou yeah🙈

#

what do i have to do?

tame sparrow
#

It's already red?

pine ember
#

no

tame sparrow
#

Then press the firmware restart once and then just wait

#

If it's red send a log

pine ember
#

nothing happend when i presst the firmware restart button

tame sparrow
#

Then just wait now

#

Could take maybe 10+mins 🤷‍♂️

pine ember
#

oke i wait...

pine ember
#

oke somthing isent right its still in this blue screen?

#

I eating now i will check after i finisht

tame sparrow
#

If it still is on the blue screen after you finished eating, open a ssh session and run following commands and send the output:

cd ~/klipper
git status
git remote -v
pine ember
#

what shoud happen?

tame sparrow
#

What exatly do you mean?

#

The blue panel or the commands?

pine ember
#

the commands?

tame sparrow
#

They should give output

#

And I need that output to check your klipper install

pine ember
tame sparrow
#

And the first one?

#

That's the output of the third command, but I also need the output of the second command. The first command has no output

pine ember
#

what now?

tame sparrow
#

Send a log

pine ember
tame sparrow
#

And then just wait, as I don't know the answer and ask someone

#

Klar, der Fehler im og, zeigt, dass er nicht kommunizieren kann, aber dann sollte er doch wenigstens nicht ewig hängen bleiben

pine ember
#

true

#

would reflashing both boards help?

#

i have reloded the page and now this is showing:

tame sparrow
#

Run systemctl status klipper