Controller · HEIDENHAIN
Connect HEIDENHAIN TNC 640
TNC 640 supports the HEIDENHAIN OPC UA NC Server from NC software 34059x-10, with one option (56 to 61) per connected application, and HEIDENHAIN DNC with option 18. DNC clients connect on TCP 19003 and receive on 19010 to 19015 (Cybus guidance); TNC 640 needs four passwords for full DNC access.
At a glance
| Native protocols | OPC UA NC Server; HEIDENHAIN DNC; LSV-2 |
|---|---|
| OPC UA | From 34059x-10, options 56–61 |
| DNC | Option 18 required |
| DNC ports | 19003 to control, 19010–19015 back |
| Data | Production, tools, messages, PLC |
Connection paths
OPC UA NC ServerRecommended
From 34059x-10.
HEIDENHAIN DNCAlternative
Windows clients, option 18.
LSV-2Legacy
File and status access through LSV-2 tools; vendor-licensed protocol.
Licences and options
| Item | Option / part number | Paid? | Note |
|---|---|---|---|
| OPC UA NC Server | Options 56–61 | Paid | Per application |
| HEIDENHAIN DNC | Option 18 | Paid | Check with MOD + SIK |
Ports
| Port | Protocol | Note |
|---|---|---|
19003 | TCP | DNC to control |
19010–19015 | TCP | DNC back to the agent |
9000 | TCP | Used by the Litmus Edge HEIDENHAIN 640 driver |
Software versions
- OPC UA NC Server: 34059x-10 or later
- Tool data application: software 17
- OPC Router DNC plug-in lists TNC 640 34059x-01 (DNC 1.5.1)
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
- 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.
- 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.
- Allow external accessEnable external access (MOD > External access / CfgAccessCtrl). On iTNC 530, REMOTE.PERMISSION in TNC:\TNC.SYS controls it.
- 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).
- Install the clientDNC clients use HEIDENHAIN's RemoTools SDK (Windows COM), so the collector runs on Windows.
Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| DNC client times out | Return ports 19010–19015 blocked | Allow them from the control to the agent PC. |
| Access denied over DNC | External access not permitted or passwords missing | Enable external access and supply the PLC, user, table and system passwords. |
Traps to avoid
- DNC requires a Windows host for the RemoTools SDK COM component.
Connectors that support this control
| Product | Vendor | Type | Outputs |
|---|---|---|---|
| StateMonitor | HEIDENHAIN | Control or machine maker | ERP/MES job interface |
| Connectware | Cybus | Edge platform | MQTT, OPC UA server |
| Litmus Edge | Litmus | Edge platform | Broker integrations |
| OPC Router + HEIDENHAIN plug-in | inray | Middleware | OPC UA, MQTT, REST, SQL, SAP |
| WebAccess/CNC | Advantech | Monitoring software | OPC UA/DA, Modbus, REST |
| pyLSV2 | Open source (MIT) | Open source | Python |
| Predator MDC | Predator Software | Monitoring software | SQL / MES / ERP |
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 on vendor pages
Questions engineers ask
Does the TNC 640 need option 18?
For HEIDENHAIN DNC access, yes. For the OPC UA NC Server, options 56 to 61 apply instead.
Related
Sources
Facts on this page come from these documents, opened on 27 October 2026.
- HEIDENHAIN — OPC UA NC Server brochure
- HEIDENHAIN — TNC options and accessories brochure
- MachineMetrics support — HEIDENHAIN DNC connectivity
- Cybus — Connecting a machine via HEIDENHAIN DNC
- OPC Router — HEIDENHAIN plug-in
- Litmus Edge — HEIDENHAIN 640 Ethernet driver
- pyLSV2 — protocol notes
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.