|
|
PRINT, PRINT0, PRINT1 to PRINT10
These statements are very similar to the OUTPUT statement, except that they send the output text to other files (not the main G-code file).
PRINT argument1 argument2 ...
PRINT0 argument1 argument2 ...
PRINT10 argument1 argument2 ...
The arguments are exactly the same as in the OUTPUT statement. The output of each statement is sent to the destination shown in the following table:
Statement |
Destination File |
<toolpath>.<post>.msg.txt The text is also printed to the GPP2 application screen. |
|
PRINT0 |
Print0.txt in the current folder. |
PRINT1 to PRINT10 |
<toolpath>.<post>.<ext> The extensions <ext> for the 10 files are defined in the DF2 file parameters "PRINT1 File Extension" to "PRINT10 File Extension". Leaving an extension empty inhibits the output to that file. |
Notes:
It is not recommended to use the new-line character (For example, $) in any of these PRINT statements (since the block will probably contain OUTPUT statements that will send text to the main G-code file, not to the expected PRINT destination). The \J control character (new line) should be used instead.
The <toolpath> name is the name of the GPP2 input DAT file, without any extension.
The <post> name is the name of the current post-processor used, without any extension.
PRINT0 was traditionally used in old GPP to create the script (batch) file that is run after the post-processor execution. With GPP2, post-run system commands may be created and executed in the POST SCRIPT block, essentially making the PRINT0 command mostly redundant.
|
