Welcome to Sovol-SV06-firmware Discussions!

[bassamanator]

👋 Welcome!

We’re using Discussions as a place to connect with other members of our community. We hope that you:

• Ask questions you’re wondering about.
• Share ideas.
• Engage with other community members.
• Welcome others and are open-minded. Remember that this is a community we
  build together 💪.

To get started, comment below with an introduction of yourself and tell us about what you do with this community.

[shogun-fpv]

Hello Bassam. Thanks for putting this together.
Do you have some basic Slicer settings that are specific to your configuration?
The documentation makes reference of Andrew Ellis' guide, but wondering if you had specific Gcodes for your setup.

Thanks.

[bassamanator]

@shogun-fpv Not sure if I follow. All the macros included are listed under Highlights. The SuperSlicer config bundle already includes the start and end gcodes.

[dweenz]

Hi Bassam, Hope you are well. I know I can just add the BED_MESH_PROFILE LOAD=default to my gcode to load my mesh, but could you explain if you have time how to create the macro to add the above command with the m420 command in it's place I am on klipper and m420 does not work.
Cheers,

[bassamanator]

@dweenz My friend you missed the last step, see the 'adjust your slicer section'. All of these nitty gritty details are taken care of when using this config.

[LzLang]

Hello Bassam,
thanks for your work!

I'm new to Klipper and I have a question about position_max :
When I use the command G1 X300 F3000 and G1 Y300 F3000 I have about 3 mm on the X-Axis and 5 mm on the Y-Axis till it "hit's" the frame.
My question is now: should the max_position for X: 303 and for Y:305 because that the maximum movement, or is max_position only important for the overall print size?
(Same goes for the Z-Axis)

Thanks in advance!

[bassamanator]

@LzLang So max_position is not a thing, so I'll just ignore it.

From klipper docs:

position_max:
#   Maximum valid distance (in mm) the user may command the stepper to
#   move to. This parameter must be provided for the X, Y, and Z
#   steppers on cartesian style printers.

So if you can actually get to X303, then you can set 303mm as your X build plate size for example. I recommend to leave 2-3mm as a margin for error, in my case my filament sensor cable hangs around that area and I would never want it to get pinched. Make adjustments according to your needs.

[Aquaman7]

will this work on BigTreeTechs pad 7? I got it for review and wanted to use it on the sv06 plus because it prints so slow but I'm kind of new to klipper and not entirely sure I'm doing this right.

[bassamanator]

Yes it will. Here's a video using my config and the pad 7, however, it's in German, but you can use the auto-translate subtitles feature.

[Manfredo1952]

Indeed. I am from Germany and have used the video linked by Bassam to be convinced to by it for the SV06+ that I have. Am using the Pad7 with my SV06+ quite happily.

[bassamanator]

@Manfredo1952 I was quite delighted when I came across that video, even though I couldn't understand any of it, and had to use the auto-translated subtitles. I'm glad my config has made it around the world.

And that mpoxDE is a super nice dude!

[milan360]

Hey Bassam,

I have an SV06 with an SKR-mini-e3-v3 board and recently tried your config. The issue I'm having is once I load up and start a print job, and both the bed and hotend reach their temperature, both of the heaters turn off and the printer keeps the print going until the temperatures get too low and Klipper just cancels the print.

I am using Cura to slice, and have updated my gcode start and end to reflect what you have in your instructions:

PRINT_START BED=[first_layer_bed_temperature] HOTEND={first_layer_temperature[initial_extruder]+extruder_temperature_offset[initial_extruder]} CHAMBER=[chamber_temperature] PURGE_LINE
Is there something simple I'm missing?

[bassamanator]

This is the correct start gcode for cura:

PRINT_START BED={material_bed_temperature_layer_0} HOTEND={material_print_temperature_layer_0} CHAMBER={build_volume_temperature}

Feel free to add the purge_line on a second line.

[bassamanator]

It says clearly that this is an example.

[milan360]

Understood. Thank you for the reply and the help.

[bassamanator]

This whole Klipper switch is quite technical, it's crucial that the instructions are followed to a T, they are correct and have been tested thousands of times.

[bassamanator]

@milan360 Instructions have been tweaked based on your feedback. Thanks!

Feel free to report other issues.

[lrochfort]

Hi @bassamanator , thanks for the guide.

I've just installed Mainsail using MainsailOS. It says to import mainsail.cfg into the printer.cfg. I see you don't have that in your printer.cfg.

Should I add it?

[bassamanator]

I'm a MainsailOS user my self and I never had to do this. However, it's possible that this is a recent change. Please do a [include .mainsail.cfg] in your printer.cfg, somewhere near the top. Will look into this.

[bassamanator]

I just checked this with the latest version of MainsailOS. mainsail.cfg is not required. You've missed a step somewhere.

[lrochfort]

Thanks for looking.

I looked here: https://docs-os.mainsail.xyz/getting-started/first-boot

In the "Config" section it states:

We recommend checking mainsail.cfg and adapting it to your needs. Then open the printer.cfg and type in the editor [include mainsail.cfg] and click on "SAVE & RESTART".

[bassamanator]

Recommendation, not a requirement...

[chainsawsquirrel]

Im going nutz, the sv06 plus wont home properly, thinks the back of the bed is home position , Ive copied your stepper settings into the config.cfg still doing it .. is there another place home etc defined ?

[tayloredenterprises]

Hiya!

Wondered if you could help me please.

I have upgraded my sv06+ with a BTT skr e3 3.0 and Klipper. Using stock motors.

The first layer looks good however in subsequent layers, the extruder seems to be skipping steps / not rising as it should which results in the nozzle going into the previous layer.

I’ve tried adapting your BTT / sv06 printer config, however it doesn’t fix the problem. Is there a different stepper/driver config required for BTT with sv06+? Particularly microsteps , rotation distance and current?

[bassamanator]

So it seems that everything is working? Simply pull in stepper currents from sv06-plus branch for the steppers. Also read warning about steppers on skr branch.

Original wrote this but ignore it since you have everything working already

You need to carefully blend 2 branches together, sv06-plus, skr-mini-e3-v3.

Start off with skr-mini-e3-v3:

1. apply dimensions from sv06-plus
2. apply run_current from sv06-plus
3. handle filament sensor after you have everything working, so leave it commented out

[ChrSch84]

@bassamanator

Hello first of all i love your klipper Guide :) Thanks for the hard work.

Now my Question.

I found out that there is a Klipper Default Config for the S06 Plus and there a few changes to your Config.

Found it on the Github for Klipper.
https://github.com/Klipper3d/klipper/blob/master/config/printer-sovol-sv06-plus-2023.cfg

i Compared the two files and this is a small snapshot of it.

Left is your Config.
"

"

Some Settings are faster with yours but not all.

Could you give us some Info why you use "this" settings over the "klipper" ones? Mybe Pro and Con?

Thank you

[bassamanator]

I added a second paragraph to the Preface on the repo to answer such questions quite some time ago. Please read that, and further, know that the config found on the Klipper repo is not created by someone who writes code for the Klipper repo, or some 3d printing expert, and it is certainly not the "source of truth" (that would be Sovol's Marlin source code and now the Klipper config that comes with the Sovol Klipper screen).

Glad you found the repo useful. Please also see the everything-sovol-sv06 repo.

[ChrSch84]

Ok thank you.

Found the Klipper Config from the Klipper Screen.

But there is even more split of the settings.

Example:

"[printer]
kinematics: cartesian
max_velocity: 300
max_accel: 10000
max_accel_to_decel:5000
max_z_velocity: 15
max_z_accel: 200
square_corner_velocity:5.0"

10k vs 3k and other Settings like the stepper Motors. I know your settings are your settings... i get it but why is there so a big gap?

Is it that sovol is "fuck it" give them speed over quality or is there something else?

We all here want to push our printers but at what cost? Hope you could shine a light on this.

Thank you.

[bassamanator]

The properties that you're pointing to, max_velocity, max_accel, etc., are meaningless, as in, they will vary from printer to printer in the budget market. You need to adjust those to your needs (check the personal branch to see the settings that I use, for example). And yes, Sovol doesn't care about these details unfortunately, I'm not joking here, it's a bit of a sad truth, but this can be said about most manufacturer's (companies such as Bambu Lab being an exception). For example, I've encountered one or two users who can't push their printers past 3k/4k accel, I'm sure there are many more of them.

You're overthinking this when you should be testing and adjusting these values to the capabilities of your particular unit.

[tjhayko]

I'm not sure if this is the correct place to ask this, but I'm trying to get my SV06plus working with a BTT Pad 7 based on bassmanator's instructions, but /dev/serial doesn't seem to exist :(

I've flashed CB1_Debian11_Klipper_kernel5.16_20240319.img.xz onto my SD card, so I think I'm on the latest OS for the BTT Pad 7 with CB1.

Any help or pointers would be appreciated.

[tjhayko]

Okay, I changed that, and I'm still getting the same error in my klippy.log :(

Is there any way to determine if the printer was correctly flashed with the klipper firmware? That's a wild guess on my part, but now that the Pad appears to be able to recognize that the printer is connected.

I also found that the moonraker.conf had the klippy_uds_address set incorrectly to /home/pi/printer_data/comms/klippy.sock, instead of /home/biqu/printer_data/comms/klippy.sock, so I fixed that. Now at least I'm getting the error in the web UI rather than having to go to the logs.

[bassamanator]

I also found that the moonraker.conf had the klippy_uds_address set incorrectly to /home/pi/printer_data/comms/klippy.sock ...

This is already clearly mentioned in the documentation, which you obviously haven't read, hence your struggle. It takes 9 minutes to read the entire page. I'm sure you've missed other things as well.

[tjhayko]

Thanks. I've read the page a couple of times, but I guess I unfortunately missed that part.

After reading again, I think the only step I've missed is disabling the 5V pin on the USB cable. Is the a possible cause of this type of problem? I've ordered a USB power blocker to try, but it won't be here for a few days

[tjhayko]

Apparently, microSD card #4 is the charm. I reflashed again with yet another SD card. I'm able to get connected it looks like mainsail is working or at least I'm able to home the extruder and move the head around now.

[bassamanator]

Great. Just run through the rest of the steps carefully, you're more likely to have a collision during the initial setup. Best of luck!