'MCU' object has no attribute '_mcu_freq'

Basic Information:

Printer Model: Voron Trident 350 AWD
MCU / Printerboard: Manta MP8 v.2
Host / SBC: BTT CB2
klippy.log:

klippy.log.zip (993.5 KB)

Fill out above information and in all cases attach your klippy.log file (use zip to compress it, if too big). Pasting your printer.cfg is not needed
Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there

Describe your issue:

After updating Klipper from v0.13.0-303-gac6f059c to v0.13.0-320 via KIAUH, when booting the printer I got the error: ‘MCU’ object has no attribute ‘_mcu_freq’. I had to roll back the new version to v0.13.0-303 and everything worked again. All of the printer’s MCUs (Manta MCU and EBBCan MCU) are flashed to v0.13.0-303-gac6f059cb. I would appreciate advice on how to solve this problem.

Your log doesn’t show the error as it doesn’t contain any attempt to run Klippy on version v0.13.0-320. That said, most likely the issue is with one of your 3rd party modifications. Its accessing code it shouldn’t which makes it susceptible to errors when the main software changes.

We had a similar report on klipper discord yesterday. It is the cartographer causing the issue and as of yesterday there was no compatible firmware for it.

Quote from the user: ”Update: The latest upate does not work wit cartho at the moment. had to roll back 6 versions after visiting the cartho discord.”

Unfortunately I cant say which commit that actually is.

1 Like

Hi @AlexTheGreat ,

From the Cartographer Discord:

Yet again breaking changes were pushed to klipper main branch and you will receive the following error

Internal error during connect: 'MCU' object has no attribute '_mcu_freq'

DO. NOT. UPDATE. KLIPPER

(again ..)

if you did

  • Option A: use KIAUH to rollback to the first oct or earlier
  • Option B: use command line like so:
cd ~/klipper/
sudo systemctl stop klipper
git checkout 35aeb78088f2a5c76c1945266e3458e097dc0c69 
sudo systemctl start klipper
2 Likes

My apologies. I replaced the klippy.log file with the one from yesterday.

Hi @AlexTheGreat ,

Cartographer has released a software update that is compatible with the newest Klipper. You can now update Klipper and Cartographer software as usual.

1 Like

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