> For the complete documentation index, see [llms.txt](https://docs.enlyze.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enlyze.com/en/connect/ot-connectivity/supported-industrial-protocols/odac.md).
# ODAC
This guide walks you through connecting [Zumbach](/en/connect/ot-connectivity/supported-machine-manufacturers/zumbach.md) ODAC measuring heads. The ODAC Connector reads the measured values of the measuring head (such as diameter, deviation, and production length) directly via its Ethernet interface.
## Supported devices
* [Zumbach ODAC](/en/connect/ot-connectivity/supported-machine-manufacturers/zumbach/odac.md) measuring heads with an Ethernet interface
The Zumbach ODAC measuring head communicates either via the native **ODAC** protocol or the **ANSI Host** protocol. ENLYZE detects which protocol is active automatically when the connection is established. In most cases you do not need to worry about this. See [Tips & practical notes](/en/connect/ot-connectivity/supported-industrial-protocols/odac/known-issues.md) for background.
## Connect an ODAC data source
{% stepper %}
{% step %}
#### Connect the data source to the network
If not already done, establish a network connection between the ODAC measuring head and the Edge Device. See [Integration scenarios](/en/connect/integration-scenarios.md) for the available options.
{% hint style="info" %}
You need the IP address of the measuring head for the connection. It cannot be derived automatically. Instead, you read it directly from the HMI:
1. Log in to the HMI. The password is printed in the device manual. If it has been changed, ask the person responsible for the machine.
2. Navigate to the console in the menu.
3. Query the IP address with the matching command: `SL` in ODAC mode, `a930` in ANSI Host mode (service port), or `a940` in ANSI Host mode (host port).
{% endhint %}
{% endstep %}
{% step %}
#### Create the data source
Open the [ENLYZE Manufacturing Data Platform](https://app.enlyze.com/platform), select the machine you want to add the data source to, and click **+ Data source**.
Next, fill in the **Data source details** form. The following table shows an example value for each field when connecting a Zumbach ODAC measuring head:
| Field | Example | Comment |
| ----------------------- | ------------------------- | ----------------------------------------------------------------------------------------------------- |
| **Name** | `Zumbach ODAC 18XY` | Pick a descriptive name for the data source |
| **Machine** | `Test Machine ABC - Köln` | Each data source is assigned to exactly one machine (preselected from the previous step) |
| **Device manufacturer** | `Zumbach` | Name of the device manufacturer |
| **Device information** | `ODAC 18XY` | Model number, version, or CPU of the measuring head |
| **Note** | (optional) | Comments or important remarks |
| **Edge device** | `quirky-keller` | Printed on a sticker on each Edge Device. Follows the pattern `adjective-scientist` |
| **Connector** | `ODAC` | Select the ODAC Connector |
| **IP address** | `192.168.17.2` | The IP must be [reachable](/en/connect/edge-device/enlyze-edge/network-tools.md) from the Edge Device |
| **Port** | `2020` | Default: `2020`. The port is fixed to `2020` on the ODAC |
Connection details of an ODAC data source
Finally, click **Save**.
{% endstep %}
{% step %}
#### Add variables
The ODAC Connector supports [Variable Discovery](/en/connect/ot-connectivity.md#variable-discovery), so variables are added automatically. The first Variable Discovery run is triggered as soon as you save the data source.
ODAC variables carry short two-letter codes (e.g. `DA` for the measured diameter). Each variable comes with a description so you can identify the relevant measured values.
{% hint style="warning" %}
After Variable Discovery completes, no data is being recorded yet. You first need to select the [variables](/en/variable-mapping/contextualisation.md) to record. Follow our variable onboarding flow.
{% endhint %}
{% endstep %}
{% endstepper %}
## Commonly recorded measured values
The following variables are the most commonly recorded in practice. Which of them a given measuring head provides depends on the model and its configuration.
| Code | Measured value |
| ---- | --------------------------- |
| `DA` | Diameter (measured value 1) |
| `DB` | Deviation 1 (RMS diameter) |
| `DC` | Measured value 2 |
| `DE` | Measured value 3 |
| `DR` | Production length |
| `MJ` | Neckdown counter |
| `MK` | Lump counter |
| `EB` | Device error code |
## See also
* [Tips & practical notes](/en/connect/ot-connectivity/supported-industrial-protocols/odac/known-issues.md): notes on operating the ODAC Connector and how to handle common effects.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.enlyze.com/en/connect/ot-connectivity/supported-industrial-protocols/odac.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.