Hi everybody,
i am having a hard time trying to use G2 and G3 in a selfmade GCode. It seems to read the G2 and G3 command, but ignores all G1 and G0 after those arcs.
Does Luban support G2 and G3 that at all?
Here’s the gcode:
This request has been forwarded to our firmware developer, @scotthuang . He also is in charge of our GitHub repository. We will make sure if we will add G3 nearly.
Hi there. Is there any update on this issue, please? I could really, REALLY do with being able to use the G2 and G3 moves as the incessant G0 Z1.00 G1 Z-1.00 F200 lift and plunge at the end of EVERY tiny arc segment is doing my nut in!
Alternatively, and other than manually editing the Gcode files, is there any way of tweaking how the backend of Luban writes the Gcode? Id like to stop it doing so many needless G0 Z++ moves - I reckon its tripling the machining time.
Huh, it shouldn’t be retracting between G1 segments… Is that actually how luban is slicing things?
G2/G3 should just be moving the arc segmentation down to the firmware, so I’ll not sure how much benefit it would provide, especially if the processor on the SM is slower, it might even be better to be streaming gcode segments instead of the controller trying to compute the segments on the fly (but there’s other benefits to doing that processing in the firmware layer).
This is in 3axis CNC, and it is Gcode built by Luban. I use Solidworks CAM and I can’t get it to post- without using G2/3 moves. I have got a bit of software that converts arcs to lines, but it’s all a bit of a ballsache using several bits of software. I get that Luban will never be DelCAM, but I’d like to have a LOT more configurability on hand without resorting to rebuilding it all from GitHub!
The powerful search/replace functionality of notepad++ is beginning to make it a go-to editor…