Menu
▾
▴
[Emc-commit] v2.5_branch: Docs: markup fixes
|
From: John T. <gi...@gi...> - 2011-12-14 14:41:36
|
Docs: markup fixes Signed-off-by: John Thornton <jth...@gn...> http://git.linuxcnc.org/?p=emc2.git;a=commitdiff;h=fbb6b6e --- docs/src/gcode/coordinates.txt | 28 +- docs/src/gcode/coordinates_de.txt | 48 ++-- docs/src/gcode/coordinates_es.txt | 40 ++-- docs/src/gcode/coordinates_pl.txt | 28 +- docs/src/gcode/gcode.txt | 439 ++++++++++++++++--------------- docs/src/gcode/gcode_de.txt | 441 ++++++++++++++++--------------- docs/src/gcode/gcode_es.txt | 441 ++++++++++++++++--------------- docs/src/gcode/gcode_pl.txt | 441 ++++++++++++++++--------------- docs/src/gcode/tool_compensation.txt | 18 +- docs/src/gcode/tool_compensation_de.txt | 18 +- docs/src/gcode/tool_compensation_es.txt | 18 +- docs/src/gcode/tool_compensation_pl.txt | 18 +- 12 files changed, 999 insertions(+), 979 deletions(-) diff --git a/docs/src/gcode/coordinates.txt b/docs/src/gcode/coordinates.txt index 5b82b89..2bbdadd 100644 --- a/docs/src/gcode/coordinates.txt +++ b/docs/src/gcode/coordinates.txt @@ -24,7 +24,9 @@ Regardless of any offsets that may be in effect, putting a G53 in a block of code tells the interpreter to go to the real or absolute axis positions commanded in the block. For example - G53 G0 X0 Y0 Z0 +---- +G53 G0 X0 Y0 Z0 +---- will get you to the actual position where these three axes are zero. You might use a command like this if you have a favorite position for @@ -95,7 +97,7 @@ reference for each of the locations and all of the work to be done there. The following code is offered as an example of making a square using the G55 offsets that we set above. -------------------- +---- G55 G0 X0 Y0 Z0 G1 F2 Z-0.2000 X1 @@ -105,9 +107,9 @@ Y0 G0 Z0 G54 X0 Y0 Z0 M2 -------------------- +---- -"But," you say, "why is there a G54 in there near the end." Many +But, you say, why is there a G54 in there near the end. Many programmers leave the G54 coordinate system with all zero values so that there is a modal code for the absolute machine based axis positions. This program assumes that we have done that and use the @@ -117,7 +119,7 @@ not have been modal and any commands issued after it would have returned to using the G55 offsets because that coordinate system would still be in effect. ------------------------------------------------------------ +---- G54   use preset work coordinate system 1(((G54))) G55   use preset work coordinate system 2(((G55))) G56   use preset work coordinate system 3(((G56))) @@ -127,7 +129,7 @@ G59   use preset work coordinate system 6(((G59))) G59.1 use preset work coordinate system 7(((G59.1))) G59.2 use preset work coordinate system 8(((G59.3))) G59.3 use preset work coordinate system 9(((G59.3))) ------------------------------------------------------------ +---- === Default coordinate system @@ -182,8 +184,8 @@ much as you would expect. A user must understand the correct ways that the G92 values work. They are set based upon the location of each axis when the G92 command is -invoked. The NIST document is clear that, "To make the current point -have the coordinates" X0, Y0, and Z0 you would use G92 X0 Y0 Z0. +invoked. The NIST document is clear that, To make the current point +have the coordinates X0, Y0, and Z0 you would use G92 X0 Y0 Z0. G92 'does not work from absolute machine coordinates'. It works from 'current location'. @@ -216,7 +218,7 @@ There are at least two ways to set G92 values. Both of these work from the current location of the axis to which the offset is to be applied. -Issuing `G92 X Y Z A B C U V W` does in fact set values to the G92 variables +Issuing 'G92 X Y Z A B C U V W' does in fact set values to the G92 variables such that each axis takes on the value associated with its name. These values are assigned to the current position of the machine axis. These results satisfy paragraphs one and two of the NIST document. @@ -225,10 +227,10 @@ G92 commands work from current axis location and add and subtract correctly to give the current axis position the value assigned by the G92 command. The effects work even though previous offsets are in. -So if the X axis is currently showing 2.0000 as its position a `G92 X0` +So if the X axis is currently showing 2.0000 as its position a 'G92 X0' will set an offset of -2.0000 so that the current location of X becomes -zero. A `G92 X2` will set an offset of 0.0000 and the displayed position -will not change. A `G92 X5.0000` will set an offset of 3.0000 so that the +zero. A 'G92 X2' will set an offset of 0.0000 and the displayed position +will not change. A 'G92 X5.0000' will set an offset of 3.0000 so that the current displayed position becomes 5.0000. === G92 Cautions @@ -259,7 +261,7 @@ set as machine zero everything will be correct. Once home has been established using real machine switches, or by moving each axis to a known home position and issuing an axis home command, any G92 offsets will be applied. If you have a G92 X1 in effect when you home the X axis the -DRO will read "X: 1.000" instead of the expected "X: 0.000" because the +DRO will read 'X: 1.000' instead of the expected 'X: 0.000' because the G92 was applied to the machine origin. If you issue a G92.1 and the DRO now reads all zeros then you had a G92 offset in effect when you last ran EMC. diff --git a/docs/src/gcode/coordinates_de.txt b/docs/src/gcode/coordinates_de.txt index a07a324..2bbdadd 100644 --- a/docs/src/gcode/coordinates_de.txt +++ b/docs/src/gcode/coordinates_de.txt @@ -24,7 +24,9 @@ Regardless of any offsets that may be in effect, putting a G53 in a block of code tells the interpreter to go to the real or absolute axis positions commanded in the block. For example - G53 G0 X0 Y0 Z0 +---- +G53 G0 X0 Y0 Z0 +---- will get you to the actual position where these three axes are zero. You might use a command like this if you have a favorite position for @@ -52,14 +54,14 @@ the INI file during the startup of an EMC. In our example below we'll use (((G55)))G55. The values for each axis for G55 are stored as variable numbers. -|=============== +|============== |5241 | 0.000000 |5242 | 0.000000 |5243 | 0.000000 |5244 | 0.000000 |5245 | 0.000000 |5246 | 0.000000 -|=============== +|============== In the VAR file scheme, the first variable number stores the X offset, the second the Y offset and so on for all six axes. There are numbered @@ -72,14 +74,14 @@ this is not the recommended way. G10, G92, G28.1, etc are better ways to affect variables. For our example let's directly edit the file so that G55 takes on the following values. -|=============== +|============== |5241 | 2.000000 |5242 | 1.000000 |5243 |-2.000000 |5244 | 0.000000 |5245 | 0.000000 |5246 | 0.000000 -|=============== +|============== You should read this as moving the zero positions of G55 to X = 2 units, Y= 1 unit, and Z = -2 units away from the absolute zero @@ -95,7 +97,7 @@ reference for each of the locations and all of the work to be done there. The following code is offered as an example of making a square using the G55 offsets that we set above. -------------------- +---- G55 G0 X0 Y0 Z0 G1 F2 Z-0.2000 X1 @@ -105,9 +107,9 @@ Y0 G0 Z0 G54 X0 Y0 Z0 M2 -------------------- +---- -"But," you say, "why is there a G54 in there near the end." Many +But, you say, why is there a G54 in there near the end. Many programmers leave the G54 coordinate system with all zero values so that there is a modal code for the absolute machine based axis positions. This program assumes that we have done that and use the @@ -117,7 +119,7 @@ not have been modal and any commands issued after it would have returned to using the G55 offsets because that coordinate system would still be in effect. ------------------------------------------------------------ +---- G54   use preset work coordinate system 1(((G54))) G55   use preset work coordinate system 2(((G55))) G56   use preset work coordinate system 3(((G56))) @@ -127,7 +129,7 @@ G59   use preset work coordinate system 6(((G59))) G59.1 use preset work coordinate system 7(((G59.1))) G59.2 use preset work coordinate system 8(((G59.3))) G59.3 use preset work coordinate system 9(((G59.3))) ------------------------------------------------------------ +---- === Default coordinate system @@ -182,8 +184,8 @@ much as you would expect. A user must understand the correct ways that the G92 values work. They are set based upon the location of each axis when the G92 command is -invoked. The NIST document is clear that, "To make the current point -have the coordinates" X0, Y0, and Z0 you would use G92 X0 Y0 Z0. +invoked. The NIST document is clear that, To make the current point +have the coordinates X0, Y0, and Z0 you would use G92 X0 Y0 Z0. G92 'does not work from absolute machine coordinates'. It works from 'current location'. @@ -216,7 +218,7 @@ There are at least two ways to set G92 values. Both of these work from the current location of the axis to which the offset is to be applied. -Issuing `G92 X Y Z A B C U V W` does in fact set values to the G92 variables +Issuing 'G92 X Y Z A B C U V W' does in fact set values to the G92 variables such that each axis takes on the value associated with its name. These values are assigned to the current position of the machine axis. These results satisfy paragraphs one and two of the NIST document. @@ -225,10 +227,10 @@ G92 commands work from current axis location and add and subtract correctly to give the current axis position the value assigned by the G92 command. The effects work even though previous offsets are in. -So if the X axis is currently showing 2.0000 as its position a `G92 X0` +So if the X axis is currently showing 2.0000 as its position a 'G92 X0' will set an offset of -2.0000 so that the current location of X becomes -zero. A `G92 X2` will set an offset of 0.0000 and the displayed position -will not change. A `G92 X5.0000` will set an offset of 3.0000 so that the +zero. A 'G92 X2' will set an offset of 0.0000 and the displayed position +will not change. A 'G92 X5.0000' will set an offset of 3.0000 so that the current displayed position becomes 5.0000. === G92 Cautions @@ -239,12 +241,12 @@ offsets in effect. When this happens reset or a startup will cause them to become active again. The variables are named: |============== -|5211 | 0.000000 -|5212 | 0.000000 -|5213 | 0.000000 -|5214 | 0.000000 -|5215 | 0.000000 -|5216 | 0.000000 +|5211 | 0.000000 +|5212 | 0.000000 +|5213 | 0.000000 +|5214 | 0.000000 +|5215 | 0.000000 +|5216 | 0.000000 |============== where 5211 is the X axis offset and so on. If you are seeing @@ -259,7 +261,7 @@ set as machine zero everything will be correct. Once home has been established using real machine switches, or by moving each axis to a known home position and issuing an axis home command, any G92 offsets will be applied. If you have a G92 X1 in effect when you home the X axis the -DRO will read "X: 1.000" instead of the expected "X: 0.000" because the +DRO will read 'X: 1.000' instead of the expected 'X: 0.000' because the G92 was applied to the machine origin. If you issue a G92.1 and the DRO now reads all zeros then you had a G92 offset in effect when you last ran EMC. diff --git a/docs/src/gcode/coordinates_es.txt b/docs/src/gcode/coordinates_es.txt index 5a9da97..2bbdadd 100644 --- a/docs/src/gcode/coordinates_es.txt +++ b/docs/src/gcode/coordinates_es.txt @@ -24,7 +24,9 @@ Regardless of any offsets that may be in effect, putting a G53 in a block of code tells the interpreter to go to the real or absolute axis positions commanded in the block. For example - G53 G0 X0 Y0 Z0 +---- +G53 G0 X0 Y0 Z0 +---- will get you to the actual position where these three axes are zero. You might use a command like this if you have a favorite position for @@ -95,7 +97,7 @@ reference for each of the locations and all of the work to be done there. The following code is offered as an example of making a square using the G55 offsets that we set above. -------------------- +---- G55 G0 X0 Y0 Z0 G1 F2 Z-0.2000 X1 @@ -105,9 +107,9 @@ Y0 G0 Z0 G54 X0 Y0 Z0 M2 -------------------- +---- -"But," you say, "why is there a G54 in there near the end." Many +But, you say, why is there a G54 in there near the end. Many programmers leave the G54 coordinate system with all zero values so that there is a modal code for the absolute machine based axis positions. This program assumes that we have done that and use the @@ -117,7 +119,7 @@ not have been modal and any commands issued after it would have returned to using the G55 offsets because that coordinate system would still be in effect. ------------------------------------------------------------ +---- G54   use preset work coordinate system 1(((G54))) G55   use preset work coordinate system 2(((G55))) G56   use preset work coordinate system 3(((G56))) @@ -127,7 +129,7 @@ G59   use preset work coordinate system 6(((G59))) G59.1 use preset work coordinate system 7(((G59.1))) G59.2 use preset work coordinate system 8(((G59.3))) G59.3 use preset work coordinate system 9(((G59.3))) ------------------------------------------------------------ +---- === Default coordinate system @@ -182,8 +184,8 @@ much as you would expect. A user must understand the correct ways that the G92 values work. They are set based upon the location of each axis when the G92 command is -invoked. The NIST document is clear that, "To make the current point -have the coordinates" X0, Y0, and Z0 you would use G92 X0 Y0 Z0. +invoked. The NIST document is clear that, To make the current point +have the coordinates X0, Y0, and Z0 you would use G92 X0 Y0 Z0. G92 'does not work from absolute machine coordinates'. It works from 'current location'. @@ -216,7 +218,7 @@ There are at least two ways to set G92 values. Both of these work from the current location of the axis to which the offset is to be applied. -Issuing `G92 X Y Z A B C U V W` does in fact set values to the G92 variables +Issuing 'G92 X Y Z A B C U V W' does in fact set values to the G92 variables such that each axis takes on the value associated with its name. These values are assigned to the current position of the machine axis. These results satisfy paragraphs one and two of the NIST document. @@ -225,10 +227,10 @@ G92 commands work from current axis location and add and subtract correctly to give the current axis position the value assigned by the G92 command. The effects work even though previous offsets are in. -So if the X axis is currently showing 2.0000 as its position a `G92 X0` +So if the X axis is currently showing 2.0000 as its position a 'G92 X0' will set an offset of -2.0000 so that the current location of X becomes -zero. A `G92 X2` will set an offset of 0.0000 and the displayed position -will not change. A `G92 X5.0000` will set an offset of 3.0000 so that the +zero. A 'G92 X2' will set an offset of 0.0000 and the displayed position +will not change. A 'G92 X5.0000' will set an offset of 3.0000 so that the current displayed position becomes 5.0000. === G92 Cautions @@ -239,12 +241,12 @@ offsets in effect. When this happens reset or a startup will cause them to become active again. The variables are named: |============== -|5211 | 0.000000 -|5212 | 0.000000 -|5213 | 0.000000 -|5214 | 0.000000 -|5215 | 0.000000 -|5216 | 0.000000 +|5211 | 0.000000 +|5212 | 0.000000 +|5213 | 0.000000 +|5214 | 0.000000 +|5215 | 0.000000 +|5216 | 0.000000 |============== where 5211 is the X axis offset and so on. If you are seeing @@ -259,7 +261,7 @@ set as machine zero everything will be correct. Once home has been established using real machine switches, or by moving each axis to a known home position and issuing an axis home command, any G92 offsets will be applied. If you have a G92 X1 in effect when you home the X axis the -DRO will read "X: 1.000" instead of the expected "X: 0.000" because the +DRO will read 'X: 1.000' instead of the expected 'X: 0.000' because the G92 was applied to the machine origin. If you issue a G92.1 and the DRO now reads all zeros then you had a G92 offset in effect when you last ran EMC. diff --git a/docs/src/gcode/coordinates_pl.txt b/docs/src/gcode/coordinates_pl.txt index 5b82b89..2bbdadd 100644 --- a/docs/src/gcode/coordinates_pl.txt +++ b/docs/src/gcode/coordinates_pl.txt @@ -24,7 +24,9 @@ Regardless of any offsets that may be in effect, putting a G53 in a block of code tells the interpreter to go to the real or absolute axis positions commanded in the block. For example - G53 G0 X0 Y0 Z0 +---- +G53 G0 X0 Y0 Z0 +---- will get you to the actual position where these three axes are zero. You might use a command like this if you have a favorite position for @@ -95,7 +97,7 @@ reference for each of the locations and all of the work to be done there. The following code is offered as an example of making a square using the G55 offsets that we set above. -------------------- +---- G55 G0 X0 Y0 Z0 G1 F2 Z-0.2000 X1 @@ -105,9 +107,9 @@ Y0 G0 Z0 G54 X0 Y0 Z0 M2 -------------------- +---- -"But," you say, "why is there a G54 in there near the end." Many +But, you say, why is there a G54 in there near the end. Many programmers leave the G54 coordinate system with all zero values so that there is a modal code for the absolute machine based axis positions. This program assumes that we have done that and use the @@ -117,7 +119,7 @@ not have been modal and any commands issued after it would have returned to using the G55 offsets because that coordinate system would still be in effect. ------------------------------------------------------------ +---- G54   use preset work coordinate system 1(((G54))) G55   use preset work coordinate system 2(((G55))) G56   use preset work coordinate system 3(((G56))) @@ -127,7 +129,7 @@ G59   use preset work coordinate system 6(((G59))) G59.1 use preset work coordinate system 7(((G59.1))) G59.2 use preset work coordinate system 8(((G59.3))) G59.3 use preset work coordinate system 9(((G59.3))) ------------------------------------------------------------ +---- === Default coordinate system @@ -182,8 +184,8 @@ much as you would expect. A user must understand the correct ways that the G92 values work. They are set based upon the location of each axis when the G92 command is -invoked. The NIST document is clear that, "To make the current point -have the coordinates" X0, Y0, and Z0 you would use G92 X0 Y0 Z0. +invoked. The NIST document is clear that, To make the current point +have the coordinates X0, Y0, and Z0 you would use G92 X0 Y0 Z0. G92 'does not work from absolute machine coordinates'. It works from 'current location'. @@ -216,7 +218,7 @@ There are at least two ways to set G92 values. Both of these work from the current location of the axis to which the offset is to be applied. -Issuing `G92 X Y Z A B C U V W` does in fact set values to the G92 variables +Issuing 'G92 X Y Z A B C U V W' does in fact set values to the G92 variables such that each axis takes on the value associated with its name. These values are assigned to the current position of the machine axis. These results satisfy paragraphs one and two of the NIST document. @@ -225,10 +227,10 @@ G92 commands work from current axis location and add and subtract correctly to give the current axis position the value assigned by the G92 command. The effects work even though previous offsets are in. -So if the X axis is currently showing 2.0000 as its position a `G92 X0` +So if the X axis is currently showing 2.0000 as its position a 'G92 X0' will set an offset of -2.0000 so that the current location of X becomes -zero. A `G92 X2` will set an offset of 0.0000 and the displayed position -will not change. A `G92 X5.0000` will set an offset of 3.0000 so that the +zero. A 'G92 X2' will set an offset of 0.0000 and the displayed position +will not change. A 'G92 X5.0000' will set an offset of 3.0000 so that the current displayed position becomes 5.0000. === G92 Cautions @@ -259,7 +261,7 @@ set as machine zero everything will be correct. Once home has been established using real machine switches, or by moving each axis to a known home position and issuing an axis home command, any G92 offsets will be applied. If you have a G92 X1 in effect when you home the X axis the -DRO will read "X: 1.000" instead of the expected "X: 0.000" because the +DRO will read 'X: 1.000' instead of the expected 'X: 0.000' because the G92 was applied to the machine origin. If you issue a G92.1 and the DRO now reads all zeros then you had a G92 offset in effect when you last ran EMC. diff --git a/docs/src/gcode/gcode.txt b/docs/src/gcode/gcode.txt index 088d884..c0878cb 100644 --- a/docs/src/gcode/gcode.txt +++ b/docs/src/gcode/gcode.txt @@ -2,21 +2,22 @@ :toc: = G Code Reference + (((G Codes))) Conventions used in this section -In the G Code prototypes the hyphen (`-`) stands for a real value. +In the G Code prototypes the hyphen ('-') stands for a real value. A real value may be: - - An explicit number, `4` - - An expression, `[2+2]` - - A parameter value, `#88` - - A unary function value, `acos[0]` + - An explicit number, '4' + - An expression, '[2+2]' + - A parameter value, '#88' + - A unary function value, 'acos[0]' In most cases, if axis words are given -(any or all of `XYZABCUVW`), +(any or all of 'XYZABCUVW'), they specify a destination point. Axis numbers are in the currently active coordinate system, @@ -29,11 +30,11 @@ optional are required. The values following letters are often given as explicit numbers. Unless stated otherwise, the explicit numbers can be real values. For -example, `G10 L2` could equally well be written `G[2*5] L[1+1]`. If the -value of parameter 100 were 2, `G10 L#100` would also mean the same. +example, 'G10 L2' could equally well be written 'G[2*5] L[1+1]'. If the +value of parameter 100 were 2, 'G10 L#100' would also mean the same. -If `L-` is written in a prototype the `-` will often be referred to -as the "L number", and so on for any other letter. +If 'L-' is written in a prototype the '-' will often be referred to +as the 'L number', and so on for any other letter. == Polar Coordinates (((Polar Coordinates))) @@ -188,17 +189,17 @@ It is an error if: G0 axes -For rapid linear (straight line) motion, program `G0 'axes'`, where -all the axis words are optional. The `G0` is optional if the current -motion mode is `G0`. This will produce coordinated linear motion to +For rapid linear (straight line) motion, program 'G0 'axes'', where +all the axis words are optional. The 'G0' is optional if the current +motion mode is 'G0'. This will produce coordinated linear motion to the destination point at the current traverse rate (or slower if the machine will not go that fast). It is expected that cutting -will not take place when a `G0` command is executing. +will not take place when a 'G0' command is executing. If cutter radius compensation is active, the motion will differ from the above; see Section <<sec:Cutter-Radius-Compensation>>. -If `G53` is programmed on the same line, the motion will also differ; +If 'G53' is programmed on the same line, the motion will also differ; see Section <<sec:G53-Move-in>>. It is an error if: @@ -212,8 +213,8 @@ It is an error if: G1 axes For linear (straight line) motion at programed feed rate (for cutting -or not), program `G1 'axes'`, where all the axis words are optional. -The `G1` is optional if the current motion mode is `G1` . This will +or not), program 'G1 'axes'', where all the axis words are optional. +The 'G1' is optional if the current motion mode is 'G1' . This will produce coordinated linear motion to the destination point at the current feed rate (or slower if the machine will not go that fast). @@ -221,7 +222,7 @@ fast). If cutter radius compensation is active, the motion will differ from the above; see Section <<sec:Cutter-Radius-Compensation>>. -If `G53` is programmed on the same line, the motion will also differ; +If 'G53' is programmed on the same line, the motion will also differ; see Section <<sec:G53-Move-in>>. It is an error if: @@ -232,28 +233,28 @@ It is an error if: (((G2, G3 Arc))) -A circular or helical arc is specified using either `G2` (clockwise -arc) or `G3` (counterclockwise arc). The direction (CW, CCW) is as +A circular or helical arc is specified using either 'G2' (clockwise +arc) or 'G3' (counterclockwise arc). The direction (CW, CCW) is as viewed from the positive end of the axis about which the circular motion occurs. The axis of the circle or helix must be parallel to the X, Y, or Z axis of the machine coordinate system. The axis (or, equivalently, the plane perpendicular to the axis) -is selected with `G17` (Z-axis, XY-plane), -`G18` (Y-axis, XZ-plane), or `G19` (X-axis, YZ-plane). -Planes `17.1`, `18.1`, and `19.1` are not currently supported. +is selected with 'G17' (Z-axis, XY-plane), +'G18' (Y-axis, XZ-plane), or 'G19' (X-axis, YZ-plane). +Planes '17.1', '18.1', and '19.1' are not currently supported. If the arc is circular, it lies in a plane parallel to the selected plane. To program a helix, include the axis word perpendicular to the arc -plane: for example, if in the `G17` plane, include a `Z` word. This -will cause the `Z` axis to move to the programmed value during the -circular `XY` motion. +plane: for example, if in the 'G17' plane, include a 'Z' word. This +will cause the 'Z' axis to move to the programmed value during the +circular 'XY' motion. -To program an arc that gives more than one full turn, use a `P` word -specifying the number of full or partial turns of arc. If `P` is -unspecified, the behavior is as if `P1` was given: that is, only one +To program an arc that gives more than one full turn, use a 'P' word +specifying the number of full or partial turns of arc. If 'P' is +unspecified, the behavior is as if 'P1' was given: that is, only one full or partial turn will result, giving an arc less than or equal to one full circle. For example, if an arc is programmed with P2, the resulting motion will be more than one full circle and up to two full @@ -395,7 +396,7 @@ In the center format, the radius of the arc is not specified, but it may be found easily as the distance from the center of the circle to either the current point or the end point of the arc. -Deciphering the Error message "Radius to end of arc differs from radius to start:" +Deciphering the Error message 'Radius to end of arc differs from radius to start:' start = the current position center = the center position as calculated using the i,j or k words end = the programmed end point @@ -420,7 +421,7 @@ It is an error if: In the radius format, the coordinates of the end point of the arc in the selected plane are specified along with the radius of the arc. -Program `G2` `axes` `R-` (or use `G3` instead of `G2` ). R is the +Program 'G2' 'axes' 'R-' (or use 'G3' instead of 'G2' ). R is the radius. The axis words are all optional except that at least one of the two words for the axes in the selected plane must be used. The R number is the radius. A positive radius indicates that the @@ -490,7 +491,7 @@ Warning: G5.2, G5.3 is experimental and not fully tested. G5.2 is for opening the data block defining a NURBs and G5.3 for closing the data block. In the lines between these two codes the curve -control points are defined with both their related "weights" (P) and +control points are defined with both their related 'weights' (P) and their parameter (L) which determines the order of the curve (k) and subsequently its degree (k-1). @@ -577,16 +578,16 @@ see the <<cap:Lathe-Tool-Orientations>> diagram. The coordinate system is described in Section <<cha:Coordinate-System>>. -To set the origin of a coordinate system, program `G10 L2 P- R- axes`, +To set the origin of a coordinate system, program 'G10 L2 P- R- axes', where the P number is in the range 0 to 9. For the currently active coordinate system program P0. -To specify a coordinate system program 1 to 9 corresponding to `G54` to `G59.3`. +To specify a coordinate system program 1 to 9 corresponding to 'G54' to 'G59.3'. Optionally program R to indicate the rotation of the XY axis around the Z axis. All axis words are optional. The origin of the coordinate system specified by the P number is set to the given values (in terms of the not offset machine coordinate system). Only those coordinates for which an axis word is included on the line will be set. -Being in incremental distance mode (`G91`) has no effect on `G10 L2`. +Being in incremental distance mode ('G91') has no effect on 'G10 L2'. The direction of rotation is CCW as viewed from the Top View. Important Concepts: @@ -601,17 +602,17 @@ It is an error if: - The P number does not evaluate to an integer in the range 0 to 9. - An axis is programmed that is not defined in the configuration. -If a `G92` origin offset was in effect before `G10 L2`, +If a 'G92' origin offset was in effect before 'G10 L2', it will continue to be in effect afterwards. -The coordinate system whose origin is set by a `G10` command may be -active or inactive at the time the `G10` is executed. +The coordinate system whose origin is set by a 'G10' command may be +active or inactive at the time the 'G10' is executed. If it is currently active, the new coordinates take effect immediately. Examples: G10 L2 P1 X3.5 Y17.2:: - Sets the origin of the first coordinate system (the one selected by `G54`) + Sets the origin of the first coordinate system (the one selected by 'G54') to be X=3.5 and Y=17.2. Because only X and Y are specified, the origin point is only moved in X and Y; the other coordinates are not changed. @@ -741,8 +742,8 @@ make a rapid traverse move to from the current position. The parameter values are in terms of the absolute coordinate system and the machine's native coordinate system. -`G28 axes` will make a rapid traverse move -to the position specified by `axes`, +'G28 axes' will make a rapid traverse move +to the position specified by 'axes', then will make a rapid traverse move to the predefined position in parameters 5161-5166. @@ -762,8 +763,8 @@ as the absolute values to make a rapid traverse move to from the current positio The parameter values are in terms of the absolute coordinate system and the machine's native coordinate system. -G30 `axes` will make a rapid traverse move -to the position specified by `axes`, +G30 'axes' will make a rapid traverse move +to the position specified by 'axes', then will make a rapid traverse move to the predefined position in parameters 5181-5186. G30.1 stores the current absolute position into parameters 5181-5186. @@ -781,18 +782,18 @@ It is an error if : G33 X- Y- Z- K- -For spindle-synchronized motion in one direction, code `G33 X- Y- Z- K-` +For spindle-synchronized motion in one direction, code 'G33 X- Y- Z- K-' where K gives the distance moved in XYZ for each revolution of the spindle. -For instance, if starting at `Z=0`, `G33 Z-1 K.0625` produces +For instance, if starting at 'Z=0', 'G33 Z-1 K.0625' produces a 1 inch motion in Z over 16 revolutions of the spindle. This command might be part of a program to produce a 16TPI thread. -Another example in metric, `G33 Z-15 K1.5` produces +Another example in metric, 'G33 Z-15 K1.5' produces a movement of 15mm while the spindle rotates 10 times for a thread of 1.5mm. -Note: K follows the drive line described by `X- Y- Z-` and is not parallel to the Z axis. +Note: K follows the drive line described by 'X- Y- Z-' and is not parallel to the Z axis. Spindle-synchronized motions wait for spindle index, so multiple passes line up. -`G33` moves end at the programmed endpoint. +'G33' moves end at the programmed endpoint. All the axis words are optional, except that at least one must be used. @@ -810,7 +811,7 @@ It is an error if: G33.1 X- Y- Z- K- For rigid tapping (spindle synchronized motion with return), -code `G33.1 X- Y- Z- K-` where `K-` gives the distance moved +code 'G33.1 X- Y- Z- K-' where 'K-' gives the distance moved for each revolution of the spindle. A rigid tapping move consists of the following sequence: @@ -830,7 +831,7 @@ A rigid tapping move consists of the following sequence: Spindle-synchronized motions wait for spindle index, so multiple passes line up. -`G33.1` moves end at the original coordinate. +'G33.1' moves end at the original coordinate. All the axis words are optional, except that at least one must be used. @@ -854,12 +855,12 @@ Example: IMPORTANT: You will not be able to use a probe move until your machine has been set up to provide a probe input signal. -The probe input signal must be connected to `motion.probe-input` in a .hal file. +The probe input signal must be connected to 'motion.probe-input' in a .hal file. G38.x uses motion.probe-input to determine when the probe has made (or lost) contact. TRUE for probe contact closed (touching), FALSE for probe contact open. -Program `G38.2 axes`, `G38.3 axes`, `G38.4 axes`, or -`G38.5 axes` to perform a straight probe operation. +Program 'G38.2 axes', 'G38.3 axes', 'G38.4 axes', or +'G38.5 axes' to perform a straight probe operation. The axis words are optional, except that at least one of them must be used. The axis words together define the destination point that the probe will move towards, starting from the current location. @@ -906,10 +907,10 @@ If the probing operation failed, G38.2 and G38.4 will signal an error by posting an message onscreen if the selected GUI supports that. (And by halting program execution? *FIXME* TODO ) -A comment of the form `(PROBEOPEN filename.txt)` will open +A comment of the form '(PROBEOPEN filename.txt)' will open 'filename.txt' and store the 9-number coordinate consisting of XYZABCUVW of each successful straight probe in it. -The file must be closed with `(PROBECLOSE)`. +The file must be closed with '(PROBECLOSE)'. == G40 Compensation Off[[sec:G40]] @@ -952,10 +953,10 @@ is on is described in Section <<sec:Cutter-Radius-Compensation>> To turn cutter radius compensation on left (i.e., the cutter stays to the left of the programmed path when the tool radius is positive), -program `G41 D-`. +program 'G41 D-'. To turn cutter radius compensation on right (i.e., the cutter stays to the right of the programmed path when the tool radius is positive), - program `G42 D-`. + program 'G42 D-'. The D word is optional; if there is no D word, the radius of the tool currently in the spindle will be used. If used, the D number should normally be the slot number of @@ -976,9 +977,9 @@ It is an error if: G41.1 or G42.1 D[diameter] <L[orientation]> -To turn cutter radius compensation on left, program `G41.1 D- L-`. +To turn cutter radius compensation on left, program 'G41.1 D- L-'. -To turn cutter compensation on right, program `G42.1 D- L-`. +To turn cutter compensation on right, program 'G42.1 D- L-'. The D word specifies the cutter diameter. The L word specifies the cutter orientation, and defaults to 0 if unspecified. @@ -1012,7 +1013,7 @@ To use the currently loaded tool from the last Tn M6 program a G43 ==== G43 Hn: Offsets from tool table -To use a tool length offset from the tool table, program `G43 Hn`, +To use a tool length offset from the tool table, program 'G43 Hn', where the n number is the desired index in the tool table. The H number will typically be, but does not have to be, the same as the slot number of the tool currently in the spindle. It is OK for the H number @@ -1025,12 +1026,12 @@ It is an error if: ==== G43.1: Dynamic tool compensation -To use a tool length offset from the program, use `G43.1 Xn Yn ... Wn` +To use a tool length offset from the program, use 'G43.1 Xn Yn ... Wn' to set any axis tlo at run time. It is an error if: - - motion is commanded on the same line as `G43.1` + - motion is commanded on the same line as 'G43.1' === G49: Cancel tool length compensation[[sec:G49-Tool]] @@ -1044,11 +1045,11 @@ used. (((G53 Absolute Coordinates))) -To move in absolute coordinates from the machine origin, program `G53` -on the same line as a linear move. `G53` is not modal and must be -programmed on each line. `G0` or `G1` does not have to be programmed +To move in absolute coordinates from the machine origin, program 'G53' +on the same line as a linear move. 'G53' is not modal and must be +programmed on each line. 'G0' or 'G1' does not have to be programmed on the same line if one is currently active. -For example `G53 G0 X0 Y0 Z0` will move the axes to the home +For example 'G53 G0 X0 Y0 Z0' will move the axes to the home position even if the currently selected coordinate system has offsets in effect. @@ -1073,9 +1074,9 @@ To select coordinate system 1, program G54, and similarly for other coordinate systems. The system-number-G-code pairs are: -(1 - `G54`), (2 - `G55`), (3 - `G56`), -(4 - `G57`), (5 - `G58`), (6 - `G59`), -(7 - `G59.1`), (8 - `G59.2`), and (9 - `G59.3` ). +(1 - 'G54'), (2 - 'G55'), (3 - 'G56'), +(4 - 'G57'), (5 - 'G58'), (6 - 'G59'), +(7 - 'G59.1'), (8 - 'G59.2'), and (9 - 'G59.3' ). The coordinate systems store the values for each system in the variables shown in the following table. @@ -1126,7 +1127,7 @@ G64 P- Q- is a way to fine tune your system for best compromise between speed and accuracy. The P- tolerance means that the actual path will be no more than P- away from the programmed endpoint. The velocity will be reduced if needed to maintain the path. In addition, when you -activate G64 P- Q- it turns on the "naive cam detector"; when there are +activate G64 P- Q- it turns on the 'naive cam detector'; when there are a series of linear XYZ feed moves at the same feed rate that are less than Q- away from being collinear, they are collapsed into a single linear move. On G2/G3 moves in the G17 (XY) plane when the maximum @@ -1134,8 +1135,8 @@ deviation of an arc from a straight line is less than the G64 P- tolerance the arc is broken into two lines (from start of arc to midpoint, and from midpoint to end). those lines are then subject to the naive cam algorithm for lines. Thus, line-arc, arc-arc, and -arc-line cases as well as line-line benefit from the "naive cam -detector". This improves contouring performance by simplifying the +arc-line cases as well as line-line benefit from the 'naive cam +detector'. This improves contouring performance by simplifying the path. It is OK to program for the mode that is already active. See also Section <<sec:Path-Control-Mode>> for a discussion of these modes. If Q is not specified then it will have the same behavior as before and @@ -1151,13 +1152,13 @@ use the value of P-. Interpretation of G Code can be in one of two distance modes: absolute or incremental. -To go into absolute distance mode, program `G90`. In absolute +To go into absolute distance mode, program 'G90'. In absolute distance mode, axis numbers (X, Y, Z, A, B, C, U, V, W) usually represent positions in terms of the currently active coordinate system. Any exceptions to that rule are described explicitly in section <<sec:G81-G89>>. -To go into incremental distance mode, program `G91`. In incremental +To go into incremental distance mode, program 'G91'. In incremental distance mode, axis numbers usually represent increments from the current coordinate. @@ -1185,7 +1186,7 @@ systems. See Section <<sec:G92-Offsets>> for more information on Offsets. To make the current point have the coordinates you want (without -motion), program `G92 X- Y- Z- A- B- C- U- V- W-` , where the axis +motion), program 'G92 X- Y- Z- A- B- C- U- V- W-' , where the axis words contain the axis numbers you want. All axis words are optional, except that at least one must be used. If an axis word is not used for a given axis, the coordinate on that axis of the @@ -1193,37 +1194,37 @@ current point is not changed. It is an error if: - all axis words are omitted. -When `G92` is executed, the origins of all coordinate systems move. +When 'G92' is executed, the origins of all coordinate systems move. They move such that the value of the current controlled point, in the currently active coordinate system, becomes the specified value. All coordinate system's origins are offset this same distance. For example, suppose the current point is at X=4 and there is -currently no `G92` offset active. Then `G92 x7` is programmed. This +currently no 'G92' offset active. Then 'G92 x7' is programmed. This moves all origins -3 in X, which causes the current point to become X=7. This -3 is saved in parameter 5211. -Being in incremental distance mode has no effect on the action of `G92`. +Being in incremental distance mode has no effect on the action of 'G92'. -`G92` offsets may be already be in effect when the `G92` is called. +'G92' offsets may be already be in effect when the 'G92' is called. If this is the case, the offset is replaced with a new offset that makes the current point become the specified value. -To reset axis offsets to zero, program `G92.1` or `G92.2`. `G92.1` -sets parameters 5211 to 5219 to zero, whereas `G92.2` leaves their +To reset axis offsets to zero, program 'G92.1' or 'G92.2'. 'G92.1' +sets parameters 5211 to 5219 to zero, whereas 'G92.2' leaves their current values alone. To set the axis offset to the values saved in parameters 5211 to 5219, -program `G92.3`. +program 'G92.3'. You can set axis offsets in one program and use the same offsets in -another program. Program `G92` in the first program. This will set +another program. Program 'G92' in the first program. This will set parameters 5211 to 5219. Do not - use `G92.1` in the remainder of the first program. The parameter + use 'G92.1' in the remainder of the first program. The parameter values will be saved when the first program exits and restored when the second one - starts up. Use `G92.3` near the beginning of the second program. That + starts up. Use 'G92.3' near the beginning of the second program. That will restore the offsets saved in the first program. @@ -1303,10 +1304,10 @@ It is an error if: G73 X- Y- Z- A- B- C- R- L- Q- -The `G73` cycle is intended for deep drilling or milling with chip breaking. +The 'G73' cycle is intended for deep drilling or milling with chip breaking. The retracts in this cycle cut off any long stringers (which are common when drilling in aluminum). This cycle takes a Q number which -represents a "delta" increment along the Z axis. +represents a 'delta' increment along the Z axis. . Preliminary motion, as described above. . Move the Z-axis only at the current feed rate downward by delta or to @@ -1329,10 +1330,10 @@ It is an error if: - The active plane is not the ZX plane - Other axis words, such as X- or Y-, are specified - - The `R-` degression value is less than 1.0. + - The 'R-' degression value is less than 1.0. - All the required words are not specified - - `P-`, `J-`, `K-` or `H-` is negative - - `E-` is greater than half the drive line length + - 'P-', 'J-', 'K-' or 'H-' is negative + - 'E-' is greater than half the drive line length .G76 Threading[[fig:G76-Threading]] @@ -1342,31 +1343,31 @@ Drive Line:: A line through the initial X position parallel to the Z. P-:: - The "thread pitch" in distance per revolution. + The 'thread pitch' in distance per revolution. Z-:: The final position of threads. At the end of the cycle the tool will be at this Z position. I-:: - The "thread peak" offset from the "drive line". Negative `I` values - are external threads, and positive `I` values are internal threads. + The 'thread peak' offset from the 'drive line'. Negative 'I' values + are external threads, and positive 'I' values are internal threads. Generally the material has been turned - to this size before the `G76` cycle. + to this size before the 'G76' cycle. J-:: |