ENDER 3 V3 SE Using 'Github' Profile + PrusaSlicer
I have a few MK3S+ machines, and use Prusaslicer ONLY. Its great. works for me. Know where everything is..
but I got a couple ENDER machines Id like to get running well to pick up some slack..
Using a homeade github download profile someone made that gets the job done for the V3 SE . .gives me a few preset
profiles, and seems to print fine... HOWEVER it has no bells and whistles built in, mainly the way it does Color changes
from a Prusaslicer generated gcode.
Long story short it pauses for the color change, but thats about it, it retracts for filament release, and pauses.
My Neo and other Ender printers which had approved profiles I got from Prusa, when they pause for color change
it is a guided on screen process , like the mk3s... press this, press that, wait for purge, which makes it soooooo much easier, to know
whats going on, with my v3 se newer model , it just pauses, retracts and waits for me to hit the buttons, no purge, just waiting for me to
press go after ive changed the filament.
long story short , is there a few lines of gcode i could add to this already built githib profile im using that will... move over, pause. tell me to insert ,wait for purge, guide me thru , like the rest ??
if anyone knows, itd be a lifesaver, believe it or not this v3 se prints awesome and FAST.. and is doing bulk items quite well, just that damn color change is always a ok whats it waiting for .
thanks in advance. i use prusaslicer for every printer i get, no matter brand. if i can.
= C
RE: ENDER 3 V3 SE Using 'Github' Profile + PrusaSlicer
Dont think so but you could compare the prusa slicer output for the change for gcode files for your different machines.
Been awhile since I had a creality printer but there was tremendous variability on firmware between then. I suspect the PS is just emitting the usual M600 code or similar and that its the firmware that is then taking over and doing the rest. Thats the normal way it works with most machines. PS just says 'change filament' (whatever the command the firmware expects is what needs to be added to the gcode fields in PS) and then lets the firmware deal with it.