> For the complete documentation index, see [llms.txt](https://docs.heisenware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.heisenware.com/reference/functions/connectors/heidenhain-dnc.md).

# Heidenhain DNC

Some Heidenhain controls offer no OPC UA server. Those are reached over DNC, Heidenhain's own remote interface. Heisenware talks to them through an agent built for that interface, not through a connector you create an instance of yourself.

[Reach out to us](mailto:support@heisenware.com) for this integration. We build the agent for your control and hand it to your IT to install.

{% hint style="info" %}
If your control offers an OPC UA server, you need none of this: use [Heidenhain OPC UA](https://docs.heisenware.com/reference/functions/connectors/heidenhain-opc-ua.md), which is part of the platform and which you set up yourself.
{% endhint %}

## How it looks in the Builder

* **Its own agent**: the DNC agent runs in the machine's network and appears in the [Functions explorer](https://docs.heisenware.com/app-builder/app-builder/functions.md) next to the other agents once it comes online. An executor addresses it like any other agent, so the same flow can serve several machines by their agent names (see [Agents and where code runs](https://docs.heisenware.com/concepts/agents-and-where-code-runs.md)).
* **Functions for your control**: the class the agent offers is built for the control it talks to. What you can read and write differs from machine to machine; the Functions explorer lists what yours has.
* **Names without parameter help**: the agent is not written in JavaScript, so the explorer shows its function names but no parameter descriptions. The notes delivered with the integration say what each function takes.
* **Not part of the agent fleet**: the App Manager's **Agents** panel does not build, update or restart a DNC agent. Its host is maintained with us.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.heisenware.com/reference/functions/connectors/heidenhain-dnc.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
