Controller · HEIDENHAIN

Connect HEIDENHAIN TNC 620

TNC 620 supports the HEIDENHAIN OPC UA NC Server from NC software 81760x-08 (options 56 to 61) and HEIDENHAIN DNC (option 18). Older TNC 620 software versions are covered by DNC tools such as the OPC Router HEIDENHAIN plug-in (34056x-01, 73498x-01, 81760x-01).

At a glance

OPC UAFrom 81760x-08, options 56–61
DNCOption 18
Older softwareDNC tools

Connection paths

HEIDENHAIN DNCAlternative

Option 18.

Licences and options

ItemOption / part numberPaid?Note
OPC UA NC ServerOptions 56–61Paid
HEIDENHAIN DNCOption 18Paid

Ports

PortProtocolNote
19003 / 19010–19015TCPDNC (TNC 640-generation controls)

Software versions

  • OPC UA NC Server: 81760x-08
  • Production data application: software 08; tool data: 17

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
  • ExecutionMode: MANUAL, MDI, RPF, SINGLESTEP, AUTOMATIC, HANDWHEEL
  • ProgramStatus: IDLE, RUNNING, STOPPED, INTERRUPTED, FINISHED, ERROR, NOT_SELECTED

Setting it up

  1. 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.
  2. Run the HEIDENHAIN Connection AssistantThe wizard on the control sets up the server, the certificates and the user mapping.
  3. 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).
  4. 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.
  5. Grant write rights deliberatelyChanging counters via OPC UA needs the NC.RemoteOperator role.
  6. Check option 18HEIDENHAIN DNC (option 18, SIK2 3-03-1) is required on TNC 640 and later; integrator documentation says it is not required on iTNC 530. Check with MOD and the SIK menu.
  7. Allow external accessEnable external access (MOD > External access / CfgAccessCtrl). On iTNC 530, REMOTE.PERMISSION in TNC:\TNC.SYS controls it.
  8. Open the portsiTNC 530 / TNC 426: TCP 19000. TNC 640: TCP 19003 to the control and 19010 to 19015 back to the client agent (Cybus guidance).
  9. Install the clientDNC clients use HEIDENHAIN's RemoTools SDK (Windows COM), so the collector runs on Windows.

Traps to avoid

  • Axis and spindle data via OPC UA is TNC7-only.

Connectors that support this control

ProductVendorTypeOutputs
StateMonitorHEIDENHAINControl or machine makerERP/MES job interface
OPC Router + HEIDENHAIN plug-ininrayMiddlewareOPC UA, MQTT, REST, SQL, SAP
ConnectwareCybusEdge platformMQTT, OPC UA server
pyLSV2Open source (MIT)Open sourcePython

CNC connector directory →

Sources

Facts on this page come from these documents, opened on 27 October 2026.

  1. HEIDENHAIN — OPC UA NC Server brochure
  2. HEIDENHAIN — TNC options and accessories brochure
  3. OPC Router — HEIDENHAIN plug-in

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.

CNC Connectivity Field Kit
Take the Field Kit to site
Every controller on one spreadsheet, with ports, licences, commissioning checklists and a firewall request template. Free with an engineer account.
Get the Field Kit →