1A0-008A

Identify Active Transformations

Press 'PGM MGT' then select 'Program Run' and check the 'Positions' display. Review the 'Transformations' section to see which coordinate transformations are currently active (PLANE, M128, Cycle 19, basic rotations).

The transformation stack shows all active transformations in order - the last activated transformation may conflict with earlier ones still in effect.

Review NC Program Structure

Trace back through the NC program, including all called subroutines (CALL LBL) and cycles, to identify where each transformation was activated. Look specifically for PLANE SPATIAL, PLANE VECTOR, PLANE EULER, PLANE PROJECTED, PLANE AXIAL, M128, or CYCL DEF 19 commands.

Use the Test Run graphics with 'Show Transformations' active to visualize when conflicting transformations are attempted.

Insert PLANE RESET Command

Add 'PLANE RESET' or 'M130' before the NC block causing the alarm to cancel all previous coordinate transformations. This ensures a clean state before activating the new transformation.

PLANE RESET cancels ALL active transformations including basic rotations - verify this does not affect preceding machining operations.

Restructure Transformation Logic

If both transformations are required, separate them into distinct program sections with PLANE RESET between them, or use M128/M129 pairs to properly manage tilted working plane activation and deactivation.

Use modal transformation management - activate transformation, perform operations, reset transformation, then activate next transformation rather than layering them.

Examine PLANE Command Parameters

Locate the PLANE function in your NC program and verify all vector components and spatial points. For PLANE SPATIAL, ensure the three points are not collinear. For PLANE VECTOR, verify base vector and normal vector are not parallel (dot product ≠ ±1).

Use the calculator function (MOD > Calculator) to verify vector calculations - normal vectors must be non-zero and perpendicular to the intended plane.

Check Vector Magnitude

Calculate the magnitude of all vectors used in PLANE definitions. Zero or near-zero length vectors (magnitude < 0.0001) create undefined coordinate systems. Replace calculated vectors with explicit non-zero values.

If using calculated coordinate values from Q parameters, add error checking: 'FN18: SYSREAD Q1 = ID350 NR1' to verify values before using in PLANE commands.

Validate Rotation Angles

For PLANE EULER, check that rotation angle combinations (A, B, C values) do not create gimbal lock conditions or undefined rotations. Avoid 90-degree or 270-degree angles in specific axes that create singular positions.

iTNC 530 and TNC 620/640 handle EULER angles differently - refer to the specific control's Cycle Programming manual for valid angle ranges.

Test with Simple Values

Replace complex calculated parameters with simple test values (e.g., PLANE SPATIAL SPA+0 SPB+0 SPC+0 ROT+0 TURN FMAX) to verify the PLANE syntax is correct before reintroducing variable parameters.

Always use FMAX parameter with PLANE commands to specify maximum feed rate during auto-positioning movements.

Check Compensation Status

At the alarm location, verify if tool radius compensation is active. Check for G41/RL or G42/RR commands without a corresponding G40 cancellation before the transformation. Review the 'Positions' display under 'Comp' column.

Compensation remains modal across program sections - check main program and all subroutines for unbalanced RL/RR and G40 pairs.