> For the complete documentation index, see [llms.txt](https://docs.gremsy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gremsy.com/payloads/general/gremsy-payload-sdk.md).

# GREMSY PAYLOAD SDK

Designed for developers and integrators, the Gremsy Payload SDK provides the tools you need to customize and control your Gremsy Payload and Gimbal system for unique applications.

<https://github.com/Gremsy/PayloadSdk/tree/payloadsdk_v2>

### Hardware

* Ubuntu PC (x86\_64)
* Jetson platform (aarch64)
* Raspberry Pi

### Clone the project

```
git clone -b develop --recurse-submodules https://github.com/Gremsy/PayloadSdk.git

cd PayloadSdk/libs/gSDK/
git checkout gSDK_V3_alpha
git pull origin gSDK_V3_alpha
```

### Hardware setup

PayloadSDK supports 2 control conections, that's configured at payloadsdk.h:

<figure><img src="https://github.com/Gremsy/PayloadSdk/raw/master/PayloadSDK_HW_Setup.png" alt=""><figcaption></figcaption></figure>

**Figure 1:** Hardware setup use Ethernet or UART connection

### How to build

* Install required lib

```
sudo apt-get install libcurl4-openssl-dev libjsoncpp-dev
```

* Build project

```
cd PayloadSdk
mkdir build && cd build

cmake -Dpayload ../
e.g. cmake -DVIO=1 ../
     cmake -DGHADRON=1 ../
     cmake -DZIO=1 ../

make -j6
```


---

# 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.gremsy.com/payloads/general/gremsy-payload-sdk.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.