Forcing a Scenario Action

In some cases, scenario actions may be skipped, if GPP2 determines that they are redundant:

A MOVE_, MOVE_UP or MOVE_DOWN action where no axis is actually set (so there will be no linear motion block anyway).
A SET_UCS action where both the qualifier and the machine axis angles are the same as the previous SET_UCS action.

However, it is sometime necessary to force GPP2 to execute the action regardless of these rules. This is especially important when a SET_UCS action must be executed to ensure that the GPP2 output UCS is not rotated (before a scenario linear motion).

To do this, the FORCE_ACTION keyword is used before the action name:

FORCE_ACTION SET_UCS ( ... action variables ... )

This SET_UCS action will be executed regardless of the previous one.

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