> For the complete documentation index, see [llms.txt](https://docs.freeflysystems.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.freeflysystems.com/ecosystem/payloads/wiris-pro-thermal/integration-for-3rd-party-applications/electrical-interface.md).

# Electrical Interface

## Connector

Wiris Pro Payload uses the Smart Dovetail interface for power, data, and control. Pinouts for this connector can be found at both links bellow:

{% content-ref url="<https://github.com/freefly-systems/wiki-public-ecosystem/blob/main/ecosystem/development-tools/payload-mounting-interfaces.md>" %}
<https://github.com/freefly-systems/wiki-public-ecosystem/blob/main/ecosystem/development-tools/payload-mounting-interfaces.md>
{% endcontent-ref %}

{% embed url="<https://github.com/pixhawk/Pixhawk-Standards/blob/master/DS-014%20Pixhawk%20Payload%20Bus%20Standard.pdf>" %}
Pixhawk Payload Bus specs
{% endembed %}

The Wiris video and control is passed through over the ethernet pins on the smart dovetail. Info on communicating with the camera can be found in the document bellow.

{% file src="/files/SlU62ON7jAVaAiQ5Tu4K" %}
Wiris Ethernet SDK
{% endfile %}

The gimbal utilizes Mavlink for control from the aircraft over the UART pins.

## Power requirements:

The Wiris is powered directly from the gimbal, these specs account for the entire package in operation. Power is drawn from the V\_BATT pins on the Smart Dovetail pinout.

| Voltage           | 18-25.2V                                |
| ----------------- | --------------------------------------- |
| Current (Nominal) | 0.7-1.5A depending on flight conditions |
| Current (Max)     | 5A                                      |


---

# 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.freeflysystems.com/ecosystem/payloads/wiris-pro-thermal/integration-for-3rd-party-applications/electrical-interface.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.