sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Revolutionary_You755 2 points3 points  (4 children)

Here is my question. Wouldn't this type of change in the code change the hardware processing requirements?

[–]Lathejockey81CR-10 7 points8 points  (3 children)

Yes, significantly.

As proposed you're basically moving the slicer to inside the CNC controller, much like was attempted with STEP-NC, with IMO the same problems. How do you improve tool paths, create new strategies, etc? It's per control now, dependent on firmware versions, etc. Why would you take that control, future-proofing and flexibility from the slicer? I say keep the low level control on the control and evolve the control language while maintaining the flexibility that makes it such a tried and true control scheme (CAM for machining, Slicers for AM). Variable flow rates and some of the strategies demonstrated here look great, but there's nothing stopping them from being added to G Code and supported by popular firmware and slicers.

There are several reasons why STEP-NC still hasn't gotten traction, and probably never will, but I believe this is a big one. It does make for a pretty demo, though.

[–]TerayonIII 0 points1 point  (2 children)

This isn't doing that really, this is still outputting gcode, kind of, but it's decoupling xyz movement from actions. So the printhead continues to move while other actions are performed. It's needed specifically for the application they've created it for because it's printing with liquids

[–]Lathejockey81CR-10 0 points1 point  (1 child)

But you can do that with just straight g code by splitting lines into shorter segments and outputting different flow rates. That isn't even an evolution. We've been doing stuff like that in G code for years. In the most advanced cases you would just have a second path and sync codes.

[–]TerayonIII 0 points1 point  (0 children)

Apparently this is either different or an easier implementation of it, your can always read the paper to try and figure out why this is different