Rappetor / Sovol-SV08-Mainline

Getting the Sovol SV08 onto mainline Klipper
GNU General Public License v3.0
93 stars 26 forks source link

Reddit user had issues (like heater turned on full blast) #48

Closed froh42 closed 2 months ago

froh42 commented 2 months ago

This is not mine, but I'll open an issue to have it documented. The failure scenario when mixing up the MCUs seems concerning, we might add some steps to prevent that.

https://www.reddit.com/r/SovolSV08/comments/1f4z7fh/sv08_mainline_klipper_notes/

Copying what reddit's u/TomB19 wrote:

I want to document a few things, before I forget.

"Value out of range, shutting down" can be caused by [MCU] and [MCU EXTRA_MCU] being swapped. There are two serial connections and they are easy to transpose. Try swapping them

If your MCU serials are swapped, the hot end heater is slammed on. For this reason, it's best to be in the room with the printer when configuring. I could smell mine getting really hot and pulled the plug before it burned down.

I spent two 5 hour days, unsuccessfully trying to get Rappetor/Sovol-SV08-Mainline to work. It didn't work on my system until the August 28, 2024 update. Believe me, I tried every conceivable combination and did the process dozens of times.

Ultimately, I got it to work with the SD->eMMC path.

Be careful of the details in the process. You cannot burn through the instructions like nearly any other project. The devil is in the details.

It's important to use a micro SD card smaller than 32GB. I found an 8GB card that worked fine. 32GB cards will flash just fine but the "nand-sata-install" step will fail. If nothing is working and you fail at every step, check your TF card size.

I now hate Balena-Etcher. I'm sure the software is fine. I was able to find a two generations old AppImage that worked fine but I ended up compiling from source to get the current version during my 10 hours of troubleshooting. Somehow, my linux distro does not work properly on current Balena-Etcher images. To be fair, the current EXE doesn't work on my Windows 10 box, either; it just hangs when I select an image.

rPi Imager worked well for me on both linux and Windows 10. Ultimately, I went with the version on the BTT GitHub account for CB1 firmware, as I had highest confidence it would work. I think any recent version would work, though.

I apologize if this post offends the people working on SV08 mainline Klipper. I am profoundly grateful for the work you have done to bring us to the supported, standard, Klipper. This post is intended to help other people who may, like me, struggle for an extended period working on getting this up and running.

froh42 commented 2 months ago

Reply on reddit, maybe there will be an answer on what went wrong: https://www.reddit.com/r/SovolSV08/comments/1f4z7fh/comment/lkp5ln4/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

Rappetor commented 2 months ago

Weird, 32GB sd card worked fine here (nand-sata-install), have tried multiple time last weekend (did some additional testing which made me update some stuff in the guide as well). Same with flashing the eMMCs with Balena Etcher, used multiple versions of that software and they all worked fine on both WIN10 and WIN11.

But I think I have cleared and reflashed like 30 times now with different eMMC's and multiple SD cards of different sizes. And did the WHOLE guide from start to finish following the exact steps multiple times as well (from different computers).

Point being, I guess that is the difficulty in things, you always end up with weird edge cases where it all goes according to plan like 99/100 times and then 1/100 something weird happens. Nobody's fault, just a weird combination of -something- causing an issue at some spot in the guide. Hell, not too long ago there was someone at the Discord who couldn't get the SD card to boot.. turned out the little spring clip inside the SD card slot was faulty and sticking out.. You can't make that sh*t up I'm telling you! 😄

Anyway, back to business: I'd say we add a warning about swapping the serials. And if someone can figure out a way (software, via SSH) to like 100% know which MCU is which MCU I'll gladly add that too.

The most easy thing I can think of is just unplugging the toolhead power and then see what serial is left, that is the MCU. Plug toolhead power back in and that is your EXTRA MCU. Think I'm going to add that to the guide right away.. Don't want stuff to burn down because of this.

And I'll try swapping the serials as well later tonight on my printer, see if that is a default thing that happens (the heating) or was also perhaps caused by something else.

Rappetor commented 2 months ago

Ok, just swapped my serials and indeed interesting things happen 😆 Also heating of the nozzle.

It's really a shame Sovol started with the /dev/ttyACM0 and /dev/ttyACM1 serials instead of the real serials. Thats what's been causing all this to begin with (otherwise you will find the correct serials in the original printer.cfg).

So.. extra step to add: remove the usb plug on the toolhead and see what serial is left. Plug it back in and see what new serial appeared. The only 100% sure way of knowing which is which. Will add this in like 30 mins or something.

Rappetor commented 2 months ago

Ok, I have added a pretty big warning at the spot where we want people to add their serial to Klipper. Together with an image of what plug to disconnect for the USB (in order to identify the correct serial).

froh42 commented 2 months ago

Perfect, a warning and a step with removing the toolhead USB is a great solution. I remember that I didn't read some stuff when mainlining for the first time, so adding that step to make it safer for us scatterbrains is great.

Btw, as I have my EMMC now I'll also try to switch over to EMMC (my SV08 runs on SD card now for quite some time). I'll find out if I see anything similar like the reddit user. I suspect a bit he was hasty, or not reading closely for his problems. He also mentioned trying balena on linux, I have Win and Linux here and might try both.

Rappetor commented 2 months ago

Ok, added the warning and how to determine what serial is for what mcu. I think we can close this issue! In the next update I have a small additional warning all the way at the top of that chapter added as well.

People... you have been warned! 😆