Having some experience of writing code but being new to G-Code I struggle to understand which command that forces the SV04 to switch extruders in Dual Print mode. I have reviewed Dual Mode .gcode files but fail to find the exact lines that tells the SV04 to park one extruder and activate the second one. All I find is a “T1” command in the beginning of the file activating the second extruder loaded with support filament. There are no “T0” commands whatsoever in the file. What am I missing?
Hi Ekkehard,
you are looking for g-code M605 S1 which is documented here, however, the M605 implementation in the SV04 firmware differs from the Marlin firmware it has been derived from. The safest way to chose the print mode is using the touch display.
/R
Björn
Thanks for your help. I realize that I have still a lot to learn when it comes to even understanding how all of this works. I was under the impression that the slicer puts out a file with a “Start of Print” code, the actual print code and the “End of Print” code, and that the code is universal meaning that the different commands are interpreted equally ny different printers. By looking at the gcode file I would then be able to understand exactly what the printer does.That is obviously not the case…
Anyways, I will use your firmware. Can I use Cura or do you recommend the Prusa slicer? In which order do I need to load the firmware, main board first and display second?
Hi Ekkehard,
the firmware does not care about the slicer at all.
Usually there are slicer profiles for each print mode, that might have individual code blocks for each stage of the print process & profiles for each type of filament… I could upload my PrusaSilcer configuration bundle here if you like.
The software installation order does not matter. In case your SV04 dislikes your SD-card or MicroSD-card during the update process the firmware wiki will guide to further information. Or just ask…
Good luck!
Björn
G-code certainly isn’t universal; which codes that are actually implemented, and how they work, varies a lot among different printer manufacturers. Unfortunately, that is currently the way things are.
If you would upload your PrusaSlicer configuration that would be real nice. Looking at the printers behaviour executing a .gcode file produced with the Cura slicer there are a couple of things I do not understand (could be me though). So I figured I will test the Prusa slicer instead.
Hi Ekkehard,
there are hundreds of options that come with a slicer. Understanding the options in a way that benefits your current use case will take its time. Good documentation will be quite helpful.
I attached my config bundle for PrusaSlicer 2.8.0 below. Import is quite simple:
Menu > File > Import > Import Config Bundle…