> 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/gimbals-for-m300-m350/pixy-sm/getting-started/introduction.md).

# Introduction

## OVERVIEW

Pixy SM is specially designed to integrate the leading professional M300 RTK drone with the full-frame mirrorless Sony α7R IV camera, offering an unbeatable combination for precision aerial mapping missions.

<figure><img src="https://3309772875-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnikHUDUd2JXqkOsnOi7l%2Fuploads%2FJvSRqPG3q5xvCJxZVGYb%2Forder-gimbal.gif?alt=media&amp;token=c05c713d-893c-4ccd-a1b9-0799df582e25" alt=""><figcaption></figcaption></figure>

## FEATURES

### PLUG & PLAY WITH M300 RTK

Utilizing the built-in advanced processing module, integrating with M300 RTK is quick and straightforward within seconds. Just mount, connect, and you’re ready to go.

<figure><img src="https://3309772875-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnikHUDUd2JXqkOsnOi7l%2Fuploads%2F64TEwUZnkplLKSj5v70g%2Fplug-play.gif?alt=media&amp;token=418199a6-83e8-4b9d-bc70-d48f5ab43d50" alt=""><figcaption></figcaption></figure>

### FULLY COMPATIBLE WITH SONY Α7R IV

Pixy SM is optimized to work perfectly with the 61-megapixel Sony α7R IV, ensuring that you can get high-resolution imagery for creating accurate maps.

Supported lens: 28mm, 35mm, 55mm

Recommended SD cards: 256GB, at least 90MB/s read/write speed.

### BUILT FOR MAPPING

In concert with M300 RTK and Sony α7R IV, Pixy SM brings out the best-ever-grade mapping solution for geospatial experts.

<figure><img src="https://3309772875-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnikHUDUd2JXqkOsnOi7l%2Fuploads%2F8Wcsi5onLQ5Kz4c5QBAN%2Fimage.png?alt=media&amp;token=656412b2-ede7-487b-aef1-2aef78cd9cba" alt=""><figcaption></figcaption></figure>

### HEATED & TEMPERATURE CONTROLLED IMU

Heated and temperature controlled IMU sensor allows reliable performance even in extreme weather. Temperature is maintained within 0.2 degrees Celsius accuracy.

<figure><img src="https://3309772875-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnikHUDUd2JXqkOsnOi7l%2Fuploads%2FET5L0cI5PtzDEt7YjqAv%2Fcamera-control.png?alt=media&amp;token=2559a308-80f6-4529-a615-6b57c2bc4865" alt=""><figcaption></figcaption></figure>

### HIGH PERFORMANCE GIMBAL CONTROLLER & IMAGE PROCESSOR

Advanced gimbal controller designed and made by Gremsy based on a 32 bit high performance ARM microprocessor providing fast response and accurate calculation. Combine with high performance data & image processors that allow to process the image and GPS data as highest accuracy during mission.


---

# 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/gimbals-for-m300-m350/pixy-sm/getting-started/introduction.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.