Broke my MCU Octopus v1.1 and am trying to get the replacement operating

I did some bad wiring and shorted out the fan ports on my MCU Octopus 1.1 running my Vcore3.1. So I installed a new Octopus 1.1, All cables were disconnected, old MCU removed, all jumpers set to original MCU's settings, new MCU mounted, and then all cables but the fans are hooked up. I power on just the rPi and eventually see "mcu 'mcu': Unable to connect on the klipper touchscreen and on the klipper web page. The final line is "Error configuring printer". This makes sense as the MCU is not powered on. I power on the MCU. Wait a while. Click "Restart" and get: "Klipper reports: ERROR" and "mcu 'mcu': Unable to connect" ... "Error configuring printer" If I click Restart I breifly see the following: This is followed by blue screen reporting: "Klipper reports: STARTUP" and "Please retry in a few minutes" until the screen returns to "Klipper reports: ERROR". Inside the KLIPPER LOG I see this as the last few lines: Extruder max_extrude_ratio=0.266081 mcu 'mcu': Starting serial connect mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/btt-octopus-11: [Errno 2] No such file or directory: '/dev/btt-octopus-11' webhooks client 3040103800: New connection webhooks client 3040103800: Client info {'program': 'Moonraker', 'version': 'v0.8.0-39-g6c7dfe5'} I appears that the rPi and MCU/OctopusV1.1 are not talking. I did remove the jumper from the power jumpers to match the original MCU so it is getting power from the 24V source instead of a USB C. I am using the same USB C to USB C cable to connect them togather. I have made no changes to the rPi. I expect that I need to do an initial firmware update to get the MCU out of its factory "as shipped" state. I expect that I need to get USB connecting between the rPi and MMU to go any further. What is the next step in configuring the rPi and MCU to get them communicating?
No description
No description
9 Replies
blacksmithforlife
Installing RatOS | RatOS
Raspberry Pi Installation
rare-sapphire
rare-sapphire12mo ago
I will start reading that document and following it.
In the meantime I was following other threads and tried: ran "dmesg -w" on the rPi. I get the following when I power on the MCU: [ 2817.384521] usb 1-1.2: USB disconnect, device number 3 [ 2906.012880] usb 1-1.2: new full-speed USB device number 5 using xhci_hcd [ 2906.152720] usb 1-1.2: New USB device found, idVendor=0483, idProduct=5740, bcdDevice= 0.00 [ 2906.152744] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 2906.152763] usb 1-1.2: Product: BIGTREE_OCTOPUS CDC in FS Mode [ 2906.152831] usb 1-1.2: Manufacturer: STMicroelectronics [ 2906.152859] usb 1-1.2: SerialNumber: 203631714E53 [ 2906.157965] cdc_acm 1-1.2:1.0: ttyACM0: USB ACM device
blacksmithforlife
You haven't flashed the MCU. Until you do that it's not going to work
rare-sapphire
rare-sapphire12mo ago
I was following that document when I got into the current situation. My issue following that was that when I open the link " http://RatOS.local/configure?step=1 " I get a web page with left sidebar and top title bar but nothing appearing in the central panel.
No description
rare-sapphire
rare-sapphire12mo ago
Agree. I setup my original MCU two years ago. I can't find the instructions on how to do this now. Please point me in the right direction. I was hoping that magic would happen and Klipper would reattach and flash it automatically. This did not happen.
blacksmithforlife
You are running a old version of Rat-OS then. Upgrade to version 2.0(reflash your pi) Yes, because it can't
rare-sapphire
rare-sapphire12mo ago
I have the working Rat-OS running on the rPi. It reports to be 'RatOS v1.2.4-4-g898b8ae' and claims "UP-TO-DATE". I never notice an update of Rat-OS from V1 to a V2. I assume that there is not an automated upgrade so I will start the adventure of making a new SD card with the newer RatOS V2.
blacksmithforlife
It is a breaking change. You cannot upgrade in place