Cannot Connect Octopus Pro to Pi
Hi guys, I'm very new to this community and admittedly a little over my head when it comes to this kind of custom 3D printer and I bought it looking to expand my experience and knowledge. I have been stuck trying to connect the Octopus pro to my Raspberry Pi. I keep getting the error mcu 'mcu' : unable to connect. I have tried searching online and through this discord but what works for others doesn't seem to be working for me. I could really use any help I can get. Thanks in advance!
51 Replies
graceful-beigeOP•3y ago
Yes, although I do not know how to SSH into my raspberry pi but I have gone through all the other points
What operating system is the computer you are using to connect to the mainsail interface (ratos.local)?
graceful-beigeOP•3y ago
Windows 11
ok, so open up powershell and type in
ssh pi@<IP ADDRESS>
where <IP ADDRESS> is the ip address of your raspberry piIt should look something like this
graceful-beigeOP•3y ago
sorry if this is a dumb question but how do I get the ip address from the Pi?
nope, not a dumb question. Since you have the web UI working you can grab it form the machine tab
graceful-beigeOP•3y ago
okay i connected but its now asking for password
default password is
raspberry
unless you have changed it
when typing the password it will not show anything. When you are done, just hit entergraceful-beigeOP•3y ago
im in
now do i run the dmesg -w?
ok, so now you can continue with the FAQ
graceful-beigeOP•3y ago
gotcha
I would first run
lsusb
and see if it is connected
so I see
that OpenMoko
is my octopus boardgraceful-beigeOP•3y ago

graceful-beigeOP•3y ago
This is all that shows for me, no OpenMoko
ok, so yeah now you need to unplug the octopus, run
dmseg -w
and while it is running plug your octopus back ingraceful-beigeOP•3y ago
and i did remove the jumper that changed the type c port from power in to data
gotcha
So it immediately spit out a bunch of information but then did nothing as I plugged in the board
so sounds like the octopus isn't even trying to communicate with the PI.
Just to double check, you were able to flash the octopus correctly?
graceful-beigeOP•3y ago
Yes, once i put it back into the PC it changed from the .bin to .cur
and you are sure you selected the correct firmware? We have had users select the wrong one before
graceful-beigeOP•3y ago
Let me double check
looks to be the right one as far as I can tell, would it be safe to re run the compile firmware command and download it again?
I believe so. How long did you wait while the board was being flashed?
graceful-beigeOP•3y ago
I didn't see any indicator of it being finished so left it for 5 minutes or so
was that enough time?
maybe? I was overly cautious and waited 10 minutes
graceful-beigeOP•3y ago
fair enough, I'll try to flash it again and let it sit longer this time
I really appreciate the help by the way, thank you!
So I'm no longer getting the mcu error but it just says
Printer is not ready
The klippy host software is attempting to connect. Please
retry in a few moments.
ok, did you change your printer.cfg file to match your setup?
graceful-beigeOP•3y ago
Yes but I'll double check it now
Yep, it's configured properly
dumb question, you did plug the octopus board back into the pi right?
graceful-beigeOP•3y ago
yes i did lol
I would try
dmesg -w
again and see if it is trying to connectgraceful-beigeOP•3y ago
okay
Same result as last time sadly
Although I did get some undervoltage warnings for some reason
that's not good. How do you have everything powered?
graceful-beigeOP•3y ago
I have it wired directly to the 24V PSU
how do you have the pi powered?
graceful-beigeOP•3y ago
using a seperate USB power supply
can that supply enough amps?
graceful-beigeOP•3y ago
Its 5v 2.4A, that should be enough for the Pi 3 right?
it should be, but if it is throwing low power errors then for some reason your setup is not delivering enough power
graceful-beigeOP•3y ago
fair enough, I'll see if I can find something more powerful
just swapped it for a 3 amp charger
It's still giving me undervoltage warnings
did you change the USB cord from the charger to the pi?
graceful-beigeOP•3y ago
Yes but I'll try another one
you could try powering it via the header pins (that is what I do). I use two 5v pins and 2 ground pins and have those connected to a dedicated psu (though you can use pins from octopus. I believe it even has a raspberry pi header port that is meant for powering it)
graceful-beigeOP•3y ago
Nice, would that effect the issue with connecting to the controller?
maybe? since it is having under voltage issues the PI will turn things off to conserve power and it will just generally cause issues.
graceful-beigeOP•3y ago
Okay, then I'll work on fixing that first
So I forgot I had a Pi 4 and official PSU lying around and that doesn't seem to have the same voltage issues
I re ran the dmesg -w again and tried plugging the board in to no avail
also I replaced the jumper to make the type C port the power in again and once connecting it to power I noticed that a green LED is now lit instead of a red one that was lit while it was wired directly
But i can't seem to find a manual or guide that explains what any of these LEDs mean
What are the chances that the octopus is just dead? because nothing I'm doing seems to be working at all and I can't get any message to show up from dmesg -w
While a long shot I would test
dmesg -w
with another USB device on the pi. Just to rule out that it's the cord or the port on the pigraceful-beigeOP•3y ago
just tried it, it showed up immediately
there's a store near me that has an octopus V1.1 board in stock. I'm going to pick that up tonight and try it out tomorrow
optimistic-gold•3y ago
Hi, did you fix it? a friend of mine has the same issue. MCU printer not connected. seems to have a similar issue
https://discord.com/channels/582187371529764864/1046952693480038500 if they are still having issues, start a new post please
Try manually compiling the firmware instead of using the auto compiled firmware. There is a bug in the auto compile somewhere.
Manual compile generated a different file size firmware file for me and that solved this issue.