Printer Model: ender 6
MCU / Printerboard: manta m4p
klippy.log
printercfg.zip (304.7 KB)
printercfg.zip (304.7 KB)
Got an error after updating that has me puzzled.
It says i have wrong klipper mcu firmware
Says my current is v0.12.0-125
And should be
V0.10.0-508
Would this not be an old firmware its saying i should have?.
Or maybe i have misread something? Lol confused its been so long since i had an issue.
printercfg.zip (304.7 KB)
printercfg.zip (304.7 KB)
Ok so commenting out adxl345 and resonance tester has allowed me control of my printer again, but what do i have to do now for my resonance testing?
Your log is showing that you have OLD Firmware in your MCU v0.10.0-508-g1636a975
But your klipper probably is the latest v0.12.0-16-g0ccf5f8e-dirty
it’s pretty big difference.
Just try to build and flash fresh firmware to your MCU.
I have been trying to so but all the instructions i have followed have led to dead ends…not only do the instructions lack any common sense, they use ssh clients that do match any options i have on putty(no mention of what client they are using),and then its all directed to “pi” including that of instructions offered by the manufacturer of my board. I am completely at a loss. But they real confusing part is the printer directly beside the problem printer is up to date with the exact same config but it has none of these issues?
So please if you are going to recommend re flashing, could you also point one in the proper direction please.
The biggest issue is i have run all the make menuconfig but have no where that the bin file seems to be? I have spent almost an hour no looking for these bin files that were supposed to have been created.
What is hosting your klipper “host” (not MCU)?
As I understand M4p manta - it’s just a 3D printer controller which will drive stepper and other hardware - in klipper word we call this a MCU (Micro Controller Unit), when you flash it with klipper firmware - it will become just execution device, it don’t store any configs, setting, etc…
MCU is just dumb device which is executing actions and communicate with klipper host thru serial connection.
Then there is another part of system where klipper main code is working, usually it can be any hardware with Linux OS system, often it’s Raspbery PI but can be any pc - in klipper word we call it “Host”, its job is to store configuration, calculating paths, driving MCUs, etc…
In your case with Manta M4P board - Your “host” can live inside of additional module for Manta M4P board and it’s called “CB1 module” - it’s a kind of Raspbery PI replacement, it should contain Linux OS and klipper “host”
Good overview of a system and all it’s parts you can pick here: Klipper Architecture / Ecosystem
So when you read something about SSH - it’s about accessing “host” system where usually klipper sources are located, where you are Building firmwares, etc…
As that host have direct connection to MCU - it can push prepared Firmware to MCU (if it’s possible), or can prepare firmware which then you manually will deliver to MCU for update.
But building and preparing of firmwares can be done in any Linux OS in any hardware.
I don’t have some specific instructions for your case, but hope I did explain what goes where and now you will have better understanding what is happening and what should be done.
I do appreciate you taking the time, now i have re done and re compiled the firmware and it seems i am still stuck on the same version which has me even more puzzled now lol
When you are building firmware with command “make flash”
it will compile and build all required peace’s to “out” folded which is located in same place where you did execute “make flash” - it should be a root of klipeer sources.
If klipper build system do know how to push this new firmware to MCU - it will try to do it, if it don’t know or just can’t - it will display some instruction what you need to do manually.
So if sources are in this path “/home/user/klipper” then folder with firmware should be here “/home/user/klipper/out”
that “out” folder contain not only firmware, but many different temporary files and folderr which was generated during build process, in most cases firmware will be there if “make flash” did finish cleanly without errors, if during build you hit some error - most probably firmware will not be build.
I believe now that it all lays with the adxl345 when i re enable it i get the error but disable it i dont get the error so somewhere with the update something was changed and not properly given instructions as to what changed and how to fix such error.
Also with the manta m4p it has the cb1 on board which i guess would be the host, so its alot like a pi? But on board
Klipper is constantly evolving and new version of host can require new kind of protocols to communicate with MCU.
So if your adxl345 was working thru MCU which have old version but latest “host” is talking on new language (protocol) which old MCU firmware just don’t understand.
Yes, exactly “CB1 module” - it’s just a mini pc with Linux OS.
And behind of “CB1 module” you have Manta M4P control board (MCU) which have serial(or some other type) connection to “CB1 module”
Yes i do understandt that thank you… but for the life of me through re compiling etc i cannot find a new firmware for that mcu, but i forgot i had a new l2sdw adxl from btt and compiled the firmware etc and setup the configs and the printer ate it up like it was double fudge cake , no complaints from it, except i have the complaint it needs to be constantly plugged in, but that must offer some extra feature some how of it is constantly reading the values?
If I remember correctly currently klipper uses adxl only when you are setting up input shaping - to do the tests and collect data, after that - it’s not used at all, there is no “online monitoring” of resonance.
But maybe system is just checking if it’s there during startup - because it’s present in config.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.