Fill out above information andin all cases attach yourklippy.logfile (use zip to compress it, if too big). Pasting yourprinter.cfgis 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.