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
#Cant connect with MCU
93 messages · Page 1 of 1 (latest)
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.....
witch log file is needed?
i was not sure it was Posted.
klippy.log
Why? Because the bot asked for logs?
yeah i was not sure
i think i found the problem i did not flash the BTT Pico board right
i will try reflashing it.
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
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
where shoud i check that. with ssh?
Yes with ssh
Ofc it can be that. To be sure just run lsusb and maybe disconnect it and run it again. If there was a change after unplugging, then it's at least detected by the system
yeah sure
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
Then change the serial path according to the stm path
So it should be:
/dev/serial/by-id/usb-STMicroelec... and so on
okey and what now
again the error message is showing: mcu 'mcu': Unable to connect...
Klippy?
Yes
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
ou sorry
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(?)....
no its from a config file i found on github for voron 0 i was thinking maybe this on will work.
Don't copy random addresses. They won't work 🙈
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.
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
its loading like 5 min is this normal?
It shouldn't. Did you press some button, or did you let it alone for 5mins now?
i reloded the page
You can, but it shouldn't make a difference
Press it once and then just wait until it switches to a red error screen
It's already red?
no
nothing happend when i presst the firmware restart button
oke i wait...
oke somthing isent right its still in this blue screen?
I eating now i will check after i finisht
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
what shoud happen?
the commands?
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
Send a log
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
true
would reflashing both boards help?
i have reloded the page and now this is showing:
Run systemctl status klipper