MCU Error in Mainsail - cant connect to mcu

I finished up the wifi setup and board firmware installation and now I am trying to proceed to Mainsail. I always get an error "MCU couldnt connect".
No description
44 Replies
Helge Keck
Helge Keck•15mo ago
share your printer.cfg as well please i assume everything is connected to the board?
rising-crimson
rising-crimson•15mo ago
no not yet i only connected the pi at this moment
Helge Keck
Helge Keck•15mo ago
have you told klipper what board you are using?
rising-crimson
rising-crimson•15mo ago
i dont think so i just completed the wifi setup and flashed the board and then i wanted to proceed to the mainsail initial configuration. I havent touched the printer.cfg
Helge Keck
Helge Keck•15mo ago
then you cant connect to the baord, thats totally normal ahh please ssh into the PI
Helge Keck
Helge Keck•15mo ago
like this
No description
Helge Keck
Helge Keck•15mo ago
to this
No description
Helge Keck
Helge Keck•15mo ago
end execute lsusb
Helge Keck
Helge Keck•15mo ago
should look like this
No description
Helge Keck
Helge Keck•15mo ago
then please share a screenshot of it
rising-crimson
rising-crimson•15mo ago
i am using a mac is it the same for me then?
Helge Keck
Helge Keck•15mo ago
yes
rising-crimson
rising-crimson•15mo ago
operation failed do i have to change the IP? if so how do i find out my ip
Helge Keck
Helge Keck•15mo ago
well, you need of course use the IP form your PI
rising-crimson
rising-crimson•15mo ago
right i should have known lol
Helge Keck
Helge Keck•15mo ago
use ssh ratos.local
rising-crimson
rising-crimson•15mo ago
ok it wants me to type in a password
Helge Keck
Helge Keck•15mo ago
raspberry wait ssh pi@ratos.local sorry
rising-crimson
rising-crimson•15mo ago
ahh okay now it worked so now just run lsusb
Helge Keck
Helge Keck•15mo ago
yes
rising-crimson
rising-crimson•15mo ago
alright
rising-crimson
rising-crimson•15mo ago
No description
rising-crimson
rising-crimson•15mo ago
now it looks like this
Helge Keck
Helge Keck•15mo ago
good now execute ls /dev/serial/by-id/* and share the output
rising-crimson
rising-crimson•15mo ago
/dev/serial/by-id/usb-Klipper_stm32f446xx_btt-octopus-11-if00 thats the output
Helge Keck
Helge Keck•15mo ago
very good then all is ok
rising-crimson
rising-crimson•15mo ago
okay thanks so much
Helge Keck
Helge Keck•15mo ago
i would isntall everything now and then make the config
rising-crimson
rising-crimson•15mo ago
okay so now connect all the wires and everything and then config right?
Helge Keck
Helge Keck•15mo ago
yes
rising-crimson
rising-crimson•15mo ago
okay thanks! It still gives me the same error i didnt check yesterday if it actually works now I did wire up everything now
miklschmidt
miklschmidt•15mo ago
Then you have wiring problems 🙂 Most common is the endstops
Steven Machado
Steven Machado•14mo ago
Just for my own curiosity.. on v-core 3.1.. wiring matches and connected to diag 0 & 1 where are the endstops in ratOS defined?
miklschmidt
miklschmidt•14mo ago
Should be pretty obvious from the includes.. pins are in the board config. Why?
Steven Machado
Steven Machado•14mo ago
Well. same old story really (and I found the aliases for the octo 1.1 to confirm) endstops are always triggered. Ohm switches, wires, I even purchased a new board. I find myself becoming a bit frustrated with the thing. Im sure I'll figure it out eventually just how much damage I do before then will be the question... well ,next will be replacing the switches themselves
miklschmidt
miklschmidt•14mo ago
That's a wiring issue. Unless you're not using the RR endstops?
Steven Machado
Steven Machado•14mo ago
Endstops are RR 400 kit stock. Wiring is verified problem remains. Board changed and problem remains the only variable left are the endstops themselves
Helge Keck
Helge Keck•14mo ago
No description
Steven Machado
Steven Machado•14mo ago
Yea got this.. I replaced the endstops. Today I pressed the updates klipper etc. and now for some reason my Pi takes off and chokes. Yes, I can put a sink on it, or a fan on it.. but the temps climb almost uncontrolably. Im thinking of just going back ot a previous image and then ignoring updates LOL
VanOfHoogen
VanOfHoogen•14mo ago
Sorry to use this error to request help on an edge case where I am having the same issue
VanOfHoogen
VanOfHoogen•14mo ago
No description
VanOfHoogen
VanOfHoogen•14mo ago
This is the screen that I am getting
No description
blacksmithforlife
blacksmithforlife•14mo ago
please create your own post