> 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/martin-p3-protocol.md).

# Martin P3 Protocol

Depence supports the Martin P3 protocol for transmitting pixel data over the network.

#### Setup

1. First, make sure that a Visualizer has been added under Hardware.
2. Start the Martin P3 software on another PC.

{% hint style="info" %}
Due to current protocol limitations, running Depence and the P3 software on the same PC is currently not supported.
{% endhint %}

#### Fixtures

Select the fixtures that you want to control via P3.

In the Settings window, right-click and add the Martin P3 extension.

In the settings of the P3 extension, select the Martin P3 Controller IP. The PC running the P3 software should appear in this list.

<figure><img src="https://2214631663-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSJPsyh5CBOise9BtVNGO%2Fuploads%2FHOhciPr3MjSv7IF2lRCm%2Fimage.png?alt=media&amp;token=78bc628f-d3bc-467d-ba4e-a4c9d786edbb" alt=""><figcaption></figcaption></figure>

&#x20;

#### Martin P3 Fixture ID

When the extension is created, the current Fixture ID is automatically assigned.

If you do not need to use a different ID, you can leave this field empty.


---

# 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/martin-p3-protocol.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.