> 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-construction/depence-connect-dependencies.md).

# Connect Dependencies

Dependencies are logically connected between fixtures. These can share information on water (pressure, flow rate, etc), lighting or power. Dependencies are elemental, especially for fountain devices.

![](https://content.gitbook.com/content/SJPsyh5CBOise9BtVNGO/blobs/BjnrBYIo3DVLSWgVd2XK/40992785.png)

*A classic example: Nozzles connected to valves, which are further connected to a water distributor, which gets finally powered by one or more pumps.*

In general, there are two types of fixtures:

**Active Fixtures:**\
All fixtures, which are delivering information and are usually DMX controlled like pumps or valves.

**Passive Fixtures:**\
All fixtures, which do only have dependency connectors waiting for an input signal. Like nozzles.

Passive fixtures, which are added to the scene, will always simulate input of 100% until they get connected to an active fixture. For example, a nozzle fixture will emit water even if it's not connected to a pump. This behavior makes the scene-building process easier.


---

# 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-construction/depence-connect-dependencies.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.