Ratos v2.0 beta not reconnecting to octopus pro 446 mcu (solved)
Hi
I am using v2.0 beta but it isnt on this version that i have had this problem with i did have it with the alphas as well,whats happening is when i update all the files that need updating Ratos wont reconnect to the octopus pro 446 mcu and in the klippy log i can this error ,
mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/btt-octopus-pro-446: [Errno 2] No such file or directory: '/dev/btt-octopus-pro-446'
so i have to reboot the pi to get things working again why could this be and is there something i could do so it doesnt keep on happening?
Thank you DS
29 Replies
What’s happening exactly? You say you’re loosing connection to your board when you update through mainsail?
Nothing should happen unless klipper is updated.
I always leave klipper update last so yes that is most probably when it happens ,klipper updates the board and then after it's finished it restarts but doesn't connect.
And you get this on 2.0? That's super strange.
Yes I was on the alpha's which was the same
i'm gonna have to pull out my 446 to see if i can reproduce. There was another user who had issues with the bootloader on his regular octopus v1.1 (same chip), he reflashed the bootloader and it solved the problem. Thinking it may be the same thing here.
I can do that ,it wouldn't be a problem
@miklschmidt i am still getting a lot of this again mcu 'mcu': Starting serial connect
mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/btt-octopus-pro-446: [Errno 2] No such file or directory: '/dev/btt-octopus-pro-446'
webhooks client 1964455176: New connection
webhooks client 1964455176: Client info {'program': 'Moonraker', 'version': 'v0.7.1-875-ga40dae2'}
mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/btt-octopus-pro-446: [Errno 2] No such file or directory: '/dev/btt-octopus-pro-446'
mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/btt-octopus-pro-446: [Errno 2] No such file or directory: '/dev/btt-octopus-pro-446'
When does it happen?
Did you get it back up and running and then it broke again, or?
yes i had to change to the 32bit version of Ratos which i did but now it is still doing this again at the moment i have tried a new usb cable but it is going through a powered usb hub because i have a toolboard installed as well and i am using a pi 3 with only one usb port so could that be the problem?
i think ive found the problem it seems when i updated klipper earlier it updated the pi but not the octopus pro,i shall reflash and got from there.
If you didn't remove the V_USB power jumper from both boards, then possibly.
It should have though
In any case it should stilll be available at /dev/btt-octopus-pro-446
jumper removed
im connected at the moment so i shall see how it goes
make sure the boot0 jumper isn't installed on the octopus pro as well:
no thats not installed either
its lost connection again if i put ls /dev/serial/by-id/* terminal it only shows the toolboard /dev/serial/by-id/usb-Klipper_stm32g0b1xx_btt-ebb36-12-if00 and not the octopus?
try
lsusb and post the results
Either it's stuck in DFU mode, or the board fails to boot afterwards.it has been connected but when i try to see in the toolboard is running the right klipper through the configurator it drops connection
I take that back the toolboards not connecting this time
I'm wondering if it's the hub causing the trouble
Yes that's supposed to happen, but it should come back afterwards
looks like it could be
its taking to switching the printer of to switching it back on to get it back
Does sound like some USB shenanigans
Do you have a different hub you can try?
unfortunately not i have just bagged myself a pi 4 so hopefully take that out of the equation
Yeah give that a shot, i haven't tested this with a hub before so i have no idea if there are some issues there, but it wouldn't surprise me
Although, the pi4 usb ports are just a hub as well. so.. 🤷♂️ .. Probably depends on the hub 😄
fingers crossed im going to have more pis that a pie shop lol soon at least i should get the money back if i sell them.
Well i have done a few test cubes and every now again i would get random mcu disconnects which i gather is the toolboard for some strange reason . Do you think its tied to the same problem or something different?
Do you have good strain relief? Like make sure the connector cannot move independent of the board etc?
Yes as far as I know it's tight could the usb wire pick up interference from the 4028 fan cables maybe?
Yeah this looks good to me. I don't think so no, I'm using a shoddy cable myself, 1.5m and have no issues.
How long is this one?
It's a 1m long
Looking at your log it alternates between the mcu and the toolboard, i think it's the hub.
Well I shall hopefully get the pi 4 in the next day or 2 and hopefully it well solve the problem fingers crossed. Thanks for your help much appreciated