Sovol SV06Ace profile start g-code
The provided slicer software for the Sovol SV06 Ace does not include a linux version. OrcaSlicer is a mess right now in Linux; in both Debian 12 and ArchLinux, it will not build and the AppImage won't run.
Using an online *.json -> *.ini converter, on the Sovol SV06 ACE 0.4 nozzle.json, and importing into PrusaSlicer 2.90 I had some start g-code. On cross checking the *.json file there was additional code which I copy/pasted.
I'm posting the start g-code that I can up with if it can help any other Linux user and to get comments/criticism:
M140 S[bed_temperature_initial_layer_single] ;set bed temp M190 S[bed_temperature_initial_layer_single] ;wait for bed temp G90; G1 X0 F6000; G1 Y20; G1 Z0.400 F600; G1 Y-4 F6000; M400; M104 S[nozzle_temperature_initial_layer] ;set extruder temp M109 S[nozzle_temperature_initial_layer]; wait for extruder temp G91; M83; G1 E-0.200 Z5 F600\nG1 X{print_bed_max[1] / 3} F6000; G1 Z-4.800 F600; G1 X{print_bed_max[1] / 6} E{print_bed_max[1] / 6 * 0.24} F3000; G1 X{print_bed_max[1] / 6} E{print_bed_max[1] / 6 * 0.16} F3000; G1 Y1 E0.16 F3000; G1 X-{print_bed_max[1] / 6} E{print_bed_max[1] / 6 * 0.16} F3000; G1 X-{print_bed_max[1] / 6} E{print_bed_max[1] / 6 * 0.24} F3000; G1 Y1 E0.24 F3000\nG1 X{print_bed_max[1] / 6} E{print_bed_max[1] / 6 * 0.24} F3000; G1 X{print_bed_max[1] / 6} E{print_bed_max[1] / 6 * 0.16} F3000; G1 E-0.200 Z1 F600; M400; G28 ; home all axes G1 Z5 F5000 ; lift nozzle
RE: Sovol SV06Ace profile start g-code
For a start you have a \nG1 on a line so you are missing a return.
The other obvious problem is the placeholders are not going to work with PS as they are not the same as the ones used by prusa slicer. For the extruder its [first_layer_temperature] and [temperature] and for the bed its [first_layer_bed_temperature] and [bed_temperature]
Although you are better off using this form
M140 S{first_layer_bed_temperature[0]} ;set bed temp M104 S{first_layer_temperature[0]} ;set extruder temp M190 S{first_layer_bed_temperature[0]} ;wait for bed temp M109 S{first_layer_temperature[0]};wait for extruder temp
Which defines the ones for Filament 1 (index is from zero internally).
Also I'm not sure the print bed max is valid either. Might be but I'm not familiar with that is PS.
Also why don't you just run the printer wizard again and install the prusa supplied default profiles for the SV06 ? They have the SV06 and SV06 plus listed. At least that way you have a basis to go from that you can tweak and compare to what you have using your json converter.
RE: Sovol SV06Ace profile start g-code
Also I'm not sure the print bed max is valid either. Might be but I'm not familiar with that is PS
I'm operating on the assumption that the code in a *.json file can accurately specify the parameters.
The SV06 Ace has some significant differences from the earlier SV06
It is Klipper based and has a single large fan on the tool head. It accomodates the faster print speeds with bigger nozzle heater and auto levels before each print.
In some ways it is closer to the SV07 and I did find a Klipperized SV06 profile:
https://www.printables.com/model/607280-cvs-orcaslicer-presets-v155-for-sv07plus-klipperiz
Sovol supplied the g-code for 2 benchy's. The PS interface suggested I could pull the SV06 Ace profile from the benchy code. Would that route be more likely to give me a better SV06Ace profile?
It also has a silicon brush for nozzle wiping. A youtube reviewer reports, but I have not verified, that it needs a voron style auto leveling g-code pre-pended to the stl in order for it to print which I think is this code snippet:
G28 ; home all axes G1 Z5 F5000 ; lift nozzle
On my initial code, I missed the newline. Corrected - thanks
M140 S[bed_temperature_initial_layer_single] ;set bed temp M190 S[bed_temperature_initial_layer_single] ;wait for bed temp G90; G1 X0 F6000; G1 Y20; G1 Z0.400 F600; G1 Y-4 F6000; M400; M104 S[nozzle_temperature_initial_layer] ;set extruder temp M109 S[nozzle_temperature_initial_layer]; wait for extruder temp G91; M83; G1 E-0.200 Z5 F600 G1 X{print_bed_max[1] / 3} F6000; G1 Z-4.800 F600; G1 X{print_bed_max[1] / 6} E{print_bed_max[1] / 6 * 0.24} F3000; G1 X{print_bed_max[1] / 6} E{print_bed_max[1] / 6 * 0.16} F3000; G1 Y1 E0.16 F3000; G1 X-{print_bed_max[1] / 6} E{print_bed_max[1] / 6 * 0.16} F3000; G1 X-{print_bed_max[1] / 6} E{print_bed_max[1] / 6 * 0.24} F3000; G1 Y1 E0.24 F3000\nG1 X{print_bed_max[1] / 6} E{print_bed_max[1] / 6 * 0.24} F3000; G1 X{print_bed_max[1] / 6} E{print_bed_max[1] / 6 * 0.16} F3000; G1 E-0.200 Z1 F600; M400; G28 ; home all axes G1 Z5 F5000 ; lift nozzle
RE: Sovol SV06Ace profile start g-code
I'm currently trying to get this all to work and I'm new to 3d printers but need to use prusaslicer for a the same reason, orcaslicer doesn't work on linux well, and even if It did the sovol sv06 ACE config isn't built in and I can't import it. My problem is, the print will start and do the wiping the nozzle thing and the position thing but when It goes to start the print, the temp is set too low and I'm not sure why, I don't see in my start gcode anywhere that it could be setting it to 130 instead of 200. This is my gcode if it helps. I've also made sure that the filament temps are set to 200 as well.
START_PRINT
M140 S60 ;set bed temp
M190 S60 ;wait for bed temp
G90
G1 X0 F6000
G1 Y20
G1 Z0.400 F600
G1 Y-4 F6000
M400\nM104 S200 ;set extruder temp
M109 S200;wait for extruder temp
G91
M83
G1 E-0.200 Z5 F600
G1 X{print_bed_max[1] / 3} F6000
G1 Z-4.800 F600
G1 X{print_bed_max[1] / 6} E{print_bed_max[1] / 6 * 0.24} F3000
G1 X{print_bed_max[1] / 6} E{print_bed_max[1] / 6 * 0.16} F3000
G1 Y1 E0.16 F3000
G1 X-{print_bed_max[1] / 6} E{print_bed_max[1] / 6 * 0.16} F3000
G1 X-{print_bed_max[1] / 6} E{print_bed_max[1] / 6 * 0.24} F3000
G1 Y1 E0.24 F3000
G1 X{print_bed_max[1] / 6} E{print_bed_max[1] / 6 * 0.24} F3000
G1 X{print_bed_max[1] / 6} E{print_bed_max[1] / 6 * 0.16} F3000
G1 E-0.200 Z1 F600\nM400
RE: Sovol SV06Ace profile start g-code
As pointed out initially the placeholders you have arent the correct ones for Prusa Slicer. If you do not use the correct ones then the temperatures wont be pulled through.
For the Sovol SV08 which is klipper based you just install an actual Voron profile and then adjust the bed size and height to match. Then adjust from there.
The whole thing with Klipper is that you dont do most of the start and end stuff in the slicer (still have to pass on the placeholders to whatever Klipper variables you have in the Klipper configs). But most of the actual stuff that you want to control like cleaning, meshing et is all handled by editing your Klipper Print.cfg and Macro.cgf files. and for those you need the Klipper documentation and the lots of examples of customising that are available.
I've recently gone through all that for my SV08.
RE: Sovol SV06Ace profile start g-code
I did manage to compile the most recent Orca Slicer git pull (tag e315586) on Debian and Arch but I still think it would be valuable to have a PrusaSlicer profile. @neophyl, are you happy with your SV08 profile in PS? Is it similar to a Voron 2.4 profile? Can you post it somewhere? Just interested in having something to start with on the SV06 Ace.
RE: Sovol SV06Ace profile start g-code
My SV08 is relatively new, one of those black friday purchases 🙂 I started with the default orca profiles, decided (again) that I really don't like Orca's gui layout compared to PS. I got it working fairly well though and then did a PS profile to match.
I will attach a project file that has the printer profile as well as a basic print and filament profiles too but I'm not sure how much it will help. Due to the fact that most of the config with Klipper is done in its files, especially Printer.cfg and Macro.cfg.
When you load it, it should warn you about a missing post process script. This is for Small Area Flow Control. That's something built into Orca now and I was using it with that. I was also using the stand alone processor in PS for my Klipperised Elegoo Max 3 previously. Makes your top layers much better when set up well.
RE: Sovol SV06Ace profile start g-code
@neophyl Thanks.
Given the forking of the different slicers back to SuperSlicer, I'm kinda surprised that the allocation of the configuration variable varies between the projects. I've heard that Prusa has such consistent manufacturing that resonance compensation is built in.
The main reason I went with the SV06 Ace over an MK4S kit was the adoption of Kipper and I will likely mod it in the future.