#sovol sv06 ace MCU error
1 messages · Page 1 of 1 (latest)
Is the fan in the large black control box on the left and right running when you turn the printer on or run a print?
(Motherboard box)
And check all the cables are plugged in all the way by pushing them in (WHILE POWER IS OFF)
Otherwise might be klipper related... 🤔
The mcu \ cpu is the brain of the printer.
If it overheats, you can get errors. (But theres other reasons too)
The thing your trying to print....is it round or circular by any chance?
Sorta round
It's a split keyboard case
Oh! Ok so really shouldnt be a massive issue.
Used be an issue when you'd send lots of g1 one commands to a weaker mcu (so the solution was to enable arc moves in the slicer to send g2(?) g3 commands (?) instead and thus reduce the amount of processing needed.
should i try a test print first to make sure its not a hardware issue?
i didnt mean to delete that message 😐
anyways, i think i could be a klipper issue because its not connecting from my browser
I don't there would be much hardware related to the issues except heat and cabling...
But you can try a really high res cylinder without arc moves on maybe? That should hammer the mcu + in theory reliably trigger the message (this is a guess)
Klipper usually has a log file you can pull and look at.
sure but if it is of any relevance here is what im trying to print
you can see its pretty detailed, that might be part of it
Dactyl manuform?
Yeah but that shouldnt be triggering an error even though.
If you restart the printer, and download the klippy.log (i think) it might say something? (And other with more klipper knowlegde can then help)
dactyl scylla but yes
im trying a benchy just to see if its a gcode issue or a hardware issue,
after that ill check the logs
benchy was flawless, must be a gcode issue
I have an SV08, not an SV06 ACE but I was having the move queue overflow problem a lot. I figured out how to fix it, it’s probably similar for the SV06. For anybody else who gets stuck with this error I found the root cause and how to fix it. The problem is Sovol’s PLR (power loss recovery) customization to Klipper. This is why moving to ma...
ill look at this tomorrow, its late here. thanks
This post has been inactive for over 1 hour and so has been closed. To reopen this post simply send another message.
ok, sorry for the late reply but i have not been at the computer for the past few days so i am just not getting to this
ok, ive sshed into the printer but i do not think the code is the same as the sv08s
yeah, not sure what to do here
This post has been inactive for over 1 hour and so has been closed. To reopen this post simply send another message.
thats a local IP, local ones can change day to day
pretty sure its a static ip
you set it in your router?
well
i have the IP bookmarked and 90% of the time it works
i didnt set it in my router, i think it sets itself automatically
it does set automaticaly, i guess it set itself to the same thing for a long time, but without a static set from the router it can change
IE you dont use it or a day, some other thing gets the IP and then it cant set the same
and i would expect the UI to load in the first place if the IP was right, regardless of the klipper error
every once in awhile it doesnt load
not really the main issue for me right now, its working flawlessly right now
webcam is working too
im hesitant to try printing it again considering this didnt work and i havent made any other changes
im wondering if there are any gcode optimizations i should be making in orca slicer
whats the resolution and is arc fitting on in quality/precision?
.16 i think? i didnt change anything related to arc fitting
i mostly use the default settings given
i may aswell just reslice it though, i dont have the project file saved
how would arc fitting benefit me here?
it wouldnt with klipper
and .16 is fine, even probably rough, it makes the moves larger and easier to parse
.016 would probably also be fine
¯_(ツ)_/¯
i hope this isnt some deeper issue, i do not think its a hardware issue because i printed a benchy flawlessly a few days ago
maybe i should be keeping an eye on the cpu and ram when its printing
you slice the benchy? also dont think its a gcode issue off that
though dont really know if there is some config issue with the ace that would cause that
i am pretty sure i reset all of the configs not that long ago
my firmware should be up to date aswell
ah, sovol messed up klipper, its trying to save after every G1 command https://forum.sovol3d.com/t/shutdown-mid-print-mcu-shutdown-move-queue-overflow/6374/10
I have an SV08, not an SV06 ACE but I was having the move queue overflow problem a lot. I figured out how to fix it, it’s probably similar for the SV06. For anybody else who gets stuck with this error I found the root cause and how to fix it. The problem is Sovol’s PLR (power loss recovery) customization to Klipper. This is why moving to ma...
klipper doesnt really need power loss, and it causes much more errors than it solves
i looked at that before but the code between the sv08 and the sv06 ace is not the same, i could send the gcode_main.py here if its of any use
im not smart enough to know what that file does on its own lol
is that part from the link not in there?
any rename_existing or gcode_macro with a G1 in it?
not seeing any issues with that myself either
yeah im clueless honestly