> For the complete documentation index, see [llms.txt](https://extend-robotics.gitbook.io/user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://extend-robotics.gitbook.io/user-guide/cortex-api/sensekit.md).

# Sensors

Application Programming Interfaces for SenseKit

### Firmware

Firmware is packaged as:

* x86-64 case -  .run installer with binary deb packages and OS tweaks, communicating with 3rd party rosnodes through the ROS1 protocol
* arm64 Jetson case - docker image with binaries communicating with 3rd party rosnodes through the ROS1 protocol

### Available Data

A Sensor consumes ROS data from camera including depth, RGB, calibration and geometric relationships. No specific data is shared for 3rd party by Sensor but the same data it uses is available also for 3rd party using ROS interfaces.&#x20;

Sensor settings may be configured using AMAS (sensor dependent).

### Interfacing New Sensors

For unsupported sensors, the process may require custom work.

#### Requirements for sensor's ROS driver

The minimum to integrate new sensor is ROS driver with:

* color topic (RGB) and camera\_info
  * typically `image_raw` and `camera_info` topics
* depth topic (2D range image) and camera\_info
  * typically `image_raw` and `camera_info` topics
  * depth in 16 bit unsigned mm range format (also called OpenNI)
* tf2 geometric relationship data between depth/color subsensors (extrinsics)
  * typically camera has depth and color subsensors

#### Integration process

Typically, integrating a new sensor requires (assuming ROS driver exists):

* writing sensor-specific ROS launch files&#x20;
  * for streaming services
  * for calibration services
* ensuring optical distortion models used by the sensor are supported
* ensuring reasonable data workflow
  * decoupling ROS data from compression may be necessary
    * image republish node(lets) may be used
* ensuring compatibility with custom compression (image transports)
  * support for sensor image pixel format may be added as needed
* Ensuring depth/RGB synchronization is within tolerance
  * typically driver, specific settings


---

# 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://extend-robotics.gitbook.io/user-guide/cortex-api/sensekit.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.
