New release (anyone who forked please do a pull) - Added heated bed temperature control. PrusaSlicer would assign sometimes assign wrong temperature to the heated bed. Script now cleans up the heated bed gcode from PS (M140 and M190 commands) and adds the M140 and M190 commands to set the temperature that is MAX of all heated bed temperatures of filaments in use - Changed the behaviour of the PrimeTower generation. Now if the prime tower is padded at the end of Tool printing process, printer will not do an extra move to the previous position
I did reslice my current project with the new version and the print is ongoing. Rightnow everything seems to be ok. Some detail about the priming tower: - I still have the feeling that the amount of material is somehow off when the base plate for the priming-tower is being printed. It always seems to be some sort of overextrusion (while the actual part seems to be ok). Might this be connected with the number of edges? (I didnt look at the generation algorithm so far.) - When printing PETG with PLA as support: Whenever the base plate for the priming tower is made of PLA and the next ful baseplate layer is PETG it is a mess. Because the PETG does not stick to PLA and build up some tiny blob which is dragged around circular. It would be perfect if the base plate is always the same extruder. Or maybe generated with different extruders rings which consist of the the same material piled up. Maybe it would be perfect if we have multiple rings in the baseplate because there is always some material that sticks best to the print bed. When I print the upper part of the priming tower the print works ok. Did you as well experience these problems with the priming tower?
Hi, no - not really but it may be related to the order of extruders/materials. I will check that code later on and have a look. Might redo the code for the prime tower brim generation to make it more robust. As for the overextrusion issue - it may be related to the fact that algorithm tries to create a ful circular infill on the base of prime tower. I will add it to my notes to change it so - rather then full infill do n-ammount of rings on each side (using the outermost materials) This should provide structural integrity - without creating too much mess.
Sorry, is this active still? I get an error parsing; [Error] Setting retraction state while no tool is active no idea how to fix this. Using new Prusaslicer 2.3 Optional question, if i may: Why are the M104 Snn and M109 Snn used instead of G10 Snn Pnn and M116 Pn ?
Hi it is I was relocating from London to Munich - please provide more details. Single error message is not enough - whole output would help.
Hello, I had time to fix the issues - so today (14/03/2021) there is a new release, please check it out from the github; - Changed the M104 gcode (deprecated) to G10 for temperature control - Fixed the G10 gcode retraction detection to differentiate between G10 (no params) retraction and G10 for temp control - Changed the logging to use python logging, settings are configured in logging.conf, logging is now outputing to console and tcpspp.log files - Tested the post processing script with PrusaSlicer 2.3, script now works with both the new RepRapFirmware g-code flavour as well as the old RepRap/Splinter G-code output
Also includes a fix for: - extrusion amount for prime tower generation - fix to PrusaSlicer G10 generation, when only first tool is used
Something I've noticed on my IDEX machine. If printing with just the first tool, PrusaSlicer sets the temperatures (bed and hotend) to the temperatures of the filament selected for the second filament. Nothing to do with the post processing script, just thought I'd mention it incase it caught someone else out. Unless I'm missing something, the post processing script appears to ignore any Z offset set in Printer Settings - General. The PrusaSlicer does a G1 Z including any Z offset but the G1 Z in the prime-tower (;TC-PSPP - TXXX - Pillar - Start) doesn't include the offset.
Hi, I know this thread is a little old, but I have some question about your script. -Will it work on superslicer? -And is there a defenition of errors? It prompt me error 2 can't figure what cause it -Will it work without the tower? Thanks
I encountered some problem after updating to PrusaSlicer 2.5 / 2.6.1 I did not yet search for any solution yet, but wanted to document the bug here.
I did print some prints with the script. The main usability problem I had is that I always forget to move the tower to a place where it does not overlap with the actual print. That is a bit fiddly.