SINUMERIK 880M Tool Length: Reading with @-Codes and D Offsets

Reading Tool Length on SINUMERIK 880M: @-Codes, D Offsets, and GETTCOR

Tool length readout on Siemens CNC controllers is one of the most frequently misunderstood operations because three independent concepts — physical tool selection (T), wear/geometry offset selection (D), and runtime tool data access (@320 or GETTCOR) — are often conflated. This reference consolidates the @-code tool read mechanism used on SINUMERIK 880M, the modern GETTCOR function documented for the SINUMERIK 840D sl, and the safety procedures required to handle manual tools when the automatic changer must be bypassed.

1. System Overview

The SINUMERIK 880M separates tool identity from tool compensation. Three logical data sets participate in every cutting operation:

• Tool magazine slot (T number) — physical tool location. T1 is the first magazine pocket, T0 denotes an empty spindle.
• Tool offset (D number) — geometric and wear values entered in the offset screen. D1–Dn are available independent of magazine state.
• Active compensation (G43/G44/G49 state) — the modal group that selects which D offset is currently applied to the programmed axis positions.

An @320 read against a missing or inactive offset returns 0 regardless of how the offset screen is populated, because the runtime has no active record to report.

2. Tool Number (T) vs. Tool Offset (D)

The T/D split is the first concept every 880M programmer must internalize.

Key principle: any D number can be paired with any T number. T selects the magazine slot; D selects the compensation record. The two are not coupled by index.

3. @-Code 320 — Tool Data Read Syntax

The @320 function reads tool compensation data into a user-defined R-variable. The full syntax observed on 880M is:

@320 R<target> K<area> K<tool_no> K<component>

Where:

• R<target> — destination R-variable (e.g., R500).
• K<area> — tool area selector. 1 typically selects the active tool area.
• K<tool_no> — T number of the tool whose offset is being queried.
• K<component> — offset sub-index: typically 1 = length 1 (Z), 2 = length 2 (Y or secondary), 3 = radius.

Example from the source case:

@320 R500 K1 K1 K2   ; TO AREA 1-D1-P2 — read Z-secondary length of tool 1, offset 1

This call should deposit the secondary length of tool 1, offset 1, into R500. When R500 remains zero, one of the conditions listed in Section 5 has not been satisfied.

4. Parameter Mapping Reference

The K-parameter mapping used by @320 is consistent across 880M revisions but the offset sub-index numbering is OEM-customizable. The following mapping applies to standard Siemens tool offset screens:

If the machine builder has implemented a non-standard offset screen (very common on production-turnkey machines), the K-component meaning can shift by ±1. Always verify against the machine-specific programming manual.

5. Root Cause Analysis: Why @320 Returns Zero

A zero return from @320 is not a programming error — it is a runtime condition report. The following five conditions each produce a zero result:

1. Tool not loaded. The spindle contains no tool (T0 active). @320 has no compensation record to read.
2. Offset record empty. The D number exists but the length field has not been measured or entered. The default value is 0.
3. Wrong tool area. K<area> selects a tool data area that is not active for the current setup (e.g., area 2 selected but only area 1 is configured).
4. T/D mismatch. The queried T number has no offset pairing configured. Reading component 2 of an offset that does not have a secondary length entry returns 0.
5. Compensation not active. G49 has cancelled compensation. The offset data still exists, but G49 prevents it from being applied — and some 880M builds gate @320 behind the active compensation state.

Diagnostic flow:

1. Verify the active tool with the machine HMI: confirm a T number other than T0 is loaded.
2. Open the tool offset screen and confirm the D number contains a non-zero length value.
3. Issue a G43 H<D> to activate the offset and re-run the read.
4. If still zero, change the area parameter K1 to K2 and re-test.

6. GETTCOR — Modern Equivalent on SINUMERIK 840D sl

On SINUMERIK 840D sl and successors, the runtime tool data read is performed by GETTCOR. The function returns tool lengths or tool length components of the active tool or any indexed tool/edge. The 840D sl programming manual (Siemens support ID 109777937) defines the read parameters as:

GETTCOR(<tNo>, <dNo>, <comp>)

• <tNo> — tool number
• <dNo> — offset number
• <comp> — component selector (length 1, length 2, length 3, radius)

Compared to @320, GETTCOR provides several advantages: it supports structured error handling via state queries, it operates on tool-management-active configurations without re-numbering, and it returns a meaningful status when no valid record exists rather than silently zeroing the destination.

When migrating 880M programs to 840D sl, replace @320 R<var> K1 K<t> K<comp> with R<var> = GETTCOR(<t>, <d>, <comp>) after verifying the tool-management configuration on the target controller.

7. Manual Tool Loading Without Triggering the Changer

Operators occasionally need to run a manual tool (e.g., a long boring bar or an edge finder) that the automatic magazine cannot accommodate. The 880M supports this through the T0 mechanism:

T0 M6                  ; evacuate current tool from spindle
M0                     ; optional: program stop for operator mounting
; --- operator mounts manual tool manually ---
G43 H<D_no>            ; activate the manual tool's offset
; ... machining moves ...
G49                    ; cancel offset before returning to auto mode
T<next> M6             ; reload an auto-magazine tool

The D number for the manual tool is selected freely from the offset table; it is not linked to T0. The T0 state only affects magazine behavior, not offset lookup.

8. Operator Messaging for Manual Tool Blocks

Siemens 880M supports inline operator messages via MSG(). Two messages are required for safe manual-tool handling:

MSG("MOUNT MANUAL TOOL <NAME> — CONFIRM SPINDLE EMPTY")
M0
T0 M6                ; or skip if spindle is already empty
G43 H<D_manual>
; ... manual tool work ...
G49
MSG("REMOVE MANUAL TOOL <NAME> — RESUME AUTO CHANGER")
M0

This pattern satisfies the machine-builder best practice of bracketing every manual-tool block with a confirmation stop. Production programs that omit the second message risk an unattended tool collision on next job start.

9. Tool Management Configuration

The 880M supports two operating modes for tool data:

If tool management is active, @320 must query the resolved T number, not the programmed T alias. Failure to do so is a common cause of unexpected zero returns in managed configurations.

10. Verification and Commissioning Procedure

1. Load a known tool. Mount tool 1, enter a non-zero value for length 1 in offset D1 (e.g., 100.000 mm).
2. Activate offset. Issue T1 M6 followed by G43 H1.
3. Read length. Execute @320 R500 K1 K1 K1 and verify R500 reports 100.000.
4. Test secondary component. Enter 25.000 mm in length 2 of D1, then execute @320 R501 K1 K1 K2. Verify R501 reports 25.000.
5. Test radius. Enter 10.000 mm in radius of D1, execute @320 R502 K1 K1 K4. Verify R502 reports 10.000.
6. Test empty case. Issue G49 then re-run the read. Observe whether the controller reports 0 (some builds) or holds the last value (others).
7. Test manual block. Run the T0 / manual-tool / MSG sequence from Section 7 with no spindle collision and confirm the second MSG fires on completion.

11. Troubleshooting Matrix

12. Frequently Asked Questions