ArcWelder PostProcess

[mberlinger3]

Hey guys I made a quick post-process script for arcwelder in superslicer on linux. I run fluidd in a container so I didn't really want to have to install octoprint. This will replace the original g-code file.

#!/usr/bin/python

import sys
import os
import subprocess

path=<path to unarchived root of arcwelder>
binFile = 'bin/ArcWelder'
logFile = 'log.txt'


logPath = os.path.join(path,logFile)
binPath = os.path.join(path,binFile)

sourceFile=sys.argv[1]

out = subprocess.check_output([binPath, sourceFile])

with open(logPath,'wb') as log:
    log.write(out)

[thebrelon]

hi!
we are currently looking into arc welder with a small group of 3d printers. we use super slicer and would be interrested to see arc welder being integrated into super slicer, kind of like it is in cura, with the ability to tweak settings like resolution.
do you thing that's doable and would devs would dig in it?

thanks
new to github, don't know much about the uses here, sorry

[mberlinger3]

Hey glad to see someone else using arcwelder. I used a postprocessing script as a stopgap solution (with defaults) because it is easy to implement.

I am not sure how cura integrates it but it is more than doable from a development standpoint. There is no reason the binary cannot be included with super slicer and have the options in the GUI. It would be up to the devels to do this but I think there is an active feature request already.

Alternatively, my script can also be customized by passing more args into the subprocess call (i.e. for resolution adjustments) if needed.

[supermerill]

@lordofhyphens is working to integrate it.

[salocain]

i put arcwelder bin in the "bin" folder of superSlicer and i just add "post proccesing script" link to arcwelder.

everithing work well ,but no setting ,ok

[salocain]

but integrate the "ARC" function it's to be great

like kisslicer for exemple

[DzzD]

I have tried using ArcWelder as a post processing in SuperSlicer and this is definitely a feature that must be added to SuperSlicer with only some few parameters available it will be a must.

From my tiny experience & tests it give :

• smaller gcode
• smoother print and surface
• faster print
• resolve problem caused by "Printer=>Minimum extrusion length" too low on high definition model

[inspectionsbybob]

Arcwelder is easy to implement, just download the standalone version, and then point at it in the post processing section, and it becomes automatic when you save. It does take some time so it isn't invoked until you save so you don't waste cycles if you forgot an edit...

My Post Processing script is:
C:\Users\Bob\ArcWelder.exe -g ;
Works just fine....

[DzzD]

Yes I know and that's what I already do, but I was meaning fully integrated in GUI with some settings, but also with the produced gcode in the preview gcode window (and the time computed also)

[supermerill]

I think it's already in the gcode preview. The gcode preview should read the gcode after the post-process.
It discretize the arc into small strait segment, like a firmware may do. It's not too small to avoid slowing the preview with too many triangles.

[DzzD]

But I only see ArcWelder popup cmd when I save the gcode to my SDCard, so I believe it is not executed when generating gcode but only when saving it no ?

[supermerill]

mmm, you're right.
When i added support for G0, maybe that was for loading the generated gcode in the standalone gcode-viewer.

[kubark42]

@inspectionsbybob, thanks for the tip! On macOS, it worked perfectly to:

• put ArcWelder into ~/Library/Application\ Support/SuperSlicer/ and then ...
• ... add ~/Library/Application\ Support/SuperSlicer/ArcWelder -g ; into Print Settings --> Output options --> Post-processing script.

One question: what is the ; doing on the end, though?

[DzzD]

I would like to add a recomendation for the G-code viewer : even if G2/G3 curves are rendered with small segments it should only count for one instruction when sliding horizontaly in G-code viewer (this is what Simplify 3d do and it is IMO usefull for user to understand what happen). (sidenote : in the G-code window viewing the text corresponding to the actual line/curve G-code in a popin would be nice to)

[neophyl]

The gcode for the current cursor section has been added to PS 2.4 so when that's merged in future that should also appear in the gcode viewer in SuSi.

Basically if it is in new versions of PS then its likely to make it into Susi too in the future.

[DzzD]

Sorry I am new to Super Slicer and dont undestand yet well all the connection between all parts of the project like Slic3r and other, so what is SuSi ?

[neophyl]

SuSi is the short form of Super Slicer. People us PS as a shorthand for Prusa Slicer but naturally Merill didnt like SS being used as a shorthand for Super Slicer given the historical use of that short form in many parts of the world. So SuSi/Susi

[DzzD]

Ha ok :) and I suppose PS is for Prusa Slicer.

So SuperSlicer is based on Prusa Slicer wich is based on Slic3r that's it ?

[supermerill]

yes.

[inspectionsbybob]

the last ";" was either in the ArcWelder documentation or a typo, in either case it is in all of my profiles and it works, so I leave it alone....