Define the TNC 360 Failure Boundary
The reported machine is a three-axis Heidenhain TNC 360 mill receiving ISO-format output from NX. Linear motion is not identified as the problem; the control reports an incorrect-parameter-type error when it reaches G02 or G03 arc blocks written in a combined form such as G02 X... I... J....
| Confirmed from the report | Not established |
|---|---|
| The fault occurs on G02/G03 blocks | The exact control alarm text or number |
| NX currently generates ISO code | The active NX post and its arc-output settings |
| The machine is identified as a TNC 360 | Whether every arc plane and direction fails |
Troubleshoot the Arc-Block Syntax
The evidence points to a dialect mismatch between the ISO syntax emitted by the NX post and the block structure expected by this control configuration. The working program pattern supplied for comparison declares the arc-center parameters in one block and commands G02 in the following block:
I+0 J+0
G02 F500This differs from the failing combined form:
G02 X... I... J...Treat the separated-center format as a test, not proof that it is the only valid TNC 360 arc format. The evidence does not provide the complete failing program, alarm number, endpoint values, active modal state, or control configuration needed to isolate one parameter conclusively.
Correct and Verify One Arc
- Reduce the program to one failing G02 or G03 move while preserving its preceding positioning blocks and active plane.
- Record whether the program uses G17 and whether G90 or G91 is active; both modes appear in the supplied Heidenhain-oriented examples and can change how coordinates are interpreted.
- Rewrite the test so the I and J center declaration precedes the G02 or G03 block, following the demonstrated structure.
- Run the test using the machine's normal safe prove-out procedure and confirm that the parameter error disappears and the commanded path is correct.
- If the error remains, capture the exact alarm text and complete surrounding blocks. Without those details, it is not possible to distinguish an unsupported block format from an invalid center, endpoint, plane, or modal combination.
Configure the NX Post for Heidenhain Output
Do not solve a recurring syntax mismatch by manually editing every program. Select or develop an NX post that targets Heidenhain output, then verify its arc formatting against a program already accepted by this machine. A post for another Heidenhain control may provide a starting structure, but the evidence does not establish compatibility with the TNC 360.
Validate the post with short programs covering linear motion, G02, G03, the required plane, and both coordinate modes actually used in production. Compare the generated center declarations and arc blocks with the proven machine syntax before releasing a full part program.
FAQ
Why does a Heidenhain TNC 360 reject G02 X... I... J...?
The reported failure is consistent with the NX post emitting an arc-block structure that does not match the control's accepted syntax. Test the demonstrated arrangement with I and J in the preceding block, then place G02 or G03 in the next block.
Can I use any Heidenhain NX post for a TNC 360?
A generic Heidenhain post may be a starting point, but compatibility is not established by the evidence. Verify its G02/G03 formatting, G17 plane handling, and G90/G91 behavior on the actual control.
What information is needed if the TNC 360 arc error remains?
Capture the exact alarm text or number, the complete failing block, preceding positioning and modal blocks, the active plane, and whether G90 or G91 is active. Those details are required to separate a syntax problem from invalid arc geometry or modal interpretation.
