> 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/single-sensor/single-sensor/single-sensor-technical-documentation-and-integration-guide.md).

# Single Sensor Technical Documentation & Integration Guide

**Resources**

Scroll to the bottom of the page to download the *Using Sentera Sensors with MAVLink and Pixhawk* document, as well as download these documents below for technical details on the Sentera Singles Sensor and instructions for integrating with other systems:

{% file src="/files/tcUG39vCyFn5yeDG3L8C" %}

{% file src="/files/35OaZlIBc1rxsL3FbIhE" %}

{% file src="/files/qZUOIpzI4Ln3hxbdc8d7" %}

**Sentera Single Hardware Integration**

You can easily integrate the Sentera Single Sensor with a wide range of systems. These include interfaces to power the camera, as well as external devices that can be powered by the camera. Supported devices include: 

* Lockheed Martin Kestrel autopilot (3.3V UART)
* Pixhawk autopilot (3.3V UART)
* MAVLink based systems (3.3V UART)
* Sentera based systems (100Base-T Ethernet)
* GPS based triggering/metadata (PWR and 3.3V UART)
* Sentera Light Sensor (3.3V I2C)
* Customized ICD options available upon request

You can purchase camera cable interfaces directly from Sentera. Major suppliers also offer pre-terminated cables/contracts that allow you to create cable installations to suit your specific requirements. \
\
J1 - Ethernet 

Connector J1 is a 100Base-T Ethernet interface that can be used for all camera functions as detailed below. Most standard interfaces do not require the Ethernet interface. You can also use the J1-Ethernet interface to access the camera's microSD card when the device is on the ground.

| Pin | Signal | Type | T568A Color |
| --- | ------ | ---- | ----------- |
| 1   | TX+    | I/O  | GRN/WHT     |
| 2   | TX-    | I/O  | GRN         |
| 3   | RX+    | I/O  | ORG/WHT     |
| 4   | RX-    | I/O  | ORG         |

Connector: 53047-0410

Mating Connector: 51021-0400

\
J2 - Power and I/O

Connector J2 is a Power and I/O connector. It typically is used to help trigger the camera from the flight controller of GPS receiver. It provides a 3.3V voltage source to power the Sentera Light Sensor and/or an external GPS receiver. <br>

| Pin | Signal   | Type | Description                           |
| --- | -------- | ---- | ------------------------------------- |
| 1   | VBATT    | PWR  | 6 to 26V Input - 2.4W @ 12VIn typical |
| 2   | GND      | PWR  |                                       |
| 3   | (3V3)RXD | I    | 3.3V UART Input                       |
| 4   | (3V3)TXD | O    | 3.3V UART Output                      |
| 5   | VCC\_3V3 | PWR  | 3.3VDC @ 1A. Power Output             |
| 6   | GND      | PWR  |                                       |
| 7   | (3V3)SCL | I/O  | 3.3V I2C - Light Sensor               |
| 8   | V)SDA    | I/O  | 3.3V I2C - Light Sensor               |

Connector: 53047-0810

Mating Connector: 51021-0800


---

# 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/single-sensor/single-sensor/single-sensor-technical-documentation-and-integration-guide.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.