Thread Mill Cycle

Cimatron Auto-Drill procedure supports, among other things, a special thread-mill cycle, which is not supported by the legacy Drill procedure. This cycle contains several dedicated parameters, and is expected to be executed by the machine itself, like other drill cycles.

However, many machines and controllers do not include built-in thread mill cycles. In such cases, the cycle has to be executed using standard milling operations (linear and circular motions). The cycle needs to be “exploded” to multiple milling motions. This used to be done inside the post-processor (GPP or GPP2) program, and was usually limited to the basic thread mill behavior. Options like multiple passes (at different depth) or tapered threads were hard to implement.

The feature in GPP2 does all that automatically, breaking the thread mill cycle into multiple milling motions (if so desired). Every standard PP can handle thread milling with no modifications needed in the PP at all.

See below for information on how to use the new feature, how to invoke it selectively even if the machine does support thread mill cycles, and the various GPP2 variables that control execution.

Invoking GPP2 Thread Mill Processing

GPP2 will invoke the thread mill process (breaking the cycle into multiple milling motions) when the toolpath contains a thread-mill cycle (cycle type 14, variable CYCLE_SUB is 14) and the PP does not contain any block to handle this cycle (no CYCLE block with qualifier “specialon” or “special”). This indicates to GPP2 that the PP has no capability to handle thread-mill cycles through the machine, and the cycle is exploded.

Another way to invoke the cycle breakup process is available to the PP developer, from within the CYCLE block (any cycle type). For instance, suppose the machine can handle simple thread-mill cycles, but cannot handle tapered thread-mill cycles. In that case, the PP developer can check for tapered angle (see variables later), and if non-zero, raise a new GPP2 system flag (TRD_BREAK_MOTIONS) to TRUE_ (and not send anything to the machine). This instructs GPP2 to start the whole exploded thread-mill process.

See relevant variables in Block: CYCLE.

Note that not all parameters are actually set by the user as part of the Auto-Drill procedure. Some are internal to GPP2 and can be modified inside the EX2 program if the default values are not suitable. Others are received from the NC file.

Notes:

Some functionality may be dependent on the product package. Contact your Reseller if you require a license.