#Apparently this is above my pay grade...
90 messages · Page 1 of 1 (latest)
I had a look at the mod view and I might have been wrong yesterday. You might need to reflash. The last time you came here, you sent a "klippy.log" but that was not official Klippy. So it might be that you need to rebuild and reflash your mcu again.
Just to get you understand this. The crew is doing basically most of the support here. No one here is using those weird Creality products. Our experience is based on this support. Iirc they used somewhat real Klipper on the sonic pads in the past, but it seems like they changed something.
Just to get you there a bit faster:
https://github.com/Klipper3d/klipper/blob/master/config/generic-creality-v4.2.7.cfg
mcu.error: Can not update MCU 'mcu' config as it is shutdown
Can not update MCU 'mcu' config as it is shutdown
Once the underlying issue is corrected, use the
"FIRMWARE_RESTART" command to reset the firmware, reload the
config, and restart the host software.
Error configuring printer
your mcu not reacting on the init process of klipper. so as @hushed marsh already wrote, try to flash your MCU again.
ok i can do that but where do i get the proper file from?
you dont flashed this board with klipper until now?
i did the sonic pad makes you copy a file to a sd card then you flash
did you do that?
along time ago
did the board/printer works one time with that?
so this printer/board worked already with the sonic pad?
and then you changed something on this printer and after that, you got this problem?
The sonic pad does not use mainline klipper. It's some shitty modified version
Now he switched to mainline klipper
yes but i jail breaked the sonic pad im running debian now
everything is working im even connected to my wifi its just the problem im having
i needed to go this route because i got a beacon scanner and the sonic pad wont allow you to install it now i can
after the jail breake, it stopped working with the printer?
yes
ok. these are all important informations, we would need to help here! we thought you use a "generic sonic pad"
if you change to mainline klipper, you have to rebuild your board firmware and flash the printer board again. which board do you use?
well the way i see it im not having issues with the os its with klipper
loooool
creality 4.2.7
but the default OS doesnt have a mainline klipper
if you speak from sonic pad, we all think about this creapy creality thing and our "generic klipper" stuff will not fit for that. but if you jail break it and run mainline klipper on it, we have to direct you in a complete different way!
yes no klipper logo
we all dont have a sonic pad (i put my one in the trash a long time ago). do you really think this logo is a identicator for us?
i honestly dont know 🙂 LOL
you can just share these important informations. for example the last point you did, before it doesnt work. then we would identify this issue much faster!
ok. do you build a klipper firmware already? do you know how this work?
no
like i ssaid when you get the sonic pad it does that for you
the sonic pad makes you plug in a sd card reader then puts the file on the card then you put it into the machine turn it on and flash it
since then i havent done anything to it
like i asked mr yel yesterday i figured it was going to be this firmware issue
login via ssh to your sonic pad and run:
cd ~/klipper
make clean
make menuconfig
make
ok
and in make menuconfig, you have to set these settings for your board: https://github.com/Klipper3d/klipper/blob/master/config/generic-creality-v4.2.7.cfg
here in the first lines, there is the description. then oyu can find the firmware file in ~/klipper/out/klipper.bin. in the last lines of the header, is the description how to flash it (the same as you have done with the sonic board)
these are just the default settings for building the firmware. if you dont build the firmware with these settings and dont upload it (it would not upload, because a atmega has no .bin file), nothing happens here
ok what do i do with that first menu i showed you
did you read, what i posted?
i see ok didnt know i could do that
theirs alot here i dont know how to answer i understand the printer.cfg stuff but the stuff in the make config is different
enable extra low level config options has an asterisk
the microcontroler i did
bootloader offset 8kib bootloader?
just dont touch the other settings. the default value will fit, if they are not in the config file above
ok i saved the config now do you want me to copy over that printer config?
ok im following give me a sec
ok i compiled everything now what do i do?
ok i just put the bin file on an sd card its called klipper.bin should i rename it?
sry for the dumb question, but did you read anything?
here in the first lines, there is the description. then oyu can find the firmware file in ~/klipper/out/klipper.bin. in the last lines of the header, is the description how to flash it (the same as you have done with the sonic board)
Flash this firmware by copying "out/klipper.bin" to a SD card and turning on the printer with the card inserted. The firmware filename must end in ".bin" and must not match the last filename that was flashed.
at first i wasnt paying attention to the greyed out section of the printer.cfg and then i figured out that the make config app defaults to low level i had to turn that off i got the bin installed and it worked for a split second then its back to the same thing
i renamed the file dont worry
after i got the screen to pop up it said something about stopping cause its to hot
it was talking about the hot end
is there a way i can see if the bin file took?
i copyed the printer.cfg over and now its working yippy
thanks for all your help
if you have a different error, pls post the new log, that we can double check it the next time...
happy printing!
i do have another problem but its with the beacon eddy current surface scanner i just installed do you want me to post that? i was just going to goto their discord channel
heres all the info i have so far
Can you tell us how you installed everything?
Also did you try to setup resonance testing?
Here is the real error
can you also send the output oft apt search libopenblas
i ended up putting the new firmware on the mainboard like meteyou told me. took me a second to figure everything out. then i have been chasing down gremlins in the printer.cfg I'm almost done. i ended up getting this numpy error [pic posted] guy in beacon channel told me to do what's shown. now im having an issue its not wanting to accept a homing after doing it so i can do a beacon calibration like i said one gremlin after the other.
The command above would be good for debugging your issue, but now you did a lot between and it's not very helpful anymore.
Also cross posting is the worst case for helping! You executed different things and spoke with different helpers who don't know what other helpers already said.
So we stop here helping you, because this progress is useless!
I only went to the manufactures site for the Beacon eddy current scanner
Yes, but they helped you with a problem unrelated to the Beacon, maybe with more issues too. We don't know what they helped you with.
Furthermore your newest "Gremlin" is connected to the Beacon. They can help you best with it.
That you get our view of this. We are doing this all in our free time. If you post in multiple places it's possible that we waste our time to write responses or do research, but then you go to a different place anyway and get some solutions there, invalidating all the info you gave us.
I also asked for a few command outputs, that would have helped us to understand that exact issue better, as we are right now doing research on that exact topic.
i think you miss understood what i ment buy gremlins i was talking about printer.cfg problems like with my mins and max for the printer bed stuff like that. i am haveing a problem that has been more of a nusance up until now tho. moonraker has been taking an awful longtime to start. it does eventually then everything works fine. any hints?
I know what you meant with gremlins