Replies: 2 comments 1 reply
-
There are three units in play, the gcode state (G20/G21), the reporting units ($13) and the units displayed in the UGS UI. To avoid all confusion, UGS will convert the There is no need to set the If you run this gcode, it should move one inch. If it doesn't it might mean that your machine isn't calibrated properly and you need check the GRBL settings.
|
Beta Was this translation helpful? Give feedback.
-
I think I figured it out. Typing $N0 = G20 into the command line of UGS does fix the problem. Turns out CamBam was inserting G64 at the top of the Gcode on the same line as it put G20 and UGS was ignoring that line. |
Beta Was this translation helpful? Give feedback.
-
I got tired of using Win 7 with Mach 3 and a parallel port. With a new PC, GRBL USB interface and UGS I need help. Trying one of my gcode files it looked like it was running in mm, not inches. I have $13 set to 1 and G20 was at the top of the gcode. From info in a closed topic it says to put in a startup line of $N0 = G20. I think if I type that into the command window that UGS will send that to GRBL at every startup. Do I just type that into the command line? Will UGS send it to GRBL each time I connect with UGS? The Mach3 mm/in changover was much different.
Beta Was this translation helpful? Give feedback.
All reactions