Printer Model: Elegoo Orange Storm Giga
klippy.log
After trying to update klipper and moonraker, I have an error saying Internal error during connect: ‘MCU’ object has no attribute ‘register_flush_callback’
I am unable to understand what the issue is and what I can do to get rid of it.
I have searched online, but seemingly am the only person having this issue.
Any help would be highly apprechiated.
klippy.log (81.9 KB)
Hello @Gallo !
Git version: 'v0.12.0-321-g8e1cdb199-dirty'
Have you tried with a clean Klipper setup?
Heeya @EddyMI3D,
Thanks for the fast reply.
I have no idea how to re-install or revert to a prior revision through the command line.
Would you be able to point me to the right documentation page?
Did you install your Klipper system with KIAUH?
The printer came preconfigured with Klipper, thus I didn’t flash anything yet.
I have flashed an other printer with Klipper (Anycubic MZ2.0 through OctoPrint), but the command ls /dev/serial/by-id/* doesn’t give me a valid output, so that installation guide is not of much use here unfortunately.
Furthermore I have no idea what the mcu the printer is running and searching online didn’t give me any result. Else I would have recompiled it.
Edit: just saw the kiauh directory, so yes. It was installed via kiauh.
Update:
After finding the kiauh directory and opening kiauh.sh, I checked the update section and saw, that everything was on “old” revisions; moonraker was even 2 versions old (V7… when current one is V9).
Updated everything one by one. Only thing which wasn’t updatable was moonraker, as it gave me something along the line Uncommitted files stashed or whatever as an error.
I then unistalled and installed it again using the kiauh script.
Everything seems to be working again, except for klipper, where I suspect to have corrupted the firmware of the MCU. Currently I’m unable to flash it again; the reason is unclear to me, but probably the compiled firmware doesn’t have the right options set, as I don’t know any of them and just puzzled them together from sparse information on the world wide web.
I’m waiting for Elegoo to come back to me and tell me what the correct options are.
I will keep this thread updated.
Here an update on the issues I have encountered:
I heard back from Elegoo and they’ve sent me a fix package which fixed the machine. (I would have attached it here, but it is too big)
After having brought the printer to a working state, I tried to update the versions of Klipper and Moonraker, which didn’t even show any version number, through Fluidd. Klipper worked fine (just judging from not getting a heap of errors), but after trying to update Moonraker, the machine spit out one error after the other again.
Right, back to the start again, by putting on the Elegoo fix package.
I then tried to update everything using the kiauh script.
Started with Moonraker; didn’t work at all this time due to a git issue. Uninstalled Moonraker and installed it again, and see there, it worked. Horray!
Went on to Klipper; also didn’t work due to a git issue… Uninstalled it and installed it again, and see there, doesn’t work at all…
Between the version the printer is running (supposedly v7) and the current one (v9), the path for the configuration files seems to have moved (from ~/klipper_config/ to ~/printer_data/config/), which would be an easy fix. Copied the files and…still errors. This time some problems with the content of the config files (Section ‘gcode_shell_command clear_plr’ is not a valid config section and Section ‘motor_constants ldo-42sth60-2004ac’ is not a valid config section are two of them)
At this point, I give up and ask for Elegoo to bring out an update which brings the printer to a more up-to-date state and from which it is safe to update Klipper and Moonraker.
This probably is not going to happen. Unfortunately quite some vendors deviate significantly from the original Klipper and sometimes also Moonraker / KlipperScreen / Fluidd etc.
Often it is outright impossible to use the “official” versions due to this and doing so will break your printer for good.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.