Rat Rig Community [Unofficial]•2mo ago

RatOS/MCU/Klipper failure after update (Octopus Pro 446)

I have a BTT Octopus Pro 446, VC3.1, 400mm. Just did an "update all", which never goes well but usually I get through it. Not this time.

MCU Protocol error

This is frequently caused by running an older version of the
firmware on the MCU(s). Fix by recompiling and flashing the
firmware.

Your Klipper version is: v0.12.0-267-g12cd1d9e-dirty
MCU(s) which should be updated:
mcu: Current version v0.11.0-200-g7511151a
Up-to-date MCU(s):
<none>

Once the underlying issue is corrected, use the "RESTART"
command to reload the config and restart the host software.

mcu 'mcu': Command format mismatch: query_adxl345 oid=%c rest_ticks=%u vs query_adxl345 oid=%c clock=%u rest_ticks=%u

MCU Protocol error

This is frequently caused by running an older version of the
firmware on the MCU(s). Fix by recompiling and flashing the
firmware.

Your Klipper version is: v0.12.0-267-g12cd1d9e-dirty
MCU(s) which should be updated:
mcu: Current version v0.11.0-200-g7511151a
Up-to-date MCU(s):
<none>

Once the underlying issue is corrected, use the "RESTART"
command to reload the config and restart the host software.

mcu 'mcu': Command format mismatch: query_adxl345 oid=%c rest_ticks=%u vs query_adxl345 oid=%c clock=%u rest_ticks=%u

Annoyingly, there seems to be acknowledgement of this issue on the the RatOS 446 config page, but the link there doesn't work. It looks to be a link back to RatOS/mainsail, which just takes me back to the error.
There is a directory in my machine tab for firmware_binaries but it's looks last updated May 18, 2023. So that's probably not the binary I need to flash. I feel like I should just be able to download a new binary onto SD card and flash the Octopus, but I'm not clear where to get it.

13 Replies

miklschmidt•2mo ago

It prolly doesn't go well because you've done hard recovery and killed the RatOS automation (moonraker deletes the repository when you do that). Here's a fix;

ssh pi@ratos.local
sudo ~/printer_data/config/RatOS/scripts/ratos-update.sh

ssh pi@ratos.local
sudo ~/printer_data/config/RatOS/scripts/ratos-update.sh

if that goes well, you can do this to run the automatic flashing procedure:

sudo ~/printer_data/config/RatOS/scripts/klipper-mcu-update.sh

sudo ~/printer_data/config/RatOS/scripts/klipper-mcu-update.sh

etotheipi•2mo ago

pi@ptah:~ $ sudo ~/printer_data/config/RatOS/scripts/ratos-update.sh
Updating RatOS device symlinks..

###### Updating whitelisted commands

###### Updating service permissions

###### Installing beacon module...
beacon: beacon already installed, skipping...

###### Installing git hooks

###### Registering klippy extension 'ratos_homing_extension' with the RatOS Configurator...
curl: (7) Failed to connect to localhost port 3000: Connection refused
ERROR: Failed to register ratos_homing_extension. Is the RatOS configurator running?

pi@ptah:~ $ sudo ~/printer_data/config/RatOS/scripts/ratos-update.sh
Updating RatOS device symlinks..

###### Updating whitelisted commands

###### Updating service permissions

###### Installing beacon module...
beacon: beacon already installed, skipping...

###### Installing git hooks

###### Registering klippy extension 'ratos_homing_extension' with the RatOS Configurator...
curl: (7) Failed to connect to localhost port 3000: Connection refused
ERROR: Failed to register ratos_homing_extension. Is the RatOS configurator running?

What is the "configurator"?

miklschmidt•2mo ago

It'll now flash it automatically next time you update klipper, unless your run hard recovery again. Ah yes you killed the configurator too (hard recovery again), another step:

sudo ~/ratos-configurator/scripts/update.sh
sudo systemctl restart ratos-configurator

sudo ~/ratos-configurator/scripts/update.sh
sudo systemctl restart ratos-configurator

etotheipi•2mo ago

So what did I do wrong? Or what should I have done? (before I did the update all)

miklschmidt•2mo ago

after that ☝️ run the two others

etotheipi•2mo ago

...

###### Updating whitelisted commands
/home/pi/ratos-configurator /home/pi
ERROR: This version of pnpm requires at least Node.js v18.12
The current version of Node.js is v16.20.2
Visit https://r.pnpm.io/comp to see the list of past pnpm versions with respective Node.js version support.

...

###### Updating whitelisted commands
/home/pi/ratos-configurator /home/pi
ERROR: This version of pnpm requires at least Node.js v18.12
The current version of Node.js is v16.20.2
Visit https://r.pnpm.io/comp to see the list of past pnpm versions with respective Node.js version support.

Looks like I gotta get the latest node.

miklschmidt•2mo ago

Moonraker has had bugs which made it list repositories as corrupted for arbitrary unrelated reasons, if the wind blew in the wrong direction it would mark the repository as corrupted. When that happens you can't update unless you choose between soft or hard recovery in the mainsail update manager. Hard recovery screws everything over as it deletes everything. This kind of looks like you're on the wrong branch... Another moonraker bug that was fixed several months ago caused it to check out the wrong branch when you ran hard recovery. I'm assuming you're running an older RAtOS v2.0 install

etotheipi•2mo ago

Heh, sorry. It's been a long time since I did anythign with this RatOS Should I just copy out my printer.cfg and reflash the pi? I feel like I should get a fresh start at this point, haha

miklschmidt•2mo ago

Here's the fix for all of it combined

cd ~/ratos-configurator
git checkout v2.x-deployment
sudo ~/ratos-configurator/scripts/update.sh
sudo systemctl restart ratos-configurator
sudo ~/printer_data/config/RatOS/scripts/ratos-update.sh

cd ~/ratos-configurator
git checkout v2.x-deployment
sudo ~/ratos-configurator/scripts/update.sh
sudo systemctl restart ratos-configurator
sudo ~/printer_data/config/RatOS/scripts/ratos-update.sh

miklschmidt•2mo ago

That's definitely an option. I would recommend you go with RatOS 2.1-RC1 in that case: https://github.com/Rat-OS/RatOS/releases/tag/v2.1.0-RC1

GitHub

Release RatOS-v2.1.0-RC1 · Rat-OS/RatOS

Documentation is underway, 2.1.0-RC1 is marked as a pre-release until it's ready. Update all packages after connecting RatOS to your wifi network. If you like the project and want to see it con...

etotheipi•2mo ago

Okay, let me try your recommendation first I was just about to upgrade node Yeah, it says I was already on v2.x-deployment branch Okay ,I did some linux guru magic to upgrade node.js, and all those scripts ran successfully. Still see an error in the UI. Should I do a "firmware restart?" I'm afriad to touch anything now 😅 Okay, so I did all that, but nothing changed, even after firmware reset. Exact same error message. Is it possible to just download the latest firmware and flash manually? I'd like to try that before doing a full reset of everything. I guess it would have to be a version of the firmware compiled by RatOS, right? I still only have one from mid-2023 in that folder

miklschmidt•2mo ago

Sorry didn't see this till now, sudo ~/printer_data/config/RatOS/scripts/klipper-mcu-update.sh flashes connected boards. If that throws errors paste it here Yeah it seems like you've gotten yourself a pnpm version that requires node 18, only v2.1.x is setup up for that, so that's why i was confused Shit, v2.x automatically updates pnpm as well.. oh well.. I'll make sure node is updated as well then, i guess. done

etotheipi•2mo ago

No worries. I did end up doing a full flash. NBD. I'm having fun playing with the new version.

Gaming

Programming

RatOS/MCU/Klipper failure after update (Octopus Pro 446)