You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The following fix is causing an issue with TinyG: #38
Apparently, G3 commands for full circle are not interpreted correctly by TinyG if there are XY values in the command, here is an example:
G3 X10.64 Y18.93 I0.5000 <- current code after above fix
G3 I0.5000 <- Previous code before fix
I totally forgot how G3/G4 commands work, I need to do some reading to find a solution.
Apparently, not all controllers handle those commands the same way! Is it better to switch back to G1 and breaking the path to multiple segments?
The text was updated successfully, but these errors were encountered:
You could break into half circles or 1/3rd circles too. Those seem to be
interpreted in a more consistent way out there. And, of course, G1 moves
are what I always went with because I thought they were brainless, but they
do sure bloat the Gcode.
The following fix is causing an issue with TinyG:
#38
Apparently, G3 commands for full circle are not interpreted correctly by TinyG if there are XY values in the command, here is an example:
G3 X10.64 Y18.93 I0.5000 <- current code after above fix
G3 I0.5000 <- Previous code before fix
I totally forgot how G3/G4 commands work, I need to do some reading to find a solution.
Apparently, not all controllers handle those commands the same way! Is it better to switch back to G1 and breaking the path to multiple segments?
The text was updated successfully, but these errors were encountered: