> 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-hardware/modules/depence-logic-module/logic-module-items/outputs.md).
# Outputs
###  Write DMX Universe
A complete DMX universe can be connected to the input. Then it´s mixed into the internal DMX buffer. The number of universes to be connected can be set via Count. With Start by DMX Line the index of the first universe.
###  Variable Text
Writes a text to a variable named memory cell from which it can be displayed in the User Live Panel. A text and a text color can be set if the condition is true or false.\
Pay attention to the upper-lower case of the variables name.
###  Write MIDI Note
Sends a MIDI note with a velocity value from the MIDI Output.
###  Write MIDI Controller
Writes a MIDI controller value to the MIDI output.
###  Variable Value
Writes the value at the module input into a variable. Pay attention to the upper - lower case of the variables name.
###  Analog Output
Writes the module input value to an analog output from vServer4.
###  Write DMX
Converts the module input value to a DMX value (0-255) and writes it to a DMX address.
###  Write Virtual Master
Writes a module input value to a virtual master. To do this, drop a virtual master from the repository to this module.
---
# 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-hardware/modules/depence-logic-module/logic-module-items/outputs.md?ask=&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.