home.social

#arcwelder — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #arcwelder, aggregated by home.social.

fetched live
  1. 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

  2. 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

  3. 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

  4. 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

  5. A few days ago, we spoke about . I used the plugin, so since I switched to , 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

  6. @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

  7. @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

  8. @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

  9. @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

  10. @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

  11. Does anyone know if the #ArcWelder plug-in for @octoprint is still being developed. Hasn't been updated since 2021 on their GitHub page.

  12. Does anyone know if the #ArcWelder plug-in for @octoprint is still being developed. Hasn't been updated since 2021 on their GitHub page.

  13. Does anyone know if the #ArcWelder plug-in for @octoprint is still being developed. Hasn't been updated since 2021 on their GitHub page.

  14. @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

  15. @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

  16. @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

  17. @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

  18. @stooovie

    It isn't as bad printing from an SD card or but still occurs. Even 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 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 , using 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

  19. 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

  20. 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

  21. 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

  22. 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

  23. 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 we use like and 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 file is processed further after it was created.

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

    @3dprinting

  24. This GCode Post-Processor Squeezes Lines into Arcs - When the slicer software for a 3D printer model files into GCode, it’s essentially creating a sequen... - hackaday.com/2020/11/03/this-g #gcodepost-processing #3dprinterhacks #3dprinter #arcwelder #octolapse #gcode

  25. Fuel From Water Using Only an Arc Welder - Water, high currents, blinding balls of plasma, and a highly flammable gas that’s toxic enough to ... more: hackaday.com/2020/04/26/fuel-f #chemistryhacks #carbonmonoxide #mischacks #arcwelder #gasometer #hydrogen #watergas #carbon #plasma #arc #hho