Internal Error on Command "BED_MESH_CALIBRATE"
Hi, when i start my print, it heats up the bed, z tilt and make a mesh.
immediately after mesh it crashes with Error:
21:15
Internal error on command:"START_PRINT"
21:15
Internal error on command:"_START_PRINT_BED_MESH"
21:15
Internal error on command:"BED_MESH_CALIBRATE"
In the Klippy Log i can see this error:
virtual_sdcard.py
TypeError: init() missing 1 required positional argument: 'name'
Klipper : v0.12.0-102-g9f41f53c
RatOS: v2.0.2-23-g4beae44
15 Replies
Most likely invalid characters in your .gcode filename. Stick to a-Z, 0-9 and -_
Are you sure ? "EBB42 Mount - Eva 3.x - Orbiter 2_0.2mm_PETG_1h39m.gcode"
Renamed to "EBB_02_1h39.gocde" and same issue
Nope then it’s something else
Have you installed any extensions or made any modifications to your RatOS installation besides modifying printer.cfg?
Only printer.cfg and made all updates available
Curious. Please post your klippy.log and i’ll take a look.
Hmm it appears to be related to either the beacon code or maybe the new bed_mesh changes in klipper.
Please try and refresh your update manager in the machine tab in mainsail and see if there are any updates.
There is a beacon update, i will update it and get back here
👍
You were correct ! Beacon was the problem : 4 Days ago there was a commit for "Add adaptive bed mesh support".
Now it works
Good to hear! 🙂
I am getting the same exact error after running a PA tune for some reason. Not sure if that is what caused the issue or not, but I can reprint the last test cube over and over. Just can't print anything new. How was it fixed?
10:06 PM
Internal error on command:"START_PRINT"
10:06 PM
Internal error on command:"_START_PRINT_BED_MESH"
10:06 PM
Internal error on command:"CALIBRATE_ADAPTIVE_MESH"
10:06 PM
Internal error on command:"BED_MESH_CALIBRATE"
by updating the software, check your klippy.log for more information on the errors
I did recently update my system, I had a few OS-packages. I grabbed the log after the event and did see the errors towards the bottom, but don't see where the issue lies.
Did some searching, oddly if I add BED_MESH_CALIBRATE ADAPTIVE=1 to my start gcode in Orca the issue goes away.
Is there a reason I would suddenly need to add that when everything worked fine before?