MK3 with PRUSASLICER 2.0 big retraction at start
Just upgraded slicer to Pruserslicer 2.0 as I wanted to try the stop and change filament feature to manually change colours.
Turned out to be a bad move as I lost some of my profilers. Later found the instruction to retreive them, but not all were there. Never mind, I'll live with that.
Real issue is that with all gcode files produced by Prusaslicer 2.0 causes a HUGE extruder retraction while it is moving in to do the bed calibration just before starting the print. It retracts so much that it takes more than a few minutes to recover whilst printing before the filament returns.
I cannot find any specific outstanding G code that in the file that is doing this. There are many G1 codes near the start but haven't identified which is the culprit.
I cannot find a command in Prusaslicer 2.0 software that is doing this either. It is definitely the software, because I can successfully print any number of my older gcode files made with the old slicing software.
Does anyone have any ideas.
[...] Real issue is that with all gcode files produced by Prusaslicer 2.0 causes a HUGE extruder retraction while it is moving in to do the bed calibration just before starting the print. It retracts so much that it takes more than a few minutes to recover whilst printing before the filament returns.
Have you selected a MMU2 configuration? The default PrusaSlicer 2 without MMU2 profile does not do such a retraction at the start.
[...] I cannot find a command in Prusaslicer 2.0 software that is doing this either. It is definitely the software, because I can successfully print any number of my older gcode files made with the old slicing software.
Does anyone have any ideas.
At this point, I'm wondering if you're using an MMU2. Other than that, all startup movement should be in the gcode file. Are you using Octoprint or any other means of printing besides directly off the SD card?
Thanks for reply.
Stock I3Mk3 no MMU, printing straight from SD card.
To be clear, I have gone to basic test, just printing same model, one sliced by the old slicer software - works fine. The other with Prusaslicer 2.0, no special stuff, just a basic print - as soon as it starts moving to the front left corner to do the calibration a bunch (perhaps 20 or 30mm) of filament retracts. It gets a good way through the print before the filament catches back up again.
I have been comparing the gcode manually from both slicers. Both very different layout of code, but in general I have spotted any relevant g-code difference yet.
I'm sure it will be something stupid, but I have spent probably 4 hours so far investigating it without any luck.
Okay, think I have nailed it.
Was something stupid but surprised the installation or software did not walk me through it the first time.
THE CONFIGURATION WIZARD - I did not do this step, only just found it in the menu. Now I have selected a base standard Mk3 printer, much has changed. The lost predefined profiles have reappeared (and mine are still there too).
About to do a test print but confident it will work.
Will advise shortly.
Cheers to you bobstro you led my thinking to the right spot.
Okay final result, all fixed. Although, it was not as straight forward as my last post above. There seemed to be a conflict or corruption with the software and/or profiles which still caused the extreme retraction before print.
I knew it was something to do with the configuration (blaming myself here), so decided to backup all my profiles ( 🙂 ), then uninstall all the slicer software off the computer completely, and then do a clean installation, re-copy my old profiles back in and then CAREFULLY run through the setup wizard and other config selections.
Almost always...."blame the human".
A lot of time to sort out but lessons learnt.
Once you have it working do an export config bundle. That way if it happens again or if you try one of the alphas/beta versions you can just import config bundle and get all profiles back without any manual copying required.
My MK3S (upgraded with Bondtech Extruder and all the new MK3S goodies) does a HUGE retraction when it first loads the filament into the extruder gears. The problem is the retraction pushes the filament completely OUT of the gears so it cannot be pulled back in.
What is causing that so I can edit the firmware to make it stop moving so far back.
it's the feed check i think - do you have the IR sensor door in that extruder?
the mmu2s mk3s config feeds till the IR sensor trips then feeds almost to the nozzle and retracts back almost to the bondtechs to check that the extruder loaded correctly
It is a steel ball the gets pushed to the side by the filament and trips the sensor just above the teeth.
It retracts too far, pulling clean out of the teeth so they lose their grip.