Connect HEIDENHAIN iTNC 530
iTNC 530 has no OPC UA NC Server in HEIDENHAIN's documentation; it is read through HEIDENHAIN DNC on TCP 19000, and integrator documentation says option 18 is not required on the iTNC 530. LSV-2 tools also work on it. DMG MORI's IoTconnector lists iTNC 530 HSCI and iTNC 530².
At a glance
| OPC UA NC Server | Not listed by HEIDENHAIN |
|---|---|
| DNC port | TCP 19000 |
| Option 18 | Not required (integrator documentation) |
| LSV-2 | Supported by LSV-2 tools |
Connection paths
Windows collector with RemoTools SDK, port 19000.
pyLSV2 or commercial LSV-2 packages; file and status access.
DMG MORI IoTconnector on DMG MORI machines.
Licences and options
| Item | Option / part number | Paid? | Note |
|---|---|---|---|
| HEIDENHAIN DNC | Option 18 | Not required on iTNC 530 per integrator docs | Check SIK with password Opt18 |
Ports
| Port | Protocol | Note |
|---|---|---|
19000 | TCP | DNC |
Software versions
- OPC Router plug-in: iTNC 530 NC 340420-06, 340422-01, 340480-01, 34049x-03, 60642x-01 (DNC 1.6.1)
Data you can read
- ExecutionMode: MANUAL, MDI, RPF, SINGLESTEP, AUTOMATIC, HANDWHEEL
- ProgramStatus: IDLE, RUNNING, STOPPED, INTERRUPTED, FINISHED, ERROR, NOT_SELECTED
- Program name, run time, overrides, errors, tool status
- Tool and pocket tables, file system, PLC data (depending on the client)
Setting it up
- 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 |
|---|---|---|
| Connection refused on 19000 | External access disabled | Set REMOTE.PERMISSION in TNC:\TNC.SYS and allow external access in MOD. |
Traps to avoid
- pyLSV2's author warns it can damage the control and is not meant for production use; a lockout parameter blocks most operations beyond file handling.
Connectors that support this control
| Product | Vendor | Type | Outputs |
|---|---|---|---|
| OPC Router + HEIDENHAIN plug-in | inray | Middleware | OPC UA, MQTT, REST, SQL, SAP |
| Connectware | Cybus | Edge platform | MQTT, OPC UA server |
| StateMonitor | HEIDENHAIN | Control or machine maker | ERP/MES job interface |
| pyLSV2 | Open source (MIT) | Open source | Python |
| WebAccess/CNC | Advantech | Monitoring software | OPC UA/DA, Modbus, REST |
| Predator MDC | Predator Software | Monitoring software | SQL / MES / ERP |
Questions engineers ask
Does iTNC 530 support OPC UA?
Not natively according to HEIDENHAIN's OPC UA NC Server documentation. Use HEIDENHAIN DNC (port 19000) or a gateway that serves OPC UA from DNC.
Sources
Facts on this page come from these documents, opened on 27 October 2026.
- MachineMetrics support — HEIDENHAIN DNC connectivity
- Cybus — Connecting a machine via HEIDENHAIN DNC
- OPC Router — HEIDENHAIN plug-in
- pyLSV2 — protocol notes
- DMG MORI — IoTconnector release (23 Dec 2020)
- HEIDENHAIN — OPC UA NC Server brochure
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.