A few days ago, we spoke about #ArcWelder. I used the #Octoprint plugin, so since I switched to #Klipper, I dont have the neativ feature, and I haven't set it up as a post-processing script yet in my slicer.

The lack of ArcWelder is clear: You'll see that the circle in the back of this Preasure Advance tower is very blocking, I would never get this with Arcwelder

@3dprinting #3dprinting

@Siff @3dprinting

It depends on your geometry and speed. It js possible that you get an increase in centripetal force because of the circular motions, so I would decrease the maximum speed and acceleration by a bit and try again.

I've not had any negative effects using #ArcWelder

@wookiearocket

The argument about whether to use post-processors or implementing it directly in the slicer is similar to the argument of addons, mods, and plugins to existing software.

I like the idea of post processors, and #ArcWelder is by far my favorite.

During my time in the space, slicers have gone from not being able to print round circles to organic supports released the last few weeks.

The idea behind ArcWelder is amazing.

One benefit about post-processors is that you can improve existing #Gcode after they were created and improve them without having access to the original model.

@MaryPot

@3dprinting #3dprinting

@stooovie

It isn't as bad printing from an SD card or #Klipper but still occurs. Even #Klipper can lag behind. It comes down to, too high, that a resolution could literally result in 1000s of G1 movements for tiny circles. Say what you want, but even Klipper can't handle that. Because Klipper would still do 1000s of G1 movements.

G3 movements replace all of those 1000s mocements to an actual circular movement and also to a single command.

So even if you don't see the bulges, your #Gcode will be compressed in the sense that it reduces the total amount of commands.

I once had a 34-hour print, which was about 40MB in #Gcode, using #ArcWelder and replacing all of the circular motions with G3, I reduced the size to 17MB on Gcode. More than 50% compression, which helps a lot when you have a cheaper 8-bit printer, will very little RAM.

It's the law of big number, the less lines you have, the less possible things can go wrong.

@3dprinting #3dprinting

#ArcWelder on #github:

https://github.com/FormerLurker/ArcWelderLib

#ArchWelder plugin for #octoprint:

https://plugins.octoprint.org/plugins/arc_welder/

Color me impressed!!!

So how did I do this?

Well, as you saw in the videos, not all circular mocements were converted, and without this technique, none of them are. Why is that?

Well, the #Slicers we use like #Cura #PrusaSlicer and #Superslicer need to "slice" or models. This converts the 3D model from its original format to the tool paths of the printer.

These software are insanely complex, and they dont recognize circles easily. They basically just find the shortest straight path with the least amount of deviation from the original curve.

Some slicers do use arc movements, but it is better to do it in post-processing.

Post-processing is when a sliced #Gcode file is processed further after it was created.

The tool I use for this is #ArcWelder. You can either download and use a #Python script or use an #Octoprint plugin to do it automatically for you.

@3dprinting #3dprinting

We use #Octoprint and #ArcWelder to compress the #GCode and improve the quality!

#3DPrinting folks, how do you like to use Arc Welder?

I want to give it a shot but wanted to see if people liked it as a PrusaSlicer post processing “script” or as a @octoprint plugin more?

🏷️: #prusa #octoprint #arcwelder