Controller · HEIDENHAIN
Connect HEIDENHAIN TNC7 and TNC7 basic
TNC7 has the HEIDENHAIN OPC UA NC Server from NC software 81762x-16 (TNC7 basic from 81762x-18), licensed per connected application: options 56 to 61, or 3-02-1 on SIK2 controls, which accept up to 10 connections. TNC7 is the only control with the axis and spindle data application (from software 20) and bidirectional FUNCTION OPCUA. HEIDENHAIN DNC (option 18) remains available for Windows clients.
At a glance
| Native protocol | OPC UA NC Server; HEIDENHAIN DNC |
|---|---|
| Options | 56–61 (SIK) or 3-02-1 (SIK2); DNC 18 / 3-03-1 |
| Min software | 81762x-16 (TNC7), 81762x-18 (TNC7 basic) |
| Connections | Up to 10 on SIK2, one option per application |
| Security | X.509 user certificates, Basic256Sha256 |
| Port | Not published by HEIDENHAIN |
Connection paths
OPC UA NC ServerRecommended
Cross-platform clients (Windows, Linux, macOS), units and ranges transmitted.
HEIDENHAIN DNCAlternative
Windows COM interface (RemoTools SDK).
StateMonitorVendor product
HEIDENHAIN's monitoring software (DNC, OPC UA, umati, MTConnect, Modbus, FOCAS).
Licences and options
| Item | Option / part number | Paid? | Note |
|---|---|---|---|
| OPC UA NC Server (per application) | Options 56–61 (ID 1291434-01…06) | Paid | One option per connected application; 90-day trial |
| OPC UA NC Server (SIK2) | 3-02-1 (ID 1395873-01) | Paid | Up to 10 connections |
| HEIDENHAIN DNC | Option 18 / 3-03-1 | Paid | Windows COM interface |
| Process Tracking Interface | 3-04-01 | Paid | TNC7 only |
Ports
| Port | Protocol | Note |
|---|---|---|
Not published | TCP | HEIDENHAIN pages do not state the OPC UA port; read it from the Connection Assistant |
19003 / 19010–19015 | TCP | DNC on TNC 640-generation controls (Cybus) |
Software versions
- Production data application: TNC7 software 16
- Tool data application: software 17
- Axis and spindle data: TNC7 software 20 only
Data you can read
- Machine messages: program end and abort, maintenance messages, custom messages raised from the NC program
- Production data: running and interrupted jobs and their durations
- NC program transfer and program control
- Tool data (for example from a presetter)
- Counters, program durations, temperatures, fill levels, pallet magazine status
- PLC values published by the machine builder, with units and value ranges
- Axis and spindle data (TNC7, software 20 and later)
Setting it up
- Check the software and optionsOPC UA NC Server needs NC software TNC7 81762x-16, TNC 640 34059x-10 or TNC 620 81760x-08 or later, and one software option per connected application: options 56 to 61 (SIK) or 3-02-1 (SIK2). A 90-day trial is available.
- Run the HEIDENHAIN Connection AssistantThe wizard on the control sets up the server, the certificates and the user mapping.
- Use certificate-based usersThe default authentication is an X.509 v3 user certificate; username and password can be allowed (NC.OpcUaPwAuth), optionally only on the machine network (NC.OpcUaPwAuthOnlyMachineNet).
- Connect the clientUse Basic256Sha256 with SignAndEncrypt. The programming station (free demo software) includes the full OPC UA NC Server, so you can develop the client before touching the machine.
- Grant write rights deliberatelyChanging counters via OPC UA needs the NC.RemoteOperator role.
Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| Second application cannot connect | Only one option per connected application | Add another option (56–61) or consolidate clients behind one gateway. |
| Client rejects login | Certificate user not mapped | Map the client certificate to a user in the Connection Assistant. |
Traps to avoid
- Each connected application consumes one option: a historian, an MES and a dashboard connecting separately need three.
- Use a gateway (MQTT or REST) if many consumers need the data.
Connectors that support this control
| Product | Vendor | Type | Outputs |
|---|---|---|---|
| StateMonitor | HEIDENHAIN | Control or machine maker | ERP/MES job interface |
| IoTconnector (retrofit, flex) + Messenger V4 | DMG MORI | Control or machine maker | OPC UA, MTConnect, MQTT |
| Connectware | Cybus | Edge platform | MQTT, OPC UA server |
| WebAccess/CNC | Advantech | Monitoring software | OPC UA/DA, Modbus, REST |
| OPC Router + HEIDENHAIN plug-in | inray | Middleware | OPC UA, MQTT, REST, SQL, SAP |
| pyLSV2 | Open source (MIT) | Open source | Python |
Not published by the vendor. We could not find these in vendor documentation. Ask the control or machine maker before you rely on them.
- OPC UA port and endpoint format
- Option price
- An OPC 40501 (umati) model statement on HEIDENHAIN pages (VDW lists HEIDENHAIN among supporting control suppliers)
Questions engineers ask
How many OPC UA clients can a TNC7 serve?
One per OPC UA NC Server option (56 to 61); on SIK2 controls up to 10 connections.
Related
Sources
Facts on this page come from these documents, opened on 27 October 2026.
- HEIDENHAIN — OPC UA NC Server brochure
- HEIDENHAIN — OPC UA NC Server
- HEIDENHAIN — TNC7 basic 81762x-19 release notes (09/2024)
- HEIDENHAIN infobase — software option 59
- HEIDENHAIN — TNC options and accessories brochure
- HEIDENHAIN — StateMonitor
- VDW — control suppliers supporting umati
Last verified 27 October 2026 against vendor documentation. OPC UA Connect is an educational resource published by TEEPTRAK; it is not affiliated with the OPC Foundation, the MTConnect Institute or any control maker.