Update manager in MCU and Canboard

General Discussion
1

Basic Information:

Printer Model: Vcore 3.1
MCU / Printerboard: Octopus Prro
klippy.log

not necesary log…

Describe your issue:

Hi,

I have a theory why I had the problems with this weekend’s Klipper updates.

My theory:

At some point over the weekend, the Fluidd update manager notified me that there was a new version of Klipper.

I gave it an update… but it did NOT update the MCU, it only updated the Canboard (Ebb42), so the version on the Canboard was different from the MCU, that produced the error that prevented me from accessing the printer via the web.

And I had to use the “manual” method that I saw on Voron’s website.

This could be?
If so, is there any way when I update, through Fluidd, to do it in the MCU and the Canboard?
…

2

Actually already answered here: Different versions in update manager / installed

See MCU Protocol error caused by running an older version of the firmware

No (also answered in the link above), but improvements to the MCU flashing are on the roadmap.

1 Like
3

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.