Cycles process flags
- Mitchell Wacker
Process activation relative to movement types
When it comes to cycles operations, the behavior of process activation commands may not output exactly how you’d expect. Below is an example of what may be encountered:
The same process activation condition is chosen for two paths, but the process activation command is placed:
Before the feed height approach for Cycles and…
After the feed height approach for Contouring
While this may seem inconsistent, the process activation command is placed accurately according to each path’s process flags; The data in each point that indicates if the program should be “in-process” as it moves to said point.
Process Flags relative to movement types
For most operations, the first point of a path that is flagged as “in-process” is the second point at depth height. See the example below for contour paths:
Cycles, however, is different than other operations because it only has one point at depth height. There is not a second point at depth height, so the first point of this path that is “in-process” is the first point at depth height. See below:
Process activation relative to process flags
With this in mind, there are two process activation conditions that place the process activation command relative to “in-process” points. These conditions are:
First point of contact: Places the process activation condition on the point before the first point in-process.
First move in process: Places the process activation condition on the first point in-process.
To mirror the first example shown in this article, an example using the first point of contact condition is shown below on a Cycles and Contour path:
As shown above, the process activation condition places the process activation command on the same point of each operation’s path relative to the first “in-process” point. The name of the condition, first point of contact, is also accurate as it places the process activation command on the first point that contacts the workpiece surface for both operation types. The before index is just pushing that command upward to be called before the program starts moving to the first point of contact.
Looking back at the first example shown in this article, while the process activation placement may seem inconsistent relative to approach and feed moves, it makes sense knowing the process flags of each operation.