|
|
|
The subroutine body G-Code output is located in one of two places:
At the end of the G-Code file. Subroutine body commands are processed early in the posting process (even before any call to the subroutine is processed), but the output is stored internally until the end of the run. Then, it is copied to the end of the G-Code file (it may not be the first file, if a tape cut operation took place during the run). This is important to remember - the order of blocks in the output file does not represent the order of processing in case subroutines are involved.
The subroutine data is copied to the end of the file before the END OF FILE block is executed. Therefore, any OUTPUT generated in the END OF FILE block (For example, the % character) will be placed after the subroutine G-Code.
In separate files, one per subroutine, with extension ._snn, where nn is a serial number, starting from 01. In order to direct the subroutine G-code to separate files, the GPP2 user has to check the DF2 file parameter Subroutines in Separate Files.
If separate files are requested, GPP2 will take a decision regarding the file extension, based on how many subroutines exist in the toolpath being processed.
If the number of subroutines is up to 99, the extension will be of the form ._snn, from ._s01 to ._s99.
If the number of subroutines is between 100 and 999, a digit is added to the extension, ranging from ._s001 to ._s999. If a 1000 or more subroutines exist, yet another digit is added (from ._s0001 to ._s9999).
|
