Wondering when the sv04 will be a default printer in Orca Slicer? Has anyone got a profile I could import and give a try?
thanks
Try this :
Thanks a bunch. Will give it a try.
1 Like
that did not go so well or i needed better directions. I thought there would be a simple import for OrcaSlicer by now.
I have a working profile for extruder 1 if you are interested. I have played with the above mentioned profile, but it seems to only be for dual mode on the sv04. I have only done a couple prints with the ext 1 profile, but I can share if interested.
I keep winding up at that github page. The gcode shown there does not work for DUAL Mode on the SV04 like it says it does. A lot of it is commented out.
Does anybody have real working gcode for the SV04 DUAL Mode for Orca Slicer?
I would greatly appreciate it.
Hello,
You should ask @Bjoern who is the SV04 expert.
Unfortunately, I don’t know if he’s also an Orcaslicer expert.
Regards
Hi there,
my SV04 gets his print jobs via SD-card & I’m not using any kind of 3D-printer host.
Anyhow, Marlin host support is enabled in my firmware version.
In order to manage expectations: Some SV04 modes that can be set via touch screen are different from Marlin’s native dual extruder modes that could be set via g-code M605: Single mode 1 & 2 have been implemented on top of dual mode, which offers two different options:
M605 S1 will activate the auto-park mode. The firmware takes care to park the inactive extruder in this mode. A full control mode can be activated by M605 S0 In this mode your slicer settings will have to avoid extruder crashes.
Enabling the SV04 mode would be feasable by changing the M605 implementation. I’m still reluctant to do that.
Good luck!
Björn
Well, that repository hasn’t changed in 2 years, and there is one open issue and one open pull request, so it looks like the author has abandoned this repository.
Still, it isn’t too hard for any interested Sovol SV04 owner (I’m not - I have a SV07+) to generate working .gcode files with a slicer she / he knows to be working (Cura for example) and compare that output to the output Orca Slicer generates, thus being able to compare, find differences and fix the problems.
I finally figured it out.
To get OrcaSlicer to change from one extruder to the other, I used the gcode at the filament level.
Thet “advanced” tab in the filament definition is where the gcodes go. So for each filament, I assigned T0 for the left and T1 for the right extruder.
Then I placed a few more lines of gcode under that. It works!
It’s a little cumbersome since you may change filaments. I just have the gcodes in a text file and copy them in.
I hope this helps somebody. If you have a better solution please let me know.
1 Like
It’s because you’re using a profile based on a single extruder machine.
I’ve created a new machine based on “MyToolChanger 0.4 nozzle” with Marlin 2.0 and it works absolutely perfect.
It also adds some (rather useless) Ooze Prevention, tool change times which give you real print time and so on.
No need to have any custom filament code as T0 and T1 are issued automatically and change the heads.
I am using Bjoern’s FW of course. My Orca is 2.2.0
1 Like
@Bjoern can you post your orca profiles?
Hello anon137,
negative - I don’t use any kind of print server.
There are some Orca profiles available in the German 3D printer forum - you might need to sign up there in order to download them. Here are the links to the latest threads that contain additional information about the profiles & the download links:
/R
Björn
@Bjoern I can’t get my SV04 to print with your firmware. When I try to print (Single Left), it gets up to temp, homes, then moves the right extruder to the left just a bit and turns it to 170, after it gets to temp the pause print screen comes up and it starts beeping. Thank you!!!
Hi again,
your observation indicates missing filament. Ensure that both filament runout sensors are loaded at least with a piece of filament & that they are both lit. Alternatively, unplug the runout sensors.
/R
Björn
1 Like
Thank you so much for your help again. I got it to do something different, but now it when it gets up to temp then goes above and then drops back down and just keeps doing that repeatedly.
Hi again,
your problem description lacks precision. Assuming that neither your slicer settings nor your print server scripts are the problem source, running PID-tuning might help:
Settings → Extra settings → Left nozzle PID
Settings → Extra settings → Right nozzle PID
Settings → Extra settings → Hot-bed PID
Tuning temperatures should match the target temperatures of your filament type. 5 tuning cycles should be sufficient.
Good luck!
Björn