> 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/known-issues.md). # Tips & practical notes This page collects tips and practical notes for operating the ODAC Connector with [Zumbach ODAC](/en/connect/ot-connectivity/supported-industrial-protocols/odac.md) measuring heads. It explains common observations and how best to handle them. ## Variable naming differs by protocol ### Symptom After Variable Discovery, the variables carry cryptic numeric codes (e.g. `a925`) and are hard to map to the measured values you are looking for. ### Cause An ODAC measuring head can communicate via two protocols: the native **ODAC** protocol and the **ANSI Host** protocol. The variable set is identical in both protocols. It depends solely on the capabilities of the device. A measuring head with two measuring positions, for example, leaves the variables for positions 3 and 4 empty regardless of the protocol. Only the naming of the variables differs: * In the native **ODAC** protocol, all variables carry systematic two-letter codes (e.g. `DL` or `UG`) and can be identified directly. * In the **ANSI Host** protocol, the variables are encoded purely numerically (e.g. `a925`). There is no consistent scheme, so the values are hard to identify. ENLYZE detects the active protocol automatically when the connection is established. ### Resolution options * The codes listed under [commonly recorded measured values](/en/connect/ot-connectivity/supported-industrial-protocols/odac.md#commonly-recorded-measured-values) refer to the ODAC protocol. * If the variables appear with numeric codes, the measuring head is running in the ANSI Host protocol. So that the variables are named systematically and easier to map, ENLYZE can switch the device to the ODAC protocol. Switching the protocol is a persistent write. It is port-specific and therefore only affects the connection to the Edge Device, not other devices or HMIs on the measuring head. The switch is done in coordination with ENLYZE. Contact us at . {% hint style="info" %} During normal operation, the ODAC Connector only reads measured values and does not change the configuration of the measuring head. {% endhint %} ## Measured values are only valid with a product in the measuring field ### Symptom The recorded diameter shows implausible values (e.g. `0` or an error code), even though the connection is established. ### Cause An ODAC measures the product in its measuring field without contact. If no product is in the measuring field (e.g. when the line is stopped or during threading), the device cannot provide a valid diameter and instead reports an error code or a value outside the measuring range. ### Resolution options * This behavior is expected and not a connection error. As soon as a product is back in the measuring field, the measuring head provides valid values again. * The `EB` variable (error code) can be recorded alongside to make such phases traceable afterward. --- # 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/known-issues.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.