RE: script to drop temperature during ramming
I have a new MMU2S and this helped me so much with my tips for PETG, thank you! Before I started using the script the PETG was so stringy.
Not sure if anyone is still working with script or not, but the problem that I'm having now is that the cool temp that I'm having to use (225) is so low that the purge block is not working well - the temp is so low that the filament extruded onto the purge block doesn't adhere well (it tends to stick up), and subsequent prints to the purge block will then come in contact with filament on that block that didn't lay down well.
Any suggestions?
RE: script to drop temperature during ramming
@greg-whitehead
https://github.com/antimix/PrusaSlicer/releases
www.antalife.com
RE: script to drop temperature during ramming
Thanks - I had seen your PrusaSlicer with Dribbling, but haven't tried it yet. Any chance you're going to update to 2.3.0? I'm using the paint on supports quite a bit.
Are people using the PrusaSlicer with Dribbling successfully with PETG? What PETG and what filaments settings are you using? So far I've tried Atomic and Overture PETG with this script (as well as lots of experimentation without the script), and it has fixed my issues with stringing tips, but now all kinds of issues with the purge block (because the print temperatures are much lower when purging).
RE: script to drop temperature during ramming
I've read through this forum and can't quite pin point how to run/configure this script. I am trying to get good tips on my MMU3 with petg. I've currently got it printing OK at 223c but strings are causing jams after about 100 filament changes. I'm running on windows and I've installed python. I've changed the start of the python script to where my python is installed. If anyone has some screenshots from prusa slicer post processing window or can lay out the steps exactly as to how to make it work, that would be helpful.
"#!C:\Users\myuser\AppData\Local\Programs\Python\Python311 python"
In Prusaslicer, under the "Post-processing scripts" of print settings I input "C:\Users\myuser\Downloads\cool_ram.py -t 205"
Doing this prusaslicer throws an error "Failed starting the script C:\Users\myuser\Downloads\cool_ram.py -t 205 C:\Users\myuser\AppData\Local\Temp\.26916.gcode.pp, Win32 error: 193"
Is this the correct way to make this script work? I've also tried manually in powershell and command prompt. Command prompt throws an access denied error(I have full control over all the files involved) and powershell does nothing.
RE: script to drop temperature during ramming
It seems like you're trying to use a Python script to post-process G-code generated by PrusaSlicer for your MMU3 with PETG filament. However, there might be some issues with your approach and configuration. Let's break down the steps and troubleshoot the problems you're encountering:
Script Configuration:
The shebang line at the beginning of your script looks correct, pointing to your Python installation.Make sure your Python script (cool_ram.py) is saved in the correct directory (C:\Users\myuser\Downloads in this case).
Post-Processing Configuration in PrusaSlicer:
It's important to provide the full path to the Python script when specifying it in PrusaSlicer.However, it seems you're trying to pass arguments to the script directly within the path. PrusaSlicer's post-processing scripts don't work this way.
Here's how you should set up the post-processing configuration in PrusaSlicer:
Save your Python script in an accessible location, for example: C:\Users\myuser\Documents\cool_ram.py.
In PrusaSlicer, go to "Printer Settings" (not Print Settings) and then "Custom G-code."
Scroll down to the "End G-code" section and add the following line at the end of your existing end G-code (if you have any):
javaCopy code; Post-processing script M117 Cooling RAM system('C:\Users\myuser\Documents\cool_ram.py -t 205')
Note: Make sure to adjust the path to the script and the desired temperature (-t 205) accordingly.
Save your printer profile settings.
This configuration will run the post-processing script after the print finishes, and it will use the system command to execute the Python script with the desired arguments.
Regarding the errors you're encountering:
Access Denied Error: Make sure that the user account running PrusaSlicer has the necessary permissions to access and execute the Python script. Right-click on the script file and check its properties to ensure the necessary permissions are granted.
PowerShell Not Responding: If you're testing the script in PowerShell and it's not responding, ensure that you're running the correct command, including the full path to the script. You might also want to check the script's content to see if it's expected to produce any visible output.
Remember to troubleshoot one step at a time. Verify that your script works when run directly from the command line, and then implement it into PrusaSlicer's post-processing accordingly. If you're still encountering issues, consider seeking help on Prusa forums or related communities, where users with similar setups might provide further guidance.