> For the complete documentation index, see [llms.txt](https://help.depence.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.depence.com/depence-tips-and-tricks/using-variables.md).

# Using Variables

Connecting controls in different modules and pages

#### What are variables: Variables are named containers into which any values can be written and read from other places.

To connect the LogicModule to the UserLivePanel in Depence, the system uses internal variable fields.

<figure><img src="https://content.gitbook.com/content/SJPsyh5CBOise9BtVNGO/blobs/kMcGod4Vm3BxuGk0Cb3z/image.png" alt=""><figcaption></figcaption></figure>

In this example, two digital inputs of a vNano/wec were read out and written to two variables.\
Variable 1 = IsLightOn \
Variable 2 = IsEnabled

Now two LED controls were placed on the UserLivePanel and each given the same variable name.

Thus, the state of the digital outputs in the LogicModule is now transferred to the LEDs on the UserLivePanel.

You can also use variables to exchange information between different LogicModule pages.

Furthermore, variables are suitable for displaying different texts on the UserLivePanel depending on the states in the LogicModule.


---

# 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://help.depence.com/depence-tips-and-tricks/using-variables.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.