> For the complete documentation index, see [llms.txt](https://docs.cybus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cybus.io/2-6-1/connectors/shop-floor-connectors/heidenhain-dnc/heidenhainendpoint.md).

# Heidenhain DNC Endpoint Properties

## `description` (string)

Some descriptive text about the endpoint

## `method` (string, required)

The function to call on the DNC control

Example: `"isConnected"`

## `params` (array)

Only for subscribe: The parameter values for the function call to set up subscriptions. (For read calls, the function parameters are given in the payload data instead.)

The elements of the array must match *at least one* of the following properties:

## (number)

## (integer)

## (string)

## (boolean)

## (array)

The schema defines an array with all elements of the type `string`.

## (object)

Default:

```
[]
```

Examples: `[1,"NAME"]`, `["this","that"]`

## `pollInterval` (integer)

Only for subscribe operation using type poll: Interval in milliseconds to poll the property

Default: `1000`

Example: `1000`

## `type` (string, enum)

Only subscribe operation: Choose whether the subscription should be polled by the Connectware or whether it should be notified by DNC event notifiers.

This element must be one of the following enum values:

* `poll`
* `notify`

Example: `"notify"`


---

# 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.cybus.io/2-6-1/connectors/shop-floor-connectors/heidenhain-dnc/heidenhainendpoint.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.