> For the complete documentation index, see [llms.txt](https://support.senterasensors.com/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.senterasensors.com/home/65r-sensor-user-guide/integration-information/communication-protocol/dji-skyport.md).

# DJI Skyport

## Requirements

DJI Skyport operation is available on DJI Skyport equipped hardware:

{% content-ref url="/pages/pmZa92TsP8xnGJSNvfe0" %}
[Interface Variants](/home/65r-sensor-user-guide/65r-sensor/anatomy/gimbal/interface-variants.md)
{% endcontent-ref %}

To operate the 65R sensor in this mode, the camera must be set up for one of the DJI Skyport configurations. For DJI M200 and M300 series aircraft, select the type "DJI Skyport - M2XX/M3XX".

<figure><img src="https://3675182560-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXxc0lOfDa92aCfFa5lb4%2Fuploads%2Fgit-blob-abdbeb02f9953f3eac3ee32ab071b4e975f9bd3c%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>

For DJI M400 aircraft, select the type "DJI Skyport - M400".

<figure><img src="https://3675182560-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXxc0lOfDa92aCfFa5lb4%2Fuploads%2Fgit-blob-cfe36dcac1e0e75561ddd5205435760eb73973aa%2Fimage%20(373).png?alt=media" alt=""><figcaption></figcaption></figure>

If the 65R is not configured for the required mode, follow the instructions to update the configuration:

{% content-ref url="/pages/e5cOPQCznLLL0THgNXnJ" %}
[How To Change Configuration](/home/65r-sensor-user-guide/65r-sensor/configuration-and-settings/configuration/how-to-change-configuration.md)
{% endcontent-ref %}

## Mode Description

In this mode, the 65R is tightly integrated with the DJI airframe. This allows for gimbal control and image triggering from the DJI hand controller (e.g., using the FieldAgent iOS application). All data necessary for metadata population is available and automatically written to generated imagery.

## Skyport Hardware Compatibility

DJI has produced two versions of Skyport hardware, designated as Skyport-V1 and Skyport-V2. A Sentera gimbal built with Skyport-V2 hardware will contain an etching or sticker on the back of the assembly:

<figure><img src="https://3675182560-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXxc0lOfDa92aCfFa5lb4%2Fuploads%2FyHQGCefj6NBz0pljtioP%2Fimage.png?alt=media&amp;token=35719e7d-f944-4f6f-92bb-5a012866c0bc" alt="" width="378"><figcaption></figcaption></figure>

A Sentera gimbal built with Skyport-V1 hardware will not contain a corresponding etching or sticker. DJI aircraft only support specific versions of DJI Skyport hardware. The list of compatibility follows:

<table><thead><tr><th width="179">DJI Airframe</th><th width="286">Skyport Hardware Compatibility</th></tr></thead><tbody><tr><td>M200/M210 V1</td><td>Skyport-V1 only</td></tr><tr><td>M200/M210 V2</td><td>Skyport-V1 only</td></tr><tr><td>M300 RTK</td><td>Skyport-V1 and Skyport-V2</td></tr><tr><td>M350 RTK</td><td>Skyport-V2 only</td></tr><tr><td>M400</td><td>Skyport-V2 only</td></tr></tbody></table>

Contact Sentera if you want to fly a Sentera gimbal on an incompatible DJI airframe. It is possible for Sentera to modify a gimbal (e.g., Skyport-V1 -> Skyport-V2), but this requires significant hardware modification.

{% hint style="info" %}
Stand-alone Sentera GPS mode can still be used when operating on an incompatible airframe. However, additional setup will be required, such as configuring the 65R overlap percentage, because the camera is no longer tightly integrated with the airframe.
{% endhint %}

{% content-ref url="/pages/YpCv3HvZTz7MyNdGF0vm" %}
[Stand Alone Mode (External GPS)](/home/65r-sensor-user-guide/65r-sensor/operation/standard-operating-procedure/stand-alone-mode-external-gps.md)
{% endcontent-ref %}

## Skyport Firmware Compatibility

DJI aircraft require a specific version of DJI Skyport firmware to operate successfully. The following list identifies this required firmware:

<table><thead><tr><th width="190">DJI Aircraft</th><th align="center">Skyport-V1 Firmware</th><th align="center">Skyport-V2 Firmware</th></tr></thead><tbody><tr><td>M200/M210 V1</td><td align="center">v01.03.00.09</td><td align="center">-</td></tr><tr><td>M200/M210 V2</td><td align="center">v01.04.00.00</td><td align="center">-</td></tr><tr><td>M300 RTK</td><td align="center">v01.04.00.00</td><td align="center">V01.03.05.00</td></tr><tr><td>M350 RTK</td><td align="center">-</td><td align="center">V01.03.05.00</td></tr><tr><td>M400</td><td align="center">-</td><td align="center">V01.04.11.14</td></tr></tbody></table>

The version of DJI Skyport firmware can be viewed and upgraded using the DJI Assistant 2 application. See DJI documentation for details and instructions.


---

# 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://support.senterasensors.com/home/65r-sensor-user-guide/integration-information/communication-protocol/dji-skyport.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.