PLR and ‘mcu’ shutdown: Move queue overflow

Firmware
1

Back in December @imagio discovered a bug in Sovol’s PLR routines that contributed to the ‘mcu’ shutdown: Move queue overflow error. see this thread https://forum.sovol3d.com/t/mcu-mcu-shutdown-move-queue-overflow/8952 for details.

I had implemented those patches on my SV07 without issue. Recently I has a power loss event and was unable to restart using Sovol’s macros.

So I fed Sovol’s original routines into Claud AI and told it to debug the whole PLR system. 5 issues were identified (including the known issues discussed above). The ZIP file below has 3 udated files and a PDF explaining what was changed, and why. There also instructions on how to apply the patch and how to roll back if needed.

I’ve tested on my SV07 and was able to restart an interrupted print.
@sovol3d Feel free to distribute these files with no need for attribution.

Beta testers WANTED. As far as I can tell every Sovol printer has buggy PLR code. Sovol has forked their public klipper repository to a private git server. There MAY be versions that are incompatible
Feel free to pass this along on Discord and Facebook.
files.zip (20.2 KB)

2

Thank you @cardoc I’ve run across both errors on my Sovol Zero “starts from the wrong layer or produces invalid gcode and errors out entirely”, lost half finished prints both times.

Appreciate you sharing the patch!

Cheers,
-Mike

3

Has there been any word from Sovol about them officially fixing these bugs? After I originally found/fixed the bug I reported it to them and got “thanks we’ll pass it along to the engineering team” and heard nothing since.

4

@sovol3d

……………………….….

5

I got a like from @sovol3d on the first post in this thread… Does that count?

@sovol it’s been broke for 3 years.

I’d still to beta test it on different printer models. Sovol’s private Git server (open source my ass) make it impossible to know how many models are effected.

6

Absolutely brilliant! @cardoc

I’ve tried a couple of other solutions that did not solve the root cause of this “MCU Shutdown” problem.

Since not being an advanced user I needed a comprehensive step by step instruction in order to carry out the changes in a safe way.

Thank you very much for your work! Very professional ! My 6 month old SV08 is now printing big and complex prints like a dream.

I really hope the Sovol team will implement your solution in a not so far away new firmware release, otherwise it is a shame.

PS. I noticed that the mainbord fan now only have to work half as hard as before to keep the temp below 60C.

Volunteer beta tester: Sovol SV08 with Eddy Current Kit & FW v2.5.0

7

Thanks for the feedback. Glad it worked for you.

@imagio did the hard part, I just packaged it up.

Have you tested the PLR function?

8

Hi,

have not tested the PLR function yet. Working on the backlog for the moment but I’ll post back when I’ve tested it. Best regards also @imagio for his part of the brilliant work.

Volunteer beta tester: Sovol SV08 with Eddy Current Kit & FW v2.5.0

9

Usually that mean that they will mention it to the techs.
But you have to remember, that doesn’t mean they will fix it.

10

I downloaded and installed the three files in the zip.

This fixed the MCU move queue error for my Zero, thank you!

I get this message on the console:

2:35 PM Unknown command:“SET_PLR_STATE”

and am not finding that defined anywhere. I only find it used in plr.cfg.

Should it be defined in plr.cfg or ?

Thank you!

11

The only thing I can figure out is your machine is still running the old gcode_move.py

Reinstall the patch making sure you are in the correct folder on the printer for each file.

12

I rebooted a few times and the message hasn’t come back. Sigh

Thank you!