Each of the above lines declares that the corresponding gcode will be handled by a variabless subroutine of the same name (times ten); eg, O<G310>, O<G10>, O<G22>, etc. If there is already a "hardwired" gcode with that number, it may be accessed by adding 1000 to the gcode time ten. So, the original G1 will be accessed as G1010, the original M10 will be accessed as M1100, etc. |
Each of the above lines declares that the corresponding gcode will be handled by a variabless subroutine of the same name; eg, O<G31>, O<G1>, O<G2.2>, etc. If there is already a "hardwired" gcode with that number, it may be accessed by adding 100 to the gcode. So, the original G1 will be accessed as G101. For mcodes, add 1000 to the original code. So the original M10 will be accessed as M1010, etc. |
O<GmissingWord?> call [10] [#<missing>] [#<extra>] |
O<GmissingWord?> call [1] [#<missing>] [#<extra>] |
In this case, 10 is ten times the gcode number (1) and missing is a parameter with mask bits for the missing parameters. This subroutine will print messages describing the problem and then exit. A similar routine MmissingWord? should be called from mcode subroutines detecting errors. |
In this case, 1 is the gcode number (1) and missing is a parameter with mask bits for the missing parameters. This subroutine will print messages describing the problem and then exit. A similar routine MmissingWord? should be called from mcode subroutines detecting errors. |