# Configuration

## Introduction

The configuration page is used to change:&#x20;

* How the 6X interacts with the aircraft it is connected to.
* The triggering method

In most cases the 6X is preconfigured based on what aircraft/system the camera is ordered for and the configuration doesn't need to be changed.&#x20;

{% hint style="info" %}
If using the Inspired Flight RTK PPK Module please ensure the sensor is set to the Sentera GNSS configuration. View the Support link below for information on changing sensor configuration. \
[6X Sensor | Sentera Support](https://support.senterasensors.com/home/rtk-ppk-module/setup-and-installation/sentera-sensor-setup/6x-series-sensors#software-configuration)&#x20;
{% endhint %}

To learn how to change the configuration of the 6X or change the overlap for stand-alone mode, see the pages linked below.

<figure><img src="/files/lm2q2q4UhH1Kf85hrZjg" alt=""><figcaption></figcaption></figure>

***

## How To Instructions

{% content-ref url="/pages/xdW5hlU4peNfQEtLr4SD" %}
[How To Change Overlap Settings](/home/6x-series-sensors-user-guide/6x-series-sensors/configuration-and-settings/configuration/how-to-change-overlap-settings.md)
{% endcontent-ref %}

{% content-ref url="/pages/aNkd97dHeg95LL7U6UA3" %}
[How To Change Configuration](/home/6x-series-sensors-user-guide/6x-series-sensors/configuration-and-settings/configuration/how-to-change-configuration.md)
{% endcontent-ref %}

***

## Platform/Metadata Configuration

The platform and metadata configuration is used to tell the 6X what aircraft it will be used with and where data sources (altitude, GPS, heading, etc) will come from.

### Config File

The Config File field will display the currently config file. It also contains the change button used for changing the config file.&#x20;

<figure><img src="/files/c5bODGU6OkVRFy7vpWos" alt=""><figcaption></figcaption></figure>

Depending on the current config file there will be limited config files displayed in the change menu. To display all configuration file options select the "All platform configurations" and/or the "Advanced configurations" radio buttons as shown in the advanced tab below.&#x20;

{% tabs %}
{% tab title="Standard" %}

<figure><img src="/files/K4PtCUP9VYOuVgqNkcaY" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/cClZXDE6KqJl5iEOtcyj" alt=""><figcaption></figcaption></figure>

{% endtab %}

{% tab title="Advanced" %}

<figure><img src="/files/wJIR6FXgGMnZxXzfcjzI" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/npP1Oekklhb8hgFubH0N" alt=""><figcaption></figcaption></figure>
{% endtab %}
{% endtabs %}

### Config Type

The Config Type is tied to the config file and gives more specific instruction about the metadata sources. The config names and data source information are listed below.&#x20;

{% tabs %}
{% tab title="Gimballed" %}

<table><thead><tr><th width="115">Name</th><th width="128" align="center">GPS Source</th><th width="151" align="center">Attitude Source</th><th width="144" align="center">Trigger Source</th><th align="center">Platform Complatibility</th></tr></thead><tbody><tr><td>DJI Skyport</td><td align="center">DJI Autopilot</td><td align="center">DJI Autopilot</td><td align="center">DJI Autopilot</td><td align="center">M300<br>M350<br>M200<br>M210</td></tr><tr><td>Sentera GPS</td><td align="center">Sentera External GPS</td><td align="center">65R Sensor Internal IMU</td><td align="center">65R Sensor</td><td align="center"><p>M300<br>M350<br>M200<br>M210</p><p>Astro<br>IF800<br>IF1200<br>Custom</p></td></tr></tbody></table>
{% endtab %}

{% tab title="Freefly" %}

<table><thead><tr><th>Name</th><th width="128" align="center">GPS Source</th><th width="102" align="center">Attitude Source</th><th width="144" align="center">Trigger Source</th><th align="center">Platform Complatibility</th></tr></thead><tbody><tr><td>Freefly Astro Gimbal </td><td align="center">Astro Autopilot</td><td align="center">Astro Autopilot</td><td align="center">Astro Autopilot</td><td align="center">Astro</td></tr></tbody></table>
{% endtab %}

{% tab title="Inspired Flight" %}

<table><thead><tr><th>Name</th><th width="128" align="center">GPS Source</th><th width="103" align="center">Attitude Source</th><th width="144" align="center">Trigger Source</th><th align="center">Platform Complatibility</th></tr></thead><tbody><tr><td>IF800</td><td align="center">IF800 Autopilot</td><td align="center">IF800 Autopilot</td><td align="center">IF800 Autopilot</td><td align="center">IF800</td></tr><tr><td>IF800 - Sentera GNSS</td><td align="center">Sentera RTK PPK Module</td><td align="center">IF800 Autopilot</td><td align="center">IF800 Autopilot</td><td align="center">IF800</td></tr><tr><td>IF1200A</td><td align="center">IF200 Autopilot</td><td align="center">IF200 Autopilot</td><td align="center">IF200 Autopilot</td><td align="center">IF1200</td></tr><tr><td>IF1200A - Sentera GNSS</td><td align="center">Sentera RTK PPK Module</td><td align="center">IF200 Autopilot</td><td align="center">IF200 Autopilot</td><td align="center">IF200</td></tr></tbody></table>

{% hint style="warning" %}
In the IF800 GNSS configuration, the RTK-PPK module is required to initialize the sensor. Without the RTK-PPK module, the sensor will not get green LED indicator lights, and will not be ready to capture data.
{% endhint %}
{% endtab %}

{% tab title="Gremsy Hyper Quick" %}

<table><thead><tr><th width="144">Name</th><th width="120" align="center">GPS Source</th><th width="107" align="center">Attitude Source</th><th width="144" align="center">Trigger Source</th><th align="center">Platform Complatibility</th></tr></thead><tbody><tr><td>MAVLink-V2</td><td align="center">MAVlink Autopilot</td><td align="center">MAVlink Autopilot</td><td align="center">MAVlink Autopilot</td><td align="center">Custom MAVlink Autopilot Systems</td></tr></tbody></table>
{% endtab %}

{% tab title="DGR" %}

<table><thead><tr><th>Name</th><th width="128" align="center">GPS Source</th><th width="124" align="center">Attitude Source</th><th width="144" align="center">Trigger Source</th><th align="center">Platform Complatibility</th></tr></thead><tbody><tr><td>DJI M300 DGR</td><td align="center">Sentera DGR Sensor Package</td><td align="center">Sentera DGR Sensor Package</td><td align="center">Sentera DGR Sensor Package</td><td align="center">M300<br>M350</td></tr><tr><td>DJI M600 DGR</td><td align="center">Sentera DGR Sensor Package</td><td align="center">Sentera DGR Sensor Package</td><td align="center">Sentera DGR Sensor Package</td><td align="center">M600</td></tr></tbody></table>
{% endtab %}

{% tab title="OEM" %}

<table><thead><tr><th width="110" align="center"> Name</th><th width="125" align="center">GPS Source</th><th width="155" align="center">Attitude Source</th><th width="149" align="center">Trigger Source</th><th align="center">Platforms</th></tr></thead><tbody><tr><td align="center">DJI M600 OSDK</td><td align="center">DJI A3 Autopilot</td><td align="center">DJI A3 Autopilot</td><td align="center">DJI A3 Autopilot</td><td align="center">M600</td></tr><tr><td align="center">MAVlink</td><td align="center">MAVlink V1</td><td align="center">MAVlink V1</td><td align="center">MAVlink V1</td><td align="center">Most MAVlink enabled platforms with configurable serial port. </td></tr><tr><td align="center">Sentera GPS</td><td align="center">Sentera GPS</td><td align="center">6X Sensor Internal IMU</td><td align="center">6X Sensor</td><td align="center">Custom</td></tr></tbody></table>
{% endtab %}
{% endtabs %}

{% hint style="info" %}
Configurations with 6X Sensor Internal IMU as an Attitude source does not contain yaw/heading information.
{% endhint %}

***

## Trigger

The trigger field is used to set the trigger type and related settings.&#x20;

<figure><img src="/files/rpLz7Dgn6GbHpfWvqV8N" alt=""><figcaption></figcaption></figure>

### Trigger Type

{% tabs %}
{% tab title="Command" %}
The Command trigger type is used when the trigger commands come directly from the aircraft autopilot.&#x20;

<figure><img src="/files/rZCiPe2ZHBQaRjdQCH4K" alt=""><figcaption></figcaption></figure>

No settings are provided for this mode. The sensor will only trigger if it receives a trigger command from MAVLink, the web page, Payload SDK, or the custom Sentera Protocol.
{% endtab %}

{% tab title="External" %}
The External trigger type is used when an external source is used to trigger the 6X.&#x20;

There are 4 options for the external trigger commands. See the details in the table below.&#x20;

#### Rising/Falling Edge

<figure><img src="/files/xfbTOBdYkS8WPqvJaFz7" alt=""><figcaption></figcaption></figure>

#### Low/High PWM

<figure><img src="/files/wRzT5eI3F27m6BEfmZ9O" alt=""><figcaption></figcaption></figure>

<table><thead><tr><th width="151.5">Mode</th><th>Description</th></tr></thead><tbody><tr><td>Rising Edge</td><td>The trigger input must be stable for 50 milliseconds to register as a commanded trigger. This is also known as the mechanical switch debounce period.</td></tr><tr><td>Falling Edge</td><td>The trigger input must be stable for 50 milliseconds to register as a commanded trigger. This is also known as the mechanical switch debounce period.</td></tr><tr><td>Low PWM</td><td>The lower value of the PWM TRIGGER input in milliseconds.</td></tr><tr><td>High PWM</td><td>The higher value of the PWM TRIGGER input in milliseconds.</td></tr></tbody></table>

The trigger input is the TRIGGER signal on connector J2.

{% content-ref url="/pages/DGnlQRaBW3scGRGF7DMd" %}
[I/O](/home/6x-series-sensors-user-guide/integration-information/i-o.md)
{% endcontent-ref %}

{% hint style="info" %}
For all modes, the TRIGGER input must be actively driven using 3.3V logic levels.
{% endhint %}
{% endtab %}

{% tab title="Interval" %}
The Interval trigger type is used to capture images at a specified time interval rather than distance travelled. The minimum capture interval is 0.200 seconds (5Hz).&#x20;

<figure><img src="/files/MJKQRv02ApE6s4PlneuI" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
The sensor will start triggering the moment a session starts, so this may result in images taken on the ground as well as in the air.
{% endhint %}
{% endtab %}

{% tab title="Overlap" %}
The Overlap trigger type is used when the the 6X is being powered by an aircraft,  not  receiving triggers from the aircraft or an external device, and classical overlap settings are used. This is useful for many applications as it removes the need for in depth integration with the aircraft. The 6X in combination with the Light Sensor/GPS will operate without direct communication with the aircraft.&#x20;

Once 6X detects it is more than the minimum altitude above the takeoff point, it begins to capture images and continues to do so to achieve the correct image overlap. Triggering stops when it detects the platform has departed from the minimum altitude.

The 6X works with any ground station or flight controller in this mode, as it makes calculations about altitude using the GPS receiver’s measured altitude at takeoff.

{% hint style="info" %}
This is the standard setting for systems without MAVLink or DJI Skyport.
{% endhint %}

There are 2 overlap modes:&#x20;

#### Auto Height (most common)

The 6X detects the flight altitude (AGL) based on the detected GPS altitude between where the session starts (on the ground) and where the aircraft flies at (survey altitude).&#x20;

<figure><img src="/files/Di3rnPbTnjY8CSLhhmYa" alt=""><figcaption></figcaption></figure>

#### Fixed Height

The 6X assumes the survey altitude of the aircraft matches the fixed height input in the altitude box.&#x20;

<figure><img src="/files/jSgfSTt9MOTSSRge9JXG" alt=""><figcaption></figcaption></figure>

| Item          | Description                                                                                                                                                                                                                                                                                                                                   |
| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Overlap       | Changes the frequency of the trigger based on the overlap of the image. Fifty percent overlap means that when the sensor has moved such that 50% of the image is new, an image will be triggered. Use the slider to adjust the overlap percentage in the text box. There are markers present in the slider at settings for typical use cases. |
| Altitude Type | Selects whether a fixed altitude is used for calculating overlap, or automatic altitude determined from GPS.                                                                                                                                                                                                                                  |
| Atlitide      | Selects whether a fixed altitude is used for calculating overlap, or automatic altitude determined from GPS.                                                                                                                                                                                                                                  |
| Min AGL       | To prevent triggers from occurring while walking around on the ground, a minimum altitude can be set. Any triggers that occur due to the sensor moving around will be blocked if the sensor estimates that its altitude is less than this number.                                                                                             |
| Min Distance  | If the sensor is flying very low to the ground, the overlap setting may result in very rapid triggers. To prevent a flood of images, a minimum trigger distance can be set. This distance is the minimum distance the sensor must travel before the next trigger can be sent.                                                                 |
| {% endtab %}  |                                                                                                                                                                                                                                                                                                                                               |
| {% endtabs %} |                                                                                                                                                                                                                                                                                                                                               |


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://support.senterasensors.com/home/6x-series-sensors-user-guide/6x-series-sensors/configuration-and-settings/configuration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
