mcu not connecting
i re wrote my post as it as been deleted ...
i was having problem to connect and flash an octopus v.11 and after much testing with the great help of @Helge Keck (many thx again) to diagnostic the problem it seems that the octopus not responding was a problem of the board.
i reopen the post as i have development on the matter: thinking that the board was bad and waiting for another one i tried to put the pi4 on an ender 3v2 with an v4.2.7 board...
trying to install klipper i runned in some problem: mcu not connecting maybe another bad board i tried a third one and same so maybe the problem came from the pi:
the problem came from when ssh into the pi looking for " ls /dev/serial/by-id/" following the procedure >>> https://www.klipper3d.org/Installation.html
never the pi responded the correct answer but when trying "ls /dev/serial//*" the pi found a connection and when swaping this answer into printer.cfg i go the bord to respond and connect: every thing was running fine.
so my question is how knowing that could we try to make ratos work on the octopus or should i just go and run basic klipper
5 Replies
We don't just delete posts. Your old post is here: https://discord.com/channels/582187371529764864/1100072457886519306/1100072457886519306
never the pi responded the correct answer but when trying "ls /dev/serial//*" the pi found a connection and when swaping this answer into printer.cfg i go the bord to respond and connect: every thing was running fine.that tells us that you didn't install the correct firmware that ratos is expecting
he wasnt able to do the initial flashing on that board
we tried it together afair
sorry didn't find it
i am following right now the klipper procedure to see if it does something different
That won't work
You need to explicitly follow the RatOS instructions
Read what it says in the configurator