Router-CIM Automation Suite



Previous topic Next topic  


Previous topic Next topic  

Post Processor Considerations

The process of translation is a sequential process.  Each time a piece of data (such as a line or arc element) is encountered, a specific NC code is developed for that piece of data.  This means that the data to be translated must be in the order in which the elements are to be processed.  Router-CIM provides the necessary commands to ensure that proper order of the data is achieved.


One printed line of NC code is referred to as a command block or motion block. An example would be the line "N1G01X3Y3M08".  Within this command block, several NC commands exist.  In this case the M08 turns on an air blower unit and the G01X3Y3 performs a move to the location 3,3.


Several NC commands can exist in one command block.   Methods are provided to define the different NC codes that should appear in one command block.  The block definitions discussed in the "Configuration" section refer to this grouping of NC codes into one command block.


The translation rules and the arrangement of codes within a command block is governed by an ASCII file.  This file has a file extension of .$PP.  This file represents the heart of the postprocessor.  Each line of information in this file contains the translation rules and the NC code grouping requirements.  Any behavior changes in the translation process can usually be affected by changing the $PP file.


Various other files affect the translation of codes to the proper format.  Some of the other files in addition to the $pp file are:












These files exist in the Ncpost and Ncdwgs folders within Router-CIM’s directory structure and perform functions that work together with the $PP file to achieve the proper translation.


Other files may exist in particular systems, depending on the complexity of the machine and the amount of modification required to the Router-CIM system to achieve the proper translation.


Router-CIM works in a fairly straight forward manner, and according to some strict rules that govern all the steps that are made in the software from the time you start it, until the time you make code.  Understanding these steps is critical if you wish to modify the output to suit a particular machine tool.