I am curious when it comes to the flashing of your MCU, should the version flashed to the Mcu match the version that is currently on the host?
Why I ask is when I run the script through ssh it says it has been flashed, but when I refresh web browser my versions do not match?
I apologize but since my other issues and a comment another member that always offers help, I figured maybe he is right I don’t know my machines as well as I thought lol… so with that being said I’m trying to be more thorough.
Thanks everyone for all the help being almost 50 I’ll get this figured out!!!
On a new installation, you’ll have the same version number on both the host and the MCU because they’re going to be from the same version of the source tree. After that, you can usually do updates of the host code without having to update the MCU code, at which point you’ll have different version numbers. Sometimes there’s a change that requires updating the MCU code, and Klipper will usually produce an error to notify you this is the case.
Thank you theophile, and you were the one I was referring too haha, I was just concerned as I noticed my klipper is the 0.12.191 on host and Mcu is 0.10.291.
“Sometimes”, not always. I’ve had a couple of instances over the years where I was having some strange behaviour and, as a last resort, I reflashed the main and toolhead controller boards to be at the same level as the host and the instabilities/issues went away.
I would suggest that you at least always have the same high level version (ie “0.12” right now) on both the host and the controller board(s).
Thanks for your reply, I was just thinking maybe that remote possibility like you explained could be happening, but also being a possibility that when I was attempting to put kamp etc I messed something up. Who knows I have an extra but pi that perfect excuse to redo everything with the one machine and see what transpires
Thank you!! Tonight thanks to your message I was like what the heck I’ll start doing it…. We’ll not far into it I found some issues, some how I mixed my heat break fan and board fans up so they were plugged in the wrong slots while they did start up, they weren’t running as they should. The good news is I was able to have the Mcu firmware now matching for the current.
YAY now let’s see what other rookie dumb things I have done haha
To expand what @theophile said:
It is even not only version depended - it is also feature dependend.
If klipper is not using a feature that got a mcu protocol change since it got flashed it will not error out.
As an example let use your version
If you configure a resonance tester sensor on you mainboard mcu klipper would error out since around v0.12.0-75 the resonance sensors part of the mcu protocol got changes. As soon as you comment out your sensor in your printer.cfg it will no longer error out since the feature is no longer used.
Of course you should update your mcu in case you get a protocol mismatch error and not commenting out the feature ^^
Also it is good to subscribe to the Announcements channel since every major update gets posted there and also specifi stuff like this example:
I have re flashed, re installed klipper on bother the Mcu and host btt pi, already there is a huge difference the cr touch is reporting a whole different picture now when I run a bed mesh and that’s without even touching anything mechanical… so with that being said I’m pointed more in the direction that either while installing kamp I had messed something up and now it’s, or with the Mcu and host being so far apart and me adding things it cause a problem…. Most likely just a remote incident that was unique to my situation, but having gone through what I have I can offer advice if someone else happens to stumble upon this same issue.
The Mcu for this machine is just a mini e3v3, I didn’t think the ended 3 really needed a manta mp4. But if your not familiar the mini e3s are pretty small but good and powerful for what they are, much better then a stock creakily board in my opinion.