> 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/gremsy-tiny-series/lynx/faq.md).

# FAQ?

<details>

<summary>How many sensor cameras are on the Lynx?</summary>

Lynx payload features two sensors: an EO (Electro-Optical) camera and an IR (Infrared) camera

</details>

<details>

<summary>How many versions of the Lynx are available?</summary>

There are two versions of the Lynx:

* **LYNX Standard**
* **LYNX NDAA-Compliant**

</details>

<details>

<summary>What drone platforms are compatible with the Lynx?</summary>

The Lynx is compatible with major autopilot platforms, including

* **Pixhawk**
* **CubePilot**

</details>

<details>

<summary>Does Lynx use a Quick Release system?</summary>

No, Lynx does not use a Quick Release.

</details>

<details>

<summary>How to Use Lynx with Full Solution?</summary>

Let’s integrate it with the Gremsy Mainboard for maximum performance and ease of use.

</details>

<details>

<summary>What is the weight of the Lynx?</summary>

* **Lynx Standard Version:**  235 grams
* **Lynx NDAA-Compliant Version:** 190 grams
* **Lynx Full Solution (including gimbal, mainboard, wiring):** Ranges from **320g to 365g**, depending on configuration

</details>

<details>

<summary>What is the default IP of the MAINBOARD?</summary>

Default Mainboard IP: **192.168.144.240**

</details>

<details>

<summary>Is it possible to receive the video feed over Ethernet Without the Mainboard?</summary>

It’s not possible. LYNX supports video streaming via Ethernet and HDMI through our mainboard. Please note that LYNX does not support custom development or modification of its camera driver.

</details>


---

# 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/gremsy-tiny-series/lynx/faq.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.