> For the complete documentation index, see [llms.txt](https://docs.payfacto.com/payfacto-knowledge/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payfacto.com/payfacto-knowledge/veloce-pos/velmix-lq-232-ip/installation.md).

# Installation

### Installation

For an efficient work zone, place the Velmix LQ controller, activator holder, bottles and POS screen close together. The user will frequently have to touch the screen while handling the bottles.

{% hint style="info" %}
NOTE : Before you begin the installation, check the counter top thickness to ensure that the screws won't protrude through the top.
{% endhint %}

**To install your Velmix LQ:**

1. Firmly screw the controller and activator bracket (AZC-900036) to the underside of the counter top using the supplied screws (AZC-501035).

\
![Installation Velmix](https://documentation.payfacto.com/LiquorControl/Velmix/UG/CA-EN/assets/images/Picture25.png)

2. Connect the RS232 communication cable (AVP-002113) to the Veloce POS or the Ethernet cable (AVP-002118) to the network.
3. Plug the 120V cord into the power supply, then into the 120V outlet.

{% hint style="warning" %}
IMPORTANT! Do not alter the angle or bend the activator support, as Velmix automatically releases the plug (if programmed) when in the resting position. Bending the support may prevent this function from working properly.
{% endhint %}


---

# 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.payfacto.com/payfacto-knowledge/veloce-pos/velmix-lq-232-ip/installation.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.