VORON Design
Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members!
MCU ERROR AFTER UPDATE
- Thread starter Devis
- Start date
Klipper's latest update was a "major" version including changes to the firmware, so you will need to re-flash all your MCU's per the message you are seeing.
Simply following your EBB guide will fix the EBB,
Your MCU will be your mainboard, depending on what this is will determine on a suitable guide
the RPI uses the linux mcu, so the instructions are here : > https://www.klipper3d.org/RPi_microcontroller.html#building-the-micro-controller-code
Simply following your EBB guide will fix the EBB,
Your MCU will be your mainboard, depending on what this is will determine on a suitable guide
the RPI uses the linux mcu, so the instructions are here : > https://www.klipper3d.org/RPi_microcontroller.html#building-the-micro-controller-code
Klipper lists all MCUs which are not up to date. You will need to update mainly MCUs which have and use accelerometer because of the change in communication protocol from those sensors. In your case it's EBB and Pi. After that, error messages disappear.
Another option is to comment out ADXL section in your config. But that means you will not be able to use accelerometer on those devices.
Another option is to comment out ADXL section in your config. But that means you will not be able to use accelerometer on those devices.
I also had this happen, but the last lines on the error message was what was wrong. I re-flashed everything twice and got the same error message both times when I was done. I didn't notice the mcu ' scanner' portion at first because I was following the MCU Protocol error fixes. It turned out, my Cartographer was set for scanner in my config and I hadn't updated its firmware to be able to use this new setup. I went back and followed the install instructions and came online. might be helpful for anyone else who had this issue.
Attachments
Hello (new guy here), I too had the same issue. With some further tinkering my Error window had now upgraded to (see attached). Is anyone able to explain a fix in laymen's terms? I don't even know what an EBB is... but thank you Maz for trying to help. I wish I was at your level.
In my case Mainsail seems to be talking with Moonraker but Moonraker is not able to communicate with Klipper. My thought was to try reinstall Klipper but no idea how to go about it or where to find a download? In my case I have a Voron 2.4 300mm with tap. Sorry for my ignorance, I was fortunate enough to purchase my Voron from a very gifted mechanical engineer so I am at a start level 0.
In my case Mainsail seems to be talking with Moonraker but Moonraker is not able to communicate with Klipper. My thought was to try reinstall Klipper but no idea how to go about it or where to find a download? In my case I have a Voron 2.4 300mm with tap. Sorry for my ignorance, I was fortunate enough to purchase my Voron from a very gifted mechanical engineer so I am at a start level 0.
Well, the first thing to check is if there is a printer.cfg file at that location. It's needed for basically anything to work. Was this an older install that you just updated? Klipper moved the config file location a while ago.
Hello, yes I do have the printer.cfg file. (it was named with date/time stamp) so I just renamed it back to simply "printer.cfg" , applied and now I'm back to the previous error message that I originally had immediately after trying to install the current updates. See attached for my current error
Well, like @Sanity Agathion said, that is pretty clearly telling us you need to flash the mcu again with updated firmware.
Interesting chain of events (for what it's worth). I actually went back after applying the name change to this particular machine profile which got me the above error. I started looking at some other machine profiles stored in the "Machine" tab. First I changed an old profile (being careful to change the currently applied profile name to something else) and voila, I got control of my Voron back. Unfortunately this profile had several portions missing from the g-code so I looked at some of the more recent profiles. In the end I had went with my most recent profile (about a year old) using the same renaming "trick" but for some reason I had to remove the accelerometer g-code to get rid of the error message (which you can actually see in the above error adxl345). Machine seems to be back to normal but I'll have to chip away at what/why I needed to remove the accelerometer portion of the machine g-code. Either way, thank you for writing back! If I find an easy fix I'll add below. Take care.
5twenty
Well-known member
The file location error is usually fixed by removing the home/pi and replacing it with ~/
Linux doesn't like those "static" calls, or however you want to refer to those links. Try going into a subfolder, and cd'ing to home/pi...you might find it doesn't know where that is as it thinks it is where you currently are, throwing the tilde in there makes it got to the root (for the user).
Start here: https://docs.mainsail.xyz/setup/configuration#virtual-sd-card
The error that this post is actually about has been addressed: it's out of date.
Linux doesn't like those "static" calls, or however you want to refer to those links. Try going into a subfolder, and cd'ing to home/pi...you might find it doesn't know where that is as it thinks it is where you currently are, throwing the tilde in there makes it got to the root (for the user).
Start here: https://docs.mainsail.xyz/setup/configuration#virtual-sd-card
The error that this post is actually about has been addressed: it's out of date.
